-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Replicate module to GovCMS #867
Comments
So I think this offers better value than Quick Node Clone as per #828 I'm curious from those in the community and if you think this functionality would benefit those using GovCMS? Please leave a comment or a +1 on the original post. Thanks! |
I would highly recommend Replicate over other modules as well, however you will also need Replicate UI to get the UI aspect. Replicate's API is much more robust and uses event subscribers to hook into functionality. It works well with paragraphs, layout builder, etc. |
Ah yes, the UI would benefit most users when thinking of GovCMS. Thanks for pointing that out @acbramley ! |
An entity clone module has a huge amount of utility when you think of how long it takes to create a copy of a node which has a lot of paragraphs/etc in it. This often applies to large pages that require a lot of work, so the agency plays it safe and creates a new node for it. I'd take larowlan and acbramley's recommendation for replicate. |
My clients ask for this all the time. |
+1 support Replicate functionality, often requested for the ability to clone content. |
+1 |
+1 also, node clone i have used in the past and is quite helpful with certain use cases. |
I am not familiar with this module. From the module home page: "... You need Replicate if you have the need to clone / duplicate content on your site and if you want to have full control over how entities are replicated, and write specific replication process. How much of this functionality is reliant on creating custom modules to be useful? Are the hooks which it provides easily accessible form the theme layer? Just curious to know how useful this module would be in a GovCMS environment. Given that there is a separate Replicate UI module makes this module sound like it could be more of a developer focused module. Can anyone clarify? |
@Benjen See #867 (comment), it's not very useful without Replicate UI. Both are well maintained modules. We should advocate for adding both to GovCMS. |
+1 Come on GovCMS! You can do it. I believe in you. |
Has been awhile since they have had added a new module :) |
** What value does this module/package add to GovCMS?
It allows cloning of entities
https://www.drupal.org/project/replicate
** Is the module Drupal 10 compatible?
Yes
** Please provide a brief outline of what this module does.
Replicate provides a main cloning function, along with several hooks to control exactly how a field or entity is duplicated based on its type, add info after cloning, and supports custom fields and entities. It is intended to developers and does not contain any GUI (a dedicated module is available).
The goal is to provide a way to easily clone any entity, and to allow developers to be able to control exactly how entities are replicated, based on their type or the fields they contain, and to be able to easily extend the replication control to custom fields or entities.
** Who does this module benefit:
[x] end users
[ ] content editors
[ ] site builders
[ ] themers
[ ] developers
** How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
You can't - see also #828
This is a more thorough approach to replication than quick node clone as it also allows cloning other entities
** If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.
It provides functionality that can't be replicated in the theme
** What is the maintenance and support status of the module. Describe the issue queue activity.
Maintained by core entity API maintainers
Only 9 open issues
1st response is < 1 day
** What permissions are needed to utilise the module (and are any new permissions provided by the module)?
Permissions to govern access to replicating
** Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?
** Is the module designed to capture anonymous user data?
No
** Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.
Yes
** What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?
Of the various cloning modules it is the most robust
** Additional information
The text was updated successfully, but these errors were encountered: