Move fields from one entity to another

Created on 22 November 2011, over 13 years ago
Updated 1 March 2023, over 2 years ago

What about a feature to move fields from one entity to another? Use case example -- fields were created on nodes using content profile in D6, I want to move them to either the user or a Profile 2 entity in D7. The field data is migrated fine and ends up on a D7 node, just need a way to switch the entity the fields are associated to (see http://drupal.org/node/560324#comment-4817254).

Another use case -- I have a bunch of populated image nodes and now would like to use media module and move the field data to a media entity from a node entity.

No code to provide at this point, but it should be possible.

✨ Feature request
Status

Closed: won't fix

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States KarenS

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    @joachim: Would you agree with my point in #8?

    Still makes sense to either disallow to copy a field from one entity type to another OR (even better) copy it over correctly.
    

    It's quite dangerous, if someone clones a field across entity types currently, isn't it?
    I suggest only showing current entities fields, until this is properly implemented

    If you agree, I'll provide a patch for that until someone has the time to fully implement support for that.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Update: I created a separate issue for that now: πŸ› Cloning to other entity type bundles should not be allowed, until it's supported Active would appreciate a short feedback @joachim before I start with the implementation.

  • πŸ‡¬πŸ‡§United Kingdom joachim

    > It's quite dangerous, if someone clones a field across entity types currently, isn't it?
    I suggest only showing current entities fields, until this is properly implemented

    It should be fine, but you have to:

    a. check the field name isn't already used on the destination entity type
    b. clone the field storage as well as the instances

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    Thanks @joachim!! :) So this issue can still be used to implement the full support!

  • Status changed to Closed: won't fix over 2 years ago
  • πŸ‡¬πŸ‡§United Kingdom joachim

    Ok.

    I'm going to put this issue to wontfix, since you're working on the new one, and this issue's summary is about field data, which Field Tools isn't going to support.

Production build 0.71.5 2024