Before this version, updating went like this: no way to learn about a new version, download it yourself, upload it over FTP, and only then click "Apply". Four of the five steps happened outside the engine — which is why sites stay for years on a version whose bugs were fixed long ago.
Updates from the panel
- The engine checks the server itself and shows a new-version notice on the overview as a blue bar: the site works, nothing is on fire.
- A person decides. The check only asks; without a click the engine installs nothing — an update changes the code of a live site.
- Downloads are verified by size and SHA-256 fingerprint; without a fingerprint the update is not installed at all. Files being replaced are backed up first. Configuration, uploaded files and the database are left untouched.
- The database is a separate click, with a separate backup: between swapping files and changing the schema you need time to check that the site still opens.
What leaves the site
An update check sends the domain name, the engine version and the PHP version to the server. Nothing else. This is stated right in the settings, next to the server address field. Checking can be turned off: Settings → General → Updates → Check for updates → never.Protection
- "What protects the site" as a checklist on System health: how forms are signed, how passwords are stored, whether the site runs over HTTPS, whether debugging is off, whether code execution in uploads is blocked, whether a file snapshot exists, whether database backups are made. Where something needs fixing, the row links there.
- Scheduled database backups: how often, in days, and how many to keep. Off by default — the engine has no right to decide this for the owner.
Panel and site
- Bulk actions moved below the list in all remaining sections; permanent deletion asks for separate consent.
- A hundred panel fields got accessible names for screen readers.
- The image placeholder was transparent in three of the four themes.
- The "Call me back" button did not appear for a week: the block was failing silently.
How to update
No new core migrations. If you are updating from 0.9.5 or earlier, read the 0.9.6 notes first: that release has migrations, and after installing the files you need to click "Update" in the panel.---
Links
- Release page — notes, archive size and SHA-256 checksum.
- Discussion on the forum (in Russian).
- All NEX1ON releases.