Skip to content

Upgrade from i10 to i11

In this tutorial you will learn how to upgrade from any version of imperia 10 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 11#

Follow the steps in the Update Guide.

Step 3: Rebuild database#

Note

You only need to perform this step if you are updating from imperia 10.2 or an earlier imperia 10 version.

When switching from imperia 10.2.3 to a higher version, the database must be rebuilt once. However, the minimal rebuild, which is activated with the parameter -m, is sufficient here. Execute the site_rebuild_db script:

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

Step 4: Insert Regkey file#

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

Step 5: 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#

Create Hermes configuration file#

Note

This update instruction is only necessary if you are updating from imperia 10.1.x or an earlier imperia version.

Since imperia 10.2.0, the administrator must create a configuration file for Hermes (site/config/hermes.conf). The administrator can define several Hermes Workers in the configuration file so that the Hermes service can perform the tasks faster by parallel processing. To divide the tasks into Hermes-Worker, follow the example in site/config/hermes.conf.sample and adapt the format.

You can use the following script command to automatically create the configuration file. However, all Hermes tasks are not yet divided into separate workers.

Script call on UNIX systems:

perl /var/www/imperia/dev/site/bin/site_hermes_plugins_list.pl -g -q -i Monitor\|Analyzer

Script call on Windows:

C:\Strawberry\perl\bin\perl.exe C:/imperia/dev/site_hermes_plugins_list.pl -g -q -i Monitor\|Analyzer

Extending the Apache web server configuration#

Note

This update instruction is only necessary if you use the Apache web server and imperia under mod_perl.

Add the following variable to your Apache-Conf or vHost file in the Perl block:

$ENV{IMPERIA_BASE_DIR} = "/var/www/imperia/dev";

The path /var/www/imperia/dev represents the root directory of your imperia system. Replace the path accordingly.

Customize IWE Configuration#

Since imperia 10.2.2, customized IWE configuration files have a slightly different format. So if you are using a custom configuration for the WYSIWYG editor (CK editor), you need to remove this line, which was previously necessary, from the configuration:

config.customConfig = '/imperia/js/components/iwe2/default_config.js'

Install CryptX#

To enable the push notifications feature that has been available since imperia 10.4, you must meet 2 requirements: CryptX must be installed and SSL encryption must be set up.

Install CryptX: You have to install the Perl module "CryptX". Unfortunately, this module is not included in the package managers (apt-get or yum) and must be installed via Cpan.

For Unix and Mac it is best to use the package manager "cpanm". An installation guide for cpanm can be found at metacpan.org. Then install the module with the following command:

cpanm CryptX

Alternatively, you can install the package directly via cpan:

sudo perl -MCPAN -e 'CPAN::install CryptX'

Under Windows, open the CPAN client of Strawberry-Perl and install the CryptX module via the GUI.

Activate new module design#

imperia 11 features a new standard view for slot, flex and block modules. The new view is automatically changed as long as the view is not explicitly specified in the module call.

If you set the view manually, you can either delete the view parameter or explicitly set it to the boxd view.

Here are some examples of the different module calls:

<!--INSERT_SLOTMODULE:INDEX=102:VIEW=boxd.html:DND=1:JS_OPERATIONS=1-->

<!--INSERT_FLEXMODULE:INDEX=31:VIEW=boxd.html:DND=1:JS_OPERATIONS=1:VALIDCODES=2019-->

<!--IMPERIABLOCK:INDEX=3:VIEW=boxd.html:DND=1:JS_OPERATIONS=1-->

Add icons and descriptions to modules#

In order to display a meaningful icon and a description text when adding new modules, these must first be added in the module administrations for slot and flex modules. The tagging of the modules is also configured here.

Tagging and description text is entered directly in the header of the module. Here is an example for a video module:

DESCRIPTION: Video
HELPTEXT: Video-Modul for YouTube  or movingimage
TAG: embed
LOAD:AJAX
  • With DESCRIPTION the title of the module is given as usual.
  • With the new variable HELPTEXT you can describe the module in more detail.
  • With the new variable TAG you can enter one or more tags (comma separated).

Directly below the detail area of module editing, you can upload an icon for the module: