We extended the CMS with a tagging functionality. For example a client has tagged project pages (planning, funded, completed, type a, type b, type c). This allows us to group pages (all type a projects, all funded or all planned) and link to pages that are in different page trees.
However, to create a new project page an old one is copied and adapted by the client (= user-triggered copy action via the web interface ). With the current setup all tags are then lost. Am Donnerstag, 28. Juli 2016 16:59:35 UTC+2 schrieb Daniele Procida: > > On Wed, Jul 27, 2016, Philippe O. Wagner <[email protected] <javascript:>> > wrote: > > >We are missing a signal that will be fired after a page was copied using > >page.copy_page? > >Would this be helpful for anybody else? > > What is the exact use-case? Is it: > > * a user-triggered copy action via the web interface > * a copy invoked via the CMS's APIs, by an external application > * a copy action triggered by publishing a page > * something else? > > I can imagine that you might want it in one of the first two cases, but > not the third, for example, but I don't think the mechanism actually > distinguishes between the different ways it might be called. > > Daniele > > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to [email protected] --- You received this message because you are subscribed to the Google Groups "django CMS developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/1877f18d-71a2-435e-ac43-034a950f9356%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
