Forum Replies Created

Viewing 15 replies - 46 through 60 (of 90 total)
  • Will do for sure.

    I’m also having the same issue. It seems to work as intended on desktop it’s just a visual issue.

    However, there may be some functionality issues with it on mobile. I’m having issues with the language not translating and having to refresh the page multiple times to get the translation. I’m also not able to toggle between translations and once I translate one time I’m unable to translate again. This is when not in Incognito Mode.

    Thread Starter chargeup

    (@chargeup)

    Did some more digging. I setup a blank WordPress install and installed Jetpack and WooCommerce. The issue occurs in Firefox only when WooCommerce is installed with Jetpack. Hope this helps and hopefully you can find a fix soon.

    Thread Starter chargeup

    (@chargeup)

    Do you have a way for me to email or message the URL in private?

    Thread Starter chargeup

    (@chargeup)

    It seems to only be showing in Firefox. Just curious why it is reporting back as invalid domain. Is there anyway to solve this? Not sure what issues (if any) it is causing.

    I’m seeing it reproduce the error multiple times. Here is one example of the same type of error being thrown over about a week.

    [26-Nov-2022 21:00:03 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [27-Nov-2022 02:00:02 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [27-Nov-2022 05:00:03 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [27-Nov-2022 08:00:03 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [27-Nov-2022 18:00:02 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [27-Nov-2022 19:00:01 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [29-Nov-2022 02:00:01 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [29-Nov-2022 05:00:03 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [30-Nov-2022 17:00:03 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [02-Dec-2022 05:00:03 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [02-Dec-2022 13:00:03 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}
    
    [02-Dec-2022 18:00:03 UTC] Cron reschedule event error for hook: wp_privacy_delete_old_export_files, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"hourly","args":[],"interval":3600}

    @domainsupport judging from other comments it doesn’t seem like anyone if actual having problems with their sites. Health check is also saying cron are running properly for most people.

    It might be a bug but at least I think we are close now. I think we should submit the bug with the information from your last comment.

    2 scenarios.

    1) They find an actual bug that may be happening when trying to save to the database.
    2) They get rid of a very bad error reporting system that constantly throws phantom errors. That’s gonna fill up these error logs pretty bad over time.

    I’d put a link to the support thread so they can read through all the comments.

    @domainsupport The following code looks to have been added to wp-cron.php in the 6.1 update. It’s line 126-177. I’m not sure what is causing the issue outside of this, but this seems to be the code throwing all the errors.

    ———————-

    $result = wp_reschedule_event( $timestamp, $schedule, $hook, $v['args'], true );	
    				if ( is_wp_error( $result ) ) {	
    					error_log(	
    						sprintf(	
    							/* translators: 1: Hook name, 2: Error code, 3: Error message, 4: Event data. */	
    							__( 'Cron reschedule event error for hook: %1$s, Error code: %2$s, Error message: %3$s, Data: %4$s' ),	
    							$hook,	
    							$result->get_error_code(),	
    							$result->get_error_message(),	
    							wp_json_encode( $v )	
    						)	
    					);	
    					/**	
    					 * Fires when an error happens rescheduling a cron event.	
    					 *	
    					 * @since 6.1.0	
    					 *	
    					 * @param WP_Error $result The WP_Error object.	
    					 * @param string   $hook   Action hook to execute when the event is run.	
    					 * @param array    $v      Event data.	
    					 */	
    					do_action( 'cron_reschedule_event_error', $result, $hook, $v );	
    				}	
    			}	
    			$result = wp_unschedule_event( $timestamp, $hook, $v['args'], true );	
    			if ( is_wp_error( $result ) ) {	
    				error_log(	
    					sprintf(	
    						/* translators: 1: Hook name, 2: Error code, 3: Error message, 4: Event data. */	
    						__( 'Cron unschedule event error for hook: %1$s, Error code: %2$s, Error message: %3$s, Data: %4$s' ),	
    						$hook,	
    						$result->get_error_code(),	
    						$result->get_error_message(),	
    						wp_json_encode( $v )	
    					)	
    				);	
    				/**	
    				 * Fires when an error happens unscheduling a cron event.	
    				 *	
    				 * @since 6.1.0	
    				 *	
    				 * @param WP_Error $result The WP_Error object.	
    				 * @param string   $hook   Action hook to execute when the event is run.	
    				 * @param array    $v      Event data.	
    				 */	
    				do_action( 'cron_unschedule_event_error', $result, $hook, $v );	
    			}

    @domainsupport Thanks for much for taking control on this. Much appreciation.

    @domainsupport I’d say it’s totally your call. This is a tough one because it’s not as simple as “activate/deactivate this plugin. trigger this event, etc.” There is clearly something going on somewhere in the code that is causing this issue and since there are many people with the same issue it’s doesn’t seem to be intermittent.

    Thread Starter chargeup

    (@chargeup)

    No worries on the delay. Thanks for the link to Stripe.

    However, how are you going to handle the error within PayPal Standard? My particular site is a pre-WooCommerce 5.5 site so it is built into WooCommerce. This is before you you hid it post-5.5 and recommended the PayPal plugin instead.

    Thread Starter chargeup

    (@chargeup)

    Got it. Thanks for the clarification.

    Thread Starter chargeup

    (@chargeup)

    My apologies but want to make sure I’m following. Previously you said the following:

    “there is an unfortunate bug in it that caused the set value to be ignored that’s been there for years but never been hit due to the version number.”

    This seems to have started on my sites at least after updating to the latest version of WordPress.

    Is it dependent on version number?

    • This reply was modified 3 years, 6 months ago by Marius L. J..
    • This reply was modified 3 years, 6 months ago by chargeup.
    Thread Starter chargeup

    (@chargeup)

    Thanks for the info. Just for reference. Is this affecting all sites with this plugin or is it only affecting sites that have been updated to WordPress 6.1 or a certain version of MonsterInsights?

    Thread Starter chargeup

    (@chargeup)

    Thanks. I just emailed all of the information to you.

Viewing 15 replies - 46 through 60 (of 90 total)