| Title | Bugzilla patch breaks editparams on Bugzilla 2.18rc2 |
| Status | closed |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | Applying the P4DTI Bugzilla patch breaks the Bugzilla user interface (for Bugzilla versions from 2.17.7 onwards) until the next time the checksetup.pl Bugzilla script is run. In particular, the editparams.cgi script is broken, and generates the message "No value for param p4dti (try running checksetup.pl again) at Bugzilla/Config.pm line 161.". Running the checksetup.pl script again fixes the problem. |
| Analysis | Reported by Gerry Thompson at Perforce. [1] The editparams script now requires there to be a current value for every parameter, so adding a new parameter in defparams.pl breaks it. The AG should instruct to run checksetup.pl again. I have also created Bugzilla bug 255537 [2], which was RESOLVED/WONTFIX by the Bugzilla project leader: "That was done on purpose because usually when a param that didn't previously exist magically shows up, it means a patch has been applied, and usually patches need to have setup done (which checksetup.pl does)." So our only option is to update the AG to advise running checksetup.pl. |
| How found | customer |
| Evidence | [1] <http://info.ravenbrook.com/mail/2004/08/10/16-08-40/0.txt>[2] < http://bugzilla.mozilla.org/show_bug.cgi?id=255537> |
| Observed in | 2.2.0 |
| Introduced in | 2.2.0 |
| Created by | Nick Barnes |
| Created on | 2004-08-13 17:26:07 |
| Last modified by | Nick Barnes |
| Last modified on | 2004-10-04 17:09:14 |
| History | 2004-08-13 NB Created. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 120417 | closed | 2004-10-04 17:09:05 | Nick Barnes | Add checksetup step to Bugzilla installation instructions. |