Content Publisher v13 – New UI, improved workflows and strict compatibility
A lot has happened in the latest releases. With v13 of Content Publisher, we have not only tidied up the technical side of things, but also set the strategic course for the future. From the basic architecture to fine UI details for editors – here is an overview of the development from version 13.0.0 to the current status.
13.0.0: Full focus on TYPO3 v13
Let's start with the most important technical change: we have decided to discontinue dual version support. In other words, this version only supports TYPO3 v13.
To ensure long-term quality and maintainability, we have removed legacy code for backward compatibility, which will provide greater stability in the long run. This means that parallel use on older versions such as TYPO3 v12 is no longer technically possible.
Before installing this update, your system must already be running TYPO3 v13.
13.0.1: Strengthening the foundation
With 13.0.1, we focused directly on code hygiene and bug fixing. We fixed various type errors and removed warnings about outdated PHP functions. In addition, a bug related to image resolution was corrected and the database dumps for local testing were updated.
The result is code that runs more strictly and cleanly, prevents crashes, and works best with modern PHP versions.With 13.0.1, we focused directly on code hygiene and bug fixing. We fixed various type errors and removed warnings about outdated PHP functions. In addition, a bug related to image resolution was corrected and the database dumps for local testing were updated.
The result is code that runs more strictly and cleanly, prevents crashes, and works best with modern PHP versions.
13.1.0: A breath of fresh air for editors
This update really stands out!
The Publish Overview module has been given a new UI and new functions. The revised layout ensures a better visual hierarchy. Colours and icons in the page tree make it easier to find your way around during daily operations.
The highlight, however, is the improved language handling: languages and translations can now be published separately and filtered. This allows individual language versions to be released without affecting the main page or other languages.
Want to go live with the English translation, but still need to refine the German version? No problem.
13.1.1 & 13.2.0: Optimised workflows and logic
In versions 13.1.1 and 13.2.0, we have made significant changes to the process logic to make your workflows more secure and flexible:
- Synchronous deletion: When a parent element is published, the deletion of an associated translation is now automatically carried over. This prevents data deadwood. At the same time, we have loosened the technical requirements for translations, which makes working more flexible.
- Secure sequence: With version 13.2.0, we ensure that the deletion of a translated page is complete and published before a new translation goes live. This prevents data conflicts.
- More tolerance: Content Publisher is now more robust in ‘Connected Mode’. It no longer reports unfulfilled dependencies simply because inconsistent content elements exist.
The visual appearance has also been adjusted: layout issues in the Overview module have been fixed and dialogue boxes (modals) are now easier to read thanks to added line breaks.
13.2.1 & 13.2.2: The finishing touches
The latest updates cover details and compatibility.
In 13.2.1, we have removed a harmless but annoying warning message that appeared when the hideRecordsDeletedDifferently function was active. Although this warning was harmless, it led to unnecessary flooding of the error logs.
With 13.2.2 (and preparatory 13.0.2), we come to the most important technical point for integrators: we have completed the bug fixes for the schema API and restored the ability to overwrite templates in the Publish Files module. This allows developers to customise the design again.
View into the backend of the Content Publisher modules




