@morganelite Issues like this are most often caused by conflicts. Disabling plugins will usually bring the site back on, but re-enabling the conflicting plugin will cause the error to pop up again.
These issues can be caused by a specific combination of plugins. So, for example, a plugin that adds functionality to the main WooCommerce plugin may be the culprit, but deactivating the WooCommerce plugin would also disable the functionality of that second plugin, thus giving the appearance of the issue being solved.
The error you shared above those references this plugin: woo-checkout-field-editor-pro
. So that would be a great place to start testing. If you disable this plugin, does the issue go away?
If that doesn’t solve the issue, what you’ll want to do to find out which plugin is the true culprit, is run a full conflict test. You’ll want to temporarily switch your theme to Storefront. Then, disable all plugins on the site except for WooCommerce, and test for the issue.
If the site works correctly under that default setup, you’ll then have to re-enable features one by one, while testing for the issue; until you find out which one is causing this behavior. If the site crashes again, you’ll know that the last plugin to be updated is what’s causing the issue.
We recommend that these steps are taken on a staging site, which is a clone of your live site that you can modify without risking making any permanent damage to your live site. You can create it using a plugin like WP-Staging.