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

Hi Stack19,

What’s your PHP and WP versions? Is it a multi-site installation?

WP Version 5.4.1
PHP version 7.3.15

It is not multi-site

I have the same issue now also, Deactivating the pluging triggered a fatal error ( 500 error ) in the website…

@oaymen Thanks for the report.

Can you provide the error message? You can find it on your log file. Is it the same as reported by @stack19? His error was “Uncaught Error: Class ‘UserExportWithMeta\Main’ not found”.

I would appreciate it if you could provide us with the log error message, as it will prevent other users from experiencing the same issue.

But as it can take some days for me to fix this issue, and as it can take you some work to find the error in the logs – it may even require you to enable the logs first, if you are in a hurry you can just proceed to manually remove the plugin.

To manually remove the plugin, you can delete the plugin folder in your WP installation. The folder is located on “/wp-content/plugins/user-export-with-their-meta-data”.

[27-May-2020 20:20:46 UTC] PHP Fatal error: Default value for parameters with a class type hint can only be NULL in ../wp-content/plugins/user-export-with-their-meta-data/vendor/loureirorg/settings-as-woocommerce/src/Woocommerce/WC.php on line 158

@stack19 I just tested with the exact same versions as you have (WP Version 5.4.1
PHP version 7.3.15) and it worked perfectly.

So, I am wondering if this issue is being triggered by something specific to your installation.

Where’s your website running on? Are you using a WordPress host service like wpengine or flywheel? Or is on something like digitalocean, vultr, aws? Are you using CPanel or something similar?

Thanks a lot @oaymen. What’s you PHP and WP version?

You are welcome.

PHP version: 7.3
The latest version of WP: 5.4.1

Best regards,

@loureirorg

Are there any problems with multiple instances of the plug in working on the same server? We do not have a Multi-site install, but another instance of your plug in is running fine in other subdomain.
It’s just that in this subdomain it does not work.

We are getting more information from the server

@oaymen I just published a new version.

Can you update the plugin to the latest version (0.5.1) and let me know if it works (i.e. if you can deactivate it without a 500 error)?

@stack19 It shouldn’t be a problem since I also have many websites with this plugin running on the same server.

Is it your “plugins” folder a symbolic link? If the plugin is on a symlink folder, then there’s a chance this is the issue.