Offering to maintain Replicate UI [#3554698]

Problem/Motivation

Based on the plan to make Replicate + Replicate UI the reliable default for cloning entities in Drupal (#3554633: Should Replicate UI become THE Drupal entity cloning module (and deprecate all others)?) I'd like to offer my help as maintainer of https://www.drupal.org/project/replicate_ui

It seems that most of the current maintainers are not active, while @Berdir already has A LOT of modules to maintain and also invests a lot of time in Drupal core.

So here's my (and our companies) offer to help to push things forward! :)

If @btopro (only maintainer with "administer maintainers" permission) sees this, please also see #3554700: Make 8.x-1.x the default branch - Only users with "administer maintainers" permission can set the default branch. So I'd vote to also make @Berdir full maintainer or give him the appropriate permissions. If possible, please change the default branch directly.

Thank you! :)

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

Comment #1

28 October 2025 at 08:11

anybody created an issue. See original summary.

Comment #2

anybody

German

Porta Westfalica

commented 28 October 2025 at 08:17

Issue summary:

View changes

Comment #3

berdir

German

Switzerland

commented 30 October 2025 at 07:03

Status:

Active

» Reviewed & tested by the community

Oh, I wasn't aware that I can't give you access here either myself.

Either way, I think there's plenty that you can help without having access, based on the discussions we've had in the linked issue:

* Draft new project pages for both modules (I'd suggest an issue for each module and put it in the issue summary so I can copy the raw HTML), for the current state, and possibly also preparing for the 2.x plan by mentioning that, then once it's starting to be ready, we can switch to making that the focus)
* Create an issue to drop usage of the replicate API and just call $entity->createDuplicate() directly, we can make that the start of the 2.x branch.
* Work on other issues, such as the redirect one, more general, adopt functionality we consider useful from replicate_actions per #3554706: Merge functionality into replicate_ui, each configurable I'd say. Quick notes on that: unpublish: Yes, but we should also support content_moderation with a configurable target state for replicated entities (publish could be on by default, but content moderation requires a setting as states are configuration, could check if draft is available. see similar logic in tmgmt). set owner: yes (maybe on by default?). redirect: yes, i think even by default/unconditionally, group integration: We actually have that custom, but also exposed in the UI where you can optionally alter the target group. lower prio, maybe as a separate integration module.