Permissions and Metadata Schemas when cloning

(Oliver Kass) #1

Matrix Version: 5.3.4

We’re working on a version of a site and ideally would like to clone some file assets down from the live version while we work on the build.

One issue I’ve encountered is that the cloned assets keep the permissions and schemas that were assigned to the original as well as inheriting the new site’s relevant permission/schema settings.

Is there a way to clone assets across to a new site and only apply the new permissions/schemas?? The fact that it’s also keeping the old settings by default is annoying and could potentially cause issues further down the line.

Obviously can go in and manually delete but thinking there must be a better way. Triggers?

Oli

(Bart Banda) #2

Yea I think Triggers would be the way to go.
Alternatively, once you have cloned all your assets to your new site, you can apply the old Schema and Permissions on the new site asset (but don’t cascade the change), and then remove them (and cascade the change). That should run a Hipo to remove those schemas and permissions from any child assets under that site that still has them.

(Oliver Kass) #3

Thanks Bart. Will look at both options.