Child pages
  • Upgrade from CONTENIDO 4.8 to 4.9

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


titleTrouble 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 local (or one 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.



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 ensure, that no new content is being added to the page once you have taken a backup of all files and the database. Otherwise, the replace of your local installation also would replace any content entered 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.

Checks before upgrade

Upgrading to another version of CONTENIDO can change the systems behavior. Thus, modules and plugins must be checked. Please have a look for compatibility of all plugins you are using. The author of the plugin must offer a version that works with version 4.9. Plugins of version 4.8 definitely do NOT work with version 4.9 because the plugin system was changed. Chains should work as before.

Verify that all languages of all clients have a configured language and a country code. The upgrade process will not proceed if it detects any language without a country and/or language code. Set these codes in the language administration of CONTENIDO by selecting a value for "Country" and "Language".

Create a backup of filesystem and database

The very first step of an 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, because the frontend now gets affected and will display errors.


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

Replace previous system files

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



If you have multiple clients or your clients 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. 



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 before to avoid display problems.


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

Moving configuration files

You have to move the configuration files stored in the root directory of your client to the folder data/config/ENVIRONMENT. Do not miss other local configuration files such as config.local.php and config.after.php!

If you changed configurations for the backend, you must apply them to the new configuration files in data/config/ENVIRONMENT. We recommend you to use the config.local.php, so you don't have to modify any core files.


Cleaning up and finish upgrade

Once you made sure that everything works correctly, 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.


titleto be done

The translation of this paragraph is still missing.