[CONTLOCK-6] Publishing fails when sub node is locked Created: 11/May/23  Updated: 23/May/23  Resolved: 23/May/23

Status: Closed
Project: Content Locking
Component/s: None
Affects Version/s: 2.0.2
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: Sonali Raulo Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-05-11-16-42-56-915.png    
Template:
Start Date:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Steps to reproduce

  1. Go to pages app and lock a page.
  2. Publish a parent page including sub nodes.

.. Logs, screenshot s, gifs...

Expected results

1.Publishing including sub nodes should allow publishing of all the pages except the one which is locked. 

2.User who has locked the page (lock owner) must be able to publish the page even if page is locked.

Actual results

If any of the sub node is locked it blocks the whole publishing. 

 

Workaround

Development notes



 Comments   
Comment by Richard Gange [ 23/May/23 ]

It's not practical for me to rewrite publishing actions to consider locking. It's a hard lock for all users. It's expected that publishing would fail since publishing would be trying to change the node's metadata.

Generated at Mon Feb 12 00:22:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.