Add ability to duplicate whole event page to quickly populate repetitive adding of events

[willguv]

This was posted by @LizziCBFC

We run a lot of events that are very similar. When we get blocks of events to add we are manually creating an event for every one, and the location/facet details are often the same. It would be useful to be able to quickly duplicate a single event and tweak where required.

[andybroomfield]

Maybe something like

• Quick Node Clone
• Entity Clone
• Clone Nodes

How will this play with the recurring date functionlity that already exists with events? I seem to remember cloning nodes causes some issues with refrences as just the references used to get cloned, but still point to underlying data.

[ekes]

We're using Replicate for microsites. It's much easier to configure (as a programmer) and hide the complexity from the user. Some of the other clone options have quite scary UIs to default clone paragraphs, but not taxonomy terms etc. But using replicate would need thought here if other fields can be added to the content type by the end implementation.

[andybroomfield]

Sounds like a good plan, though is replicate API only?

[ekes]

Sounds like a good plan, though is replicate API only?

Yes, exactly the reason you can end up with a decent UI :) What I've done elsewhere with it (for user triggered clone of individual content) is add a route, local task and controller (extending drupal confirm form). This clones the entity and appropriate referenced entities (down the tree as required).

It's just the thing about adding fields on different sites. You will end up needing a configuration UI that's like Entity Clone? Or is there a more clever way of doing that too, when we know a lot about the entities already?

[andybroomfield]

For reference #56 has the differences between stock localgov_events and what Brighton has, so some way to either extend it or for it to know to clone all fields and how to treat them would be helpful. I guess from a UI perspective its just replicate event and takes you to the new events edit page when done.

[ekes]

I guess from a UI perspective its just replicate event and takes you to the new events edit page when done.

Exactly, removing the option to choose which bits get cloned makes it with the example I mentioned: click 'Clone' tab, hit 'Confirm' on form, end up on new cloned content.

[willguv]

Thanks for this input everyone!

"Duplicate" seems a better word than "Clone", do we have any choice over this?

Flagging to @LizziCBFC too

[willguv]

@RyanFH257 uses Entity Clone at H&F. Could bulk upload of events remove the need for cloning

@andybroomfield familiar for events in Libraries etc. If we use Replicate we could configure something that makes sense for each content type

@stephen-cox agrees Replicate best for this reason

Will: we need to avoid people having to think about what part of the content they need to clone. We can create sensible defaults

eg clone an event, but not the venue

@stephen-cox let's estimate effort Entity Clone vs Replicate