Showing results 876 to 900 of 1561

Feature
New Orphaned felogin

#106761 Add PSR-14 Event BeforePasswordRecoveryEvent to allow validation before password reset email is sent

Currently, the EXT:felogin extension provides a password recovery workflow via the PasswordRecoveryController::recoveryAction() method. However, there is no way to intercept or validate the request before the recovery email is triggered.

This limitation makes it difficult to implement common requirements such as:

CAPTCHA validation to prevent automated abuse

Custom rate limiting or throttling logic beyond what is built-in

Audit logging or analytics for recovery attempts

Custom business rules before proceeding (e.g., blocklisted emails)

While TYPO3 already provides the SendRecoveryEmailEvent (dispatched within RecoveryService::sendRecoveryEmail()), it occurs too late in the process — after:

The user has already been looked up in the database

A recovery hash has been generated and saved

The process has committed to sending the email

This makes SendRecoveryEmailEvent unsuitable for early validation tasks. A new BeforePasswordRecoveryEvent dispatched at the beginning of recoveryAction() would allow integrators to cancel or modify the workflow before any sensitive actions occur.

This would align with other PSR-14 events in TYPO3 (e.g., AfterUserLoggedInEvent, PasswordChangeEvent) and improve the security and extensibility of the password recovery process.

Author Lina Wolf
Created 05/26/25, 06:10
Updated 04/21/26, 11:23
Feature
New Orphaned Caching

#106734 Allow plugins to set storage pages and tables to consider for page cache lifetime

As far is i can tell from the changelogs etc. this is not yet possible:

There is a TS config option to let the frontend rendering respect the visibility of records from specific tables when a page is rendered and put to cache: https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/TopLevelObjects/Config.html#confval-config-cache

One of my clients is using news plugins a lot to tease articles that relate to the current content. But if i want to influence the cache for these pages, i’d have to put all of them to the TypoScript config. Any newly created plugin then is also not take care of automatically —> thus i now configured the cache for all pages (even if they do not have a news plugin) to respect the visibility.

It would be great if a plugin / code could tell the frontend rendering to use table xyz from storage pages 1,2,3,recursive to be considered when the cache entry is created.
A plugin could surely take care of it all on its own and influence the cache timeout, but it would be great to have a simple api that mimics the behaviour of the TS setting

Author Andreas Kießling
Created 05/20/25, 13:45
Updated 04/21/26, 11:23
Feature
New Orphaned Install Tool

#106222 Offline Mode / externally maintained

There are some TYPO3 users who manage their instances centrally externally, sometimes even in read-only systems or without backend internet access, as they are located in a DMZ.

For these instances, it is important that no hard errors are thrown when the TYPO3 version endpoint cannot be reached, for example, when the backend tries to fetch versions via cURL.

Additionally, the system should only display an informational message and prevent editing when files cannot be written, instead of throwing a hard error.

Perhaps the feature-toggle mechanism could actually be used to implement this functionality. With feature toggles.

For example, a toggle could ensure that when attempting to fetch the versions, instead of a hard error, an informational message is displayed if the endpoint is unreachable. Similarly, editing files in a ‘read-only’ mode could be disabled via a toggle, without overloading the instance.

Author Christian Rath-Ulrich
Created 02/20/25, 20:27
Updated 04/21/26, 11:23
Feature
Needs Feedback Orphaned Backend API

#106022 implement CRUD for backend usergroup permissions

I need a usergroup which should be able to edit a content element but neither delete it nor be able to create a new content element.

As I see it, the TYPO3 backend user management is not making this possible. The only options I have for page content is
- no access
- read
- read and write

When chosing the last option a user can write but also delete and create new content – which is not what I want.

It would be better to implement CRUD here, so that for user groups these options are available:
- no access
- read
- update
- delete
- create

It would also be desirable to have it not only for page content in general but also for each content element in particular.

But maybe I overlooked something here and it also can be done via USER TSconfig. Unfortunately I found nothing in the documentation.

Author Michael Perlbach
Created 01/29/25, 23:02
Updated 04/21/26, 11:23
Bug
New Orphaned Database API (Doctrine DBAL) TYPO3 CMS 12

#109610 Table in external not created if existing in default connection

Steps to reproduce:

  • Default database with no migrations needed
  • Add additional database connection with a table mapping. (e.g. fe_sessions)
  • Run DB compare

Expected:

Table will be created in additional DB

Actual:

No change is suggested.

Author Markus Klein
Assigned to Stefan Bürk
Created 04/16/26, 16:05
Updated 04/16/26, 19:41
Bug
Accepted Orphaned Frontend TYPO3 CMS 13

#15984 menu.showAccessRestrictedPages doesn't replace link for "include subpages"

When creating a menu with showAccessRestrictedPages set to any PID, links to pages that inherit a usergroup restriction (“include subpages” set on a parent page) won’t be substituted.

function changeLinksForAccessRestrictedPages(..) @ class.tslib_menu.php is calling $GLOBALS[‘TSFE’]->checkPageGroupAccess($page) which itself does not traverse the pagetree to check if a parent page has the field “extendToSubpages” set true.

Same problem may occour when using config.typolinkLinkAccessRestrictedPages for typolinks, but I have not tried yet.
(issue imported from #M3129)

Author Wolfgang Sassik
Created 04/05/06, 03:07
Updated 04/15/26, 09:44
Bug
New Orphaned Backend User Interface TYPO3 CMS 7

#81478 Datepicker in backend - unlogical behaviour with keyboard navigation

In the TYPO3 backend you have a datepicker in the date fields. When you click in the input field and change the day manually (backspace and type new day manually) and then want to get to the month using the arrow keys, the day flips back to the initial number. The arrow key is used to change the day in the datepicker here. So no “normal” navigation in the input field is possible anymore. I have a website with many (mid-aged) editors and they find this really confusing.

I think it would make sense to deactivate the “keyboard navigation” in the datepicker. Or don’t allow keyboard interaction in the input field itself – forcing the editor to use the datepicker.

Author Tobias Wollender
Created 06/06/17, 10:16
Updated 04/15/26, 09:05
Bug
Needs Feedback Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 13

#107997 Saving changes in Site Configuration breaks config

For example, when changing the domain when going live with a new site in our multi site installation, the config.yaml gets corrupted. Therefore we always edit the config.yaml file directly, and automatic cache clearing does not happen.
Example: Change from https://temporary-domain.dk to https://live-domain.dk

config.yaml before saving:

base: 'https://temporary-domain.dk'
baseVariants:
  -
    base: '%env(DKM_INSTANCE_HOST)%/3skursus/'
    condition: 'applicationContext != "Production/Live"'
rootPageId: 1061
pids:
  news:
    storage: '1062'
    detail: '1063'
  events:
    storage: '1064'
    detail: '1065'
  intranet:
    storage: '1082'
    root: '1081'
  mail:
    storage: '3909'
websiteTitle: '3S Kursus'
imports:
  -
    resource: 'EXT:mspconfig/Configuration/Site/Default.yaml'

config.yaml after saving:

DKMYouTube:
  channels:
    - __UNSET
base: 'https://live-domain.dk'
baseVariants:
  -
    base: 'https://71061.dkmweb4v12.ddev.site'
    condition: 'applicationContext != "Production/Live"'
  -
    base: dkmweb4v12.ddev.site/3skursus/
dynamic_be_groups:
  config_name:
    conditions:
      -
        value: '73909'
env_config_key: 2019old
env_instanceHost: dkmweb4v12.ddev.site
env_typo3_context: Development
env_typo3_path_app: /var/www/html
errorHandling:
  -
    errorCode: 404
    errorContentSource: 't3://page?uid=71061'
  -
    errorCode: 403
    errorContentSource: 't3://page?uid=71061'
languages:
  -
    languageId: 0
    solr_core_read: dkmweb4_dk
matomoWidgetsActiveWidgets: ''
matomoWidgetsIdSite: ''
matomoWidgetsPagesNotFoundTemplate: '404/URL = {path}/From = {referrer}'
matomoWidgetsTitle: ''
matomoWidgetsTokenAuth: ''
matomoWidgetsUrl: ''
pids:
  news:
    storage: '1062'
    detail: '1063'
  events:
    storage: '1064'
    detail: '1065'
  intranet:
    storage: '1082'
    root: '1081'
  mail:
    storage: '3909'
rootPageId: 1061
routeEnhancers:
  Login:
    limitToPages:
      - 1061
  Cookie:
    limitToPages:
      - 1061
  EventNewsPlugin:
    limitToPages:
      - '1065'
  NewsPlugin:
    limitToPages:
      - '1063'
solr_path_read: null
websiteTitle: '3S Kursus 2'
imports:
  -
    resource: 'EXT:mspconfig/Configuration/Site/Default.yaml'

wanted config.yaml:

base: 'https://live-domain.dk'
baseVariants:
  -
    base: '%env(DKM_INSTANCE_HOST)%/3skursus/'
    condition: 'applicationContext != "Production/Live"'
rootPageId: 1061
pids:
  news:
    storage: '1062'
    detail: '1063'
  events:
    storage: '1064'
    detail: '1065'
  intranet:
    storage: '1082'
    root: '1081'
  mail:
    storage: '3909'
websiteTitle: '3S Kursus'
imports:
  -
    resource: 'EXT:mspconfig/Configuration/Site/Default.yaml'
Author Stig Nørgaard Færch
Assigned to Garvin Hicking
Created 11/06/25, 14:45
Updated 04/15/26, 08:25
Bug
Accepted Orphaned Backend User Interface TYPO3 CMS 13

#108288 The heading hierarchy in the create folder modal in filelist is incorrect.

In the “Create new folder” dialog, the main heading is marked as H1. Immediately below, the entry “Fileadmin/(auto-created)…” is marked as H4. This skips levels and violates the expected, programmatically discernible hierarchy.

Per WCAG, the number of headings at the same level is not limited; multiple H4s under an H3 are allowed if the hierarchy is consistent and semantically correct. Here, the heading structure must be adjusted so no levels are skipped (e.g., H1 → H2 → H3 …).

The goal is a semantically correct structure that works well with assistive technologies, without changing the visual appearance.

Current issue: H1 “Create new folder” followed by H4 “Fileadmin/(auto-created)…”.
Expected: No H4 right after an H1; use H2 (or H3) instead, depending on the logical structure.
Multiple same-level headings are allowed if properly nested in the hierarchy.
Optionally recommended structure in the modal:

H1: Dialog title (or—if the backend already provides a page-level H1—start with H2 in the modal)
H2: Section heading (e.g., “Location” / “Storage”)
H3/H4: Sub-items within that section (e.g., “fileadmin/(auto-created)…”)

Author Christian Jung
Created 11/24/25, 09:53
Updated 04/14/26, 09:41
Bug
New Orphaned Frontend TYPO3 CMS 14

#109571 create site during setup creates static TS for FE display

when using the CLI setup of a new instance and telling it to create a simple site, a root page with a CE is created, as well as a site config and some Typoscript to display it.
Sadly, the created TS doesn’t care for any created CEs, but displayes a static text. This is very confusing, because changing the content of the CE does not change the displayed content in FE at all.
It would be way better to generate TS to read from colPos of the generated BE layout.

Author Anja Leichsenring
Created 04/14/26, 04:28
Updated 04/14/26, 05:17
Bug
New Orphaned Frontend TYPO3 CMS 12

#105889 Problem with ContentObjectRenderer select and pidInList = root

Hello,

I am using this TypoScript from the documentation https://docs.typo3.org/permalink/t3tsref:select-pidinlist:

10 = CONTENT
10 {
   table = sys_category
   select {
      pidInList = root,-1
      selectFields = sys_category.*
      join = sys_category_record_mm ON sys_category_record_mm.uid_local = sys_category.uid
      where.data = field:_ORIG_uid // field:uid
      where.intval = 1
      where.wrap = sys_category_record_mm.uid_foreign=|
      orderBy = sys_category_record_mm.sorting_foreign
      languageField = 0 # disable translation handling of sys_category
   }
}

but it doesn’t work.

The problem seems to be in typo3/cms-frontend/Classes/ContentObject/ContentObjectRenderer.php. In the method getQuery(), starting on line 5138, the program calls in line 5207 the method $this->getTypoScriptFrontendController()->sys_page->getPageIdsRecursive(). This method transforms with

$pageIds = array_map('intval', $pageIds);

all entries in pidInList in integers.

Back in ContentObjectRenderer.php on on line 5217 the programm calls $this->getQueryConstraints(), which checks on line 5463 if pidInList contains ‘root’ but that got already transformed into the integer 0. So the example from the documentation doesn’t work.

Author Thorsten Lübkemann
Created 01/06/25, 11:25
Updated 04/13/26, 17:18
Bug
New Orphaned Extbase TYPO3 CMS 13

#109524 $this->redirect() in an Extbase Controller should accept a Plugin Name

If after getting rid of Switchable Controller Actions you split up your formerly one plugin into several plugin it becomes neccessary to redirect beetween differnt Plugins, as those will be contained in the generated URL parameters.

Currently you have to override $this->redirect() in the controller or return a cutom RedirectResponse.

Author Lina Wolf
Created 04/09/26, 07:18
Updated 04/11/26, 10:13
Feature
New Orphaned Form Framework

#109487 Enhance multiple file upload for EXT:form

With the new possibility (described at https://github.com/typo3/typo3/commit/8357227e46) it’s finally possible to allow multiple files and to allow vistiors to remove the files.

File selection: If the upload of multiple files is allowed it is only possible to select more than one if they files are in the same folder (at least on Windows with CRTL+selection). If a user wants to select a second file after the dialog is closed the second call of the dialog and selction of another file replaces the first.

Removing files: The also new possibility to remove files is only accessible if a summery page is in use. The user has to navigate forth and back in order to delete the selected files (this is more erratic than self-evident). In my opinion the remove-checkox needs to be appeare immediately after the file shows up in the form. From a user point of view it is disturbing that marking the ckeckbox is not followed by any action. I think it would be much better to use a remove-button that instantly removes the file, with a visual feedback to the user.

Author wini2 no-lastname-given
Created 04/03/26, 19:53
Updated 04/06/26, 17:08
Feature
Under Review Orphaned Form Framework

#109341 Allow form labels to be translated via "LLL:" prefixed keys

The form framework already offers a possibility to define translations for a form and its labels and options: https://docs.typo3.org/permalink/typo3-cms-form:concepts-frontendrendering-translation-formdefinition

This already brings some flexibility and allows to set a label by element identifier (e.g. “myfield”) or element type (e.g. “Text”) and it’s even possible to override labels only for specific forms by using the form definition identifier:

  • <formDefinitionIdentifier>.element.<elementIdentifier>.properties.<propertyName>
  • element.<formElementIdentifier>.properties.<propertyName>
  • element.<elementType>.properties.<propertyName>

But I there is one thing, I miss:

It would be awesome to be able to define locallang labels directly in the form definition. There might be cases, when several fields in the same form needs the same label. An example might be the addresses for shipping and for billing. Both of them need fields like “Postal code” and “City”. With the actual behavior, I would need to have redundant entries in my translation file for shippingStreet and billingStreet.

If it would be allowed to directly set LLL:EXT:my_extension/Resources/Private/Language/form.xlf as form labels in my form definition, I could avoid redundant entries in the translation files.

Example:

# street as part of the shipping address
-
  defaultValue: ''
  type: Text
  identifier: shippingStreet
  label: 'LLL:EXT:my_extension/Resources/Private/Language/form.xlf:street'
  properties:
    fluidAdditionalAttributes:
      required: required
      autocomplete: address-line1
  validators:
    -
      identifier: NotEmpty

# street as part of the billing address
-
  defaultValue: ''
  type: Text
  identifier: billingStreet
  label: 'LLL:EXT:my_extension/Resources/Private/Language/form.xlf:street'
  properties:
    fluidAdditionalAttributes:
      required: required
      autocomplete: address-line1
  validators:
    -
      identifier: NotEmpty
Author Albrecht Köhnlein
Created 03/24/26, 11:35
Updated 04/02/26, 15:02
Feature
Under Review Orphaned Dashboard

#104966 Introduce dashboard widget for duplicated files

I worked on the extension editor-widgets and want to contribute a widget from this extension to the EXT:dashboard.

This widget will show a list of files which are identical in terms of their sha1 hash. With that information, the users are able to cleanup file-mounts for files which are uploaded multiple times.

Author Ulrich Mathes
Created 09/13/24, 20:56
Updated 03/30/26, 10:34
Feature
Under Review Orphaned Link Handling & Redirect Handling

#103032 Redirects Integrity Check: Find hidden targets

As a TYPO3 user, I would like the Integrity check to mark redirects to hidden pages.

Author Guido Schmechel
Created 02/04/24, 10:16
Updated 03/28/26, 13:08
Feature
New Orphaned System/Bootstrap/Configuration

#109396 Reactions from file configuration

The Reactions extension currently allows creating reactions as database records. Extensions can register reaction types.

Various disadvantages arise from the DB-based management:

1. No automatic deployment of new/changed Reactions: an admin must create/update reactions manually after deploying the related code. This can lead to delays or errors in the meantime.
2. Risk of outdated/unsynced Reactions in multiple environments: in addition to production there are often other environments like staging, testing, etc. These must be kept in sync manually to ensure reliable and predictable behavior.
3. Harder automated tests due to unknown secret: secrets of Reactions are known only once on creation. Writing realistic automated tests for existing Reactions requires replacing the secret with a static, predefined value.

Given these facts it would be useful if Reactions could also be registered via file configuration. This is similar to form definitions which can be defined as files and (since #108653) as database records. Other examples are purely file-based like site configurations. All of these have in common that they are basically code/infrastructure/setup without actual user content.

Author Mathias Brodala
Created 03/27/26, 08:57
Updated 03/27/26, 16:47
Bug
New Orphaned Backend API TYPO3 CMS 13

#109335 FormProtection prevents form validation after cleaning session token.

While using the Form Protection system, it becomes impossible to validate a form if the `clean()` function is called.

Class : typo3/cms-core/Classes/FormProtection/AbstractFormProtection.php
https://github.com/TYPO3/typo3/blob/13.4/typo3/sysext/core/Classes/FormProtection/AbstractFormProtection.php#L51

This function “clean” assigns the value ‘’ (empty string).

    public function clean()
    {
        $this->sessionToken = ''; <---- here
        $this->persistSessionToken();
    }

However, generating a new session token becomes impossible because of the code in the `getSessionToken` function, which checks for the presence of a session token using the `??` test.

    protected function getSessionToken()
    {
        $this->sessionToken = $this->sessionToken ?? $this->retrieveSessionToken();
        return $this->sessionToken;
    }

If the session token is ‘’ (empty string), the `??` test is valid and does not retrieve a new session token.

Possible solutions:
- set null in clean function :

$this->sessionToken = null;

- use ifempty test

if (empty($this->sessionToken)) {
   $this->sessionToken = $this->retrieveSessionToken();
}
Author Olivier SC
Created 03/24/26, 08:35
Updated 03/26/26, 21:32
Feature
Under Review Orphaned Backend API

#109332 Introduce AfterHistoryDataCollectedForRecordEvent PSR-14 event in RecordHistory

Problem

`RecordHistory::getHistoryDataForRecord()` collects history entries for a given record, but there is currently no way for extensions to augment or extend this history data without overriding the class via Xclass. This is limiting in cases where related records are linked through a custom foreign-key field rather than pid. For example, records which are referenced over an inline field are invisible in the history view because the core logic only follows pid-based sub-entries.

Solution

Introduce a new PSR-14 event `AfterHistoryDataCollectedForRecordEvent` dispatched at the end of `RecordHistory::getHistoryDataForRecord()`, after all core history data has been collected but before the result is sorted and returned.

Impact

  • New event class: TYPO3\CMS\Backend\History\Event\AfterHistoryDataCollectedForRecordEvent
  • Small, non-breaking change to RecordHistory::getHistoryDataForRecord()
Author Amir Arends
Created 03/24/26, 07:23
Updated 03/24/26, 08:42
Task
New Orphaned TYPO3 CMS 14

#109333 Use alternative markup for icons in ModifyButtonBarEvent

I’m using a ModifyButtonBarEvent event listener to add a button. This button has an svg icon (not sprite). It does not seem possible to set an alternative markup in this context.

I need the inline context because the icon uses currentColor to match the dark mode option.

My workaround is to set the markup to the alternative markup:

$button = $this->componentFactory->createGenericButton();
$icon = $this->iconFactory->getIcon('page-feedback-thumbs-up-regular');
$icon->setMarkup($icon->getAlternativeMarkup(SvgIconProvider::MARKUP_IDENTIFIER_INLINE));
$button->setIcon($icon)

Maybe svg icons should be rendered generally inline in that context?

Author Tobias Jungmann
Created 03/24/26, 08:24
Updated 03/24/26, 08:24
Bug
Under Review Orphaned Localization TYPO3 CMS 12

#102345 Copy/Move pages with existing translation into another site with different language setup results in orphaned problematic page translation records

Problem/Description

Steps to reproduce

  • set up a TYPO3 instance with 2 TYPO3 site configs with different language setup
    • site a: default:en (0) + translation:de (1)
    • site b: default:de (0) + translation:en (2)
  • Create a subpage in site a and add a translation
  • Copy the created subpage into site b
  • The translated page translation is now “somehow” orphaned as you can only reach it (in TYPO3 12) via the Backend Live Search component (e.g. via #page:uidOfTranslation or the title)

Resulting problems

  • the editor does not know what’s going on
  • the editor maybe thinks, that TYPO3 is dumb due to the fact, that the copied records are not changed (default to translation and vice-versa)
  • or the editor get’s not stopped by TYPO3 while trying to copy/move a record to another TYPO3 site with a different language setup
  • there are scenarios if there are relations like FAL and/or CEs which results in datalost if the orphaned translation get’s deleted via the TYPO3 backend AKA DataHandler
  • we also had wrong/problematic speaking urls / slugs. (but this is something I did not investigated when the problem occurs a year ago)

Notes

  • in our scenario the problem seems to be occured in TYPO3 9 or 10 when an editor copied a subpagetree from one site to another site. In our scenario, those orphaned page translation records where easily findable via SELECT uid, pid, sys_language_uid, l10n_source, l10n_parent, slug, title, hidden,cruser_id, deleted FROM pages WHERE deleted = 0 AND l10n_parent != l10n_source;
  • in 2022, @benni had also the same scenario in his real life projects in B13
  • we try to disable copying/moving from one site to another site in this project with hooking into the DataHandler (I will add the workaround code when done/finished)

ToDo(s)

IDK so far.

  • stop copy/move from one site to another site via DataHandler when die language setup is not the same betwwen sites
  • add a modal with a wizard where the editor have the possibilities to decide what to do
  • or introduce a completely new way of copying empty structures. e.g. one wants to copy just the skeleton of a page with empty elements but with correct settings for backendLayout and so… (you see: beLayout can also be differently configured in another site, so one might say just stop copying from site to site :-) )

Acceptance Criteria

  • prohibit problematic copy/move or improve this as a feature in the TYPO3 core (TBD)
  • document the actual problem until it get’s fixed (or not fixed)

—-

Related external links

Author Josef Glatz
Created 11/07/23, 16:53
Updated 03/23/26, 11:36
Task
New Orphaned Fluid TYPO3 CMS 14

#109307 Deprecate fluid templates

We need to determine the best way to deprecate a fluid template.

Author Josua Vogel
Created 03/20/26, 15:50
Updated 03/20/26, 15:50
Task
New Orphaned Backend User Interface TYPO3 CMS 14

#109303 Improve Wizard steps with a "Quick Finish" / "Fast Forward" / "Accept defaults" / ... methodology

The new form, page and localization wizards can be very verbose.

The second-to-last-step is only a “summary” of all actions, the last step contains the success messages. And then the modal also needs to be closed.

That means there are three steps (that can be ENTER-multitapped) that are kind of unneeded.

For the page creation wizard (especially the drag-drop variant that starts in step 3), it would be very helpful to have the ability to skip through the form very quickly, to create stubs of pages to be filled later.

In the current implementation, the missing focus of the first field with a required field (page title) also slows down the process, and missing validation. Both will be adressed as part of the feature.

For future reworks of the modal process it would be great to have a functionality that “skips all steps that have no mandatory input, and auto-close the modal if there are no errors”.

This functionality must be available on a case-by-case basis. People may want to quickly step through the page wizard, but not the form wizard, localization or other custom wizards. This means, it should not be a user-specific option. Also it should not be an option that would persist for the same kinds of wizards, because in some cases you may want to fill out fields/steps that are optional, or to specifically check the summary for correctness.

Author Garvin Hicking
Created 03/20/26, 12:22
Updated 03/20/26, 12:22
Feature
New Orphaned Logging

#109300 Delete all error messages with exception code

Context: Administration log
Class: vendor/typo3/cms-belog/Classes/Controller/BackendLogController.php
Function: deleteMessageAction()

Current: Clicking “Delete similar error” deletes all log entries of this type based on the “detail” field. This field also contains the “Requested URL.” If the URL is different, duplicate errors are not deleted, and I have to click multiple times to clean up the log.

Goal: As an integrator, I would like to be able to delete all error messages for a single exception in one go.

Example: Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1407060572: Fluid parse error in […]

Possible solution: Add a new sys_log field “code”. Delete all error messages with exception code 1407060572.

Author Guido Schmechel
Created 03/20/26, 10:22
Updated 03/20/26, 10:22
Bug
New Orphaned Localization TYPO3 CMS 8

#86709 TYPO3 Translation missleading List of content which should be translated

(Occurs in TYPO3 8.7.17 and TYPO3 8.7.19 both PHP 7.0.32, I expect the bug to also occur in 9.5 LTS but have not yet tested that.)

Symptom

If you want to translate two content elements from one language to another and both are shown in the translation manager but not only one gets really translated.

How to recreate the bug

First create a test-element and translate it to any language you want.
Then change the language of the the translated element to the default language, which should in my opinion not work. But thats only my opinion.
Next press the translate button again. You will see both elements in the wizard but only the original element would be translated.

So whats now the bug.

In my perspective we are encountering two bugs here. First that the language of a translated content element can be changed, second that both (the original and translated) elements are shown in the wizard but only one gets really translated.

I have made a video as an step to step manual which you can find in the file section below.

Author Markus Gehrig
Created 10/22/18, 11:50
Updated 03/20/26, 09:36

Showing results 876 to 900 of 1561