There's a little issue with name suggestion for automatically created databases upon installing scripts.
All is okay as long as the default name "firstpartofdomainname_scriptname" is available (not yet present).
But as soon as the installer needs to make an alternate choice, because the default name already exists, things go wrong. :) Example:
Domain "example.com". I install "mantis" with no existing DBs. Default choice "example_mantis" presented and accepted.
I create an empty database "example_mediawiki". Then try to install MediaWiki. Name choice is now "example_mantis_mediawiki". Uuhm, unfortunate naming somewhat. :)
Then I try to install "wordpress", WITHOUT creating any "obstacle database". Name choice is "example_mantis_wordpress" even though "example_wordpress" is available.
This scheme continues (names get longer and longer) with each "obstacle" I create.
Comments
Submitted by JamieCameron on Tue, 06/07/2011 - 15:06 Comment #1
Thanks for pointing this out .. this can happen if the domain didn't have any databases to start with, which is rare so the issue wasn't noticed before. I will fix this in the 3.87 release.
Submitted by Issues on Wed, 06/22/2011 - 02:22 Comment #2
Automatically closed -- issue fixed for 2 weeks with no activity.