Editing of File contents not possible when page name is "files"

[tobimori]

Description

When the page name is files, and you're trying to edit a files' contents (e.g. an Alt text field) the lock panel request will fail and forbid any editing.

{
    "status": "error",
    "message": "Invalid model type: .",
    "code": 400,
    "exception": "Kirby\\Exception\\InvalidArgumentException",
    "key": "error.invalidArgument",
    "file": "../kirby/src/Cms/Find.php",
    "line": 126,
    "details": [],
    "route": "(.*)/lock"
}

Expected behavior
File contents editing world work normally as when the page name isn't files.

Screenshots

To reproduce

1. Create a page with the slug files.
2. Upload a file with custom blueprint that has fields.
3. Open the file and try to edit a field

Your setup

Kirby Version 4.0.0-alpha.2 / 3.9.4

[distantnative]

This is new with v4?

[tobimori]

This is new with v4?

You're right, it's also happening with 3.9.4, I just haven't noticed it yet because the lock calls where less frequent on another site.

[lukasbestle]

Looks like the wrong API route matches.

[distantnative]

@lukasbestle I think we only could solve this when moving to Panel urls based on UUIDs

[lukasbestle]

Would be good to know which exact route causes this, so far it's only an assumption from me reading the issue. Because we separate page levels with + in API URLs, I feel like there should be a way to differentiate between "page called files" and "files of whatever page".

[bastianallgeier]

@distantnative as soon as we move to UUIDs for panel URLs, we can no longer switch them off.

[distantnative]

@bastianallgeier true

@lukasbestle so it's a call to the API such as http://sandbox.test/api/pages/files/files/team.jpg/lock, I would think all 5 lock API endpoints are affected as they all do pretty much the same with the path.