search

token454 / pwm

Automatically exported from code.google.com/p/pwm
0 stars 0 forks source link

PWM 1.7 User Interface Bugs #493

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
PWM 1.7. Apache 2.2.12 and Tomcat 6 on Linux server. 

There are some minor bugs on the last page (Changing the password) of the pwm 
process.

1. Password Guide is visible as a link even though not selected to be visible 
from the configuration editor. Clicking on it will give you a blank tiny page.

2. In the previous versions, if you click on any of the passwords, generated by 
the "Auto-generate a new password", the password field used to get populated 
with that password. It doesn't work anymore.

3. The Change Password button is enabled even you haven't entered the Password 
yet. 

4. The "Cancel" Button doesn't work, both on Chrome and IE. i.e. You will stay 
on the same page.
While using Chrome (version 30.0.1599.69), If you click the "Cancel" button, 
then Chrome gives you two options, "Stay on the Page" or "Leave the Page". If 
you select "Leave the page", you will stay on the same page and if you select 
"Stay on the page", you will stuck into the "Please Wait..." process and it 
won't proceed anywhere.

Hoping for a little guidance, please. Thanks

Original issue reported on code.google.com by haqa...@gmail.com on 9 Oct 2013 at 12:39

GoogleCodeExporter commented 8 years ago 
#1 and #2 are fixed in current builds.  #3 is working as designed, as disabling 
this button from the start inhibits some low-functioning javascript 
environments.  #4 the cancel button will take you to the location of the 
forwardURL parameter/setting and depending on circumstances it could very well 
keep you on the change password page.  If this is still an issue please open a 
new issue and include a trace log of the problem.

Original comment by jrivard on 11 Nov 2013 at 5:09

GoogleCodeExporter commented 8 years ago 
We are seeing exactly the same bugs in v 1.7, this does NOT appear to be fixed 
in the currently released build.

Original comment by Unibombe...@gmail.com on 18 Nov 2013 at 4:09

GoogleCodeExporter commented 8 years ago 
Could you identify which commit fixed issues #1 and #2? I would like to fix 
them in my version if possible but don't want to move to the latest build.

Original comment by andypturner on 18 Nov 2013 at 4:49