Project

General

Profile

Bug #7900

Bastion pages fail to load due to error in CurrentUser JSON

Added by Eric Helms over 7 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Web UI
Target version:
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Uncaught SyntaxError: Unexpected token
angular.js?body=1:1037
Uncaught Error: [$injector:modulerr] Failed to instantiate module Bastion.activation-keys due to:
Error: [$injector:modulerr] Failed to instantiate module Bastion due to:
Error: [$injector:unpr] Unknown provider: BastionConfig
http://errors.angular...<omitted>...1)


Related issues

Has duplicate Katello - Bug #7901: Pages fail to load correctlyDuplicate2014-10-10

Associated revisions

Revision 7f6af41a (diff)
Added by Eric Helms over 7 years ago

Fixes #7900: Bastion pages couldn't load due to unparseable User.to_json

A change to the User model led some fields to be unparseable when
User.current.to_json is done within the layout. This reduces the fields
to only those specifically needed by the UI.

Revision 18a89203
Added by Eric Helms over 7 years ago

Merge pull request #4733 from ehelms/fixes-7900

Fixes #7900: Bastion pages couldn't load due to unparseable User.to_json

History

#1 Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/4733 added
  • Pull request deleted ()

#2 Updated by Eric Helms over 7 years ago

  • Has duplicate Bug #7901: Pages fail to load correctly added

#3 Updated by Eric Helms over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF