I just recently went to install a forum on a cPanel server with MariaDB.
However, if you check out http://furryavalon.net/forums/install/install.php you'll notice it states there's no MySQL support... except there is.
On the server: http://furryavalon.net/info.php for your viewing pleasure.
It needs the MySQLi interface, thats not listed in your phpinfo() output.
Can we link to documentation that refers to how to resolve the issue? Maybe a LMGTFY link regarding solving this?
I've done an EasyApache rebuild with that extension enabled, should be resolved shortly. But still... you know. :P
Edit: EasyApache recompiled with that support enabled. I was confused as to why it wasn't working and why I got that message when I knew I had a MySQL server. Having a documentation/LMGTFY reference would clarify things quite nicely.
Also, this isn't really a bug, per se... but go ahead and close it, as I've resolved this issue... then again, perhaps my suggestion should be added to the Github issue list?
Let's keep it here then, so that there is at least a note on the fact it should be added.
Honestly I'm not an expert on the matter and I'm not sure what would be the best wording for it, if you have any suggestion about what and where add the note feel free and I'll be happy to make the necessary changes. ;D
Hmm... I'm trying to find where the code detects the fact that the mysqli extension isn't loaded and I can't seem to find it just from browsing the Github repo...
muttersEdit: I see that Db-check-MySQL.php checks for the extension... but I'm not seeing where it displays the error message.
Edit2: I'd have figured Errors.php, Errors.class.php or ErrorContext.php would've had the error message... but no. Where is this message hiding? :|
Ohh... I thought you meant documentation. Sorry, I misunderstood! ;D
At install time, the db-type is checked in install.php (at least in 1.0, in 1.1 I made few changes and I don't remember exactly where it is detected) and the language string is in install.english.php (at least it should be :P).
Documentation helps, too. But I think personally in my opinion, that if such an error is presented, an error message should at least hint as to how to resolve such an error. Perhaps by linking to documentation or to a topic that has a discussion with a solution?
I'll make an edit to the language string for that specific error to link to the documentation and/or this topic/post describing the solution. Then submit a PR. Would that work?
Sure! :D