WordPress MU

This error message:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 146379 bytes) in /home/cburell/public_html/wp-includes/cache.php on line 48

is causing a millon problems.

It's preventing activation of new accounts.

It's preventing activation of widgets.

etc.

I looked at line 48 and it's blank.

Hm. Replaced the Automattic WP widgets plugin with the latest version and that improved things (more details soon).

Now widgets can be activated and activation emails are being sent, but so far no follow-up password/login email has arrived.

More soon. Don't want anyone wasting time since it's improving. Stay tuned... :)

That's php using more than the "default" 8M.

Not an uncommon problem on shared hosting.

Only thing you can do is ask your host to see if they can bump up the max memory setting in php.ini. 12M should do it, 16 would be better.

Something that "might" help is turning on the object cache.

In your wp-config.php file, right under where it sets the table prefix, add this:

define('ENABLE_CACHE', true);

Might help, might not. Hard to say since each shared host sets up their boxes different.

Re: the wp-config.php hack, like so?...From this

// Change the prefix if you want to have multiple blogs in a single database.
$table_prefix  = 'wp_';   // example: 'wp_' or 'b2' or 'mylogin_'

// Change this to localize WordPress.  A corresponding MO file for the

to this?....

// Change the prefix if you want to have multiple blogs in a single database.
$table_prefix  = 'wp_';   // example: 'wp_' or 'b2' or 'mylogin_'
define('ENABLE_CACHE', true);
// Change this to localize WordPress.  A corresponding MO file for the

Thanks for the bazillionth time.

"I'm going to buy you a nice fruitbasket."
--Bill Murray, _Ghostbusters_

lunabyte, when I add that line to enable cache, I get this msg:

[a fatal error or timeout occurred while processing this directive]

I'm adding it exactly as copied in the post right above this one.

Thanks~

Wow.
No offense, but your VPS is sounding like it wasn't such a good deal.

If your "site" isn't going to be freely available to everyone, and you're keeping it kind of small (less than 100 users), you might try something like Media Temple's Grid Server. It seems to be working for people.

With the combination of MU, and whatever else is being processed by php that's set by the host, it's eating up more memory than what is specified in php.ini. By default it's set to 8M, but I'd ssh into your box and raise it to 16M. Might work, might not. Hard to tell.

Google search just for reference.

Thanks both.

I sent a Service Ticket to the VPS tech support--the jury's still out on them, with so far one great helper and one ogre--and they seemed to debug whatever the problem was.

Thanks again :)