Issue Feature Closed

#34624Changing the type field of a new element should not result in saving

Nico de Haen 03/07/12, 08:12 updated 04/20/25, 14:37

Description

This is really an old gremlin, but I couldn’t find an issue related to that.
Changing the type field of a new element should not result in saving that element.

This is for 3 reasons:
1. There is no validation (possible) since the required fields of a certain type may be not visible in the other types configuration
2. If you click on “Cancel” instead of “Ok” you will have a mixed form: the type field selector shows the new type but the form is still displayed with the old types configuration
3. For usability reasons any dataset should only be saved when an editor clicks the save button

As you probably know this behaviour is almost as old as TYPO3, maybe we can get rid of it in 6.0? ;-)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.