Y’know, if this happens all the time, even with a clean, uncustomized using-the-default-theme install, then maybe you should check with your host to see if they have any ideas, are doing something strange, or have “upgraded” or otherwise changed one of the programs which enable wp to work on their servers (such as apache, php, mysql…. um. You’re not on an IIS server are you?)
Maybe your host has installed mod_security. Put this in your .htaccess:
SecFilterEngine off
(to turn mod_security off), and hopefully you won’t see the error anymore. Good luck.
Dear Experts….I continue my experiment. Hopefully your comments and my trial and error will help others who may come across this same problem.
Here is the latest.
The directory I put wordpress in is online-dating-blog
It has been indexed by google.
So in my endeavors to fix the Precondition Error, I would rename the directory to something like online-dating-blog-backup.
Create a new directory, and again call it online-dating-blog and installl WordPress again. Would get the same Precondition failed error right after the install (no changes made).
This time I installed WordPress and put it in a directory called dating
Went in to check out WordPress and no errors.
So is there a rule in WordPress about naming your directories with hyphens? I didn’t read any?
Any guess why when I used the directory name online-dating-blog I get this Precondition error, but if I install WordPress in another directory with a single name I do not get this error?
Hmmmm, any clues would be appreciated. If I have to not use that directory name I guess that is ok….but again, only because it is already indexed by google I was trying to keep the same name.
By the way, this precondition error did not always exist. It started about 2 weeks ago — at least a month prior to that I never saw this error even with my directory named online-dating-blog. It’s like once the error started, that directory is no good anymore. I can see the error continuing with the first install, but when I do a fresh install and use the same name for my directory, why would I get the error then…..????????
puzzling?????????
Steve
I still think it’s something your host did. You changed nothing between when it was working and when it borked. To me that ALWAYS smells of something the host did and may not want to admit to.
Unless you did something you’ve forgotten you did?
Vkaryl
I agree….for some reason it smells like a host thing. But what I don’t understand is why would it work under a different directory name and not under the name online-dating-blog. I don’t know enough about the host side of the house to even have a clue.
My host is Ipower….man, they really don’t want to take responsibility for any software that I may install. However, in the past if I was able to tell them specifically what the problem was, I may get them to help. Again, any clue why it would work on the server under a diretory called dating but not under a directory called online-dating-blog — especially when it worked at one time under this directory name.
I absolutely couldn’t say…. unless this is due to something they do moving stuff around on shared servers (NOT unlikely…. I’ve not heard great things about Ipower….)
This isn’t of course an option if you’re cash-strapped…. but if it were me, I would move to a new host and see if I had the same problem there. If not, then it’s fairly obvious the culprit is Ipower, ain’t?
