 Menno van den Heuvel
|
Hi Shekhar,
The page hidden link had switched back to Dutch Wednesday.
I reverted it back to a French revision so that the page would be correct again.
|
 Shekhar Bhandari
WPML Supporter since 03/2015
Languages:
English (English )
Timezone:
Asia/Kathmandu (GMT+05:45)
|
Hello,
I am currently discussing the issue with our second-tier support team and will provide an update as soon as I receive their feedback.
I look forward to your response.
Thank you.
|
 Shekhar Bhandari
WPML Supporter since 03/2015
Languages:
English (English )
Timezone:
Asia/Kathmandu (GMT+05:45)
|
Hello,
Thank you for your patience while we continue investigating this issue.
Based on feedback from our second-tier team, the current stack trace only captures what happens during shutdown, so it doesn’t show which cron job was running beforehand. To help identify that, they’ve suggested adding some temporary logging to trace cron activity.
Could you please try adding the following snippet to your site?
add_action('all', function($hook) {
if (defined('DOING_CRON') && DOING_CRON) {
error_log("---cron-trace--- hook: $hook");
}
});
This will log all hooks triggered during cron jobs into your debug.log file.
After adding it, please reproduce the issue and then check the log. You can search for your existing message:
`--- Revision created during cron ---`
The hook that appears immediately before that entry should indicate which cron event is running.
We understand this may generate quite a few log entries, but searching for that specific line should make it easier to locate the relevant section.
Once you have the results, please share them with us and we’ll continue the investigation with our second-tier team.
Thanks
|
 Menno van den Heuvel
|
Hi Shekhar,
I added that line of code. Now twiddle our thumbs until it breaks again.
Thanks,
Menno
|
 Shekhar Bhandari
WPML Supporter since 03/2015
Languages:
English (English )
Timezone:
Asia/Kathmandu (GMT+05:45)
|
Sure, will wait for your feedback.
|
 Menno van den Heuvel
|
Still nothing so far.
Either the problem somehow is fixed, or it depends on the moon phase or something.
I also cannot keep the logging active indefinitely; it adds up to around 200 MB per day.
I propose we close this ticket for now. If the problem returns, I'll reactivate the logging, and we'll have some more info to go off of.
|