Plugin Directory

Blog Control

Blog Control helps to avoid the common operations blog's owners do when adopting a new template: add scripts from mybloglog, google analytics, adsense

Download Version 1.1.2

The agressive cache

This cache is simple and very efficient. WordPress, when a blog page is called, lets someone to intercept the call and do "something" before all. No database access will be made before this call neither a connection is activated.

For who, like me, have a very slow database, servin the page at this step is very efficient. But there are some drawbacks:

  1. no plugin are initialized neither loaded
  2. no statistics can be collected
  3. no dynamic code in the page will be executed (after the first call)

So, if you have a simple blog like mine, try to see if this cache can be useful. Tha cache is expertimental, this is why no automatic installation has ben provided.

=Agressive cache installation (experimental)=

  1. if you already have the blog control plugin, deactivate and reactivate it
  2. deactivate the wp cache plugin if installed
  3. remove or rename the link "wp-content/advanced-cache.php"
  4. copy/upload the file "advanced-cache.php" in the folder "wp-content" from the blog control folder
  5. edit the "wp-config.php" and add the line define("WP_CACHE", true"); (if you use the wp cache plugin this code is already there)
  6. now the aggressive cache is active! In the blog control configuration page activate the cache option otherwise when you add a post it won't show on home page
  7. you're alone now...
  8. you're alone now...

=Remove the agressive cache=

  1. edit the "wp-config.php" and remove the line define("WP_CACHE", true");
  2. delete the "wp-content/advanced-cache.php"
  3. deactivate the cache option on the blog control configuration page
  4. delete the "wp-content/bc-cache" directory

Requires: 2.1 or higher
Compatible up to: 2.3.2
Last Updated: 2008-3-19 Downloads: 2,718

Average Rating

5 stars
4 stars
3 stars
2 stars
1 star
(1 ratings)

Compatibility

+
=
Not enough data

0 people say it works.
0 people say it's broken.

Log in to vote.