Repository navigation
Editing Locks EN
Available from plugin version 1.1.0. Editing locks help prevent people from overwriting each other's attendance changes. They apply to one event within one configuration; other events can still be edited.
As an administrator, open Plugin settings → Editing locks.
- Enable Prevent simultaneous attendance recording. This is disabled by default.
- Set Maximum lock duration (minutes). The default is 5 minutes; values from 1 to 1,440 are allowed.
- Save this settings section.
The duration is the time a lock stays valid without a successful renewal. It is not a limit on how long you can work in the form. While the form is open and connected, it renews the lock every 5 seconds automatically.
Opening an attendance form acquires a lock. If someone in another browser session is already editing that event in the same configuration, a message shows their name and you stay on the overview.
This also applies when the same account is used in another browser. Tabs sharing the same browser session can reuse the lock, so use one attendance form at a time to avoid conflicting changes.
A successful save releases the lock. Navigating back or closing the browser does not release it immediately. Once renewals stop, it expires after the configured duration.
Minimising a browser, locking a phone or losing the connection can interrupt renewals. If the interruption lasts longer than the configured duration, the old form can no longer save its changes.
When the form next successfully checks its lock, a message explains that the lock has expired and changes were not saved. After you confirm it, you return to the plugin's main page. Open the event again and re-enter any unsaved changes.
The 5-second check interval applies while the browser is running normally and connected; background tabs and sleeping devices may detect a lost lock later.
Under Plugin settings → Editing locks, choose Clear all editing locks. This button is visible when editing locks are enabled.
It removes all editing locks for the current organisation, including locks for forms that are still being used. Coordinate with the people recording attendance first: their old forms can no longer save, and they receive the expiry message on the next successful check. Saved attendance data is retained.
The settings page confirms the action without reloading. The event can then be opened again to acquire a new lock. Saving the settings with editing locks disabled also clears existing locks for the organisation.
Editing locks prevent concurrent work in different browser sessions. The recording deadline under Rules controls how long attendance may be changed after an event ends. These are separate settings; clearing editing locks does not bypass the recording deadline.