Showing results 1226 to 1250 of 1561

Feature
Needs Feedback Orphaned Fluid

#91951 FLUID assets

Hello,
can we get a “order” attribute of the assets viewhelpers?

for example, I have 2 times the f:asset.script viewhelper in my template. The first one should be an inline script and the second one is an external file.
TYPO3 renders the external file before the inline one…

<f:asset identifier="first" priority="true">alert(“my inline script”);<br><f:asset identifier="functions" src="EXT:my_ext/Resources/Public/JavaScript/functions.min.js" priority="true"></f:asset></f:asset>

Maybe you can change the “identifier” to get a sort order.

thank you!

Author Christian Hackl
Created 08/07/20, 15:43
Updated 08/22/24, 16:22
Bug
New Orphaned Workspaces TYPO3 CMS 11

#103158 Workspace-View: CE menue_pages did not show link to page after special circumstances in workspace-environment

Workspace-View: CE menue_pages did not show link to page after special circumstances in workspace-environment

I have a page ‘test’ with a disabeld toogle “Page enabled in menu”[nav_hide] in the page-settings.
There is a Content-element [menu_pages] with out a link to the page ‘test’ on the startpage.
Step 1. Change into workspace.
Step 2. Generate a sysfolder named ‘footer’.
Step 3. Move page ‘test’ into the new sysfolder named ‘footer’.
Step 4. Enable the toggle “Page enabled in menu”[nav_hide] in the page-settings of ‘test’.
Step 5. Check the startpage.

estimated:
The link to the page “test” is part of the view in the view of the workspace.

reality: bug:
The link to the page is not part of the menu in the view of the workspace.

You can change the order of Step 3 and step 4. The result is the same.
If you move back the page “test” to the original position in the pagetree, there would be no longer shown any link to the page ‘test’ in the menu.

P.S.
The Step 2 seems irrelevant. The same will happen, if you move a existing page, which has a link in the menu (live), into an existing sysfolder. After that movement the link to the page is missing in the menu.

Author Dieter Dr. Porth
Created 02/20/24, 11:16
Updated 08/22/24, 13:08
Bug
New Orphaned RTE (rtehtmlarea + ckeditor) TYPO3 CMS 11

#104520 RteHtmlParser does not allow custom attribute configuration for <span> tags as children of a <p> tag

We were wondering, why it is impossible to add custom attributes to tags. It turns out, that the “allowedAttribs” definition is hard-coded only for tags in RteHtmlParser.php! This issue was reported already 9 years ago but closed.

Wouldn’t it makes much more sense to apply the YAML configuration processing.allowAttributes of Processing.yaml here as well, so we are able to customize it, like for any other tags?

*Use-Case:*
In CKEditor we want to add an editor-plugin for ToolTips which can be placed on whole headlines, paragraphs, but also on single words:

<h1>Hello <span data-tooltip-content="This works!" data-tooltip-position="auto">world</span></h1>
<p data-tooltip-content="This works!" data-tooltip-position="top">Hello world</p>
<p>Hello <span data-tooltip-content="Why is this not working?">world</span></p>
If we append these data-attributes to processing.allowAttributes, it works perfectly well for the

and the

tag. But everything is stripped away from the if

is the parent tag ! The header has a as child to mark only one word, and here its working. So this should work on

as well, but it isn’t.

Is there a reason for it or is this just a left-over behavior of old times? Our current (ugly) workaround is the usage of a composer-patch.

Background:*
The JavaScript to init the tooltip uses the data-attribute like *tooltip(‘[data-tooltip-content]’, {});
with some default options, which can be overwritten by the data-attribute (see e.g. “data-tooltip-position” in the above example)

Author Bastian Stargazer
Created 08/01/24, 13:58
Updated 08/15/24, 08:26
Feature
Under Review Orphaned Content Rendering

#91933 Add an option to include the poster attribute in VideoTagRenderer

Could we add the possibility to add the poster attribute in the VideoTagRenderer?

Author Kevin Ditscheid
Created 08/05/20, 13:00
Updated 08/07/24, 15:14
Bug
Accepted Orphaned Categorization API TYPO3 CMS 8

#65404 File collection : allow multiple category selection

It’s currently not possible to create a file collection with multiple category selection.

Author David Lemaitre
Created 02/27/15, 16:21
Updated 08/07/24, 13:42
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
Feature
Accepted Orphaned Caching

#17630 gr_list concept needs to be improved

TYPO3 uses the “gr_list” which indicates the groups of which a frontend user is a member of.

This information is used to identify cache records, indexed records, and probably more.

If user A is a member of group 1 while user B is a number of groups 1 AND 2, both can’t use the cached page which has been built for the other gr_list, even if their content is exactly the same.

One of the resulting problems of this are:
- page needs to be built multiple times (which is not needed in many situations)
- users cannot find indexed content before someone else having the same gr_list has visited (=> indexed) the page
(issue imported from #M6403)

Author Michael Stucki
Created 09/27/07, 10:45
Updated 08/03/24, 06:35
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
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 11

#100351 ElementBrowserRecordlist::isRowListingConditionFulfilled does not work with flexforms

*Story*
The element browser should respect the filter property of group fields.
This works for regular TCA group field definitions but not for group fields comming from a flexform.
This missbehavior is caused by function isRowListingConditionFulfilled fetching the field configuration from from the relating table and field which in case of a flexform is always “tt_conntent”/pi_flexfrom insteand of the actual configuration within the flexform.

Therefor filter userfunc are not executed for groupfields configured within flexforms.

*Reproduce*
Add a flexform to a plugin.
E.g.:

<config>
    <type>group</type>
    <internal_type>db</internal_type>
    <allowed>tx_foo_domain_model_bar</allowed>
    <minitems>1</minitems>
    <filter>
        <numIndex index="0">
            <userFunc>Foo/User/Filter->doFilter</userFunc>
            <parameters>
                <myParameter>abc</myParameter>
            </parameters>
        </numIndex>
    </filter>
</config>    

*Expected Behavior*
Foo/User/Filter->doFilter should be called

*Actual Behavior*
Foo/User/Filter->doFilter is not called because isRowListingConditionFulfilled looks for a filter in

$GLOBALS['TCA']['tt_content']['columns']['pi_flexform']['config']

*Possible Solution*
Introduce an exception for pi_flexform. Not that easy though because the content of the pi_flexform is not available at this point.

Author Nikolas Hagelstein
Created 03/29/23, 15:48
Updated 07/31/24, 13:46
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 11

#100863 Shortcut page url with id and non-existing language fails

Reproduce:
  1. Create a page with uid X as shortcut to another page.
  2. Having a site without languages, config.linkVars is not set
  3. Open browser with url: https://www.your-site.com/index.php?id=X&L=1

Expected result:
The target page is opened with resolved url and without language parameter

Experienced result:
The frontend breaks with message “The target page does not have a language with ID 1 configured in its site configuration.“
Code lines: typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php:4800-4823

TYPO3 11.5.27

Author Stefan Terborg
Created 05/12/23, 07:01
Updated 07/31/24, 11:07
Story
New Orphaned Localization TYPO3 CMS 13

#101564 User Interface related translation issues

This is a sub container to collect issues that are related to the user interface during translation processes

Author Jo Hasenau
Created 08/03/23, 20:09
Updated 07/31/24, 10:41
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
Story
New Orphaned Extbase + l10n TYPO3 CMS 13

#101566 Extbase related translation issues

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

Author Jo Hasenau
Created 08/03/23, 20:32
Updated 07/31/24, 10:40
Bug
New Orphaned Performance TYPO3 CMS 11

#101798 Prevent saving unchanged inline records to save performance

Problem

When you have a record, which has 10 inline items and the record is translated (along with the inline items) into 10 languages, then saving the record even with no changes to the inline items causes the DataHandler to save 110 database records which can take some 30 seconds.

Why is that?

The inline records have toggles to hide/unhide them (unless the table does no support that), which means when saving the record there will be a `someid => [‘hidden’ => ‘0’]` entry for each inline item, which causes DataHandler to save that inline item, which then also triggers saving of its translations.

Solution(?)

It could be solved in backend JavaScript, so that the inline `hidden` form fields are only included in the request when their value was changed.

Workaround

For our project I created a backend middleware, that intercepts the `data` when a record is saved and removes any entries, that have just the hidden field and it is unchanged. (Yes, I create a database request for each of those entries but it’s still way faster than before)

Author Sebastian Michaelsen
Created 08/30/23, 11:27
Updated 07/31/24, 10:37
Task
New Orphaned TypoScript TYPO3 CMS 13

#102103 Refactor TS IncludeTree condition detail

Similar to #102102

The “condition” include object tree structure should be improved: A “body” include should be added as child of the condition that represents the executed body when the condition matches. The condition object itself should just contain the condition snipped. Also, the body include should then have the according body line objects set, those are currently not added at all and are only attached to the parent include, which makes everything harder than it should be, especially in IncludeTreeSyntaxScannerVisitor, and in BE module source rendering.

This change should probably be done before #102102 to simplify the needed IncludeTreeSyntaxScannerVisitor refactoring.

Sidenote: We may want to change [global] and [end] to single objects, too. I think we fiddled in this area once already, but still, it might be good to reconsider again. Having an own object for this would probably simplify the ast builder, may reduce some headaches with source rendering, and would simplify a possible detection of “double” [globals] as well, which could be implemented in IncludeTreeSyntaxScannerVisitor.

Author Christian Kuhn
Created 10/06/23, 11:51
Updated 07/31/24, 10:27
Bug
New Orphaned Workspaces TYPO3 CMS 11

#102720 Versioning should consider displayCond for children relations

Use case: I have a database table where PDF files get attached to records by an automated process. The IRRE/FAL field to which such records are attached is set as read-only. The project uses workspaces and when a new version is created, a copy of all sys_file_reference entries is also created. Upon publication, 2 problems may occur:
  1. the user has the rights to the sys_file_reference table. Even if nothing has changed, the “tstamp” field of the sys_file_reference entries are updated, which is not desirable, since we want to keep the date at which the automated process attached the file to the record.
  2. when the user does not have the rights to the sys_file_reference table, the problem gets worse: when the parent record is published, the children are left ignored. They may then appear in some other user’s workspace view, when that use has the rights to the sys_file_reference table, but they are then “detached” from their parent record.

I tried to have the field ignored in workspaces by using a display condition like VERSION:IS:false, but this has no effect on children relations.

Unfortunately, I don’t have the time to fully dig into this issue to try and submit a patch. For now, I will use one of the DataHandler hooks to clean up the mess, but I think it would be really correct to ignore dependencies when a field is excluded from workspaces (and AFAIK the display condition is the only way to exclude a field from the versioning process).

Author Francois Suter
Created 12/26/23, 08:44
Updated 07/31/24, 10:01
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 Database API (Doctrine DBAL) TYPO3 CMS 10

#91178 Applying needed DB change fails in BE using PostgreSQL

On Typo3 9.5.15 using PostgreSQL.

Using “Analyse Database Structure” from the Admin Tools I get the following needed change listed

ALTER TABLE "sys_file_processedfile" ALTER "configuration" TYPE BYTEA 
Current value: configuration TEXT DEFAULT NULL

When applying the change the following error is shown

Database update failed
Error: SQLSTATE[42804]: Datatype mismatch: 7 FEHLER:  Spalte »configuration« kann nicht automatisch in Typ bytea umgewandelt werden
HINT:  Sie müssen möglicherweise »USING configuration::bytea« angeben.

I followed the documented migration from a non-composer installation to composer based installation. After the migration was done, checking the DB structure I encountered this error.

PS: I hope this is the right place to report exceptions found by normal users, if not please redirect me.

Author Tobias Diekershoff
Assigned to Stefan Bürk
Created 04/23/20, 12:09
Updated 07/31/24, 08:44
Feature
New Orphaned Authentication

#100260 Add ExcludeFromLiveCheckInterface

In order to exclude expensive checks in custom validators from the live check via JavaScript (see #97393), the new Interface ExcludeFromLiveCheckInterface must be added.

Author Torben Hansen
Assigned to Torben Hansen
Created 03/22/23, 18:30
Updated 07/31/24, 08:41
Feature
New Orphaned Workspaces

#76429 Workspace Autopublishing

New Functionality
—————————
Webmaster/editor would like to move from stage Validated to Published automatically by giving a different publication date for each page in a single workspace

In tYPO3 7.6 Workspace Module the edited content (in draft) should be published automatically based on a date given if it is in Ready to publish stage.

Solution
————

When editing a single content there should be a publishing date option for the editors to choose , so that when it is in ready to publish stage it will be automatically published. We could write a scheduler task for auto publishing the task based on the date entered by the editor.

Author Sk no-lastname-given
Created 06/02/16, 09:10
Updated 07/25/24, 06:33
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#90436 Some weird behaviour with autogenerated site config

*Preset:*
We already have an existing page root “Root A”.

*Step 1*
Now create a new Page root “Root B”.
TYPO3 will now automatically generate new site config in the format “autogenerated-96-26657d5ff9”.
The page has the checkbox “is_siteroot” NOT checked.

*Step 2*
Move the page “Root B” somewhere inside “Root A” to make it a part of its page tree.

If you now visit the Site config module, the autogenerated site config will be now marked as unassigned.
But if you open the page in the pages module, it will still have its site config for “autogenerated-96-26657d5ff9” assigned, which can lead to many bugs.

Examples:

- My site config for “Root A” allows for translations, but I can’t translate the page “Root B”, as the autogenerated site config has no other languages than “Default”.
- If I open the page with the “view” button, the url will look something like “https://typo3.ddev.site/autogenerated-96/en/root-b”

*My conclusions:*
- Autogenerated site configs should only be created, if you create a page set with “is_siteroot” to true.
- If I delete a root page, its autogenerated (!) site config should be deleted as well.
- It’s weird, that the Site config module shows the site config as “unassigned”, but it is actually loaded in several places, as can be seen from the behaviour. My understanding was, that a page would need to have “is_siteroot” set, but that is apparently not the case?

Author Christian Eßl
Created 02/19/20, 18:01
Updated 07/19/24, 07:08
Bug
New Orphaned Extbase TYPO3 CMS 11

#104419 TCA setting "allowLanguageSynchronization" for pages records not working when using extbase model

I’ve defined an extbase model based on table “pages” in file Configuration/Extbase/Persistence/Classes.php:

return [
    \MyVendor\MyExt\Domain\Model\Teaser::class => [
        'tableName' => 'pages'
    ]
];

When I now request a translated page record…

$this->teaserRepository->findOneByUid(123)

…resulting object contains image from default language:

   media => protectedTYPO3\CMS\Extbase\Domain\Model\FileReference prototypepersistent entity (uid=350, pid=264)
      uidLocal => protected 15 (integer)
      originalResource => protected NULL
      uid => protected 350 (integer)
      _localizedUid => protected 350 (integer)
      _languageUid => protected 0 (integer)
      _versionedUid => protected 350 (integer)
      pid => protected 264 (integer)

But “media” has setting “allowLanguageSynchronization=true”, so I’ve expected the image from my translated page record here.

This is working for simple TCA fields like “type=input” and I’ve expected it’s working for images, too.

I’ve uploaded an extension where you can test the behaviour.

Author Sven Burkert
Created 07/18/24, 09:52
Updated 07/18/24, 09:52
Bug
Accepted Orphaned DataHandler aka TCEmain TYPO3 CMS 11

#101936 Duplicate MM records after copy

For TYPO3 11 (and 12) records with a bidirectional MM relations to themselves have duplicate MM records after copying them via DataHandler.

A prominent example would be EXT:news with its two columns related and related_from (stripped down to relevant parts):

EXT:news/Configuration/TCA/tx_news_domain_model_news.php:

        'related' => [
            'config' => [
                'type' => 'group',
                'allowed' => 'tx_news_domain_model_news',
                'foreign_table' => 'tx_news_domain_model_news',
                'MM_opposite_field' => 'related_from',
                'MM' => 'tx_news_domain_model_news_related_mm',
            ],
        ],
        'related_from' => [
            'config' => [
                'type' => 'group',
                'foreign_table' => 'tx_news_domain_model_news',
                'allowed' => 'tx_news_domain_model_news',
                'MM' => 'tx_news_domain_model_news_related_mm',
                'readOnly' => 1,
            ],
        ],
Scenario:
  • Install EXT:news
  • Create a folder with 2 news records, one refering to the other (via related column)
  • Copy that folder
_.Original folder _.Copied folder

Expected result: 2nd folder with 2 news records, one refering one time to the other
**Actual result:** 2nd folder with 2 news records one refering three times to the other

With TYPO3 10 this worked as expected. And since the TCA in news hadn’t changed, I assume it’s a TYPO3 core issue. Plus I can reproduce it with pages records as well.

Hint: when unsetting the TCA for the related_from field, it’s working flawlessly.

Author Philipp Kitzberger
Created 09/17/23, 21:44
Updated 07/18/24, 07:18
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
Feature
Accepted Orphaned Content Rendering

#104000 Find a better replacement for lib.contentElement

lib.contentElement currently is “kind-of” API but is not “context aware” (am I a regular Content Element, a plugin or a Content Block). We need to come up with a better API (probably a new cObject) to handle rendering of a “Record” / “Content Block”.

Author Benni Mack
Created 06/07/24, 21:03
Updated 07/12/24, 17:48

Showing results 1226 to 1250 of 1561