shockdiode

Hello there,

I’m also curious about this. Any news at all here?

@ylyman: Turn them back on one by one until you figure out which one caused it. I’m guessing it was the extreme seo plugin for you as well as everyone using that seems to be seeing that same error today.

Between the gibberish being spit out on posts by your activation routines the other night when the script calls home and the current “got error 134 from storage engine” (you’ve got a table somewhere that needs to be repaired) – I can’t say I can recommend this to anyone at the moment.

Just started seeing this on a client site that was using the “extreme seo” plugin. Shutting that off resolved it here.

That plugin was spitting out gibberish the other day as well due to a malformed php file on the site that plugin calls home to so I’m recommending my client stay away from it.

macmanx’ suggestion of shutting off all plugins is a good place to start for sure.

Otherwise, try repairing wp_posts and wp_postmeta.