What to read about building a multi-user data editing application?

Question

JavaScript

Good afternoon. We make a web application, something like CRM. There is a company in which, for example, 10 managers. The company has a website with a huge form. WordPress site, form - gravity forms. The client fills out the form and the application comes to the site. And there is a second application site on Laravel + JS, where the data of these completed forms is loaded using the Gravity forms API. This site, in fact, is empty - in the sense that the markup (almost all) and data substitution are generated in JS based on the received endpoint. Roughly speaking, all this data is drawn up in a table. The designated managers can edit and save this table - then the data on the server is overwritten. Moreover, you can edit one single record, or you can select several or all at once - and change this or that field for several records at once.
The problem is this: how to prevent data from being overwritten if, for example, two or more managers accidentally work on the same form? What can you read about this, in which direction at least google?
I hope I have clearly formulated the situation and the problem, but if anything, I can clarify something.

Answer 1

Read about co-authoring. ( the first article that came across )
If it's difficult, and the company is small, then make notifications, such as "this file is being edited by Anton Borisov"
or
"while you were editing, this file was changed by Vasily Ivanov
what to do: overwrite, do not save, see the diff"

Answer 2

What can you read about this, in which direction at least google?

The main options, on a vskidka, I can offer the following:
1. When editing a record (a string or any other entity, at your discretion), a label is set on it, something like this: "edited by such and such a user", the corresponding label is deleted upon completion of editing. Thus it works in some CMS.
2. You can come up with some kind of system based on the WebSocket protocol, I think services like GoogleDocs or Trello (allowing several users to edit one document at once) work on its basis, this will at least allow all users to see data updates almost in real time
3. You can store all versions of the data, and then do something with them... I do not fully understand what your final requirements are, perhaps this option will not work.

Answer 3

when saving the record, update the timestamp.
if the labels of the record in the database and the record from the user who edited it do not match, then the output is that the row has already been edited. further, depending on the required logic.

Answer 4

Based on the error message, it is in the config.php file on the 9th line. On your screen, another file. Attach the correct one.
On the 9th 'name' = 'blog'
Correct: 'name' => 'blog'

Answer 5

Сравните с тем, как написаны строки 6-8 и с тем, как определена 9я. очевидно, что-то пропущено