Closed Bug 345200 Opened 19 years ago Closed 19 years ago

undef error - Can't find param named changer at Bugzilla/Config.pm line 171.

Categories

(Bugzilla :: Creating/Changing Bugs, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: after.fallout, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060710 Firefox/2.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060710 Firefox/2.0b1 Trying to change the product on multiple bugs (~ 750), only one gets changed and an internal error shows up in Bugzilla. Reproducible: Always Steps to Reproduce: 1. Install Bugzilla 2.22 (cvs update -rBugzilla_Stable -dP) 2. Have 2 products (hereafter AAA and BBB), AAA with a whole bunch of bugs 3. Perform a search to find a list of bugs in product AAA 4. Click the "Change Several bugs at once link" 5. Press the Check All button 6. Change the product to BBB 7. (Optional, depends on params I guess) Enter a comment 8. Click Commit button 9. Select version and component 10. Click Commit button Actual Results: Only one bug changed (first one in list); this message is displayed: Internal Error Bugzilla has suffered an internal error. Please save this page and send it to bugzilla@localhost.com with details of what you were doing at the time this message appeared. URL: http://192.168.21.60/bugzilla/process_bug.cgi undef error - Can't find param named changer at Bugzilla/Config.pm line 171. Expected Results: All bugs changed to new product
(In reply to comment #0) > undef error - Can't find param named changer at Bugzilla/Config.pm line 171. "changer" is not a valid parameter nor a valid field for bugmails in 2.22. It's only valid starting with 2.23. Could you reset your "newchangedmail" parameter in editparams.cgi?section=mta#newchangedmail and try again? Probably this parameter, which is a template for emails, contains the line: X-Bugzilla-Who: %changer% That's the reason of the failure. I cannot reproduce the bug on 2.22.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.