▲ How to update NEX1ON properly stengt

The engine updates from the admin panel, without FTP: it downloads the archive, checks its fingerprint, backs up the database and replaces the files. Nothing is installed until you press the button.

Before updating

• Licence key: enter it under "System → Updates → Licence". Without a key the engine shows what is new but does not download updates from the panel.
• Read the release notes on the releases page: they say whether anything must be done by hand. Skipping several versions? Read the notes for each one you skipped.
• Download a fresh database backup to your computer ("Backups and transfer → Database backups"). The engine makes its own backup too, but a copy that lives on the same hosting will not help if the hosting fails.

Updating

1. Open "System → Updates → Engine" and press "Check for updates".
2. Read what changed and press "Download and install".
3. The engine then goes step by step: downloads the archive, checks size and fingerprint, backs up the database, sets aside the files it replaces and puts the new ones in place. Your settings, uploaded files, themes and modules are not touched.
4. After the files are replaced, the database updates by itself: backup first, then the table changes. If that did not happen, press "Back up and apply" on the same page.

Translations of installed languages are updated at the same time from the catalogue. If that fails, you can update them later under "System → Languages".

If something goes wrong

• A migration stopped — the database stays as it was before it, and the backup is under "Database backups".
• The site stopped answering after the files were replaced — the update page puts the previous files back by itself. Keep the recovery key it shows: it is valid for 6 hours, and if the panel does not open, enter it at /nx-recover.php on your site. Recovery restores files, not the database.

Modules and themes

"System → Add-on catalogue" shows which installed modules and themes have a newer version (marked "Update available"). If a module update changes tables, make a database backup first.

More in the help articles "Updating the engine" and "Backups". If it did not work, post here the version you updated from and the lines from the error log.