In Kirby2, I have some plugins that provide custom blueprints. I would like to rework these plugins for Kirby3. Unfortunately the blueprints defined in a plugin do not appear in the list of available blueprints when adding new pages.
To break its down, I created a simple test plugin. So the following in a clean installation of plainkit doesn’t work as expected:
Thanks! Obviously, I had to allow site/pages using the blueprint.
But it seems, the blueprint is not taken into account correctly.
I enriched my test blueprint as follow:
Adding a page based on this blueprint leads to a form with one textarea field, only. The file my-blueprint-from-file.txt appears in the content folder but the file content does not correspond to the blueprint:
That would be nice. Could you post the link here? I also have this problem for some time. I guess I cannot link to my slack-msg from here, so I might add a sample of how I did it in my plugin to your issue, maybe that helps solving it.
I can’t reproduce that the blueprint doesn’t show up on the list of available templates, and I wasn’t using the create attribute to make it appear. The thing I can reproduce is that the fields don’t appear and no matter if I use a preset or not, all I ever get, is a default page preset layout, while the text file gets the correct blueprint name. Very weird.
I just copied my plugins blueprint to the kirby-blueprint dir and renamed it. Doing so it appears in the list of blueprints within the panel, but as you mentioned, whativer I do, I get the default-blueprint.