Support » Plugin: Lagersystem.dk: Parcelpickup locator for Woocommerce » Bug report: fatal error after WooCommerce update to 4.5.2

  • Resolved skafte

    (@skafte)


    Hi there,

    I’m experiencing that the plugin is causing a fatal error on one of my multisite sites. Here’s the error message I see when I put the site in DEBUG mode:

    Fatal error: Uncaught Error: Call to undefined function WC() in /www/wp-content/plugins/lagersystem-dk-parcelpickup-locator-for-woocommerce/admin/class-lagersystem-parcelpickup-woocommerce-admin.php:261 Stack trace: #0 /wordpress/wp-includes/class-wp-hook.php(287): Lagersystem_Parcelpickup_Woocommerce_Admin->register_shippingoptions('') #1 /wordpress/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array) #2 /wordpress/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #3 /wordpress/wp-admin/admin.php(175): do_action('admin_init') #4 /wordpress/wp-admin/index.php(10): require_once('/wordpress/wp-a...') #5 {main} thrown in /www/wp-content/plugins/lagersystem-dk-parcelpickup-locator-for-woocommerce/admin/class-lagersystem-parcelpickup-woocommerce-admin.php on line 261

    I’m not sure this error is definitely due to the WooCommerce update, but it came right after I had made the update.

    Also, there doesn’t seem to be a problem on the other sites in the multisite network.

    • This topic was modified 4 months, 2 weeks ago by skafte.
Viewing 3 replies - 1 through 3 (of 3 total)
  • UPDATE:

    I’ve just reinstalled WooCommerce 4.5.1 via FTP and that did not seem to help. I’m now thinking this might not have anything to do with WooCommerce – unless the update affected the database, which then caused the error. However, I doubt that…

    UPDATE:

    It definitely seems to be a multisite compatibility issue. For the record, I’ve not tried to run the plugin across a network of sites, but have simply installed it on the network and activated the plugin separately on each child site.

    Hope you’ll consider fixing this issue and making the plugin multisite compatible – and maybe even put it on GitHub as well 😉

    Cheers!

    UPDATE:

    Hi there @lagersystem – just wanted to let know that strangely, out of the blue, it suddenly started working on all child-sites. Very odd! I believe it must have been a caching issue or similar. Anyway, I hope that reporting the fatal error will still have been useful 🙂

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