WPIntell

Source evidence

Error with MariaDB

Display PHP Version · support · 2021-05-08T11:46:00+00:00

complaintsentiment
mediumseverity
0.92relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 31 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Ian MP unresolved
Delighted to see that this simple but very helpful plugin has once again been activated and will get off the ‘deprecated’ list. I installed the 1.7 update, but the following error is being displayed on the dashboard page: “Warning: mysqli_connect(): (HY000/2002): Connection refused in /…/wp-content/plugins/display-php-version/display-php-version.php on line 38 Warning: mysqli_get_server_info() expects parameter 1 to be mysqli, bool given in /volume1/web/wordpress/wp-content/plugins/display-php-version/display-php-version.php on line 38” I don’t know if this is because my system is using MariaDB instead of MySQL as the display returns an blank for the MySQL entry. Thanks for reporting. I’ll take a look (from Monday) and get back to you. Are you running the plugin on a local WordPress site? If so I’ve had other reports that the DB_HOST value in wp-config.pgp should be set to 127.0.0.1 to fix any issues associated with MariaDB. This reply was modified 4 years, 12 months ago by David Gwyer . Hello David, thanks for getting back. I’m running on a development server, but not a localhost as it has an external URL (for checking https etc). However, I have since installed it on my existing live site ( a simple 4-page static site) and it works fine, although that’s running MySQL and not MariaDB. To be sure, I tested it on a localhost (with & without your suggested change above but running MariaDB in both instances) and it also worked fine. So, back to my development site: it seems that the only difference is, while the original sites (live & localhost) were using the GeneratePress theme and running Elementor, my new site is using the Kadence theme with Kadence Blocks. My conclusion therefore is that it is either the Kadence theme or Kadence plugins. However, as both are integral to my site, I can’t disable either without breaking it but it does seem that Kadence is the problem. Hope this helps. Thanks for the update. However, I’m not sure how the current theme could be the issue as the plugin is querying the DB directly using the PHP function mysqli_get_server_info .

Comments

4 shown
David Gwyer 2021-05-08T13:40:00+00:00

Thanks for reporting. I’ll take a look (from Monday) and get back to you.

David Gwyer 2021-06-02T11:09:00+00:00

Are you running the plugin on a local WordPress site? If so I’ve had other reports that the DB_HOST value in wp-config.pgp should be set to 127.0.0.1 to fix any issues associated with MariaDB. This reply was modified 4 years, 12 months ago by David Gwyer .

Ian MP 2021-06-02T12:10:00+00:00

Hello David, thanks for getting back. I’m running on a development server, but not a localhost as it has an external URL (for checking https etc). However, I have since installed it on my existing live site ( a simple 4-page static site) and it works fine, although that’s running MySQL and not MariaDB. To be sure, I tested it on a localhost (with & without your suggested change above but running MariaDB in both instances) and it also worked fine. So, back to my development site: it seems that the only difference is, while the original sites (live & localhost) were using the GeneratePress theme and running Elementor, my new site is using the Kadence theme with Kadence Blocks. My conclusion therefore is that it is either the Kadence theme or Kadence plugins. However, as both are integral to my site, I can’t disable either without breaking it but it does seem that Kadence is the problem. Hope this helps.

David Gwyer 2021-06-02T12:30:00+00:00

Thanks for the update. However, I’m not sure how the current theme could be the issue as the plugin is querying the DB directly using the PHP function mysqli_get_server_info .