Installation/Troubleshooting

From Lanius CMS Wiki

Troubleshooting

There may be cases where you are unable to finish the installation process successfully, sometimes your server configuration doesn't allow for that. Below is the list of error cases that you can encounter during the installation.

Stage 0:

• error can appear only when you're trying to install over a Lanius CMS which is already installed

Stage 0 - error message while installing over existing copy of Lanius CMS

Stage 1:

• warnings regarding optimal configuration is not met:
• red warning signals a broken feature,
• orange warning signals setting which is not optimal, but Lanius CMS will work even without it, however some features can be disabled,
• grey warning signals setting which is not optimal, but Lanius CMS will work even without it
• green notices are shown if your server met Lanius CMS requirements.

For example, if the PHP version is not 4.3.3+ Lanius CMS won't install, this is the only fatal error and the only solution is to update PHP.

• red warnings regarding the write permissions of files/directories. It is important to set proper (0777 or 0755) privileges for all Lanius CMS files and directories, so it can modify itself when doing updates. If they are not set correctly, the Lanius CMS installation wizard will try to locate a directory which has enough write permissions, so it can move files there in order to let them acquire the correct privileges, then it will move files back. If it still doesn't work, you'll have to set privileges manually, mostly using FTP or a shell client.

In FileZilla you can change write permissions by clicking on remote directory with Lanius CMS files and selecting File Attributes... A new window will open, where you should set all privileges, just like it is shown on screenshot below. Other FTP clients should also have appropriate option.

If you have shell access to your webserver, you can connect to the host and type following command to set write permissions:

chmod 777 /usr123/htdocs/Lanius CMScms -R

where /usr123/htdocs/Lanius CMScms is the path of your Lanius CMS directory. You can check write permissions applied to Lanius CMS files by typing

ls -l

in its directory.

Please note that Lanius CMS will continue with the installation without the correct write permissions, but the listed features will not work. You'll also not be able to use the flatfile databases, like Gladius DB or SQLite.

Stage 2:

• in this stage you will encounter only those notices about availability of databases:
• red item requires PHP update (which is not possible for some users using services from a webhosting company) to use this DBMS,
• gray item means that you can use this database system after installing additional database driver
• green items are for available database systems

Stage 3:

• You shouldn't encounter any problems with Stage 3

Stage 4:

• if a user has chosen a flat file database (SQLite or Gladius DB), the file private/$dbname ($dbname is by default Lanius CMS) should be writable. If it is not, installation will fail here and the reason will be shown from, usually one of two:
• if you didn't specify Lanius CMS as a database name and the rename operation from private/Lanius CMS to private/smth_else fails,
• if private/$dbname file is not writable.

• if the database connection fails, an error is shown. You should use the Test button in stage 2 to prevent such errors.

• if some SQL queries (schemas and default data SQL statements are executed) fail, the native DBMS error will be shown for each of them
• in case of insufficient write permissions, a box with config.php file content will be shown and the user will have to manually create it

Stage 1 will show Continue link only when the minimal requirements are met. Stage 2 will show Continue, Continue without the above features or no link, depending on the received results. Stage 4 will not say that everything went OK, if it really didn't.