An error of type E_ERROR was caused in line 136

  • Resolved nhhomegrown

    (@nhhomegrown)


    1 year, 3 months ago

    Hi my website is completely crashed due to these errors:

    An error of type E_ERROR was caused in line 136 of the file /home/newhomegrown/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Events.php. Error message: Uncaught Error: Call to undefined method WC_Notes_Refund_Returns::init() in /home/newhomegrown/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Events.php:136
    Stack trace:
    #0 /home/newhomegrown/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(150): Automattic\WooCommerce\Internal\Admin\Events->init()
    #1 /home/newhomegrown/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(99): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->includes()
    #2 /home/newhomegrown/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/FeaturePlugin.php(82): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->on_plugins_loaded()
    #3 /home/newhomegrown/public_html/wp-content/plugins/woocommerce/src/Admin/Composer/Package.php(65): Automattic\WooCommerce\Internal\Admin\FeaturePlugin->init()
    #4 /home/newhomegrown/public_html/wp-content/plugins/woocommerce/src/Packages.php(64): Automattic\WooCommerce\Admin\Composer\Package::init()
    #5 /home/newhomegrown/pub

    Please help! Thank you!

    • This topic was modified 1 year, 3 months ago by nhhomegrown.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)

  • Hi @nhhomegrown,

    my website is completely crashed due to these errors: An error of type E_ERROR was caused in line 136

    From what I understand, you’re experiencing a critical issue with your website due to an error of type E_ERROR on line 136 of the Events.php file in your WooCommerce plugin.

    The error message you’re seeing suggests that there’s a call to an undefined method ‘WC_Notes_Refund_Returns::init()’. This could be due to a variety of reasons, such as a conflict with another plugin or a problem with the theme you’re using.

    Here are a few steps you can take to troubleshoot this issue:

    1. Update your plugins and themes: This is a good practice to keep everything running smoothly and avoid any unexpected issues.
    2. Deactivate all plugins except WooCommerce: Sometimes, plugin conflicts can cause errors. Deactivating all other plugins will help you determine if this is the case. If the error disappears after doing this, reactivate each plugin one by one until the error reappears to identify the conflicting plugin.
    3. Switch to a default theme: If the issue isn’t resolved by deactivating plugins, try switching to a default theme like Storefront. If the error disappears after doing this, the issue may be with your theme. Here’s a handy guide on testing for conflicts: ?? How to Test for Plugin and Theme Conflicts.

    If none of these steps work, could you please share your site’s System Status with us? This will give us a better understanding of your site’s setup and help us identify the problem. You can find it via WooCommerce > Status. Select Get system report and then Copy for support.

    Once you’ve gathered this information, please paste it inside a Code block in your reply, or use https://pastebin.com to paste it and share the link with us.

    Thanks for your patience and cooperation in this matter! We’re here to help you get this sorted.

Viewing 1 replies (of 1 total)
  • The topic ‘An error of type E_ERROR was caused in line 136’ is closed to new replies.