2015-01-22, 20:46:09
Further to my earlier report of Save throwing an error in Settings/Theme or Settings/Fields:
I have found that if I delete the "http://" default content of the Image field 'Default' entry, that Settings/Fields then saves fine. Other content is ok, it just doesn't seem to like "http://".
Similarly, if I delete all of the content from all of the Settings/Theme sections, it saves ok too. Manually pasting back the default content (progressively, a section at a time) saves ok for the 'Header' section, but when I get to the '(Index) Categories' section it throws the error again when I try to save after pasting back in:
So I'm wondering if some of the default install content is triggering mod_sec on my server. I've not had a mod_sec problem elsewhere.
Any thoughts?
I have found that if I delete the "http://" default content of the Image field 'Default' entry, that Settings/Fields then saves fine. Other content is ok, it just doesn't seem to like "http://".
Similarly, if I delete all of the content from all of the Settings/Theme sections, it saves ok too. Manually pasting back the default content (progressively, a section at a time) saves ok for the 'Header' section, but when I get to the '(Index) Categories' section it throws the error again when I try to save after pasting back in:
PHP Code:
<h3>
<a href="<?php echo catalog_get_category_url($category->get('slug')); ?>"><?php echo $category->get('title'); ?></a>
</h3>
So I'm wondering if some of the default install content is triggering mod_sec on my server. I've not had a mod_sec problem elsewhere.
Any thoughts?