Project

General

Profile

Actions

Bug #24398

closed

IRRE uses page reload instead element reload

Added by Lorenz Ulrich over 13 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2010-12-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
nightmare
Is Regression:
No
Sprint Focus:

Description

If a record you're adding has a type field, changing the type forces a reload of the element (i.e. an IRRE tt_content/text record and you're changing it to a text with image record). As the whole page is reloaded and not only the element, all IRRE elements are collapsed after the reload. So you loose the context you've been working in. This is a usability weakness that can be quite annoying when you have a lot of records, i.e. in a big Powermail form.

(issue imported from #M16822)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #48686: Don't reload form when changing field typeClosed2013-05-31

Actions
Has duplicate TYPO3 Core - Task #60875: IRRE: On changing a dropdown with onchange only reload that one IRRE-recordClosed2014-08-10

Actions
Actions #1

Updated by Urs Braem almost 13 years ago

  • Target version deleted (0)

This is definitely an annoying behaviour.

There is a workaround for the moment: if you're inserting records (say a dozen new form fields in Powermail) you can answer the "Would you like to save now in order to refresh the display" dialog with "Cancel", so you can go on inserting fields, and in a second roundup fill in all the details for each record after having saved.

Actions #2

Updated by Ingo Schmitt over 10 years ago

  • Category set to 978
  • Is Regression set to No
Actions #3

Updated by Mathias Schreiber over 9 years ago

  • Target version set to 7.4 (Backend)
  • Complexity set to nightmare

just saying:
We know about this, but this requires rewriting FormEngine, which is 50% of TYPO3 :)

Actions #4

Updated by Susanne Moog almost 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #5

Updated by Benni Mack over 8 years ago

  • Target version deleted (7.5)
Actions #6

Updated by Andreas Kienast over 4 years ago

  • Status changed from New to Closed

This issue is solved in at least v10, all IRRE record preserve their according state on reload.

Actions #7

Updated by Frank Gerards over 2 years ago

i cannot confirm, that the behaviour is solved in v10.4.latest - IRRE childs in a content-element field get lost, if an reload-event occurs in the IRRE child and the parent record is not saved.

Actions

Also available in: Atom PDF