v1.0.1

Release v1.0.1:

Align the ext_emconf.php dependency constraints with the dual TYPO3 v13 + v14 support already declared in composer.json.

• [FIX] Widen the ext_emconf constraints to the dual range (typo3 13.4.19-14.99.99, content_blocks 1.4.6-2.99.99). composer.json already declared ^13.4.19 || ^14.3 and ^1.4.6 || ^2.0. Only relevant to non-Composer (legacy) installs — Composer mode reads composer.json, and TYPO3 v14 skips ext_emconf via providesPackages.

v1.0.0

Release v1.0.0:

TYPO3 v14 support, the Content Blocks GUI now runs on both TYPO3 v13 and v14 (and content-blocks 1.x and 2.x) from a single, dual-compatible codebase.

• [FEATURE] Support TYPO3 v14 alongside v13 (composer: typo3/cms-* ^13.4.19 || ^14.3, friendsoftypo3/content-blocks ^1.4.6 || ^2.0)
• [FIX] Resolve SchemaMigrator from a fresh container so Collection child tables are created correctly on TYPO3 v14 (Doctrine DBAL 4)
• [FIX] Use the AsController attribute, available on both v13 and v14
• [FIX] Read content block translations via getAllTranslations() on content-blocks 2.x and getLanguageFile() on 1.x
• [TASK] Declare providesPackages so TYPO3 v14 skips the deprecated ext_emconf.php, which is kept for v13 and non-Composer (legacy) mode
• [TASK] Make the E2E suite dual-compatible (v14 renders modals as native ) and robust against cold-start flakes

Verified green on TYPO3 v13 (Composer), v14 and v13 legacy (non-Composer): unit, functional, phpstan, cs-fixer and the full Playwright E2E suite.

Includes all improvements from v0.4.0 (mandatory field validation #20, incompatible Basics filtering #19, independent pane scrolling #18, and extensive mutation-verified test hardening).

v0.4.0

Release v0.4.0:

• [FEATURE] Enforce and mark vendor/name/host extension as required; Record Types additionally require table and label field (fixes #20)
• [FIX] Hide re-use Basics incompatible with the content type, both in the Basics list and the field property dropdown (fixes #19)
• [FIX] Give editor panes independent scroll so the field configuration stays visible (fixes #18)
• [FIX] Keep table/typeField in Record Type YAML on update (fixes save schema error)
• [FIX] Scope field identifier uniqueness per table (Collection = new scope, Palette/Tab transparent)
• [FIX] Block Save & Close on missing required fields without a stuck "Saving..." overlay
• Set extension state to beta
• Extensive mutation-verified E2E, functional and unit test hardening

v0.3.0

Release v0.3.0:

• Fixing broken legacy mode, broken save action and database update schema, thx to @mkrappitz for reporting in #14
• Refactor property parent path structure
• Fix close handling after upload
• Update Content Blocks dependency

v0.2.0

Release v0.2.0:
Refactoring extension development, move all necessary scripts, tests, and TypeScript files to this extension repository to enable contribution.

• Fix support for legacy setup destination extension detection, thx to @mkrappitz mentioned in #14.
• Fix toggle all in select mode. fixes #13, thx to @richardkrikler for pointing out this issue

v0.1.2

Bugfix Release 0.1.2:

• fixes #8 add support for Pallets, fix not shown Collection properties, thx to @baderpaul.
• Update README.md to reflect new location of Content Blocks GUI in TYPO3 backend. fixes #11 thx to @richardkrikler

Bugfix Release 0.1.1

Bugfix Release v0.1.1

• No Content Block creation possible in non composer mode, thx to @mkrappitz fixes #1
• Saving existing Basic creates duplicate, thx to @nhovratov fixes #2
• Checkbox "items" property saved incorrctly, thx to @nhovratov fixes #3
• prefixType must not be saved with empty string, thx to @nhovratov fixes #4
• Add soft fail for currently not supported FileType handling, thx to @baderpaul
  and @nhovratov #7
• Increase dark mode support, thx to @jonaseberle

Detailed commits you can find in development repo.

Initial Release

Initial Release of the Content Blocks GUI. This is an early alpha state.