In a project with many concurrent users I noticed how confusing unsaved module changes can get: someone edits a module, leaves without saving, and the next person sees those edits as their own unsaved changes, free to publish or discard them without knowing.
Editing a module now locks the whole page with Kirby's native lock. Everyone else sees who is working on it, and once the lock expires, the page names whoever left unsaved changes behind.
Also new
$page->createModule() creates a real module from code, stored on disk and editable in the Panel. Useful for imports, seeding and migrations. Thanks to @nilshoerrmann for the idea!
Fixes
- Rapid edits can no longer save out of order
composer.jsonnow declares the Kirby 5 requirement
Contributors
nilshoerrmann