Updating CoreInto
Updates are signed, installed from the admin area in a minute, and never touch your own templates or modules.
Before you update#
Read the release notes of the new version, and take a database backup from Settings > Database Backups or your hosting control panel. Keep a copy of configuration.php.
From the admin area#
- Open Utilities > Update CoreInto. It shows the version you run and the latest release.
- Press the button to install. CoreInto downloads the release, checks its signature against the release key built into CoreInto, keeps a zip of every file it replaces under
storage/updates, and installs the new files. - If the release changes the database, CoreInto asks you to run the Database Update at
/upgrade. Confirm, and it brings the tables up to date.
While a database update is pending, the automation waits, so nothing runs half-updated. The client area keeps working throughout.
Automatic update checks#
The automation asks the licence server for new releases every day and shows the answer as "Last checked" on Update CoreInto and on Automation Status. It never installs anything by itself: you decide when to update.
Updating by hand#
Download the release zip from your service page at system.coreinto.com, upload its files over the old ones (keep configuration.php and storage/), then open /upgrade in the admin area to run the database update.
Your own templates and modules#
Updates replace only CoreInto's own templates (studio, classic and horizon) and modules. Your own template folders and add-on modules are never touched. When a release adds pages to the client area, compare your template with the new Classic and copy the new pages across.
Frequently asked questions
Is it safe to update?
Every release is signed, and CoreInto installs it only when the signature matches. A copy of the replaced files is kept. Take a database backup first all the same.
Do updates cost extra?
No. Every release is included while your plan is active.