Haoxian

@kent Brockman – If you could receive the Start/Completed messages, the WPSC must be working properly.

@donncha – I had a test on this just now. It seems to be the same as I described at the very beginning. It’s so weird! Here is the log message: https://cnzhx.net/wp-content/cache/e6d5643c7c7c21d2ccca42e310561fcd.txt

Hi, donncha

It seems that I run into the same situation with Kent Brockman.

After upgrading to the newest alpha version of WP 3.1, the current stable version of WPSC doesn’t preload correctly as you described upper.

Then I follow your advice to Kent Brockman, upgrade WPSC to the development version. It still doesn’t preload correctly and the plugin doesn’t send me the notification message of beginning to preload.

I haven’t done a debug test.

As I pointed out that after I moving to another host, the problem had never showed up again.

I also write about this in Simple Chinese (because I am not sure whether I can write it in English).

If you are interesting, here is the post. If you could not read Simple Chinese, you could use Google translate.

By the way, Kent Brockman, are you using a free hosting plan like xtreemhost.com?

OK, I found the reason.

That’s because the webhosting server restricted the cron job feature, and had nothing to do with the WP or this wonderful plugin of WPSC.

You’re so fast!
Thank you! I see now.

I don’t know how to fix it, so, just let it be.

Maybe, it’s a compatible issue between wp 3.1 alpha and this new version wpsc.

Thank you, donncha! You’re so appreciate!

Something new:

The “Preload Cache Now” button DO clear the old supercache files, but don’t generate new files.

I also get a message from debug like that:
supercache dir: xxx/htdocs/wp-content/cache/supercache/cnzhx.net/wp-admin/options-general.php/

Does this means that WPSC is attempting to cache a wp-admin webpage?

Could I downgrade WPSC to version 0.9.9.3 ? This problem occurred only after the upgrading. And I’m using WP 3.1 alpha.

Thank you, donncha!

But I don’t know how to check the access_logs for hits on wp_cron.php.

Could you give a hint?

I have the same problem. It’s a theme side problem, I guess.