TYPO3 Core

Georg Ringer wrote:

Thanks for your report! Which type of page module are you using? You can check that in Install Tool > Settings > Feature toggles > Fluid based page module > Is this enabled or disabled?

If it is enabled, can you please check if it works if it is disabled which uses then the "classic page module."

It appears in both modes. Changing to classic doesent fix it but currently im using the new one.
Looks like this issue disappears at a certain amount of CEs. With one CE in col 1 and two CEs in col 0 the sorting isnt working but now i have about seven CEs in col 0 and its working...strange.

Got the same Issue at TYPO3 10.4.1 in both modes, even if I use only one column.

TYPO3: 10.4.1
Fluid based page module
PHP 7.3.12

I got the same bug. The output on the frontend side differs from that what we see in the module, but the frontend ordering respects the ordering saved in the DB. After the bug occurs, the ordering can't be changed anymore through the module and no change will be applied in the db .

Same issue for me.

Probably another useful information:
Creating a menu through a MenuProcessor for all content elements of the current page (e.g. for one pagers and so), the order in the menu differs from the order in the content.

Example:

Menu:
News - About us - Contact

Content:
1. Contact
2. News
3. About us

In the case of Contentelements:
Even if the ordering is changed via drag and drop, the sorting in the db is changed correctly. Just the output in the BE-view is wrong. I got two reloads in that view. first the output is correct and after a second reload it is sorted back by uid.

Hm ... this is realy strange ... I now changed some deleted elements in database (set visible and changed page id) and suddenly sorting is correct. I had same behaviour yesterday and after some other changes sorting was broken again???

... it seems to be some combination with the number of content elements of page. In my case, if I have 16 or more content elments active, sorting is broken. 15 elements -> sorting is ok. But I do not know what it is depending. Because yesterday when see bug first time, there where only about 8 elements active and sorting was broken also.

I am not sure, if my hack is fine, but adding sorting in query builder seems to fix my problem. In file typo3/sysext/backend/Classes/View/BackendLayout/ContentFetcher.php I added in line 210 ->orderBy('sorting');

..
$queryBuilder
            ->select(...$fields)
            ->from('tt_content')
            ->orderBy('sorting');

        $queryBuilder->andWhere(
...

I have an empty, new 10.4.1 installation. Sorting does not work in the page module. After adding "orderBy('sorting');" it works. After installation and activation of "gridelements" it does not work again. I created a simple single-column gridelement. All content elements moved into the grid. Sorting works within the grid. All content elements moved out of the grid again. Sorting does not work

I have the same Problem!

This seems to have been the regression for the legacy PageLayoutView, since the whole $addSorting section has been removed.
Later on the parameter was removed from the method parameters too, but sorting has not been reimplemented yet.

https://review.typo3.org/c/Packages/TYPO3.CMS/+/63063/9/typo3/sysext/backend/Classes/View/PageLayoutView.php#b3032

        if ($addSorting) {
            if ($this->sortField && in_array($this->sortField, $this->makeFieldList($table))) {
                $queryBuilder->orderBy($this->sortField, $this->sortRev ? 'DESC' : 'ASC');
            } else {
                $orderBy = $GLOBALS['TCA'][$table]['ctrl']['sortby'] ?: $GLOBALS['TCA'][$table]['ctrl']['default_sortby'];
                $orderBys = QueryHelper::parseOrderBy((string)$orderBy);
                foreach ($orderBys as $orderBy) {
                    $queryBuilder->addOrderBy($orderBy[0], $orderBy[1]);
                }
            }
        }

Since the ContentFetcher class has been created for the first time after that patch, the sorting part is missing in there too, because it was unknown to the team working on it, that the former $addSorting parameter did not exist anymore.

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64567

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64567

I don't know if this is only a gridelements related problem which we're using on our pages, but if that's not the case, then I realized this unexpected behaviour in TYPO3 v9.5.17 & 9.5.18, too.

- We're placing a header and a text element inside a gridelement in a workspace environment (not PROD) and check this in the frontend: everything is looking fine.
- Then we're changing the order of the two elements via drag and drop: text first, header second. For a short time everything is looking like expected, then there's the autoreload and after that the ordering is the same as before (header first, text second). But in the frontend is the text first, header second.

Can anyone reproduce that behaviour? When NOT using a workspace, everything is working fine.

Update: The same is happening on TYPO3 v8.7.30 (& gridelements v8.5.2).

New TYPO3 version 10.4.4 LTS but the same problem. Sorting in the page module not possible. Version 10 is not usable at the moment.

The Same for me with TYPO3 10.4.4 together with gridelements version 10 and new_bootstrap_gridelements version 10. Ordering in page module is broken. You can reorder CEs but the visual Feedback is wrong.
The Patch (https://review.typo3.org/c/Packages/TYPO3.CMS/+/64567) is working fine. Thanks to all that worked on this patch!

Still problems in 10.4.4 with sorting. Gridelements and Mask installed.

Same here. Typo3 10.4.4, Mask 5.0.0, Gridelements 10.0.0

Same problem here with TYPO3 10.4.4, gridelements and mask - but the Bugfix Jo presents seems to work for me

Same problem still exists unter Typo3 10.4.5 - no matter which feature is selected. Using gridelements in v10 and normal tt_content-Elements. Typo3 unusable for the client at the moment. The patch mentioned above solves the problem! THX.

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64567

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64567

Recreation of the index didnt work for me in 10.4.6. The elements still jumps back after reload.

Same here in 10.4.6. The elements jumps back after reload. No chance to sort CE's in the page module.

same here with a fresh install of 10.4.6 and a clean index

Same with TYPO3 10.4.6 and PHP 7.4.2, no gridelements but with Container Extension.
If i add a new Content Element on the top of the Page, the Content Element will be ordered to the bottom of the page - but only in the Backend Page view.

Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64567

Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64567

Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64567

Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65427

@Jo: Is this something that you can apply to TYOP3 v9 branch, too?

Jo Hasenau wrote in #note-42:

Sorry - I just missed that getQueryBuilder will make use of prepareQueryBuilder too - so while the behaviour is still buggy, it does not seem to be caused by a missing orderBy.

Closing this issue again.

Still it bugs. Is there another issue going on?

Any updates here? This is a major issue.