Weirdness with posts containing specific words could be due to mod_security on Apache. Worth asking the host if they’re doing anything with that…
I have the same problem with a post which has been online for several months and suddenly disappeared for no apparent reason. In addition to the “Not Found” advisory, the following error message was generated:
WordPress database error: [Can’t create/write to file ‘C:\DOCUME~1\mysql\LOCALS~1\Temp\#sql_b8_0.MYD’ (Errcode: 17)]
SELECT DISTINCT * FROM wp_posts WHERE 1=1 AND post_date_gmt <= ‘2007-03-08 21:46:59’ AND (post_status = “publish”) AND post_status != “attachment” GROUP BY wp_posts.ID ORDER BY post_date DESC LIMIT 0, 10
Dutch Schaal’s Blog Heaven
As I said, the post was initially successful and has been residing on the site for some time.
(@iampariah)
17 years, 4 months ago
One of my clients’ sites is having serious WP problems, and I’m at a loss.
PHP 4.4.3, WP 2.03 and then 2.05
Symptom 1: Visitors try to comment and randomly receive this error message from /wp-comments-post.php : “Not Found, Sorry, but you are looking for something that isn’t here”.
Symptom 2: The above error, as well as other odd behaviors, seem related to the length of the comment AND to its CONTENT (strange, but true).
Comments that are more than 10 characters or so fail, while very short ones usually successfully post. I’m not talking about fifty page comments, just a couple hundred words. It’s like WP is not recognizing that the comments field in mysql is set to Text.
ALSO, posts (not comments) that use the word “converted” fail to post. Hitting Save, Save and Continue Editing, or Publish jump the user to the home page and fail to create the post.
Steps taken (without success):
– Run repair and optimize on the db.
– Upgraded site from WP 2.03 to WP 2.05
– Checked all directory and file permissions against the WP Codex list of what they should be.
– Flushed and regenerated .htaccess and permalinks
All my other WP sites work without these issues, and the client hasn’t changed anything.
The problems all started happening when the client upgraded his virtual server to a bigger one 3 weeks ago. From what I can tell, the hosting company did a clean install of PHP, Apache, and so on, but I THINK something got left off, they’re using a different PHP wrapper, or something else is wrong on the server.
I’ve got the client asking the hosting company about the new environment, including directory owner and authorized script owners.
Any suggestions or help? Anyone seen these behaviors before?
Thanks you!