28073[BUGFIX] Update foreign_sortby field for IRRE 1:n CSVs
Commit message
Review
-
Code review CR 0
-
Verified V 0
Issues 1
Files 1
Review log 12
-
Mr. Jenkins commented on patch set 1 CR -1 V -1 03/05/14, 11:54
Build Failed https://ci.typo3.org/job/typo3-v4-core-gerrit/14595/ : FAILURE -
Thomas Luzat uploaded patch set 2 03/05/14, 12:01
-
Mr. Jenkins commented on patch set 2 03/05/14, 12:14
Build Successful https://ci.typo3.org/job/typo3-v4-core-gerrit/14596/ : SUCCESS -
Mathias Schreiber wrote 12/17/14, 20:37
Topic set to Datahandler -
Alexander Opitz voted on patch set 2 CR +1 06/18/15, 10:29
-
Frederic Gaus voted on patch set 2 CR +1 06/24/15, 13:19
-
Andreas Kienast voted on patch set 2 CR +1 06/24/15, 13:25
-
Daniel Goerz voted on patch set 2 CR +1 07/21/15, 10:06
-
Daniel Goerz commented on patch set 2 CR 0 08/23/15, 11:42
Commit message says 6.2 but its actually a patch for master right now. -
Alexander Opitz commented on patch set 2 08/24/15, 07:18
Hi Thomas, can you please rebase your change? -
Oliver Hader commented on patch set 2 CR -2 12/01/15, 13:26
The foreign_sortyby and symmetric_sortyby properties are only available for the foreign_field approach, not for the 1:n CSV approach. This is unfortunately not well documented, which is the reason for me creating an accordant pull request to the documentation (https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-TCA/pull/52). Implementing that behavior for 1:n CSV is not trivial since the serialization order of the parent (string), default sortby, foreign_sortby and symmetric_sortby needs to be implemented and considered for live workspaces, draft workspaces and record localizations as well. The comma-seprated-list behavior on record relations is a topic to be deprecated in TYPO3 CMS 8 however... -
Oliver Hader abandoned the change 12/01/15, 13:29
Since implementing this behavior in DataHandler/RelationHandler for workspaces and localizations is far out of scope, I'm closing this patch-set.