Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

CQ 5.6: Is there a way to make a given page unmovable and/or uncopyable?

Avatar

Level 7

Hi,

Is there a way to make certain pages unmovable/uncopyable in CQ5?

For example, we want all pages that are located at /content/myapp/*/home not to be movable and/or copy/pastable.

Also is it possible to make sure that only specifc page (node) names are allowed under a given path (e.g. /content/myapp/*/)?

To be more precise, in our deployment, we have folders similar to:

  • /content/myapp/site1
  • /content/myapp/site2,
  • etc.

site1, site2, etc. are [nt:folder] nodes.

Under each of these folders, there's one "root" page named "home":

  • /content/myapp/site1/home
  • /content/myapp/site2/home,
  • etc.

We want to prevent users from creating any other pages right below site1, site2, etc. and only allow them to create pages that are children of home.

We also want to restrict users from copying any of these home nodes and paste them back to the same site node.

Finally, we also want to prevent users from copying any page, and paste them under any of site1, site2, etc. nodes

What options do we have to implement these requirements?

Thanks.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi,

It isn't easy to prevent users not to use copy&paste, because you cannot deny it via ACLs. If a user can create a new page, she can do it either manually or by using copy&paste. The only chance I see is to disable the copy&paste menu items.

kind regards,
Jörg

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

Hi,

It isn't easy to prevent users not to use copy&paste, because you cannot deny it via ACLs. If a user can create a new page, she can do it either manually or by using copy&paste. The only chance I see is to disable the copy&paste menu items.

kind regards,
Jörg

Avatar

Level 4

You may restrict your templates ( other than homepage ) to be created under home only with allowedPaths property ( eg, /content/myapp/site1/home(/.*)? ) and create the actual homepage programmatically and uploading as package. If there is no allowedPaths  property set for your home page template , it can not be created by anybody.