Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
# Summary
Replicate module provides an API to duplicate / clone an entity.
# Project URL
https://www.drupal.org/project/replicate
# Where is the code?
# Estimated completion date
Only requires example in readme for Stable according to #2660854: Port Replicate to Drupal 8
# Dependencies
?
# Who's doing the port?
?
# What help do they need?
?
# D8 roadmap
#2660854: Port Replicate to Drupal 8
# Background and reference information
?
Comments
Comment #2
darol100 CreditAttribution: darol100 as a volunteer and commentedComment #3
dawehnerI'm currently starting some work on https://github.com/dawehner/replicate
Comment #4
maxilein CreditAttribution: maxilein commentedWhat is the status of the module? Alpha? Beta?
All the functionality ported and testable?
Comment #5
mmjvb CreditAttribution: mmjvb as a volunteer commentedWith 8.x-1.x-dev Status should be Needs work.
Comment #6
colanLooks like everybody's using Entity Clone now. That module is being used by 1,164 sites vs. 159 for this one.
I just spoke to @dawehner on IRC:
Comment #7
casey CreditAttribution: casey at SWIS commentedI don't think Entity Clone is the D8 replacement of Replicate.
Comment #8
casey CreditAttribution: casey at SWIS commentedFor example the D8 version of the Paragraphs module already integrates with the Replicate module.
Comment #9
colanThat's not a very good example as Paragraphs also integrates with Entity Clone: #2706639: Support for sub-entity cloning.
Comment #10
sachbearbeiter CreditAttribution: sachbearbeiter commentedI had a short look - we have:
https://www.drupal.org/project/quick_node_clone
https://www.drupal.org/project/entity_clone
https://www.drupal.org/project/replicate
https://www.drupal.org/project/node_clone
Maybe the maintainers could try to merge some of the projects?
Comment #11
colanWe should merge everything into Entity Clone. I'm currently doing some maintenance with the maintainer to stabilize it, even though it already has the largest number of sites that are using it.
Comment #12
mmjvb CreditAttribution: mmjvb as a volunteer commentedWith people prepared to port, it should not be Closed (Duplicate), unless maintainers agree. See no agreement here!
Set Status back to Needs work because it was close to be released. Providing a D8 version is the right thing to do. No need to make migration from D7 more difficult than it already is. Not providing a D8 version is just bad release management!
There were some alternatives mentioned above. The current users may choose to go with whatever they want. Consider it a bad thing to force them.
Whether merging the available alternatives is the right thing to do remains to be seen. Planning that definitely is beyond the scope of this issue. Suggest to create a separate issue for that. Once that is available, the modules that don't survive can be deprecated. Which is the right order to do things. First provide the alternative before you remove functionality.
Comment #13
colanSounds reasonable. I was just afraid of everyone working on separate projects instead of working together on a single one, but sure, we can worry about this later.
Comment #14
2Geckos CreditAttribution: 2Geckos commentedAny movement on porting this tool to Drupal 8?
Need a way to replicate calendar content.
Thanks
Comment #15
mmjvb CreditAttribution: mmjvb as a volunteer commentedhttps://www.drupal.org/project/replicate/releases/8.x-1.0-alpha1
Comment #16
colanFollow-up to #13: See #3023686: Redundant module?.
Comment #17
BerdirComment #18
BerdirI think @bojanz is working on getting API's for this into core/entity module to fix the duplication, then these modules could just be a UI and we can consolidate then.
Comment #19
apadernoI am giving credits to the users who participated in this issue.