Bug 1089789 - Login Broken for GWT Dev Mode
Summary: Login Broken for GWT Dev Mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.11
Hardware: All
OS: All
medium
low
Target Milestone: ---
: RHQ 4.11
Assignee: Jirka Kremser
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-22 02:05 UTC by Mike Thompson
Modified: 2014-07-21 10:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-07-21 10:14:00 UTC
Embargoed:


Attachments (Terms of Use)
Login failed screen. (113.17 KB, image/jpeg)
2014-04-22 02:07 UTC, Mike Thompson
no flags Details

Description Mike Thompson 2014-04-22 02:05:16 UTC
Description of problem:
This has been broken for about a week now. It seems the new look and feel changes have broken login in GWT dev mode.


Version-Release number of selected component (if applicable):
RHQ 4.11 Master


How reproducible: 
Always


Steps to Reproduce:
1. Login 
2. observe that you are not able to login

Actual results:
Unable to login in GWT Dev mode.


Expected results:
Should be able to login in GWT dev mode.


Additional info:
This will make it very difficult for any community members.

Comment 1 Mike Thompson 2014-04-22 02:07:27 UTC
Created attachment 888335 [details]
Login failed screen.

Comment 2 Jirka Kremser 2014-04-22 10:39:41 UTC
I've fixed that locally on 17th, but I forgot to push it. Here it is.

branch:  master
link:    https://github.com/rhq-project/rhq/commit/769bb647a
time:    2014-04-22 12:36:02 +0200
commit:  769bb647a4f448b3a3d6fb105e20ee1f4effe2e8
author:  Jirka Kremser - jkremser
message: [BZ 1089789] - Login Broken for GWT Dev Mode - Fixing the new login page
         for GWT development mode.

Comment 3 Heiko W. Rupp 2014-07-21 10:14:00 UTC
Bulk closing of RHQ 4.11 issues, now that RHQ 4.12 is out.

If you find an issue with those, please open a new BZ, linking to the old one.


Note You need to log in before you can comment on or make changes to this bug.