Project

General

Profile

Actions

Feature #34624

open

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

Added by Nico de Haen over 12 years ago. Updated over 4 years ago.

Status:
Accepted
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2012-03-07
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

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? ;-)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #89220: Revert value of input if confirmation modal is not acceptedClosed2019-09-21

Actions
Actions

Also available in: Atom PDF