Details
-
Bug
-
Status: Closed
-
Top
-
Resolution: Fixed
-
None
-
None
-
1
-
Quasar
-
Puma Sprint 235, Puma Sprint 236, Puma Sprint 237, Puma Sprint 239, Puma Sprint 241, Puma Sprint 242, Puma Sprint 243
Description
For normal documents, in case the document branch is part of a review, the document cannot be edited any more until the review has been approved
It doesn't make sense that in this 'locked' case, an author/editor could still modify the XPage layout in the CM, therefor make sure it is locked (or shown unmodifiable) there as well (perhaps with a lock hint?) cdekort, what do you think?
aschrijvers if the XPage (branch) is part of a project that is in review (or running as a campaign), then the channel is too. Currently this means that overlays and components tab (and Page menu) are disabled and the user cannot edit the layout.
However:
- if the channel has been rejected and the XPage has not, then the channel is editable but the XPage (document) should not be. I'd like the review appearance (overlay) of an XPage to be different than the locked appearance, but indeed: the user should not be able to change the layout of the XPage.
- if the XPage has been rejected and the channel has not, then the channel is not editable but the XPage should be. But editing a layout is hard without a component overlay and with a disabled Components tab...
So the appearance of the project-page in the Experience Manager for a project in review, is not only determined by the project state but by the project-xPage's own state as well!
Attachments
Issue Links
- clones
-
CMS-13366 Make the XPage in CM unmodifiable (locked?) in case an author did a request for publication
- Closed