Showing results 126 to 150 of 1561

Bug
Accepted Orphaned Localization TYPO3 CMS 10

#92809 Anchor Links in Link Wizard not translated correctly

I have a page A in the default language and a translated page B in ‘Free Mode’.
Page A has a Textmedia content element with an anker link to a content element on the same page.
The content element is selected via Link Wizard – it shows all records from page A.

But when I translate the Textmedia element to page B, the UID of the selected content element on page A doesn’t get updated.
Furthermore I don’t have the possibility to change the selection of the element, because the elements in the Link Wizard on page B are the ones from page A.

Shouldn’t see the editor for page B the content elements on page B in the Link Wizard?

Author Philipp Parzer
Created 11/10/20, 06:52
Updated 01/12/23, 12:41
Feature
New Orphaned Backend User Interface

#99419 Add a recycler module access icon in the header toolbar list

Hello,

We want the editors stop hidding useless contents instead of deleting them, and cluttering their own working area.

This improvement is splitted in smaller, and if possible, independant patches.

link to the full video (publically accessible): https://drive.google.com/file/d/1cxHaU7JHPiDE1_4hFsfDiM1m2YxfHoLz/view?usp=share_link

This tasks relates to the time 0.34min of the video

Rachel

Author Rachel Foucard
Created 12/23/22, 16:09
Updated 01/10/23, 16:12
Bug
New Orphaned Backend User Interface TYPO3 CMS 11

#99056 SingleSelect takes full width if select icons are used

Author Oliver Bartsch
Assigned to Oliver Bartsch
Created 11/10/22, 17:14
Updated 11/10/22, 17:14
Feature
New Orphaned Linkvalidator

#89426 Remove stale broken links in tx_linkvalidator_link

If a page (or content element, or …) is removed, the related broken links are not removed from tx_linkvalidator_link.

They are not displayed because only broken links of subpages of current page are displayed, so it is not a huge problem. But, eventually, this clutters up the tx_linkvalidator_link table.

Currently, there is no possibility to remove stale (no longer relevant) broken links except removing them manually from the db table.

Author Sybille Peters
Created 10/15/19, 19:35
Updated 11/03/22, 09:04
Feature
New Orphaned Install Tool

#88521 Incoherent settings interface: Presets don't show "non-final" warning while Site-Wide Configuration does

While the settings in “Configure Installation-Wide Options” show a warning if a change in LocalConfiguration will not be the final value

Note that $GLOBALS['TYPO3_CONF_VARS'] currently contains a different value. This could mean that the value is overwritten in AdditionalConfiguration.php. 

This is not the case under “Configuration Presets”.

Use case: you change e.g. the mail config from “Configuration Presets” -> Mail -> Custom while settings are set in AdditionalConfiguration.php. While used to getting the warning in “Configure Installation-Wide Options”, you won’t get a warning here.

Author Jonas Eberle
Created 06/07/19, 15:22
Updated 11/03/22, 09:04
Bug
New Orphaned Localization TYPO3 CMS 9

#88024 allowLanguageSynchronization doesn't synchronise cropping from images

I have an image in a TCA and want to reuse this image (and the cropping) in localised records. I configured the field (relevant snippet):

'image' => [
    'config' => \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig(
        'image',
        [
            ...
            'behaviour' => [
                'allowLanguageSynchronization' => true,
            ],
        ]
    ),
]

In backend now I have the possibility to switch between “Custom value”/“Value of default language” in the image field. I created a new record, added an image, cropped it. Now I localised the record, the image with cropping is copied over from the default language.

When I change the cropping of the default language record, the new cropping is not used for the localised record (“Value of default language” is set) in backend preview and frontend output.

When I now change the image in the default language record and apply a cropping, both are set in the localised record.

I encountered the same problem with l10n_mode=exclude: If the cropping is changed later it is not reflected in the localised record.

TYPO3 version 9.5.5

Author Chris Müller
Created 03/27/19, 16:26
Updated 11/03/22, 09:04
Bug
New Orphaned Localization TYPO3 CMS 8

#86231 Distinguish between free-mode localization and chained translation

Based on my note https://forge.typo3.org/issues/86141#note-5 when analyzing the behavior

TL;DR

When skimming over the examples below, focus and compare the values in l10n_parent and realize that l10n_source is optional.

Usage

Localizations can be created using the graphical backend interface (e.g. page module) or by invoking direct commands to DataHandler [1]. Thus even if the page module is only valid for tt_content records, it does not prevent records from being translated or localized explicitly. That’s why this analysis used element instead of tt_conent a pointer to a database table holding relevant records.

Terminology

Connected Mode

When translating elements, each element is bound to it’s relative ancestor. This results into a chain (that can be used for language fallbacks etc.).
The following example illustrates that, l10n_parent always points to the initial record in default language, l10n_source points to it’s relative translation ancestor – that’s the record a new translation is based on. All records are connected in a chain.

+ element:1 - English (Default)           - language:0, l10n_parent=0, l10n_source=0
+ element:2 - French Translation          - language:1, l10n_parent=1, l10n_source=1
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=1, l10n_source=2

Free Mode

When localizing elements in free-mode, the previously mentioned translation chain is broken up, thus “free-mode localizaion elements” are in a specific language, but are not related to any relative ancestor and thus are idependent. The following example uses element:3 as “free-mode localization”, l10n_parent is set to 0, but l10n_source still points to it’s relative localization ancestor (just as information, not as a strict relation in like a “composition” [2] would have been).

+ element:1 - English (Default)           - language:0, l10n_parent=0, l10n_source=0
+ element:2 - French Translation          - language:1, l10n_parent=1, l10n_source=1
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=0, l10n_source=2

The Challenge

Translation from existing localization

It is possible, to create a new localization directly, that does not have a record in default language – or as alternative start a translation based on a “free-mode localization element”.
The example shows, that the “English (Default)” record is now missing – the translation chain should(!) start with “French Translation” as first chain link. Since no record in default language s involved l10n_parent stay empty with 0, only l10n_source point to their according relative ancestor records.

+ element:2 - French Translation          - language:1, l10n_parent=0, l10n_source=1  # <- translation chain or free-mode localization?!
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=0, l10n_source=2  # <- translation chain or free-mode localization?!

When comparing the “Franco-Canadian Translation” here to the one shown in the “Free Mode” section, it cannot be distinguished anymore, whether the record is part of a “translation chain” or has been created as “free-mode localization”.

The information in l10n_source is not mandatory

Besides that, the information stored in the l10n_source field is optional and has to be configured in the control section of $TCA using the translationSource property. Thus, that information might not be available at all. The following examples show persisted results without having the l10n_source information.

Connected Mode without l10n_source

+ element:1 - English (Default)           - language:0, l10n_parent=0
+ element:2 - French Translation          - language:1, l10n_parent=1  # <- part of a translation chain, which one?!
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=1  # <- part of a translation chain, which one?!

It is not possible anymore to determine at all, whether a record is part of a translation chain – since the relative ancestor is missing.

Free Mode without l10n_source

+ element:1 - English (Default)           - language:0, l10n_parent=0
+ element:2 - French Translation          - language:1, l10n_parent=1  # <- part of a translation chain, which one?!
+ element:3 - Franco-Canadian Translation - language:2, l10n_parent=0  # <- translation chain or free-mode localization?!

It is (like in section “Translation from existing localization”) not possible to distinguish between “connected translations” and “free-mode localizations”.

References

[1]: DataHandler commands “localize” and “copyToLanguage”: https://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Typo3CoreEngine/Database/Index.html#command-keywords-and-values
2: Association, Aggregation, Composition in UML: https://www.visual-paradigm.com/guide/uml-unified-modeling-language/uml-aggregation-vs-composition/

Author Oliver Hader
Created 09/12/18, 08:51
Updated 11/03/22, 09:04
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 11

#98592 DataHandler: copy l10n-exclude fields even if excluded for current user

prose

cite: https://typo3.slack.com/archives/C025BQLFA/p1629827725005900

step by step

Pre-requisites: TYPO3 installation with at least one additional language. e.g. default + EN

Then u need:

  • backend user with no admin rights. I name it ‘editor’.
  • don’t give this user rights to see `is_siteroot`

Now:

  • with an admin account: create a new page, name it “Atemberaubende Weltkugel” (uid:1), make it a root-page (check `is_siteroot`)

Then:

  • log in as ‘editor’
  • visit page uid:1 in page module
  • click “translate page”
  • save page

what now happens

The translated page has `is_siteroot` set to `0` (it is the ext-tables.sql default value – see https://github.com/TYPO3/typo3/blob/v12.0.0/typo3/sysext/core/ext_tables.sql#L75).

what I expect

The translated page `is_siteroot` aligned with default-language. Because this reason: “‘l10n_mode’ => ‘exclude’” (https://github.com/TYPO3/typo3/blob/v12.0.0/typo3/sysext/core/Configuration/TCA/pages.php#L718)

Author Anonymous
Created 10/12/22, 16:14
Updated 10/12/22, 16:17
Task
New Orphaned Install Tool TYPO3 CMS 12

#98556 Improve the usability of the password field + the hide/show functionality for screenreader users

A few weeks back I’ve taken a look how a password field and in case available, the hide and show password option, is announced in screeenreaders across different CMS systems. one of the CMSes I have taken a look at back then was v11 of Typo3. I got reminded to that issue today when I tested the new TYPO3 v12 support in DDEV (*disclaimer: i am not a Typo3 user). The behavior is slightly different but the overall result more or less the same. For the context I have tested on MacOS 12.6 with VoiceOver in Safari. A few observations:
  • the announcement of the recommendations showing up when the first character is entered into the password field gets immediately stopped on the second keystroke. if you enter a password manually you usually add the first one or two characters fast, as soon as you know you are in the password field, that way the announcement gets cut off (see v11.mp4). problem if you leave the field and reenter that announcement isn’t made again. seems it is only announced when it shows up for the first time.
  • for sighted users the password strength is communicated by the change of color of the password field. screenreader users are completely missing out on that information.
  • the state change if the password is hidden or shown with the icon/button isn’t announced. one functionality which I considered convenient in Joomla was if you change the state of hide/show the focus shifted back to password field.
Author Ralf Koller
Created 10/08/22, 23:50
Updated 10/09/22, 10:25
Task
Under Review Orphaned composer / dependencies / third-party TYPO3 CMS 12

#98481 Hash package version into public resource paths

This applies to installations in TYPO3 composer mode using
typo3/cms-composer-installers v4 where TYPO3 extensions
are stored in vendor/ and their public resources as linked
to public/_assets/.

The symlink name in public/_assets/ should be extended to be not
just a hash of the relative path to the vendor folder, but also
acts as a cacheHash, by including the package version into the
symlink name.

That means an extension update of packages/extensions
will trigger a new symlink name.
This has the drawback that that names in public/_assets/ are
no longer predictable, but brings the benifit that this will allow
TYPO3 to skip modification-timstamp-lookups in
GeneralUtility::createVersionNumberedFilename() and to generate
performant JavaScript importmaps via trailing slashes1 syntax.

Author Benjamin Franzke
Assigned to Benjamin Franzke
Created 09/30/22, 12:43
Updated 09/30/22, 14: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
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
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
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
Feature
New Orphaned Site Handling, Site Sets & Routing

#84187 Add possibility to change links inside a recursive copy of a pagetree

For links to subpages of a tree it would be cool to define that those links will be treated relatively. Currently they still link to the original pid. But it would be nice to copy them “relative” to the newly copied pagetree.

Author Stefan Neufeind
Created 03/09/18, 17:22
Updated 01/26/22, 10:25
Bug
New Orphaned Form Framework TYPO3 CMS 11

#96435 Apply rate limiter to mail forms

In order to limit sending forms again and again (which can be automated e.g. by using Selenium or similar techniques), sending out a particular form should be rate-limited (available since TYPO3 v11).

Author Oliver Hader
Created 12/27/21, 18:09
Updated 12/27/21, 18:09
Feature
New Orphaned DataHandler aka TCEmain

#92874 RFC: When activating a record from outside the TCA view check for missing required fields

Say you create a new page in the page tree and don’t go into the edit mode but immediately activate it via the context menu. You then have an invalid page activated. In the worst case it breaks the frontend at some point.

In my opinion it would be neat to have this process being secured by a check for missing mandatory fields. Should there be it fails with a proper response.

This would apply for any kind of record. I am not sure to which category it belongs, so I stick to Miscellaneous.

Depending on how this is implemented one could create a Widget which lists invalid record throughout the TYPO3 instance as well. For example when you import pages during a relaunch which had a different format.

Author Alex Nostadt
Created 11/19/20, 10:20
Updated 12/17/21, 14:33
Feature
Under Review Orphaned Content Rendering

#93450 ContentObjectRenderer: allow TypoScript select object without any constraint of uidInList or pidInList

Current state

A TypoScript select object must have at least one constraint of uid or pid – configured via properties uidInList and pidInList

Feature proposal

Allow to completely disable the pid_uid constraint on purpose in ContentObjectRenderer.

10 = CONTENT
10 {
   table =
   select {
      uidInList = 0
      pidInList = 0
   }
}

Motivation

Get records from a m:n-relation where you already know the uids of one side.
Tables respresenting m:n-relations do not have a field named uid – instead they have uid_local and uid_foreign.

As a current work-around you must pre-fill pidInList with all pids of the entire database to make this work:

pidInList.data = leveluid : 0
recursive = 99

Example code taken from tt_content.menu_categorized_content

tt_content.menu_categorized_content =< lib.contentElement
tt_content.menu_categorized_content {
    templateName = MenuCategorizedContent
    dataProcessing {
        10 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
        10 {
            table = tt_content
            selectFields = tt_content.*
            groupBy = uid
            pidInList.data = leveluid : 0
            recursive = 99
            join.data = field:selected_categories
            join.wrap = sys_category_record_mm ON uid = sys_category_record_mm.uid_foreign AND sys_category_record_mm.uid_local IN(|)
            where.data = field:category_field
            where.wrap = tablenames='tt_content' and fieldname='|'
            orderBy = tt_content.sorting
            as = content
        }
    }
}

Code base

TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer – L6078-L6081

        // If not uid and not pid then uid is set to 0 - which results in nothing!!
        if (!$pid_uid_flag) {
            $constraints[] = $expressionBuilder->eq($table . '.uid', 0);
        }
Author Ayke Halder
Created 02/05/21, 18:30
Updated 11/29/21, 13:15
Feature
New Orphaned Backend User Interface

#90825 link to an explicit language of a page - usability issue

This is a kind of follow-up of ticket #22113

It is currently possible (TYPO3 9.5.14 and 10.4.0-dev) to link to an explicit language version of a page with the following procedure:

Prerequisites

1) At least an additional language (e.g. with ID=1) and some translated pages
2) If you want to use the RTE, enable the “additional parameter selector” with the TSConfig

RTE.default.buttons.link.queryParametersSelector.enabled = 1

Procedure

1) Open the “link wizard” on the [header_link] field or using the RTE
2) On the “additional parameter selector” write “&L=1“
3) Select the appropriate target page

This works,but it has some usability flaws:

1) on the select link wizard you have to write &L=1 (for example) inside the “Additional link parameters” field so the editor must know what parameter is needed and its syntax
2) on the select link wizard, you must write &L=1 inside the “Additional link parameters” field before choosing the page, or the wizard popup will close and the procedure must be repeated.
3) If you click on some other page on the tree in the wizard window, the parameter field will become empty
4) the editor must know beforehand that the target page is translated

I set this issue as “feature”, feel free to change it if needed.

Author Riccardo De Contardi
Created 03/24/20, 21:44
Updated 11/25/21, 10:37
Bug
New Orphaned TYPO3 CMS 10

#96000 Match behaviour of folderTree.altElementBrowserMountPoints to pageTree

So I’ve run into the case that a user with access to a restricted pagetree wants to link to a page outside of his area.
I happily discovered that the option
@options.pageTree.altElementBrowserMountPoints@
lets me replace the defined dbmount with whatever I want.

If I don’t want to replace my defined dbmounts but instead want to append some, I can enable the following option
@options.pageTree.altElementBrowserMountPoints.append@

Both of this is great!

I then checked if the same exists for the foldertree (if someone wants to link to a file outside of his assigned file folder).

The option
@options.folderTree.altElementBrowserMountPoints@
exists! Great!
However, unlike the pageTree version, this one only appends filemounts, it doesn’t replace them.
The append option doesn’t exist (I tried to set options.folderTree.altElementBrowserMountPoints.append = 0)

What is the reasoning for this different behaviour?
I feel like the default behaviour for folderTree.altElementBrowserMountPoints should be “replace” and “folderTree.altElementBrowserMountPoints.append” should be added for those who want it.

Author Marco H
Created 11/16/21, 17:17
Updated 11/16/21, 17:17
Feature
Under Review Fresh Backend API

#111328 Decide page permissions with a security voter

The page permissions of backend users are decided by BackendUserAuthentication only: the SQL clause of getPagePermsClause(), the webmount check of isInWebMount() and the permission bitmask of calcPerms(). Voters of the authorization checker (#111235) cannot use them without the user object, and new APIs such as a record read check have to pass the user object around.

Proposal

  • An internal PagePermissionEvaluator decides page permissions for a context of the user, its groups and the mounts of the request. The three methods of BackendUserAuthentication delegate to it.
  • A PageVoter decides on Page objects for reading, updating, deleting, creating subpages and a new scope for changing the content of a page.
  • Webmounts and the workspace are no part of the principal. The backend stores them, together with the file mounts and storages (resolved on first access only), as mount context on the security token of the request.
  • The hooks getPagePermsClause and calcPerms are deprecated in favour of two PSR-14 events:
    • ModifyPagePermissionClauseEvent: listeners build constraints with an expression builder instead of SQL strings
    • ModifyPagePermissionsEvent: listeners grant or revoke permissions on a single page

The events apply to the voter and to the methods of BackendUserAuthentication alike, so that extensions such as access control lists keep working with both.

Author Benni Mack
Created 11/03/26, 11:30
Updated 11/18/26, 19:16
Bug
Under Review Fresh Backend User Interface TYPO3 CMS 13

#108187 Live Search opens edit record in filelist content frame

Actual behaviour

  1. open filelist modul
  2. open live search (e.g. with cmd+k)
  3. search for a db-record and click on edit
  4. the edit form get’s displayed within the content frame of the actual be module filelist which feels wrong having the file storages on the left side.
Author Josef Glatz
Created 11/19/25, 10:01
Updated 11/18/26, 17:52

Showing results 126 to 150 of 1561