NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #3220 most downloaded on Packagist
TYPO3 CMS Content Blocks - Content Types API | Define reusable components via YAML
Latest stable
2.4.10
Last release 2 months ago
22 Sep 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
136 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Full Changelog: https://github.com/nhovratov/content-blocks/compare/0.6.0...0.6.1
Full Changelog: https://github.com/nhovratov/content-blocks/compare/0.6.0...0.6.1
This release includes a breaking change :boom: :
This version requires the minimum TYPO3 version 12.4.11
This release includes a breaking change :boom: :
Content Blocks started as a new realm on top of TYPO3, which only new about its own defined Content Types. This led to confusion among users, who expected seamless integration between natively defined types and Content Blocks. In the first step, native types are now also converted to the so called ContentBlockData object. This is the object, which is available in the {data} variable and holds the {data._raw} and {data._processed} data of the current database row. This was e.g. needed in order to use Nested Content Elements in a unified way. If you used native types as nested child elements (or native page types), adjustments to Fluid might be necessary.
More dedicated caches were added for each aspect of Content Blocks. To create a new Content Type basically three steps are happening:
TableDefinitionCollection -> second level PHP cache of the object state.All these caches are stored in the group system. Flushing this cache means all these steps have to be repeated. The first step is the most expensive as it includes file system lookups and YAML parsing.
Backend Previews: In general, the backend view of TYPO3 is not completely cached. Expensive database lookups are done on every click in the backend. So it was for automatic relation resolving for Content Block data. If you had a preview for your slider or nested content, then this could take a while in case you had plenty of elements on a page. This result is now also cached and will only be resolved again when the Content Element changes. In my tests this approximately cut the loading time in half.
In the last version we introduced the possibility to define Nested Content and render it in the frontend. Now it is also possible to automatically create backend previews. These previews reuse the native grid templates so it looks and feels as if it was natively in TYPO3:
<f:render partial="PageLayout/Grid" arguments="{data: data, identifier: 'tabs_item'}"/>
Thanks to @DanielSiepmann for pioneering this feature.
A guide for the migration from Mask to Content Blocks is now available: https://docs.typo3.org/p/contentblocks/content-blocks/main/en-us/Migrations/Mask/Index.html
A guide on how to add custom groups is added: https://docs.typo3.org/p/contentblocks/content-blocks/main/en-us/Guides/AddingNewGroups/Index.html
As TYPO3 v13 approaches we needed a plan for the transition into the Core. This release is the first milestone of the roadmap. There will be one more version before the port for the Core patch begins. During this time, there will be no more features. After successfull merge into the Core (which is expected), we declare Content Blocks as stable version v1.0.0. The v13 and v12 version will be kept in sync from there on.
| Milestone | Date |
|---|---|
| Content Blocks v0.6 | 26.02 |
| Content Blocks v0.7 | 01.04 |
| Core patch | 01.04 - 23.04 |
| TYPO3 v13.1 | 23.04 |
| Review period | 23.04 - 14.06 |
| Patch merged latest | 01.07 |
| TYPO3 v13.2 | 02.07 |
| Content Blocks v1.0.0 | 02.07 |
And like always some bugfixes, documentation improvements and much much code refactoring along the way.
Nikita Hovratov - Content Blocks developer
Your coding agent can read these notes before it upgrades. Set up the MCP server →
[BUGFIX] Lift hard requirement for labelField type (#112) [BUGFIX] Add more foreign_* option as non-overridable (#110) [BUGFIX] Allow integers as item
[BUGFIX] Lift hard requirement for labelField type (#112) [BUGFIX] Add more foreign_* option as non-overridable (#110) [BUGFIX] Allow integers as item labels and allow to omit them (#108, #111) [BUGFIX] Expand searchable fields
[BUGFIX] Prevent PHP warning "iteration on nullable"
[BUGFIX] Prevent PHP warning "iteration on nullable"
This release in non-breaking :ok_hand:
This release in non-breaking :ok_hand:
This release comes with the feature of basic nested Content Elements :tada: special thanks to @DanielSiepmann :clap: Also, a guide was added on how to use the classic Fluid Styled Content Layouts.
The main focus of this sprint release was to harden the API and to provide small missing features like missing field types (special thanks to @PKuhlmay), localization of select items or the saveAndClose option.
Special thanks to @garvinhicking for digging into identifier replacement for displayCond :clap:
fields if foreign_table is definedAnd much more refactoring and documentation improvements.
Further contributers for this release. Thanks!
Nikita Hovratov - Content Blocks developer
The Database Analyzer will most probably want to remove some fields. This is fine and intended! The only thing you should look out for is the constell
The Database Analyzer will most probably want to remove some fields. This is fine and intended! The only thing you
should look out for is the constellation: Collection with foreign_table set. If you want to be able to reuse the
referenced table in more than one table or field (within the same Content Block), you should add the options
shareAcrossTables and shareAcrossFields to the Collection field respectively.
alternativeSql removed. Please use ext_tables.sql overrides instead.shareAcrossTables and shareAcrossFields.aggregateRoot option. This will be detected automatically.title and description can now be also set in EditorInterface.yamlAnd many more bugfixes, refactoring and documentation improvements.
[!!!][TASK] Automatic language keys for title and description simplified. The vendor and name do not need to be included anymore. See documenation
title and description simplified. The vendor and name do not need to be included anymore. See documenationenableImageManipulation renamed to extendedPalette. See documentationTYPO3/Seo is removed.label for FlexForm fieldsfieldControl and fieldWizard available for all field typesAnd many more bugfixes, refactoring and documentation improvements.
Nothing published for this version
type Select relations with foreign_table are now resolved recursively
Select relations with foreign_table are now resolved recursivelyRelation relations with foreign_table are now resolved recursivelyprefixType with value full and vendorNothing published for this version
Nothing published for this version
Enable TCA/Overrides for Content Blocks
Enable TCA/Overrides for Content Blocks
Fix caching issue for icons #25
Fixed icon path in classic mode.
Fixed icon path in classic mode.
Nothing published for this version
The first public TER release for Content Blocks! We've worked for 1 year to get to this state. Please try it out and send feedback to us. This will ev
The first public TER release for Content Blocks! We've worked for 1 year to get to this state. Please try it out and send feedback to us. This will eventually become the official system extension content_blocks for TYPO3 v13. As this is a beta version, be careful using it in production. Things may break in every new release. Have fun using Content Blocks!
One column per quarter.