You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I do: I copy a content element with FAL References from one page into another page into a position, where it doesn't belong, but not first position on page.
What happens:
The element does not appear on his new position (correct)
An error flash message pops up (correct, but I got 2 for one element, hard to read for an editor)
The original record gets all FAL references twice (Wrong)
Why does this happen (IMHO):
The insert of the new record is not stopped inside the DataHandler::processCmdmap_beforeStart it gets stopped inside the DataHandler::processDatamap_beforeStart so the copy of the references gets preprocessed but not postprocessed which leads to doubling the references on the source record.
The CmdmapDataHandlerHook doesn't support negative target ids (beside the DatamapDataHandlerHook does this) for inserting Data after a given record on target page. (Maybe this leads to Copy&Paste of container element with children #74 )
The newly introduced $backendLayoutConfiguration->getConfigurationByColPos gets the id of the source record and thinks it needs to handle this which leads to issues in b13/containers handling
What else may be wrong:
The BackendLayoutConfiguration::getConfigurationByColPos have a static cache on $columnConfiguration which holds configurations depending on $colPos but the result may also depend on $recordUid as this is a parameter for the hook manipulateConfiguration (Maybe the $recordId was meant as a hint/helper but b13/conteiner returns different results).
The text was updated successfully, but these errors were encountered:
opi99
pushed a commit
to extrameile/content_defender
that referenced
this issue
Dec 10, 2020
System: TYPO3 10.4.10
contend_defender: 3.1.0
b13/bolt: 2.0.2
b13/container: 1.2.0
What I do: I copy a content element with FAL References from one page into another page into a position, where it doesn't belong, but not first position on page.
What happens:
Why does this happen (IMHO):
$backendLayoutConfiguration->getConfigurationByColPos
gets the id of the source record and thinks it needs to handle this which leads to issues in b13/containers handlingWhat else may be wrong:
BackendLayoutConfiguration::getConfigurationByColPos
have a static cache on $columnConfiguration which holds configurations depending on $colPos but the result may also depend on $recordUid as this is a parameter for the hook manipulateConfiguration (Maybe the $recordId was meant as a hint/helper but b13/conteiner returns different results).The text was updated successfully, but these errors were encountered: