Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I would like to restrict the feature to make a clone to a specific page. How can I achieve this?
Comments
Comment #1
pwolanin commentedYou'd need to provide much more in the way of details in terms of your current configuration.
Probably the short answer would be- you'd need to make a custom adaptation of this module if you really want to restrict to a few specific nodes.
Comment #2
pwolanin commentedComment #3
charles belovTechnically, the status would correctly be closed (won't fix). But I believe there is a use case to reopen it.
If we didn't want users cloning pages in general, but did want users cloning templates, this would be a helpful feature.
For example, we have a meeting content type. There are multiple hearings and committees that hold meetings:
Hearing type A
Hearing type B
Committee C
Committee D
Most information for hearing type A repeats from one hearing to the next, e.g., locations, policies, how to get there), but differs from that same information for hearing type B or the two committees. Therefore, for the meeting committee type, we want templates A, B, C and D.
We don't want them cloning a previous meeting, as there will be additional information from that meeting that does not carry over, e.g., agenda, date, attachments.
So, how can I allow them to clone a template but not anything else?
(I'm not specifically requesting this ability for templates, but in general being able to restrict which nodes are clonable, with the default being not clonable.)