Version 4.3 Fatal Error

Resolved larrystew
(@larrystew)

3 years, 9 months ago

Tried to update to v. 4.3 today but instead wound up with a broken backend that I was unable to log in to. After some hosting technical help, went back in to begin activating plugins STARTING with WooCommerce. It was unable to be activated due to not being able to find a particular VAR directory…? Sorry for not having the actual text of the error. I’m running the latest WordPress version, the latest Storefront child theme, and WooCommerce 4.3. Doesn’t look like a plug-in conflict since WooCommerce was the first one I tried when re-activating.

Viewing 11 replies - 1 through 11 (of 11 total)

Plugin Support Rynald0s.a11n
(@rynald0s)

Automattic Happiness Engineer

3 years, 9 months ago

Hi @larrystew!

It was unable to be activated due to not being able to find a particular VAR directory…?

Sorry for not having the actual text of the error.

Are you able to access the fatal error log found under “WooCommerce > Status > Logs” and paste that log data back here so we can take a closer look?

Cheers!

Thread Starter larrystew
(@larrystew)

3 years, 9 months ago

I tried activating again after updating Storefront, and here’s the error message I received:

Warning: require_once(classes/ActionScheduler_Versions.php): failed to open stream: No such file or directory in /var/www/wp-content/plugins/woocommerce/packages/action-scheduler/action-scheduler.php on line 31

arcangelini
(@arcangelini)

3 years, 9 months ago

Hey @larrystew !

No problem at all. That is an odd error that I am not seeing in any of our bug reports.That appears to be referencing the Action Scheduler package which WooCommerce uses to process all the scheduled events.

I would suggest leaving WooCommerce deactivated, then installing Action Scheduler manually. You can read through this guide here, specifically the part that references “Usage as a plugin”.

Once you have installed the latest version of WooCommerce, then you can attempt to activate WooCommerce again to see if that helps.

Thread Starter larrystew
(@larrystew)

3 years, 9 months ago

Tony, which of the following methods do you suggest using? I ask this only because WC seems to be the only plugin with this error.

Installation
There are two ways to install Action Scheduler:

regular WordPress plugin; or
a library within your plugin’s codebase.

Thread Starter larrystew
(@larrystew)

3 years, 9 months ago

Tony, here’s the message I received after adding the Action Scheduler plugin.

Missing the WooCommerce woocommerce-admin package
Your installation of WooCommerce is incomplete. If you installed WooCommerce from GitHub, please refer to this document to set up your development environment.
Thread Starter larrystew
(@larrystew)

3 years, 9 months ago
```
### WordPress Environment ###

WordPress address (URL): http://vm0.daa.myftpupload.com
Site address (URL): http://vm0.daa.myftpupload.com
WC Version: 4.3.0
REST API Version: ✔ 1.0.10
WC Blocks Version: ✔ 2.7.1
Action Scheduler Version: ✔ 3.1.6
WC Admin Version: There has been a critical error on your website. Please check your site admin email inbox for instructions.Learn more about debugging in WordPress.
```
Thread Starter larrystew
(@larrystew)

3 years, 9 months ago

Here’s the error in its complete form:

Error Details
=============
An error of type E_COMPILE_ERROR was caused in line 168 of the file /var/www/wp-content/plugins/woocommerce/vendor/autoload_packages.php. Error message: require_once(): Failed opening required ‘/var/www/wp-content/plugins/woocommerce/packages/woocommerce-admin/src/Package.php’ (include_path=’.:/opt/remi/php73/root/usr/share/pear:/opt/remi/php73/root/usr/share/php:/usr/share/pear:/usr/share/php’)

arcangelini
(@arcangelini)

3 years, 9 months ago

Hey @larrystew

That is really odd, both of those are packages that should be included with WooCommerce. At one point they were separate plugins but now should be included.

It is possible that your core files for WooCommerce may not be correct. Before moving forward, can you download the latest version of WooCommerce from here. Then manually replace the WooCommerce plugin folder in your site.

You can do this from a file manager, or FTP. The WooCommerce folder will be in wp-content ⇢ plugins. Follow these steps if you need some help.

If that does not work, then you can try installing WooCommerce Admin plugin separately to see if that resolves the error.

Thread Starter larrystew
(@larrystew)

3 years, 9 months ago

Tony, what will happen to my settings if I simply deactivate and delete the original plugin (which IS 4.3 at this time)? Do I need to take screenshots or make notation of my settings before going through with this? Is there a file I can download to keep those settings?

arcangelini
(@arcangelini)

3 years, 9 months ago

Hey again @larrystew !

Great question.

By simply deactivating and deleting the plugin you will only remove the plugin files. All you settings and such are stored in the database which is not affected.

I always advise taking a backup in case something unexpected happens. You are welcome to try that first if you want.

Plugin Support Tseten a11n
(@tibetanitech)

3 years, 8 months ago

We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘Version 4.3 Fatal Error’ is closed to new replies.

Tags