[CONTLOCK-3] Locking status should not be applied on public instance Created: 14/Sep/22  Updated: 05/Oct/22  Resolved: 05/Oct/22

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

Type: Bug Priority: Low
Reporter: Manuel Schmidt Assignee: Richard Gange
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3h
Original Estimate: Not Specified

Attachments: Text File error-magnolia-locking-app.log     PNG File image-2022-09-14-10-27-00-619.png    
Issue Links:
relation
is related to MGNLUI-6098 Statuses Showing On Content In Public... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled

 Description   

Reproduce

  1. Install the `magnolia-content-locking` extension on Magnolia DX 6.2.18 (tested on 6.2.18 and 6.2.22)
  2. Access asset app in the public instance and you get the attached error.

Expected
No unhandled errors when accessing the asset app, content can be edited if it's done

Actual
Errors are shown in the attached documents.


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