# Summary

Replicate module provides an API to duplicate / clone an entity.

# Project URL

https://www.drupal.org/project/replicate

# Where is the code?

8.x-1.0-alpha1

# 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

darol100 created an issue. See original summary.

darol100’s picture

Issue summary: View changes
dawehner’s picture

I'm currently starting some work on https://github.com/dawehner/replicate

maxilein’s picture

What is the status of the module? Alpha? Beta?
All the functionality ported and testable?

mmjvb’s picture

Issue summary: View changes
Status: Active » Needs work

With 8.x-1.x-dev Status should be Needs work.

colan’s picture

Status: Needs work » Closed (duplicate)

Looks 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:

I guess entity clone is less flexible, but is probably actually battletested, so I would go with those

casey’s picture

Status: Closed (duplicate) » Needs work

I don't think Entity Clone is the D8 replacement of Replicate.

casey’s picture

For example the D8 version of the Paragraphs module already integrates with the Replicate module.

colan’s picture

Status: Needs work » Closed (duplicate)

That's not a very good example as Paragraphs also integrates with Entity Clone: #2706639: Support for sub-entity cloning.

sachbearbeiter’s picture

colan’s picture

We 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.

mmjvb’s picture

Status: Closed (duplicate) » Needs work

With 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.

colan’s picture

Sounds 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.

2Geckos’s picture

Any movement on porting this tool to Drupal 8?

Need a way to replicate calendar content.
Thanks

mmjvb’s picture

Issue summary: View changes
Status: Needs work » Needs review
colan’s picture

Follow-up to #13: See #3023686: Redundant module?.

Berdir’s picture

Status: Needs review » Fixed
Berdir’s picture

I 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.

apaderno’s picture

I am giving credits to the users who participated in this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.