Open GoogleCodeExporter opened 9 years ago
We're having this trouble as well. It could be that our data has more special
characters that others, but it comes up quite frequently. Frequently enough
that we haven't rolled MobileCat out to our libraries. I would call this High
priority issue personally.
I'm all for a proper fix, but can you give me an idea where the utf8_encode()
would go?
Original comment by hopkin...@gmail.com
on 9 Dec 2011 at 5:57
For the time being I've modified the Smarty template for the search results
page to escape the title, author, etc. This isn't a very good fix because it
just throws away the content of the offending string - the entire string. But
it does give me the search results ;) Attached is a patch for your amusement.
Original comment by hopkin...@gmail.com
on 9 Dec 2011 at 7:58
Attachments:
Original issue reported on code.google.com by
dmh4%stm...@gtempaccount.com
on 24 May 2011 at 3:22