kwdavids

Sorry, this was entered twice. Ignore this one.

There is a plug-in called “Widgets on pages” that provides a general solution.

I use WP Super Cache on one of the blogs that get errors and I don’t use it on another that got errors.

If you are suggesting that I use these plug-ins instead of XCache, I would just note that the blog that uses WP SuperCache is heavily commented (I have 185,000 comments on it), so pages have to be re-generated a lot.

I don’t see any problems with my site except that it uses 5-7x more memory when XCache is disabled.

I don’t have any XCache plug-in in my WordPress installation; it’s something my hosting company apparently does server wide.

Any time my site is messed up for 3 days, I want to understand what the problem is, and I would hope eventually not to need a custom .htaccess in the long term because various plug-ins play with that and it’s an accident waiting to happen again.

The plug-ins on that site are:

Akismet
Enhanced WP-ContactForm
Hotfix
Limit Login Attempts
TPC! Memory Usage
WordPress Database Backup
WP Photo Album Plus
WP Super Cache (not activated on this particular site)
Hello Dolly (not activated)

All are the latest version and the theme is Twenty Ten

https://www.blogordie.com

is one of the sites. I have disabled XCache, so you won’t see any errors. And when XCache is enabled, you can go for some time without seeing an error, and then there would be a cluster of them. For some reason, the most likely thing to fail is posting an article through the xmlrpc api using Microsoft Live Write.

I run WP SuperCache also, so the PHP doesn’t get run some of the time. Usually the error occurs to a user posting a comment. They get the error, but the comment posts anyway.

I can confirm the bug, and deactivating WordPress SEO makes it go away. However, I never compose posts with the WordPress editor in the first place, so it doesn’t make any difference to me.

I’ve used WordPress SEO for several months now, and the sitemap has never caused me a lick of trouble. I consider it one of the important features of the plug-in because other site-map-only plug-ins have caused me so much grief in the past.

Thanks, Impostercide looks like what I need. I’m surprised, though, that this isn’t a core feature.

I used a different browser and went to another blog. I was obviously not logged in because the Word Press bar the top was missing. I left a comment with the name of the owner of the blog. No problem.

Yeah, I get this all the time.

If you look at the code, the “200” return is supposed to be treated as not an error (the API function returns true). I guess it’s just broken somehow. I don’t know enough PHP to fix it.

It’s a real annoyance.

This can be caused by the /tmp directory on the server hosting MySQL being full. I think in my case it was caused by file system errors on the SAN, since I know there were disk problems at the time.

Yes, I have backups. The problem went away, however, without my doing anything.

The hosting company swears that they didn’t change anything in MySQL, but it got fixed. I looked in the error log and saw tons of errors, for example:

WordPress database error Got error 28 from storage engine for query SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy IN (‘link_category’) AND tt.count > 0 ORDER BY t.name ASC made by require, require_once, include, get_footer, locate_template, load_template, require_once, woo_footer_top, woo_do_atomic, do_action, call_user_func_array, woo_footer_sidebars, woo_sidebar, dynamic_sidebar, call_user_func_array, WidgetCache->widget_cache_redirected_callback, call_user_func_array, WP_Widget->display_callback, WP_Widget_Links->widget, wp_list_bookmarks, get_terms

and I also saw a bunch of these:

WordPress database error Duplicate column name ‘comment_subscribe_optin_mailed’ for query ALTER TABLE wp_comments ADD COLUMN comment_subscribe_optin_mailed enum(‘Y’,’N’) NOT NULL default ‘N’ made by require, require_once, do_action, call_user_func_array, lcp_output_js, include, comment_form, do_action, call_user_func_array, show_subscription_checkbox, sg_subscribe_start, sg_subscribe->sg_subscribe, sg_subscribe->db_upgrade_check

Same here.