Is this module significantly different from Entity Clone in Drupal 8, which is being used by > 6K sites? If it is, the differences should be documented on the project page. Otherwise, this module should be deprecated, and all development efforts should be directed over there.

At the time of this writing, only 380 sites are using this module.

CommentFileSizeAuthor
#2 replicate_downloads.png23.73 KBrobertwb

Comments

colan created an issue. See original summary.

robertwb’s picture

robertwb commented
StatusFileSize
new replicate_downloads.png23.73 KB

I don't care either way, and thought the same thing myself, but FWIW todays stats (pic below) show this module to have over 15K active sites, and D7 support, which for many developers is a plus.

Replicate downloads 300k, installs 15,000+

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented

That's in total. Click on the link to see the numbers split up by major Drupal version.

Also, while the D7 support is nice, it doesn't really add any value as these modules don't manage any data. There's no upgrade / migration patch to worry about.

It's a simple switch for users to either follow a D8 link here to Entity Clone, or to find a link to it from Upgrade Status (which I already added in #303588: Show suggested replacement for obsolete modules).

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented
Status: Active » Needs review
beltofte’s picture

beltofte
Primary language Danish
Location Copenhagen 🇩🇰
commented

One major reason why I prefer Replicate is the support for Entity Reference Revision (ERR), which makes it useful for cloning entities with nested Paragraphs. See https://www.drupal.org/project/paragraphs/issues/2975033#comment-12628782.

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented

That was fixed in Entity Clone in #2706639: Support for sub-entity cloning so Replicate is no longer necessary.

ekes’s picture

ekes commented

So I'm just doing a quick review to decide which to use. What I'm missing with Entity Clone is the ability to control it easily via the API rather than via a Form. This manifests itself in the fact that the events are called by the form as well - which means they aren't on recursion. And it looks rather non-simple to programatically set what happens to each field and referenced entities (if it they get cloned or not, or if they need to be altered) on a clone by content type or whatever. It would probably be nice to use Entity Clone as there's lots of effort there, but structurally being able to do that seems like re-factoring it quite a bit?

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented

#7: Would you kindly create an issue for this in the Entity Clone issue queue (unless there's one there already)? I would be good to discuss in that context. Maybe this can be fixed with some refactoring, as you suggest, but let's get some feedback from the maintainer, etc.

idebr’s picture

idebr commented

Entity Clone issue is available at #2965701: Add API to entity_clone

acbramley’s picture

acbramley commented

FYI entity_clone still has critical bugs around cloning paragraphs. #3060223: Corrupted data on cloning nodes that contain paragraphs

jannakha’s picture

jannakha commented

No, I don't think it's a redundant module.

It's an API only, clean way to create clones of entities with ability to modify behaviour via EventSubscriberInterface.

Entity Clone has UI which might not be even required.

ruslan piskarov’s picture

ruslan piskarov
he/him
Primary language Ukrainian
Location Kyiv, Ukraine
commented

In my opinion, the Replicate module is the best module for cloning and is very simple.
I use it together with https://www.drupal.org/project/replicate_actions.

hudri’s picture

hudri
Primary language German
Location Austria
commented

There currently is a lot of traction in entity_clone module, covering the two major issues mentioned here: The issue with paragraphs cloning seems finally worked out, and also the cloning API has a promising MR.

When those two MR's are commited, I'd say this module's functionality is fully covered by entity clone.

itamair’s picture

itamair commented

+ 1 to Replicate ...
I was using Entity Clone ... but facing some important issues.
I ended up adopting with Replicate (and Replicate UI) with much satisfaction ...

acbramley’s picture

acbramley commented
Status: Needs review » Closed (outdated)

This module now has almost 18k installs. I think it's safe to say it's not redundant.