[MGNLSLOCK-50] Notification of pending changes is shown several times Created: 24/Sep/19  Updated: 16/Dec/21

Status: Open
Project: Magnolia Soft Locking Module
Component/s: None
Affects Version/s: 2.7, 3.0
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Adam Siska Assignee: Unassigned
Resolution: Unresolved Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSLOCK-56 Display notification as stack instead... Open
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
Date of First Response:

 Description   

Steps to reproduce:

open two magnolia instance with different users logged (superuser, eric):

1) as superuser open sporstation page

2) as eric open the same page (superuser gets notification about this)

3) as superuser open "edit page properties" dialog, update "navigation title" field and save changes

4) eric gets "pending changes" notification eight times in a row

Basic observation: This is a bit bypassed in M5 by auto-closing notification after delay. If user does nothing, all notification are closed automaticaly. Bug can be seen if one tries to close notification before self-closing. Behaviour is a bit different in M6 as notifications disappear sequentially one after another always with new closing delay (so delay is way to long in described case).



 Comments   
Comment by Richard Uttenthaler [ 16/Dec/21 ]

Please also consider the usability here (see [SUPPORT-14066] Softlocking Module - Trigger "user no longer editing this page" wrong - Magnolia - Issue tracker (magnolia-cms.com))

From my point of view (and maybe also by some productive users), notifications should not disappear after some time. To reduce parallel editing, the user must close the notifications. Think of real scenarios (Children's distraction, coffee breaks)! 3.6 seconds (the actual delay) is quite short

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