Changes

Update to UBIK 5.2 and configure plugin deployment

257 bytes removed, 29 October

* Ensure that an appropriate database backup is available according to the project's update procedure.

* Decide whether the plugins should be configured in the database or continue to be supplied through the Injection folder.

~~{{Note|The example used for this procedure starts with a UBIK® 5.0 database using the UBIK Interface CUI and MO plugins. The iCAL plugin is installed automatically as an embedded submodule of MO.}}~~

== Recommended update procedure ==

Save the changes. UBIK® Studio continues startup and updates and initialises the database. This may take one or two minutes.

~~{{Note|Do not interrupt database initialisation.}}~~

=== Verify the update ===

After initialisation has completed, verify the database version and the loaded plugins in '''View → Plugins'''.

{{Warning|: When plugins are supplied through the Injection folder, administrators must maintain the Injection folder on every relevant UBIK® Studio installation.}}

== Migrate from the Injection folder ==

# Verify that the configured plugins are loaded successfully.

{{Note|:The Injection folder can still be used in addition to the database-stored configuration, for example for custom plugins. Avoid deploying the same standard plugin through both mechanisms.}}

== Verification checklist ==

MHM

1,730

edits