Issue Bug Closed

#68614setToDefaultOnCopy prevents from moving relations when record is moved in list module (cut/paste)

Philipp Wrann 07/29/15, 13:37 updated 03/24/25, 12:17

Description

I defined setToDefaultOnCopy for a field “content_elements” because i store the content-element uids in a MM table and when the record is copied the second record would have the same relation, so updating the content in the copied record would also change the original.

Anymay – I recognized, that the relation is also removed when the record is moved (using cut/paste). That should not happen i think, the actions cut and copy are not identical and should behave differently with this option.

Maybe you should have an option to define (for inline+mm elements) that the child record should be copied to… This only happens when using MM relation for inline fields.

Reviews 0

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

History 3

  1. Philipp Wrann commented 10/09/15, 13:17

    If you move a record with inline relations that are set as “setToDefaultOnCopy” you can not translate the relations anymore because the pid is different.

    Reproduce:

    1) Add a field to some record that adds content_elements as inline-relations (like tx_news does)
    2) set the field as setToDefaultOnCopy
    3) move the record from one folder to another
    4) create translation for that record
    5) try to translate the relations -> wont work

    The Installation runs TYPO3 6.2.9.

  2. Christian Kuhn commented and changed status New Closed 03/24/25, 12:17

    Hey.

    I think this issues is obsolete meanwhile: setToDefaultOnCopy has been removed in v10.

  3. Christian Kuhn changed Related to #87989 03/24/25, 12:17