Project

General

Profile

Actions

Task #60875

closed

IRRE: On changing a dropdown with onchange only reload that one IRRE-record

Added by Stefan Neufeind over 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2014-08-10
Due date:
% Done:

0%

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

Description

When a dropdown inside a child-record (using IRRE) is configured to force a postback and reload of the record because more/less fields might be visible currently the full record is reloaded. Allow to only reload that one IRRE-record (through AJAX, not with a full page-reload).


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #24398: IRRE uses page reload instead element reloadClosed2010-12-22

Actions
Actions #1

Updated by Martin Sonnenholzer over 9 years ago

Is there even any need to reload (and save) a record for onchange operations, or is this just an old artifact?

Actions #2

Updated by Stefan Neufeind over 9 years ago

Depending on the chosen type certain fields are shown or hidden. Maybe that could even be solved on the client-side, but currently re-rendering the form is done on the server.
Special case for IRRE is that in case an IRRE-record is closed and you open it, it is already dynamically fetched from the server. So upon change of a type-field inside the IRRE-record it should be (easily?) possible to use that same way to just fetch that IRRE-record again instead of the whole page - which currently leads to maybe the browser jumping to the top of the page, back to the first tab (though the IRRE-fields you edited are on the second tab), all other IRRE-fields being closed now and their state being reloaded etc. A real mess for no obvious reason.

Actions #3

Updated by Alexander Opitz almost 9 years ago

  • Status changed from New to Closed

Closing as duplicate of #24398

Actions

Also available in: Atom PDF