Support

Hm... there's something strange here. The phpinfo() page claims both mysqli and PDO MySQL are enabled on PHP 7.4.18. ANGIE, the restoration script, claims that mysqli is not enabled (by omission the initial check does not test for PDO MySQL, this is something I noticed and fixed four days ago).

There is only one reasonable way this can happen: the phpinfo page you sent me is not from the same version of PHP you are using to restore the site. MAMP does support using different versions of PHP per site, each PHP version has its own configuration.

Let's try something.

If you go to the next page, do you see any options in the drop-down menu? If so, don't worry, continue the restoration. Also rest assured that future versions of the restoration script will display the correct database support status in the main page as I am changing it to use the common detection code used in the Restore Database page to populate the dropdown.

If you see no options in the drop-down I would say the problem is that you are restoring to a different version of PHP, one which does not have either mysqli or PDO MySQL enabled. In this case I'd like to kindly request that you tell me which version of MAMP Pro you are using. My wife is on a recent if not the latest version of MAMP Pro and we observed no problems like that — we currently work in the same office, she runs a website studio, she restores sites all the time as part of the site development process and I can't deny her priority support for obvious reasons :)

The database support does check for mysqli which I see in the dropdown list. I am not sure what is going on there. In any case I am not going to spend time on it as four days ago I changed how that check works. It will now be using the same checks used to show the dropdown of available database types. So that would work on your server.

> However, I am having issues with my CMS (Joomla) stopping connections to MySQL randomly with no obvious error so I figured something may still not be right in my PHP config.

It's not your site's configuration. That's MAMP. I've noticed that for whatever reason the MySQL server they supply seems to randomly crash. Restarting the database server through MAMP's interface fixes it.

I don't have this problem using MySQL 8.0.28 installed through Homebrew on my M1 Mac mini so it's definitely something about the MAMP-supplied binaries.

Standalone. I gave up on MAMP years ago because it'd take forever to include new PHP versions, adding PECL extensions (especially SSH2 which I need for testing our software's SFTP features) was complicated and I disagreed on many performance settings.

For the past several years I install MySQL, Apache and PHP through Homebrew. I have documented my setup in my blog: Custom Apache and PHP server on macOS, the definitive 2019 edition     

Obviously with an M1 Mac the Homebrew installation is in /opt/homebrew instead of /usr/local so that part of all instructions needs to be changed. Also, the article being old was using PHP 5.6, 7.2 and 7.3. My current setup uses 7.4, 8.0 and 8.1 with 8.1 being the default. If we need to test against older PHP versions I either use my Linux box (I have PHP 5.6 to 8.1 inclusive over there) or Docker containers on my Intel MacBook Pro. To be honest, last I had to test with anything older than 7.4 was over a year ago so there's that.

Technically, MySQL has not crashed, it has become unresponsive. Until it crashes there will be no log dump. Even so, there's no use for it as I don't think they are using a debug build.