Nico Hoffmann ෴.
Nico Hoffmann ෴.
@bastianallgeier I think so. I cannot rule out that there are some use cases where we still have a bug, but we'll find these out probably best with users testing...
It's a bit trickier as the app instance can be cloned with new options. In that case, calling `Uuids::enabled()` could return a value that doesn't match the config option anymore...
I am not arguing against it. Just trying to find a good sustainable way as the clone method isn't the only way a new app object with different config option...
@bastianallgeier Not too happy with it either today... do you have any idea where to put it better?
@bastianallgeier Made it a very simple section
@bogdancondorachi Thanks for bringing this up. Your CSS code didn't quite work for me: multi-row layouts were broken and it would still be rather large if a layout column had...
Thanks for reporting this. I have already fixed the API reference links.
@linusrogge You are making a call to `$newPage->update()` which will create a new object (as objects are immutable in Kirby). But you don't continue using the newly created object, but...
My suggestion here: - Change https://github.com/getkirby/kirby/blob/4.4.1/panel/src/components/Sections/ModelsSection.vue#L200 to fall back to `null` instead of `1` so that the default defined by the blueprint `page` option kicks in - Switch from `localStorage`...
@bastianallgeier I think this is caused by the Form/Fields/Field class refactoring now not catching the error anymore inside it classes and turning it into an error field - but bubbling...