Updates · TMKAN

Legal Center

License Terms

Service Plans

What's new

Every new version is yours while your licence is genuine: install it safely after a backup, and know what to do if it stops.

Updates, backups and add-ons

While your licence is genuine, every new version of TMKAN is yours. Your system checks for one every day, tells you when it arrives, and installs it only when you press the button, after a full backup.

Before you start

The permission Modify Maintenance & Updates, and the master password.

A quiet time: while the update runs, your team cannot use the system.

Know when an update arrives

Your notifications bell says “A system update is available”. To check yourself:

Open Settings › Maintenance & Updates.

Press Check now on the Updates card.

The Updates card, with a new version

Install the update

On the Updates card, press Update the system. You see the new version, its size and its Changes.

Press Start. The system checks that the update is signed by TMKAN, is newer than yours and fits on your server. Nothing changes yet.

Press Update the system and give the master password.

Wait for the seven steps, from Checking the update to Finish, and do not close the page.

At Updated to version …, press Reload now.

The first stage, with the Start button

The seven steps, running

Updated, with Reload now

If an update stops

If…Do…

It stopped before changing your files, and you see “Update failed. The system was put back as it was”Try again later. Nothing changed.

It stopped while updating the database, and the system stays paused on The update stopped part wayPress Restore the previous copy, confirm, and give the master password: the backup taken before the update brings everything back.

The update stopped part way

Good to know

Updates go only to an active licence, at the address it is tied to. Your system licence has no end date, and updates need no hosting or support plan.

An update only goes forward. The backup it takes first stays in Settings › Backup, marked Pre-update.

An update never touches your .env file or your backups.

Could not check for updates names its reason, such as “Central could not be reached”. It never says your system is up to date when it could not ask.