Closed
Bug 90933
Opened 23 years ago
Closed 23 years ago
different handling of disabledtext
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.14
People
(Reporter: gruetzmacher, Assigned: jacob)
Details
Attachments
(1 file)
1.02 KB,
patch
|
Details | Diff | Splinter Review |
creating a user by using editusers.cgi (administrative) the field disabled text will be set to '' (because the edit field is empty) Using the login screen (results in globals.pl:InsertNewUser) the field will not be set and keeps NULL This results in hang of edit user created in the second way - the details screen (editusers.cgi?action=edit&user=...) will never be opened You can fix this by setting disabled text to '' in globals.pl
Assignee | ||
Comment 1•23 years ago
|
||
Hmm... I haven't seen this particular issue with editusers not loading, but there does seem to be some inconsitancy w/the way disabledtext is handled, even just within checksetup.pl. At line 1012 where it is defined in the table declaration, it's simply "disabledtext mediumtext", but at line 1828 where the AddField is called to add it to a pre-existing database, it's defined as "disabledtext mediumtext not null". I think the proper declaration should be "not null" which would make an it "" when empty rather than null. Patch to checksetup.pl forthcoming. If this is causing the problems described here, it should be included in 2.14.
Assignee | ||
Comment 2•23 years ago
|
||
Comment 3•23 years ago
|
||
r= justdave checked in
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 4•23 years ago
|
||
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: Bugzilla 2.12 → unspecified
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•