Showing results 1026 to 1050 of 1561

Bug
New Orphaned TYPO3 CMS 13

#107426 WCAG: Optimizing the view dropdown in fileadmin

The user is in the file list module in a folder that already contains files. The tile view is selected.

The user navigates to the dropdown field to switch to the list view. When selected, the selection list opens with several options.

When tabbing, the screen reader does not indicate the end of the list and the user jumps out of the list after the last entry.

Expected result:

I select the drop-down list and can navigate through the individual entries using the tab key. When I reach the end, the screen reader indicates that I have reached the end of the list.

Author Christian Rath-Ulrich
Created 09/10/25, 16:34
Updated 09/12/25, 08:18
Bug
New Orphaned TYPO3 CMS 13

#107445 WCAG: Contrast / Inverted display - Headings, names & icons

Framework conditions: Zoom 150% / inverted mode / external monitor

Description:

Example 1:

The user navigates through the various files in the “File List” module. The file names are not inverted in inverted mode and appear in black font on a black background.

Example 2:

The user navigates through the page titles. These are not displayed in inverted mode and appear in black font on a black background.

Example 3:

The workspace is structured with tabs; inverted display makes it impossible to see which tab you are currently in.

Example 4:

The Typo3 bar in the header region is not highlighted in color in high contrast mode. As a result, it is not clear which work environment you are in.

Example 5:

The contrast of the icons needs to be sharper; depending on the background color selected, the contrast is insufficient. This primarily affects clickable icons and graphics.

Example 6:

Hover icons must not be used and must be displayed constantly to enable orientation; the corresponding icons must also be given a clear title (examples: Dashboard —> Move / Delete) so that the screen reader can output them.

Example 7:

In the inverted display, pop-ups are not clearly recognizable because a black area appears on a black background. The “X” for closing the pop-up could also be displayed larger.

Example 8:

Preview function: Buttons are not displayed in inverted mode; furthermore, there is no clear distinction from the website.

Faulty behavior:

It appears as if some of the fonts are “hard coded.”

There is a lack of contrast.

Expected behavior:

Even in inverted mode, users should be able to clearly read all labels and names.

Author Christian Rath-Ulrich
Created 09/12/25, 08:14
Updated 09/12/25, 08:16
Bug
New Orphaned TYPO3 CMS 13

#107444 WCAG: focus after element creation

The user creates a page and updates it – Focus setting / screen reader is used.

Incorrect behavior:

After updating, the focus jumps to the top of the page.

Expected behavior:

After updating a page, users should be taken to where they were last (focus setting) – currently, the focus jumps to the top of the page.

Author Christian Rath-Ulrich
Created 09/12/25, 07:58
Updated 09/12/25, 07:59
Bug
New Orphaned Workspaces TYPO3 CMS 12

#107430 Editor working in workspace is swapped to LIVE without user interaction

Short summary:

A editor working in a workspace, experience that some changes happens to be published to live, because the workspace is changing.

We have a full video and sys_log entries where we follow the editors move and can see the change in workspace.

More detailed:

A editor submitted a issue, that some changes weren’t in the workspace after completing the work. But was published to live, without the editor going through the “publish” step of the Workspace.

The editors experience is: * Change to relevant workspace * Make changes to content (delete, new, edit) * See preview in workspace * Find not all changes are visible in the workspace * Find that some changes is changed in LIVE

When we follow the users screenrecording and matches it with the sys_log entries, we can see how the Workspace all of a sudden changes from “Workspace name” to “LIVE”, without any user interaction.

It leaves the in a mix, with a workspace preview showing some changes, but not all, as some is already published.

We can’t seem to see any interaction that would force a change of workspace to LIVE as the editor only manages content in the Page module while it’s clearly stated that the work is done in a workspace (topbar colors is different, fewer modules).

Author Soren Malling
Created 09/10/25, 21:47
Updated 09/10/25, 21:47
Task
New Orphaned FormEngine aka TCEforms TYPO3 CMS 14

#107259 Move system fields into dedicated systemColumns array in TCA

In TYPO3 v14, we want to further reduce TCA complexity by restructuring the handling of system fields such as starttime, endtime, and similar fields. These fields are already automatically added via TCA enrichment and no longer need to be explicitly defined in TCA.

The plan is to completely remove these fields from showitem definitions (and similar places) and move them into a new dedicated TCA array called systemColumns.

Details:
A new array systemColumns will contain all system fields that are automatically added via TCA enrichment. The TCA schema will reflect this via a new method getSystemFields(). FormEngine will react to systemColumns and render these fields separately from the record-type-specific fields. In the first implementation step, FormEngine will still render them exactly as before, just based on the new systemColumns source. In a later step (not part of this issue), these fields will be rendered in a separate section, making the main editing interface cleaner by showing only type-specific fields at first glance. Another follow-up step will be the automatic inclusion of essential fields that must always be present because they are defined in ctrl (e.g., the type field like CType in tt_content).

Benefits:
  • Simplifies showitem and palette definitions
  • Reduces TCA duplication and maintenance effort
  • Improves editor experience by separating essential system fields from type-specific fields.
  • Prepares the ground for a cleaner backend UI in future versions.
Scope of this issue:
  • Introduce systemColumns in TCA
  • Add Migration of those filed to systemColumns, while removing them from columns and showitem
  • Adjust TCA schema: Add getSystemFields()
  • Check if TcaSchemaFactory needs adjustments to correctly handle those fields.
  • Make FormEngine react to systemColumns but render them as before for now

Note: No UI changes yet – separation of rendering will follow in a later issue.

Author Oliver Bartsch
Created 08/11/25, 20:28
Updated 09/09/25, 07:02
Feature
Needs Feedback Orphaned Localization

#88766 Unpredictable allowLanguageSynchronization behaviour with file references

The TCA behaviour “allowLanguageSynchronization” has some user experience or design issues in combination with sys_file_references.

For the following examples I’ve used the actual TYPO3 CMS Master (10.0.x-dev) and the media field in page properties. Make sure you have at least one page with a translation.

Let’s beginn simple:

1. Parallel display of buttons to add relations and translation behaviour

IMHO the buttons to add relations should only be displayed on translations if “custom value” is chosen.
Or the other way round, if you add a relation in a translation it should automatically switch to “custom value”.

ATM if you add a relation and hit the save button while “value of default language” is still selected, the relation wont be saved. -> Bad UX
(see also topic 3)

2. Custom value != custom value

Starting with a empty media field (also in translations)
Step 1: Add a relation in default language and save
Step 2: Switch the translation behaviour to “custom value” in your translation and save.
Step 3: Go back to the default language of the page, delete the relation and save.

The relation is also deleted on the translated page with “custom value”. The editor would first have to delete the image and add it again in the translation to keep it.
Just because the l10n_parent is set, it is not necessary right to delete the relation. The translation behaviour isn’t taken into account.

3. Resync relations

Starting again with a empty media field (also in translations)
Step 1: Set translation behaviour “custom value” in translation
Step 2: Add a relation in default language

No relation added on translation. Yay, expected behaviour :-D

Step 3: Change translation behaviour to “value of default language” and save

The image is resynced correctly :-D

Step 4: Delete relation relation while keeping “value of default language” active and save

The image is gone for the translation until somebody saves the default language. This can be misleading for editors if they forget to switch to “custom value” at this point. This can be solved along with topic 1

4. Show warning when relation of translation is deleted

Starting again with a empty media field (also in translations)
Step 1: Add a relation on translation with “custom value” behaviour
Step 2: Switch translation behaviour to “value or default language” and save

Custom relation of translation is kept.

Step 3: Switch to default language and add save

Custom relation of translation is still there.

Step 4: Add new relation on default language and save

The new translation is added for all languages and the custom relation of the translation is deleted.

IMHO this is correct, but for better usability I would prefer a warning dialog when an editor changes to “value of default language” and if there are any relations without l10n_parent.
Something like: “Some relations are not connected to the default language. Are you sure to remove them?” and then delete them directly on approval.

5. Permission error

Starting with a empty media field (also in translations) and “value of default language” enabled
Step 1: Add relation on default language and save
Step 2: Add to “custom value, add a new relation on the translation and save
Step 3: Back on default add a new relation and save
Step 4: Switch translation behaviour back to “value of default language” and save

You should get an error like “1: Attempt to modify record ‘rawpixel-1046262-unsplash.jpg’ (sys_file_reference:292) without permission. Or non-existing page.” for the relation added in step 2.

—-

I hope those cases can help to improve the US with the allowLanguageSynchronization behaviour for editors.

Author André Buchmann
Created 07/15/19, 17:00
Updated 09/04/25, 12:58
Bug
New Orphaned AdminPanel TYPO3 CMS 13

#107391 Font size too small under circumstances in admin panel

On a website the styles define

html {
  font-size: 62.5%
}

This enables the frontend developer to use relative sizes (rem) which can be calculated easily (1rem = 10px, 2rem = 20px). The admin panel however also defines relative font sizes (0.75rem, and also 0.6875rem), resulting the calculated font size to 7.5px which is way to small:

The admin panel should be agnostic of the defined font size of the website.

Author Chris Müller
Created 09/04/25, 11:51
Updated 09/04/25, 11:51
Bug
New Orphaned TYPO3 CMS 14

#107387 Cache flush of localized records in DH clears caches of all languages

I don’t know if this behavior is expected, but I’m a little bit worried about the reasons of this.

Given pages with uid=1 (default language), uid=2 (DE localization), uid=3 (DA localization) and uid=4 (CZ localization). When caches are cleared for the localized page with uid=2, caches for all other pages (uid=1,3,4) are cleared as well. This does not make sense to me – it should only be the case for the default language. It may make sense for languages which have a fallback language configured, but this constraint does obviously not apply here.

(Side note: \TYPO3\CMS\Core\DataHandling\DataHandler::prepareCacheFlush calculates the cache tags to clear, so it might be necessary to make changes there, in case the described behavior is considered inappropriate and needs to be adapted.)

Author Elias Häußler
Created 09/04/25, 05:58
Updated 09/04/25, 06:02
Task
New Orphaned TYPO3 CMS 14

#107377 Drop usage of pageId_* cache tags

We already have pages_*. It might be a good idea to (finally) drop pageId_* and streamline caching behavior for pages with other tables (<table>_<uid>).

This is of course highly breaking, but lowers maintenance barriers in the future and also makes bugfixes like #107376 easier to implement.

Author Elias Häußler
Created 09/03/25, 09:07
Updated 09/03/25, 09:07
Task
New Orphaned Security TYPO3 CMS 14

#107374 Replace typo3/html-sanitizer with symfony/html-sanitizer

  • try to reuse TypoScript settings of tags as much as possible (see https://docs.typo3.org/permalink/t3tsref:tags)
  • replace typo3/html-sanitizer with symfony/html-sanitizer
  • extend symfony/html-sanitizer to support
    • HTML comments (required for COA_INT et al)
    • closure handlers (e.g. checking URI prefixes for a.href attrs)
    • dealing with SVG/MathML data (to replace enshrined/svg-sanitize)
  • finally drop HtmlParser of the TYPO3 core
Author Oliver Hader
Assigned to Oliver Hader
Created 09/02/25, 15:36
Updated 09/02/25, 15:36
Bug
New Orphaned System/Bootstrap/Configuration TYPO3 CMS 12

#103883 View generated in LinkBrowserController missed PageTS configuration

Given:

- a package having following files:

Configuration/page.tsconfig with content templates.typo3/cms-backend.123 = EXT:foo/Resources/Private/TemplateOverrides
*Resources/Private/TemplateOverrides/Templates/LinkBrowser/Page.html* with content Foo_
*Configuration/PageTs/PageTs.typoscript* with content _templates.typo3/cms-backend.123 >

The given PageTS is used on the root page (in page settings).

Expectation:

- LinkBrowser in Redirect record (pageUid = 0) shows “Foo” in the page browser as the overrides template is used
- any other LinkBrowser (in page context) shows default page tree in browser

Actual:

- the reset of the overrides template isn’t triggered. “Foo” is always shown.

The view is rendered in typo3/cms-backend/Classes/View/BackendViewFactory.php:73 expecting an “id” parameter in the request. This parameter isn’t available in a “wizard/link/browse” context as the page id is provided in P[pid]=161 parameter

Author Nicole Hummel
Created 05/23/24, 09:39
Updated 09/01/25, 14:36
Bug
New Orphaned Workspaces TYPO3 CMS 13

#107354 Preview in multi-site not using the base url of the current tree in draft mode

We have a TYPO3 instance with four different sites in it – each with their own domain. Some editors are only allowed to edit content in a draft workspace.

So let’s say we have domain1.tld, domain2.tld, … for each tree.

Now the (draft restricted) editor logs in via domain1.tld/typo3 and starts editing. The editor is not limited to one tree. It’s possible for them to edit pages/ content in every tree.

After editing something in the tree of domain1.tld, the editor decides to edit something in the tree of domain4.tld. To make sure everything looks promising, he clicks the “View webpage” button.

Now, that will just open a “white” page because the generated preview link does not use the base url of the current site. Instead it opens the preview with base url, from where the editor logged in to the system. In this example that would be something like:

https://domain1.tld/typo3/workspace/preview-control?token=fa5bd244730de1a2dbed600c20e47694fe03e301&id=123

instead of

https://domain4.tld/typo3/workspace/preview-control?token=fa5bd244730de1a2dbed600c20e47694fe03e301&id=123

—-

This only happens to editors who are locked to a draft workspace. Editors who are allowed to edit in LIVE won’t have these problems. In LIVE workspace the “View webpage” button always opens the correct base url, regardless which domain the editor used to login into the backend before.

Author Axel Böswetter
Created 08/29/25, 14:22
Updated 08/29/25, 14:22
Bug
New Orphaned Backend API TYPO3 CMS 14

#107344 Deleting page results in 503: "You don't have access to this page" if switch user to non-admin user

It looks like the page can be deleted but the currently selected page in page tree is still selected and this results in the error.

This problem is not reproducible with older versions, e.g. v12. Also, it is not reproducible as admin user.

Reproduce

Using latest TYPO3 instance from git repo “main” branch (v14.0.0-dev) and “styleguide” extension.

1. With styleguide extension create “styleguide frontend demo” test pages
2. If BE user does not exist, add BE user
3. Switch to BE user
4. Create test pages or test page
6. Jump to new page in page tree
7. Try to delete page by using context menu “Delete” in page tree

Result:

> 503
> Oops, an error occurred!
> You don’t have access to this page

However, page is deleted. So I assume it gets deleted, but current page is now the deleted page.

Author Sybille Peters
Created 08/28/25, 16:24
Updated 08/28/25, 16:24
Feature
Accepted Orphaned Backend User Interface

#106098 Create default backend usergroups by GUI

Currently there is no way to create the default backend user groups that can be created via

bin/typo3 setup:begroups:default -g Both

From the TYPO3 backend. As creating backend user groups is a complicated task, expecially for new administrators I would suggest to
create a button “Create default user groups” if no user groups or none of those names have been created yet (see also https://forge.typo3.org/issues/105877)

This would make it easier for new administrators to get started using backend editors. It could prevent new administrators from “Granting administrative rights because they are unable to create a functioning backend editor”

Author Lina Wolf
Assigned to Sven Liebert
Created 02/06/25, 13:03
Updated 08/27/25, 07:46
Bug
New Orphaned TypoScript TYPO3 CMS 13

#107308 PageTSconfig won't get inherited to site if included in rootline before site

  1. introduced the option to include PageTSconfig to sites. However it seems that this also removes the option to inherit PageTSconfig from higher up pages in the rootline if those aren’t part of a site (i.e. defining a site/rootpage drops all includes on pids above).

I have a page tree where I include PageTSconfig (via pages.tsconfig_includes) above the actual sites/rootpages (e.g. have multiple parent “template” or “configuration” nodes and the actual Sites below that). The PageTSconfig is included in the parent nodes correctly, but on the actual sites/rootpages below, the formerly included PageTSconfig is not available.

So the sitestructure is like

A (PageTSconfig definition)
`A1
 `A1.1 (Site, Rootpage)

If I look into Module PagesTSconfig / Included pageTSconfig in 13LTS it doesn’t show the entries for pagesTsConfig-page-<pid of page A>-includes-0 which were available in 12LTS. In that place the new “site pageTSconfig include” is there, but the former includes are missing, which would be expected to be there as well.
It seems somewhere in https://review.typo3.org/c/Packages/TYPO3.CMS/+/83586/21/typo3/sysext/core/Classes/TypoScript/IncludeTree/TsConfigTreeBuilder.php#176 there is a hiccup which focusses on sites and site subpages, but leaves out the parent pages of a site.

(Obviously I can refactor away from inheritance to site include, but nevertheless this seems like there is an bug).

Author J. Peter M. Schuler
Created 08/18/25, 13:48
Updated 08/23/25, 15:38
Bug
New Orphaned Backend User Interface TYPO3 CMS 12

#102352 The modal-backendloginform must ask for the real user's passwords in SwitchTo user mode

Problem/Description

  1. login with your admin user
  2. switch to another user
  3. do nothing and wait until the refresh-login modal (t3js-modal-backendloginform) appears
  4. It clearly asks for the switchTo user’s password

Acceptance Criteria

You don’t know the password of any other user (or any test-editor user) in good conditions. Therefore my suggestion:

  • respect the switchTo mode
  • adopt the wording which informs the editor about “you are still in switch to but we need the password for your real user”
Author Josef Glatz
Created 11/09/23, 04:48
Updated 08/21/25, 09:21
Bug
New Orphaned RTE (rtehtmlarea + ckeditor) TYPO3 CMS 12

#105749 Unable to use "&"/ampersand character within URL parameters of "rte_ckeditor" link wizard/popup

When trying to use the “buttons.link.queryParametersSelector” optin within the “rte_ckeditor” extension, its possible to add custom parameters to a URL. But is seems not to be possible to add a “&” character. Using the ViewHelpers “uri.typolink” or “link.typolink”, the result is always a mixed up URL.

Entered data in the “queryParametersSelector” field within the backend:
test=begin&end

Output of saved (raw) data within the fronend:
t3://page?uid=123 – - – test=begin&end

Result after using the ViewHelper/s:
/testpage?end=&test=begin&cHash=c1234567890123456789012345678901

That of cause was expected, because the string “&end” is treated as an additional parameter “end”. But trying to use the URL encoded form “%26” of the “&” character is not possible: After commiting the added URL parameters by exiting the wizard, the “%26” character is immediately replaced by the standard “&” character.
So it is not possible to enter and save the parameter in the already encoded form “test=begin%26end”.

What would be the correct way to use “&” characters within URL parameters? In the meantime, is there a workaround?

Author Stefan Wagler
Created 12/03/24, 12:38
Updated 08/20/25, 09:20
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 13

#107148 DataHandler value check does not consider overrideChildTca in fields of type inline

When the DataHandler checks values and removes invalid values from the field array before updating the database row, it only checks against the TCA configuration of the original table. While it does respect column overrides of different types, it does not take into account that a configuration could have been altered in an inline context using overrideChildTca.

For example, say I have a table “foo” with a required “endtime” field:

Configuration/TCA/foo.php


'endtime' => [
  'exclude' => FALSE,
  'label' => 'LLL:EXT:core/Resources/Private/Language/locallang_general.xlf:LGL.starttime',
    'config' => [
      'type' => 'datetime',
      'format' => 'datetime',
      'required' => TRUE,
      'size' => 20,
    ]
]

.. and another table “bar” with a field “foos” where I want to set required to false:

Configuration/TCA/bar.php

'foos' => [
  'config' => [
    'type' => 'inline',
    'foreign_table' => 'foo',
    'foreign_field' => 'bar',
    'overrideChildTca' => [
      'columns' => [
        'endtime' => [
          'config' => [
            'required' => FALSE
          ]
        ]
      ]
    ]
]

Expected result would be that now the field in the inline records of type “foo” within “bar” are no longer required and can be left empty.

Actual behaviour:

This works in regards of form rendering and client side validation. You can leave the fields empty and the record can be saved.
However, if you have set a value and then try to remove it by emptying the “endtime” field, then after saving, the previous value will remain unchanged. You can overwrite it with another value but not empty.

I’ve digged a bit deeper in the DataHandler class and it seems that this happens because \TYPO3\CMS\Core\DataHandling\DataHandler::checkValue_SW checks the input values against the TCA configuration of the table and removes invalid values.

I would guess that to fix this, \TYPO3\CMS\Core\DataHandling\DataHandler::resolveFieldConfigurationAndRespectColumnsOverrides would have to be changed in a way that also respects inline contexts, because right now it only gets its configuration from the current table itself.

My workaround right now is to just use another type explicitly for that use case in the original table and use columnsOverrides in the type configuration. That limits the types usable in the inline field though.

Author Thomas Prangenberg
Created 07/25/25, 16:56
Updated 08/18/25, 06:41
Bug
Under Review Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#100097 Long external parameters causes TYPO3 crash in Extbase Routing Enhancer

If an external parameter is added to a page, which is resolved using an Routing-Enhancer, this might cause a crash, if the parameter name is too long.

Steps to reproduce:

You need a page with configured Extbase Plugin Enhancer.
If you call this page it should work in the frontend with the normal output of the extbase plugin used.
If you call this page with a manipulated URL (add a long parameter, e.g. ?L_Instagram_FeedAd_EstimatedAdRecall=whatever you see an error in the frontend.

I expect the non-TYPO3 parameter is simply ignored.

I have stripped this down to https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Routing/Enhancer/VariableProcessor.php#L61

if the parameter is longer than 31 chars and it’s not a valid hash, the OutOfRangeException is throwed, which leads to an error in the frontend.

As for shorter parameters the input argument is simply returned, I suggest to change the method resolveHash to return the value from $this->hashes, if the key $hash exists, and $hash otherwise.

This would make the method shorter and more stable.

I’m unsure, if this might have unwanted side effects.

I found this in a TYPO3 10.4.36 instance, but the method and the error is also in current main. It seems not related to the PHP version.

Author Marc Willmann
Created 03/06/23, 12:27
Updated 08/15/25, 12:49
Feature
New Orphaned Site Handling, Site Sets & Routing

#89552 Redirect URLs with trailing slashes to their canonical non-trailing-slash URL (or the other way around)

I noticed that in TYPO 9 LTS, the following two URLs will show the same page:

Live example:

For various reasons (including SEO and web analytics, https://searchfacts.com/url-trailing-slash/ ) it would be great to have only one of these URLs be canonical, while a request to the other URL results in a 301 Redirect to the canonical URL.

TYPO 9 seems to generate URLs without a trailing slash (which I also prefer). (Pre-TYPO 9) realurl seems to generate URLs with a trailing slash.

Author Gerrit Hübbers
Created 10/30/19, 18:12
Updated 08/14/25, 10:05
Bug
Accepted Orphaned Frontend TYPO3 CMS 9

#88631 Page type parameter is ignored in POST requests/parameters

Since TYPO3 9 the page type parameter is ignored when set in POST parameters (for example from a form field). If it’s set in GET parameters (query string) everything is fine. This is because the PageArguments object is instantiated at several points with only the type parameter from the query params (for example in \TYPO3\CMS\Frontend\Middleware\PageResolver) not respecting the POST parameters. On the other hand the TypoScriptFrontendController is instantiated in \TYPO3\CMS\Frontend\Middleware\TypoScriptFrontendInitialization with GeneralUtility::_GP(‘type’) handling both POST and GET parameters. This is inconsistent behaviour and should be fixed as soon as possible. Or is this intended and not a bug?

Author DMK E-BUSINESS GmbH
Created 06/26/19, 10:19
Updated 08/12/25, 10:50
Task
New Orphaned Backend User Interface TYPO3 CMS 12

#106913 Add locale to page module tooltips on "Link to External URL" pages

The tooltip in the Page module shows the default language content. I understand that the page module itself is language-agnostic.
As an editor, my point of view is the “current” language that is (possibly) displayed in the content section.
Regarding the target URL field of the “Link to External Page” page type they will eventually differ and that’s confusing to me as I don’t see that the link refers to the base language.

Proposal: Can we either show no URL in the tooltip or add the URL locale as prefix?

Author Tibor Legat
Created 06/19/25, 12:36
Updated 08/11/25, 07:17
Feature
New Orphaned Fluid

#107090 f:link.typolink removes entire tag when no valid link target can be generated, causing CSS class loss

The <f:link></f:link> ViewHelper completely removes the entire link tag when it cannot generate a valid link target (e.g., when linking to a hidden page). This behavior causes CSS classes and other attributes to be lost, potentially breaking the layout and styling of frontend elements.

<!-- Input -->
<f:link.typolink class="test" parameter="{linkToHiddenPage}">
   <span>Link Text</span>
</f:link.typolink>

<!-- Output when page is hidden or inaccessible -->
<!-- Only slot content is rendered - entire link is removed -->
<span>Link Text</span>

Impact

  • Layout breaks: CSS styling fails when expected classes are missing
  • Unpredictable behavior: Works in 99% of cases but fails when pages are hidden/inaccessible
  • Manual workarounds required: Developers need to implement explicit condition checks

*Possible solution:*
Render an tag with a placeholder href.
This causes CSS styling like “a.test” to be valid and simply replaces the incorrect link with a “#” placeholder.

<a href="#" class="test">
   <span>Link Text</span>
</a>
Author Felix Ranesberger
Created 07/14/25, 08:28
Updated 08/08/25, 17:46
Feature
New Orphaned Backend User Interface

#107218 Allow manually changing filename in case of conflict

Currently, if a file is uploaded that already exists, it is possible to resolve the conflict by renaming the file. However, unlike almost everywhere else, the user cannot change the filename manually. Instead, a suffix _NN is appended automatically.

To make this process more user-friendly, the user should be given a possibility to manually change the filename. This would also need an automated check if the new filename exists already.

Prior art: There is #64363, but that is classified as a bug, so I guess creating a feature-ticket is probably justified.

Author Andreas Wolf
Assigned to Andreas Wolf
Created 08/07/25, 18:35
Updated 08/07/25, 18:35
Bug
New Orphaned Localization TYPO3 CMS 12

#106774 Translate button not shown when default language doesn't have content

Steps to reproduce:
  1. Create a blank TYPO3 Site
  2. Configure default language
  3. Configure two additional languages
  4. Create a page in default language
  5. Translate page to the two additional languages
  6. Create content in one additional language

Expected: See “Translate” button in the other additional language, offering to translate from the existing content of the other additional language.
Actual: No “Translate” button.

Adding content to the default language will enable the “Translate” button. Editors are able to select the additional language as base for translation.

The value of l18n_cfg doesn’t affect the situation.

Use Cases:
Some websites have a lot of languages, sometimes for multiple countries. There editors need to be able to translate from one Language (e.g. French) in one Country (e.g. France) to the same language (French) in another country (e.g. Switzerland).

This is probably closely related, if not a duplicate of #76274

My investigation showed that TYPO3\CMS\Backend\View\BackendLayout\ContentFetcher->getTranslationData() always only checks for default language via hard coded value 0.
The fluid template will use the outcome to determine whether to show the button in EXT:backend/Resources/Private/Partials/PageLayout/LanguageColumns.html.

I guess the logic needs some tweaking to really determine if there is still anything left for translation, respecting connection – free mode, etc. and the possible sources of translations.

Author Daniel Siepmann
Created 05/27/25, 07:09
Updated 08/04/25, 13:09

Showing results 1026 to 1050 of 1561