I’m afraid I have no idea what the problem is (if it’s not mod_security), but you might be able to work around it by putting the troublesome words in a snippet. So, instead of this:
onclick("whatever")
You’d have [[oc]] and a snippet called oc with this code:
<?php
return 'onclick("whatever")';
?>
-
MODX Staff
- 12,272 Posts
I really do suspect mod_security or some other server (mis)configuration.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Quote from: cbaone at Apr 23, 2010, 02:19 PM
@thingstodo: I wish that were the case for me! I tried adding those commands to the .htaccess file one by one with no luck, but glad you got it sorted out!
Are you sure the host is processing the .htaccess file? Some don’t.
Yes. It is processing the file because I get errors sometimes when I change it. Besides, FURLs are enabled...
If I’m doing a webpage in swedish with collation utf8_general_ci // the best one in the world
and choose Swedish as manager language instead of Swedish-utf8 I have seen the
same behaviours of what is described here.
So are the manager language file in same charset as the collation of your database.
All collations match. That’s actually the first thing I checked.
If utf8 have you made sure the utf8 lang file is coded without "BOOM"
Not sure how I check for "BOOM"??
-
MODX Staff
- 1,535 Posts
LOL - I think mrhaw means BOM (Byte Order Mark) - when you save a file in a code editor, you normally have the option to save as "UTF8 - No BOM". That’s the desired format for UTF8 files as the presence of the BOM can cause issues with PHP.
Now, if you haven’t changed any of your language files, then I think they should be in the correct format anyhow. But, maybe worth a check.
Garry Nutting
Senior Developer
MODX, LLC
Email:
[email protected]
Twitter: @garryn
Web: modx.com