Showing results 776 to 800 of 1561

Bug
New Stale Workspaces TYPO3 CMS 13

#110077 Hidden Content is visible in Workspace preview

The hidden (disable) flag of tt_content elements is not honored in the workspace frontend preview (the “Staged version” of the Workspaces compare/preview view). Disabled content elements are rendered there although they must not be.

This affects (at least) two cases:

A) An element that is hidden in Live and has no workspace version.
B) An element that is newly created in the workspace and set to hidden there.

In both cases the disabled element appears in the workspace/staged preview. On the live site and in the live preview pane the elements are correctly hidden. This worked correctly in TYPO3 v12 and is a regression in v13.

Steps to reproduce

Case A – hidden in Live, no workspace overlay:
  1. Have at least one draft workspace configured (system extension workspaces).
  2. In the Live workspace, on any page, create a standard content element (e.g. CType Text) and set it to hidden. Do not create/edit a workspace version of it.
  3. In the backend, switch to the draft workspace.
  4. Open the page in the Workspaces module preview (Compare mode, “Published version” ↔ “Staged version”), or view the page in workspace context.
  5. Look at the Staged version pane.
Case B – created and hidden inside the workspace:
  1. In the draft workspace, on any page, create a new content element (e.g. CType Text) and set it to hidden. Do not publish.
  2. Open the same workspace preview as above and look at the Staged version pane.

Expected behavior:

The hidden element is not rendered in the workspace/staged preview — it is disabled and (Case A) has no workspace change un-hiding it / (Case B) would also be hidden after publishing.

Actual behavior

The hidden element is rendered in the workspace/staged preview. The live pane (ADMCMD_prev=LIVE) and the public live page correctly do not show it.

Additional information

  • The page itself is visible (not hidden); standard frontend content rendering is used (no custom DataProcessor).
  • In the Workspaces compare view, the live iframe (?ADMCMD_prev=LIVE) hides the element correctly; only the staged iframe shows it.

Environment

  • TYPO3: 13.4.28
  • PHP: 8.4.18
  • System extension: workspaces
    Might be similar to #108814 but does not – as descripbed above – depend on visibility of a page.
Author S. H.
Created 06/18/26, 11:49
Updated 06/18/26, 11:55
Bug
Needs Feedback Stale Backend User Interface TYPO3 CMS 13

#108443 Modal alert for required fields doesn’t name the affected field or tab

*Description*
The modal alert shown for missing required fields is too generic: it does not mention the specific field nor its tab. With multiple errors, neither the count nor an overview is provided, making corrections cumbersome.

Reproduction Steps
  1. Open a backend form with at least one required field.
  2. Leave at least one required field empty.
  3. Trigger “Save.”
  4. Observe the modal alert: message is generic, without field/tab names.
Impact
  • Increased time to fix, as users must search for the failing field.
  • Risk of incomplete or incorrect data remaining.
  • Poor UX, especially in forms with many tabs/fields.
Recommended Solution
  • Extend the validation collector to gather context: for each failing required field, determine field label and tab label.
  • Message logic:
    > * Exactly one error → include field and tab by name in the modal.
    > * Multiple errors → include the error count n and optionally provide a list/link to an error overview.
Definition of Done
  • For a single error, the modal names the exact field label and tab.
  • For multiple errors, the count n is shown; optionally provide a list or navigation hint.
Acceptance Criteria
  • Saving with exactly one empty required field shows: “Please correct the required field ‘{FieldLabel}’ in tab ‘{TabName}’.”
  • Saving with multiple empty required fields shows: “There are n required fields incomplete.
Author Christian Jung
Created 12/09/25, 14:42
Updated 06/17/26, 11:45
Bug
New Stale Link Handling & Redirect Handling TYPO3 CMS 14

#101156 Record links with L>0 records resolve to page URLs with L=0, also record links ignore the L parameter completly

Having a setup like this:

domain/de is L=0
domain/en is L=1

Having a redirect source domain/shortcut (note: no given language context) with target t3://record?identifier=whatever&uid=123 with a uid 123 from L=1!

This leads to domain/de/detail-page/english-record, which is wrong ( de page with en record). The requested record is correctly fetched and overlayed, but displayed on the wrong site language (which usally is a 404).
In the time of the redirect middleware execution the request has no SiteLanguage attribute set, but the RouteResult attribute already has one (to L=0, whyever this is assumed, I suspect this to be the cause of the problem, but changing the RouteResult language in a custom Middleware is forbidden by an explicit Exception).

Adding the L=1 parameter explicitly to the target link (t3://record?...&L=1) does not change anything, it gets ignored.

Expected behaviour 1: as long as no explicit language is present, a RecordLink should use the language from the record also for the page resolving (let L follow from record.sys_language_uid, instead of just assuming L=0)

Expected behaviour 2: When passing an explicit L to a record link it should be respected by the page resolving, just how it is like adding L to a t3://page?uid=123&L=1 link.

I assume this is also valid when not being in redirect context, but for example in command context, where also no language context is present.

Discovered in v11, probbaly valid in all others as well.

Our current workaround is to always force-append the L parameter in record link configuration,see below. But this should not be needed, but happen implicitly.

config.recordLinks.whatever {
  typolink {
    additionalParams {
       cObject {
         1 = TEXT
         1 {
           data = field:sys_language_uid
           wrap = &L=|
         }

         2 = TEXT
         2 {
           data = field:uid
           wrap = tx_foo_the_usualstuff&tx_foo_record[uid]=|
         }
       }
    }
  }
}
Author S P
Created 06/23/23, 06:01
Updated 06/17/26, 08:49
Feature
Under Review Stale Site Handling, Site Sets & Routing

#108621 Password Type for Site Settings

New `password` type for Site Settings that automatically encrypts passwords using AES-256-CBC and displays them masked in the backend editor.

Problem

Previously, passwords had to be stored as regular `string` types, which means:
- Passwords are stored in plain text in `settings.yaml`
- Security risk in version control
- No masking in the backend editor

Solution

New `password` type with:
- Automatic encryption using AES-256-CBC
- Uses TYPO3 `encryptionKey`
- Masked as `********` in backend editor
- Smart handling of already encrypted values

Usage

In settings.definitions.yaml

settings:
  api.password:
    label: 'API Password'
    description: 'Password for external API authentication'
    type: password
    default: ''
    category: api

In PHP Code

use TYPO3\CMS\Core\Settings\Type\PasswordType;

// Read password from settings (encrypted)
$encryptedPassword = $site->getSettings()->get('api.password');

// Decrypt password

$passwordType = GeneralUtility::makeInstance(PasswordType::class);
$decryptedPassword = $passwordType->decrypt($encryptedPassword);

Implementation

New Files

- `typo3/sysext/core/Classes/Settings/Type/PasswordType.php` – PHP class
- `Build/Sources/TypeScript/backend/settings/type/password.ts` – TypeScript component

Modified Files

- `Build/Sources/TypeScript/backend/settings/editor.ts` – Added import

Security

- Encryption using AES-256-CBC
- Uses TYPO3 `encryptionKey`
- Encrypted values have prefix `###ENCRYPTED###`
- Empty passwords are not encrypted

Example: Encrypted Value


api.password: '###ENCRYPTED###dGhpc2lzYW5leGFtcGxlZW5jcnlwdGVkcGFzc3dvcmQ='

for testing

https://github.com/Rathch/setting_type_test

Author Christian Rath-Ulrich
Assigned to Christian Rath-Ulrich
Created 01/13/26, 08:44
Updated 06/16/26, 22:28
Bug
Under Review Stale Workspaces TYPO3 CMS 13

#110062 l10n_mode exlude fields are not synced to translations if changed within workspace

Changing the backend-layout of a page within a workspace creates a new workspace-version of that page.
All translations also get their workspace-version. All those workspace versions get the right backend-layout.

Changing the backend-layout again now of the default language, does not sync the selected layout to the translations.

The reason is a missing lookup within the Core, that does not consider workspace-versions correctly, when determining the records that need updates.

Author Markus Klein
Created 06/16/26, 13:31
Updated 06/16/26, 13:33
Feature
Under Review Stale Backend User Interface

#110047 Button for removing all of a field's sys_file_references

If you want to delete file references from a field and there are a large number of references, you currently have to remove them one by one. Therefore, it would be useful to have a “Delete all references” button that removes all references from that field.

Author Christoph Bolda
Created 06/10/26, 14:21
Updated 06/13/26, 11:28
Feature
Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 06/11/26, 20:52
Updated 06/12/26, 20:27
Bug
New Stale Extbase TYPO3 CMS 14

#101541 The data type of validator options is neither respected nor documented, the required flag is not documented

When extending \TYPO3\CMS\Extbase\Validation\Validator\AbstractValidator to write a custom validator having options, for example when doing this in combination with ext:form, one has to specifiy the $supportedOptions array inside the validator class, like so

protected $supportedOptions = [
    'optionOne' => [1, 'Some option', 'int'],
    'optionTwo' => [5, 'another option', 'int']
];

Containing the type of the value as the third array element.

When I dump what is in the final values in my options ($this->getOptions() or directly $this->options) I can see that the int cast is not happening. For example, when using this in combination with ext:form the option values come from the YAML which contains strings. So my options does contain '5' instead of 5.

Shouldn’t the configured option types in some way be respected (at least in the documentation of this API)? What I’m saying: I’m not even sure whether I just made a bug report, or even a feature request or simply reported missing/inconsistent documentation.

https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/Extbase/Reference/Validation/Index.html (and subpages) has nothing about it. What is the intention of this configuration? Is this a left-over or planned to be used in the future?

And the fourth flag (“option required or not”) is also not documented, but it is respected in code.

Author S P
Created 08/03/23, 07:31
Updated 06/12/26, 05:42
Bug
New Stale TypoScript TYPO3 CMS 14

#93877 pidInList keyword 'this' not working when CE is referenced via CType = shortcut because it points to the page of the shortcut CE and not to the page of the referenced CE

Consider a CE that fetches inline records with a DatabaseQueryProcessor. Since the records are on the same page as the CE itself, for pidInList the default this is correct.

If this CE is now referenced in CType shortcut the inline records are not fetched because this uses the pid of the shortcut element, not from the referenced record. You have to explcitly state pidInList.field = pid which makes the this keyword essentially useless (because you can never use it because under normal circumstances every CType is allowed to be rendered in a shortcut so you always have to explicitly set it to field = pid anyways).

I’m not sure whether this is actually a flaw of this or the source configuration of RECORDS (which shortcut is using internally).

Author S P
Created 04/08/21, 05:55
Updated 06/11/26, 09:10
Task
New Stale Site Handling, Site Sets & Routing TYPO3 CMS 14

#91860 Simplify SlugHelper to make it actually useful

Whenever one uses the SlugHelper (be it core code or 3rd party code) one has to do this copy-pasting afterwards:

        $state = RecordStateFactory::forName($table)
            ->fromArray($fullRecord, $realPid, $id);
        $evalCodesArray = GeneralUtility::trimExplode(',', $tcaFieldConf['eval'], true);
        if (in_array('unique', $evalCodesArray, true)) {
            $value = $helper->buildSlugForUniqueInTable($value, $state);
        }
        if (in_array('uniqueInSite', $evalCodesArray, true)) {
            $value = $helper->buildSlugForUniqueInSite($value, $state);
        }
        if (in_array('uniqueInPid', $evalCodesArray, true)) {
            $value = $helper->buildSlugForUniqueInPid($value, $state);
        }

This should happen implicitly in the generate() and sanitize() methods of the SlugHelper itself, because it has to happen anyways and the SlugHelper already has all needed parameters anyways…

Also the constructor should allow to pass null to $configuration (default it to $configuration = null) and in this case it should fetch the configuration automatically from the TCA. Then you don’t need to access GLOBALS[TCA][table] whenever calling the SlugHelper with default configuration (because the slug helper gets the table and field name anyways and can fetch it automatically).

Author S P
Created 07/24/20, 09:58
Updated 06/11/26, 09:00
Bug
New Stale Localization TYPO3 CMS 14

#88890 URL segments (slugs) of translated pages should be autogenerated

When creating a new page and not set a slug it gets autogenerated.

But when translating a page the slug gets pre-filled with “translate-to-target-language-original-title” and thus is not auto-generated with the real title on saving.

The slug field should initially be empty on a newly translated page record. Since v14 this is ven more serious, because this overlay translation wizard does not even allow to change the title…

This is
  1. big nuisance for non-technical editors in large envorinments. The UX can be improved here by emptying the slug initially to trigger the auto-filling when no slug is entered manually.
  2. more an just an annoyance when doing automatic translations (see comments)
Author S P
Created 08/02/19, 15:04
Updated 06/11/26, 08:11
Feature
New Stale FormEngine aka TCEforms

#93926 Allow setting empty labels via TSconfig

Via TSconfig TCEFORM it’s possible to set label and (since v11) also description of TCA fields.

However it was never possible to set empty labels, because the form data providers evaluating the TSconfig check for empty(), not just for isset().

For example:
@TCEFORM.pages.title.label = @
will be interpreted like as it was not there at all.

As an intgerator or developer, when writing such a line explicitly int my code, I’d expect that it is evaluated by the Core API.

For example I may want to unset a description in a specific page tree.

This should be generally possible for all “label-like” TSconfig settings (label and description where just an example).

Author S P
Created 04/15/21, 08:37
Updated 06/11/26, 07:13
Bug
Needs Feedback Stale Database API (Doctrine DBAL) TYPO3 CMS 14

#105438 Setting a foreign key on an TCA-autogenerated SQL column crashes the DB compare tool

When having an inline field or a select field to another table, it can be useful to declare foreign keys on the relation field (for reeferential integrity, generating SQL relation diagrams or doing ON DELETE/@ON UPDATE@ stuff directly via SQL). When letting the TCA autogenerate the SQL definition it is not possible to declare a foreign key. The DB compare tool will just crash hard. One has to copy the field definition to ext_tables.sql then.

# When letting this field be created by TCA automagic (same SQL defintion) it will crash:
my_field int unsigned DEFAULT NULL,

FOREIGN KEY fk_my_field (my_field) REFERENCES foreign_table (uid)

Note: this bug only affects foreign keys! Normal indexes work just fine on TCA-autogenerated fields!

Author S P
Assigned to Stefan Bürk
Created 10/24/24, 13:00
Updated 06/11/26, 07:05
Task
Under Review Stale Extbase TYPO3 CMS 14

#109101 Mark AbstractDomainObject as not-internal

Author Oliver Klee
Assigned to Oliver Klee
Created 02/25/26, 18:07
Updated 06/10/26, 15:06
Bug
New Stale TYPO3 CMS 13

#110044 Error reporting with reliance on DI container for log methods is volatile

https://forge.typo3.org/issues/110031 showed that the error handler requires services obtained from the DI container.

This has several weaknesses that it it volatile:

  • The service that is needed for logging, might be created at the moment, causing a dependency loop
  • The DI container might not be available yet (during Core/Bootstrap)
  • The actual errors (the once that triggered the error handler) are lost and hard to debug/find
Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 06/10/26, 11:59
Updated 06/10/26, 12:00
Task
New Stale TYPO3 CMS 14

#110001 Provide colPos in FormEngineDataProvider Result

The Core does not have a concept of “Nested Content Elements”. TCA-wise it is possible to define a Content Element with an inline field having foreign_table set to “tt_content”, which effectively enables such usage. The Content Blocks extensions builds upon this technical possibility and adds multiple Event Listeners to filter child elements in the backend (and frontend). With the new introduction of allowed content types in page layouts (content defender), it became necessary that inline children have the same colPos as their parent. Per default, colPos is always “0”. Only the root Content Element receives an override, when put into a colPos area. The FormEngine should be extended, so that every tt_content record in the rendering chain has the same colPos as the top most parent element.

See also Content Blocks Issue: https://github.com/FriendsOfTYPO3/content-blocks/issues/501

Author Nikita Hovratov
Created 06/04/26, 16:22
Updated 06/04/26, 16:22
Feature
New Stale Site Handling, Site Sets & Routing

#109979 Inject site settings in extbase plugin

The site setting can contain page ids used for linking in views or values in the controller

Adapted from the frontend “RequestHandler”, we can inject them reading it from the request given to processRequest with this (excluding inject* method)

$pageSettings = $request->getAttribute('frontend.typoscript')->getSettingsTree()->
$this->view->assign('siteSettings', $this->typoScriptService->convertTypoScriptArrayToPlainArray($pageSettings));
Author Soren Malling
Created 06/03/26, 11:19
Updated 06/03/26, 19:42
Bug
New Stale Workspaces TYPO3 CMS 13

#109941 Page becomes its own parent after successive moves when initially moved as last child

When working in a workspace, moving an existing page multiple times can lead to data corruption where the page becomes its own parent (pid = t3ver_oid).
This results in:

  • The page disappearing from the page tree
  • An inconsistent page structure in the database
The issue only occurs under specific conditions:
  • The page being moved must initially exist in the Live workspace (already published)
  • The page is first moved as the last child of a parent page
  • The page is then moved again to another position, specifically between its parent page and its next sibling

*Initial page tree*
Root
├── Page A
├── Page B
└── Page C

*Step 1 – Move Page A under Page B (as LAST child)*
Root
├── Page B
│ └── Page A (moved here as last child)
└── Page C

*Step 2 — Move Page A between Page B and Page C*
Root
├── Page B
├── Page A ← expected position
└── Page C

*Actual result*
Root
├── Page B
└── Page C

(Page A disappears from tree)

In the database, the Page B has the same pid and t3ver_id

Additional note:

Attempting the same steps in the Live workspace correctly triggers the following error:
“Attempt to move pages:{pageId} to inside of its own rootline.”

In this case, the page remains visible and no corruption occurs.

The bug could not be reproduced in a TYPO3 v12 environment.

The behavior suggests that the move logic may rely primarily on visual adjacency in the tree rather than the actual hierarchical structure.

Author Dominic Petit
Created 06/01/26, 16:05
Updated 06/01/26, 19:20
Feature
Under Review Stale Security

#109911 Require explicit inheritAccessFromModule declaration for AJAX routes

Aim for having inheritAccessFromModule either set to a module name (string) or false (bool).
This shall make it more explicit, when a particular AJAX route is allowed to be used.

In addition, there should be a new check in the reports module, that list AJAX routes that did not define these settings explicitly.

Optional:
  • Consider adding a feature flag, to enforce inheritAccessFromModule (which is a breaking change and should be enabled explicitly).
  • Consider back-porting this feature flag to older TYPO3 versions as well (v14, v13)

—-

inheritAccessFromModule was introduced with https://review.typo3.org/c/Packages/TYPO3.CMS/+/90631

Author Oliver Hader
Created 05/29/26, 09:17
Updated 05/29/26, 12:56
Bug
Needs Feedback Stale Backend JavaScript TYPO3 CMS 14

#88008 Clicking "Save and close" in the popup after selecting another backend module loads the previous module

I did this:
  • going to file module and open a file for editing metadata
  • changed something, NOT saving
  • clicking another backend module (I clicked “Backend users”)
  • Popup appears because of unsaved changes
  • up until now everything is fine
  • But: clicking “Save and close” saves, but loads the old module, not the requested one! I ended up being in the file list module, not in the backend user module

I assume this behaviour is true for any module combination.

Author S P
Created 03/26/19, 12:47
Updated 05/29/26, 07:13
Bug
Needs Feedback Stale Fluid TYPO3 CMS 14

#109899 The f:image.srcset VH wrongly requires the srcset attribute (instead of defaulting to "1x"), the official HTML spec has it as optional (defaulting to "1x")

See https://html.spec.whatwg.org/#srcset-attribute – zero or one

> Zero or one of the following:
> # A width descriptor, consisting of: ASCII whitespace, a valid non-negative integer giving a number greater than zero representing the width descriptor value, and a U+0077 LATIN SMALL LETTER W character.
> # A pixel density descriptor, consisting of: ASCII whitespace, a valid floating-point number giving a number greater than zero representing the pixel density descriptor value, and a U+0078 LATIN SMALL LETTER X character.

And Mozilla says explicitly this, https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/source#srcset

> If the descriptors are not specified, the default value used is 1x

However, the f:image.srcset ViewHelper has this:

$this->registerArgument(‘srcset’, ‘string’, ‘Comma-separated list of width descriptors (e. g. 200w) or pixel density descriptors (e. g. 2x).’, true);

So, the required flag set to true for the srcset argument. This is HTML-spec-violating.

Correct would be $required = false and $defaultValue = '1x'.

Of course, we could adjust hundreds of places by explcitly passing “1x” – but this is super-tedious and basically renders this VH useless (in the sense of comfort-gain). Much better would be if the VH behaves just fully compliant to the HTML-spec oob.

Author S P
Created 05/28/26, 09:37
Updated 05/29/26, 05:31
Task
New Stale TYPO3 CMS 14

#109882 Add method to reset generated cache in UriBuilder

Prevent stale CSRF tokens in cached URIs causing redirect loops

Author Jochen Roth
Created 05/27/26, 20:48
Updated 05/27/26, 20:48
Bug
Needs Feedback Stale TYPO3 CMS 13

#87979 TYPO3\CMS\Extbase\Service::getImageUri in CLI Mode

Hi,

i´ve the follwoing problem in TYPO3 v9.5.5 / Composer-Mode, Public-Root is “web”:

I use this TYPO3-Service “TYPO3\CMS\Extbase\Service::getImageUri” to retrieve the image path´s, e.g. for a Json-File.

But there is some confusion with the “uriPrefix”:

If this is called from the frontend, always fine – the path will be correct: _fileadmin/…_
but I run this service also in a Command/CLI and it seems the calculated “doc-root” is the composer-dir”: _*/web/*fileadmin/…_
This path is wrong against the frontend because the doc-Root itself is “web”.

My question is now:
Where ever I have to set a special “TYPO3_SITE_PATH” manually for CLI-Mode or is it a normal behavior or maybe a bug?

Kind regards
Ralf

Author Ralf Hübner
Created 03/22/19, 09:30
Updated 05/26/26, 15:27
Bug
New Stale TYPO3 CMS 12

#107609 TCA: excluded inline records don't change

TYPO3 12.4.37

'property' => [
            'exclude' => true,
            'label' => 'Inline record',
            'l10n_mode' => 'exclude',
            'config' => [
                'type' => 'inline',
                'foreign_table' => 'tx_test_domain_model_relation',
                'foreign_field' => 'property',
                'foreign_sortby' => 'sorting',
                'maxitems' => 9999,
                'appearance' => [
                    'collapseAll' => 1,
                    'levelLinksPosition' => 'top',
                    'showSynchronizationLink' => 1,
                    'showPossibleLocalizationRecords' => 1,
                    'showAllLocalizationLink' => 1,
                ],
            ],

        ],

new elements get created, but changes to the hidden field of the records don’t get synced to other languages

Author Philipp Parzer
Created 10/06/25, 09:16
Updated 05/26/26, 07:57
Bug
Needs Feedback Orphaned Backend User Interface TYPO3 CMS 10

#91593 Improved error msg if checkbox "Editable for Admins Only " set

If checkbox “Editable for Admins Only” is set on a page, the records inside can be opened by an editor and there is the save btn but it will lead to an error “…without permission. Or non-existing page.”

ideas:

  • drop save button
  • add flash message in sys folder + single record to inform user
  • change all fields to readonly just like it would be for ctrl>readOnly = 1
Author Georg Ringer
Created 06/05/20, 09:24
Updated 05/22/26, 07:49

Showing results 776 to 800 of 1561