Fatal error: Uncaught Error: Call to a member function getTimestamp() on bool in

  • Resolved enmuci

    (@enmuci)


    1 year, 6 months ago

    Fatal error: Uncaught Error: Call to a member function getTimestamp() on bool in /wp-includes/functions.php:202 Stack trace: #0 /wp-content/plugins/wp-super-cache/partials/advanced.php(201): date_i18n() #1 /wp-content/plugins/wp-super-cache/wp-cache.php(3937): include(‘/data/wwwroot/d…’) #2 /wp-content/plugins/wp-super-cache/wp-cache.php(1245): wpsc_render_partial() #3 /wp-includes/class-wp-hook.php(308): wp_cache_manager() #4 /wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #5 /wp-includes/plugin.php(517): WP_Hook->do_action() #6 /wp-admin/admin.php(259): do_action() #7 /wp-admin/options-general.php(10): require_once(‘/data/wwwroot/d…’) #8 {main} thrown in /wp-includes/functions.php on line 202

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Bruce (a11n)

    (@bruceallen)

    Happiness Engineer

    1 year, 6 months ago

    Hi @enmuci

    Could you please post your site URL here so that we can have a look?

    If you want it to remain private, you can also contact us via this contact form. If you choose to reach out directly, please include a link to this thread.

    Can you also make sure you have the latest versions of WordPress and WP Super Cache installed on your site?

    It could also have something to do with your timezone setting; you may want to check that in the WordPress General Settings.

    Thread Starter enmuci

    (@enmuci)

    1 year, 6 months ago

    @bruceallen

    I tried to change the time zone, but it still doesn’t work, including restarting the server, uninstalling and reinstalling the plug-in. The plug-in is the latest. Before this error occurred, I made a wrong operation and set the timer time in the garbage collection period to be too long. I found the link to restore the default settings through other websites, and the default settings were restored successfully, but the problem still exists. In addition, it should be noted that the website cache is normal, that is, all the settings in the background from the expiration time and the garbage collector down to buI will now change to other caches.

    Plugin Contributor Mark (a11n)

    (@thingalon)

    1 year, 6 months ago

    Hi @enmuci,

    Thanks for writing in, and for sending in a full stack trace. That helped me understand where the problem is pretty quickly.

    Based on the stack trace, I think the issue is to do with the date of your next scheduled wp_cache_gc task – that is, your next “Garbage collection” run.

    I suspect the date scheduled for that in your database is somehow corrupt (or so far into the future that WordPress’ internationalization-friendly date formatter can’t cope with it).

    To solve the issue, can I please ask you to install a plugin which lets you delete scheduled events, such as Advanced Cron Manager and use it to delete the next scheduled wp_cache_gc task. Hopefully by doing that, we can clear out the issue and get things moving again.

    Thread Starter enmuci

    (@enmuci)

    1 year, 6 months ago

    @thingalon

    Failed to delete the event, prompting that the event timestamp must be a valid UNIX timestamp.

    Thread Starter enmuci

    (@enmuci)

    1 year, 6 months ago

    @thingalon @bruceallen

    Thank you very much for your help. Now the problem has been solved. It’s about planning events

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal error: Uncaught Error: Call to a member function getTimestamp() on bool in’ is closed to new replies.