Why use this module over Entity Clone?

Created on 9 September 2022, about 2 years ago
Updated 12 September 2023, about 1 year ago

Entity Clone β†’ has been around for a while. What does this module offer that Entity Clone doesn't and/or why might I choose to use this module instead of Entity Clone?

πŸ’¬ Support request
Status

Active

Version

1.0

Component

Documentation

Created by

πŸ‡ΊπŸ‡ΈUnited States sonfd Portland, ME

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.

  • πŸ‡ΊπŸ‡ΈUnited States boinkster

    This would be helpful on the project page. Entity clone is way more heavy handed and has less granular control on fields, not a bad thing if that's what you need. I had a project with a bunch of entity ref fields, some of them with nested ref's, Entity Clone enthusiastically cloned all the ref's down the stack (again, not bad and kind of cool - if that's what you need).
    This module makes it easier for content editors to choose before committing to make a copy.

  • First commit to issue fork.
  • πŸ‡¨πŸ‡­Switzerland sir_squall

    fully agree, this module is much easier, more faster, and go directly to the edit page (create), just perfect

  • πŸ‡΅πŸ‡±Poland sebaz

    It should be wider explained on module page. Maybe some difference to Entity Clone?

    @orakill explanation in #2 reminds me how node_clone β†’ worked in D7 which was pre-filling form and was allowing you to save the node (with proper filling missing fields) or not.

Production build 0.71.5 2024