Closed
Bug 324784
Opened 19 years ago
Closed 18 years ago
editgroups.cgi should make sure groups it edits/removes are not used by editparams.cgi
Categories
(Bugzilla :: Administration, task)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.22
People
(Reporter: LpSolit, Assigned: LpSolit)
References
Details
Attachments
(1 file)
(deleted),
patch
|
wicked
:
review+
|
Details | Diff | Splinter Review |
There are some missing checks in editgroups.cgi IMO. It should:
1) update groups in editparams.cgi (or more exactly in data/params) when a group used by it is renamed;
2) reject to delete a group if the group is used in editparams.cgi.
If you set insidergroup to groupA and then you rename or delete groupA, editparams.cgi will still mention groupA as being the insidergroup despite this group no longer exists. And so all "private" comments and attachments are inaccessible.
Marking as depending on bug 324783 as editparams.cgi should also not let you use inexistent groups.
Again, I would tend to take it for 2.22.
Assignee | ||
Comment 1•18 years ago
|
||
Reversing dependencies.
Assignee | ||
Comment 2•18 years ago
|
||
If a group used by chartgroup, insidergroup or timetrackinggroup is renamed, update data/params accordingly. If one tries to delete it, reject this deletion.
Attachment #223636 -
Flags: review?(wicked+bz)
Comment 3•18 years ago
|
||
Comment on attachment 223636 [details] [diff] [review]
patch, v1
Group list only shows first parameter that uses the group. Other than that, this seems to work as advertised.
Attachment #223636 -
Flags: review?(wicked+bz) → review+
Updated•18 years ago
|
Flags: approval?
Comment 4•18 years ago
|
||
ooh, by all means. :)
Can we backport this to the older branches that contain group names in editparams?
Flags: approval? → approval+
Assignee | ||
Comment 5•18 years ago
|
||
(19:50:45) LpSolit: justdave: on *all* branches? or 2.22 only?
(19:52:15) justdave: umm, any that aren't locked to security-only yet
(19:53:06) LpSolit: so 2.22 only
(20:03:02) LpSolit: justdave: if you approve bug 323525 for 2.22, my patch would apply cleanly on the 2.22 branch too
Meanwhile, here is the checkin for tip:
Checking in editgroups.cgi;
/cvsroot/mozilla/webtools/bugzilla/editgroups.cgi,v <-- editgroups.cgi
new revision: 1.70; previous revision: 1.69
done
Checking in template/en/default/admin/groups/list.html.tmpl;
/cvsroot/mozilla/webtools/bugzilla/template/en/default/admin/groups/list.html.tmpl,v <-- list.html.tmpl
new revision: 1.6; previous revision: 1.5
done
Checking in template/en/default/global/user-error.html.tmpl;
/cvsroot/mozilla/webtools/bugzilla/template/en/default/global/user-error.html.tmpl,v <-- user-error.html.tmpl
new revision: 1.169; previous revision: 1.168
done
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•18 years ago
|
||
Assuming bug 323525 is approved for 2.22, requesting approval for 2.22 too.
Flags: approval2.22?
Comment 7•18 years ago
|
||
reopening just to make sure it doesn't get lost since we still have pending
checkin
Status: RESOLVED → REOPENED
Flags: approval2.22? → approval2.22+
Resolution: FIXED → ---
Assignee | ||
Comment 8•18 years ago
|
||
2.22:
Checking in editgroups.cgi;
/cvsroot/mozilla/webtools/bugzilla/editgroups.cgi,v <-- editgroups.cgi
new revision: 1.65.2.1; previous revision: 1.65
done
Checking in template/en/default/admin/groups/list.html.tmpl;
/cvsroot/mozilla/webtools/bugzilla/template/en/default/admin/groups/list.html.tmpl,v <-- list.html.tmpl
new revision: 1.4.2.2; previous revision: 1.4.2.1
done
Checking in template/en/default/global/user-error.html.tmpl;
/cvsroot/mozilla/webtools/bugzilla/template/en/default/global/user-error.html.tmpl,v <-- user-error.html.tmpl
new revision: 1.145.2.11; previous revision: 1.145.2.10
done
Status: REOPENED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → FIXED
Target Milestone: Bugzilla 2.24 → Bugzilla 2.22
You need to log in
before you can comment on or make changes to this bug.
Description
•