Showing results 451 to 475 of 1561

Bug
Accepted Orphaned SEO TYPO3 CMS 12

#105837 Sitemap.xml can be called with every URL of one domain

So I am accusing a strange behavior:
If I add /sitemap.xml to every URL in my domain, i can call the sitemap.xml

test.de/sitemap.xml
test.de/anotherURL/sitemap.xml
test.de/anotherPath/to/anotherURL/sitemap.xml
etc.
These are also no redirects e.g. from test.de/anotherURL/sitemap.xml -> test.de/sitemap.xml

My sitemap configuration looks like this:

routeEnhancers:
  PageTypeSuffix:
    type: PageType
    map:
      sitemap.xml: 1533906435

Am I doing something wrong?
I thought the sitemap.xml should only be displayed at test.de/sitemap.xml

This occurs in v12 and 13

Author Fabian Schiller
Assigned to Benni Mack
Created 12/17/24, 10:55
Updated 07/18/25, 13:46
Bug
Needs Feedback Orphaned DataHandler aka TCEmain TYPO3 CMS 13

#107030 Fields hidden, starttime and endtime do not sync

I have records that I want to keep some field in sync in the translated version.
I’ve add l10n_mode=exclude dans l10n_display=defaultAsReadonly to the fields hidden, starttime and endtime.
In the translated record in the backend, I see the original value (defaultAsReadonly), but in the database, the value can be different.
When I update the original record, those fields are not kept in sync with the original record, as it do with other fields.
Not sure if a bug, a feature or I’m missing something.
By records are used in an IRRE, but it work with other fields (ex: a custom title field).
It’s a custom table, not a tt_content.

I use Content-Block to create my records, and I use the content-blocks dataProcessor to retreive the content.
Is it the dataProcessor that do not do the overlay as it should? Overlay is only for tt_content, no?

Author Maxime Lafontaine
Created 07/03/25, 18:41
Updated 07/04/25, 13:54
Bug
Accepted Orphaned Pagetree TYPO3 CMS 13

#104697 Unexpected behaviour - placing new items in the page tree. Safari Desktop

When adding a new item to the page tree (Page, Mount Point etc) I expect to see the blue line which indicates where my new item will be placed in the page tree.

In both Safari Desktop 17.6 & 18.0 Preview the blue line appears intermittently.

Examples attached.

Author Tom Warwick
Assigned to Benjamin Kott
Created 08/22/24, 11:38
Updated 07/02/25, 09:19
Feature
Accepted Orphaned Backend User Interface

#65505 Add paging for IRRE-records (working with many IRRE-entries)

There exist cases when many child-records are added to an entry. If an entry with 50 or more IRRE-relations gets opened in the backend things quickly get slow and are also not really easy to work with. Find a way to handle “many IRRE-relations” in one record.

Author Stefan Neufeind
Created 03/04/15, 11:58
Updated 06/24/25, 10:02
Task
New Orphaned TypoScript TYPO3 CMS 13

#106877 Log a warning if site set provided TypoScript is overwriten by a sys_template record if clear flag

It is very hard to debug – in tests and in real scenarios – if site set provided TypoScript is overwritten by a sys_template record that has the clear flag set.

A warning (and ideally a message in the backend) should appear that informs the integrator about this configuration, that is probably a mistake.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 06/13/25, 07:31
Updated 06/13/25, 07:31
Bug
Needs Feedback Orphaned Extbase TYPO3 CMS 11

#102299 Incomprehensible behavior: Entity in a forward argument

Hello,

I’m not quite sure if this is a bug or if I fundamentally misunderstood something.

In my self programmed controller I have several actions. Many small Actions do their job and forward a few arguments to a larger Action method, which then organizes everything else and whose template is rendered.

But now when I put an entity into the forward arguments, it only goes well once.
Ex: user clicks on a submit button. Then he lands in my small action method. This validates and forwards among other things also a manipulated entity. This is fast, the errors are displayed. Everything is top. But if the user clicks the button again, it takes many seconds until the page is loaded again.

Currently I convert the entity into an array by hand to put it into the arguments, so that the “big” method “copies” the array back into an entity. This works reliably and quickly.

But surely this can’t be intentional? Is there a caching mechanism or some other generic algorithm interfering?

Can anyone else confirm this behavior? Or show me where in the manual it says not to put Entity in the forward arguments?

I thought the advantage of forwards was just that you can transport more complex objects from action to action without going through the browser….

Thanks for your help… Clemens

Author C. Gogolin
Created 10/31/23, 19:36
Updated 06/06/25, 09:38
Feature
New Orphaned Site Handling, Site Sets & Routing

#106753 Add a pageType parameter to Plugin Enhancer and Extbase Plugin Enhancer

It would be useful to be able to set the pageType in a plugin or extbase enhancer, without using the PageTypeDecorator.
Would permit to have clean url to call JSON pages, without using the pageType decorator (by calling directly a plugin, instead of a page, via TypoScript).

Author Maxime Lafontaine
Created 05/22/25, 15:11
Updated 05/22/25, 15:11
Bug
New Orphaned TYPO3 CMS 10

#94327 TCA type=inline and l10n_mode=exclude doesn't respect hidden field

In TYPO3 10.4 LTS, having a TCA column of a type=inline configured with l10n_mode=exclude doesn’t respect hidden field of default language record.

Example:

Having a site configured with fallbackType=fallback and having a product model with images.

There’s a product record:
- Product1 (default language)
– image1 (hidden=0)
– image2 (hidden=1)

In the FE:
- in the default language page only image1 is shown (correct)
- in the translated page both image1 and image2 are shown

Other things like sorting of images work.

Author Christian Toffolo
Created 06/12/21, 17:26
Updated 05/16/25, 10:09
Task
Under Review Orphaned Linkvalidator TYPO3 CMS 13

#106677 Improve Linkvalidator broken URL output in E-Mail Report

Right now the report provides the actual broken Target/URLs.
Those are cropped at 15 characters, but fully available as a title attribute on a <span> tag.

It would make sense to turn the <span> tag into a <a> tag with an actual link.
That way people receiving the report could directly check the broken url right from the email.

This only affects the HTML E-Mail as the plain text E-Mail already provides the full URL.

One could also add links to edit the broken Link. But TYPO3 isn’t able to build absolute URLs to its backend in CLI context right now.

Author Daniel Siepmann
Assigned to Daniel Siepmann
Created 05/12/25, 06:44
Updated 05/14/25, 07:15
Feature
New Orphaned FormEngine aka TCEforms

#93905 Visualize hidden state of items in TCA selects

When a TCA select element (e.g. SelectMultipleSideBySideElement) is used to allow the selection of records, it is not possible to visually show, if the state of a record is hidden or not. This may lead to unexpected expectations for users selecting items of TCA selects.

Adding a visual indicator (e.g. different color/styling for hidden items, postfix for hidden items) may help to make this more clear.

Author Torben Hansen
Created 04/12/21, 13:41
Updated 05/05/25, 08:04
Task
New Orphaned Backend User Interface TYPO3 CMS 14

#106624 Add "Create new root page" to page tree context menu

Currently – even if you never created a page you only find a “New subpage” entry in the page tree on root level. I would suggest to add an option “Create new rootpage” in the context menu:

If the “New root page” option is chosen, the page should be

  • Automatically created on rootlevel with pid=0
  • Have the “Root page” flag preselected
  • Automatically have a new site config attached
  • Prompt user that a site set or TypoScript record is needed before page can be displayed
  • Maybe offer to pick a site set from the list or create a basic TypoScript record as would be done in the install tool
Author Lina Wolf
Created 04/26/25, 09:35
Updated 04/26/25, 09:51
Feature
New Orphaned Frontend

#106619 Allow fine-grained control of Cache-Control headers

If config.sendCacheHeaders == 1, TSFE currently supports two possible values for the Cache-Control header, depending on whether the rendered response is cacheable or not.

If the response is not cacheable, belongs to a workspace or there is an active BE session, TSFE outputs Cache-Control: private, no-store. However, if the response is cacheable, only the calculated lifetime of the page is considered (as calculated by CacheLifetimeCalculator) and then hardwired Cache-Control: max-age=<lifetime> (or, from TYPO3 13, an additional s-maxage if needed).

There is no way to set additional flags for Cache-Control or to influence this process globally in any other way. However, for using TYPO3 behind a CDN, it would be great if we could append additional options to the generated Cache-Control header, depending on whether the response is cacheable or not. The most important options here would be, for example, stale-if-error and stale-while-revalidate, which can control more precisely how long the CDN may continue to deliver a cacheable response from TYPO3 if, for example, TYPO3 is briefly unavailable.

I have no concrete idea how this could be elegantly designed in TS – one possible idea would be, for example, to do this via additional fields in config. So far we have solved the problem using a PSR-15 middleware that rewrites the header after the rendering process, but I think a proper solution would be much better.

Author Christian Spoo
Created 04/25/25, 13:59
Updated 04/25/25, 14:01
Bug
Needs Feedback Orphaned Performance TYPO3 CMS 11

#104718 Filelist extremly slow having a lot of folders with subfolders on Rootlevel

Story

Loading the file tree takes ages on a storage which has many Folders on rootlevel (122 folder ins my Case) when the folders themselves are containing a lot of subfolders.
This might even lead to max_memory exceed errors or maximum_execution time exceed

Cause

The FileStorageTreeProvides determines the presence of subfolder in a very inefficent and redundant way. Due to recursive nature of the used fuction the performance impact is extremly high.

Solution

*Step 1*
To detect if a folder has a subfolder or not it is not neccessary to fetch all subfolder one is enought so change:
https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/backend/Classes/Tree/FileStorageTreeProvider.php#L64

 $hasSubfolders = !empty($folder->getSubfolders());

To:

 $hasSubfolders = !empty($folder->getSubfolders(0, 1));

*Step 2*
The prepareFolderInformation already holds the information if there is a subfolder or not. So no need to determine it again.

So remove this
https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/backend/Classes/Tree/FileStorageTreeProvider.php#L207

And referre to “prepareFolderInformation[‘hasChildren’]” instead and reaad the check for InaccessibleFolder here:
https://github.com/TYPO3/typo3/blob/11.5/typo3/sysext/backend/Classes/Tree/FileStorageTreeProvider.php#L223

I applied the above changes to a my testystem and the loading time dropped from 30-55s to 2-3s.

Affected Systems:

  • Confirmed on TYPO3 11
  • Code looks the same in TYPO3 12 and 13 (only tested on v11)
Author Nikolas Hagelstein
Created 08/23/24, 15:40
Updated 04/24/25, 09:02
Feature
New Orphaned Backend User Interface

#98297 [UX] - Highlight Save Button in Edit View

As an editor,
I want to find the Save Button quick,
so I can speed up my work, by not reading every button label, to find the correct action to use.

Acceptance criteria

  • the most important and most used action is highlighted

Acceptance test

  • I am logged in as an editor
  • I am editing view
  • the Save button is highlighted by color and I can identify the Save button as Primary button

Technical remarks

Author Annett Jähnichen
Assigned to Annett Jähnichen
Created 09/08/22, 10:35
Updated 04/23/25, 10:14
Feature
Accepted Orphaned Backend User Interface

#90478 Better UX for the backend user module - managing be user groups, rights assignment

Hi,

I would like to make a suggestion for a more userfriendly backend user groups modul.

When you have multiple backend users and backend usergroups, it’s really complicated to keep track of the rights assignment.
You have the users and you can assign groups to the user but you don’t know which particular rights the user has. You have to go into each be usergroup to find out which checkmarks are set. Comparing 3 or 4 different groups, almost impossible. Sure, you can name the be groups to make the purpose clear and split them for functionality/roles (ACL Group, Database mount group, page groups etc.) We already use this approach and have a lot of groups because some groups inherit from each other.

Lets say someone sets a right in the wrong group…you have to check every group which is assigned to the user to find out what is wrong.

My suggestion:

Add a new tab “user rights” to the be user properties where you can see all options and usergroups in a 2-dimensional overview (see the attached screenshot). Vertically you see all the ACL, DM, PG options and horizontally you see all usergroups. With this view you can easily see all the groups and rights which the user has. You can easily check if you have assigned the same right to multiple groups, you can change and edit the groups right, maybe create new groups aswell. That way you don’t have to switch the usergroups to check the rights assignment – which can be very time consuming.

Maybe you have other suggestions or want to add something. I think there is much potential to optimize the rights assignment workflow. Maybe not for the upcoming LTS10, but maybe for LTS11…

Author David Menzel
Created 02/21/20, 22:41
Updated 04/18/25, 09:24
Task
New Orphaned Backend User Interface TYPO3 CMS 9

#81238 Streamline severity and message of delete modal

Story:

As an user I would like to know if a record or a file is moved to trash or deleted from database or file system.

Reference behavior:

Delete a tt_content record:
  • modal serverity warning (yellow).
Switch to the recycler module and delete the record there:
  • modal severity danger (red).
So as an user I expect the following relation:
  • warning → moved to trash
  • danger → delete

Overview:

case expected behavior current behavior example
TCA record with ctrl – delete and deleted = 0 warning warning tt_content
TCA record with ctrl – delete and deleted = 1 danger danger tt_content
TCA record without ctrl – delete danger warning sys_domain
Record without TCA danger warning scheduler task
File with recycler available and not in recycler warning warning file
File in recycler danger warning file
File without recycler danger warning file
Author Daniel Windloff
Created 05/17/17, 08:55
Updated 04/18/25, 07:56
Task
Accepted Orphaned File Abstraction Layer (FAL) TYPO3 CMS 6.2

#77988 Moving folders between local file storages does not work

Trying to move one folder to another storage leads to an flash error message in the backend file module >Directory … was not moved to “/”. Write permission problem?<

Source and target storage are using both the local filesystem driver and are writable, readable, accessible and online.

I tried to debug this issue and tracked it down so far to $this->absoluteBasePath = null in the LocalDriver class. I have not figured out why this is null at this point, but it leads to an error while checking permissions on an malformed file path, due to $this->absoluteBasePath = null.

Thank you

Author Steffen Wargalla
Created 09/18/16, 23:40
Updated 04/12/25, 20:03
Bug
New Orphaned Localization TYPO3 CMS 8

#89498 FSC menu_categorized_content doesn't return content of non default language

Envireonment:
A site with multible languages and categorised content elements.

On a overview page we use the fsc ctype menu_categorized_content to display all ces related to a branch (category).
On the page with the default language menu_categorized_content returns all ces related to the category. Perfect!
On the translated page menu_categorized_content doesn’t return any ce.

After checking the sql query there are two problems.

Query in default language:

SELECT tt_content.* FROM `tt_content` INNER JOIN `sys_category_record_mm` ON uid = sys_category_record_mm.uid_foreign AND sys_category_record_mm.uid_local IN(18) WHERE (`tt_content`.`pid` IN (1, 2, 3, 4, 5, 6, 7, 8, 9)) AND (tablenames='tt_content' and fieldname='categories') AND (`tt_content`.`sys_language_uid` IN (0, -1)) AND ((`tt_content`.`deleted` = 0) AND (`tt_content`.`t3ver_state` <= 0) AND (`tt_content`.`pid` <> -1) AND (`tt_content`.`hidden` = 0) AND (`tt_content`.`starttime` <= 1571910180) AND ((`tt_content`.`endtime` = 0) OR (`tt_content`.`endtime` > 1571910180)) AND (((`tt_content`.`fe_group` = '') OR (`tt_content`.`fe_group` IS NULL) OR (`tt_content`.`fe_group` = '0') OR (FIND_IN_SET('0', `tt_content`.`fe_group`)) OR (FIND_IN_SET('-2', `tt_content`.`fe_group`)) OR (FIND_IN_SET('13', `tt_content`.`fe_group`))))) GROUP BY `uid` ORDER BY `tt_content`.`header` ASC

Query in lang 1:

SELECT tt_content.* FROM `tt_content` INNER JOIN `sys_category_record_mm` ON uid = sys_category_record_mm.uid_foreign AND sys_category_record_mm.uid_local IN(18) WHERE (`tt_content`.`pid` IN (1, 2, 3, 4, 5, 6, 7, 8, 9)) AND (tablenames='tt_content' and fieldname='0') AND (`tt_content`.`sys_language_uid` IN (0, -1)) AND ((`tt_content`.`deleted` = 0) AND (`tt_content`.`t3ver_state` <= 0) AND (`tt_content`.`pid` <> -1) AND (`tt_content`.`hidden` = 0) AND (`tt_content`.`starttime` <= 1571909640) AND ((`tt_content`.`endtime` = 0) OR (`tt_content`.`endtime` > 1571909640)) AND (((`tt_content`.`fe_group` = '') OR (`tt_content`.`fe_group` IS NULL) OR (`tt_content`.`fe_group` = '0') OR (FIND_IN_SET('0', `tt_content`.`fe_group`)) OR (FIND_IN_SET('-2', `tt_content`.`fe_group`)) OR (FIND_IN_SET('13', `tt_content`.`fe_group`))))) GROUP BY `uid` ORDER BY `tt_content`.`header` ASC

Problems in the query:

1:

(tablenames='tt_content' and fieldname='0')

Seems like “data = field:category_field” returns 0 in non default lannguage.
https://github.com/TYPO3/TYPO3.CMS/blob/v8.7.28/typo3/sysext/fluid_styled_content/Configuration/TypoScript/ContentElement/MenuCategorizedContent.txt#L19

2:

(`tt_content`.`sys_language_uid` IN (0, -1)

It just queries default and all language records instead of the current language.

The first I have workedaround with fixing the fieldname

tt_content.menu_categorized_content.dataProcessing.10.where >
tt_content.menu_categorized_content.dataProcessing.10.where = {#tablenames}='tt_content' and {#fieldname}='categories'

For problem 2 I haven’t a workaround yet.

Author Jan Kiesewetter
Created 10/24/19, 12:21
Updated 04/11/25, 07:55
Feature
New Orphaned Backend User Interface

#103414 Add a date restriction/filter to backend search

As an editor, I want to use date fields in the backend search to limit long search hit lists to the selection that is relevant to me.

Background: My editors often have to search for specific records and the general search offers an unusable number of results for larger instances. A useful restriction would often be to be able to select a time period for a specific date field.

Examples:

  • Search for »Apple« in the demo instance (see screenshot)

Use Cases:

  • All content elements created after 01.01.2024 (crdate)
  • All content elements that were created before 28.02.2024 (crdate)
  • All pages that were last edited before 01.01.2020 (tstamp)
  • All news with a publication date between 01.01.2022 and 31.12.2023 (datetime)
  • All events with a start date after 01.02.2024 and before 01.03.2024 (startdate)
Author Dan Kleine (Untenzu)
Created 03/18/24, 09:58
Updated 04/10/25, 09:49
Feature
New Orphaned Backend User Interface

#77580 List module: Make the selection of single record mode, multi-selection mode and the selection of the record type available via module menus

To make the features of the list module (EXT:recordlist) easy to find, add the main (currently implicit) selections to the module menu.
Remove the “activated clipboard” dependency from the selection mode.

Example 1:
The user wants to edit or remove multiple records.

Current situation:
The user has to scroll down, active the clipboard, scroll down and click to the multi selection mode (e.g. Clipboard 1).
The action itself (edit, remove) has no relation to clipboard features (move, copy, paste).

Proposed behaviour:
Select the single record mode or the multi-selection mode via module menu (in case of a deactivated clipboard). Select the clipboard via module menu in case of an activated clipboard.

Example 2:
The user wants to select an additional column (download a csv…).

Current situation:
Scroll to the table of the record type and click to the table title. If there are many record types and records, the link will be hard to find.

Proposed behaviour:
Select record type in the module menu.

Author Daniel Windloff
Created 08/22/16, 14:35
Updated 04/10/25, 08:04
Feature
Accepted Orphaned Backend User Interface

#95369 improve readability of "New Record Selector”

When selecting a new record, it would be nice if the tables would be shown in columns in the backend.
Something like the following:

Maybe even in three columns on wide screens.
At the moment we have a pretty large unused space given that the item names are reasonably short.
The positioning of the tables in columns should be responsive of course (they should stack on smaller screens).

Author Michael Schams
Created 09/27/21, 11:26
Updated 04/01/25, 13:20
Feature
New Orphaned File Abstraction Layer (FAL)

#20558 Mass file uploader: Uploading directories

Many users want to upload a lot of files in a given directory structure. The mass file upload should support uploading whole directory structures just like ameos_dragndropupload. The drag&drop possibility there is also a very user-friendly feature.

(issue imported from #M11256)

Author Thomas Schröder
Assigned to Christian Eßl
Created 06/03/09, 12:31
Updated 04/01/25, 13:20
Feature
New Orphaned Backend User Interface

#71429 Limit selection of content elements to allowed languages

I have a page with 4 languages. For each language I created a be user limited to only one language. If this user wants to create a link to a content element thru a link wizard, a link with all content elements in all languages is shown. It would be great, if this list would be limited to the allowed language. Additionaly it would be helpful to show the content element uid in this list. Like it is possible to show the page uid in page tree.

Author Natalia Postnikova
Created 11/09/15, 09:58
Updated 04/01/25, 13:14
Bug
Accepted Orphaned Form Framework TYPO3 CMS 12

#104118 Avoid hard dependency on final validation viewhelper

I inherited a project that xclassed the NotEmptyViewHelper and am currently updating it to v12.4
Previously, the ViewHelper was extended, but since they are final now this can’t be done anymore.
Thus i copied the code over, made the adjustments —> done, or so i thought…

Now when i tried to add a new form with EXT:form, i could not get the required sign to show up. After quite some debugging i found that there are hard dependencies with instanceof checks in place
https://github.com/search?q=repo%3ATYPO3%2Ftypo3+%22instanceof+NotEmpty%22&type=code

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/extbase/Classes/Validation/Validator/NotEmptyValidator.php

IMHO this implementation needs to be changed, we can not have any hardcoded checks that way without being able to switch out the code. I know that the final declaration is unlikely to change, thus the NotEmptyValidator should probably have an interface or tag to indicate it is a required validator.

Author Andreas Kießling
Created 06/15/24, 19:33
Updated 03/26/25, 09:21
Bug
New Orphaned Backend API TYPO3 CMS 12

#106101 allow a null value for the getSession method

Under some circumstances the session member variable of FrontendUserAuthentication is null.

abstract class AbstractUserAuthentication implements LoggerAwareInterface
{
…
protected ?UserSession $userSession = null;
…
public function getSession(): UserSession {
return $this->userSession;
}
}

The method getSession should return the null value if userSession is null and not cause a PHP TypeError.

TypeError TYPO3\CMS\Core\Authentication\AbstractUserAuthentication::getSession(): Return value must be of type TYPO3\CMS\Core\Session\UserSession, null returned

Solution:

public function getSession(): ?UserSession
Author Franz Holzinger
Created 02/06/25, 16:06
Updated 03/07/25, 12:08

Showing results 451 to 475 of 1561