Bug #23375


IRRE: fails to save preexisting child record selected by combo

Added by Florian Sauer over 13 years ago. Updated 2 months ago.

Should have
FormEngine aka TCEforms
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


Installed Ext IRRE Tutorial Sample files on a clean 4.4.2 Installation to reproduce the error.

- Choose the example "m:n asymmetric combo"
- add a child record mn asym Offers
- select a Hotel (e.g. Rosengarten Hotels Luxury Ressort"
- the newly created offer appears in the combo
- click on the entry in the combo
- fields of this child record are displayed and filled with the correct information of the child record ("offer")
- save and close the hotel record
- open the hotel record from the list again
- child record information has not been saved

The same procedure as described above succeeded on a Typo3 V 4.3.3 installation.

I also applied the IRRE patches I found here (irre_7611_rev8536.. and _v2.patch) but this did not solve the problem
(issue imported from #M15459)


step1.png (66.9 KB) step1.png Riccardo De Contardi, 2018-03-17 22:00
step2.png (28.3 KB) step2.png Riccardo De Contardi, 2018-03-17 22:00
step3.png (47.3 KB) step3.png Riccardo De Contardi, 2018-03-17 22:00
step4.png (26.8 KB) step4.png Riccardo De Contardi, 2018-03-17 22:00
step5.png (30.6 KB) step5.png Riccardo De Contardi, 2018-03-17 22:00
step6.png (30.4 KB) step6.png Riccardo De Contardi, 2018-03-17 22:00
23375.png (105 KB) 23375.png Oliver Hader, 2023-09-22 16:13

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #18968: Add existing records to IRRE fieldClosed2008-06-17

Actions #1

Updated by Thomas Mammitzsch almost 13 years ago

  • Target version deleted (0)


Actions #2

Updated by Lars Houmark over 11 years ago

I can confirm this bug still exists in TYPO3 4.7.5 and it is completely breaking m:n relations and the possibility to relate the same child record to several parents, and by that pretty much makes IRRE useless IRL.

It seems this has been broken for several major TYPO3 versions. Replicating is easy though, simply install irre_tutorial extension, and follow the guide from Florian and the child record ends up empty after saving.

I'll be looking more into debugging, but IRRE is fairly complicated just to understand from a configuration perspective.

Actions #3

Updated by Ingo Schmitt about 10 years ago

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

Updated by Mathias Schreiber about 9 years ago

  • Target version set to 7.4 (Backend)
  • Complexity set to nightmare
Actions #5

Updated by Susanne Moog over 8 years ago

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

Updated by Benni Mack over 8 years ago

  • Target version deleted (7.5)

Updated by Riccardo De Contardi almost 6 years ago

I think it is still reproducible with the latest 9.2.0-dev (latest master) with the following procedure:


1) as the extension EXT:irre_tutorial on TER does not work anymore on TYPO3, you have to copy the fixture from typo3/sysext/core/Tests/Functional/Fixtures/Extensions/irre_tutorial to your /typo3conf/ext

2) enable the extension

3) use the fake data from; once you have imported it, you will have a sysfolder IRRE Sample Tutorial Data with some subpages

Text execution

1) Click on the page "m:n asymmetric combo" and open the hotel record "Rosengarten Hotels Apparment"

2) Offers > Create New > OFFER TEST 1 and save

3) Create a price "PRICE 1 OFFER TEST 1", save and close

4) open the second hotel "Rosengarten Hotels Luxury Resort"

5) create new relation > to OFFER TEST 1 >when you click on "save" you end up with a "No title" relation

6) if you open this record "m:n ASym: Hotels<->Offers" from list view, you'll see that it has offerid: [INVALID VALUE ("0")] [0]

Actions #8

Updated by Riccardo De Contardi almost 6 years ago

Actions #9

Updated by Oliver Hader 5 months ago

With appearance/useCombination enabled, the "child" records is just aggregated, but not composed anymore - thus, it's actually not a "child" record and can be referenced by many "parents". That's why this is basically useful only with a record selector and a cardinality of m:n.

Thus, in case the foreign_field would have been filled, it would only belong to one other entity. I don't know how the TCA was configured, migrated, interpreted back then, in the current ext:styleguide in TYPO3 v13.0-dev the "useCombination" examples seem to work fine.

Actions #10

Updated by Christian Kuhn 2 months ago

  • Status changed from Needs Feedback to Closed

Closing here. This seems to have been resolved meanwhile somehow. In case this is still an issue, let's start with a fresh issue documenting the TCA in question.


Also available in: Atom PDF