Kajona

Systemupdate from 3.2.x to 3.3.0

Preparations

In general, the update should be processed the same way as the other updates.

This includes to backup the templates, the config.php, the global_includes.php and, if given, pictures and downloads.

In addition, the following steps should be taken:

• Make a backup of the complete system (including the database)
• If enabled, disable gzip-compression using module system -> system-settings
• During the update, start with the module system

Updateprocedure

With Kajona 3.3, parts of the database-structure are rebuilt. This is necessary since the hierarchy is now created more strictly according to our guidelines.
Thats's the reason for the module-system updater to verify if there are modules remaining having invalid records in the database.
If there are found any invalid records, the update stops the execution printing the following error-message:

Please upgrade other modules before.
Aborting update!

Above the message, a list of erroneous ids is printed, showing the records remaining invalid.
To update those records, the update-procedures of the other modules should be executed right now-
Afterwards, the update of the system-module can be continued.

Note: In rare cases it could happen, that even after running all module-updates the system-update complains about invalid records. This indicates that there are orphaned records in the system-table, no longer assigend to any record. To identify those records, use the debug-skript "systemtablevisualizer" provided by the debug-package. Alternatively, post a message at the board in order to get support.

Common hints

Up from Kajona 3.3, even more elements support their own templates.
The advantage is the increased flexibility when adopting the layout of elements. There's no longer the need to change php-files, all changes can be made in the template.

As a consequence, the changes made to classes have to be migrated to the new templates (this has to be done only once).

This affects the following elements:

• Paragraph (in some cases Absatz before)
• Image (in some cases Bild before)
• Row (in some cases Zeile before)
• Imagelightbox

All of those elements render their layout via a new template.

global_includes.php

Since Kajona 3.3 the constant KAJONA_WEBPATH can be used in own JavaScript files. Therefore the constant must be defined before other JavaScript files are loaded. If you modified the file /portal/global_includes.php in your project, please update it to the one in the release 3.3.

Templates

Since changes to the templates couldn't be avoided completely, it may be possible that the templates used need to be updated or matched with the sample templates. This is particularly for the module postacomment.