Skip to content

Upgrade from i9 to i11

In this tutorial you will learn how to upgrade from any version of imperia 9 to imperia 11.

Step 1: Receive new license data from the vendor#

Get your license key for imperia 11 at our support desk. In this process we will also create an account for you on our docker registry: Create support ticket here.

Step 2: Update editorial system to imperia 9.2#

A direct update from imperia 9.0.x or 9.1.x to imperia 11 is basically possible. However, we recommend to take an intermediate step and update to imperia 9.2.15 first. Please follow the steps of the Update Guide.

Step 3: Upgrade editorial system to imperia 11#

Now install imperia 11 and follow the Update instructions again. Please notice the following exception:

If you update the database schema after the update, pass the --auto parameter to extend the database and remove obsolete tables. The complete script call is the following:

perl /var/www/imperia/dev/site/bin/site_doctree_admin.pl -U --auto

Step 4: Rebuild database#

For the update, the database must be rebuilt once. Execute the site_rebuild_db script:

perl /var/www/imperia/dev/site/bin/site_rebuild_db.pl -t -b

Step 5: Insert Regkey file#

Copy the regkey.bin file you received from pirobase imperia gmbh into the site/config directory.

Step 6: Enter license data#

Enter your imperia 11 license key. (You can get the license key from the support desk of pirobase imperia gmbh)

Set up imperia 11#

Upgrade instructions for imperia 10#

Please also refer to the Upgrade instructions for upgrading from imperia 10 to imperia 11.

LDAP connection#

The LDAP connection in imperia 10 has been completely revised.

After the database upgrade, as well as after any changes to the group structure in your LDAP or in case of problems, you should replicate the LDAP data to imperia user management. To do this, run the following script:

perl site/bin/site_replicate_um.pl --backend=LDAP

Note

With the additional option --debug you create a more detailed output of the replication script.

By setting the environment variable LDAP_DEBUG to a true value, you activate informative debug output in all areas of imperia.

The format of the configuration file site/config/LDAP.conf has changed slightly. The installer automatically adapts the file to the new format. The system variables UMLIGHT_PLUGIN and DATABASE_STORAGE_PLUGIN are no longer needed. imperia will automatically set the new system variable UM_PROVIDERS to "LDAP" if LDAP authentication is enabled in your installation.

Role rights management#

The most extensive API change in imperia 10 is the user and group management API.

However, the old class files Roles.pm, Users.pm and Groups.pm are intentionally not touched by the installer and continue to work for the most important read accesses to the user and group data.

Nevertheless, you should adapt existing Perl code to the new API. See Hitchhiker's Guide To The New User Management in imperia 10 in site/docs/UM-i10.txt for more information. The Perl code adapted to the new API will usually be shorter, easier to read and more stable.

Self-written Plugins/Perl-CodeIncludes/Controller must be adapted if necessary.

Compatibility layer#

Note

Please note that the compatibility layer is only equipped with limited functionality to facilitate the switchover.

  • If imperia 11 is installed via an existing imperia 9 system or i9 via an existing i8 system, a so-called "compatibility layer" is also installed.
  • This compatibility layer still interprets some of the system conf variables that no longer exist in imperia 10 or 9.
  • This means among other things that project scripts can continue to function.

Dashboards#

In imperia 9 personalized dashboards are not adopted. The reason for this is an adaptation of the dashboards in order to be able to extend the configuration options of the widgets.

New IWE version#

CK-Editor has been updated to Verion 4. The old version 3 is still included and can be used.