WP-Super-Cache reverting to Half ON

You’ve probably got another option in the plugin set on that requires half-on mode. It’s 99% as fast anyway so nothing really to worry about unless you regularly get *huge* traffic spikes.

The only options I have on are “Don’t cache pages for logged in users” and “Proudly tell the world your server is Digg proof!”

Maybe Bad Behavior? That’s turned on.

Anyway, what does the ON option do?

It’s Bad Behaviour.

Read the readme.txt for the rest. It’s all in there!

The Super Cache readme file has nothing I could see about it.

The Bad Behavior readme file has this:

Edit the wp-content/plugins/wp-cache/wp-cache-phase1.php or wp-content/plugins/wp-super-cache/wp-cache-phase1.php file and find the following two lines at around line 34 (line 56 in WP-Super Cache):

if (! ($meta = unserialize(@file_get_contents($meta_pathname))) )
		return true;

Immediately after this, insert the following line:

require_once( ABSPATH . 'wp-content/plugins/Bad-Behavior/bad-behavior-generic.php');

First, the phase1 code is different.

Second, it would be quite simply for you to check in the code if Bad Behavior is enabled and if so, require_once the relevant module.

How about it?

Load up the Supercache admin page again and scroll to the bottom:

Bad Behaviour support is disabled.(Only half-on caching supported, disabled compression and requires Bad Behavior in “/www/wp-content/plugins/bad-behavior/”)

I meant that the readme.txt tells you what the ON option does.

@donncha, I totally respect you for developing this plugin and I think many people benefit from it greatly, but the readme file isn’t one of your greatest creations ??

What I gathered was the ON uses static pages, while HALF ON still runs PHP, but both of them take advantage of compression, if it’s available. Is this correct?

Still, why not support Bad Behavior in ON mode? Its developers seem to think it should work (or am I missing something?).

The readme.txt can’t be that bad. You understood what each mode does! Feel free to send me a rewrite of the bits of the readme.txt that aren’t 100% clear. I’ve spent more hours than I care to mention on that document but nothing is ever perfect.

BB doesn’t work in ON mode. The developer of that plugin even says so. I had to *add* extra code to switch the plugin to half-on mode. Even though I don’t even use the plugin.

Hmm. Sad conflict among two very important plugins. Based on experience with sites on non-WP platforms (Drupal) I don’t think I can afford to have bb disabled, so I’ve got to run wp-supercache in crippled mode (half on, no compression). I’m not sure I’m getting much speed-up, but at least bb is keeping the bots off the server.

Oh, and the error message language block-quoted above *IS* awful. Sorry.

How about

“You can’t run badbheavior if you also run wp-supercache in full on mode OR with compression enabled.”

OR

“To retain badbehavior functionality, you must disable wp-supercache compression AND turn off wp-supercache compression AND make sure badbehavior is in the directory …. ”

Half on is almost as fast as “ON”, you shouldn’t notice any difference.

I use the “cookies for comments” plugin that stops a huge amount of spam on my blogs.

When you activate the BB plugin it sets up the plugin for you.