Showing results 751 to 775 of 1561

Task
Accepted Stale Frontend TYPO3 CMS 15

#110265 Support "Forwarded" HTTP header

The @Forwarded@ HTTP header is a standard header and replaces/combines the well known but only de-facto standard X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Proto headers.

TYPO3 does not support this header currently but there is no real reason aside from slightly higher parsing complexity.

Author Mathias Brodala
Assigned to Benni Mack
Created 07/22/26, 14:36
Updated 07/22/26, 14:52
Bug
Under Review Stale DataHandler aka TCEmain TYPO3 CMS 11

#102336 Add support for localizing n:1 relations

When localizing a parent-child relationship (IRRE) from the parent side, DataHandler correctly creates the localized children and also sets their “parent” relation (n:1) field to the localized parent.

But when localizing a parent-child relationship from the other (child) side (or localizing any record containing n:1 relations in general), DataHandler does not set these (n:1) relations to point to the localized record (instead, they point to the L=0 record). This is not a consistent behavior and at least breaks extbase, too.

The current behaviour is also problematic in the following use case: When having a parent-child relationship with 100 parents each owning 100 children. In addition to the “parent” (n:1) relation, these children also contain any other n:1 relations to different models. Now after localizing a “parent”, for each “children” these additional n:1 relations must be modified manually by an editor to point to the localized record (which is impossible when dealing with larger datasets).

My suggestion is, when localizing a record containing any n:1 relation, DataHandler should behave like this:

  • Lookup if there is any localized version of this (n:1) relation target
  • If there is, set the relation to the localized records uid
  • If there isn’t, set the relation to the original records uid (as a fallback)
Author Jan Kornblum
Created 11/07/23, 10:08
Updated 07/22/26, 10:16
Feature
New Stale scheduler

#110251 Scheduler task form for Symfony Commands (schedulable commands) should show the defined icon by ModifySchedulerTaskWizardListener

I have several Symfony Commands (schedulable commands) which have an event listener for the new ModifyNewSchedulerTaskWizardItemsEvent to override the default task icon. For the task wizard this works great. A huge usability improvement. I can also rename the task category.

<?php

declare(strict_types=1);

namespace Vendor\MyPackage\EventListener;

use TYPO3\CMS\Core\Attribute\AsEventListener;
use TYPO3\CMS\Scheduler\Event\ModifyNewSchedulerTaskWizardItemsEvent;

final class ModifySchedulerTaskWizardListener
{
    #[AsEventListener('ext-my-extkey-modify-scheduler-task-wizard')]
    public function __invoke(ModifyNewSchedulerTaskWizardItemsEvent $event): void
    {
        // Modify existing wizard items
        $wizardItems = $event->getWizardItems();
        foreach ($wizardItems as $key => $item) {
            if (isset($item['header']) && $item['header'] === 'Myextkey') {
                $item['header'] = 'My ext key';
                $event->addWizardItem($key, $item);
            }
            if (isset($item['title']) && str_contains($item['title'], 'myextkey:my-command')) {
                $item['icon'] = 'mimetypes-x-tx_myextkey_task_my_command';
                $event->addWizardItem($key, $item);
            }
        }
    }
}

For the usability it would be great and consistent, if the Scheduler task form should also show the defined icon from the event listener and not the default one.

Author Tee Ohh
Created 07/21/26, 15:12
Updated 07/21/26, 15:12
Bug
New Stale Workspaces TYPO3 CMS 12

#85284 Workspace shows unchecked sectionIndex in preview

If you uncheck sectionIndex (Show in Section Menus) of a tt_content it will still be shown in the Workspace preview.

It looks like the WS preview doesn’t care about sectionIndex=0 and show it anyway.

Also true for the Menu sections in WS Preview: The tt_content will be in the list even with sectionIndex=0

Author Patrick Gaumond
Created 06/15/18, 20:41
Updated 07/20/26, 13:27
Bug
Under Review Stale Workspaces TYPO3 CMS 13

#108361 Error when deleting a nested inline element in a workspace

The problem has been observed in to projects from different agencies.

Prerequisits:
  • Custom content element, which allows to create nested content via an inline field (e.g. Accordion with accordion items)
  • Accordion item record, which allow to add various content elements as relation via an inline field

Basically, this is: tt_content.inline_field ➡️ custom_table.inline_field ➡️ tt_content records

The attached patch for ext:styleguide shows the TCA of the custom content element. It is required to reproduce the problem with current main.

How to reproduce:
  • In live workspace, create a content element of CType styleguide_accordion
  • While editing the content element, add one “Accordion Items” inline record
  • For the new inline record, add 3 content element (e.g. CType header)
  • Save the content element
  • Switch to a workspace
  • Edit the content element
  • Delete one of the created CType header elements
  • Save the content element

Behavior in TYPO3 13.4

  • Two error messages are shown, stating that a delete placeholder can not be edited and that the edit form could not be loaded

Behavior in TYPO3 14.0

  • PHP undefined array index exception is thrown for EditDocumentController::createBreadcrumb()
  • Two error messages are shown, stating that a delete placeholder can not be edited and that the edit form could not be loaded (is shown, when undefined array index bug is fixed).

The reason for the two error messages is, that EditDocumentController::processData() evaluates the redirect URL GET parameters wrong (R_URL_getvars), because the function does not respect the visible state of the deleted element from a workspaces perspective (t3ver_state === -2).

Author Torben Hansen
Assigned to Torben Hansen
Created 11/29/25, 13:36
Updated 07/18/26, 09:03
Feature
Under Review Stale Install Tool

#110189 Add SQLite performance mode option to the installer

Currently, when choosing SQLite as the database driver during installation, TYPO3 creates the database file using SQLite’s out-of-the-box defaults.

These defaults are conservative and not well suited for web application workloads — most notably, the default DELETE journal mode causes significantly more disk I/O than the WAL (Write-Ahead Logging) mode, and several other PRAGMA settings (synchronous, busy_timeout, cache_size, foreign_keys, temp_store) are left at their compile-time defaults rather than values commonly recommended for this use case.

This patch adds a new option to the database driver selection step of the installer: “SQLite (performance mode, WAL)”, alongside the existing “Manually configured SQLite connection” option.
When selected, the following PRAGMAs are applied via the connection’s initCommands at the time the database file is created:

PRAGMA auto_vacuum = INCREMENTAL PRAGMA journal_mode = WAL PRAGMA synchronous = NORMAL PRAGMA busy_timeout = 5000 PRAGMA cache_size = -20000 PRAGMA foreign_keys = ON PRAGMA temp_store = MEMORY

Note that the order of these PRAGMAs matters: auto_vacuum only takes effect on a still completely empty (0-byte) database file.
Any other PRAGMA or write operation, including switching to journal_mode = WAL, initializes the file header and silently turns any subsequent auto_vacuum change into a no-op. auto_vacuum is therefore applied first.

These recommendations are based on the widely referenced SQLite tuning guide at https://briandouglas.ie/sqlite-defaults/, which is also linked from TYPO3’s own blog post on using TYPO3 with SQLite for small projects (https://typo3.com/blog/using-typo3-for-small-projects).
This is a pure opt-in addition — the existing “Manually configured SQLite connection” option remains completely unchanged, so there is no behavior change for existing installations or workflows.

Author Michael Staatz
Created 07/12/26, 10:58
Updated 07/17/26, 04:44
Task
Author Ayke Halder
Created 07/16/26, 12:51
Updated 07/16/26, 12:53
Task
Under Review Stale Backend User Interface TYPO3 CMS 14

#108357 Streamline icons in setup module

  • Use empty icon, if an option is not available (like in records).
  • Move detail view icon after action icons (like in users).
  • Use actions-cog for site setting
Author Daniel Windloff
Assigned to Daniel Windloff
Created 11/28/25, 11:05
Updated 07/15/26, 07:50
Bug
Needs Feedback Stale Performance TYPO3 CMS 14

#109180 Editing a record in TYPO3 v14.2.0-dev takes much longer than in TYPO3 v13 LTS

(context for me: cpal.ch, opening concert program 2020 – Mendelssohn en intimité, this is a custom extension, own TCA with multiple IRRE)

Website in v14-dev, PHP 8.3.30

(current dev state)

1. DDEV xdebug off
2. Dev console / Network empty
3. Content > Records > Click on pencil to edit
4. Call to edit?token=… took 15.60 seconds

Same website in v13.4.26

(switch back project to branch for v13, composer update, resync all files and DB from production)

1. DDEV xdebug off
2. Dev console / Network empty
3. Web > List > Click on pencil to edit
4. Call to edit?token=… took 464 ms

Switching back to v14.2.0-dev

1. DDEV xdebug off
2. Install Tool to perform all suggested migrations (DB), my extensions are compatible with both v13 and v14, same source code
3. Web > List > Click on pencil to edit
4. Call to edit?token=… took 16.11 s
5. Close and again
6. Call to edit?token=… took 15.82 s

Bottom-line

Open to analysing anything, just tell me.

Author Xavier Perseguers
Created 03/06/26, 13:45
Updated 07/15/26, 07:41
Task
Under Review Stale Themes TYPO3 CMS 14

#109708 Re-export theme_camino demo data

Since #109687 changed the export to omit default data,
the camino theme should be exported again to account for
these improvements.

Author Benjamin Franzke
Created 04/24/26, 14:13
Updated 07/15/26, 07:39
Bug
Under Review Stale Workspaces TYPO3 CMS 13

#110142 Workspace: l18n_parent change cannot be published

Via workspaces a change in tt_content.l18n_parent cannot be published. A change of that field is being deliberately blocked in EXT:workspaces/Classes/Hook/DataHandlerHook.php (see array $keepFields) to prevent losing localization by accident, I guess.

A valid scenario of changing that field is this though: user wants to decouple two content elements and thus switch from “connected mode” to “free” or “mixed” mode. Or vice versa.

Steps to reproduce:

  1. have a page with a translated CE (connected mode!)
  2. switch to a workspace
  3. decouple the translated record from its translation origin (that’s basically: l18n_parent=X => 0)
  4. see that change in the workspace diff view
  5. publish it
  6. nothing changed. still connected mode.
Author Philipp Kitzberger
Created 07/02/26, 09:03
Updated 07/12/26, 08:32
Bug
New Stale Backend API TYPO3 CMS 13

#110183 Record for BE preview ignores current language

Records loaded for BE previews by the Record API always use the default language instead of the selected language. As a result e.g. previews which show fields of related records always contain content from the default language instead of translations.

Internally the Context must be adjusted based on the PageLayoutContext and passed to RecordFactory::createResolvedRecordFromDatabaseRow() consistently.

Author Mathias Brodala
Created 07/10/26, 11:47
Updated 07/10/26, 11:47
Feature
Under Review Stale FormEngine aka TCEforms

#24019 Enhance IRRE to allow new records to appear at the top

The current implementation always adds new IRRE records after all or after an already existing record.
There are some cases, when the ordering of the list is not relevant or if you sort the records e.g. by date, the newest one should be displayed at the top.
If the list of records is very long, the only visual feedback you get is a growing scrollbar, so some people might click “Create new” several times until they realize the that something happend.

Solution: add new config option “newRecordPosition” in the appearance section
prototype already has actions to make a “Insertion.Top”, so the only big change is to let IRRE use that function and reorder the list of records right.

How to test:
- install the extension “irre_tutorial” and import the sample t3d to get something to work on
- add this to your extTables.php to create all new relations at the top:

t3lib_div::loadTCA(‘tx_irretutorial_1ncsv_hotel’);
t3lib_div::loadTCA(‘tx_irretutorial_1nff_hotel’);
t3lib_div::loadTCA(‘tx_irretutorial_mnasym_hotel’);
t3lib_div::loadTCA(‘tx_irretutorial_mnattr_hotel’);
t3lib_div::loadTCA(‘tx_irretutorial_mnmmasym_hotel’);
t3lib_div::loadTCA(‘tx_irretutorial_mnsym_hotel’);

$GLOBALS[‘TCA’][‘tx_irretutorial_1ncsv_hotel’][‘columns’][‘offers’][‘config’][‘appearance’][‘newRecordPosition’] = ‘top’;
$GLOBALS[‘TCA’][‘tx_irretutorial_1nff_hotel’][‘columns’][‘offers’][‘config’][‘appearance’][‘newRecordPosition’] = ‘top’;
$GLOBALS[‘TCA’][‘tx_irretutorial_mnasym_hotel’][‘columns’][‘offers’][‘config’][‘appearance’][‘newRecordPosition’] = ‘top’;
$GLOBALS[‘TCA’][‘tx_irretutorial_mnattr_hotel’][‘columns’][‘offers’][‘config’][‘appearance’][‘newRecordPosition’] = ‘top’;
$GLOBALS[‘TCA’][‘tx_irretutorial_mnmmasym_hotel’][‘columns’][‘offers’][‘config’][‘appearance’][‘newRecordPosition’] = ‘top’;
$GLOBALS[‘TCA’][‘tx_irretutorial_mnsym_hotel’][‘columns’][‘branches’][‘config’][‘appearance’][‘newRecordPosition’] = ‘top’;

If you want to check one level deeper, you can add something like this:
$GLOBALS[‘TCA’][‘tx_irretutorial_1ncsv_offer’][‘columns’][‘prices’][‘config’][‘appearance’][‘newRecordPosition’] = ‘top’;

Note: there will be an error on saving records on the page “m:n asymmetric combo”, but this has nothing do to with the patch.
See http://bugs.typo3.org/view.php?id=15996 for that.

For the pending documentation:
= doc_core_api (4.5) =

Chapter: Table Configuration Array, $TCA
Part: [‘columns’][fieldname][‘config’] / TYPE: “inline”

Field: appeareance:
newRecordPosition (string)
Values: ‘top’, ‘bottom’ – default: ‘bottom’
Defines where the new record is inserted in the list of records.
(issue imported from #M16350)

Author Andreas Kießling
Created 11/11/10, 12:12
Updated 07/09/26, 14:59
Bug
New Stale System/Bootstrap/Configuration TYPO3 CMS 13

#110159 RTE YAML loader should support safe custom tags like !reset

TYPO3’s YAML loader currently rejects Symfony YAML custom tags such as `!reset`.

Example (here for extending RTE Config):

imports:
  - { resource: "EXT:rte_ckeditor/Configuration/RTE/Default.yaml" }

editor:
  config:
    heading:
      options: !reset
        - { model: 'paragraph', title: 'Paragraph', class: 'ck-heading_paragraph' }
        - { model: 'heading1', view: 'h1', title: 'Heading 1', class: 'ck-heading_heading1' }
        - { model: 'heading2', view: 'h2', title: 'Heading 2', class: 'ck-heading_heading2' }

This fails with:

YamlParseException:
Tags support is not enabled. You must use the flag "Yaml::PARSE_CUSTOM_TAGS" to use "!reset"

*Expected behavior*
RTE YAML presets should allow safe custom tags such as `!reset`, or TYPO3 should provide another documented way to replace imported list values.

*Proposed solution*
Enable safe custom tag parsing for RTE YAML presets, for example using:

Yaml::PARSE_CUSTOM_TAGS

or document an official alternative for resetting imported arrays/lists in RTE YAML configuration. But I think the goal should be to stay YAML and Symfony compatible here.

Author Gabriel Kaufmann TYPOworx GmbH | NewMedia
Created 07/06/26, 12:30
Updated 07/09/26, 05:50
Bug
New Stale Extbase TYPO3 CMS 13

#94965 QueryResultPaginator override current limit/offset

Hi,

If I use the `QueryResultPaginator` with a `QueryResult` who has already a limit and/or an offset they are all overrided.
The correct behaviour has to take care of the current state of the `QueryResult` and paginate only the result without overriding the query.

Thanks,
Eric

Author Eric Chavaillaz
Created 08/23/21, 15:36
Updated 07/08/26, 08:48
Bug
New Stale Backend User Interface TYPO3 CMS 14

#110125 Not possible to add files in page creation wizard

We have a custom page type, where files are required.
The new page creation wizard allows to handle this nicely and avoid broken pages with no asset linked.
The required field is visible and required within the wizard. Clicking on the “Create new relation” button opens the file selection window.
But: Selecting a file does not do anything – meaning the file does not get added and creating the page is impossible as the field is required but it’s not possible to add a file.
There is no error in JS console but also no requests – not sure if there should be, but I would expect something to happen to be able to debug this.

Author f7media ka
Created 06/30/26, 14:49
Updated 07/03/26, 17:39
Bug
Needs Feedback Stale File Abstraction Layer (FAL) TYPO3 CMS 13

#110137 Image processing stores a 0-byte / invalid result as a successful ProcessedFile

Summary

When the image processor (GraphicsMagick/ImageMagick) does not produce a valid output but leaves a 0-byte file behind, TYPO3 treats the run as successful — it only checks `file_exists()`, never the file’s validity/size — creates a `sys_file_processedfile` record for it, and then serves that 0-byte file on every subsequent request.

A single transient processing failure therefore turns into a permanently cached, broken image until the processed-files cache is cleared or the original file changes. This is why it typically shows up as “images are sometimes broken, sometimes not”.

Trigger

The output is empty whenever the underlying CLI run fails after (partially) creating the target file. GM/IM does exactly this on a WebP encode error: it leaves a 0-byte target file.

A reliable, deterministic trigger is a WebP output whose width or height exceeds libwebp’s hard limit of 16383 px — GM/IM aborts with `width or height exceeds limit` but leaves a 0-byte file. In production the same empty output also occurs from transient failures under load (resource contention), which is the “sometimes” case.

Steps to reproduce

1. Put a source image wider than 16383 px into a storage, e.g. `fileadmin/wide.png` (17000×1000):

gm convert -size 17000x1000 xc:teal fileadmin/wide.png

2. Process it to WebP at original size (so the result is 17000 px wide → exceeds the libwebp limit):

   $file = $storage->getFile('/wide.png');
   $processed = $file->process(
       \TYPO3\CMS\Core\Resource\ProcessedFile::CONTEXT_IMAGECROPSCALEMASK,
       ['width' => '', 'height' => '', 'fileExtension' => 'webp']
   );

Actual result (TYPO3 13.4)

isProcessed       = 1
usesOriginalFile  = 0
name              = csm_wide_<hash>.webp
exists            = 1
size              = 0          <-- empty file
width / height    = 0 / 0

- A `sys_file_processedfile` row is created (width=0, height=0).
- A second `process()` call returns the same cached 0-byte file (no reprocessing) → the failure is sticky.
- The rendered `` points to a 0-byte `.webp` → broken image, permanently, until the processed-files cache is cleared.

Expected result

A run that did not produce a valid image must not be treated as successful and must not be persisted as a ProcessedFile. The invalid result should be discarded (so the next request reprocesses) and/or the original file used as fallback — a 0-byte file should never be cached and served.

Root cause

`TYPO3\CMS\Core\Resource\Processing\LocalImageProcessor::processTaskWithLocalFile()` decides success purely on file existence (TYPO3 13.4, ~line 69):

} elseif (!empty($result['filePath']) && file_exists($result['filePath'])) {
    $task->setExecuted(true);
    $imageInformation = GeneralUtility::makeInstance(ImageInfo::class, $result['filePath']);
    // ...
    $task->getTargetFile()->updateProperties([
        'width'  => $imageInformation->getWidth(),   // 0 for an empty file
        'height' => $imageInformation->getHeight(),  // 0
        'size'   => $imageInformation->getSize(),     // 0
        'checksum' => $task->getConfigurationChecksum(),
    ]);
    $task->getTargetFile()->updateWithLocalFile($result['filePath']);
}

A 0-byte file “exists”, so the task is marked executed/successful and the (zero) dimensions are stored without being validated. `FileProcessingService::processFile()` then persists it because the task reports success (TYPO3 13.4, ~line 78):

if ($task->isExecuted() && $task->isSuccessful() && $processedFile->isProcessed()) {
    $this->processedFileRepository->add($processedFile);
}

(`GraphicalFunctions::imageMagickConvert()` likewise returns the target as a result based on `file_exists()`, so the empty file reaches the processor as a “result” in the first place.)

Proposed fix

Validate the produced file before marking the task successful — the needed data (`ImageInfo`) is already available at that spot. In `LocalImageProcessor::processTaskWithLocalFile()`:

} elseif (
    !empty($result['filePath'])
    && file_exists($result['filePath'])
    && filesize($result['filePath']) > 0
) {
    $task->setExecuted(true);
    $imageInformation = GeneralUtility::makeInstance(ImageInfo::class, $result['filePath']);
    if ($imageInformation->getWidth() === 0 || $imageInformation->getHeight() === 0) {
        // produced file is not a valid image -> do not cache, retry next time
        $task->setExecuted(false);
        return;
    }
    // ... existing success handling ...
} else {
    // no valid processing result
    $task->setExecuted(false);
}

With `setExecuted(false)` the result is not persisted; the next request reprocesses and no broken file is ever served.

Author Benjamin Blanck
Created 07/01/26, 13:45
Updated 07/02/26, 09:09
Bug
Under Review Stale Backend API TYPO3 CMS 14

#110059 Redirection to deleted pages should be visible to contributors

Hello,

Actually the module “redirect” is not showing redirections linked to deleted pages to a contributor. Which doesn’t make much sense.

If the target is an hidden page or a non-existent one, the system will show the redirect to the user, but if the page is flagged as “deleted=1” no. Which then leads to the user thinking the redirect doesn’t exist, he create a new one, but the old one is still in place and it leads to a 404 in the frontend (page deleted, normal behavior)

First one is a disabled page, the contributor can see it, no issue.
Second one, is a page that doesn’t exist, the user can see it again, no issue.

If I log in as an admin, their is a third redirect, at the top, the one with a deleted page as a target:

If the user is a contributor, their is some access check compared to an admin. In this file: TYPO3\CMS\Redirects\Security\RedirectPermissionGuard:113:

We simply needs to set the third parameter “$useDeleteClause = true” to false.

I don’t see any issue to do that, since the system will still check if the user can see the page or not.
The bug is present at least since TYPO3 10, but it’s not a security issue, so it should be fix for TYPO3 13 and up? If I have time I’ll send a patch.

Author Ludovic Nogueira
Created 06/16/26, 05:45
Updated 06/30/26, 13:49
Task
Under Review Stale Backend User Interface TYPO3 CMS 14

#109799 Backend breadcrumb should show record uid again (pages and records)

*Description*
In older TYPO3 versions, backend breadcrumb labels included the uid, which allowed quick identification of the current page/record at a glance.
In TYPO3 v14, the breadcrumb label no longer shows this uid information.

This is not primarily about avoiding confusion between similar titles, but about restoring a fast and practical workflow: editors and integrators can immediately see and use the uid directly from the breadcrumb.

*Expected behavior
  • Backend breadcrumb labels should include the uid suffix again, e.g. About us [42], for both pages and records.

*Actual behavior*
Breadcrumb labels currently show only the title without uid.

Author Gianluigi Martino
Assigned to Gianluigi Martino
Created 05/08/26, 09:08
Updated 06/30/26, 06:15
Task
Under Review Stale Backend JavaScript TYPO3 CMS 14

#109062 Deprecate inline language labels (TYPO3.lang)

Author Benjamin Franzke
Created 02/22/26, 14:10
Updated 06/29/26, 08:25
Bug
New Stale Database API (Doctrine DBAL) TYPO3 CMS 13

#110091 Database schema is changed once an extension regfisters a page tsconfig file via ExtensionManagementUtility::registerPageTSConfigFile()

The database schema for tsconfig_includes changes from StringType (e.g. varchar(255)) to TextType, when at least one
item has been added to the select list via ExtensionManagementUtility::registerPageTSConfigFile().

That means the installations of extension like bootstrap_package that configure select items as in https://github.com/benjaminkott/bootstrap_package/blob/15.0.4/Configuration/TCA/Overrides/100_pages.php#L15 trigger a column change.

This is unfortunate, especially in sqlite environments, as it requires the entire table to be recreated via the sqlite table recreation pattern: https://github.com/doctrine/dbal/blob/73653de42d9836e4a00350afc697c5e7e31706f2/src/Platforms/SQLitePlatform.php#L693-L709

Ideally we should try to enforce a stable schema for core fields, where we know upfront, that the column type shall be TEXT.

See screenshot:

For sake of completeness, this is the full SQL that is presented to the integrator:

CREATE TEMPORARY TABLE __temp__pages AS SELECT uid, pid, tstamp, crdate, deleted, hidden, starttime, endtime, fe_group, sorting, rowDescription, editlock, sys_language_uid, l10n_parent, l10n_source, l10n_state, l10n_diffsource, t3ver_oid, t3ver_wsid, t3ver_state, t3ver_stage, perms_userid, perms_groupid, perms_user, perms_group, perms_everybody, SYS_LASTCHANGED, shortcut, content_from_pid, mount_pid, tx_impexp_origuid, sitemap_priority, doktype, title, slug, TSconfig, php_tree_stop, categories, layout, extendToSubpages, nav_title, nav_hide, subtitle, target, url, lastUpdated, newUntil, cache_timeout, cache_tags, no_search, shortcut_mode, keywords, description, abstract, author, author_email, media, is_siteroot, mount_pid_ol, module, l18n_cfg, backend_layout, backend_layout_next_level, tsconfig_includes, seo_title, no_index, no_follow, sitemap_changefreq, canonical_link, og_title, og_description, og_image, twitter_title, twitter_description, twitter_image, twitter_card FROM "pages"
Current value: "tsconfig_includes" VARCHAR(255) DEFAULT ''

DROP TABLE "pages"
Current value: "tsconfig_includes" VARCHAR(255) DEFAULT ''

CREATE TABLE "pages" (uid INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, tstamp INTEGER UNSIGNED DEFAULT 0 NOT NULL, crdate INTEGER UNSIGNED DEFAULT 0 NOT NULL, deleted SMALLINT UNSIGNED DEFAULT 0 NOT NULL, hidden SMALLINT UNSIGNED DEFAULT 0 NOT NULL, starttime INTEGER UNSIGNED DEFAULT 0 NOT NULL, endtime INTEGER UNSIGNED DEFAULT 0 NOT NULL, fe_group VARCHAR(255) DEFAULT '0' NOT NULL, sorting INTEGER DEFAULT 0 NOT NULL, rowDescription CLOB DEFAULT NULL, editlock SMALLINT UNSIGNED DEFAULT 0 NOT NULL, sys_language_uid INTEGER DEFAULT 0 NOT NULL, l10n_parent INTEGER UNSIGNED DEFAULT 0 NOT NULL, l10n_source INTEGER UNSIGNED DEFAULT 0 NOT NULL, l10n_state CLOB DEFAULT NULL, l10n_diffsource BLOB DEFAULT NULL, t3ver_oid INTEGER UNSIGNED DEFAULT 0 NOT NULL, t3ver_wsid INTEGER UNSIGNED DEFAULT 0 NOT NULL, t3ver_state SMALLINT DEFAULT 0 NOT NULL, t3ver_stage INTEGER DEFAULT 0 NOT NULL, perms_userid INTEGER UNSIGNED DEFAULT 0 NOT NULL, perms_groupid INTEGER UNSIGNED DEFAULT 0 NOT NULL, perms_user SMALLINT UNSIGNED DEFAULT 0 NOT NULL, perms_group SMALLINT UNSIGNED DEFAULT 0 NOT NULL, perms_everybody SMALLINT UNSIGNED DEFAULT 0 NOT NULL, SYS_LASTCHANGED INTEGER UNSIGNED DEFAULT 0 NOT NULL, shortcut INTEGER UNSIGNED DEFAULT 0 NOT NULL, content_from_pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, mount_pid INTEGER UNSIGNED DEFAULT 0 NOT NULL, tx_impexp_origuid INTEGER DEFAULT 0 NOT NULL, sitemap_priority NUMERIC(2, 1) DEFAULT '0.5' NOT NULL, doktype INTEGER UNSIGNED DEFAULT 0 NOT NULL, title VARCHAR(255) DEFAULT '' NOT NULL, slug CLOB DEFAULT NULL, TSconfig CLOB DEFAULT NULL, php_tree_stop SMALLINT UNSIGNED DEFAULT 0 NOT NULL, categories INTEGER UNSIGNED DEFAULT 0 NOT NULL, layout INTEGER UNSIGNED DEFAULT 0 NOT NULL, extendToSubpages SMALLINT UNSIGNED DEFAULT 0 NOT NULL, nav_title VARCHAR(255) DEFAULT '' NOT NULL, nav_hide SMALLINT UNSIGNED DEFAULT 0 NOT NULL, subtitle VARCHAR(255) DEFAULT '' NOT NULL, target VARCHAR(80) DEFAULT '' NOT NULL, url VARCHAR(255) DEFAULT '' NOT NULL, lastUpdated BIGINT DEFAULT 0 NOT NULL, newUntil BIGINT DEFAULT 0 NOT NULL, cache_timeout INTEGER UNSIGNED DEFAULT 0 NOT NULL, cache_tags VARCHAR(255) DEFAULT '' NOT NULL, no_search SMALLINT UNSIGNED DEFAULT 0 NOT NULL, shortcut_mode INTEGER UNSIGNED DEFAULT 0 NOT NULL, keywords CLOB DEFAULT NULL, description CLOB DEFAULT NULL, abstract CLOB DEFAULT NULL, author VARCHAR(255) DEFAULT '' NOT NULL, author_email VARCHAR(255) DEFAULT '' NOT NULL, media INTEGER UNSIGNED DEFAULT 0 NOT NULL, is_siteroot SMALLINT UNSIGNED DEFAULT 0 NOT NULL, mount_pid_ol SMALLINT DEFAULT 0 NOT NULL, module VARCHAR(255) DEFAULT '' NOT NULL, l18n_cfg SMALLINT UNSIGNED DEFAULT 0 NOT NULL, backend_layout VARCHAR(64) DEFAULT '' NOT NULL, backend_layout_next_level VARCHAR(64) DEFAULT '' NOT NULL, "tsconfig_includes" CLOB DEFAULT NULL, seo_title VARCHAR(255) DEFAULT '' NOT NULL, no_index SMALLINT UNSIGNED DEFAULT 0 NOT NULL, no_follow SMALLINT UNSIGNED DEFAULT 0 NOT NULL, sitemap_changefreq VARCHAR(10) DEFAULT '' NOT NULL, canonical_link CLOB DEFAULT '' NOT NULL, og_title VARCHAR(255) DEFAULT '' NOT NULL, og_description CLOB DEFAULT NULL, og_image INTEGER UNSIGNED DEFAULT 0 NOT NULL, twitter_title VARCHAR(255) DEFAULT '' NOT NULL, twitter_description CLOB DEFAULT NULL, twitter_image INTEGER UNSIGNED DEFAULT 0 NOT NULL, twitter_card VARCHAR(255) DEFAULT '' NOT NULL)
Current value: "tsconfig_includes" VARCHAR(255) DEFAULT ''

INSERT INTO "pages" (uid, pid, tstamp, crdate, deleted, hidden, starttime, endtime, fe_group, sorting, rowDescription, editlock, sys_language_uid, l10n_parent, l10n_source, l10n_state, l10n_diffsource, t3ver_oid, t3ver_wsid, t3ver_state, t3ver_stage, perms_userid, perms_groupid, perms_user, perms_group, perms_everybody, SYS_LASTCHANGED, shortcut, content_from_pid, mount_pid, tx_impexp_origuid, sitemap_priority, doktype, title, slug, TSconfig, php_tree_stop, categories, layout, extendToSubpages, nav_title, nav_hide, subtitle, target, url, lastUpdated, newUntil, cache_timeout, cache_tags, no_search, shortcut_mode, keywords, description, abstract, author, author_email, media, is_siteroot, mount_pid_ol, module, l18n_cfg, backend_layout, backend_layout_next_level, "tsconfig_includes", seo_title, no_index, no_follow, sitemap_changefreq, canonical_link, og_title, og_description, og_image, twitter_title, twitter_description, twitter_image, twitter_card) SELECT uid, pid, tstamp, crdate, deleted, hidden, starttime, endtime, fe_group, sorting, rowDescription, editlock, sys_language_uid, l10n_parent, l10n_source, l10n_state, l10n_diffsource, t3ver_oid, t3ver_wsid, t3ver_state, t3ver_stage, perms_userid, perms_groupid, perms_user, perms_group, perms_everybody, SYS_LASTCHANGED, shortcut, content_from_pid, mount_pid, tx_impexp_origuid, sitemap_priority, doktype, title, slug, TSconfig, php_tree_stop, categories, layout, extendToSubpages, nav_title, nav_hide, subtitle, target, url, lastUpdated, newUntil, cache_timeout, cache_tags, no_search, shortcut_mode, keywords, description, abstract, author, author_email, media, is_siteroot, mount_pid_ol, module, l18n_cfg, backend_layout, backend_layout_next_level, tsconfig_includes, seo_title, no_index, no_follow, sitemap_changefreq, canonical_link, og_title, og_description, og_image, twitter_title, twitter_description, twitter_image, twitter_card FROM __temp__pages
Current value: "tsconfig_includes" VARCHAR(255) DEFAULT ''
Author Benjamin Franzke
Created 06/24/26, 07:21
Updated 06/24/26, 19:53
Bug
New Stale FormEngine aka TCEforms TYPO3 CMS 14

#110095 TcaColumnsRemoveEmptyRelations behavior is too disruptive

The default behavior of the newly introduced feature to completely hide select fields (and others) in the backend form in case not selectable items can be shown is too disruptive. In case the debug-mode is not active, an expected field is simply missing in the backend form, leaving the user clueless and confused what actually happened.

Step to reproduce

  • new TYPO3 v14/v15 instance (not having filemounts or be_groups at all)
  • TYPO3_CONF_VARS/BE/debug is disabled (false)
  • create a new be_groups record
  • the fields “subgroup” or “filemounts” are simply not shown (the “filemounts” has wizard actions for creating new file mounts

Expectation

  • at least show a hint, why the field is not shown (like it’s done when having debuggin enabled)

Suggested Change

Instead of enforcing the disruptive change and that affected fields have to opt out (which also is a breaking change), I’d suggest to apply the opposite behavior:
Fields must actively opt in, in case the want to use that TYPO3 v14.2 feature.

Docs Reference

Author Oliver Hader
Created 06/24/26, 10:30
Updated 06/24/26, 10:44
Bug
Under Review Stale TYPO3 CMS 14

#110085 Backend login log entry has no IP address

Logging in to the backend writes a sys_log entry (type LOGIN, action LOGIN), but the IP field is always empty.

LogEntryRepository::writeLogEntry() reads the IP from the request’s normalizedParams, and if no request is passed it falls back to $GLOBALS[‘TYPO3_REQUEST’]. The login runs in an auth middleware that executes before that global gets set, so the fallback is empty too.

Steps to reproduce:

1. Log in to the backend.
2. Check the log entry:

OR via DB access

SELECT IP FROM sys_log WHERE type = 255 AND action = 1 ORDER BY uid DESC LIMIT 1;
Author Jan Stockfisch
Assigned to Jan Stockfisch
Created 06/22/26, 14:40
Updated 06/23/26, 11:57
Epic
Under Review Stale

#97387 Configurable Password Policies

In order to provide strong defaults in regards to password security, TYPO3 will be able to validate user passwords against configurable password policies. This feature will increase the general security for TYPO3 users by providing a default password policy. Also TYPO3 as a CMS would be inline with recommendations on password security from the german BSI.

  • TYPO3 will ships with a default password policy
  • TYPO3 uses the default password policy for all scopes (backend and frontend user passwords)
  • The default password policy can be extended
  • It is possible to define custom password policies
  • TYPO3 will by default only support 2 scopes (BE and FE user passwords), but can be extended to support user defined scopes (e.g. in order to validate custom password fields for tables other than be_users and fe_users)

Technical implementation

A password policy is defined by a set of validators (not Extbase validators). If a password policy consists of multiple validators, they are chained. A Password checked within a password policy must match all configured and active validators.

The PasswordPolicyValidator class will provides a function to validate a given password based on the current password policy for the current scope. The validation result (true/@false@) will be returned and potential validation error messages can be retrieved from the PasswordPolicyValidator instance.

Validators

Validators for usage in a password policy must implement the PasswordValidatorInterface or extend the AbstractPasswordValidator class. Besides validation logic, a validator must also be able to return an array of strings with password requirements (e.g. “minimun length x chars”) in order to provide human readable password requirements. In case of a failed validation a validation error message can be definied.

Validators can be excluded for certain actions (e.g. no current password check for password of new users). Available actions are definied globally in the class PasswordPolicyAction.

Password Policy Configuration

Password Policy configuration is located in LocalConfiguration.php as shown below:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['passwordPolicies'] = [
    'default' => [
        'validators' => [
            \TYPO3\CMS\Core\PasswordPolicy\Validator\CorePasswordValidator::class => [
                'options' => [
                    'minimumLength' => 8,
                    'upperCaseCharacterRequired' => true,
                    'lowerCaseCharacterRequired' => true,
                    'digitCharacterRequired' => true,
                    'specialCharacterRequired' => true,
                ],
                'excludeActions' => [],
            ],
            \TYPO3\CMS\Core\PasswordPolicy\Validator\NotCurrentPasswordValidator::class => [
                'options' => [],
                'excludeActions' => [
                    \TYPO3\CMS\Core\PasswordPolicy\PasswordPolicyAction::NEW_USER_PASSWORD,
                ],
            ],
        ],
    ],
];

$GLOBALS['TYPO3_CONF_VARS']['BE']['passwordPolicy'] = 'default';
$GLOBALS['TYPO3_CONF_VARS']['FE']['passwordPolicy'] = 'default';

Password Policies can globally be disabled (e.g. for development environment) by setting the BE/FE password policy to an empty value in AdditionalConfiguration.php

→ see https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Feature-97388-ConfigurablePasswordPolicies.html

JavaScript module and API (TYPO3 backend only)

In order to provide instant feedback for users entering a password, a general JavaScript module needs to be developed, which validates a password when it is entered into a password field. The JavaScript module can be used for either password fields in FormEngine or regular password input fields (e.g. setup module or install tool) if possible.

Example:

A new backend route (similar to the slug suggest route) will use the configured password policy based on the given scope. Since custom password validators may use backend logic (e.g. check password against a deny-list), a client/server integration as described is required and has to be discussed.

Where can password policies be used in TYPO3?

  • Backend and frontend user password change using DataHandler (TCA type=password)
  • Backend user password (setup module)
  • Password reset for backend user
  • Password reset for frontend user
  • Install tool – Create Administrative User
  • Install tool – Install tool password
  • Install tool – Initial admin user
Author Torben Hansen
Assigned to Torben Hansen
Created 04/15/22, 05:49
Updated 06/21/26, 09:14
Bug
New Stale TYPO3 CMS 12

#106507 invalidateAllSessionsByUserId method in SessionManager runs out of memory when fe_sessions table has 300k+ entries

In TYPO3\CMS\Core\Session\SessionManager class method invalidateAllSessionsByUserId is called for an example when fe_user password is changed in backend.

If fe_sessions table has 300k+ entries getting all sessions runs out of memory. Increasing memory to 2GB helps but only to a point.

It would be better if only sessions specific for fe_user are fetched instead of $backend->getAll().

foreach ($backend->getAll() as $session) {
            if ($userAuthentication !== null) {
                if ($session['ses_id'] === $sessionToRenew || $session['ses_id'] === $hashedSessionToRenew) {
                    $userAuthentication->enforceNewSessionId();
                    continue;
                }
            }
            if ((int)$session['ses_userid'] === $userId) {
                $backend->remove($session['ses_id']);
            }
        }

This might also be a problem by password recovery, but I did not test that.

Number of sessions in fe_sessions needed for memory issue depends on ses_data size. My issue was with 300k+ entries.

Author B Novak
Created 04/03/25, 14:04
Updated 06/19/26, 13:52

Showing results 751 to 775 of 1561