Showing results 76 to 100 of 1561

Feature
Accepted Orphaned Form Framework

#101763 FormEditor: Add visibility to finisher

Context

An editor has a finisher with several options. He wants to switch it off for reasons. To do this, the editor must delete the finisher completely. Unfortunately, there is no control of the finisher.

Possible solution

The finishers get the keyword hidden in the YAML with the default value false. The FormEditor is extended with a button and controls this new value. For space reasons, the padding on the left of the finisher can be removed.

Author Guido Schmechel
Created 08/26/23, 14:23
Updated 10/15/24, 09:46
Feature
Author Alexander Schnitzler
Assigned to Alexander Schnitzler
Created 07/21/23, 07:35
Updated 10/15/24, 08:19
Task
New Orphaned felogin TYPO3 CMS 13

#105269 Consider to change TypoScript configuration in ext:felogin

ext:felogin uses a plugin specific TypoScript configuration by default plugin.tx_felogin_login. This makes it impossible to override plugin settings, when the felogin plugin is includes via TypoScript (USER or EXTBASEPLUGIN), since extbase configurationManager always prefers plugin specific configuration and thereby overrides possible configuration defined in USER or EXTBASEPLUGIN.

It should therefore be considered to rename the TypoScript configuration to plugin.tx_felogin in TYPO3 v14 as a breaking change

Author Torben Hansen
Assigned to Torben Hansen
Created 10/11/24, 06:39
Updated 10/14/24, 05:27
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#104679 Inconsistent behavior of form fields with .has-change class

System settings: Light mode, Windows 10, Chrome / Firefox

  1. brings a new style for .has-change CSS class of form elements. This leads to the following behavior:

+-Scenario 1:+
-When I, as a user, insert a new content element, all input and selection fields are immediately colored blue and the form label is marked with an info icon. When the mouse hovers over the icon, no further information is given as to why the info icon is there or why the field is colored blue. These are also not mandatory fields.

Wish: A note for the user when the mouse hovers over the icon would be desirable. In addition, not all fields should immediately be marked blue per se.

+Scenario 2:+
If I select a field in an existing content element, make a different selection (select field) or enter additional text (input field) and completely undo these changes, the fields are still displayed in blue with an info icon in front of them, without there being any actual change.

Wish: If no content change has been made in the field, then the field should not be marked blue and the label should not be marked with an info icon.

+Scenario 3:+
If I change a switch checkbox from deactivated to activated in an existing content element/data record, then the .has-change class has no visual influence on the field and thus the change to the field is not clear.

In addition, a change to a switch checkbox generally does not lead to an icon on the form label.

+Scenario 4:+
If I make a change in an RTE, then the field is neither colored blue nor is an info icon placed in front of the label. This is probably for technical reasons (CKEditor), but its behavior is in contrast to the now strong visual highlighting of changes in the other form fields.

Author Jasmina Ließmann
Created 08/21/24, 10:51
Updated 10/07/24, 14:24
Feature
Accepted Orphaned Security

#80792 Password strength meter for BE Login

Provide a strength meter for password fields to give the user a hint about the password he chooses.

Author Anja Leichsenring
Created 04/10/17, 16:51
Updated 08/03/24, 06:39
Bug
New Orphaned Extbase TYPO3 CMS 11

#102209 f:form Fields use old values after ForwardResponse

Hi,

when using an object in a f:form Field and this object gets replaced after submitting the form by a forwardResponse which forwards to the form again, the form still uses the previous object.

I try to explain my scenario as I think this makes it easier to understand.

I have two actions:
- newAction
- createAction
The newAction has an optional Argument $previousLog.
The create Action also has an argument $previousLog. $previousLog is a persisted Record.
The createAction creates a new $log Record (linked to the previous) and does some checks. If these fail, it persists the $log record and returns a forwardReponse to the newAction, passing the $log record as $previousLog using $forwardResponse->withArguments()

In the Template new.html there is a form field like this
@<f:form name="previousLog" value="{previousLog}"></f:form>
(could also be f:form.textfield)
After the first forward happened, this field is correct and looks like this:
<input type="hidden" name="tx_myext_myplugin[previousLog][__identity]" value="1">@

Now if there is another forward after submitting the form the hidden input still has the same value it had first time(1). No matter how many times you repeat the form submit.
Though if one does
@<f:debug>{previousLog}</f:debug>
or just output
{previousLog}@ directly the value is correct (2, then 3 and so on).
I had a look at
_\TYPO3\CMS\Fluid\ViewHelpers\Form\AbstractFormFieldViewHelper::getValueFromSubmittedFormData_
There a value from getLastSubmittedFormData() is used preferably and only if this is not available the value-Attribute of the viewhelper is used. This function uses $this->renderingContext->getRequest()->getOriginalRequest()->getArguments() So I guess this does not take the forwardResponse into Account.
But I could not dig deeper until now, as I already spent a lot of time in finding out what was going on here.

It works fine with a redirect instead of forward.

Tested on TYPO3 11.

Author Jonas Götze
Created 10/19/23, 15:42
Updated 08/01/24, 16:05
Story
New Orphaned Extbase + l10n TYPO3 CMS 13

#101565 Frontend related translation issues

This is a sub container to collect issues that are related to Frontend output and translations

Author Jo Hasenau
Created 08/03/23, 20:24
Updated 07/31/24, 10:40
Task
New Orphaned Backend User Interface TYPO3 CMS 13

#104106 Add live region to announce checking other checkboxes in read and write permissions for table restrictions

Use polite live region and announce “Checkbox page read also checked” and respective “Checkbox page write also not checked”.

For the toggle options the announcement would be “All read checkboxes also checked” and respective “All write checkboxes also not checked”.

Hints:
- the live region must be emptied after a timeout to allow announcing the same value again for the next checkbox. This needs to have a timeout (see code below)
- assistive technologies use “not checked” instead of “unchecked” because the announcement is easier to recognize.

document.getElementById('liveregion').innerText='Checkbox page read also checked';
setTimeout(()=>{document.getElementById('liveregion').innerText='';},500);
Author Michael Telgkamp
Created 06/14/24, 08:21
Updated 07/31/24, 09:00
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 10

#79069 Allows to add/remove --div-- in pageTsConfig

Hi,

With the methods addItemsFromPageTsConfig/removeItemsByRemoveItemsPageTsConfig (TYPO3\CMS\Backend\Form\FormDataProvider), it is possible to add/remove items to a select column.

Actually it is possible to deal only with one separator(—div—) like this : TCEFORM.table.field.addItems.--div-- = Separator
If I try to add another separator, the first one is overriden.

I purpose to change the syntax like in the extension “news”. To add a separator, the syntax must be like this : TCEFORM.table.field.addItems.10 = --div--,Separator

In addition an item with this syntax TCEFORM.table.field.addItems.--div-- = Separator must be by passed.

The same must be set when removing items with removeItems, I purpose a syntax like this : TCEFORM.table.field.removeItems = 10, 20,--div--|Separator (the name of the —div— after the pipe).

Finally, if items are sets directly in the TCA and an item is added with the same key in pageTsConfig, the item is added instead of override the TCA item (the result is a select box with same values). This muste be avoided.

Thanks

Author Eric Chavaillaz
Created 12/22/16, 10:32
Updated 07/17/24, 13:49
Bug
Under Review Orphaned Performance TYPO3 CMS 8

#82100 Backend Form Dataprovider load every foreign Entity, not only the related one

Hi,

I notice a massive performance drop if I add in TCA a label_userFunc.
I found the reason in the TYPO3\CMS\Backend\Form\FormDataProvider\AbstractItemProvider::processForeignTableClause

For my Setup

I have 2 Entities Post and Comment, these are Bidirectional Related with ManyToOne.
Post has a inline TCA which load all related Comments.
Comment has a label_userFunc in TCA which simply format a Datetime into the title.

After I Try to Debug the label_userFunc, i notice the method are called WAY TO OFTEN.
Then I look at the Queries. I saw that simply the sql Relation are missing in the Query.

That means every time I want to edit a Post, Typo3 load EVERY Comment from a certain PageId.
Example:
- Post_A has 3 Comments.
- All Posts together conatins over 9000 Comments.

If i want to edit Post_A, I expect that Typo3 Load only 3 Comments, but Actual load Every comment on the System and used on every Comment the label_userFunc.
In the End, i see only 3 comments (which is correct).

I worte myself a little workarund which redurce the system and Database load dramatically:
https://gist.github.com/anonymous/7e307e73e6842fd6d94f28ba62ab2a7d#file-abstractitemprovider-php-L135-L146

Post TCA:

    'comments' => [
            'exclude' => false,
            'l10n_mode' => 'exclude',
            'behaviour' => [
                'allowLanguageSynchronization' => true
            ],
            'label' => $ll . 'backend.tca.post.comments',
            'config' => [
                'type' => 'inline',
                'foreign_table' => 'tx_exampleBlog_domain_model_comments',
                'foreign_field' => 'post',
                'maxitems' => 9999,
                'appearance' => [
                    'collapseAll' => true,
                    'levelLinksPosition' => 'top',
                    'showSynchronizationLink' => false,
                    'showAllLocalizationLink' => false,
                    'showPossibleLocalizationRecords' => true,
                    'showRemovedLocalizationRecords' => true,
                    'enabledControls' => [
                        'info' => true,
                        'dragdrop' => true,
                        'localize' => true,
                    ],
                ],
            ],
        ],

Comment TCA:

    'post' => [
            'exclude' => true,
            'label' => $ll . 'backend.tca.post',
            'config' => [
                'type' => 'select',
                'renderType' => 'selectSingle',
                'foreign_table' => 'tx_exampleBlog_domain_model_post',
                'minitems' => 0,
                'maxitems' => 1,
            ],
        ],
Author Benjamin Rannow
Created 08/14/17, 16:13
Updated 07/12/24, 17:43
Bug
New Orphaned Extbase + l10n TYPO3 CMS 11

#102578 Translated content elements can not be found when the original element is disabled

Hi,

if you create a translated element in connected mode and disable the element in the default language, the translated element won’t show up anymore too, even though it still is enabled.

It seems like the record overlay can’t be fetched because of the disabled original, so it completely gets ignored.

This issue is has a longer history like an old issue I created for v6.2: https://forge.typo3.org/issues/69022

I really thinks this needs a solution as this is confusing for redakteurs.

Greetings
Daniel

Author Daniel Dorndorf
Created 12/01/23, 10:22
Updated 07/08/24, 17:55
Bug
New Orphaned Extbase + l10n TYPO3 CMS 9

#91487 Extbase repository query using equals on a relation field is different whether one passes $entity or $entity->getUid() in multi-language context

The following two queries behave differently if in L>0 context:

$query->matching(
  $query->equals('relation', $entity)
)->execute()
$query->matching(
  $query->equals('relation', $entity->getUid())
)->execute()

When dumping $entity it is always displayed with the L=0 uid (also in L>0 context) and the overlayed fields from L>0, which is correct.

In L=0 context both queries behave the same. The second one works correct also in L>0, the first one only in L=0 context.

In L>0 context the first query extracts and uses the _localizedUid from the object. This is the bug afaik.

Discovered in 9, probably present in 10 as well.

Author S P
Created 05/26/20, 10:46
Updated 07/08/24, 17:55
Bug
New Orphaned Extbase + l10n TYPO3 CMS 9

#88853 Updating relations of translated domain objects does not work if they already exist

Hey,

for my product import i must to sync relations of translated domain object models to every translated record. TYPO3 does this already right if i click on the “Save”-Button in the backend, because in my TCA configuration its set to “l10n_exclude”. But manually saving does not work for > 2500 products on a regular basis.

It works for the first time to insert m:n-relations, but for every next try it tries to insert the value, which of course already exists instead of checking for an already existing relation. Is it possible to quickly fix this or just ignore the sql error and continue with my import? Ignoring would be fine, if i only add relations instead of updating them. Exception: TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException ]
Duplicate entry ’2636-13674’ for key ‘PRIMARY’.

My current solution is to just delete all relations via sql before my import starts:
DELETE FROM tx_gwproductcatalog_product_category_mm WHERE uid_local IN (SELECT uid FROM tx_gwproductcatalog_domain_model_product WHERE sys_language_uid != 0);

I attached the error log calling this from a backend module.

Author Anton Fries
Created 07/29/19, 14:43
Updated 07/08/24, 17:55
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 12

#104331 \TYPO3\CMS\Core\Resource\FileRepository::findByRelation incapable of handling FAL relations in FlexForm in BE context

The method internally assumes that any fieldname passed to the function is a root-level TCA field. It completely ignores that FAL relations are also possible within a FlexForm context. Specifically, BackendUtility::getTcaFieldConfiguration($tableName, $fieldName) fails if $fieldName is not a root-level TCA field, causing the findByRelation to always return an empty set. Note that BackendUtility::getTcaFieldConfiguration is incapable of returning a TCEforms config array from within a FlexForm DS regardless of how you construct the $field argument.

The same problem does not exist in FE context because the method internally switches to a standard query. But in FE context another problem exists – it completely ignores any and all additional DB relation constraints like `MM_match_fields`, and ignores the workspace ID. As such it is broken for anything other than a completely vanilla FAL IRRE setup.

Unfortunately this means that the FileRepository is not trustworthy in either context. Either it is partially broken, or it is incomplete – neither context is fully functional.

One solution could be to make \TYPO3\CMS\Core\Resource\FileRepository::findByRelation require a TCA config array as argument, avoid the use of BackendUtility::getTcaFieldConfiguration and then make it use RelationHandler exclusively and drop the condition block that switches to a query in FE context. Not only would that fix the described problems, it would also reduce the complexity of FileRepository itself.

PS: This problem exists in all versions of TYPO3 since the introduction of FileRepository but the TYPO3 version of this issue has been set to 12 since that’s the only LTS that needs to be fixed. If ELTS also needs to be fixed this version goes back a lot further.

Author Claus Due
Created 07/08/24, 12:56
Updated 07/08/24, 12:56
Bug
New Orphaned Extbase TYPO3 CMS 12

#103434 Extbase should check for property, not getter first

I have this custom code in my Extbase model:

class News extends AbstractEntity
{
    protected string $authors = '';
    protected string $subsidiaries = '';
...
    public function getSubsidiaries(): array
    {
        return GeneralUtility::trimExplode(',', $this->subsidiaries);
    }

In TCA, this is a field of type select / selectMultipleSideBySide.

Extbase / Symfony PropertyInfo is detecting the field as array, even though the property is a string, due to the getter method, and cannot handle an array yet:
https://github.com/TYPO3/typo3/blob/0e1b095b51edd20e10f05edbec630e0a57074c08/typo3/sysext/extbase/Classes/Persistence/Generic/Mapper/DataMapper.php#L251C17-L251C23

For this reason, the property will never get mapped.

If I create a getter “getAvailableSubsidiaries(): array” and remove the original mapper, the type will be detected as string and then populated in DataMapper.

I think the property should take precedence over the getter.

Author Benni Mack
Created 03/20/24, 11:19
Updated 06/24/24, 14:10
Bug
New Orphaned Localization TYPO3 CMS 12

#82314 Copying content to other language creates duplicates

Hi everyone,

we have a page (german) with two translations (dutch and one for austria).
The content for dutch is translated via translation wizard and mode ‘Translate’ to connect the content elements.

The editor now wants to copy german content via drag’n‘drop while holding ctrl to austria.

Results:
1. The content is created correctly within the translation for austria.
2. The dutch representation of the german content element is duplicated within the dutch translation.

Expectation:
Result 2 should not occure.

Note: Deleting the copied element for austria also removes the dutch duplicate.

Kind Regards,
Jonathan Kieling

Author Jonathan Kieling
Created 09/06/17, 11:42
Updated 06/16/24, 07:04
Bug
New Orphaned Backend User Interface TYPO3 CMS 12

#104019 The "Paste" button does not have adequate labeling.

To improve accessibility for screen reader users, the Paste button should be labeled similarly to the + Content button. See https://forge.typo3.org/issues/104018. The ID of the title and the Ctype are suitable for labeling.

Author Christian Rath-Ulrich
Created 06/10/24, 13:47
Updated 06/10/24, 13:47
Feature
New Orphaned Dashboard

#90443 Idea for dashboard at initial installation of new TYPO3

It would be cool to add a new dashboard to the first user after a TYPO3 installation was successful.
That dashboard could carry all necessary information to get started. Would make also sense to make it the default module instead of the “About”.

That way new users that setup a TYPO3 installation get an “Introduction Dashboard” with all information to get deeper into the system.
Also static texts like “Next Steps” could be added.

That might improve the user experience for first time users.

Author Daniel Siepmann
Assigned to Richard Haeser
Created 02/19/20, 20:20
Updated 06/09/24, 18:39
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 11

#103870 Element browser search respects only the first given filemount

When an editor uses the search field in the element browser, only the first filemount is respected:

After entering “Bild” as search query, there are only results from the first filemount:

Expected behaviour: the selected filemount or all filemounts should be respected in search.

Author Holger McCloy
Created 05/21/24, 14:16
Updated 05/21/24, 14:19
Feature
New Orphaned File Abstraction Layer (FAL)

#90623 FAL: video thumbnails in BE module Filelist

The thumbnails of video files (eg: .mp4, .avi) are not displayed in the backend filelist module

Author Robert von Hackwitz
Created 03/03/20, 10:39
Updated 05/03/24, 18:08
Feature
Needs Feedback Orphaned Backend User Interface

#93344 Translate button disappear

If the base language has no content elements the translate button disappear. So you even can not translated from one translate language to another translated language. If you add one dummy element to base the translate button appre and it works fine even the translating language to another translated.

Author Timo Poppinga
Created 01/22/21, 08:23
Updated 04/01/24, 17:42
Feature
New Orphaned Site Handling, Site Sets & Routing

#103486 Configurability of the PageRouter

Hello,

I wanted to extend the PageRouter for a project but there seems to be no way without XClass.

Searching through the core I found the getRouter function in the class TYPO3\CMS\Core\Site\Entity\Site, which was commented with:
??Returns the applicable router for this site. This might be configurable in the future.??

Would this be something to be still implementable as a patch for v12 or only for v13?
(I would think adding a registration for an own class would’nt be a breaking change)

I don’t know if someone already had thoughts on this so I hope it’s okay to open this issue for the topic.

Author Daniel Dorndorf
Assigned to Stefan Bürk
Created 03/26/24, 13:06
Updated 03/26/24, 13:28
Bug
Accepted Orphaned Fluid TYPO3 CMS 12

#100758 Viewhelpers and other things do not work outside of extbase context

Using f:form* or f:*.action viewhelpers does not work anymore outside of extbase context. For instance within StandaloneView or FLUIDTEMPLATE.

StandaloneView is regularily used for rendering e-mail and there of course links should be generated.

It should be checked if this still works:

  • f:form viewhelper do correctly prefix the fieldnames. E.g. having an non-extbase plugin using StandaloneView the prefix should be like `tx_myext_pi1[name]` for a name input field

——

Collection of notes from other forge issues:

f:form – Exception:
(1/1) #1639821904 RuntimeException
ViewHelper f:form can be used only in extbase context and needs a request implementing extbase RequestInterface.
/vendor/typo3/cms-fluid/Classes/ViewHelpers/FormViewHelper.php line 148

f:link.action – Exception
(1/1) #1639818540 RuntimeException
ViewHelper f:link.action can be used only in extbase context and needs a request implementing extbase RequestInterface.
/vendor/typo3/cms-fluid/Classes/ViewHelpers/Link/ActionViewHelper.php line 81

In both cases the “TYPO3\CMS\Core\Http\ServerRequest object” is in the $request instead the RequestInterface.

Author Markus Klein
Created 04/26/23, 10:06
Updated 03/07/24, 10:08
Bug
New Orphaned Backend User Interface TYPO3 CMS 11

#97317 Duplicates when pages are copied

Creating a copy with the clipboard tends to create undesired additional copies.
One reason I remarked is when the site is reloaded, that might be the case even without user-action by the browser.
Further things like large page-trees could be possible reasons too.

I never verified how the task to create the copies are temporally saved, at least it’s not sufficient.
The copies have to be filtered / deleted manually to remove undesired ones.

Author David Bruchmann
Created 04/06/22, 10:38
Updated 02/29/24, 11:18
Bug
New Orphaned Workspaces TYPO3 CMS 11

#103173 Workspaces: starttime will not respected after pulishing a news into the live-workspace

I checked two procedures in a local TYPO3 system (ddev, TYPO3 11.5.35 & News 10.0.3):

behavior expected:
1. I create a news in the live system and define the `starttime` for the news-record. I surf the frontendpage of the news page before the starttime and don’t see the news. I am wainting. I reload the page after the starttime and see the news. (No need to clear cache in between.)

unexpected behavior:
2. I create a news in my workspace and define the `starttime` for the news-record. I publish the message. I surf the frontendpage of the news page before the starttime and don’t see the news. (expected) I am wainting. I reload the page after the starttime and DON’T see the news. (UNexpected) I clear the System-cache or Frontend-cache. I reload the page once more. I see the news.

The second approach seems to be a bug to me. But I’m not sure whether the error is in the news extension or in the workspace extension. I have ask that question in the slack-channel for the news extension. But the answers did not help me.

Author Dieter Dr. Porth
Created 02/21/24, 14:20
Updated 02/21/24, 15:33

Showing results 76 to 100 of 1561