TYPO3 Core

The Records Selector may return different results for pages, depending on where you click (either left column or right column). Apparently either a page id is returned or a "pages_ID". In the situation described below, the page ID then resolves to a tt_content id ("tt_content_ID").

This was originally reported for gridelements and can be reproduced with the latest EA version, see https://github.com/CodersCare/gridelements_EA/issues/510

I have create a minimal example where this is also reproducible: https://github.com/sypets/sypets_example_shortcut_records_pages

What is affected¶

If the configuration for the tt_content.records field (or something else?) has been changed to accept pages as well:

$GLOBALS['TCA']['tt_content']['columns']['records']['config']['allowed'] .= ',pages';

Reproduce:¶

either with gridelements or my example extension:

1. Create a content element with type "shortcut"
2. In the form, for records, click on "Page" (not "Page Content" !)
3. In the "Record selector" select a page in the left column (not in the right column) by clicking on the link symbol on the right.

What is now written to records is something like this:

select uid,records from tt_content where uid=454;
+-----+----------------+
| uid | records        |
+-----+----------------+
| 454 | tt_content_491 |
+-----+----------------+

In case no corresponding tt_content element exists for the page id, nothing is written to the field.

Cross checking¶

Weirdly enough, doing the same thing with pages.shortcut is not a problem, but here there are not several table types which can be used, it is always pages.

Screenshots¶

Screenshots for testing with gridelments: