[MGNLSLOCK-3] Gracefully handle 401, 404 and timeout errors Created: 15/Nov/10  Updated: 01/Dec/10  Resolved: 15/Nov/10

Status: Closed
Project: Magnolia Soft Locking Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed 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)

 Description   

When the page a user is working on is deleted, moved or renamed by another user or when a user's session expires, a flashing error message appears only when unloading the page (that is the result of calling releaseLock()). We should handle this kind of errors in more user friendly and informative way.


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