The application is updated by the administrator in the Settings → Updates tab. Updates are downloaded from the vendor's server. New releases are installed with one click (auto-installer, usually without FTP). Files are uploaded via FTP during the program's first installation; for updates, technical support is useful when the server doesn't allow the application to overwrite its own files. If the downloaded package doesn't have an auto-installer, the application will show instructions for uploading via FTP.

Downloading updates requires an active licence (the same one that unlocks saving in the application). The manufacturer's server provides the version list only for a key assigned to this installation's domain. Once the update entitlement stored in the key has expired, the new version button shows Locked, with the reason shown below the version number and when hovering over the button with the cursor.

With a licence with updates until a date, what counts is the version's publication date (shown next to each version on the list): the licence covers versions published before the entitlement ends, not newer ones. The program keeps working - you just won't be able to download newer releases until you renew the entitlement (a new key from the provider, see the licensing chapter). It's best to install the last update from your entitlement period before it ends: the manufacturer's server usually only provides the latest release, so after that date it may no longer show the older one.

Automatic checks and notifications

The application automatically checks for updates - you no longer need to go into settings every time:

  • after you log in (when you open the application),
  • periodically while the application remains open,
  • when you return to the browser tab (if some time has passed since the last check).

When a new release appears, the administrator sees a short notification ("Update available - version X.Y.Z is ready to install") with a Show button that opens Settings → Updates straight away. The notification appears once per version (it won't nag you every time you log in) - you'll get a new one for the next release.

If a new version can't be installed (e.g. the update entitlement has expired), the notification says so directly: "Version X.Y.Z is available, but cannot be installed: …" along with the reason. When updates are unavailable because of the licence key (missing key, unrecognised key, revoked, assigned to another domain, or unknown to the server), the administrator gets a single Updates unavailable warning with an explanation - further ones only once the problem disappears and returns.

New version indicator

Regardless of the notification, when a newer version is available, the administrator sees a red dot on the gear icon (⚙) in the top menu, and after opening settings - the same dot next to the Updates tab. The dot disappears automatically once the latest version is installed. The indicator (and the notification) are visible only to administrators.

Checking available versions

  1. Click the cog icon (⚙) → Updates tab.

Development version. If the application is running in development mode (using code directly from the repository), update checks are disabled: there is no red dot or notification, and the tab clearly states that you are using a development version.

  1. Click Check for updates. You will see:
    • Installed version - the version running on the server,
    • Code version - the version of the application files,
    • Available versions - a list of newer releases with a Changelog for each.

Versions are installed one at a time - only the button for the next version is active. Further versions become available once the previous one has been uploaded.

Task Manager: Updates tab with a list of versions and an install button.
Updates tab: the version on the server, newer releases and a changelog.

Downloading the package

  1. Click Download next to the first available version.
  2. A backup warning will appear - before updating, back up the database and the attachments folder (uploads/). Confirm to continue.
  3. The server will download the package and verify its checksum (SHA‑256). What happens next depends on the package type:
    • Package with auto-installer - an Install button will appear (described below). You don't need to upload anything via FTP.
    • Package for manual upload - the browser will save a .zip file to your disk (if needed, you can download it again using the Save package (.zip) button) and show FTP instructions.

One-click installation (auto-installer)

For releases that support auto-installation, you don't need FTP:

  1. Once downloaded, click Install.
  2. A progress bar will appear (“Installing…”) showing the stages: database migrations → file copying → finalisation.
  3. Once finished, the button changes to Refresh application - click it to load the new version (you can also refresh the page with Ctrl/Cmd + Shift + R).

The installer doesn't touch your data - it skips includes/config.php, uploads/, storage/ and logs/, and runs any necessary database migrations itself. It's still worth having a backup (as the warning shown during download reminds you).

Note: the progress bar is fully “live” only from the point when the installed version already includes this feature. When installing from an older version, the progress bar may jump forward in stages.

Installation via FTP (packages without an auto-installer)

If the package does not support automatic installation, the application will display manual upload instructions:

  1. Back up the database and the uploads/ folder (if you have not already done so).
  2. Extract the downloaded .zip file.
  3. Connect to your hosting server via FTP and upload the contents of the package to the application directory, overwriting the existing files.
  4. DO NOT overwrite (keep your own copies):
    • includes/config.php - configuration and secrets,
    • uploads/ - attachments and avatars,
    • storage/ - working data,
    • logs/ - logs.
  5. Refresh the application in your browser (Ctrl/Cmd + Shift + R), then click Check for updates again to confirm the new version number.

If the release includes database changes, the instructions for that release (changelog / release notes) will specify any additional steps. If in doubt, restore the backup first and contact the provider.

Frequently asked questions

  • "Could not connect to the update server" - check your internet connection and whether the licence is valid. The version list is only provided to installations with a valid key. The program adds the technical description of the connection error (e.g. "Could not resolve host…") in brackets after the word "details" - useful for your hosting's technical support.
  • "You have the latest version" - there's no release newer than the one installed. This message only appears when the server has recognised the key - if there's a key problem, you'll see one of the messages below.
  • "This installation has no licence key…" - enter the key in Settings → Advanced → Licence; without it, the application doesn't even ask the server about versions.
  • "The update server doesn't recognise the licence key…" - the key's signature doesn't match the manufacturer's server (the key is damaged or from another source). Enter the key you received from the provider or contact them.
  • "This installation's licence key isn't in the update server's database…" - the key is valid, but the manufacturer's server doesn't know it. The provider needs to register it or issue a new one.
  • "Licence key… has been revoked…" - the provider has revoked this key (usually after issuing a new one). Enter the new key.
  • "Licence key is assigned to another domain…" - the key was issued for a different address than the one the program is running on. Ask the provider for a key for this domain.
  • “Version X.Y.Z is available, but it cannot be installed: your update entitlement ended on DD/MM/YYYY…” - the version was published after your update entitlement ended. The program keeps working; to install it, renew your entitlement (a new key from your provider). The list usually won't show an older version from within your entitlement period either - the vendor's server only provides the latest release.
  • “The server is missing the PHP “zip” extension…” - without this extension, the application can't unpack the package. Enable it in your hosting panel (PHP settings → extensions) and try again. The application checks this before downloading the package.
  • The version didn't change after uploading - make sure the files were uploaded to the correct directory, then refresh the page bypassing the cache (Ctrl/Cmd + Shift + R).
  • Write permissions message (e.g. "Failed to overwrite file … (write permissions?)") - the server doesn't allow the application to save its files. Fix the permissions of the application directory in the hosting panel or via FTP, and retry the update. Migrations that have already run won't be repeated.
  • “The application server returned an unexpected response (HTTP …)” - the program on your server failed before it could respond (while checking for or downloading an update). The cause is recorded in your hosting's PHP error log - pass it on to technical support.
  • “Locked” button - the reason appears under the version number (and when you hover over the button): either you need to install an earlier version first, your licence no longer covers this update (e.g. your update entitlement has ended), or the release doesn't have a valid publisher signature.