Nov 28
Ever seen this? Ever created a huge article, pressed “Save” or “Publish” and the whole work has gone? Good. I had it to and I hated it.
When I was writing one of my last articles I had this error again. I just had enough, I wanted to find the reason behind it. So I took my article and started to paste it paragraph by paragraph, then sentence by sentence, then word-by-word until I found the error. The word “fetch” caused this error. After doing some research, I managed to find some solutions to this error (some other words cause this stupid error as well, such as <iframe>).
The solution is simple yet efficent. Create a .htaccess file and place it to your Wordpress admin directory and add the following to it:
<IfModule mod_security.c> SecFilterEngine Off </IfModule>
December 22nd, 2007 at 9:04 am
Thankyou so much!
I will like to this site on my next blog post, you have been a great help!
December 22nd, 2007 at 3:04 pm
I’m glad I could help
April 26th, 2008 at 4:05 pm
thanks a lot. this problem was quite annoying!
June 5th, 2008 at 3:59 pm
THX! ;D
July 1st, 2008 at 8:34 pm
I have the same problem as well. And after some digging, I found the problem is I used the word “select”. Unexpected and annoyed.
BTW, do you (or anyone) have the list of these “forbidden words”?
July 2nd, 2008 at 11:34 am
cheers for the comment mate.
Unfortunately I don’t have such a list tho I believe if you add those lines to your .htaccess you don’t have to worry about these things anymore
August 18th, 2008 at 6:39 pm
Just an update. This time is the order of words cause the error. The order is “from the”.
I’ll see if I can find anymore words and post some updates.
October 1st, 2008 at 9:13 pm
Thanks,
You just save me from a nightmare.
I was using BlogJet and found the similar error.
Thanks again,
Rui
October 24th, 2008 at 1:46 am
[...] http://tamaspiros.co.uk/2007/11/28/wordpress-error-404-postphp-was-not-found-on-this-server/ (the solution provided is to create another .htaccess file with additional code so as to override the security of WordPress) [...]
February 1st, 2009 at 3:57 pm
Interesting enough I encountered this “word” error this morning. However, after implementing your suggested code my wordpress is still spitting out an error every new edit or so. Has anyone found any other releated info on this?
February 23rd, 2009 at 10:02 am
It doesn’t work with new and draft posts?
March 27th, 2009 at 2:19 pm
This issue has to do with Mod Security on your server.
I spent 40 mins troubleshooting this with my host.
You need to whitelist certain files in your wp-admin area. Or, if you can, whitelist all of the files in wp-admin.
DO NOT use the mod_sec workarounds that seem to be posted several places on the web.
July 31st, 2009 at 4:13 pm
Thankyou so much!
January 14th, 2010 at 3:57 pm
?m glad I could help