Task #83997

Little Thing on using flexforms displayCond

Added by Maik Hagenbruch over 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2018-02-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
easy
Sprint Focus:

Description

Its just a little thing which bothers me a bit. Maybe i dont understand this behaviour correctly. I will explain.
If i use displayConds and onChange="reload" on backend fields there is an popup which asks me

"Diese Änderung wird die im Formular verfügbaren Felder beeinflussen. Möchten Sie jetzt speichern, um die Anzeige zu aktualisieren?"

In this Case i can sys "ok" and the form reloads or i can say "cancel" and ther form does not reload, but the choosen value which triggered this popup is changed.

In my oppinion the fields value should be set back to the last choosen to show the correct fields.
Maybe its even better to remove the "cancel" option in the popup because you HAVE TO reload the form to see
the changed fields. Maybe this "popup" can completely removed in this case.


Related issues

Has duplicate TYPO3 Core - Task #83999: Little Thing on using flexforms displayCondClosed2018-02-21

Actions
Has duplicate TYPO3 Core - Bug #83996: Little Thing on using flexforms displayCondClosed2018-02-21

Actions
Has duplicate TYPO3 Core - Bug #83995: Little Thing on using flexforms displayCondClosed2018-02-21

Actions
#1

Updated by Stephan Großberndt over 3 years ago

  • Has duplicate Task #83999: Little Thing on using flexforms displayCond added
#2

Updated by Stephan Großberndt over 3 years ago

  • Has duplicate Bug #83996: Little Thing on using flexforms displayCond added
#3

Updated by Stephan Großberndt over 3 years ago

  • Has duplicate Bug #83995: Little Thing on using flexforms displayCond added
#4

Updated by Nicole Cordes almost 3 years ago

I think the current implementation if "onChange" simply reloads the site. Doing this means, the form is not submitted and already changed values are not saved. Thus information would be lost if no popup is shown. Instead of triggering a site reload, the form should be submitted and reloaded.

Also available in: Atom PDF