TYPO3 Core

hey. could you provide a database sample to easier reproduce it. that would be great!

Hello,

You can use this query to update a be_groups with old data on your V12 database (set the correct uid):

UPDATE be_groups SET explicit_allowdeny='tt_content:CType:header:DENY,tt_content:CType:bullets:DENY,tt_content:CType:table:DENY,tt_content:CType:list:DENY' WHERE uid=xx;

and next:

mark undone the upgrade wizard " Migrate backend groups "explicit_allowdeny" field to simplified format " and perform it.

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

Hi Florian,

Thanks for this query, this made reproduction for me REALLY easy.

I created a patch for it. It's a bit nasty, but luckily this is the only core wizard who has this odd side effect to report additional messages that should be revealed as errors.

The symfony message stream tags the output with "error", which is seen on the console output, but not with the Wizard GUI integration sadly. The Wizard GUI sadly only knows TRUE or FALSE as a result of the upgrade.

Since this wizard actually does perform most of the migration (apart from those listed as an error) it's not a true failure, but more a soft failure - and you are right, this needs to be revealed better to the user.

My patch does it in a way that these messages are in fact returned as errors, AND the wizard fails (even though it executes). The second execution would mark it as completed. I think that would be a fair solution, because the "proper" solution to it would be to chang ethe wizard API to allow for "notices". That would be a breakiung change and can't be done in either v12 nor v13 at the current time.

What do you think?

Patch set 1 for branch 12.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/+/84955

Thanks Garvin for the patch!