Comment 12 for bug 1822630

I know that I've added my signoff for this, but some additional testing indicates that 3.2, and probably 3.1, may need a different version of the place_hold_result.tt2 patch. We're getting an internal server error with this patch applied after placing a hold. I"m not sure, yet, how much of this is due to code drift and how much could be a local customizaiton. I do know that backing out the change to place_hold_result.tt2 resolves it, and we have not customized that template.

I should also rebuild one of my virtual machines to more thoroughly test this with master.