Child pages
  • Upgrade guide
Skip to end of metadata
Go to start of metadata

This page guides you through an upgrade of CONTENIDO 4.9. If you want to update an old version (e. g. CONTENIDO 4.8) to 4.9, please read the guide "Upgrade from CONTENIDO 4.8 to 4.9". For an installation, please have a look at this guide.

Trouble during upgrade?

If you have any trouble during the upgrade, the community in the support forum at may be able to help you and answer any questions.

Recommendation for upgrades

It is highly recommended that upgrades from an earlier version are done locally (or on a second installation) and not on the production system, as many fixes and changes might came along with the upgrade depending on the amount of modules and plugins used in the system.

When you are done with the upgrade on your local system, you can replace your productive installation with the local installation. 


Doing an update on a local or second system has the major advantage that your productive page is only offline for a few minutes and you can take as long as you want for the upgrade.

However, as an update can take a long time you must make sure that no new content is being added to the page once you have taken a backup of all files and the database. Otherwise, restoring the backup might delete changes made in the meantime.

To shorten the maintenance time of the page you could take another backup of database and files on the day, you are performing the upgrade of productive system. Take care, that you are doing all steps according to the guide, to prevent any mistakes.

New directory permissions since CONTENIDO 4.10.0

Since CONTENIDO version 4.10.0 you have to set chmod permission 755 instead of 777. PHP must access the files as owner. Please respect also the owner permissions (chown) for your directories.

Checks before upgrade

Upgrading to another version of CONTENIDO can change the systems behaviour. Thus, modules and plugins must be checked. Please have a look for compatibility of all plugins you are using.

Create a backup of filesystem and database

The very first step of a upgrade is the backup of ALL existing files of your web page (including all clients with their uploads and so on) in the filesystem and of course the whole database. 


It is highly advisable to make a backup before you attempt the upgrade. If anything goes wrong you might lose your content and without a backup it will be impossible to retrieve it again. Backup the whole filesystem and the complete database and don't lose it!

Download and unzip latest version of CONTENIDO

Get a copy of the latest download release archive from the website Do not use other sources for downloads! Unzip the archive to a destination of your choice on your computer.

Prepare client folder(s) for upgrade


If you are performing the upgrade on your productive system you should ensure that from now on all requests are redirected to a maintenance page or so, because the frontend now gets affected and would display errors.

Delete the following resources (if existing) in the client folder(s) of your installation:

  • dbfs.php
  • error.php
  • front_content.php
  • index.php

Replace previous system files

Rename all directories - except all client directories and the directory "data" by appending the suffix "_old" to the directory name.

Then upload all directories from your unpacked download archive in this directory.


If you have multiple clients or your client's directory name is not "cms" you have to copy the files of the folder "cms" of your download to each client folder. Take care, that individual project changes are not overwritten.


If you have multiple environments or your environment's directory name is not "production" you have to copy all files from download folder "production" to every environment folder. Take care, that individual project changes are not overwritten.

Executing upgrade interface

Open the upgrade web interface by visiting "setup/" of your installation. 


Once again make sure you have a copy of your database backupped because the database now gets affected.

Choose setup type "upgrade" and proceed with the upgrade. 


When you are asked for entering the database credentials you must use the same as the old installation. Otherwise the upgrade fails. 

Test backend login after upgrade

If the upgrade process was successful, try to login into the backend with your previous password. Please delete any content of your browser cache to avoid display problems.

If you encountered any problems during the update, please have a look at our support forum at Maybe other persons had the same problem and you can find a solution for it there.

Fixing usage of removed functionality

Every time an update removes deprecated functionality you must check your modules and plugins for outdated functionality. If you do not, backend and frontend will behave incorrectly.

If the version you are upgrading to has any removed outdated functionality you can check in the Changelog area. If you have some problems with plugins, please contact the plugin authors to advise you what to do on upgrading the system.

Cleaning up and finish upgrade

Once you have downloaded a local copy of the filesystem backup you can delete any folder which is suffixed with "_old". These folders are not needed any longer.

Deactivate maintenance mode if activated, your website now should be running with the new version. 

Replace productive installation with upgraded system

At the beginning of this guide we recommended you to do the upgrade local. The changes made to your system now must be transferred to the production system. You must replace all files in the filesystem and import the whole database.


Do not forget to set the write permissions for folders and files. You can check correct permissions in the system integrity check in the backend.

Restore an old installation on upgrade failure

To restore the old installation when upgrade failed you have to delete all directories, which are NOT suffixed with "_old" and remove that suffix from all directories. Additionally, you must overwrite the database with your backup.

Maybe it is necessary to delete your browser cache.

Modules of Example Client: Behavior if you upgrade your CONTENIDO version

Solved errors for modules of the example client weren’t respected at upgrade mode. The module directory remains in the state before your CONTENIDO update. Thus we prevent that your individual module modifications are overwritten. The up-to-date modules are located at setup/data/examples/data/modules of CONTENIDO directory structure. If you want to upgrade your modules of the example client, please overwrite the old module directories at your server with the new module directories. But please consider, perhaps you will lost your modifications.


Version notice

This is only relevant if you use CONTENIDO version 4.10.0 or newer

CONTENIDO configures automaticly "SMTP" as transport type for your mails. But before it works, you have to configure the login informations at backend. Please go to the menu item "System" and "Configuration" to configure your SMTP mail server. If you do not want to use SMTP as mail transport type, you can choose alternatively "PHP mail".