"woof_turbo_do_recreate_file" cron job is missing
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Hello,
I have a similar problem like explained here: https://pluginus.net/support/topic/daily-cron-job-for-turbo-mode-not-working/
Turbo mode is enabled, set to daily cron, but"woof_turbo_do_recreate_file" cron job is not added. I tried manually adding it, but it could not find the corresponding callback (do_recreate_file($id, $ids, $is_end))
The file generates ok if clicked manually. By setting update to automatic, the file generates partially.
I am using version 3.3.8
Hello Sandor
I've identified the issue. The problem occurs because:
1. File clearing before write: The turbo file is truncated (cleared) before new data is written. If PHP execution time limit is exceeded during the write operation, the file remains empty. But this is ok, problem is another thing
2. WordPress Cron limitations: WP Cron isn't reliable for long-running tasks and may not execute if no one visits the site.
Recommended solution - Use server-side cron:
Step 1: Disable WordPress cron in `wp-config.php`:
define('DISABLE_WP_CRON', true);
Step 2: Add to server crontab (runs daily at 3 AM):
0 3 * * * php /path/to/your/site/wp-cron.php >/dev/null 2>&1
Or using wget:
0 3 * * * wget -q -O - https://yoursite.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1
Step 3: Increase PHP execution time in turbo mode callback
Alternative - Increase PHP limits:
Add to wp-config.php:
@ini_set('max_execution_time', 300); // 5 minutes
@ini_set('memory_limit', '512M');
This ensures cron has enough time to complete the turbo file generation. Please try server-side cron first - it's the most reliable solution for production sites.