Closed neildaniels closed 3 years ago
When #2514 was solved, I saw that this issue was solved (At least there is no error in my tests.). Is it true @neildaniels ?
I don't think that's necessarily true, unless duplicating a page and changing the slug share the same code.
I also get an error if it is related to the page.
To Reproduce:
The source of the error is: if there is no page id (copied another page or files of page id) in the lock file, kirby thinks the page has no lock file and an error occurs while moving.
I made several tests and improvements. I have solved the lock files related to the file but it seems very difficult to confirm the old data on the pages copied by manual 🤔
We've experienced this issue on 3.5.1
. It was reported by our client who said that they "changed the page title" before it happened. I was not able to reproduce it, however. I tried to reproduce it via the 5 steps above but no issues here...
As a nice side effect of our Fiber architecture, this is now solved.
Describe the bug
When a page's content folder has a
.lock
file that isn't actually for the current page, attempting to change the slug of the page cause the server the become unresponsive and timeout.This "irrelevant"
.lock
file can occur by at least 3 ways:To Reproduce
Steps to reproduce the behavior:
.lock
file that isn't actually relevant for the page (choose one of the ways above)Expected behavior
Panel refreshes to the new page.
Screenshots
Kirby Version
3.3.3
and3.3.5-rc.1
Desktop (please complete the following information):
Additional context
This is on a multi-lang setup.