Nico Hoffmann ෴.
Nico Hoffmann ෴.
@gbdesign2023 The text column not filling with a value is definitely a bug. On the mobile version here I am not so sure. You don't have any column defined as...
Text column showing again in v4.4.0-develop.
Maybe let's take a news perspective her: We always didn't what to do `if (!function_exists())` as it could lead to unwanted consequences with global helpers like e.g. `go()` if any...
Two thoughts maybe: - I'd let the version in index.php take priority over the one in composer.json? - why do you think human error is less a thing for you...
What's about instead of putting it in the extension array, it's rather a new argument in the plugin call?
I was thinking less of one third parameter with additional metadata but making use of named arguments. That way we would still add it as third parameter for backwards compatibility...
My take on "version as new property": https://github.com/getkirby/kirby/compare/v4/develop...v4/enhancement/plugin-version Still not fully sure that composer should overrule the version number that explicitly gets passed as argument to the plugin.
Yes but that's what I mean: shouldn't the version that we explicitly pass to Kirby's method to register a plugin be the truth above all?
I honestly disagree. If I tell Kirby the version of the plugin by passing it explicitly to the register method, that one should have the authority to- not some other...
But why is an arbitrary file like composer.json seen as more important than what the developer explicitly registers the plugin as. We don't do that for other things like the...