WPIntell

Source evidence

Fatal error on activation

WP phpMyAdmin · support · 2023-03-21T10:21:00+00:00

complaintsentiment
highseverity
0.97relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

4 / 31 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

27 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
johnny2r unresolved
After installing the plugin on WordPress 6.1.1, PHP 7.4.3, Ubuntu 20, when I try to Activate I get the error below: Fatal error: Uncaught Error: Call to undefined function Puvox\mb_ereg_replace() in /var/www/mysite/wp-content/plugins/wp-phpmyadmin-extension/library.php:281 Stack trace: #0 /var/www/mysite/wp-content/plugins/wp-phpmyadmin-extension/index.php(698): Puvox\library::realpath() #1 /var/www/mysite/wp-content/plugins/wp-phpmyadmin-extension/index.php(94): WpPhpMyAdminExtension\PluginClass->file_put_contents() #2 /var/www/mysite/wp-includes/class-wp-hook.php(308): WpPhpMyAdminExtension\PluginClass->setup_definitions() #3 /var/www/mysite/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #4 /var/www/mysite/wp-includes/plugin.php(517): WP_Hook->do_action() #5 /var/www/mysite/wp-admin/admin.php(175): do_action() #6 /var/www/mysite/wp-admin/index.php(10): require_once('/var/www/barnes…') #7 {main} thrown in /var/www/mysite/wp-content/plugins/wp-phpmyadmin-extension/library.php on line 281 A search here has shown this reported before, and the fix suggested was to make sure the ‘mbstring’ extension was enabled. But I have installed and enabled it, as far as I can tell. php -r "print_r(get_loaded_extensions());" shows ‘mbstring’ as one of the loaded extensions. What else might be wrong? If it’s significant, we have a live site and a staging site and on the live site the plugin version is 5.2.0.7 and all seems to be OK. The problem only exists on the staging site (otherwise identical) where the plugin was updated to 5.2.1.02. LATER: Having reverted to 5.2.0.7, the problem has gone away. So there may be some new issue there. This reply was modified 3 years, 2 months ago by johnny2r .

Comments

1 shown
johnny2r 2023-03-21T13:31:00+00:00

If it’s significant, we have a live site and a staging site and on the live site the plugin version is 5.2.0.7 and all seems to be OK. The problem only exists on the staging site (otherwise identical) where the plugin was updated to 5.2.1.02. LATER: Having reverted to 5.2.0.7, the problem has gone away. So there may be some new issue there. This reply was modified 3 years, 2 months ago by johnny2r .