• it’s a great plugin, but here’s something i can’t quite figure out, using version 1.0:

    go to the “Advanced” tab, scroll down to “Expiry Time & Garbage Collection” set the scheduler to Clock: 01:30, Interval: daily. click on “Change Expiration”, and when the page comes back:

    1. i see

    Current server time is: 2012-02-25 22:59:51
    Next scheduled garbage collection will be at (YY-MM-DD H:M:S): 2012-02-25 01:30:00

    i think there’s an off-by-one-day error there.

    2. “Interval” says “weekly” not “daily”.

    thanks!

    /mtr

    http://wordpress.org/extend/plugins/wp-super-cache/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thanks for the bug reports. Can you try the dev version? I fixed a number of bugs in that code. I suspect some other plugin has changed the interval choices as daily is a part of standard WordPress. Grep/Look through your plugins source code for the word “weekly”.

    http://downloads.wordpress.org/plugin/wp-super-cache.zip

    Thread Starter mrose17

    (@mrose17)

    hi. thanks for the note. here’s what i’ve found:

    1. the development version is much more helpful because it says “UTC” more often.

    2. the Interval is still showing “Once Weekly”. wp_get_schedules() is returning the usual choices. the reason why “Once Weekly” is selected is because none of the choices are selected, viz.,

    <select id='cache_scheduled_select' name='cache_schedule_interval' size=1>
    <option name='weekly'  /> weekly</option>
    <option name='bimonthly'  /> bimonthly</option>
    <option name='hourly'  /> hourly</option>
    <option name='twicedaily'  /> twicedaily</option>
    <option name='daily'  /> daily</option>
    </select>

    as to why that is, i couldn’t tell you.

    3. i’m going to run with email notifications enabled for a while to see when the cron job fires.

    4. please consider bumping the version number in the development version, so there’s a visual cue that this isn’t the current release.

    best,

    /mtr

    Can you select “daily” instead of weekly?

    Unfortunately I can’t bump the version number because it would fool WordPress.org into thinking it’s the new release. I’d like to make it more obvious that it was the dev version though. Should be easy enough with a flag that I unset when a new release is made.

    Thread Starter mrose17

    (@mrose17)

    it’s easy to select any of the options, the problem is that when the page comes back after clicking “Change Expiration” none of them are selected, leading to first one, ‘weekly’ being displayed.

    it’s quite perplexing.

    Thread Starter mrose17

    (@mrose17)

    donncha – just a follow-up – using the development version, the daily cron seems to clean up the cache. since i’m running this ‘daily’, i’ll report back in a few days to confirm that…

    Thread Starter mrose17

    (@mrose17)

    here is the problem – the <option/> should use value= rather than name=

    --- _wp-cache.php	2012-02-23 00:05:32.000000000 -0600
    +++ wp-cache.php	2012-03-01 00:55:30.000000000 -0600
    @@ -1544,7 +1544,7 @@
     	$schedules = wp_get_schedules();
     	echo "<tr><td><br /></td><td><label for='cache_scheduled_select'>" . __( 'Interval:', 'wp-super-cache' ) . "</label></td><td><select id='cache_scheduled_select' name='cache_schedule_interval' size=1>";
     	foreach( $schedules as $desc => $details ) {
    -		echo "<option name='$desc' " . selected( $desc, $cache_schedule_interval, false ) . " /> {$details[ 'display' ]}</option>";
    +		echo "<option value='$desc' " . selected( $desc, $cache_schedule_interval, false ) . " /> {$details[ 'display' ]}</option>";
     	}
     	echo "</select></td></tr>";
     	echo '</table></td></tr>';

    mrose17 – thanks for finding that! What a stupid mistake to make! Argh!

    Thread Starter mrose17

    (@mrose17)

    and it only took me 30m staring at the ‘inspect element’ screen to notice it. (-;

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘[Plugin: WP Super Cache] Expiry Time & Garbage Collection’ is closed to new replies.