Showing results 151 to 175 of 1561

Feature
Under Review Fresh Backend User Interface

#110510 Show Language "All" content in every language column of the Layout module

Current behavior

In Content > Layout using Language Comparison, content assigned to the special language value “All” (sys_language_uid = -1) is currently shown in the default language column only.

Since Language “All” is valid for all languages, additional language columns do not fully represent the effective language-specific content structure.

Expected behavior

Content assigned to Language “All” should be shown in every displayed language column in Language Comparison.

Its position should reflect its existing sorting value relative to the content of the respective language.

In connected mode, the existing alignment with the default language structure should remain unchanged. In free mode, the ordinal position may differ between languages because language-specific content is independent, while Language “All” represents one shared record with one sorting value.

No new language or sorting semantics should be introduced.

Motivation

The scope of this feature is deliberately small and limited to visualizing existing Core behavior in the backend.

Language Comparison should make it easier for editors to understand which content participates in a language and how the existing sorting affects its position.

This is particularly useful in free mode, where the shared sorting value of Language “All” is evaluated together with the independent sorting values of each language’s content. Showing the shared record in every language column allows editors to adjust the surrounding content according to their needs within the limitations of the existing sorting model.

The feature does not change persistence, frontend rendering or translation semantics, synchronize language-specific structures, or introduce per-language sorting for Language “All”.

Author Eric Harrer
Assigned to Eric Harrer
Created 08/21/26, 13:20
Updated 11/18/26, 12:52
Epic
Author Oliver Bartsch
Created 05/15/25, 07:58
Updated 11/17/26, 22:12
Task
Author Oliver Hader
Assigned to Oliver Hader
Created 04/10/20, 13:33
Updated 11/17/26, 17:07
Task
Under Review Fresh TYPO3 CMS 15

#111472 dumpFile token does not bind parameter keys: processing options can be swapped (thumbnail/crop bypass)

The eID=dumpFile token is HMAC(implode('|', $parameters), 'resourceStorageDumpFile').

FileDumpController::buildParametersFromRequest() builds $parameters in a fixed order (eID, t, f, r, p, s, cv, dl, fn), drops empty values and signs only the values. Two requests whose non-empty values are equal and in the same order therefore produce the same signed string, regardless of which keys carry them.

The fix for #110316 binds t to exactly one of the selectors f, r, p. The option keys are not covered: s, cv, dl and fn can still trade values with each other, and each of them changes what is delivered:

  • s: scaling / thumbnail (dumpAction(), “Apply width/height”)
  • cv: crop variant of a sys_file_reference (dumpAction(), “Apply cropping”)
  • dl: download disposition (cast to int)
  • fn: alternative file name, any string, no processing

A token issued for a processed variant of a protected file can therefore be replayed to obtain the unprocessed original of the same file.

Affected code

  • typo3/sysext/core/Classes/Resource/Service/FileDumpService.php: isTokenValid() / createToken() (implode('|', $parameters)), used by FileDumpController::dumpAction() and indexed_search\Indexer::createFileFromFileDumpUrl()
  • typo3/sysext/core/Classes/Controller/FileDumpController.php: buildParametersFromRequest(), dumpAction()
  • token generation with the same construction:
    • typo3/sysext/core/Classes/Resource/ResourceStorage.php (getPublicUrl(), ~1496-1506)
    • typo3/sysext/fluid/Classes/ViewHelpers/Link/FileViewHelper.php (~109-130)
    • typo3/sysext/form/Classes/Slot/ResourcePublicationSlot.php (~75-84)
    • typo3/sysext/indexed_search/Classes/Indexer.php (~518-559, token validation)
  • CropVariantCollection::getCropArea() returns Area::createEmpty() for an unknown variant, so a misplaced cv value silently means “no crop”
  • documented API: Feature-90068-ImplementBetterFileDumpController.rst shows signing s and cv for exactly this purpose

Reproduced against the released fix for #110316: a token signed for a 300×200 thumbnail of a protected file, replayed with the value moved from s to fn, returns HTTP 200 with the 1200×800 original (byte-identical). The same works moving cv=default into fn: the crop that hid half of the image is dropped. So this is not closed by the selector-consistency fix. Evidence in the security case material (change-95216).

All branches with the 10.3 FileDumpController API are affected (10.4 – main). Confirmed on main, not yet verified per other branch.

Prerequisites

  • an extension or project issues dumpFile tokens that include s and/or cv for a file that is otherwise not accessible (non-public storage or a ModifyFileDumpEvent listener), following the #90068 documentation, to grant thumbnail-only or crop-only access
  • the attacker obtains one such URL (e.g. the thumbnail shown to them)

Core alone never signs s or cv. ResourceStorage and the form slot sign t plus the selector; FileViewHelper additionally signs dl and fn, with fn restricted to [0-9a-z._-]. With Core-issued tokens only, a value can move between dl/@fn@ and s/@cv@, which changes processing or naming but discloses nothing.

Attack

Signed string for t=f&f=1&s=320c:280c: dumpFile|f|1|320c:280c.

  1. Thumbnail to original: replay as t=f&f=1&fn=320c:280c with the same token. Same signed string, no processing instructions, streamFile() sends the original file in full resolution.
  2. Crop removed: a token for t=r&r=5&cv=default replayed as t=r&r=5&fn=default (or s=default) delivers the full image of the reference. Relevant where the crop hides part of the image.
  3. Combined: a token for s=<S>&cv=<C> replayed as cv=<S>&fn=<C>; the unknown crop variant yields an empty area, no size is applied, the original is delivered.

ModifyFileDumpEvent listeners do not catch this: they receive the file object and the request, not the signed processing instructions, so a listener that grants access to “this reference” grants the original as well.

The resolved object stays the same. Access to a different file is not possible (closed by #110316).

Suggested fix

  1. Sign an unambiguous encoding of keys and values, e.g. http_build_query() or json_encode() of the parameter array, in one place (FileDumpService), and use it from all generators listed above instead of four copies of hmac(implode('|', …)).
  2. Keep cached and stored URLs working: accept the legacy format only as long as the request carries no s and no cv. All Core-issued URLs fall into that case, so only the documented extension use case is forced onto the new format.
Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 11/17/26, 12:18
Updated 11/17/26, 15:40
Bug
Under Review Fresh Themes TYPO3 CMS 14

#108895 Camino: Display Website title (from site settings)

Web site title (from site settings) should be displayed in theme instead of “Camino” in header and footer

Right now (14.1) setting the website title only changes the meta-title but not the page itself

Author Lina Wolf
Created 02/07/26, 10:39
Updated 11/16/26, 22:29
Task
Accepted Fresh Backend User Interface TYPO3 CMS 14

#100535 CSP module: On small browser size the UX of the details view could be improved

When working with a small browser size, the details block is not scrollable – only the list of violations. So, some buttons on the details block are not reachable:

Addition: I have to scroll the list completely down, then also the details block will scroll. Not optimal from a user experience point of view, as I am losing the focus on the row I am just investigating (and have to search for the next row when scrolling up again).

Author Chris Müller
Created 04/08/23, 09:10
Updated 11/16/26, 08:42
Feature
Under Review Fresh Frontend

#19832 sectionMarker (page anchor) prefix is hardcoded as "c"

sectionMarker (page anchor) prefix is hardcoded as “c” while it is freely configurable in css styled content.

You can change the page anchor from the default:
tt_content.stdWrap.dataWrap = |

To something like:
tt_content.stdWrap.innerWrap.cObject.default.10.value =
|
Or
tt_content.stdWrap.innerWrap.cObject.default.10.value =
|

Although it is longer, it’s more descriptive.

The point is that is is changeable by the user. But the anchor prefix is hardcoded in the core as being “c”.

This is in the following files:
sysext/cms/tslib/class.tslib_content.php (line 5268 and line 5390)
sysext/simulatestatic/class.tx_simulatestatic.php (line 166)

(issue imported from #M10147)

Author Michiel Roos
Created 01/15/09, 08:13
Updated 11/15/26, 11:21
Task
Under Review Fresh Tests TYPO3 CMS 13

#111459 Workspace publish tests expect hidden live content in frontend

Four functional tests expect a hidden, published content element to be rendered in the frontend for a backend user:

  • Regular/WorkspacesPublish/ActionTest::hideContent
  • Regular/WorkspacesPublish/ActionTest::hideContentAndMoveToDifferentPage
  • Regular/WorkspacesPublishAll/ActionTest::hideContent
  • Regular/WorkspacesPublishAll/ActionTest::hideContentAndMoveToDifferentPage

After publishing, “Regular Element #2” is hidden=1 in live (see the DataSet CSV of each test). The frontend requests pass no workspace id in the InternalRequestContext. The testing-framework BackendUserHandler then leaves BackendUserAuthentication::$workspace at its default -99, which is not live, and the frontend renders the hidden element.

The sibling tests in Regular/WorkspacesModify assert the opposite for the same situation in a workspace (DoesNotHaveRecordConstraint).

This blocks a testing-framework fix that initializes the backend user properly and defaults to the live workspace:
https://github.com/TYPO3/testing-framework/issues/535
https://github.com/TYPO3/testing-framework/pull/536

With that fix applied, the four tests fail, as reported in https://github.com/TYPO3/testing-framework/pull/536#issuecomment-1956430328

Proposed change: request the live workspace explicitly with withWorkspaceId(0) and assert that the hidden element is not rendered. The adjusted tests pass with testing-framework main and with testing-framework PR 536.

Author Sebastian Mendel
Created 11/14/26, 22:01
Updated 11/14/26, 22:26
Bug
Under Review Fresh TYPO3 CMS 10

#95311 foreign_match_fields affects copy of inline records (IRRE)

Everything that follows is based on BE testing and an assumption:

It seems like the config `foreign_match_fields` affects the copy process of inline records.
We have a content element setup with a inline record, which changes its type depending on the CType

The issue:
When copying the element, the inline records are not copied.
When copying the whole page, the inline records are added to the original element instead of the element that got created on the newly pasted page.

Example:
CType: horizonal_teaser —- inline record with field “type” = horizontal
CType: vertical_teaser —- inline record with field “type” = vertical

The type field equals the TCA “types” declaration, that displays the fields etc.
As we reuse the field we add the `foreing_match_fields`.
The config is provided via `columnsOverrides`.

Guess the best testcase would be a setup via EXT:styleguide, as i cannot provide the full setup here.

Author Henrik Elsner
Created 09/22/21, 12:21
Updated 11/14/26, 19:03
Feature
Accepted Fresh Backend User Interface

#106333 TCA-Table: Functionality to add custom filter to the table

Hi,

I don’t know whether I’ve missed something but I have checked the documentation in https://docs.typo3.org/m/typo3/reference-tca/12.4/en-us/Ctrl/Index.html and seen nothing about building custom filter for a TCA-Table. I’ve checked the documentation for `ctrl` and `columns`, but nothing about adding filter to the table (only for form). If there is already a way, kindly point me in the right direction

TYPO3 version = v12.4.26

Suppose I have a SQL-Table with column `verified` (TINYINT. Value is either 1 or 0), I would like to be able to filter the entries in the TCA-Table of said SQL-Table by `verified` column (e.g. as Checkbox or Select field on the table header). Currently I can only filter by text through the main filter, but I also want to filter by non-text columns

Author Jason Christian
Created 03/07/25, 12:21
Updated 11/14/26, 15:31
Epic
In Progress Fresh Backend User Interface

#108915 Page Creation Wizard

Our current page creation workflow is a barrier to entry for new editors. It is technically complex, not mobile-ready, and fails to guarantee data integrity, resulting in a slow and frustrating ‘time-to-content’ experience.

Our goal is to streamline the page creation process by introducing a guided, accessible, and error-proof wizard that empowers editors to build high-quality page structures without requiring deep technical knowledge.

Goals

Data Integrity and Content Readiness

We want to ensure that all mandatory fields are populated during page creation so that we avoid “broken” or incomplete page records (e.g. missing configurations for news detail pages).

Key Points:
  • Validation of required fields during the creation step.

Intuitive and Guided User Experience

Editors should get a consistent and guided process for creating pages to achieve results quickly without having to navigate complex TYPO3-specific settings.

Key Points:
  • Fast-track to results, avoid unnecessary steps.
  • Standardized workflow for all page types.
  • Zero TYPO3-specific expertise required for basic setup.

Accessibility and Responsive Design

We want to build pages using an interface that follows accessibility guidance and modern web standards.

Key Points:
  • WCAG 2.2-compliant accessibility for the entire wizard workflow.
  • Responsive layout.

Workflow Flexibility and Efficiency

It should be possible to start the wizard from different entry points in the backend, with pre-defined parameters depending on context. Creating multiple pages should also be supported.

Examples:
  • Current Drag&Drop behavior would pre-fill the page type and position.
  • Creating a page from the Records module would pre-fill the position property.
Key Points:
  • Wizard can be repeated, instead of finishing, “Create New Page”, to support a workflow of creating multiple pages.
  • Context-aware start (Wizard respects pre-selected positions or types).

Extensibility and Modularity

The page creation wizard should be modular and extensible, so that integrators can implement custom steps for their own page types or extend existing ones.

Key Points:
  • The concept “page creation wizard” should be implemented generic enough to later be adopted to improve further TYPO3 workflows (e.g., content element creation).
  • Developers should be able to extend existing configuration, but not be able to remove required steps defined by the TYPO3 Core.

Technical Concept: Frontend/User

Initialization and Type Selection

The process begins with the initialization of the Wizard UI, triggered via different actions in the Backend, the prototype suggesting a new button in the page tree actions. In the first step, the system fetches all available Page Types (doktype) through a fetch request to a JSON endpoint. This ensures that only relevant types, including custom icons and labels, are presented to the user. Once a type is selected, a frontend validation check confirms the choice before moving forward.

Dynamic Content Loading

Upon proceeding, the Wizard sends the selected doktype to the server to determine the specific requirements for the following steps. The goal is to receive a server-side rendered form using the TYPO3 FormEngine. This approach ensures that all TCA-based rules and field configurations are respected.

Positioning and Page Tree Integration

The second step presents a page tree to the user. This allows the user to select an origin and define the exact position, such as “above page”, “below page” or “as subpage”.

Data Entry and Validation

The subsequent steps gather the actual page information, divided into required fields and optional/recommended fields + additional steps. Required fields like the page title and URL slug are handled first, followed by optional metadata or SEO settings. Each transition between these steps is protected by frontend validation to ensure that all mandatory fields are correctly filled according to TCA requirements.

Review and Persistence

Before any data is written to the database, a summary screen provides an overview of all entries. This allows the user to verify the page type, position, and values at a glance. Once confirmed, the data is transmitted to the the TYPO3 DataHandler to create the record, ensuring that all system hooks and permission checks are properly executed.

Success Feedback and Workflow

The final step informs the user of a successful creation through a clear feedback message. Instead of simply closing the Wizard, the UI offers contextual follow-up actions. The user can choose to jump directly into the Layout Module to add content, start the process over to create another page, or exit the Wizard to return to their previous task.

Technical Concept: Backend

Naming of the class and method names below is not final and open to discussion.

  • A generic WizardController will be called as soon as initial data is requested.
    • The controller will be generic, wizard specific logic is to be implemented in WizardProvider classes.
    • Initial data can be anything, in the case of the Page Creation Wizard its the available page types.

Design Pattern:

The generic WizardController has three endpoints. Each endpoint gets passed the wizard type, which is internally resolved to a WizardProvider implementation

Endpoints:
  • Fetching initial data
  • Fetching wizard steps
  • Persisting wizard result
The logic for each endpoint is implemented in a wizard-specific WizardProvider:
  • WizardProviders are resolved using a WizardProviderFactory that gets the requested type passed from the controller
  • The WizardProviders should be tagged with an Attribute that allows the factory to resolve them, e.g. #[AsWizardProvider(wizard: 'page-creation')]
Example PageWizardProvider implementation:
  • Initial data request returns all available page types and their count of steps for the wizard.
  • Wizard step resolving:
    • One wizard step returns all required fields (fields marked as required in TCA)
    • Another wizard step returns all recommended fields (fields marked as recommended in TCA)
    • Markup of these steps should be rendered with FormEngine.
  • Persistance step:
    • Resulting page data should be persisted via DataHandler.

See:
!initialData.png!
!getSteps.png!

Author Andreas Nedbal
Created 02/09/26, 13:52
Updated 11/14/26, 10:39
Task
Author Josua Vogel
Assigned to Josua Vogel
Created 11/13/26, 14:05
Updated 11/13/26, 14:19
Feature
Under Review Fresh Link Handling & Redirect Handling

#101637 Redirects Overview

As a user I’d like to filter on more than the available fields, like # of hits and “Last hit on” and “date created”.

The date created is missing so far and it would have added value if this gets added to the overview.

This will help me maintaining / cleaning up the list.
This helps me deciding whether a shortcut needs to remain active while doing maintenance.

(Just the last hit is not enough in this case, as it doesn’t say anything if the counter stays at 0)

Author Jason Hoendervanger
Assigned to Stefan Bürk
Created 08/09/23, 13:06
Updated 11/13/26, 10:25
Bug
Under Review Fresh TYPO3 CMS 14

#111430 RecordFactory does not resolve record types defined in a foreign table

RecordFactory::createRawRecord() ignores TCA types that point to a field of a related record, such as “file:type” (sys_file_metadata) and “uid_local:type” (sys_file_reference).

Records of these tables therefore get no record type. Consumers such as the VisibleSchemaFieldsCollector fall back to all columns of the table instead of the fields of the actual type, e.g. the element information of a video file lists the image related metadata fields “width” and “height” (see #110150).

Expected: the record type is resolved from the related record, so getRecordType() returns e.g. “2” and the full type is “sys_file_metadata.2”.

Author Benni Mack
Assigned to Benni Mack
Created 11/13/26, 09:07
Updated 11/13/26, 10:09
Bug
Under Review Fresh Localization TYPO3 CMS 13

#104140 Confusing behaviour with file relations in translated records ("Translation behavior" = "Value of default language")

Environment

  • Translated page, field “media”
  • No existing file relations in both original language and translation
  • In translated page: “Value of default language” selected as “Translation behavior”

The problem

When adding a new relation and saving the record, the new relation vanishes. On v11, there seems to be an error message about inserting a record where it is not allowed (reported by an end user).

The problem is not there when setting “Translation behavior” to “Custom value”.

Possible solution

1. Selecting “Value of default language” should make the field read-only, i.e. hide the buttons for adding new relations, and probably also make the IRRE record r/o.
2. Changing from “custom value” to “value of default language” should reset the custom relations

Additional information

  • Existing records added with “Custom value” are kept when saving the record with “Value of default language” enabled)
Author Andreas Wolf
Created 06/18/24, 08:03
Updated 11/13/26, 09:38
Bug
Under Review Fresh DataHandler aka TCEmain TYPO3 CMS 14

#97092 DataHandler creates invalid sys_file_reference row

Scenario:
  • Create a page
  • Add an image to “Resources” media field of the page
  • Localize the page to some language, the image will be localized, too.
  • In the page localization record, “Translation behavior” “Value of default language” is selected, but the buttons to add further images are still shown. Add another image and save.

-> After save, the image is gone again. Most likely due to “Value of default language” translation behavior”. That’s fine.

But: A sys_file_reference record is created. And that one is broken since it has ‘uid_foreign’ set to 0, and empty values for ‘tablenames’ and ‘fieldname’. This should not happen. I guess, the check for the translation behavior needs to happen earlier in DH to suppress the record creation?

Author Christian Kuhn
Created 03/03/22, 12:47
Updated 11/13/26, 09:38
Bug
Under Review Fresh AdminPanel TYPO3 CMS 13

#111420 Admin Panel: "Simulate time" date/time fields show 1970-01-01 00:00 when no simulation is set

Steps to reproduce

  1. Enable the admin panel (config.admPanel = 1, user TSconfig admPanel.enable.preview = 1).
  2. Log in to the backend and open a frontend page.
  3. Open the admin panel, open the “Preview” settings. No time simulation is active (checkbox “Simulate time” unchecked).

Expected

The (disabled) date and time fields are empty.

Actual

The date field shows 01/01/1970 and the time field 00:00.

If the user ticks “Simulate time” and saves without changing the date, the result depends on the browser timezone. In a browser east of UTC (e.g. Europe/Berlin) the fields are parsed as local time, which gives a negative timestamp (-3600). PreviewModule clamps it via max($simulateDate, 60), so the frontend is rendered at 1970-01-01 00:01 UTC. All records with a starttime disappear, which is confusing. In a browser running in UTC the value becomes 0 and no simulation happens at all.

Cause

Without a simulation, PreviewModule::getPageSettings() passes (int)($this->config['simulateDate'] ?? 0), i.e. 0, to the template. Partials/Form/DateTime.fluid.html renders it into the hidden field:

<input type="hidden" name="TSFE_ADMIN_PANEL[{name}]" id="{name}" value="{value}" />

Build/Sources/TypeScript/adminpanel/modules/preview.ts only checks whether the hidden field has a value. The string “0” is truthy, so it initialises the pickers with the Unix epoch:

if (this.targetField.value) {
  const initialDate = new Date(parseInt(this.targetField.value, 10) * 1000);
  this.dateField.valueAsDate = initialDate;
  this.timeField.valueAsDate = initialDate;
}

Possible fix

Treat 0 as “no value”, e.g. in preview.ts:

const initialTimestamp = parseInt(this.targetField.value, 10);
if (initialTimestamp > 0) {
  ...
}

or render an empty value in the partial: value="{f:if(condition: value, then: value)}".

Environment

  • Reproduced with TYPO3 13.4.39 (Composer mode), PHP 8.4.
  • The code is unchanged on main (v14).
  • Related, but a different issue: #101849 (simulated time does not respect the timezone). valueAsDate interprets the timestamp as UTC, while updateDateField() parses the entered values as local time.
Author Grischa Schüring
Assigned to Maike Kiebele
Created 11/12/26, 10:49
Updated 11/13/26, 09:05
Feature
Under Review Fresh Form Framework

#111025 Add webhook finisher to EXT:form

Sending form submissions to external systems (n8n, CRM, ticketing, marketing automation) currently needs a custom finisher.
TYPO3 already ships EXT:webhooks with signed, admin-managed outgoing webhooks, but EXT:form offers no trigger for it.

  1. New webhook trigger “Form submitted” (identifier typo3/form-submitted), provided by EXT:form as TYPO3\CMS\Form\Message\FormSubmittedMessage. Like the redirect trigger of EXT:redirects it only uses the attribute and interfaces from EXT:core, so EXT:form does not depend on EXT:webhooks.
  2. New finisher “Webhook” (WebhookFinisher), available in the form editor. Its option “webhooks” takes a list of sys_webhook identifiers (UUIDs). On submit the finisher builds the payload and dispatches the message to the message bus, targeting exactly these webhooks (depends on targeted webhook messages, see related issue).

URL, secret, HTTP method, headers and SSL verification remain in the sys_webhook record, which only administrators manage. Editors can choose which webhook a form uses, but cannot define target URLs.

Payload

A fixed JSON structure:
  • submissionId (UUID)
  • submittedAt
  • form: identifier (as declared, without the content element suffix), persistenceIdentifier, label
  • context: site identifier, language, page uid, content element uid
  • values: keyed by element identifier, each with type, label and value

Never included: password fields, honeypot, disabled elements and elements without a value.

File and image uploads are a list of name, MIME type and size. The download URL (FAL public URL; the signed dumpFile URL for non-public
storages) is only added when the form has no DeleteUploads finisher, since the files would otherwise be gone before the receiver fetches them.

Behaviour

  • Fire-and-forget: the response of the endpoint does not influence the form submission. Delivery errors are logged by EXT:webhooks.
  • Exceptions while dispatching are logged; the submission always completes.
  • Without EXT:webhooks installed the finisher does nothing.

Out of scope

Configurable payload / field mapping, feedback from the endpoint into the form.

Author Josua Vogel
Created 10/12/26, 06:17
Updated 11/13/26, 08:12
Epic
In Progress Fresh Themes

#108537 Add an initial theme for TYPO3 v14 - "Camino"

For v14 we want to introduce themes. As time constraints matter, this will be added in a form of an extension for the time being… ideally this can later be moved to another “typo3-theme” project type, or even not be based on extensions.

Author Benni Mack
Created 12/19/25, 14:13
Updated 11/12/26, 21:10
Task
Under Review Fresh Tests TYPO3 CMS 15

#111428 Run Playwright e2e tests with multiple workers in CI

The Playwright e2e shards are the longest jobs of the pre-merge pipeline. In CI every shard runs its tests with a single worker (workers: process.env.CI ? 1 : worker in Build/playwright.config.ts), so about 90 tests per shard are executed strictly one after another. Setting up the instance takes about 15 seconds, the rest of the job is test execution.

Raising the worker count alone does not work, because the specs are not isolated from each other:

  • All workers share one backend user and one session. Flash messages, module state, user settings, user TSconfig and the selected workspace leak from one worker into the tests of another.
  • Several specs save the same styleguide record. FormEngine submits every field of a record, so a form that was opened before another worker saved reverts that change.
  • Some specs change state every other spec observes: install tool and system settings, the site configuration, pages other specs navigate to, workspaces.
  • Playwright distributes specs to shards by test count, not by duration, which leaves some shards with far more test time than others.

Goal: run the e2e specs with several workers per shard in CI.

  • one backend administrator per worker
  • specs that collide only with each other run one at a time, next to the parallel ones
  • specs that change global state run on their own, after the parallel ones
  • spec files are distributed to the shards by their measured duration

Measured locally (composer mode, SQLite), the slowest of the four shards drops from 276 to about 138 seconds with three workers. This has not been measured on the CI runners yet.

Follows #111424, which made the two slowest FormEngine specs cheaper.

Author Benni Mack
Created 11/12/26, 20:16
Updated 11/12/26, 20:51
Feature
New Fresh Backend User Interface

#111323 Tab scroller: scroll overflowing tabs with the vertical mouse wheel

Since #109171 (https://review.typo3.org/c/Packages/TYPO3.CMS/+/93097), overflowing .nav-tabs (e.g. in the page properties) are horizontally scrollable via arrow buttons, keyboard and the browser’s native Shift+wheel. A plain vertical mouse wheel over the tab bar does nothing, so mouse users without a tilt wheel or trackpad have to click the arrows.

Questions before submitting a patch:

  1. Was requiring Shift+wheel a deliberate decision, or simply not considered?
  2. Would a change be accepted that maps vertical wheel to horizontal scrolling only while the tab bar overflows and can still scroll in that direction (page scroll continues at the edges; trackpad gestures and Ctrl+wheel stay untouched)?
  3. Should this go in as Feature (main only) or Task/Bugfix (main + 14.3)?

A patch with tests is ready and can be pushed as WIP for discussion.

Author Sebastian Mendel
Created 11/02/26, 13:12
Updated 11/12/26, 18:07
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 13

#108926 File list: Link implemented as button

The name of a file can be clicked on and operated using the keyboard. Interaction leads to a new page where the file details can be edited.

All references must be implemented as links; only actions such as opening a menu should be implemented as buttons.

Solution
Turn the button into an a element with href.

Note
The visible accessible name of the element is already available to sighted and blind users. It does not need to be additionally output in the title attribute, which is not available to most users anyway (only works reasonably well with a connected mouse).

Author Christian Jung
Created 02/10/26, 12:46
Updated 11/12/26, 16:48
Feature
Under Review Fresh Themes

#109379 Camino: add theme toggle for dark / light mode

  • The toggle is shown on the FE page
  • Different toggle types shall be provided for the admin / site owner to select
  • The toggle type can be selected in site settings

The screenshot shows WIP on the default color-theme “Caramel Cream” and includes still utf-8 icons instead of SVGs

Author David Bruchmann
Created 03/26/26, 10:44
Updated 11/12/26, 14:53
Feature
New Fresh Workspaces

#111426 Workspace preview: keep live and workspace frame scrolled to the same content element

The workspace preview module shows a page twice, the live version (ADMCMD_prev=LIVE) and the workspace version (ADMCMD_prev=IGNORE), each in its own iframe. Both frames scroll independently. When an editor moves the slider between “Published version” and “Workspace version”, or uses the vbox/hbox split, the other frame shows a different part of the page. To compare a changed element, the editor has to find the same spot again by hand. On long pages this makes the slider hardly usable for reviewing changes.

There is no setting for this. workspaces.splitPreviewModes only selects the mode, and preview.js does not handle scrolling at all.

Steps to reproduce:

1. Switch to a workspace and change a text element far down on a long page (e.g. add two paragraphs).
2. Open the preview of the page (slider mode).
3. Scroll the workspace version to the changed element.
4. Move the slider to “Published version”.

Expected: the live version shows the same element, so the difference is visible directly.
Actual: the live version is still at the top of the page.

Proposed solution:

Sync the scroll position between both frames by content element, not by pixels, since the workspace version of an element may be longer or shorter than the live one.

  • Each frame determines the content element at the top edge of the viewport (the anchor c<uid> rendered by fluid_styled_content, which is the live uid in both versions) and how far into it the viewport is, as a ratio of its height.</uid>
  • The position is sent to the sibling frame via postMessage, so it also works when backend and frontend run on different domains.
  • The receiving frame scrolls to the same relative point of the same element. If the element does not exist in that version (new, hidden or deleted in the workspace), it scrolls to just below the nearest preceding element that exists in both.
  • Content elements rendered more than once on a page (records via “Insert records” repeat the same id) are matched by id plus occurrence.
  • Programmatic scrolling is suppressed for a short moment to avoid ping-pong between the frames.

We run this as a site-level workaround on TYPO3 14.3: a frontend middleware adds a small script to responses with ADMCMD_prev=LIVE or IGNORE when a backend user is logged in. It works with the slider and both split modes. In the core it could live in the preview module itself plus a small frontend part, or as an option, e.g. workspaces.previewScrollSync = 1.

Author Daniel Forsch
Created 11/12/26, 14:25
Updated 11/12/26, 14:25
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 14

#111342 Record history of a deleted record fails: "Trying to access array offset on null" in RecordHistory::getTranslations()

Since 14.2.0 the record history shows a language switcher (ElementHistoryController::addLanguageSwitcher()). It calls RecordHistory::getTranslations(), which reads the record and its translation origin with BackendUtility::getRecord() including the deleted restriction. For a deleted record both lookups return null, and the array access on $translationRoot fails:

  • any table other than pages: RecordHistory.php line 188 (14.3.10), (int)$translationRoot[‘pid’]
  • pages: line 192, (int)$translationRoot[$langField]

The same applies to a translation whose default language record is deleted.

With E_WARNING in SYS/exceptionalErrors (e.g. the Debug preset, 12290) the history view ends with HTTP 500:

#1476107295 TYPO3\CMS\Core\Error\Exception
PHP Warning: Trying to access array offset on null in .../typo3/cms-backend/Classes/History/RecordHistory.php line 188

The rest of the history view deliberately supports deleted records (e.g. ElementHistoryController::setPagePath() reads them with $useDeleteClause = false), and the history of a deleted record is exactly where an editor rolls back the deletion. TYPO3 14.1 and earlier are not affected.

Steps to reproduce

  1. Create a content element on a page and delete it.
  2. Open the history of the page (context menu of the page → History).
  3. In the changelog row of the deleted content element, click the filter icon (“Show history for this record”), or call /typo3/record/history?element=tt_content:<uid> directly.</uid>
  4. Result: exception #1476107295 (line 188).
  5. Same with a deleted page: element=pages:<uid> fails in line 192.</uid>

Expected result

The history of the deleted record is shown, including the rollback of the deletion, as in 14.1. Without a translation root there is nothing to switch between, so the language switcher can be omitted.

Possible fix

Return null from getTranslations() when the translation root cannot be read (patch against main):

--- a/typo3/sysext/backend/Classes/History/RecordHistory.php
+++ b/typo3/sysext/backend/Classes/History/RecordHistory.php
@@ -169,6 +169,10 @@
             $translationRoot = $record;
         } else {
             $translationRoot = BackendUtility::getRecord($table, $defaultLanguageUid);
+        }
+        if ($translationRoot === null) {
+            // The record or its translation origin is deleted, there is nothing to switch between
+            return null;
         }

         $queryBuilder = GeneralUtility::makeInstance(ConnectionPool::class)

Alternatively, read the record and the translation root without the deleted restriction, so deleted records keep the switcher.

Environment

TYPO3 14.3.10 (Composer), the code is unchanged on the 14.3 and main branches; PHP 8.4.20. We currently work around it with an XCLASS of RecordHistory that applies the check above.

Author Marian Gajda
Assigned to Maike Kiebele
Created 11/04/26, 15:24
Updated 11/12/26, 08:13

Showing results 151 to 175 of 1561