Version 4.4 introduces user content submissions for Tailor, brings Vue components to the frontend, completes the database-driven themes story for cloud deployments, adds translated page URLs and content blocks for multisite, and adds inline snippets for content editors.

Version 4.3 of OctoberCMS ships a broad set of features across the frontend, the backend, and developer tooling. The document form design brings the Tailor editor layout to every plugin, partials as components introduces attribute-bag patterns to CMS templates, view transitions enable native animated page navigations, and the release adds an official debugbar, a new theme translation editor, and October Boost for AI-assisted development.

Version 4.2 of OctoberCMS introduces a significant modernization of the frontend architecture. The administration panel has been upgraded to Vue 3 and the JavaScript layer has been migrated to native ES Modules (ESM), eliminating the need for build tools like Webpack or Laravel Mix.

Version 4.1 of OctoberCMS contains feature improvements to the platform, including better Twig support in the CMS.

The following is an instructional guide on how to upgrade your 3.x OctoberCMS installation to the latest version 4.0

Version 3.7 of OctoberCMS contains feature improvements to the platform, including new currency tools, theme blueprints and improvements to the resizer.

Version 3.6 of OctoberCMS contains some major improvements to the platform. Some of these features were scheduled to be released in v4.0 of OctoberCMS, however, since Laravel 11 includes some compatibility changes, we need to wait for those changes to mature. This means we've included the new features in the v3.6 as a backwards compatible release.

Version 3.5 of OctoberCMS contains various feature improvements, including site groups, new navigation types and stacked popups.

Version 3.4 of OctoberCMS introduces snippet features and framework upgrade support.

Version 3.3 of OctoberCMS contains introduces additional styling options to the admin panel along with white-labelling.

Version 3.2 of OctoberCMS contains extra features, including tabbed repeaters and tailor permission improvements.

Version 3.1 of OctoberCMS hallmarks the stable version of this major release. It can be safely used in production environments.

This guide is intended to help with the changes related to the Bootstrap 5 upgrade as the client-side framework used by October CMS v3 and above.

The following is an instructional guide on how to upgrade your 2.x OctoberCMS installation to the latest version 3.0

Version 2.2 of OctoberCMS contains several features that we just couldn't wait to share with you.

OctoberCMS Version 3.0 Alpha is available early for developers that want to take advantage of the latest Laravel features. This version has been upgraded to use Laravel v9.0. During the alpha phase, OctoberCMS v2 and v3 will be developed in parallel.

Version 2.1 of OctoberCMS hallmarks the stable version of this major release. It can be safely used in production environments.

The following is an instructional guide on how to upgrade your 1.x OctoberCMS installation to the latest version 2.0

Due to overwhelming support from the community, October CMS is updating its foundation framework to the latest Long Term Support (LTS) release. As a result, there are some new requirements to run October and some code changes required.

There is a serious vulnerability found in older builds of October CMS. The issue affects all websites and upgrading to the latest version is highly recommended.

Due to overwhelming support from the community, October CMS is updating its foundation framework to the latest Long Term Support (LTS) release. As a result, there are some new requirements to run October and some code changes required.

There are some important security fixes to the October platform that address vulnerabilities to the Media Manager and Asset Manager tools.

An inconsistency in the File model has been corrected, as a result the getPublicPath method will no longer return a relative path.

There have been some improvements to the internals of the NavigationManager class which may cause an exception between Build 398 and Build 408.

Some users are experiencing an error after upgrading. The error shown is: No supported encrypter found. The cipher and / or key length are invalid.

There is an issue that exists between MySQL versions that use a "strict mode" and the version of Laravel used by OctoberCMS prior to the stable release.

The save() method of a model will change in the next build (273+). This is an undocumented feature and it should be rarely used, however, some areas of the core files used it and just in case this pattern was copied, we want to announce this change.

Recently it was discovered that the groupBy() method in Laravel is flawed, not at any fault of Laravel itself but because of the inability of all SQL drivers, except MySQL, from counting grouped records.

Build 115 has renamed all instances of "Email" to "Mail". This will leave some harmless artifacts behind.