Closed
Bug 132961
Opened 23 years ago
Closed 16 years ago
Relax permission checking to account for data corruption.
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement, P4)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: CodeMachine, Unassigned)
Details
Currently when data corruption occurs users can get errors about trying to
change fields they never tried to touch. See bug #101380 and bug #64760.
I think we should relax the permission checking so these can go through.
Basically the situation is that some tranformation gets done. Rather than
checking that Old /= Transformed(New), we should check that Transformed(Old) /=
Transformed(New).
|
||
Comment 1•23 years ago
|
||
Maybe just have an exception for old==new?
|
Reporter | |
Comment 2•23 years ago
|
||
The problem is old /= new, but through no fault of whoever gets blamed.
|
|
||
Comment 3•23 years ago
|
||
We don't transform when setting form values, apart from escaping which the
browser is meant to undo for us.
For the keywords problem, at least, old would be == new, even if they were invalid.
|
|
Reporter | |
Updated•23 years ago
|
Priority: -- → P4
Target Milestone: --- → Bugzilla 2.20
|
|
||
Updated•22 years ago
|
OS: Linux → All
Hardware: PC → All
|
||
Comment 4•21 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged
enhancement that hasn't already landed is being pushed out. If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee: myk → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
|
|
||
Comment 5•16 years ago
|
||
If data corruption occurs, we want to understand why, and fix it in the DB rather than ignoring them.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•