sunspot10

For the record, I fixed the problem with the following procedure.

1. Backed up the site database with Updraft Plus plugin.

2. Renamed the table prefix in the wp_config.php file to be all lower case.

3. Did a fresh wordrpess install using the modified wp_config.php file with lower case table prefixes in it.

4. Activated the Updraft Plus plugin inside the fresh wordpress install.

5. Restored the database backup done previously with Updraft Plus

6. Logged into the admin panel and looked at the top of the page for the Woocommerce error.

The error is GONE now, because now the lower case table name prefix in MySQL matches that in the wp_config.php file.

So you were correct about a possible mismatch in the table name prefix case in Windows Server Plesk. However, the solution was not to manually try to change the table name prefix. The better answer is to use automated backup and restore. Updraft handles the translation of table names from the backup to the site it is restored to and does it properly and completely.

Thanks anyway.

The problem happens on MULTIPLE sites on the same windows server (3 sites).

1. Changing the table prefix did not help.
2. I was able to restore the data back to what it was BEFORE changing the table prefix.
3. The error still happens that began this thread with Woocommerce 4.4.1 and even 4.5 which just came out.
4. Obviously, there is a problem with Woocommerce 4.4.1 and 4.5 with running on Windoes servers because of translation of table names to all lower case.
5. Woocommerce STILL needs to be fixed to prevent this problem.

drwpcom

That is a helpful start on what the problem is. However:

1. When I change the table prefix to all lower case, I can no longer login to the site as admin at /wp-admin/. It says: “Sorry, you are not allowed to access this page.”

2. If I go back to the old wp-config.php file, I still have this problem.

Now I’m locked out of my site!

What next?

Vedanshu,

Thanks, but:

1. As I said, the user already has CREATE permissions. In fact, they have EVERY permission possible for a user to have.

2. AFTER seeing the error, I checked the tables list in phpMyAdmin and it already exists.

3. When I delete the table Woocommerce automatically restores and recreates it, but the error persists.

4. Your post also does not explain how to deal with the compile error email from WordPress.

Obviously, its a bug in the plugin, because the table is in fact being created automatically by Woocommerce but it still reports that it CANNOT be created.

I went back to Woocommerce 4.2.2 until the bug is fixed. I’m going to wait for 4.3.1 or later to try again. The error went away when I did so. This is a *.0 release and bugs like this are common when testing is insufficient.

• This reply was modified 4 years, 7 months ago by sunspot10.
• This reply was modified 4 years, 7 months ago by sunspot10.
• This reply was modified 4 years, 7 months ago by sunspot10.

Here’s an email that the site mailed to me about the error:

Here is an email I just got about the error:

“Howdy!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, WooCommerce.

First, visit your website (https://XXXX.org/) and check for any visible issues. Next, visit the page where the error was caught (https://XXXX.org/wp-login.php) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

https://XXXX.org/wp-login.php?action=enter_recovery_mode&rm_token=____OZtKttc43O9brfrTQw&rm_key=npANHpWbodQq9F9Db0C0AJ

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.4.2
Current theme: Kleo Child (version )
Current plugin: WooCommerce (version 4.3.0)
PHP version 7.3.19

Error Details
=============
An error of type E_COMPILE_ERROR was caused in line 168 of the file C:\inetpub\vhosts\XXXX.org\httpdocs\wp-content\plugins\woocommerce\vendor\autoload_packages.php. Error message: require_once(): Failed opening required ‘C:\inetpub\vhosts\XXXX.org\httpdocs\wp-content\plugins\woocommerce\packages\woocommerce-blocks\src\BlockTypes\PriceFilter.php’ (include_path=’.;.\includes;.\pear’)”

We got tired of waiting after two weeks for a fix. Found a much better solution and switched all of our sites over to that.
https://codecanyon.net/item/woocommerce-membership/8746370?s_rank=5

Pmpro didn’t fit all of our needs and always had deficiencies:

1. The payment gateway settings had no way to control the interface to Woocommerce.
2. The built-in gateways with PmPro do not support our gateway provider so we had to go through woocommerce.
3. PMPro membership joins did not register in the Woocommerce system or the graphing for woocommerce. We wanted them integrated.
3. PmPro did not handle downloadable content integration. Needed to find YET ANOTHER product to do that which had its own share of problems and its own limited payment gateways which also didn’t support our provider. Was using WordPress Download Manager for that:
https://www.ads-software.com/plugins/download-manager/
4. There were always interoperability problems between all the various plugins needed to make everything work. Something was always breaking because the plugins were not updated TOGETHER and kept in sync, or they had compatibility issues with newer versions of php.
5. PmPro recently added nag screens to the Admin backend telling you that you needed support that you had to keep shutting off.
6. PMPro raised their annual support costs from 97 to 197, and neither one should have been necessary if the product had a simpler, more integrated design like the above.

The above product solved all the above problems and allowed us to replace 11 plugins with just one, considerably lower our support costs, eliminate all support contracts, and dramatically simplify the management and reliability of our site. Dumping PmPro has been a good decision that we would recommend to anyone.

P.S.

Running Woocommerce 3.0.8. Using ONLY payment gateways available through Woocommerce and NONE of the payment gateways running under PM Pro.

FYI:

1. Version 1.4.2 came out today, 3/14/2017
2. I installed and tested it and it fixes this bug.
3. For additional information on the fix, see:
https://github.com/strangerstudios/pmpro-woocommerce/issues/50

stickymathscom

Thanks for the update.

The above fix:
1. Reduces my page load times from 11 seconds to 3 seconds.
2. Dramatically lowers the cpu utilization on my server.

Please fix this ASAP. PmPro!

P.S.

Implemented the fix suggested in the following link on version 1.4.1 and it fixes the problem.
https://github.com/strangerstudios/pmpro-woocommerce/issues/52

1. Upgraded to version 1.4.1, which is one version beyond the version with the problem.
2. Problem STILL persists.

Please fix asap.

The settings in the wp_config.php file related to this:

“/** WordPress absolute path to the WordPress directory. */
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);”

FURTHER TROUBLESHOOTING:
1. The Plesk php setting for “open_basedir” was set to: “{WEBSPACEROOT}{/}{:}{TMP}{/}”.
2. Changing it to “none” or “{DOCROOT}{/}{:}{TMP}{/}” or “/” did not fix the problem with version 1.4.

Server config:
1. Plesk Onyx update 18.
2. Windows server 2012 R2.
3. All latest updates and patches installed.

Please fix ASAP!