How to manually upgrade Concrete CMS (5.7)

This is a community-contributed tutorial. This tutorial is over a year old and may not apply to your version of Concrete CMS.
May 22, 2015
  1. First, log into your Concrete CMS site as an administrator
  2. Log into your server's control panel and backup the database (or the entire site if you wish)
  3. Download a new zip of concrete, extract it, rename the concrete folder inside it to something like concrete_new, zip that up and upload it next to the existing concrete directory
  4. Unzip the uploaded zip of the new concrete_new directory
  5. Rename the existing concrete folder to something like concrete_old, and the concrete_new to just concrete (you're swapping them over)
  6. Immediately visit /index.php/ccm/system/upgrade and perform the upgrade

After upgrading you can then delete the concrete_old folder and concrete_new.zip file from your server as they are no longer needed.

Although not covered in the video, it is often suggested that you turn off caching on your site, clear the cache and then turn it back on after the upgrade is performed.

How to manually update concrete 5.7 video:

Recent Tutorials
Customize locale icons
Oct 29, 2024
By myq.

How to customize locale (language region) flags

Concrete CMS Caching Guide
Oct 16, 2024

An overview of types of caching in Concrete and considerations when using them.

Redirect all requests to HTTPS
Oct 9, 2024
By myq.

How to follow best practices for a secure web

Upgrade Concrete versions 9.3.1 and 9.3.2
Sep 10, 2024
By myq.

How to get past a bug in versions 9.3.1 and 9.3.2 that prevents upgrading the Concrete core through the Dashboard

How to use Composer with Marketplace extensions
Aug 22, 2024

Composer can be used to manage third-party extensions from the marketplace

Controlling Google Tag Manager Tags Based on Concrete CMS Edit Toolbar Visibility
Aug 13, 2024

This document provides a step-by-step guide on how to control the firing of Google Tag Manager (GTM) tags based on the visibility of the Concrete CMS edit toolbar. It explains how to create a custom JavaScript variable in GTM to detect whether the edit toolbar is present on a page and how to set up a trigger that ensures GTM tags only fire when the toolbar is not visible. This setup is particularly useful for developers and marketers who want to ensure that tracking and analytics tags are not activated during content editing sessions, thereby preserving the accuracy of data collected.

Improvements?

Let us know by posting here.