Number validation in org unit settings creates problem with opac login
Bug #476794 reported by
James Fournie
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Low
|
Unassigned |
Bug Description
In the org unit settings, the validation on NumberTextBox causes large values to be formatted like "7,200". They are stored like this in the database. This was causing havoc with the opac timeout setting, making it impossible to login (a dialog would immediately popup saying you will be logged out). I have made a quick fix for this by using a ValidationTextBox with a regex instead.
Changed in evergreen: | |
importance: | Undecided → Low |
status: | New → Triaged |
To post a comment you must log in.
Hi James:
I tried this out (without your patch) on trunk, and it saved the value as "7200" in the database. I did see the form flip the value to 7,200 briefly after I hit "Okay" but the value itself was saved without being reformatted.
Maybe this is a problem in branches prior to trunk - possibly compounded by the version of Dojo in use. Can you include the version of Evergreen you're testing against & the version of Dojo in use?