Confusing errors when mysqli fails but mysql works

[paulschreiber]

If your php.ini is misconfigured so that mysqli fails but mysql succeeds, you get a seemingly spurious "no such file or directory" error on the setup screen.

This is confusing because you simultaneously have an error condition and success.

It would be good to alert the user that we had to fall back so the cause of the fallback can be investigated.

[dd32]

It'd be good to get a list of requirements that need to be hit for this case to show up.

As far as I can tell, it requires

• MySQL to be setup not to use networking
• WordPress to be setup to use networking, not a socket address
• php.ini mysqli set to incorrect socket path
• php.ini mysql set to correct socket path

Does that sound like the correct set of conditions to reproduce this?

[paulschreiber]

Yes, that is one way of reproducing this, yes. By default, MySQL and PHP on OS X both use socket connections, not networking, so this is a common setup.

[johnbillion]

Closing this off as the mysql extension is no longer supported.