unserialize(): Error at offset

  • Resolved treibstoff

    (@treibstoff)


    1 year, 1 month ago

    Getting this PHP Error only via Query Monitor & only if I’m on the dashboard (doesn’t show up in the debug.log or if I’m on some other backend-section….):

    unserialize(): Error at offset 2388 of 2768 bytes
    wp-includes/functions.php:650
    unserialize()
    wp-includes/functions.php:650
    maybe_unserialize()
    wp-includes/option.php:253
    get_option()
    wp-includes/option.php:1501
    get_network_option()
    wp-includes/option.php:1366
    get_site_option()
    wp-includes/option.php:2006
    get_site_transient()
    wp-admin/includes/class-wp-community-events.php:361
    WP_Community_Events->get_cached_events()
    wp-includes/script-loader.php:1978
    wp_localize_community_events()
    wp-includes/class-wp-hook.php:310
    do_action('admin_print_scripts-index.php')
    wp-admin/admin-header.php:139

    What can I do???

    • This topic was modified 1 year, 1 month ago by treibstoff.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks for the message. Query Monitor just reports errors that PHP produces, and this error isn’t being caused by Query Monitor, so your best bet is to clear the transients on your site and see if the error persists.

    Good luck!

    Thread Starter treibstoff

    (@treibstoff)

    Thanks for your repley.
    I found that the Transient for:
    _site_transient_community-events-3383c416d96e7e74e08084a6fca31eaf
    caused the unserelize-message.
    So, if I delete that transient & delete the View of Community-Events from the Dashboard the message is gone.
    It seems that is an Php Error as a result of the WP core?

    • This reply was modified 1 year, 1 month ago by treibstoff.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘unserialize(): Error at offset’ is closed to new replies.