Issue Bug Closed

#11833Sorting order of IRRE records is wrong after publishing

Oliver Hader 01/01/11, 19:48 updated 10/02/18, 12:34

Description

Imagine the following scenario:
  • existing page record with an IRRE field (use irre_tutorial to reproduce, there’s also a test case for this)
  • one child record is existing in live workspace
  • add new child records in custom workspace
  • publish them

The result is, that the sorting order of those child records is wrong, since sorting is applied in t3lib_loadBDgroup->writeForeignField() which gets called when not all records have been processed. The solution is to recall writeForeignField() with a remapAction after all database operations.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.