Bastian Allgeier

I've added this to the 3.7 project. Let's see what happens if I close this. I hope it stays in the project.

There's finally a draft for a fix: https://github.com/getkirby/kirby/pull/3850 I'm really sorry that it took so long.

@tinus what does get stored in your last example with the non-existing page?

Yes, that's the expected behaviour of the pages field. It simply ignores invalid entries. When you rely on validation to throw errors about invalid pages, I totally see why this...

@afbora I consider this an expected behaviour. The text blocks expects a writer field. But we need to document it and/or add error handling if another field type is chosen.

@afbora that's a fantastic idea!

I agree. We need to move more of those page-specific settings into the page blueprint instead of sections. This will make sections a lot less complicated and weird.

Yep, it's pretty difficult to get this right in the UI, but I think at least it could be correct in the backend. Let's say we mix sorting numbers and...

Hm, changeNum and changeSort should indeed be protected by permissions. We need to check this.

✅