Showing results 1401 to 1425 of 1561

Bug
New Orphaned System/Bootstrap/Configuration TYPO3 CMS 10

#98124 potential dangerous destructor order

TLDR: classSchemata property of ReflectionService is saved to data cache (extbase) inside the destructor the class. But the destructor of the used cache frontend is called before the destructor of ReflectionService. Currently this isn’t a problem, because the standard cache frontends doesn’t contain a destructor.

I’m currently writing an extension to collect live statistics of cache usage in typo3. For this i replace the standard frontends with other frontends which contains some counters. The counters must be persisted between two calls, so i write the data to database inside the destructor of my frontends. In the stored statistics i noticed there must be some missed cache writes. Some investigations showed this is related to how the reflection service stores his data to the cache. And i found out that the destructor of my replaced frontend class was called before the destructor of the reflection service. I’m not sure if my replaced frontends cause a change in the destructor order and if the destructor order would be the same on all installations using the same configuration.

As said earlier, currently this isn’t causing problems in typo3, but it could if there would be a cache frontend which closes the connection to the cache backend in it’s destructor.

Solution: The reflection service should write his cache data before the first destructor is called. Potential problem could be, if there is a class which uses the reflection service inside of its destructor.

Author Mordamir
Created 08/11/22, 16:57
Updated 08/11/22, 16:57
Bug
New Orphaned Localization TYPO3 CMS 10

#92925 Limit to language is broken in TYPO3 10

There are some problems in the page module with user groups that are only allowed to edit the additional languages (limit to language). Behavior was simulated on an empty TYPO3 10.4.10 instance.

Structure of the user groups (Screen 0):
Author 1 – may only edit Default (EN)
Author 2 – may only edit the additional language (DE)

The behavior of author 1 is correct, he may only edit the default language.

But there are some problems with author 2, which only appear in the page module – the list module seems to work correctly.
1. he is allowed to edit the content correctly (if you click on the icon in front), but the icons in the back are missing on the CE itself. (Screen 1)
2. in Free Mode the + icons for creating new content elements are missing. (Screen 1)
3. if the additional language is still empty, the + icons and the Translation Wizard are also missing (Screen 2)
4. and last the drop-down “Create new translation of this page” is missing for a page that has not yet been translated (Screen 3)

Greetings, Alex

Author Alex Kellner
Created 11/24/20, 16:45
Updated 08/05/22, 18:30
Bug
New Orphaned Localization TYPO3 CMS 9

#84682 TYPO3 8 Relationship Localization Bug

!When it comes to bidirectional relationships, the localization handling of TYPO3 8 is a bit different than I expected to be.

Let’s say, we use price tables and seasons which are connected through a “has many relationship”.
I then create a new season and assign them to a price table.
Whenever I translate this season, its connections will also be translated because a new record will be inserted in the mm table.
If I then edit the assigned price table, the season appears twice ( original + language record ).
Additionaly, the sorting attribute of the mm table is broken because the language record receives the default value of sorting ( 0 ).

*I’ve created a minimalistic extension to demonstrate this behaviour.*
[[https://github.com/sir-script/mm_typo3_8]]

Can anybody explain,what’s wrong here?
What would you expect as standard behaviour?
Should the mm table contain these language overlay records and the presentation is wrong?

Author Michael Rainer
Created 04/10/18, 09:47
Updated 08/05/22, 07:24
Feature
Under Review Orphaned AdminPanel

#97585 Explain SQL queries in AdminPanel

The explaination can give a hint when queries are slow.

Author Christoph Lehmann
Created 05/08/22, 16:31
Updated 07/12/22, 11:33
Feature
New Orphaned

#97496 Return 401 on failed login

Return 401 HTTP code on failed login to the BE and felogin so an intrusion prevention software like fail2ban can be configured to detect brute force attacks.

Author Christian Toffolo
Created 04/28/22, 06:51
Updated 07/12/22, 09:08
Feature
New Orphaned Site Handling, Site Sets & Routing

#91504 Subpages of pages with access setting "extendToSubpages" should be able to override this settings

Quite a bit complicated to explain but I’ll try:

Example Pagetree:

.
├── Page Level 1 A (Usergroups: A and B - ExtendToSubpages: true)
│   ├── Subpage Level 2 A
│   ├── Subpage Level 2 B (Usergroups: A, B and C - ExtendToSubpages: true)
│   │   ├── Subpage Level 3 A
│   │   └── Subpage Level 3 B
│   └── Subpage Level 2 C
└── Page Level 1 B (Usergroups: C - ExtendToSubpages: true)

I would expect that “Subpage Level 2 B” overrides the accessibility of “Page Level 1 A”. So “Subpage Level 2 B” should be accessible by usergroups A,B and C. Usergroup C would need a deep link somewhere, as “Page Level 1 A” won’t show up in menu.

The current behavior would be a “403 Page Not Found – Reason: Subsection was found and not accessible” if you access “Subpage Level 2 B” with usergroup C.

Author Alessandro Schmitz
Created 05/27/20, 11:04
Updated 06/28/22, 13:47
Bug
Accepted Orphaned DataHandler aka TCEmain TYPO3 CMS 9

#92409 Regression with Save and Preview Button

Hej,

I stumbled onto this yesterday when trying to configure multiple save and preview buttons for different folders and noticed that the links weren’t constructed properly, i.e. only no_cache parameter was created.
After debugging this I found a regression here, introduced back in 2018. Line numbers are from v9.5.21, but are also found in v10.

typo3/sysext/backend/Classes/Controller/EditDocumentController.php#1040

$previewConfiguration = BackendUtility::getPagesTSconfig($previewPageId)['TCEMAIN.']['preview.'][$table . '.'] ?? [];

The PageTS is fetched from the target page, i.e. the detail page and not the current backend folder the user is in.
Via git blame I found this review: https://review.typo3.org/c/Packages/TYPO3.CMS/+/56693/36/typo3/sysext/backend/Classes/Controller/EditDocumentController.php#b960

With a small change (I’m not sure if this is the best way to access the current page id in this context) it is working again:

$previewConfiguration = BackendUtility::getPagesTSconfig($this->pageinfo['uid'])['TCEMAIN.']['preview.'][$table . '.'] ?? [];

This might be an issue for pages, since that needed a switch before? Not 100% sure about that, because pages preview worked fine with my change.

Author Felix Jacobi
Created 09/25/20, 12:21
Updated 05/30/22, 15:48
Bug
New Orphaned Extbase TYPO3 CMS 10

#97647 Forward to referring controller causes Property Mapping exception

Hi folks,

I have an issue where I receive an TYPO3\CMS\Extbase\Property\Exception\InvalidPropertyMappingConfigurationException. The problem arises when a <f:form> is sent to a controller which results in a validation error, and subsequentely is sent back to the referring controller, if that controller also has parameters from a <f:form></f:form>.

The problem is that the general TYPO3\CMS\Extbase\Mvc\Controller\ActionController->forwardToReferringRequest rebuilds the controller/action/parameters of the referrer, but NOT the __trustedProperties.
Thus the referring controller is called with its original <f:form> POSTed parameters, but with the trusted fields of the <f:form> parameters for the new (failing) controller.

I built my page based on Extcode/Cart, but the issue comes from the Typo3 Extbase Core and can come from all such situations.

Scenario:
- Page with <f:form> that POSTs data to some controller<br>- This page has another <f:form> with (similar) fields, posting to another page<br>- Validation error on second POST =&gt; forward to referring controller<br>- Property Mapper Exception because OLD form fields are checked agains NEW trusted fields</f:form></f:form>

A basic setup can be done with Extcode/Cart and Extcode/Cart-Products, and a slightly modified EXT:cart/Resources/Private/Templates/Cart/Cart/Show.html:

[...]
<f:comment> This is instead of original Cart/OrderForm partial </f:comment>
<f:form id="form-order-address" class="form"
        name="orderItem"
        object="{orderItem}"
        controller="Cart\Cart"
        action="show"
        arguments="{step: nextStep}"
        method="post">
    <f:render partial="Cart/OrderForm/Address/Billing" arguments="{cart:cart, billingAddress:billingAddress}"/>
    <f:form.submit value="Save Address"/>
</f:form>

<f:form id="form-order" class="form"
        name="orderItem"
        object="{orderItem}"
        controller="Cart\Order"
        action="create"
        method="post">
    <f:render partial="Cart/OrderForm/Cart" arguments="{_all}"/>
    <f:form.submit value="Order"/>
</f:form>

This renders 2 forms on the cart page, one for Address Editing, Second for Submitting.

When you enter an address and POST via “Save Address”, and directly after that click on “Order” without checking the required checkboxes, the error occurs

Author Philip Masser
Created 05/17/22, 12:33
Updated 05/17/22, 12:33
Story
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 12

#97528 Add check for references and safe way to delete files in FAL to public API

Status: In progress, I can split this up into individual patches.

——

Add public functionality to

  • check if there are references to a file / within a folder (see also FileList::makeRef, ExtendedFileUtility::func_delete and ExtendedFileUtility::folderHasFilesInUse)
  • return the references to a file
  • “safely” delete a file / folder (checking for references)

If possible, use this functionality instead of having duplicate code or move the functionality to the public API and then use the function there:

  • FileList::makeRef: count number of references
  • ExtendedFileUtility::func_delete: checking for references
  • ExtendedFileUtility::transformFileReferenceToRecordReference

Add phpdoc / documentation note pointing out that a check for references is not performed when deleting a file in

Add phpdoc / documentation note that this function only handles references within the sys_file_references table. TYPO3 – when performing functionality which concern references (including soft references) typically uses sys_refindex in combination with sys_file_references (which will also consider the soft references) – depending on where this functionality is used, we might want to check for both. In any case, it might make sense to point this out here:

A similar note in phpdoc does exist in LocalDriver::deleteFile:

> * This does not check if the file is
> * still used or if it is a bad idea to delete it for some other reason
> * this has to be taken care of in the upper layers (e.g. the Storage)!

——-

In TYPO3, there is functionality to delete files, but the function ExtendedFileUtility::func_delete() which does it safely by checking the references has the problem that it is “internal” and not public and also it sends flash messages (which might be a problem if called from CLI command).

The functionality which is public and usable does not check for references (as it is used as lowlevel functionality). AFAIK there is not public API which safely handles the deletion.

Also, there is no phpdoc that points out that it does not (except in the lower level driver functions).

AFAIK, there is no publicly available function which checks for references. The checking for references is done directly in the the code (e.g. in ExtendedFileUtility::func_delete.

So effectively, you have to handle this yourself – which might result in it being done incorrectly and adds lots of internal TYPO3 functionality to code, making it less maintainable. Also, it is a bit complicated to handle sys_refindex and sys_file_references, see also ExtendedFileUtility::func_delete – so that would be really helpful to have some public API functions.

Author Sybille Peters
Assigned to Sybille Peters
Created 05/02/22, 09:25
Updated 05/02/22, 09:25
Task
New Orphaned Form Framework TYPO3 CMS 12

#97519 Improve view of form settings

The settings view of a form in the form editor is quiet hidden in the right inspector section. The understanding for clicking the “setting”-button in the middle of the header and then getting content in the right corner of the page is a bit difficult.

*The idea*
By clicking the “setting”-button, the right inspector section will be resized to the whole width of the form editor and you get more space and more focus to your form settings without a stage and without a tree.

Author Andreas Steiger
Created 04/29/22, 12:39
Updated 04/29/22, 12:39
Task
New Orphaned Form Framework TYPO3 CMS 12

#97500 Improve Editor workflow when creating/editing a form

As an editor I want to create/edit a form quickly with auto focusing and auto scrolling to a new field/element which was created.

If the editor adds a new field to an existing form. The form is quite long (longer than one screen).

  1. The focus should go into the first inspector input field of an element (e.g. Textelement: Label). So the editor can start typing straight away without clicking.
  2. The view should be scrolled to the new selected field/element on the stage.
Author Andreas Steiger
Created 04/28/22, 09:47
Updated 04/28/22, 10:22
Feature
Author Björn Jacob
Created 01/17/20, 17:54
Updated 04/28/22, 07:18
Bug
New Orphaned Frontend TYPO3 CMS 7

#63821 HTTP header status 200 should be 304 when cached page not modified

When a cached page is requested, a “Last-Modified” header is sent with the response, based on the SYS_LASTCHANGED field of the page.
The server response always has a “HTTP/1.1 200 OK” status

There is no check if the browser request comes with a “If-Modified-Since” header. If so, It should be compared with SYS_LASTCHANGED. If the date of SYS_LASTCHANGED is earlier or equal than “If-Modified-Since”, it should return a “HTTP/1.1 304 Not Modified” status, instead of “HTTP/1.1 200 OK”.

A “HTTP/1.1 304 Not Modified” status does not have to send the content of the page, which reduces traffic.

Author Patrick Broens
Created 12/13/14, 10:16
Updated 04/20/22, 11:22
Bug
New Orphaned Backend User Interface TYPO3 CMS 10

#94116 drag inline images is flawed in TYPO3 v10

TYPO3 10 LTS 10.4.13
Backend
Task: sorting of images in content elements by drag & drop
result: sorting by drag & drop does work in the visible content but it is not possible to drag an element (image) outside the visible content.

Try following:
  • open content element “image”
  • load about 20-30 images in tab “image”

First problem: all image tabs are open. This is very inconvenient but i presume it is not a bug but a feature. I miss an possibility for opening oder closing all image tabs at once.

  • close all image tabs (20-30 clicks are necessary)
  • drag the first image to the bottom of the list.

This works. The page scrolls until the bottom of the image list.

  • drag the last image up to the top of the list.

This does NOT work. You can only drag until the top of the visible region, the page does not scroll. So you have to drag the image twice or even more often to push it to the top of the list.

Author Peter Linzenkirchner
Created 05/11/21, 19:26
Updated 04/16/22, 14:36
Feature
New Orphaned Extbase

#97323 Extbase queries should respect the pages.hidden field when respecting storage pages

Currently Extbase only has a table.pid IN (...) condition-style when respecting storage pages. But actually it should do a join on pages and also query on pages.hidden = 0. This would be consistent to other core behavior (if I disable a page in Backend then also it’s content is implicitly disabled). At least there should be a way to optionally enable this behaviour, if not being default.

Author S P
Created 04/07/22, 05:45
Updated 04/07/22, 05:47
Bug
New Orphaned Extbase TYPO3 CMS 10

#94349 Extbase n:m setOrderings() does not sort correct

I have courses and they have several start types and start dates.

starttype = 1 // date
starttype = 2 // on_request
starttype = 3 // continuously

So I sort the course by starttype and then by startdatetime. Now it results in an order which only use the first entry in starts and not the earliest. But if I use the query on database the ordering is as expected. It looks like there is some ‘magic’ between the query and the database. Is there a solution for my problem?

In my controller I have set the sorting as I found it in many examples

/**
 * Find all courses and sort them by start type and start date
 * @throws \TYPO3\CMS\Extbase\Persistence\Exception\InvalidQueryException
 */
public function findAllSorted() {
    $query = $this->createQuery();
    $query->setOrderings([
        'starts.starttype' => QueryInterface::ORDER_ASCENDING,
        'starts.startdatetime' => QueryInterface::ORDER_ASCENDING
    ]);
    $query->matching(
        $query->logicalOr([
            $query->greaterThan('starts.starttype',1),
            $query->greaterThan('starts.startdatetime', time())
        ]));

    // Debug query
    //$queryParser = $this->objectManager->get(\TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbQueryParser::class);
    //\TYPO3\CMS\Extbase\Utility\DebuggerUtility::var_dump($queryParser->convertQueryToDoctrineQueryBuilder($query)->getSQL());
    //\TYPO3\CMS\Extbase\Utility\DebuggerUtility::var_dump($queryParser->convertQueryToDoctrineQueryBuilder($query)->getParameters());

    return $query->execute();
}

This results in following query

SELECT `tx_vendorcontinuingeducation_domain_model_course`.*
FROM `tx_vendorcontinuingeducation_domain_model_course` `tx_vendorcontinuingeducation_domain_model_course`
LEFT JOIN `tx_vendorcontinuingeducation_domain_model_start` `tx_vendorcontinuingeducation_domain_model_start` ON `tx_vendorcontinuingeducation_domain_model_course`.`uid` = `tx_vendorcontinuingeducation_domain_model_start`.`parent`
WHERE ((`tx_vendorcontinuingeducation_domain_model_start`.`starttype` > :dcValue1)
       OR (`tx_vendorcontinuingeducation_domain_model_start`.`startdatetime` > :dcValue2))
  AND (`tx_vendorcontinuingeducation_domain_model_course`.`sys_language_uid` IN (0,
                                                                                 -1))
  AND (`tx_vendorcontinuingeducation_domain_model_course`.`t3ver_oid` = 0)
  AND ((`tx_vendorcontinuingeducation_domain_model_course`.`deleted` = 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`t3ver_state` <= 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`t3ver_wsid` = 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`t3ver_oid` = 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`hidden` = 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`starttime` <= 1619622660)
       AND ((`tx_vendorcontinuingeducation_domain_model_course`.`endtime` = 0)
            OR (`tx_vendorcontinuingeducation_domain_model_course`.`endtime` > 1619622660))
       AND (((`tx_vendorcontinuingeducation_domain_model_course`.`fe_group` = '')
             OR (`tx_vendorcontinuingeducation_domain_model_course`.`fe_group` IS NULL)
             OR (`tx_vendorcontinuingeducation_domain_model_course`.`fe_group` = '0')
             OR (FIND_IN_SET('0', `tx_vendorcontinuingeducation_domain_model_course`.`fe_group`))
             OR (FIND_IN_SET('-1', `tx_vendorcontinuingeducation_domain_model_course`.`fe_group`)))))
  AND (((`tx_vendorcontinuingeducation_domain_model_start`.`deleted` = 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`t3ver_state` <= 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`t3ver_wsid` = 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`t3ver_oid` = 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`hidden` = 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`starttime` <= 1619622660)
        AND ((`tx_vendorcontinuingeducation_domain_model_start`.`endtime` = 0)
             OR (`tx_vendorcontinuingeducation_domain_model_start`.`endtime` > 1619622660))
        AND (((`tx_vendorcontinuingeducation_domain_model_start`.`fe_group` = '')
              OR (`tx_vendorcontinuingeducation_domain_model_start`.`fe_group` IS NULL)
              OR (`tx_vendorcontinuingeducation_domain_model_start`.`fe_group` = '0')
              OR (FIND_IN_SET('0', `tx_vendorcontinuingeducation_domain_model_start`.`fe_group`))
              OR (FIND_IN_SET('-1', `tx_vendorcontinuingeducation_domain_model_start`.`fe_group`)))))
       OR (`tx_vendorcontinuingeducation_domain_model_start`.`uid` IS NULL))
ORDER BY `tx_vendorcontinuingeducation_domain_model_start`.`starttype` ASC,
         `tx_vendorcontinuingeducation_domain_model_start`.`startdatetime` ASC

and the values

array(2 items)
   dcValue1 => 1 (integer)
   dcValue2 => 1619622708 (integer)

Now I replace the dcValues and copy them to my phpMyAdmin

SELECT `tx_vendorcontinuingeducation_domain_model_course`.*
FROM `tx_vendorcontinuingeducation_domain_model_course` `tx_vendorcontinuingeducation_domain_model_course`
LEFT JOIN `tx_vendorcontinuingeducation_domain_model_start` `tx_vendorcontinuingeducation_domain_model_start` ON `tx_vendorcontinuingeducation_domain_model_course`.`uid` = `tx_vendorcontinuingeducation_domain_model_start`.`parent`
WHERE ((`tx_vendorcontinuingeducation_domain_model_start`.`starttype` > 1)
       OR (`tx_vendorcontinuingeducation_domain_model_start`.`startdatetime` > 1619619086))
  AND (`tx_vendorcontinuingeducation_domain_model_course`.`sys_language_uid` IN (0,
                                                                                 -1))
  AND (`tx_vendorcontinuingeducation_domain_model_course`.`t3ver_oid` = 0)
  AND ((`tx_vendorcontinuingeducation_domain_model_course`.`deleted` = 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`t3ver_state` <= 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`t3ver_wsid` = 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`t3ver_oid` = 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`hidden` = 0)
       AND (`tx_vendorcontinuingeducation_domain_model_course`.`starttime` <= 1619619060)
       AND ((`tx_vendorcontinuingeducation_domain_model_course`.`endtime` = 0)
            OR (`tx_vendorcontinuingeducation_domain_model_course`.`endtime` > 1619619060))
       AND (((`tx_vendorcontinuingeducation_domain_model_course`.`fe_group` = '')
             OR (`tx_vendorcontinuingeducation_domain_model_course`.`fe_group` IS NULL)
             OR (`tx_vendorcontinuingeducation_domain_model_course`.`fe_group` = '0')
             OR (FIND_IN_SET('0', `tx_vendorcontinuingeducation_domain_model_course`.`fe_group`))
             OR (FIND_IN_SET('-1', `tx_vendorcontinuingeducation_domain_model_course`.`fe_group`)))))
  AND (((`tx_vendorcontinuingeducation_domain_model_start`.`deleted` = 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`t3ver_state` <= 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`t3ver_wsid` = 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`t3ver_oid` = 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`hidden` = 0)
        AND (`tx_vendorcontinuingeducation_domain_model_start`.`starttime` <= 1619619060)
        AND ((`tx_vendorcontinuingeducation_domain_model_start`.`endtime` = 0)
             OR (`tx_vendorcontinuingeducation_domain_model_start`.`endtime` > 1619619060))
        AND (((`tx_vendorcontinuingeducation_domain_model_start`.`fe_group` = '')
              OR (`tx_vendorcontinuingeducation_domain_model_start`.`fe_group` IS NULL)
              OR (`tx_vendorcontinuingeducation_domain_model_start`.`fe_group` = '0')
              OR (FIND_IN_SET('0', `tx_vendorcontinuingeducation_domain_model_start`.`fe_group`))
              OR (FIND_IN_SET('-1', `tx_vendorcontinuingeducation_domain_model_start`.`fe_group`)))))
       OR (`tx_vendorcontinuingeducation_domain_model_start`.`uid` IS NULL))
ORDER BY `tx_vendorcontinuingeducation_domain_model_start`.`starttype` ASC,
         `tx_vendorcontinuingeducation_domain_model_start`.`startdatetime` ASC

The sorting in phpMyAdmin is correct. Something changes between repository and database.

Author Heinz Schilling
Created 06/15/21, 11:28
Updated 04/07/22, 05:29
Epic
Accepted Orphaned Security

#97289 Integrate security module

(to be filled with more content/topics)

  • move security related checks from reports module to new security module
  • add checks for existing security-related feature flags – and “enforce” secure settings
Author Oliver Hader
Assigned to Oliver Hader
Created 04/04/22, 08:52
Updated 04/06/22, 04:51
Feature
New Orphaned Extbase

#75404 Introduce generic _translationParent Property for AbstractDomainObject

At the moment you need to add a property that points to the translation parent uid manually if you want to be able to translate extbase entities.

If you could access a generic _translationParent Property like the _languageUid it would be possible to provide a working REST API for Extbase that works via Reflection only and covers most features of the FormEngine and Extbase. I allready developed such an API, it might be possible to include it in 8 LTS (with some help of course).

Author Philipp Wrann
Created 04/05/16, 09:18
Updated 04/04/22, 09:23
Feature
New Orphaned Backend User Interface

#97278 Add multiple selection of records in IRRE as well

Add the multiple selection used in the List Module also to the records in IRRE as well so as to allow faster bulk operations such as deleting a large number of IRRE elements.

Author Christian Toffolo
Created 03/31/22, 18:17
Updated 03/31/22, 18:17
Feature
New Orphaned Backend User Interface

#97102 Link existing references warning on record delete to record info

Link existing references warning on record delete to record info so editors can click and see these references.

Author Christian Toffolo
Created 03/04/22, 14:13
Updated 03/31/22, 15:23
Feature
Accepted Orphaned Backend User Interface

#97017 Allow LiveSearch to be disabled via configuration

On very large setups the global LiveSearch is often not useful, because the result set is so large that you need to do local page-tree searches anyways to find anything relevant. Also the performance on big databases is very bad.

It would be nice if one could deactivate the rendering of the LiveSearch bar.

It is possible by unset($GLOBALS['TYPO3_CONF_VARS']['BE']['toolbarItems'][1435433108]) by this feels rather as a hack and is globally/user-independt. Nice would be some UserTsConfig setting or similar.

Author S P
Created 02/24/22, 09:23
Updated 02/28/22, 09:56
Feature
Needs Feedback Orphaned

#96893 Option to define Translation behavior default value in TCA

Hi,

we have a multilanguage website and some contents only exist in a language that’s not the base language (having sys_language_uid > 0).

We have now the case, that the base language version of those contents (sys_language_uid = 0) might be created later and gets manually connected to the original content element via the Transl.Orig option.

The problem arises if we have relations in both content elements that have no l10n relationship. The relations are deleted in the content element having sys_language_uid > 0.

With the radio option: Translation behavior > “Custom value” instead of “Value of default language” this problem could easily be fixed, but I can see no TCA configuration option to define “Custom value” as a default. It always uses “Value of default language”, which then can be changed but at this point it is already to late to preserve my relations.

Therefore I would like to suggest to extend the TCA options by the feature, to define which default “Translation behavior” should get.

How to reproduce this problem:
In my example, this problem arises with news using content elements.
The base language is German (ID 0) and the 2nd language is English.
If my english news record contains content elements and is manually connected to a german news parent record having also content elements, my english content elements are set to deleted=1.
If Translation behavior > “Custom value” would be set, this error could be prevented.

Thanks for checking!

Author cosmoblonde GmbH
Created 02/14/22, 21:11
Updated 02/25/22, 09:38
Task
New Orphaned TYPO3 CMS 11

#97002 Simplify flexform behavior and stop saving old settings in flexforms (+ get rid of the then no more necessary flexform cli command + scheduler task)

When working with the forms framework I did come over some pretty nasty core behavior in the flexform context.

I did find parts in the flexforms like:

(...)
        <sheet index="ea4ca6637d2b7dbe41c867c14d43ef95">
            <language index="lDEF">
                <field index="settings.finishers.Redirect.pageUid">
                    <value index="vDEF">59</value>
                </field>
                <field index="settings.finishers.Redirect.additionalParameters">
                    <value index="vDEF"></value>
                </field>
            </language>
        </sheet>
        <sheet index="9cc4c6a803d8627cf0c4aca3161f4314">
            <language index="lDEF">
                <field index="settings.finishers.Redirect.pageUid">
                    <value index="vDEF">59</value>
                </field>
                <field index="settings.finishers.Redirect.additionalParameters">
                    <value index="vDEF"></value>
                </field>
            </language>
        </sheet>
(...)

So duplicated settings values just because the core flexform behavior doesn’t get rid of old settings when saving a flexform. (in this case the “persistenceIdentifier” changed)

I asked myself what is the purpose of saving old settings to the flexform fields? Why not only saving the current state? I don’t see a valid use case for keeping old settings values. (please switching plugins and restoring settings is NOT a use case)

In the end simplifying this would also make it possible to get rid of the “cleanup:flexforms” cli job. Which is just another maintenance task that should not be necessary.

Author Denis Mir
Created 02/23/22, 07:52
Updated 02/23/22, 07:52
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#87667 Replacements not applied for existing slug

Since #86740 one can define replacments for slug fields, e.g. to get rid of slashes.

However, these are not applied for existing or predefined slugs, e.g. when creating pages through the DataHandler.

All replacements must be applied upon sanitation, no matter the source of the slug.

Author Mathias Brodala
Created 02/06/19, 14:41
Updated 02/21/22, 07:46
Bug
New Orphaned TYPO3 CMS 11

#96963 404 handling with disabled language leads to preview in fallback language

How to reproduce:

- have a default and any other language created
- disable the second language for FE
- (not sure it is important, I have language mode strict for this page, no fallback)
- have error handling for 404 configured to show content from page
- have a 404 page (the one showing the content that should be displayed in 404 situations), in both default and translation
- preview any regular translated page (means, same BE Domain)
- provoke 404 situation by providing a non-valid URL for this language

Expectation: 404 content is visible for language you are in
Effect: 404 content in default / fallback language is displayed

When language gets enabled, expectation is met and content shows up translated just fine.

Author Anja Leichsenring
Created 02/18/22, 09:58
Updated 02/20/22, 22:35

Showing results 1401 to 1425 of 1561