• I have a few minor issues with WP Super Cache 0.9.1 (On WordPress 2.6.5), apart from the Bad Behavior stuff covered in other threads.

    First of all, I can’t see the .htaccess rules any more, and if I make my .htaccess file writable by the web server, it isn’t updated either (Super Cache used to do this).

    Also, regardless of what time I set the expiry too, it always indicates that it does garbage collection every ten minutes (even if I set it to 1800 or under). And the time indicated doesn’t seem to correlate with any time zone I know of (it’s 30 minutes off the hour for a start).

    Also, the latest version seems to be generating a lot of cron jobs, which I assume is related to the new garbage collection code (it also seems to update the garbage collection time every time it generates a cache file).

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter ljmac

    (@ljmac)

    Alright – the time is no longer 30 minutes off the hour, but it still isn’t following my blog’s time zone, and it’s still indicating that garbage collection is done every ten minutes (even though I have it set to 1800 seconds).

    You’ll have to debug this a bit:
    1. Open wp-cache-phase2.php and add

    echo “wp_cache_gmt_offset: $wp_cache_gmt_offset”;

    after the line

    $wp_cache_gmt_offset = get_option( ‘gmt_offset’ ); // caching…

    You should also look for gmt_offset later in the file. Look for the “$log =” line and add after that line:
    $log .= “<– offset: $wp_cache_gmt_offset –>\n”

    Do you see the rewriterules when you click the “View Mod_Rewrite Rules” button in the admin page?

    Thread Starter ljmac

    (@ljmac)

    Actually Donncha, I should clarify: I no longer see the “View Mod_Rewrite Rules” button at all!

    View the source of the admin page. Can you see that text there?

    Thread Starter ljmac

    (@ljmac)

    Just tried this – it isn’t visible in the source code either!

    Please note that I am still using 2.6.5 – perhaps it only works on 2.7 now?

    Nope, it works in 2.6.5. Keep checking. It’s there somewhere!

    Thread Starter ljmac

    (@ljmac)

    I did a search for the text with my browser – it came up empty. Very strange!

    As I’m running a very old OS (Mac OS 9) my browser is old too (Mozilla 1.3.1). However, I’ve never had any problems viewing your mod_rewrite rules button in the past.

    Ljmac, first: kudos for still hanging in there with 9! I’m looking at my iMac now and think I might actually try and revive the beast… No idea WaCom still had a Mozilla 1.3.1 out there. But: it’s mighty old.

    Having said that… Have you, by any chance, changed settings of WP Super Cache to half-on? Might explain the mysterious disappearance.

    Thread Starter ljmac

    (@ljmac)

    Yes I have changed it to half on! Why would that make the mod_rewrite rules button disappear? I guess because it’s unnecessary? Please note that I would prefer to have correct the rules there, in case I switch to fully on at some time in the future.

    WaMCom actually works surprisingly well, on properly coded sites. However, there’s certainly plenty that aren’t! But between WaMCom, iCab and yes, Internet Explorer, I’ve got pretty much everything covered, except when they use the latest fancy and totally unnecessary JavaScript (as YouTube now does for its uploads unfortunately, even though the old system worked perfectly fine. Grrr…)

    The biggest problem I have is with Flash actually, which often requires version 9 (OS 9 only got up to 7). But I just can’t face all the time, effort and expense that would be involved in upgrading to OS X, especially as I still prefer the OS 9 UI. Leopard does look usable though (at last!), so I guess I’ll make the switch eventually. But I’m holding out as long as I can! And I still think the Wallstreet G3 was the greatest Mac ever (I’m typing this on one believe it or not – with a 500MHz processor upgrade!).

    Green with envy here… I still have a 9500 tower, sitting idle and waiting for when I have the time (and some money) to fill up them there array of RAM banks to push that baby to 1.5GB, install a CPU upgrade (it has an older G3 upgrade @ 400MHz) and then use it as a staging server… running Debian. I’m in love with the PowerMacs’ performance under Debian. And I still have some beloved games that run only on Classic, so… Wallstreet eh – Classic on the go, now that’s classy! 🙂

    Anyway.

    I noticed that the .htaccess thing disappeared when I switched to half-on myself (for support of intelligent mobile theming, as well as Bad Behavior).

    Thread Starter ljmac

    (@ljmac)

    I often wonder if there are any other IT pros whose main machine is more than 10 years old (she’ll be 11 in a few months!). Anyway, thanks for the info nv1962.

    Now Donncha: what about the apparently incorrect expiry times I mentioned? Are these actually incorrect, or are they only displayed incorrectly?

    There also doesn’t seem to be any good reason why the mod_rewrite rules stuff is disabled in half on mode (even if they aren’t actually necessary in this mode).

    ljmac – I don’t know why your expiry times are incorrect. Check the “wpsupercache_gc_time” in your blog’s options table and search for that string in wp-cache.php to debug it if you can.

    The rewrite stuff is hidden just because it’s not needed in half-on mode.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘A few minor issues with WP Super Cache 0.9.1’ is closed to new replies.