Installation of Flux CMS
- PHP 5.2.x or later with DOM, XML, SimpleXML, iconv, SPL, MySQL, XSLT ( --with-xsl) and Reflection (for the installer)
- (DOM, SimpleXML, SPL, iconv and Reflection are enabled by default, except if you're using --disable-all)
- It may work with PHP 5.0.x, but we don't support it anymore.
- Make sure, you have the latest libxml2 libraries. 2.6.16-20 especially have problems with the blog plugin.
- (commandline) imagemagick for auto-resizing of images in galleries (since 1.3 there's an option to use gd instead)
- ext/tidy for tidy support (optional, you can disable it in the sitemap and the installer checks for it automatically)
- Apache 1.3 or 2.0/2.2 with enabled mod_rewrite support (eg. "LoadModule rewrite_module modules/mod_rewrite.so" in httpd.conf has to be enabled)
- PHP as apache module (mod_php) or
- Apache 2.0, php5-fcgi, mod_fastcgi work wonderfull (script run as user and apache SuexecUserGroup user usergroup not as danger anonymous apache user) how-to install http://www.debianhowto.de/howtos/de/apache2-phpfcgi-sarge/ use php-5.0.4.tar.bz2
- MySQL 4.x/5.0.x, Flux CMS is currently only tested with MySQL. We recommend using MySQL 4.1.x or 5.0.x, but Flux CMS runs without any problems on 4.0.x, as well. MySQL 5.1.x is not relly tested yet. Support for other database servers (like PostgreSQL, sqlite) would be possible with little adjustements.
Check out the Download page. We highly recommend you to install Subversion for getting the latest and greatest sources.
You might have to give the correct permissions to the files you downloaded. You can use something along the lines of:
find . -type d |xargs chmod 755
find . -type f |xargs chmod 644
- Create a VirtualHost for the just created
fluxcms directory (the cms does work in a subdirectory of a VirtualHost, but this is not really tested, so we recommend using it in DOCUMENT_ROOT.)
- If you want to use VirtualHosts, don't forget to modify your hosts file like the following example:
- Be sure to have
mod_rewrite (see above) enabled in Apache. A simple VirtualHost entry may look as following:
- Open up the webbased installer: http://fluxcms/install/
- Go through that. If everything works ok, Flux CMS is set up.
- Open your newly installed Flux CMS with http://fluxcms/
- The admin can be reached with http://fluxcms/admin/ (the trailing slash is important right now). You can log in with the data provided in the installer.
- HINT: depending on your configuration, the newly created files will not have the right read permission. Someone had problems with access .htaccess after the installation and had to give read rights for all (he was using php-cgi in apache)
Doing it manually
*It's not recommended doing it manually. Too many things can go wrong Use the installer, which should work on all system. If it doesn't, please tell us *
- create a MySQL database and a user for the CMS
- import div/db/bxcms.sql into this MySQL db (make shure to replace ##bxcms_## with mytableprefix_)
- add a user to the
users table (the password has to be md5 hashed)
- cd to the fluxcms directory
- cp install/dist/htaccess to .htaccess and replace ##DIR## with your subdir (if one, if in DOCROOT, just remove it)
- cp -r install/dist/conf .
- cp -r install/dist/sitemap .
- cp -r install/dist/data .
- adjust conf/config.xml to your settings (mainly DB settings).
- make the "data" and "tmp" directory writable for the webserver
- open the page
If you don't have Apache/Mysql/PHP installed on Windows, see Installation on Windows for a simple installation instruction.
If you get PHP errors or even segfaults (during or after installation), check your Zend Extensions. Zend Optimizer is well known for not really behaving correctly. Turn it off (or download updates of those extensions) and check, if it works without. We also had problems with eAccelerator from time to time.
Also check those settings:
- GD value in conf/config.xml
- write access to root directory, ./tmp, ./files, ./data, and ./themes.
PHP as CGI
According to our tests, Flux CMS does also work on a php-as-cgi installation. The only thing, we had to change, was to remove all "php_value", resp. "php_flag" instructions from the .htaccess file (You can also do this before the installation in install/.htaccess). They are not needed anyway, just precaution settings. The installer should now take care of that issue and automatically remove these instructions, if the apache module wasn't found.
If you still get "Internal Errors" after removing those, your apache-cgi installation is missing some other modules, Flux CMS needs. Look in your Apache Error Log File, which instructions Apache is complaining about.
Sometimes IE seems to produce 500 (Internal Errors) Codes in error.log and show only a white page, where Firefox makes 304 (Not Modified) Codes and shows the page. If that happens add "cgi.nph = 1" to your php.ini file.
Moving to a subdirectory (or to /)
In case you installed flux on a local computer in a subdirectory, and you want to move the installed flux to the root directory of your remote hosting environment, you have to adjust the following:
- many lines in .htaccess
- line 6 in ./conf/config.xml