Showing results 1126 to 1150 of 1561

Feature
Accepted Orphaned Backend User Interface

#95369 improve readability of "New Record Selector”

When selecting a new record, it would be nice if the tables would be shown in columns in the backend.
Something like the following:

Maybe even in three columns on wide screens.
At the moment we have a pretty large unused space given that the item names are reasonably short.
The positioning of the tables in columns should be responsive of course (they should stack on smaller screens).

Author Michael Schams
Created 09/27/21, 11:26
Updated 04/01/25, 13:20
Feature
New Orphaned File Abstraction Layer (FAL)

#20558 Mass file uploader: Uploading directories

Many users want to upload a lot of files in a given directory structure. The mass file upload should support uploading whole directory structures just like ameos_dragndropupload. The drag&drop possibility there is also a very user-friendly feature.

(issue imported from #M11256)

Author Thomas Schröder
Assigned to Christian Eßl
Created 06/03/09, 12:31
Updated 04/01/25, 13:20
Bug
Accepted Orphaned File Abstraction Layer (FAL) TYPO3 CMS 6.2

#64363 Copy files in Filelist backend

TYPO3 version 6.2.9

When I copy a (html) file in the backend Filelist and insert the file in the same folder the following message appears: … file already exists in folder … So I must paste the file first into another folder, rename it and cut and paste it back to the desired folder.

In older versions you can copy and paste files directly because the new file was named: [filename]-copy-1.html

Author Anonymous
Created 01/19/15, 18:54
Updated 04/01/25, 13:19
Feature
New Orphaned Backend User Interface

#93512 Display Page in BE as Page or List

It would make sense if you could set how the page is displayed in the backend in the page properties. Whether as a page or a list. A folder could always be displayed as a list in order to display news there. Newbies do not have to switch between pages and lists layout. This is criticized in many forums and product comparisons on TYPO3 and would be easy to fix.
So you could possibly insert a “News Articles” button in a tx_news content element in the BE to display all news in a list in the assigned folder. This applies to blogs, calendars and much more.

Author Christian Leicht
Created 02/14/21, 21:52
Updated 04/01/25, 13:18
Feature
New Orphaned Backend User Interface

#71429 Limit selection of content elements to allowed languages

I have a page with 4 languages. For each language I created a be user limited to only one language. If this user wants to create a link to a content element thru a link wizard, a link with all content elements in all languages is shown. It would be great, if this list would be limited to the allowed language. Additionaly it would be helpful to show the content element uid in this list. Like it is possible to show the page uid in page tree.

Author Natalia Postnikova
Created 11/09/15, 09:58
Updated 04/01/25, 13:14
Feature
New Orphaned Backend User Interface

#70200 IRRE / Inline: foreign_selector should support suggest wizard.

The inline foreign_selector should support suggest wizard to find and add records.

Author Andreas Allacher
Created 09/30/15, 08:13
Updated 04/01/25, 13:14
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#106150 Improve contrast in backend dark mode for Better Usability

The dark mode in the backend appears confusing.

While the exact cause is unclear, it seems to be due to insufficient contrast between various interface elements.

Increasing the contrast by approximately 10% could significantly improve readability and overall usability.

Author Christian Toffolo
Created 02/11/25, 09:01
Updated 04/01/25, 13:10
Task
Accepted Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 12

#99655 Backend: Set correct Site in site attribute of request when the current request has sufficient contextual information

With the introduction of the site-config we added more and more multisite-specific features, that are configured in the site-config.

This works perfectly for the frontend. But when you rely on the site-config in the backend, you will need to add a middleware, that sets an internal site attribute for various backend routes. Otherwise you will often just have a NullSite, which is useless.

An example would be: You implement an api and each site has its own credentials because the site should only have access to a subset of data. So you configure the credentials in the site-config. But if you need to add some backend-features, that needs those credentials, you will often need to determine the rootpage by grabbing some id from the current queryParams and then retrieving the site-config from the rootpage id.

In my opinnion the site-config should be available whenever possible.

for example – it is possible to determine the site and set it as attribute when:

- you edit the site config itself
- you edit any tca record located inside the page-tree
- on any view you have relation to a page uid

At the moment i need to add a middleware for each extension, that makes extensive use of the site configuration.

Unfortunately i did not test the behaviour in V11, so i need to tag the typo3 version to 10. Once i can confirm this still exists in V11/V12, i can update this issue.

Update

This is still valid for V11/V12.

Author Philipp Wrann
Assigned to Benni Mack
Created 01/20/23, 09:42
Updated 03/31/25, 15:42
Feature
New Orphaned Frontend

#106436 Allow additional video/audio/text/application formats for FileType ENUM

Some MIME types are marked like “application/dash+xml” and “application/vnd.apple.mpegurl” and allow videostreaming formats.

This cannot properly be evaluated by the TYPO3 Core because it currently “listens” only for “video/” MIME types to show a video palette in the Backend. For the frontend, only very specific “video/…” formats evaluated by the MediaViewHelper / VideoTagRenderer will be returned.

By using:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['fileExtensionToMimeType']['mpd'] = 'video/mp4';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['fileExtensionToMimeType']['hls'] = 'video/mp4';

you can actually remap mime types to get the party started in the backend, and then files uploaded with this filename will receive a ‘video/mp4’ sys_file.mimetype entry.

This falls apart for the MediaViewHelper/VideoTagRenderer though, because it would then receive ‘video/mp4’ and use that for <source type="video/mp4"> frontend output.

A middleware could do string replacements later on, or with custom ViewHelpers and Partials, integrators could solve this.

But there should be a possiblity for the TYPO3 core to make this easier for integrators.

I suggest we create a new settings.php directive like:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['additionalFileTypeMapping']['text'] = '';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['additionalFileTypeMapping']['image'] = '';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['additionalFileTypeMapping']['audio'] = '';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['additionalFileTypeMapping']['video'] = 'mpd,hls';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['additionalFileTypeMapping']['application'] = '';

Then, instead of fake-mapping a MIME-Type, this could happen:

  • A new TYPO3\CMS\Core\Resource\FileType::tryFromMimeTypeAndFilename() needs to be created, to also contain the file NAME (not only mime type).
  • This new method needs to be used instead of current places in the code for tryFromMimeType where needed (for now, mainly in AbstractFile).
  • TYPO3\CMS\Core\Resource\FileType::tryFromMimeTypeAndFilename() evaluates this config option and not only matches to the base MIME type, but also inspects the filename to report the proper FileType ENUM
  • The f:media VH and the AudioTagRender / VideoTagRenderer / AudioTagRenderer would need to be changed to no longer do MIME type (via property $possibleMimeTypes) detection, but instead utilize the FileType ENUM too (maybe on top of a custom MIME type list?)

Configuring the $GLOBALS['TYPO3_CONF_VARS']['SYS']['FileInfo']['additionalFileTypeMapping'] arrays is currently not possible in the TYPO3 Core Settings GUI, so it would need to be file-based. In the future, managing these arrays within the GUI is covered by other feature requests. ;)

Author Garvin Hicking
Created 03/26/25, 10:19
Updated 03/26/25, 10:19
Bug
Accepted Orphaned Form Framework TYPO3 CMS 12

#104118 Avoid hard dependency on final validation viewhelper

I inherited a project that xclassed the NotEmptyViewHelper and am currently updating it to v12.4
Previously, the ViewHelper was extended, but since they are final now this can’t be done anymore.
Thus i copied the code over, made the adjustments —> done, or so i thought…

Now when i tried to add a new form with EXT:form, i could not get the required sign to show up. After quite some debugging i found that there are hard dependencies with instanceof checks in place
https://github.com/search?q=repo%3ATYPO3%2Ftypo3+%22instanceof+NotEmpty%22&type=code

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/extbase/Classes/Validation/Validator/NotEmptyValidator.php

IMHO this implementation needs to be changed, we can not have any hardcoded checks that way without being able to switch out the code. I know that the final declaration is unlikely to change, thus the NotEmptyValidator should probably have an interface or tag to indicate it is a required validator.

Author Andreas Kießling
Created 06/15/24, 19:33
Updated 03/26/25, 09:21
Bug
Under Review Orphaned Extbase TYPO3 CMS 11

#93576 Typo3DbBackend::getObjectCountByQuery does not work correctly with custom doctrine queries

When you build custom queries in extbase repositories, the method Typo3DbBackend::getObjectCountByQuery does not work correctly any more.
In my example, we have geo data in the database and we calculate a rough distance to a given point with an extbase repository query using doctrine. This looks something like:

$queryBuilder
    ->join(
        'foobar',
        ZipCode::TABLE_NAME,
        'zip',
        'zip.uid = foobar.zip_code'
    )
    ->addSelectLiteral('(' . self::EARTH_RADIUS . ' * acos(cos(radians( ' . $regionalObject->getLat() . ' )) * cos(radians( zip.lat )' .
        ') * cos(radians( zip.lng ) - radians( ' . $regionalObject->getLng() . ' )) + sin(radians( ' . $regionalObject->getLat() .
        ' )) * sin(radians( zip.lat )))) AS distance')
    ->andHaving(
        $queryBuilder->expr()->lte('distance', $filterDemand->getMaxDistance())
    );
$filterDemand->setSortBy('distance');
$filterDemand->setSortDir('ASC');

Now this works as expected for normal queries and output in extbase/fluid. But as soon as we use the fluid count viewhelper or the pagination widget , the getObjectCountByQuery method gets called and this error happens:

#1472074379: Unknown column ‘distance’ in ‘having clause’

The reason is the mentioned method just throws away all the defined select parts of the query and replaces them with a single
@$queryBuilder->count(‘*’);@ which is not expected. The count is expected to happen on the query result of the original query, so the code should do something like this instead:

$fullSql = $queryBuilder->getSQL();
$queryBuilder
    ->resetQueryParts()
    ->selectLiteral('count(*)')
    ->getConcreteQueryBuilder()->from("({$fullSql})", 'temporary')
;

This is how the doctrine ORM does the paging as well (subquery) instead of fumbling around in the original query. The code is the same from TYPO3 versions 8 to 11.

Author Michael Grundkötter
Created 02/24/21, 07:50
Updated 03/25/25, 21:40
Bug
New Orphaned Pagetree TYPO3 CMS 9

#91305 Wrong mount points cause empty page tree, exceptions (multiple errors in the code)

Before TYPO3 9.5 pages table only contained records for the default language. Since TYPO3 9.5 they also contain records in other languages. Unfortunately be_groups TCA definition was not updated to allow only records in the default language. This causes the following problem: if the user mistakenly adds a db mount for the page in non-default language, this page becomes inaccessible to the non-admin user and the whole page tree is not displayed with the exception.

Same problem is for be_users table with db mounts.

The exception itself is cryptic:

Core: Exception handler (WEB): Uncaught TYPO3 Exception:
 trim() expects parameter 1 to be string, null given | TypeError thrown in file
/home/prod/web/typo3/sysext/backend/Classes/Controller/Page/TreeController.php in line 267

This happens inside the function named pagesToFlatArray because it gets an empty array in $page parameter. The cause of this problem is inside getAllEntryPointPageTrees which has the following check:

            $entryPoint = $repository->getTree($entryPoint, function ($page) use ($backendUser) {
                // check each page if the user has permission to access it
                return $backendUser->doesUserHaveAccess($page, Permission::PAGE_SHOW);
            });
            if (!is_array($entryPoint)) {
                unset($entryPoints[$k]);
            }

The problem here that it will be always an array but it can be empty array. So the check should not be is_array($entry) but empty($entry). When changed to empty($entry) page tree is displayed. However the problem with be_groups TCA should still be fixed!

I see another possible problem in function named fetchDataAction, code:

        if (!empty($request->getQueryParams()['pid'])) {
            $entryPoints = [(int)$request->getQueryParams()['pid']];
        } else {
            $entryPoints = $this->getAllEntryPointPageTrees();
        }

If the condition is true, $entryPoints will not be in the correct format for pagesToFlatArray, which expects a full page record. This will also cause exceptions.

To reproduce the issue

  1. Have more than one language
  2. Have a non-admin user
  3. in the backend group for the user select a translation for the web mount instead of a default language page
  4. Login with that user and go to the Page module
Author Dmitry Dulepov
Created 05/05/20, 11:37
Updated 03/23/25, 22:32
Bug
Needs Feedback Orphaned Extbase + l10n TYPO3 CMS 11

#69022 Translated records can't be found when the original is hidden

If you deactivate a record and try to get the translated one you will get a: “#1297759968: Exception while property mapping at property path “”:Object with identity “123” not found.”

This happens because extbase always works with the uid’s of the original records and does the language overlay at last.
So if the original is hidden it can’t be found and so either you can’t get the translated overlay.

I guess best would be to expect translated items will be deactivated too if I deactivate the original one, otherwise you have to create a single record in the target language.

Checking everytime if a record is translated would be a mess for this edge case…

Author Daniel Dorndorf
Created 08/13/15, 15:55
Updated 03/23/25, 17:40
Bug
New Orphaned Frontend TYPO3 CMS 12

#59225 Disabled Pages from Type Mount Point are still visible in Frontend

System TYPO3 4.7.17

Scenario: Adding a Page of type “Mount Point” with a page from tree 1 in tree 2.

I want to have a new menu item “test” in my second tree.
Related page “News” should be shown. That works fine.

But even if I disable the Mount Point – it’s possible to open the link
in frontend. I have to delete the mount point to disable the functionality.

Author Alex Kellner
Assigned to Mathias Schreiber
Created 05/30/14, 10:58
Updated 03/23/25, 13:33
Bug
Accepted Orphaned Backend User Interface TYPO3 CMS 10

#95010 eval required broken for selectMultipleSideBySide

I got a selectMultipleSideBySide field which provides a selection of locations.
This field is required via `‘eval’ => ‘required’`

There seems to be an issue that got introduce within the last ~4 versions of v10.4 i guess.
Even if something is selected, the field is marked as required. (see Screenshot)

The workaround for the Moment:
  • you can add and remove (or the other way round) an item to get rid of the
  • switch to `‘minitems’ => 1`

My config for testing:

'locations' => [
            'exclude' => 1,
            'label' => 'Standorte',
            'config' => [
                'type' => 'select',
                'renderType' => 'selectMultipleSideBySide',
                'eval' => 'required',
                'items' => [
                    ['Nürnberg 90439', 'Nürnberg 90439'],
                    ['Fürth 90762', 'Fürth 90762'],
                    ['Bamberg 96052', 'Bamberg 96052'],
                    ['Erlangen 91056',  'Erlangen 91056'],
                    ['Regensburg 93047', 'Regensburg 93047'],
                ],
            ],
        ],
Author Henrik Elsner
Assigned to Andreas Kienast
Created 08/27/21, 06:45
Updated 03/21/25, 21:41
Feature
Under Review Orphaned Security

#106380 Switch backend maintainer re-auth (sudo-mode) from password to MFA if available

As a backend administrator with maintainer rights one currently logs in to the backend like any editor and on accessing maintainer modules one is asked to re-auth with the password (in PRODUCTION context, IIRC in DEV context this is skipped).

I think under the condition that the user has MFA enabled, instead of asking for the password, an MFA-auth should be done.
The basic principles used here are:
  • re-auth makes sense to escalate privileges, e.g. avoid scenarios with unlocked and unattended devices, session hijacking and device not locked but accessible by others, session hijacked or simply unintended mishaps
  • passwords are not safe as static secrets. Thus, additional MFA (e.g. TOTP, WebAuthn based hardware tokens) are added because they have better protection (e.g. access to a physical device or being only valid for a small time).
  • stealing a session is as easy, stealing a password is easy. stealing an addtional MFA-factor is hard.

In conclusion the re-auth to escalate to the maintainer modules should probably also use MFA (if available), instead of the password, as re-authing a session with a password seems weaker than re-authing it with an MFA.

This here does not consider 3rd party extensions supplying authentication providers in general, just the MFA providers to make it simpler.

Author J. Peter M. Schuler
Created 03/18/25, 10:27
Updated 03/19/25, 12:36
Bug
Under Review Orphaned Extbase TYPO3 CMS 6.2

#66447 Annotation @cascade remove does not delete hidden child data

You have a domain model (for example a blog entry) and this domain model has an object storage of other domain models (for example comments). Both models have no deleted flag and will be removed right away from the database. The object storage has the annotation @cascade remove. If you remove a blog entry, only comments, that are not hidden, will be removed too. Hidden comments will stay in the database as orphans. That can’t be right…

Author B. Kausch
Created 04/16/15, 11:11
Updated 03/11/25, 10:32
Bug
New Orphaned Backend API TYPO3 CMS 12

#106101 allow a null value for the getSession method

Under some circumstances the session member variable of FrontendUserAuthentication is null.

abstract class AbstractUserAuthentication implements LoggerAwareInterface
{
…
protected ?UserSession $userSession = null;
…
public function getSession(): UserSession {
return $this->userSession;
}
}

The method getSession should return the null value if userSession is null and not cause a PHP TypeError.

TypeError TYPO3\CMS\Core\Authentication\AbstractUserAuthentication::getSession(): Return value must be of type TYPO3\CMS\Core\Session\UserSession, null returned

Solution:

public function getSession(): ?UserSession
Author Franz Holzinger
Created 02/06/25, 16:06
Updated 03/07/25, 12:08
Task
Accepted Orphaned Backend API TYPO3 CMS 12

#103071 Trying to render backend/fluid T3-Link, but LinkHandler concept is kind of weird as there is no real parser for t3links into table/uid parts

I came to the conclusion that LinkHandler concept looks kind of weird.

I basically wanted to code my own Content-Element Backend Preview and came across the problem that I wanted to display a t3link as Linked Record with icon (edit-link to the backend record for given uid). I know this basically sounds crude, but obviously this is not really comfortable possible.

Initially I thought there is something like this BE/Fluid ViewHelper:
@<be:uri uid="42" table="a_table" returnurl="foo/bar"></be:uri>@

But it can’t handle t3-links on it’s own.

Okay let’s try to split the t3link, say it’s:
t3://page?uid=24

We have type page and uid 24. Ok sounds simple, but wait … page is the link-type, NOT the table-name. Of course we could simply trick here and replace it hard-coded, but it’s weird that not even TYPO3-Core has some kind of generic Class which will resolve this.

Any other utility-classes like LinkService, TypoLinkCodedService, TypolinkSoftReferenceParser and many more I discovered for a real “resolver” won’t work or also require a table-name.

TypolinkSoftReferenceParser::getTypoLinkParts method comes very clearly to what I’ve been searching, but even there table-name is required and there’s nowhere a mapping between table-name to link/record identifier like ‘page’ is table ‘pages’.

I think this should’t be hard-coded and always up to developers tricking around with such things and even TYPO3 core seems to poke around this basic problem, instead of providing a LinkHandlerMapper or some type of class we can use to manage/register linkhandlers to/from record table-name or link-identifier to the opposite.

The dirty mapping-logic done in TypolinkSoftReferenceParser::getTypoLinkParts should be refactored to it’s own class and in such a way that we don’t have to clue what table-name a t3link is ment for. Why is there the link-type ‘page’ if nowhere we use this to map it to pages table?

There are many core-classes which aim to provide anything for link-handling and we have link-handling configuration.

And additionally if we have t3links in our TYPO3-World it would be awesome to have a simple BE/Core ViewHelper which allows to render a record-link with icon just like be:uri.editRecord, but with argument for t3link, say it could be named be:typolink.editRecord.

It there’s anything I didn’t find please let me know. If my current view is really the fact, we should clean-up and refactor some things to make the linkhandler-feature better and better useable for developers for such a case I now had.

Author Gabriel Kaufmann TYPOworx GmbH | NewMedia
Created 02/07/24, 10:58
Updated 03/06/25, 21:59
Task
Author Jasmina Ließmann
Created 01/18/23, 11:09
Updated 03/04/25, 17:10
Bug
Accepted Orphaned Workspaces TYPO3 CMS 13

#106249 Related data records cannot be deleted in workspaces under certain circumstances

Description

Under certain circumstances, related data cannot be deleted when you are in a workspace.
For example, if you have a page with a resource inserted in its properties (e.g. an image). If you now switch to a workspace and open the properties of this page and then save the page properties, a new workspace record is created for this page. If you now delete the resource and then save the page properties, the resource reappears in the corresponding tab again, although it should have been removed.

How to reproduce?

1. insert a resource in the properties of a page in the live workspace
2. switch to a workspace
3. go to the page properties of 1. and press Save
4. delete the data record of the resource
5. save
6. -> deleted resource record is displayed again
You can repeat the process between 3. and 6. as often as you like.

Preliminary error analysis

Instead of the Delete method, the Discard method is called in the DataHandler.

Thanks for the great work on TYPO3 and all the effort

Author George Miller
Created 02/25/25, 12:48
Updated 02/25/25, 19:55
Bug
New Orphaned Database API (Doctrine DBAL) TYPO3 CMS 13

#86151 DatabaseQueryProcessor find_in_set in orderBy Clause fails

Code from current 7.6 project – verified to work properly

# Add content element teaser
tt_content {
    menu =< lib.fluidContent
    menu {
        templateName = Teaser.html
        dataProcessing {
            10 = TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor
            10 {
                if.isTrue.field = pages
                table = pages
                uidInList.field = pages
                pidInList = 0
                as = pageUids
                orderBy {
                    dataWrap = find_in_set(uid,'|')
                    field = pages
                }

                dataProcessing {
                    10 = TYPO3\CMS\Frontend\DataProcessing\FilesProcessor
                    10 {
                        references.fieldName = media
                        as = files
                    }
                }
            }
            20 < .10
            20 {
                if.isTrue.field = selected_categories
                fieldName = selected_categories
                as = categoryUids
            }
        }
        stdWrap {
            # Setup the edit icon for content element "menu"
            editIcons = tt_content: header [header_layout], menu_type, pages
            editIcons {
                iconTitle.data = LLL:EXT:fluid_styled_content/Resources/Private/Language/FrontendEditing.xlf:editIcon.menu
            }
        }
    }
}

The code utilizes find_in_set to ensure, that the order of the values in the select field is honored for the menu entries.

The problem lays in

\TYPO3\CMS\Frontend\DataProcessing\DatabaseQueryProcessor::process -> L 93
\TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::getRecords -> L 7075
\TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::exec_getQuery -> L 7056
\TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::getQuery -> L 7224
\TYPO3\CMS\Core\Database\Query\QueryBuilder::addOrderBy --> L 811
$this->concreteQueryBuilder->addOrderBy($this->connection->quoteIdentifier($fieldName), $order);
                                           ^-- add escaping sequence, which breaks the query for that special case

I would expect the find_in_set function to work properly.

We have 3 working workarounds, which are both not optimal:

  • remove ordering or order via title
  • use a second php based Dataprocessor to get the ordering right
  • use native queries and bypass doctrine querybuilder

I consider that as a bug, as it breaks functionality which was there for a very long time.
On the other hand escaping the values in the querybuilder might avoid certain security vectors.

I’m excited to get your feedback.

Author Kay Strobach
Created 09/05/18, 11:43
Updated 02/25/25, 06:15
Bug
New Orphaned SEO TYPO3 CMS 12

#106168 Not possible to set "robots" and "canonical_link" from uncached plugins

Currently it is not possible to manually set “robots” or “canonical_link” from uncached (extbase) plugins. The following does not work (when uncached):

$GLOBALS[‘TSFE’]->page[‘canonical_link’] = ‘Lorem ipsum dolor sit amet’
$GLOBALS[‘TSFE’]->page[‘robots’] = true;
$GLOBALS[‘TSFE’]->page[‘no_follow’] = true;
$GLOBALS[‘TSFE’]->page[‘no_index’] = true;

Also, when using the meta tag api it is not possible to set “robots” from an uncached scope (it just works for cached plugins):

$metaTagRegistry->getManagerForProperty(‘robots’)->addProperty(‘robots’, ‘noindex,nofollow);

So the only option to set “canonical_link” from an uncached scope is using the “ModifyUrlForCanonicalTagEvent” event, which is fine itself. But regarding the “robots”, the only solution seems to set it using typoscript (page.meta.robots = noindex,nofollow).

The core should be extended in the following way:

1. Add possibility to modify the “robots” tag using the meta tag api even when in uncached scope
2. Add possibility to modify the “canonical” directly ($GLOBALS[‘TSFE’]->page[‘canonical_link’], or anything else) even when in uncached scope

Author Jan Kornblum
Created 02/13/25, 11:07
Updated 02/18/25, 22:02
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 13

#106197 Use native browser resizing for viewpage module

Use browser native resize support via `resize: both` instead
of the JavaScript based
resizable actions from `interactjs` which is a framework
of its own (current 128K in size).

Author Benjamin Franzke
Created 02/18/25, 12:21
Updated 02/18/25, 12:23
Bug
New Orphaned Backend API TYPO3 CMS 12

#106175 itemsProcFunc does nothing with type=selectTree

https://docs.typo3.org/m/typo3/reference-tca/12.4/en-us/ColumnsConfig/Type/Select/Tree/Index.html#confval-select-tree-itemsprocfunc

The documentation mentions the usage of itemsProcFunc in combination with the selectTree-type. This option however does nothing. If I change the type from selectTree to selectMultipleSideBySide, my class is being used and I can alter the items array.
Either the documentation is wrong here, or there is a bug with the selectTree.

I am trying to use this in a FlexForm context.

Author Kevin Ditscheid
Created 02/13/25, 20:50
Updated 02/18/25, 08:47

Showing results 1126 to 1150 of 1561