Respectfully,
while yosemite's solution works, it breaks ALL the functionality of mod_security.
The BETTER way to fix any posting issues that mod_security might be causing is to simply upload an .htaccess with :
SecFilterInheritance Off
into your /wp-admin directory.
Once done, files in that directory are not subject to mod_security and you have still retained the ability to use mod_security for comment filtering, sql injection protection etc..
key and jenn: I just got up and checked this thread first. I just wanted to say: wheee.
Thanks to handysolo and you two for your patience ;')
EDIT: I'd still forward a note to your tech-support about updating their mod_security rules. Their current mod_security rules will break things for their other customers too.
whoami: Take another look at the .htaccess rule listed, it is specific to (only) the options.php file. Your suggestion would disable mod_security for every file under wp-admin/.
you are correct and I apologize for mis-reading your post. You replied with a workable solution to the original problem in this thread.
That said, and I state this as well in the other thread, if mod_security is getting in the way of updating options, its going to get in the way of other things -- consequently I reccommend disabling it all-together for ONLY the wp-admin dir.
One could, of course, disable it for single pages as they see problems, but then, most people arent that patient.
Posted 5 years ago #
just wanted to say thank you! I had the same problem an fixed after following your instructions. Thank you
Posted 5 years ago #
I want to thank Yosemite as well, for the code! I was experiencing the same problems when installing CuteNews, and was getting extremely impatient with the lack of help assisted in their forums so I ended up switching to WordPress. Then, I experienced the same problems from WordPress but luckily, I was able to find this thread! Many other people I know were experiencing the same errors and were getting as fustrated so I helped them out (crediting you obviously!) so you've really helped a lot of us!! Thanks a lot! You are a genius!
Btw, I am under Netrillium too.
Posted 5 years ago #
Same here!
1/ The reading options were not working...
2/ After MANY test like a user above in this thread, I found the exact word "union", in any post, would also lead to the same error...
These MOD_SECURITY issues were solved by putting an .htaccess file in /wp-admin using the following code:
<Files options.php>
SecFilterInheritance Off
</Files>
<Files post.php>
SecFilterInheritance Off
</Files>
Thank you guys :-)
Welcome! But without HandySolo, key and jennsoer I doubt the solution would have ever floated up.
Posted 5 years ago #
Hello everyone, i can't begin to tell you how much thankful i am, i have read EVERY SINGLE thread in this support forum and i was starting to think it was impossible to solve. I just instaled WP yesterday since i got tired of being a blogspot person always learning the hard way. So i got hosting, domain, latest WP, importing my beta blogger posts (hours and hours and hours of not-fun), so when i was checking my settings for options/reading the same thing over-explained here happened.
So i've been literally for hours trying to solve the thing and voila !!! so thank you very very very much hahahahaha. I had it figured out by the <Files options-reading.php>
SecFilterInheritance Off
</Files> mistake, i tried the options.php way and had it work. Then i come back here and try to post you guys on the solution, kept reading and saw you came to it by yourselves. Anyways, i wouldnt have been able to do it if it wasnt for the last 2 topic pages....
Hugs and millions of thanks from Mexico City :)
F.
Posted 5 years ago #
Thank you guys. I had the same problem with updating my General Options and Read Options in WordPress version 2.1. After uploading .htaccess with
<Files options.php>
SecFilterInheritance Off
</Files>
the problem was solved.
Thank you very much.
This topic has been closed to new replies.
