In Bug 3326, Jared resolved the odd display of ampersands caused by Zebra's odd encoding of them for the OPAC, and XSLT display was fixed for the opac, but non-XSLT display still shows the oddity. Two-line patch coming momentarily, for both Master and 3.6.x, which both exhibit this behavior.
Created attachment 7628 [details] [review] Proposed patch
In my first note, I typed, still sleepily, "Jared resolved the odd display of ampersands caused by Zebra's odd encoding of them for the OPAC" ...that should be for the *staff client*, of course.
Created attachment 7706 [details] [review] [Signed Off] Bug 7535: ampersands not showing properly in non-XSLT OPAC Jared's fix for Bug 3326 fixed this in the staff client, but not the OPAC; moving this one line fixes it both places. Signed-off-by: Liz Rea <wizzyrea@gmail.com> This can be replicated by indexing with -x OPACXSLTResults must be set to "normally" Reproduced original bug with rebuild-zebra.pl -x -b -w -r -v -v Patch corrects the issue, does not change intranet behavior.
QA comment: tiny patch, passed QA Note that + $data =~ s/\&\;amp\; /\&\; /g; is not made in output_with_http_headers It means that, if we don't output something *not* html, and the string replaced is present, it will be replaced, and that could be not what we're expecting. Howver, the risk is less than tiny, so I accept this patch.
There have been no further reports of problems so I am marking this bug resolved.