Showing results 1151 to 1175 of 1561

Feature
New Orphaned Linkvalidator

#89454 Limit list of broken links displayed / add pagination

Currently all broken links will be shown in the list, depending on what linktypes and linklevel are selected and what current page is selected. Using the start page, all linktypes and linklevel “unlimited” may lead to long load times.

If there are 2000 broken links, 2000 broken links will be displayed.

Having a very long list is probably usually unnecessary. I propose to have a configurable maximum or pagination.

Author Sybille Peters
Created 10/18/19, 16:28
Updated 02/08/25, 11:44
Feature
New Orphaned Localization

#89162 Provide possibility to switch from connected mode to free translation mode (and vice versa)

In some cases it might be desirable to change the translation mode for a page.

  1. changing from connected or mixed to free. This should be possible (currently it is possible by setting l18n_parent to 0 for each record, but this is tedious).

Make this easy to do, e.g. by clicking a button.

Author Sybille Peters
Created 09/12/19, 18:19
Updated 02/08/25, 11:33
Bug
New Orphaned TYPO3 CMS 12

#106076 Admin Panel - Ignore start and endtime without function in workspace draft mode

*Actual behavior:*
In draft mode, when the “ignore start and endtime” checkbox in the admin panel is checked, content elements with a start and end time set are still not displayed.
*
Expected behavior:*
In draft mode, when the “ignore start and endtime” checkbox in the admin panel is checked, content elements with a start and end time set should be displayed.

Author Hendrik Flechtker
Created 02/04/25, 13:14
Updated 02/07/25, 12:29
Bug
New Orphaned AdminPanel TYPO3 CMS 12

#106036 Admin panel does not trigger nonce to be consumed

When you activate the admin-panel on a frontend page as a logged-in backend user which does not have a consumed nonce, errors will show up regarding CSP. This is due to the fact the admin panel does add script and link tags with a nonce, which is never been triggered to be consumed, so the nonce does not appear in the frontend content security policy. Only the nonce string is fetched.

Also there are some link and script tags, generated by the admin panel, which do not use inline CSS or JS but refer to files using the src/href attribute, but nevertheless get a nonce attribute. When not using inline, the nonce is not needed.

requirements:
  • Frontend content security policies enabled
  • Page without any nonce (when not logged in)
  • Logged in backend user
  • The same page opened from the backend
  • Admin panel enabled
  • Admin panel activated in the page (switch in lower right corner turned from red to green)

Open the console and watch the CSP errors regarding script-src and style-src directives

Author Patrick Broens
Created 01/30/25, 15:38
Updated 01/31/25, 13:51
Bug
New Orphaned Content Rendering TYPO3 CMS 11

#96294 PageContentErrorHandler ignores configured additionalHeaders

When using a page e.g. as 404 error page the in TypoScript configured additionalHeaders are ignored and not set. Most likely these headers are lost when fetching the internal error page via HTTP and deliver the result to the client.

This behaviour was detected in TYPO3 10LTS, but is the very same in 11LTS.

TS:

page.config.additionalHeaders.10.header = X-Powered-By: nothing

works fine on every page, except the error pages.

Author Marc Willmann
Created 12/08/21, 17:08
Updated 01/29/25, 08:39
Epic
Accepted Orphaned felogin

#92641 felogin feature collection

Author Markus Klein
Created 10/21/20, 14:55
Updated 01/29/25, 08:39
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 13

#106005 Not quite sure if it's a "feature" - displaycond has effect although the related field is not displayed when creating a new content element

I habe a TCA definition for a field:

‘field_1’ => [
‘exclude’ => 1,
‘onChange’ => ‘reload’,
‘label’ => ‘LLL:EXT:ext_name/Resources/Private/Language/locallang.xlf:field_1_label’,
‘config’ => [
‘type’ => ‘check’,
‘renderType’ => ‘checkboxToggle’,
‘items’ => [
[
0 => ‘’,
1 => ‘’,
]
],
‘default’ => ’1’
]
],

The default for this checkbox is “checked”. However, this Checkbox is by configuration not part of my form. The reason for this is That my extension has two plugins. One Plugin that has the checkbox, the other plugin does not. Both plugins share a common tt_content.php in TCA/Overrides. And both use this text element:

‘text_input’ => [
‘label’ => ‘LLL:EXT:artofffunc/Resources/Private/Language/locallang_be.xlf:text_input’,
‘displayCond’ => ‘field_1:REQ:false’,
‘config’ => [
‘type’ => ‘input’,
‘size’ => 200,
],
],

As one can see I have a display condition in it which tells to show the field ‘text_input’ when the field ‘field_1’ is unchecked. I use ‘text_input’ in both plugins – and both plugins are based on tt_content as the database table.

So for the plugin that has ‘field_1’ and ‘text_input’ in its form ‘text_input’ is not shown as ‘field_1’ is checked by default. This is as it should be.

However, when I create a new content element of the second plugin ‘text_input’ is also not shown although ‘field_1’ is not part of its form. I would have expected that the display condition only holds when the appropriate form field is in the palette – and otherwise the display condition should not have any effect. Also the value of “field_1” is stored in the database although it is not part of the form. That is not the behaviour I expect – and it only applies to new content elements. Once it’s saved and I change that value for “field_1” to 0 manually in tt_content afterwards everything works a expected from then on.

Is this a feature or a bug?

Author Michael Perlbach
Created 01/29/25, 00:21
Updated 01/29/25, 08:39
Bug
New Orphaned Frontend TYPO3 CMS 12

#105946 Dont store missing-icon markup in icon LocalStorage

When using a icon-identifier, that has not been registered yet (this happens quiet often in development), typo3 will render the missing icon svg. So far so good. But typo3 will also persist the missing-icon markup in the LocalStorage. So you won’t be able to fix the issue unless you clear your local storage. If you don’t know this it is really confusing because it might work when deployed (other LocalStorage) or when simply changing the icon identifier.

This is really annoying. I suggest using the correct HTTP response code (404) if a icon can not be loaded and avoid using additional caching logic.

Author Philipp Wrann
Created 01/16/25, 09:03
Updated 01/27/25, 12:15
Bug
Under Review Orphaned SEO TYPO3 CMS 10

#101045 ext:seo sitemap ignores the fact that pages doktype is localizable

By default, a page’s doktype can change upon translation; thus, a default page can be an external link on any translation and vice versa. For example:

Page A 
lang: default, doktype: standard page
translation: fr, doktype: external link to www.foo.de

Page B 
lang: default, doktype: standard page
translation: fr, doktype: external link to www.foo.de

Page C
lang: default, doktype: external link to www.bar.de
translation: fr, doktype: standard page

On the FR sitemap, this leads to:

Page A (visible) (Entry: www.foo.de)
Page B (visible) (Entry: www.foo.de)
Page C (not visible)

Problem

  1. duplicate links in the sitemap
  2. inconsistent behavior (some external links are visible, some are not; some default pages are visible, some are not)

The sitemap should respect doktype filters (and other localizable ones) properly in all languages.
I understand that TYPO3 does filtering on the default language level only at many places, but this is inconsistent behavior.

see: https://github.com/TYPO3/typo3/blob/main/typo3/sysext/seo/Classes/XmlSitemap/PagesXmlSitemapDataProvider.php

This is true for TYPO3 10–12.

Author Martin Schulz
Created 06/14/23, 07:00
Updated 01/19/25, 15:31
Feature
New Orphaned Backend User Interface

#105951 Filter table by column value before csv download

I would like to export and download all fe_users that are filtered by a specific column, so for example all fe_users who are living in Germany or all users who are subscribed to a newsletter (checkbox). While it is possible to search for “Germany” for the country and then export those records, I cannot search for “newsletter:1” or just “1” as it would then select all searchable fields and search for “newsletter:1” or “1”.

I can also not use the lowlevel search module as i can only build my query there but export is not implemented there :(

So the only way to export the data currently is via a third party extension or a database tool. In my opinion TYPO3 core should be able to provide this feature out of the box.

Author Simon Schaufelberger
Created 01/16/25, 15:20
Updated 01/16/25, 15:54
Bug
New Orphaned Extbase + l10n TYPO3 CMS 12

#105948 Extbase: Translations ignore hidden state for 1:n relations, when relation is set to l10n_mode => exclude

As the title says: if you have a domain model “A”, which has a 1:n relation to another domain model “B” then the hidden state of the relation elements “B” is ignored in translated elements “A”. So on translated pages all relation elements are shown, on the same pages in the main language only the elements with hidden=0 are shown.

Users can work around this by also setting the hidden state in the translated record. For relations with 'l10n_mode' => 'exclude' this is not possible, as the relations are only managed in the main language record and the hidden field never gets updated in the database.

Author Manfred Egger
Created 01/16/25, 11:23
Updated 01/16/25, 12:12
Feature
New Orphaned Link Handling & Redirect Handling

#105934 Allow redirect to internal page regexp capturing groups

In sys_redirects module I want wo insert a redirect using regex to an internal page containing a placeholder like this:

Source path: #^/mylink/([a-zA-Z]{1}[a-zA-Z0-9_/-]+)#
Target: t3://page?uid=1$1

But the placeholder in target ($1) does not work. It works if I insert an absolute link (no t3: link) like this: https://domain.tld/my/final/link/$1

Author Bernhard Eckl
Created 01/15/25, 09:29
Updated 01/15/25, 14:48
Bug
Under Review Orphaned Database API (Doctrine DBAL) TYPO3 CMS 12

#105693 DB field without TCA breaks saving be_users

When having a table column in be_users that doesn’t correspond to a TCA field definition it’s not possible anymore to update a BE user record due to a ColumnDoesNotExistException: There is no column with name “zzz_deleted_cruser_id” on table “be_users”

This can happen after doing DB compare and having fields renamed to zzz_deleted_...

After dropping them the problem is gone.

We noticed this problem first in version 12.4.22. But it’s occurring on the current main branch as well!

How to reproduce:
  • ALTER TABLE be_users ADD column zzz_deleted_cruser_id INT(11);
  • Try and save a BE user record

It’s not reproducible with other tables such as tt_content!

Author Philipp Kitzberger
Assigned to Stefan Bürk
Created 11/25/24, 10:08
Updated 01/13/25, 16:37
Task
Under Review Orphaned FormEngine aka TCEforms TYPO3 CMS 13

#105908 Simplify TCA file extension preparation from placeholders

The TCA file field supports the placeholders common-image-types, common-media-types and common-text-types as values for allowed and disallowed.

These are resolved from $GLOBALS['TYPO3_CONF_VARS'] within the TcaPreparation::prepareFileExtensions() method.

Currently this happens with with a RegEx match and inline mapping and a special case for common-image-types to use GFX instead of SYS.

This is hard to read and unnecessarily complex. Also it makes it harder to spot these magic strings and the particular $GLOBALS['TYPO3_CONF_VARS'] access in case of changes afterwards.

For these reasons, this should be simplified.

Author Mathias Brodala
Assigned to Mathias Brodala
Created 01/10/25, 07:57
Updated 01/10/25, 08:02
Task
In Progress Orphaned Backend User Interface TYPO3 CMS 13

#104796 Use buttons instead of anchors for javascript handled actions

This epic is to collect dedicated issues to fix misusages of anchors () where buttons should be used.
Example: This is an anchor tag that should really be a button and needs migration.

<a href="#" onClick="foo();">Some title</a>
<button type="button" onClick="foo();">Some title</button>

*Note: We do not use onClick function calls, this is just an example.*
The look and feel should be kept as is for now.

Author Benjamin Kott
Created 09/03/24, 10:01
Updated 01/09/25, 20:53
Story
New Orphaned Backend User Interface TYPO3 CMS 12

#105876 Enhance information about affected records on modal confirm box when deleting records

When you delete a record, e.g. a page the modal confirm box should warn you about affected records;
in some cases this already happens, for example when you want to delete a page with a translation the modal box text is:

Are you sure you want to delete 'test [pages:1476]'? There are 1 reference(s) to this record! This record has 1 translation(s) which will be deleted, too!

but when you delete a page with subpages, the text does not mention it (albeit it would be useful IMHO)

I created this issue to collect all the issues about how to enhance the information shown on the confirm deletion modal box about all the records affected by the deletion

Author Riccardo De Contardi
Created 01/02/25, 16:52
Updated 01/02/25, 16:52
Task
New Orphaned Linkvalidator TYPO3 CMS 14

#105873 Should always store page id in tx_linkvalidator_broken_links not pid

The tx_linkvalidator_broken_links.record_pid always contains the pid of the content record. For pages, this is inconvenient because we need the uid, not the pid. We always need the page id.

It would be better if we generally store the page id instead of the pid.

The current state requires a lot of awkward DB queries where we have to consider pages and non-pages seperately:

For example:

->where(
                    $queryBuilder->expr()->or(
                        $queryBuilder->expr()->and(
                            $queryBuilder->expr()->in(
                                'record_uid',
                                $queryBuilder->quoteArrayBasedValueListToIntegerList($pageIdsChunk)
                            ),
                            $queryBuilder->expr()->eq('table_name', $queryBuilder->quote('pages'))
                        ),
                        $queryBuilder->expr()->and(
                            $queryBuilder->expr()->in(
                                'record_pid',
                                $queryBuilder->quoteArrayBasedValueListToIntegerList($pageIdsChunk)
                            ),
                            $queryBuilder->expr()->neq('table_name', $queryBuilder->quote('pages'))
                        )
                    )

https://github.com/TYPO3/typo3/blob/83a4a08b2a47534746593ae23f0d6e870f714f53/typo3/sysext/linkvalidator/Classes/Repository/BrokenLinkRepository.php#L107C17-L123C22

 $constraints = [
                $queryBuilder->expr()->or(
                    $queryBuilder->expr()->and(
                        $queryBuilder->expr()->in(
                            'record_uid',
                            $queryBuilder->quoteArrayBasedValueListToIntegerList($pageIdsChunk)
                        ),
                        $queryBuilder->expr()->eq('table_name', $queryBuilder->quote('pages'))
                    ),
                    $queryBuilder->expr()->and(
                        $queryBuilder->expr()->in(
                            'record_pid',
                            $queryBuilder->quoteArrayBasedValueListToIntegerList($pageIdsChunk)
                        ),
                        $queryBuilder->expr()->neq('table_name', $queryBuilder->quote('pages'))
                    )
                ),

https://github.com/TYPO3/typo3/blob/83a4a08b2a47534746593ae23f0d6e870f714f53/typo3/sysext/linkvalidator/Classes/Repository/BrokenLinkRepository.php#L266C12-L282C19

etc. ….

Author Sybille Peters
Assigned to Sybille Peters
Created 01/01/25, 10:32
Updated 01/01/25, 10:32
Bug
New Orphaned Backend User Interface TYPO3 CMS 12

#97152 Usability problem in listings: horizontal scrollbar not visible initially

In the list of reference (opened via the file list) you must scroll down to see the edit action buttons if the visible content is too wide.

There is a horizontal scrollbar on the bottom, so there is a way to reach the clipped off content.

This is only a bother, if there are lots of entries and you don’t see the scrollbar and you either have to scroll down and back up (or you are not aware there is a scrollbar and not aware there is more content).

Problems

  • have to scroll down or know how to scroll horizontally to reach action buttons to edit
  • inconsistency: e.g. in redirects module, you can also click on “Source Path” to edit, in the list of references you can only edit by clicking on the button
  • instead of using the action buttons, it is possible to click on the icon or the title, but this behaviour is also a bit hidden because the links (in the Backend in general) are not styled as links, only visible as links on hover and you have to hover exactly over the text or icon – not the entire area, see comment http://forge.typo3.org/issues/97152#note-16

Reproduce

Intention: we want to see a list of references for a file and make changes in a (related) content element.

  1. Use latest main branch with styleguide
  2. Let styleguide create content
  3. In file list click on fileadmin/styleguide and choose a file, e.g. bus_lane.jpg and click on the “Ref” link (right column)
  4. When scrolling down we see the “References to this item”

The content is clipped, we do not see the action buttons. We must scroll down to do that to get to the horizontal scrollbar.

The problem exists due to the following. Some of these are a question of general BE UI concept.

- It is not possible to resize the dialog (this is generally so, so it complies to general BE UI concept)
- In some other dialogs in the BE, in addition to the action icons on the far right, you can also click on a link in the columns. This is the case in the redirects module, for example. You can edit by clicking on source_path column. I do not find this intuitive, but in cases like these it would be helpful
- The clipping of tables can be prevented by setting a fixed size (e.g. done in linkvalidator list). But in most other cases, it is not done, so you do get the scrollbar.
- The action buttons are on the far right and in combination with above can be clipped easily. This complies to general BE UI concept (also mentioned in styleguide extension).

Example 1: Listing of references

After scrolling down:

Example 2: redirects module

Here, there is also a horizontal scrollbar and content is cut off, but you can edit by clicking on the link in “Source path” column (not really intuitive because no visible indication what the link does).

Author Sybille Peters
Created 03/09/22, 13:50
Updated 12/23/24, 09:15
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 9

#83970 Localize / Synchronize buttons are missing for Text & media assets

Tested with current master (9.2.0-dev).

If some “assets” are inserted into “Text & media” and translated (translate, not copy) and the elements in the original language are changed (order changed, new ones inserted etc.), I would expect the buttons “Localize all records” / “Synchronize with original language” to be displayed for the translation.

This does work with CE “bootstrap carousel” from bootstrap_package using “Items”, but not with Text & Media “assets”.

Note : for “Carousel” (CType “carousel”) with bootstrap_package 15.0.0 (with TYPO3 13) no button appears if the order is changed, but a button appears if a new item is added in original language.

Reproduce

Use installation with several languages, e.g. coredev installation with “styleguide”

  1. Create a page
  2. Translate the page
  3. Add “Text & Media” CE
  4. Add 2 images in “assets” field in tab “media”
  5. translate content with “translate” button, use “translate” (connected) mode
  6. Now change order of images in CE of original language, save
  7. Edit translated CE (to see if there is a button to synchronize)
  8. Now add a new asset in the original
  9. Edit translated CE again

I would now expect a way to synchronize the “assets” with original language.

Do the same thing with bootstrap_package “Carousel” items and check if buttons appear in translated CE after change in original language.

Analysis

May be missing TCA options ‘showSynchronizationLink’ and ‘showAllLocalizationLink’?

Versions

  • originally reported for TYPO3 v9
Author Sybille Peters
Created 02/20/18, 00:23
Updated 12/19/24, 19:44
Bug
New Orphaned Install Tool TYPO3 CMS 12

#96042 Row update wizard may consume too much memory for tables with many records and content

Reproduce

I did not reproduce it exactly like this but it should be able to be reproducible:

1. Use a row updater
2. Apply this on a table with lots of rows and fields with lots of content (e.g. tt_content).

When the QueryBuilder Statement is constructed, it will out of memory.

See also patch set 1 where a test was used to create a number of rows: https://review.typo3.org/c/Packages/TYPO3.CMS/+/72243/1

The test has now been removed because not really necessary for patch, just to check that out of memory is possible with current code.

Possible todos

1. Fix this. Can be done with chunking, but how to define the size of chunks?
2. Think about how to fix these things in general and find other places

Author Sybille Peters
Created 11/20/21, 19:06
Updated 12/19/24, 19:36
Bug
New Orphaned Localization TYPO3 CMS 13

#105839 Language synchronization updates wrong elements

Given:

- install the example extension
- create a new page “page1“
- edit the page and add a teaser element with an image
- add a translation of the page and localize the teaser
- copy the page and paste after
- open the original page1 and change the image in the default language

Expected behaviour:

- image of translated teaser is changed
- image of copied translated teaser is not changed

Actual behaviour:

- both images of the translations are changed

Author Nicole Hummel
Created 12/17/24, 13:25
Updated 12/17/24, 18:02
Task
New Orphaned TypoScript TYPO3 CMS 13

#102102 Refactor TS IncludeTree Import detail

The TS parser is essentially three parts: tokenizer, include / condition tree builder, ast builder.

While it seems we got tokenizer and ast builder pretty right in v12, the include tree is a bit clumsy.

One detail is that the object construct of @import / include_typoscript is a bit unfortunate:

When a snippet contains import, that snipped is marked isSplit=true. That's good, since "split=true" says that the entire snipped is represented by it's child nodes. Having two lines, one a simple assignment, another one the import, will then create two child nodes: one for the assignment “segment”, one for the import. However, the import is one object. The content of the imported file is set as lineStream, and the import code line itself is set as "originalLine". This leads to the situation that no child node is generated when an import does not resolve to a file, which then gives headaches with the syntax scanner looking for invalid imports, as well as the source renderer in the backend modules.

It would be better to split this: An import / include_typoscript should *always* create a child node that represents the import code line. If it does not resolve to something, it should create a “invalidImport” object or similar. The content of the included file(s) should then be child nodes of that node.

Doing this will simplify the overall code, will improve the BE module renderings, and we can get rid of the “original” properties in the include classes, will simplify the code that looks for ‘empty’ includes, and will streamline the source rendering in the backend modules.

Author Christian Kuhn
Created 10/06/23, 11:46
Updated 12/17/24, 11:21
Feature
New Orphaned Site Handling, Site Sets & Routing

#105726 Resolve placeholders in Yaml config with site set settings

Before, I could easily do:

routeEnhancers:
  NewsDetail:
    type: Extbase
    extension: News
    plugin: Pi1
    limitToPages:
      - '%settings.detailpids.news%'

as the settings were part of the config itself.

But now with site sets it’s no longer possible, as the settings are stored in a separate file and are also not imported into the config.

I could of course add the settings to the config again or (which I’m currently doing) just specify the page ids directly instead of using placeholders.

It would be great if thise feature is extended to include site sets settings as well.

Greetings

Author Lars Peter Søndergaard
Created 11/29/24, 08:59
Updated 12/13/24, 21:36
Bug
Needs Feedback Orphaned File Abstraction Layer (FAL) TYPO3 CMS 12

#95122 TYPO3 falesly indexes file CHANGE time (ctime) into sys_file.creation_date.

Updated description

TYPO3 indexes a file’s mtime into sys_file.modification_date, which is correct. The mtime = modification time of file content.
TYPO3 indexes a file’s ctime into sys_file.creation_date, which is wrong . The ctime = change time of the file node (including name, access modifiers, and content).

ctime >= mtime, basically always.

The “c” stands for “change”, not “creation”.

TYPO3 also labels this sys_file.creation_date field in the backend as “Created At”, which is wrong, as it contains semantically the filesystem change time of the file, as noted above.

Original ticket Description

Hey guys,

It seems that create date and Last modified date in FAL is reversed (info and ref view.) Checked it in TYPO3 7/8/10.

Cheers,

Andrea

Author Andrea Herzog-Kienast
Created 09/06/21, 14:35
Updated 12/12/24, 08:38
Epic
Accepted Orphaned Performance

#93547 Collection of problems with large sites

I used the following tags in sub-issues – where appropriate.

tags : “large-site”, “memory hog”, “prepared statement”, “placeholderlimit”, “memory”, “performance”, “throttle”, “usability” (or UI related things)

All issues related to large site are tagged with large-site.

———-

Can be many pages, many files, many directories, many categories, etc. or a combination.

The problems are mostly related to:

  • performance and resource (memory) problems.
  • exceptions, e.g. database query – “Prepared statement contains too many placeholders”
  • usability: e.g. long, unusable lists (see sys_filemount: long list of directories + performance issue, unable to filter for specific pages in pagetree filter etc.)

Can the question of large sites be addressed in general?

e.g.

  • consider large sites when creating concepts for new features
  • create a reference “large site”
  • test patches on “large sites”
  • define hard limits / soft limits (if possible) – e.g. are there specific known limitations, can we say TYPO3 easily runs with x number of pages (redirects, sites, files, be user groups etc.) in a typical installation (e.g. with a reference site)
Author Sybille Peters
Created 02/19/21, 06:57
Updated 12/11/24, 14:55

Showing results 1151 to 1175 of 1561