Updates and Setup

QUIQQER systems are maintained through package updates and setup workflows. Updates change installed package versions. Setup applies package metadata, database changes, permissions, events, settings, and other runtime definitions.

For installing or removing individual packages, see Package Management.

Before Updating

Prepare the system before changing package versions:

• create a database backup
• create a file backup of the installation and runtime data
• note the currently installed package versions
• check available disk space
• check PHP CLI memory limits for larger updates
• schedule a maintenance window for production systems
• make sure no manual changes are pending in generated files

Use the CLI for larger updates or when the web process has strict timeout or memory limits.

Core Commands

Run commands from the QUIQQER installation root.

./console update --check

Checks for available updates.

./console update

Runs the system update.

./console setup

Runs the setup workflow.

./console htaccess

Regenerates the Apache .htaccess file and includes etc/htaccess.custom.php.

See Console for more maintenance commands and calling patterns.

Package Setup

Packages can add their own setup logic through XML files and PHP setup classes. The setup workflow imports these package definitions into the installation.

Run setup after:

• installing a package
• updating a package
• changing package XML files
• changing permissions, menus, settings, events, widgets, or database definitions
• restoring a backup into a different environment

Setup routines must be safe to run repeatedly. If a setup run fails, inspect the logs before running manual database changes.

After Updating

After an update:

• run setup
• clear the relevant caches
• regenerate web server files when routing behavior changed
• open the administration interface
• check package-related backend areas
• check the public frontend
• inspect logs for update, setup, PHP, and web server errors

Keep the backup until the system has been verified and no rollback is needed.