[SOLVED] AjaxSearch and iso-8859-1 MODx System Setting

I recently upgraded a site to MODx 1.0.2 with the latest AjaxSearch 1.8.4

All is working fine except I now see strange characters () just before the AjaxSearch box that were not there before. The html for the page has:

I am using "Western European (ISO) - iso-8859-1" instead of "Unicode (UTF-8) - utf-8" for character encoding in the MODx system settings, but should that still be ok?

All the templates files are encoded in UTF-8.
So open the file templates/layout.tpl.html, check if exists a weird character somewhere and save the file as iso-8859-1.

Quote from: coroico at Nov 24, 2009, 09:25 AM

All the templates files are encoded in UTF-8.
So open the file templates/layout.tpl.html, check if exists a weird character somewhere and save the file as iso-8859-1.

Thanks for replying coroico. I checked the layout template and no weird characters. I put a test character at the start of that template and the weird characters are output before it so these weird characters are earlier in the logic?

Ok check the language file and your configuration file (if you have a custom file)

No custom configuration file. Language file looks fine.

I have just put the layout.tpl.html content in a chunk and called it via the &tplLayout parameter and that works. As a workaround I can set all the templates as chunks &tplResults , &tplResult etc but if I can get it to use the default files it would be much more simple.

ah, As I had not seen strange characters in the file I did not save it as ANSI . In doing so it seems to work. I’ll re-save all the other templates and hopefully that will be it. So have you changed the way you save the files in recent versions? Presumably anyone not using UTF-8 would need to do the same re-saving? Thanks for your help!