context: I’m have written some plugins which extend form and email capabilites of grav. therefore I need to extend an blueprint for the admin view several times (one plugin is for email encryption, one is for handling attachments and last but not least there are some theme specific fields).
problem: the blueprint form.yaml doesn’t exist by default in admin or in any other core extension/plugin and so (if I’m not mistaken) grav/admin plugin picks default.yaml to render backend view of form page type.
I know I can extend blueprints by
extends@: parent@ what will extend the blueprint of the same name. But as there is no form.yaml by default, one of my form.yaml files needs to extend default.yaml via
extends@: - type: default context: blueprints://pages
otherwise I was unable to get it to work
so there needs to be an order, which actually defeats the meaning of having independent plugins.
Do I miss something here? Is there a workaround for this? Or do I need to “force” any future plugin users to copy a “default” form.yaml into their system / blueprints / pages folder?
I would be very grateful for any suggestions or hints.
Thanks everyone and have a nice day