Plugin for locking records so only one user can edit them at same time.
This plugin provides the functionality to prevent data loss in cases where multiple users are simultaneously editing the same record within STRAPI v4.
When a user attempts to edit a record that is already being edited, a warning will be displayed.
✅ Safeguards against concurrent editing by restricting access to a record to a single user at a time.
✅ Provides clear visibility of the current editing user, enabling you to easily identify who is working on the record.
1
npm i @notum-cz/strapi-plugin-record-locking
1
yarn add @notum-cz/strapi-plugin-record-locking
config/plugins.js
and include the following code snippet:1
2
3
4
5
module.exports = ({ env }) => ({
"record-locking": {
enabled: true,
},
});
We use websockets and you can determine the necessary transport yourself:
1
2
3
4
5
6
7
8
module.exports = ({ env }) => ({
"record-locking": {
enabled: true,
config: {
transports: ["websocket"]
}
},
});
If you do not specify a transport, the default parameters will be applied:
1
DEFAULT_TRANSPORTS: ["polling", "websocket", "webtransport"]
In the config/middlewares.js
file either replace 'strapi::security'
with a middleware object (see the example below) or update your existing configuration accordingly.
1. Ensure that contentSecurityPolicy.directives.connect-src
array includes "ws:"
and "wss:"
.
2. Rebuild Strapi and test record locking features.
3. You should not encounter any Content Security Policy
errors in the console.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
module.exports = [
'strapi::errors',
{
name: "strapi::security",
config: {
contentSecurityPolicy: {
useDefaults: true,
directives: {
"connect-src": ["'self'", "https:", "ws:", "wss:", "http:"],
"img-src": [
"'self'",
"data:",
"blob:",
],
"media-src": ["'self'", "data:", "blob:"],
upgradeInsecureRequests: null,
},
},
},
},
'strapi::cors', ...
While optional, it is highly recommended to implement this step to prevent Socket.io from falling back to the HTTP protocol and generating the following error in the web console.
Refused to connect to <protocol>://<url> because it does not appear in the connect-src directive of the Content Security Policy
Are any of these features significant to you? Please show your support by giving a thumbs up on the linked issues. This will help us assess their priority on the roadmap.
We manage bugs through GitHub Issues.
If you're interested in helping us, you would be a rock ⭐.
The main star: Martin Čapek https://github.com/martincapek
Developer: Filip Janko https://github.com/fikoun
Maintainer: Ondřej Mikulčík https://github.com/omikulcik
Project owner: Ondřej Janošík
✔️ We offer valuable assistance in developing custom STRAPI, web, and mobile apps to fulfill your requirements and goals..
✔️ With a track record of 100+ projects, our open communication and exceptional project management skills provide us with the necessary tools to get your project across the finish line.
📅 To initiate a discussion about your Strapi project, feel free to reach out to us via email at sales@notum.cz. We're here to assist you!
npm install @notum-cz/strapi-plugin-record-locking
Check out the available plugin resources that will help you to develop your plugin or provider and get it listed on the marketplace.