TYPO3 Core

I've just seen, that there already has been a patch for 6.2 ([[https://review.typo3.org/#/c/27588/]]), but the bug is occurring again (tested in 6.2.5).

So, is this a regression?

Did you try TCEFORM.tt_content.ctype.keepItems ?

I've tried the above, but this is ignored.

If I use

TCEFORM.tt_content.CType.keepItems = text,textpic,17

the contentelement wizard shows me the items for text and textpic.

Ok, thanks for trying.

To summarize:

working

TCEFORM.tt_content.CType.keepItems = text,textpic

not working

TCEFORM.tt_content.CType.keepItems = text,textpic,17 # Element 17 is missing
TCEFORM.tt_content.CType.keepItems = textpic # No element is shown

Please correct me, if this is wrong.

I have found the reson, why this bug is occurring in my installation.

First of all, the applied patch for 6.2 works fine

TCEFORM.tt_content.CType.keepItems = text,textpic

But in my page TSConfig I use

TCEFORM.tt_content.imageorient.keepItems = 0,25,26

If I add the 17 again

TCEFORM.tt_content.imageorient.keepItems = 0,25,26,17

which is checked by the contentelement wizard in its default values

tt_content_defValues { CType = textpic imageorient = 17 }

the textpic item is shown again in the contentelement wizard.

I would't close the ticket, because from my point of view, it is still a bug that "TCEFORM.tt_content.imageorient.keepItems = ..." is interfering in "TCEFORM.tt_content.CType.keepItems = ..."
concerning the contentelement wizard.
Instead I would change the subject of this ticket to somewhat like "Contentelement Wizard and TSConfig misbehaviour" and change the priority to "should have".

But feel free to close this ticket, if you have another opinion about it or if this bug can't be fixed in the near future.

Seems to be still an issue for 6.2.11

It is still a problem in both 6.2.13 and 7 (latest master): I can confirm that the following Page TSConfig:

TCEFORM.tt_content.imageorient.keepItems = 0,25,26

Makes "text with images" disappear in the new element wizard.

still present on latest 7.6-dev (latest master)

I can confirm it still affects the 7.6.5 but seems fixed in the latest master (8.1-dev). Can someone confirm? Thank you

As far as I can see from my last test, TYPO3 7.6.11 and 8.5-dev (latest master) are not affected by this issue, while TYPO3 6.2.26 still is.

Do you think it is sufficient to consider it closed?