WPIntell

Source evidence

Error

Automatic Product Categories for WooCommerce · support · 2025-06-06T05:16:00+00:00

mixedsentiment
highseverity
0.94relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 23 rows with source links

17.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
danm2014 resolved
There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums. Learn more about troubleshooting WordPress. —————————————————————– When I try to enter the plugin in the dashboard I get this. I can’t do anything in the plugin. I already setup a few time ago some categories etc but now it is not accesible. The page I need help with: [ log in to see the link] Hi, Thank you for reaching out and letting us know about the issue you’re experiencing with the plugin page on your site. The error message “There has been a critical error on this website” typically indicates a PHP-related issue. Here’s what you can try to resolve the issue: 1. Enable Debugging to Identify the Error To help us pinpoint the exact cause, please enable WordPress debugging by following these steps: Access your site files via FTP or your hosting control panel (File Manager). Open the wp-config.php file in the root directory of your site. Add the following lines just before the line that says /* That’s all, stop editing! */: define(‘WP_DEBUG’, true); define(‘WP_DEBUG_LOG’, true); define(‘WP_DEBUG_DISPLAY’, false); Save the file and try to access the plugin page again. This will log any errors to a file located at: /wp-content/debug.log Once done, please send us the contents of that file (especially the most recent entries), so we can investigate further. Once we receive the error log or more details from your end, we’ll be able to provide a specific fix or update. Please let us know once you’ve had a chance to review the debug log. Came across a similar crash today. In RulesListTable.class.php, line 49 we have $rule = new (AutomaticProductCategories::instance()->ruleClass())(); … which my (old) PHP 7.3 does not seem to like. If I change this to $_classname=AutomaticProductCategories::instance()->ruleClass(); $rule=new $_classname(); … it works This issue has been fixed and the update has been released. Let us know if you encounter any further issues.

Comments

3 shown
BerryPress Support 2025-06-06T10:53:00+00:00

Hi, Thank you for reaching out and letting us know about the issue you’re experiencing with the plugin page on your site. The error message “There has been a critical error on this website” typically indicates a PHP-related issue. Here’s what you can try to resolve the issue: 1. Enable Debugging to Identify the Error To help us pinpoint the exact cause, please enable WordPress debugging by following these steps: Access your site files via FTP or your hosting control panel (File Manager). Open the wp-config.php file in the root directory of your site. Add the following lines just before the line that says /* That’s all, stop editing! */: define(‘WP_DEBUG’, true); define(‘WP_DEBUG_LOG’, true); define(‘WP_DEBUG_DISPLAY’, false); Save the file and try to access the plugin page again. This will log any errors to a file located at: /wp-content/debug.log Once done, please send us the contents of that file (especially the most recent entries), so we can investigate further. Once we receive the error log or more details from your end, we’ll be able to provide a specific fix or update. Please let us know once you’ve had a chance to review the debug log.

cduray 2025-06-13T07:26:00+00:00

Came across a similar crash today. In RulesListTable.class.php, line 49 we have $rule = new (AutomaticProductCategories::instance()->ruleClass())(); … which my (old) PHP 7.3 does not seem to like. If I change this to $_classname=AutomaticProductCategories::instance()->ruleClass(); $rule=new $_classname(); … it works

BerryPress Support 2025-06-18T12:51:00+00:00

This issue has been fixed and the update has been released. Let us know if you encounter any further issues.