Bundle as plugin when Kirby 2.3 is released

[jenstornell]

No description provided.

[jenstornell]

2.3 has been released. :)

[afbora]

What can i do for this? 😄

[dweidner]

One think could be to add a package.json file to allow installing your field via the new Kirby CLI. See the following page for more details: https://github.com/getkirby/cli#kirby-plugininstall

[jenstornell]

https://getkirby.com/docs/developer-guide/plugins/registry

[dweidner]

Well the extension registry would only make sense, if this "plugin" provides more functionality than a panel field, for example providing additional field methods. Users are supposed to install the files into site/fields and not into site/plugins. There is no need to use the extension registry here.

[jenstornell]

I quote one of the crew members:

https://forum.getkirby.com/t/multiselect-field/1213/19

With the new registry in Kirby 2.3, I believe all third-party elements like fields, snippets, blueprints etc. should also be delivered wrapped as a plugin. This enables us to keep only custom elements that are rather specific to the project in site/fields, site/tags etc.

[afbora]

@dweidner @jenstornell Added 72ce2ee

[dweidner]

Thank you for the reference, @jenstornell. I have to disagree though. I would expect fields to be in the site/fields folder regardless of the author of a field/plugin.

[afbora]

Specified as type: kirby-field in package.json

[jenstornell]

It seems like you have @dweidner on your side as he setup the package.json as field. I have not changed my mind about it tho.

[dweidner]

I think we should move the discussion to another issue: https://github.com/distantnative/field-multiselect/issues/18

[malvese]

When I try to install the plugin with Kirby's CLI I get this error:
[RuntimeException] Invalid Kirby Plugin Type

[afbora]

@malvese Could you try with downloaded new version?

[malvese]

@afbora Sorry for the delay! I just tried and it now works fine :) Thanks!