nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Looking for easy way to mark content read-only

davidpisaac

Hello-

Does anyone know a simple way to mark content read-only that would override read/write permissions? It looks like I must break permission inheritance, copy the authorities down, and give them access with a different permission set. I was hoping for something simpler.

Find more posts tagged with

Comments

kevinr

There's not really any mechanism that is simpler. If it's web-client specific then you could add a UI evaluator to hide the action etc. but it's still some work.

Thanks,

Kevin

davidpisaac

Thanks Kevin. What about using the LockService, lockable aspect, or jcr:lockisdeep?

Is there any documentation on the lockable aspect, especially the effects on repository operations? I can't find it, unless I assume it is tied directly to the LockService, and even then I don't know the effect of differen lock types.

I'm not afraid of code as documentation, so don't hesitate to point me there if needed.

alarocca

It's curious that if you open a document (better if a ms office document) via webdav, that file is locked and the lock is showed by the web client too. I guess this mechanism is based on the lockable aspect. Unfortunately it seems that it was implemented just for WCM and webdav. CIFS (avmfilesystem) does not lock by default but can do it.

See http://wiki.alfresco.com/wiki/Content_Locking

Thanks Kevin. What about using the LockService, lockable aspect, or jcr:lockisdeep?

Is there any documentation on the lockable aspect, especially the effects on repository operations? I can't find it, unless I assume it is tied directly to the LockService, and even then I don't know the effect of differen lock types.

I'm not afraid of code as documentation, so don't hesitate to point me there if needed.

davidpisaac

For those interested in this topic, I read that permissions on a child override permissions inherited from a parent. So, you should be able to put a DENY-Write-EVERYONE on the child to make it (and everything inherited from there down) read only. I haven't tried it yet, since DENY is not available from the UI or JavaScript. Feel free to try and post here if you get to it first.

cbosdonnat

For those interested in this topic, I read that permissions on a child override permissions inherited from a parent. So, you should be able to put a DENY-Write-EVERYONE on the child to make it (and everything inherited from there down) read only. I haven't tried it yet, since DENY is not available from the UI or JavaScript. Feel free to try and post here if you get to it first.

You can do this quite easily with a custom aspect. Let's say this aspect is named my:readonly. You can add some behaviour on an aspect addition or removal by using Behaviour policies. You have an example of an aspect with behaviour policies in the SDK examples: CustomAspect. The example aspect is counting the number of click on a document with this aspect.

In your casee, the my:readonly aspect will need to register the following policies:

OnRemoveAspectPolicy : remove the denied permission on the node
OnAddAspectPolicy : add the denied permission on the node

To add and remove the permission, you'll need to use the foundation services, more precisely the PermissionService.

Then setting your document read-only is as easy as apply your my:readonly aspect, which could be done using the webclient or javascript.

I hope this helps