AnsweredAssumed Answered

Search results: Escaped forward slash issue since upgrade from 3.3 to 4.2.f

Question asked by markd.paulson on Jan 29, 2016
The results of Lucene searches have been a problem since we upgraded. Everything works fine except for the fact that every forward slash has been escaped (gets returned with a backslash in front of it). This happens for every field. When I look in Alfresco Explorer the backslashes are not there. I've tried to look for places in the code where JSON objects are created or encoding or decoding happens, but I'm just not finding any obvious issues.

Where should I be looking?
Is there something in 4.2.f encodes forward slashes, but didn't in 3.3? New JSON version?

Outcomes