-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copied content elements pasted with wrong sorting value #422
Comments
Hi @dariuskapitza , can you describe how this is reproduceable on a TYPO3/container Vaniila Instance?, i know nothing about any gridtocontainer migrations ... |
We have exactly the same problem. We can reproduce it in one of our project. |
container-sorting.tar.gz
|
ok, got it, the problem here is that "global" sorting on this page is "wrong"
should be:
result can be achieved by
container sorting command only fixes sorting of container children. |
This command maybe helpful when migrating to EXT:container from any other grid extension and have inconsistent sorting on page, e.g. container is sorted before previous container child fixes: #422
This command maybe helpful when migrating to EXT:container from any other grid extension and have inconsistent sorting on page, e.g. container is sorted before previous container child fixes: #422
Hello,
we have upgraded two projects from TYPO3 v10 to TYPO3 v11 and migrated fron Gridelements to b13 Container. Both projects have the described problem below:
The migration was done with the gridtocontainer extension.
Migrated with
gridtocontainer:migrateall
command executions and cleanups in the database as described on https://docs.typo3.org/p/sbublies/gridtocontainer/main/en-us/Usage/Index.html and https://docs.typo3.org/p/sbublies/gridtocontainer/main/en-us/CommandReference/Index.htmlWe have executed the
container:sorting
command (with--apply
) mentioned in the issue#415 and executed
referenceindex:update
.Now there is a problem pasting a (simple) content element like header into a page row (not into a container) when migrated container elements are on the target page. The copied element is placed somewhere else on the page, mostly on the top but not always.
Pasting on new pages with new created container elements seems to be fine, but maybe this is randomly correct.
More details / Environment:
The text was updated successfully, but these errors were encountered: