Deactivating the plugin

  • Resolved thewebmonk

    (@thewebmonk)


    5 months, 3 weeks ago

    Hello,

    I use WP-Optimize (free version) and Updraft Plus (paid).

    I have been having many problems due to 409 conflicts and I am trying to understand which plugin is causing it.

    I would like to ask you:
    1) If I deactivate the WP-Optimize plugin, could my website break/have errors? Do I have to revert any changes I made with your plugin in order to avoid problems?
    2) Just to know, (and I don’t know if this question makes sense) – does WP-Optimize have an impact on the CRON? Because one problem I have very frequently on my error log is the following and I am trying to understand if a plugin could cause it:
    Cron reschedule event error for hook: action_scheduler_run_queue, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”every_minute”,”args”:[“WP Cron”],”interval”:60}

    Thank you very much

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)

  • Hello,

    Let’s go through your concerns:

    1. Deactivating WP-Optimize: Deactivating WP-Optimize should not break your website or cause errors, but you may notice some performance impacts:
      • Caching: If you’ve enabled caching through WP-Optimize, deactivating the plugin will stop it, which could lead to slower page loads until the cache is rebuilt.
      • Database Cleanup: Any database cleanup or optimizations made will remain intact, so no need to revert any changes. Deactivation will simply stop any automatic cleanups you’ve scheduled.
      • Image Compression: Image compressions are permanent, so those changes won’t be lost.
      • Minification: If you’ve enabled CSS/JS minification, deactivating WP-Optimize will stop this, which could result in minor layout changes. You can easily reactivate the plugin if needed to restore these optimizations.
      Overall, you can safely deactivate WP-Optimize for troubleshooting without needing to revert anything, though you might experience some temporary performance differences.
    2. Impact on CRON Jobs: WP-Optimize generally doesn’t interfere with CRON jobs, but certain database cleanups could potentially affect scheduled events if there’s a conflict with another plugin. The error you mentioned (action_scheduler_run_queue) seems to be related to a plugin like WooCommerce that uses the Action Scheduler library. Deactivating WP-Optimize temporarily might help you determine if it’s contributing to the issue.
      • If the error persists after deactivation, check other plugins that manage scheduled tasks (like WooCommerce or UpdraftPlus) to pinpoint the source. You can also use a plugin like WP Crontrol to manage and debug CRON events.

    Feel free to reach out if you need further assistance. Good luck with troubleshooting!

    Thread Starter thewebmonk

    (@thewebmonk)

    Hi, there.

    I have been checking my Error Log and I see there are many lines related to WP-Optimize, can you please let me know the problem and how to solve it? Thank you!

    [26-Sep-2024 10:38:39 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [26-Sep-2024 16:39:05 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [26-Sep-2024 17:56:10 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [26-Sep-2024 20:48:29 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [27-Sep-2024 04:10:02 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [27-Sep-2024 06:11:33 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [27-Sep-2024 15:45:16 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [27-Sep-2024 16:05:44 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [27-Sep-2024 19:03:31 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [28-Sep-2024 09:45:32 UTC] PHP Warning: rmdir(/public_html/wp-content/cache/wpo-cache/enkismusicrecords.com/shop): Directory not empty in /public_html/wp-content/plugins/wp-optimize/cache/class-wpo-page-cache.php on line 520
    [28-Sep-2024 10:34:57 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [28-Sep-2024 11:16:33 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [29-Sep-2024 10:11:44 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [30-Sep-2024 16:22:24 UTC] Cron unschedule event error for hook: icwp-wpsf-adhoc_cron_crowdsec_signals, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":false,"args":[]}
    [30-Sep-2024 22:47:00 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [01-Oct-2024 09:11:50 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [02-Oct-2024 06:22:37 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [02-Oct-2024 06:22:38 UTC] Cron unschedule event error for hook: icwp-wpsf-adhoc_cron_crowdsec_signals, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":false,"args":[]}
    [02-Oct-2024 09:21:29 UTC] WP_Optimize_Minify_Cache_Functions::cache_path(): The folder "/public_html/wp-content/cache/wpo-minify/1727860869/header" could not be created.
    [02-Oct-2024 09:22:22 UTC] Cron unschedule event error for hook: icwp-wpsf-ptg_build_snapshots, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":false,"args":[]}
    [02-Oct-2024 10:47:33 UTC] PHP Warning: Invalid argument supplied for foreach() in /public_html/wp-content/plugins/woocommerce-multilingual/classes/Rest/Wrapper/Orders/Languages.php on line 46
    [02-Oct-2024 22:43:19 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [03-Oct-2024 08:41:55 UTC] Cron reschedule event error for hook: action_scheduler_run_queue, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"every_minute","args":["WP Cron"],"interval":60}
    [03-Oct-2024 12:50:17 UTC] Cron reschedule event error for hook: action_scheduler_run_queue, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"every_minute","args":["WP Cron"],"interval":60}
    [08-Oct-2024 11:15:18 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [08-Oct-2024 19:04:04 UTC] Cron reschedule event error for hook: action_scheduler_run_queue, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"every_minute","args":["WP Cron"],"interval":60}
    [08-Oct-2024 19:45:22 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [09-Oct-2024 06:57:42 UTC] cURL error 28: Connection timed out after 5001 milliseconds
    [09-Oct-2024 13:42:53 UTC] PHP Warning: Cannot modify header information - headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692
    [09-Oct-2024 14:06:49 UTC] Cron reschedule event error for hook: action_scheduler_run_queue, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {"schedule":"every_minute","args":["WP Cron"],"interval":60}
    Thread Starter thewebmonk

    (@thewebmonk)

    Hi,

    some more error logs from today, if you can please help me understand how to fix the ones that mention wp-optimize.

    Will upgrading to premium fix these problems?

    Thank you

    [10-Oct-2024 02:57:45 UTC] Cron unschedule event error for hook: icwp-wpsf-adhoc_cron_crowdsec_signals, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

    [10-Oct-2024 03:57:25 UTC] PHP Warning:  Cannot modify header information – headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692

    [10-Oct-2024 05:20:58 UTC] PHP Warning:  Cannot modify header information – headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692

    [10-Oct-2024 15:42:55 UTC] PHP Warning:  Cannot modify header information – headers already sent in /public_html/wp-content/db-error.php on line 2

    [10-Oct-2024 15:42:55 UTC] PHP Warning:  Cannot modify header information – headers already sent in /public_html/wp-content/db-error.php on line 3

    [10-Oct-2024 15:42:55 UTC] PHP Warning:  Cannot modify header information – headers already sent in /public_html/wp-content/db-error.php on line 4

    [10-Oct-2024 15:53:28 UTC] Cron unschedule event error for hook: icwp-wpsf-adhoc_cron_crowdsec_signals, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

    [10-Oct-2024 16:34:15 UTC] PHP Warning:  Cannot modify header information – headers already sent in /public_html/wp-content/plugins/wp-optimize/cache/file-based-page-cache-functions.php on line 692

    Plugin Support vupdraft

    (@vupdraft)

    ?Cron unschedule event error – a common cause that the plugin trying to schedule an event that matches one that’s already due within one minute. This causes WordPress to identify the event as duplicate and refuse to add it. Please try to increase the time to repeat the cron event for one of the hooks and try again (you should be able to do this using the free. pluginWP Crontrol)

    The header already sent – This is most likely the result of the first error that is being sent to the output before WordPress could generate HTTP headers. In fact, if you output anything (with?print,?echo?etc.) before sending HTTP headers, you’ll get this?headers already sent?error.

    This is the code that is mentioned;

    header(‘Cache-Control: no-cache’); // Check back later

    I think the issue might be that WPO is trying to schedule it’s hook. It’s clashing with this hook: ?icwp-wpsf-adhoc_cron_crowdsec_signals which means output is being sent before the headers and you are getting the “headers already sent” error

    Changing the schedule of the clashing hook or deactivating the clashing plugin (it’s the Crowdsec one) should get rid of both issues.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.