When an update is available, users with the permission to update Craft will see a badge in the CP header. Clicking on that badge will take you to a page that shows the release notes of all the available updates.
You can get to that page at any time by clicking the “Check for updates” link in the CP footer as well. Whenever you go to the page, whether Craft thinks updates are available or not, the page will clear its cache and re-check for available updates.
At the top of the page there is an “Update” button. Clicking that will initiate Craft’s self-updating process.
For one-click updates to work, your craft/app folder and all its enclosed files and folders must be writable. The exact permissions you should use depend on the relationship between the user that Apache/PHP is running as and the user who actually owns the craft/config folder.
Here are some recommended permissions depending on that relationship:
- If they are the same user, use
- If they're in the same group, then use
- Otherwise, use
The “Update” button on the Updates page has a context menu with an alternative “Download” option. Clicking on that will give you the same
Craft.zip file you could have gotten by downloading Craft from craftcms.com.
When the zip has finished downloading, you can manually update your Craft install by replacing the old
craft/app/ folder with the new one.
If you’re manually updating a live site, we recommend you follow these instructions to minimize your site’s down time:
- Rename the
craft/app/folder in the release to
craft/app-new/to the craft folder on your server, alongside the old
app-new/is done uploading, your FTP client may have uploaded the
app-new/folder with different permissions that what your
craft/app/folder currently has. If so, make sure app-new matches what
- Rename the old
- Point your browser to your Craft Control Panel. If the update needs to run any new database migrations, you will be prompted to proceed with a database update. Click “Finish up” and let the database updates run.
- Delete the