[MAGNOLIA-8740] non-lockable nodes can't be deleted Created: 03/Feb/23 Updated: 03/Feb/23 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.7.7, 6.2.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Marek Lesiak | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: | |
| 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
|
| Description |
|
We have problem with deleting nodes by 'markAsDeleted' action, f.e. assets and some nodes from content applications. An attempt to delete ends with error: javax.jcr.lock.LockException: Unable to perform a locking operation on a non-lockable node. We checked the types of nodes and noticed that there is no "mix:lockable" type: The problem also applies to new assets - we create new assets and they cannot be deleted due to the missing type. It works only when we disable receivers in publishing-core module. We are considering adding a mix:lockable type somewhere in markAsDeleted action by: |
| Comments |
| Comment by Marek Lesiak [ 03/Feb/23 ] |
|
Please close it. It's duplicate of https://jira.magnolia-cms.com/browse/MAGNOLIA-8739 |