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.

Rewriting contents and protected content

tonizz

I have a web form that releases a file called "content.html" in a folder. when I already have a content alfresco doesnt let me to rewrite the file.

Does somebody know how to do it??

Besides, everywhen I release a content, alfresco sais that the content is protected and doesnÂ´t let me to remove it. The content appears with an small padlock. Why is it happening?

Thanks in advance.

Find more posts tagged with

Comments

arielb

in 2.1, content gets locked when edited in a sandbox. the lock is released once the content is submitted. however, while in the sandbox you should still be able to edit or revert the changes.

kvc

To add to Ariel's comment:

By default, when using the web client, all content that is created or modified is automatically locked in the GUI. That means that other users when browsing content in their sandbox will see a small padlock icon meaning that the item is currently sitting in another user's modified items list and is currently not available for editing. This resolves a concurrency issue prior to 2.1, where if an item was modified but not yet submitted another user could theoretically make concurrent, and conflicting edits.

Only user's who created and modified an asset can edit that asset in their own sandbox (since they own the lock). The exception to this is a Content Manager, who can also edit locked resources in their web project in that user's sandbox. If you want to release the lock, you can do so by either Undo-ing your change (selecting the Undo action and reverting to its original state) or by submitting the asset (which auto-unlocks once approved and checked in to Staging).

Please note that for power users (developers), locks are not automatically taken for actions done via the CIFS interface. In future releases, for these developer types working via CIFS will intend to expose more of the repo services for branching and merging, which currently is not exposed in the web client.

Kevin