There is another blog that talks about this issue at http://php-memory-and-wordpress.iamuk.co.uk should anyone want to read more (this is not my blog!)

N.

I recently went through a three week hunt trying to fix that exact error.

Thing is, I run my on linux server, so I could manually set the limit myself. Once I got to 96M though… I figured, it wasn’t really a memory error, so I began looking at other things.

After considerable research, pain, and agony on my part (one of the blogs affected was my wife’s, hence “pain, and agony”), I started suspecting that it wasn’t PHP, or permissions, or files or anything so easy to fix, or easy to find.

I had recently moved my blogs from another host, and used the Wordpress export tool to move them to my new host. As it turns out, for some reason, the new database tables created with the export (upon importing) didn’t have “autoincrement” enabled on the primary index keys of the tables in the database… Once I added it, “voila!” Everything worked as expected again.

So, to make this long comment even longer, it seems that whilst the memory error was probably an accurate error message (I’m sure WP just churned and churned trying to pull some record from some table), it seems that the REAL reason this was happening, was an improperly configured database.

Anyways, just wanted to pass that on to someone… somewhere. Maybe it’ll help somebody.

Thanks for your blog!

Robert

One plugin didn’t reactivate, though. But no big.