Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • @johnbillion I trying figured out what is happen and make some test.
    and find some more weird:
    Using the wp-cli cron function at shell.
    Executing ‘wp cron event list’, both servers show the list with the same list showing in the plugin events list.
    Executing a re-schedule of an event:
    The server that works fine, do it fine.
    The server with the problem: “Error: Event not scheduled.”

    There is some reset of the WP-CRON?

    @johnbillion – About the UTC
    I compare the 2 servers running (one work and other don’t) the PHP.ini
    Default time zone UTC – Working
    Default time zone America/Sao_Paulo – Not Working

    I put a date_default_timezone_set(‘UTC’); at Wp-config.php
    and the problem still happening

    I’d the downgrade to WordPress 5.4.1 to fix the Site Health problem.
    The site health there is no problem with the UTC.

    The site health returns no problem at all…
    But I don’t think it’s working properly because the Message: “Results are still loading…” it still there.
    then check the console there is some Javascript problem.

    Uncaught ReferenceError: commonL10n is not defined
        at HTMLDocument.<anonymous> (common.min.js:2)
        at HTMLDocument.dispatch (jquery.js:3)
        at HTMLDocument.r.handle (jquery.js:3)
        at Object.trigger (jquery.js:3)
        at HTMLDocument.<anonymous> (jquery.js:3)
        at Function.each (jquery.js:2)
        at n.fn.init.each (jquery.js:2)
        at n.fn.init.trigger (jquery.js:3)
        at Q (common.min.js:2)
        at HTMLDocument.<anonymous> (common.min.js:2)

    And now I find some Cron error in DEbug too…

    
    [27-Aug-2020 17:11:07 UTC] PHP Fatal error:  Uncaught TypeError: Argument 4 passed to Crontrol\Event\add() must be of the type array, bool given, called in /home/html/xxxxxxx/public_html/wp-content/plugins/wp-crontrol/wp-crontrol.php on line 160 and defined in /home/html/xxxxxxx/public_html/wp-content/plugins/wp-crontrol/src/event.php:87
    Stack trace:
    #0 /home/html/xxxxxxx/public_html/wp-content/plugins/wp-crontrol/wp-crontrol.php(160): Crontrol\Event\add('2020-08-27 17:4...', '_oneoff', 'wpseo_send_trac...', true)
    #1 /home/html/xxxxxxx/public_html/wp-includes/class-wp-hook.php(287): Crontrol\action_handle_posts('')
    #2 /home/html/xxxxxxx/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
    #3 /home/html/xxxxxxx/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #4 /home/html/xxxxxxx/public_html/wp-settings.php(546): do_action('init')
    #5 /home/html/xxxxxxx/public_html/wp-config.php(119): require_once('/home/html/xxxx...')
    #6 /home/html/xxxxxxx/public_html/wp-load.php(37): require_once('/home/html/alt in /home/html/xxxxxxx/public_html/wp-content/plugins/wp-crontrol/src/event.php on line 87
    [27-Aug-2020 17:11:21 UTC] PHP Fatal error:  Uncaught TypeError: Argument 4 passed to Crontrol\Event\add() must be of the type array, bool given, called in /home/html/xxxxxxx/public_html/wp-content/plugins/wp-crontrol/wp-crontrol.php on line 160 and defined in /home/html/xxxxxxx/public_html/wp-content/plugins/wp-crontrol/src/event.php:87
    Stack trace:
    #0 /home/html/xxxxxxx/public_html/wp-content/plugins/wp-crontrol/wp-crontrol.php(160): Crontrol\Event\add('2020-08-27 17:4...', '_oneoff', 'wpseo_send_trac...', true)
    #1 /home/html/xxxxxxx/public_html/wp-includes/class-wp-hook.php(287): Crontrol\action_handle_posts('')
    #2 /home/html/xxxxxxx/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
    #3 /home/html/xxxxxxx/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #4 /home/html/xxxxxxx/public_html/wp-settings.php(546): do_action('init')
    #5 /home/html/xxxxxxx/public_html/wp-config.php(119): require_once('/home/html/xxxx...')
    #6 /home/html/xxxxxxx/public_html/wp-load.php(37): require_once('/home/html/alt in /home/html/xxxxxxx/public_html/wp-content/plugins/wp-crontrol/src/event.php on line 87

    And the information about Default Time, all other entries are in my locale, sample :

    [27-Aug-2020 10:43:13 America/Sao_Paulo]

    • This reply was modified 4 years, 3 months ago by fnorte. Reason: missing information

    I’m have the same issue here.
    And the execution when happens in the normal time, the next run is allways put in one hour before the run.
    I have a copy of the WordPress with the same files and database in a homologation server, and that problem is not happening.
    there is no problem reported in the debug.log
    I’m doing a migration to a new server and WordPress version, since the new version upgraded this problem starts.
    Old version :PHP 5.4 and WP 4.8.1 and Now: PHP 7.4 and WP 5.5

    I have the same issue here.

    error.js:195 amp-ad is already registered. The script tag for amp-ad is likely included twice in the page.

    My plugins list:

    Accelerated Mobile Pages
    Vers?o 0.9.98.20 | by Ahmed Kaludi, installed Mohammed Kaludi |

    Ads for WP – Advanced Ads & Adsense Solution for WP & AMP
    Vers?o 1.9.15.1 | by Magazine3

    Bouplay Theme Core
    Vers?o 1.0 | by An-Themes

    Dave’s WordPress Live Search
    Vers?o 4.8.1 | by Dave Ross

    Disqus for WordPress
    Vers?o 3.0.17 | by Disqus

    Importador do WordPress
    Vers?o 0.6.4 | by wordpressdotorg

    iThemes Security
    Vers?o 7.5.0 | by iThemes

    Jetpack por WordPress.com
    Vers?o 7.9.1 | by Automattic

    Meta Box
    Vers?o 5.2.3 | by MetaBox.io

    Shortcodes Plugin
    Vers?o 1.2 | by An-Themes

    Thumbs Rating
    Vers?o 10.0

    WP Security Audit Log
    Vers?o 3.5.2.1 | by WP White Security

    WP Super Cache
    Vers?o 1.7.0 | by Automattic

    WP-PageNavi
    Vers?o 2.93.1 | by Lester ‘GaMerZ’ Chan

    WP-Sweep
    Vers?o 1.1.1 | by Lester ‘GaMerZ’ Chan

    XML Sitemap & Google News
    Vers?o 5.2.7 | by RavanH

    Yoast SEO
    Vers?o 12.6.2 | by Equipe da Yoast

    Thread Starter fnorte

    (@fnorte)

    suspecting the problem is in the database, I’d installed a local version to COMPARE the databases.

    The problem is solved.

    The error was in the wp_categories table, for some reason (maybe a backup recovery) the field name was changed from cat_ID to cat_id. This case difference was generating the error.

    Thanks to MichaelH to trying help, and I hope to the help others who might be get the same problem.

    Take care with database backups. ??

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