Adding Missing Column in 8.3.0 Upgrade

This tutorial is over a year old and may not apply to your version of Concrete CMS.
Dec 13, 2017

Concrete CMS version 8.3.0 requires that you update to 8.2.1 before you can upgrade to 8.3.0. This is because the migrations need to run in a very precise order for 8.3.0, since it changes how some important underlying database tables are structured. This can cause a problem for sites that are on migrations passed 8.2.1, but aren't completely updated to 8.3.0.

If you are trying to update to 8.3.0 via composer or from a release candidate, and receive complaints about a missing cIsDraft column in the Pages table, run this command from your web root, when logged in over ssh or in terminal:

concrete/bin/concrete5 -n migrations:execute 20170803000000

This will create the cIsDraft column, and make sure that any existing page drafts are migrated to using this new column. This should allow the rest of the updates to work fine. After this, you can run

concrete/bin/concrete5 c5:update

to ensure that your database is fully up to date.

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.