-
Notifications
You must be signed in to change notification settings - Fork 69
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
Upgrade Wizard "Migrate container sorting" not marked as done #539
Comments
I had the same problem, but was able to solve it today (TYPO3 11, Container 2.3.6). Have you checked/debugged which containers the wizard is trying to fix? In my case, the wizard always reported the same 5 items to fix, no matter how many times I'd run it. I re-created those containers and the problem was gone. I think there were some broken references to them, which could not be fixed or handled by the wizard. |
I also only managed to fix the issue by deleting the broken containers and rerunning the wizard. To identify which containers need to be recreated, you can add a var_dump() to the errors in Classes/Integrity/Sorting.php on line 95:
This will output the list of broken containers, helping you pinpoint the ones causing the issue. |
Hi, I also have big trouble with Upgrade Wizard "Migrate Container sorting". If I use the var_dump in the comment before I got a very huge list with hundrets of containers that should be "fixed". How can I debug it? What exactly is to fix in database? TYPO3 11 to 12 |
The upgrade wizard "EXT:container: Migrate 'container' sorting - change sorting of container children" runs without errors but is not marked as done.
I have executed the wizard more than 10 times (both in the backend and via CLI), but it keeps reappearing.
Tested with PHP 8.2 and TYPO3 v11. After upgrading to TYPO3 v12 (with the wizard still pending), the wizard continues to run without errors, but it still isn't marked as done. So far, I haven't identified any issues indicating that the wizard was not successfully executed.
The text was updated successfully, but these errors were encountered: