Kim Hornung
Forum Replies Created
-
We’re still getting the “Invalid JSON” error emails, despite having cleared our caches and resetting the Scheduler on the debug page.
Our manual scans work.
OK, I’ll reach out to your premium support.
But thank you for confirming the license numbers.
Hi again
I have now looked a bit deeper into when the problem happens, and I can see that it only happens when the “CSS & JS Toolbox PLUS” plugin is also installed.
We have v11.5 of the PLUS plugin. Is that the latest version? I don’t see any available plugin updates for the PLUS plugin, but I can see that the base plugin is on v12.0.1
With both plugins installed, it seems to happen on most page requests, both on the front end and the backend.
The error is related to the framework/extensions/extensions.class.php in line 330 where it calls get_plugin_data() which in turn calls _get_plugin_data_markup_translate() which in turn calls translate(‘CSS & JavaScript Toolbox’, ‘css-javascript-toolbox’.
I hope this helps.
Forum: Plugins
In reply to: [WP Super Cache] Edge case can lead to blank page being servedThank you the information about NFS and the suggestion to use something like Batcache.
And I’m very happy to hear that you’ve prepared a patch, including several other checks than the one I had suggest. Sounds great!
Thanks! I can confirm that I no longer see the problem after upgrading to the newest version.
/Kim
Hi Adam
Thank you for getting back to me, and for so quickly resolving the issue.
I have now upgraded to the newest version and I can confirm that I no longer see the issue.
Thanks again
KimExcellent! Will do so.
Thank you for the quick reply.Forum: Plugins
In reply to: [NS Cloner - Site Copier] Cron rescheduling errorThank you for your patience. I’m able to reproduce it on two different installations (one a local installation, the other our production site).
The notice also appears with no other plugins active.
I’m not sure why you are not able to reproduce it. Maybe because the wp-cron.php only causes the warning if there are active cron jobs ready for execution and if the ns_cloner_cron needs to be rescheduled.
It’s correct that the cron is instantiated after plugins are active and enabled. But in the the __construct() method of the NS_Cloner class you have the following line 178:
$should_load = is_admin() || ( wp_doing_ajax() && is_user_logged_in() ) || ( defined( 'WP_CLI' ) && WP_CLI ) || ns_is_signup_allowed();When wp-cron.php is being run in my environment, none of these conditions are true which leads to the warning.
To fix this, the line could be changed to also check for wp_doing_cron():
$should_load = is_admin() || ( wp_doing_ajax() && is_user_logged_in() ) || wp_doing_cron() || ( defined( 'WP_CLI' ) && WP_CLI ) || ns_is_signup_allowed();It’s fair enough if you don’t want to make this change unless other people also report the problem 🙂
But I hope you find a way to reproduce it.Forum: Plugins
In reply to: [NS Cloner - Site Copier] Cron rescheduling errorThe problem is not related to PHP version (I’m on PHP 8.2).
The problem happens if using the built-in WP cron. You can manually trigger this by accessing this URL:
http://<hostname>/wp-cron.php?doing_wp_cronThen you should (hopefully) see the warning in the debug.log file. But let me know if you don’t, then I’ll be happy to see if I can provide additional troubleshooting steps.
Forum: Plugins
In reply to: [NS Cloner - Site Copier] Cron rescheduling errorSounds great!
But according to my testing, this unfortunately doesn’t fix the issue. I still see the warnings in my debug.log file after installing v4.4.7.1 when the background cron jobs are running.
It seems that the an extra check for wp_doing_cron() should be added to the $should_load variable in the __construct() method of the NS_Cloner class.
If I manually add such a check, then I no longer see the warnings.
Forum: Plugins
In reply to: [NS Cloner - Site Copier] Cron rescheduling errorI’m also seeing this warning in the debug.log file after upgrading to the most recent NS Cloner version and WP 6.6.1.
It seems that the NS Cloner’s register_interval() hook is not active when wp-cron.php calls wp_reschedule_event()
Forum: Plugins
In reply to: [CSS & JavaScript Toolbox] Error on Update to PHP 8.1Any updates on this one? I’m running on PHP 8.2 also seeing these warnings in the my /wp-content/debug.log file.
To reproduce the issue, simply add the following lines to the wp-config.php file:
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);Then visit any frontend or backend page, and you’ll see the warnings in the log file.
Forum: Plugins
In reply to: [LiteSpeed Cache] Litespeed metabox appear on ACF field group edit pagesFantastic – I’m happy to hear!
Thank you for fixing this so quickly.
Thanks!
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] inpsyde_phone-home_checkinI have also encountered this problem, and I’ve found a workaround for it.
The problem is that the plugin’s ‘cron_schedules’ hook is initialized in the Inpsyde_PhoneHome_CronController::schedule() function. But this code is not reached when the wp-cron.php file executes the cron job.
Due to this, the wp_reschedule_event() function will try to reschedule it, but because the ‘twice_weekly’ schedule isn’t initialized, it will fall back to rescheduling the event to be executed initially.
On my solution, this gave a 2-300 ms overhead on every single request.
The fix would be to ensure the ‘cron_schedules’ hook is also called for cron requests.
My workaround was to add the following lines to my functions.php file:
// // WORKAROUND: The BackWpUp plugin doesn't reschedule events correctly // This hook fixes a problem where each request would call the WP cron and perform a remote request // The problem happened because the plugin doesn't initialize its cron schedule on the wp-cron.php page // if ( class_exists('Inpsyde_PhoneHome_CronController') ) { function fix_backwpup_cron_schedule( $schedules ) { is_array( $schedules ) or $schedules = array(); $label = __( 'Every %d days', 'inpsyde-phone-home' ); $interval = apply_filters( 'inpsyde-phone-home-cron-interval', Inpsyde_PhoneHome_CronController::RECURRENCE_INTERVAL ); is_int( $interval ) or $interval = Inpsyde_PhoneHome_CronController::RECURRENCE_INTERVAL; $schedules[ Inpsyde_PhoneHome_CronController::RECURRENCE_KEY ] = array( 'interval' => $interval, 'display' => sprintf( $label, ceil( $interval / DAY_IN_SECONDS ) ) ); return $schedules; } add_filter( 'cron_schedules', 'fix_backwpup_cron_schedule' ); }