Fatal error

Hello,

It looks like the error is coming from the theme that’s currently active on your site. You’ll want to reach out to the theme author directly and they should be able to assist you with this.

WordPress notified me of an error with my WC plugin. The error is:

An error of type E_COMPILE_ERROR was caused in line 24 of the file /var/www/volumes/xvdq/vhosts/rodsbyrane.com/httpdocs/wp-content/plugins/woocommerce/woocommerce.php. Error message: require(): Failed opening required ‘/var/www/volumes/xvdq/vhosts/rodsbyrane.com/httpdocs/wp-content/plugins/woocommerce/src/Autoloader.php’ (include_path=’.:’)

My hosting service deactivated the plugin so I could login to my admin panel. I tried to reactivate the plugin, yet failed due to this:

Plugin could not be activated because it triggered a fatal error.

What can you tell me?

Hi @ranefox!

It seems that the cause could be a conflict with your theme or another plugin you have installed on your site.

To be sure of this, please perform a conflict test by temporarily switching your theme back to Storefront, disabling all plugins, and then try to reactivate WooCoommerce. If you can install it, then re-enable all plugins one-by-one, until you find the one creating the conflict.

Let us know how that goes for you!

Here too!
PHP vers?o 7.4.3
WordPress 5.9.1
Theme: CSS child theme based on Divi 4.14.8
WooCommerce: 6.2.1

Temporary Solution

Deactivate WooCommerce

Roll Back the Divi to a previous version. There is a one click button on Divi > Options > Updates.

Take notes of versions new and old.

Activate WooCommerce.

Wait to a new-new version update of Divi.

Maybe there is a better solution by ElegantThemes, but I think it is a Divi issue.

Hi @nandocoelho

For better assistance, please create your own thread for your issue – https://www.ads-software.com/support/plugin/woocommerce/#new-topic-0.

We want to make sure that every user’s issues receive their own thread with proper attention.

* Frequently Asked Questions.

Thanks.

Hey @ihereira,

Thanks for the warning. I thought it would be just the same case as I have the same error with the same theme and plugin. I wasn’t aware of that.

Well, but let me post my last findings on the issue. I discover that this error may be replicable in one special condition along with the versions metioned above. If is used a dummy domain, a custom personal not public registered domain, say mydev.example.com it will cause the error. Otherwise if the domain is public acessible the error is not replicable.

Hello,

This is helpful for anyone looking for guidance.

We recommend contacting your theme support for further assistance.

Thank you.

Hi there,

We haven’t heard back from you in a while, so I’m marking this thread as resolved.

Hopefully, the provided information was helpful, and you solved the issue. If you have any further questions, we recommend creating a new thread.

Cheers!