I've recently started moving the panto society's website over to concrete5 (the idea being to set up a nice easy to use CMS so that people who aren't me can maintain the website in the future). Overall, I've been pretty pleased with the software; it's certainly the easiest to use php based CMS I've ever used.
So far, I only have one gripe with it: concrete5 insists on being installed into an empty database. This was somewhat problematic for us, as our hosting provider only gives us one database, and I wanted to integrate the forums, etc, from the old site into the new one. I found a thread detailing a few kludgy hacks that could be used to get concrete to install into a non-empty database, and they seemed to work fine; I got everything up and running.
However, it would have been nice if the install script could have taken care of these issues by itself. So, in the spirit of open-source software, I've modified the installer to do just that. My modified script will allow concrete5 to be installed into a non-empty database. If the user attempts to do this, it first checks the names of the tables that are already in the database to ensure that no naming conflicts occur. If a naming conflict is found, it warns the user and refuses to install. Otherwise, it happily installs concrete5 alongside anything else that happens to be living in the database.
To use the modified installer, simply replace concrete/controllers/install.php with the version linked below, and then follow the standard concrete5 installation instructions.
No comments:
Post a Comment