TYPO3 14.3.1 and 13.4.29: Maintenance releases with important bug fixes
Have the article read aloud.
TYPO3 14.3.1 and 13.4.29 are pure bugfix releases. Both without a database update, both with improvements that are noticeable in everyday use.
On May 12, 2026, the TYPO3 core team released two maintenance releases: TYPO3 14.3.1 LTS and TYPO3 13.4.29 LTS. Both are pure bugfix releases. Database updates are not necessary, only a clearing of all caches can be useful.
If you are on one of the two LTS lines, you should update as soon as possible.
The following lists are an excerpt. I am concentrating on the changes that have the greatest impact on integrators and editors in their everyday work. You can find the complete release notes here: Release Notes TYPO3 14.3.1 and Release Notes TYPO3 13.4.29.
The most important bugfixes in 14.3.1
For editors
- Drag and drop in the page module usable again. Since TYPO3 13 the page module uses native drag and drop. This meant that scrolling with the mouse wheel during a drag operation no longer worked in most browsers. On long pages, you could hardly move content elements to the desired position in a meaningful way. There is now an auto-scroll handler: as soon as you reach the edge of the visible area when dragging with the mouse, the page scrolls automatically. The closer you are to the edge, the faster.
- Fixed avatar upload in the user settings. In certain inline contexts (keyword "partitioned field names", i.e. IRRE fields with prefix segments), the JavaScript returned a different field name than the corresponding HTML element. Result: The avatar upload dialog closed without comment because the DOM lookup failed. Profile pictures can now be uploaded again.
- Page creation wizard respects the insertion position again. If you selected "after" (i.e. as a sibling of the reference page) when creating a new page, the wizard still placed the page within the reference page. "After" was silently demoted to "within". Now the new page ends up where you wanted it to be. Also pageTSConfig and permissions are evaluated against the correct parent page.
- Page Creation Wizard and Livesearch in a higher modal. Both opened in a modal with the "medium" preset (800x520 pixels). This is wider than high and does not fit well with content that grows downwards (page wizard steps, long hit lists). Both modals now use a higher variant and are therefore much more pleasant to use.
For integrators
- Site route matching for slugs identical to the site path. Concrete example: Site A has the base /, Site B has the base /t3/. Site B contains a subpage with the slug t3. The full URL is therefore /t3/t3/. Until 14.3.0, this URL was assigned to the wrong site because the routing logic determined the appropriate path share from the left instead of the right. Fixed by changing from strpos to strrpos.
- Recommended memory limit raised to 256 MB minimum, 512 MB recommended. The install tool check previously reported 64 MB as minimum and 128 MB as recommendation. The values are now at the level that a modern TYPO3 setup needs anyway. If you are still on old hosting tariffs, you should talk to your host now at the latest.
- Multibyte characters in TypoScript identifiers. Umlauts and other multibyte characters already worked in TypoScript values before. However, in the identifier itself, e.g. with over = bar, the parser silently discarded such lines. Now umlauts also work in identifiers and in multi-line comments.
- tree variable always available in TypoScript condition matcher. Conditions like [123 in tree.rootLineIds] did not work as soon as no rootline could be determined (typical case: DataHandler operations on orphaned records in CLI context). Instead of returning false, the Symfony Expression Language threw a SyntaxError for the unknown variable tree. Now tree is always present, with empty defaults if no rootline can be determined.
- Cache lifetime over 24 hours works again. The internal default cache timeout has been increased from 24 hours to 1 year. Background: If a cache tag did not have an explicit lifetime, TYPO3 fell back to this default. Since the minimum of all tag lifetimes applies at the end, the page cache was effectively capped at 24 hours, even if you had explicitly configured longer values. With the new default, your configuration now really works.
- Page cache is invalidated when changing the project path. Relevant for rolling release deployments where the TYPO3 project is under changing paths (e.g. releases/2026-05-12/). Previously, the page cache still delivered the old content after a release switch. The project path is now included in the cache identifier, which means that a fresh cache is automatically created after a path change.
- Content areas are resolved cleanly during iteration. If you iterate through a content area collection via foreach, you will now reliably get back finished ContentArea objects and no longer half-resolved ContentAreaClosure instances. Relevant for all those who work with content blocks or iterate content areas in Fluid.
- Scheduler tasks more reliable. Two related bugs from the Scheduler refactoring in TYPO3 14 (Scheduler now uses DataHandler and TCA): Firstly, tasks that did not need a backend user themselves, but then updated themselves, crashed with an exception because no $GLOBALS['BE_USER'] existed. A CommandLineUserAuthentication is now automatically generated in the CLI context. Secondly, every single task run created a new sys_log entry. The log was full of routine entries. Logging for these task updates is now disabled.
What's in 13.4.29?
13.4.29 is significantly slimmer, but includes the most important corrections from 14.3.1. Highlights:
- Drag and drop in the page module can be used again. Identical to the fix in 14.3.1: Auto-scroll handler when dragging over long page views.
- Site route matching for slugs identical to site path. Multi-site setups in which a subpage slug has the same path segment as the base of another site are now assigned to the correct site (see detailed example above at 14.3.1).
- Multibyte characters in TypoScript identifiers. Umlauts in keys such as over = bar are no longer silently discarded.
- Empty reference output in TypoScript is avoided. If you referenced an empty content object in TypoScript and wanted to set values in the reference (pattern lib.bar =< lib.foo followed by lib.bar.value = ...), you got an empty output. The ContentObjectRenderer resolved the identifier of the reference instead of its content type. The empty object can now be filled correctly via the reference.
- IRRE and file toggle switch with invertStateDisplay fixed. Since the change in TYPO3 13, which automatically activated invertStateDisplay for all hidden fields, the hide/show toggle was unusable for IRRE and file relations. The switch read the display state of the inverted checkbox instead of the actual stored value. Now data-invert-state-display is correctly taken into account and toggling works again.
Again, no database update necessary, just clear caches.
Classification: What does this mean for you?
Both releases are not spectacular versions, but solid maintenance work on the code. Exactly what an LTS line is all about.
Anyone who actively works with the TYPO3 backend will benefit noticeably. The drag-and-drop problem in the page module was particularly annoying because it directly affected the daily editing workflow. The avatar upload fix also sounds small, but has caused frustration wherever IRRE fields with nested inline structures are used.
For integrators, the increase in the recommended memory limit is particularly noteworthy. 256 MB as a minimum and 512 MB as a recommendation are not a cosmetic update, but a clear signal to the hosting landscape. However, this should not be a problem in modern environments.
The TypoScript multibyte fix and the improved site routing are inconspicuous, but exactly the kind of bugfix that suddenly explains in a live project why a strange URL or special character constellation is causing problems.
My advice: update promptly, plan to empty the caches, check briefly in the backend. That's all you need to do.
BackDo you have a question or want to discuss the topic?
In the Community Hub for TYPO3 you can exchange ideas with other TYPO3 users. And if you don't want to miss any new articles: The TYPO3 Newsletter comes once a month, without spam.
