PHP ERROR

  • Resolved schero86

    (@schero86)


    1 year, 1 month ago

    Hello,

    I get following error on backend when checking issues with querry monitor

    unserialize(): Error at offset 5 of 362 bytes / wp-includes/functions.php:650

    1. wp-includes/functions.php:650
    2. unserialize()
      wp-includes/functions.php:650
    3. maybe_unserialize()
      wp-includes/option.php:247
    4. get_option()
      wp-content/plugins/woocommerce/includes/admin/helper/class-wc-helper-options.php:53
    5. WC_Helper_Options::get()
      wp-content/plugins/woocommerce/src/Internal/Admin/Notes/WooSubscriptionsNotes.php:137
    6. Automattic\W\I\A\N\WooSubscriptionsNotes->is_connected()
      wp-content/plugins/woocommerce/src/Internal/Admin/Notes/WooSubscriptionsNotes.php:118
    7. Automattic\W\I\A\N\WooSubscriptionsNotes->check_connection()
      wp-content/plugins/woocommerce/src/Internal/Admin/Notes/WooSubscriptionsNotes.php:89
    8. Automattic\W\I\A\N\WooSubscriptionsNotes->admin_head()
      wp-includes/class-wp-hook.php:324
    9. do_action('admin_head')
      wp-admin/admin-header.php:163
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Zubair Zahid (woo-hc)

    (@doublezed2)

    Hello schero86,

    Thank you for contacting WooCommerce support.

    I understand that you’re encountering an error ‘unserialize(): Error at offset 5 of 362 bytes’ while using the Query Monitor plugin.

    To help me get a better understanding of the situation, could you please take and share a screenshot of where exactly this error is appearing?

    Also, it would be helpful to have a closer look at your site’s environment. Could you please send me a copy of your site’s System Status Report?

    You can obtain it by doing the following:
    1. Go to WooCommerce within your WordPress dashboard.
    2. Click on ‘Status’.
    3. Click on ‘Get system report’ and then on ‘Copy for support’.

    After you’ve copied the report, please paste it into a new gist at https://gist.github.com and send me the link to the gist here in your reply.

    With the screenshot and the System Status Report, I will be able to delve deeper into the issue and determine the root cause of the error you’re seeing.

    I am looking forward to your response. ??

    Best regards.

    Thread Starter schero86

    (@schero86)

    I get the error on the admin dashboard, on wc-orders page, it is shown in querry monitor.

    https://gist.github.com/scherfro/b4cabcf9a553d6f540873b02b2465d1e

    Hey, @schero86! Thanks for sharing the report.

    I see WooCommerce is updated, can you please check if there are any plugins or the theme needing update?

    If the issue persists, please run a conflict test.

    To test, you’ll first want to change the theme on your site to Storefront, then check to see if the issue is still present. If that resolves the issue, you’ll want to get in touch with your theme’s developer and see if they have an update or fix for you.

    If changing the theme doesn’t help, you’ll want to deactivate all plugins except for WooCommerce and take a look. If that fixes the problem, re-enable the other plugins one by one (gradually), checking after each, to see where the issue is coming from.

    — Be sure you have a good backup in place of your full site and database. You can ask your host for backup functionality or you can consider using a service like Jetpack. If something goes wrong, you will be able to restore it.

    — Also, you can consider using a plugin like Health Check & Troubleshooting. This is a plugin developed by the WordPress community and it is helpful to disable plugins without affecting your current site visitors.

    — It is important to consider as well a staging functionality in case you would not like to touch your production site (you can ask your host if they offer this service), or you can use WP Staging for quickly spinning up a new test site.

    You can find more about this in this guide.

    Please let us know about your findings.

    Looking forward to your reply.

    Have a wonderful day!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘PHP ERROR’ is closed to new replies.