禁用项目被锁定
我被要求关闭用户“锁定”项目的可能性。
他们可以在内容编辑器中执行此操作(“审阅”>“编辑”)。但当用户使用“页面编辑器”时,似乎也会发生这种情况。
有办法把这个关掉吗?
据我所知,它在 web.config 中被关闭:
<setting name="AutomaticLockOnSave" value="false"/>
<setting name="AutomaticUnlockOnSaved" value="true"/>
<setting name="KeepLockAfterSaveForAdminUsers" value="false"/>
<setting name="RequireLockBeforeEditing" value="false"/>
<setting name="UnlockAfterCopy" value="true"/>
但是,如果用户在 Sitecore 中锁定了某个项目,则使用页面编辑器的用户无法编辑该项目,因为它已被锁定。它说:
You cannot edit the current item because it is locked by: <username>
有没有办法完全禁用此功能?
最好的问候,
克里斯蒂安·威廉森
I've been asked to turn off the posibility for users to "lock" an item.
They can do this in the Content Editor (Review > Edit). But it seems it can also happen, when users are using the "Page Editor".
Is there anyway to turn this off?
As far as I can see it's turned off in the web.config:
<setting name="AutomaticLockOnSave" value="false"/>
<setting name="AutomaticUnlockOnSaved" value="true"/>
<setting name="KeepLockAfterSaveForAdminUsers" value="false"/>
<setting name="RequireLockBeforeEditing" value="false"/>
<setting name="UnlockAfterCopy" value="true"/>
But if a user has locked an item in Sitecore, a user using the Page Editor can't edit the item, as it is locked. It says:
You cannot edit the current item because it is locked by: <username>
Is there a way to disable this feature completely?
Best regards,
Christian Willumsen
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我对此没有直接的答案,但既然到目前为止你还是空的,我会给你我的初步反应......不要尝试将其关闭,只是让用户更容易解锁与工作流程。
如果您对内容应用简单的一步式工作流程,Sitecore 仍会在内容工作时自动锁定内容,但通过单击工作流程步骤,您的用户可以解锁内容项,甚至发布它。
锁定是有原因的。这对用户来说很烦人,但工作流程可以让它变得不那么烦人。
I don't have a direct answer to this, but since you're turning up empty so far, I'll give you my initial reaction... don't try to turn it off, just make it easier for users to unlock with workflow.
If you apply a simple one-step workflow to your content, Sitecore will still automatically lock the content when they are working in it, but through a single-click workflow step your user can unlock the content item and even publish it.
Locking is there for a reason. It's annoying to users, but workflow can make it way less annoying.