Quote:
Originally Posted by zethon
I see the problem but I'm not too sure how to fix it. I'll look into it some more and get back to you. Hopefully before I take this out of Beta.
|
I did some looking into with this. It appears it may be a bug with vBulletin, as this is the second product I've found with the same error type.
It correctly establishes a connection with our external mysql server, but still attempts to connect to a non-existent local one. The includes/config.php file only defines one master external MySQL server.
So a warning is spitted out due to the local connection issue, but successfully connects to the external one. But since this warning is tossed out into the script, the script ceases to work.
So. How does one report such a bug to vBulletin?