Plugin defined in blueprint not available


I still have a problem with defining a blueprint in my plugin. When creating a new page in the panel, my page blueprint doesn’t appear in the dropdown list.

I did this in the index.php:

    'blueprints' => [
            'pages/podcasterfeed' => __DIR__ . '/blueprints/pages/podcasterfeed.yml'

Under blueprints/pages/ there is the podcasterfeed.yml which is pretty long, so I don’t want to post it here, but you can find it here:

The blueprint works, I created a new page and set the filename of the markdown to in the terminal. The page appears in the panel, I can open, edit and save it.

But for the users of my plugin, I would like to skip that extra step of creating the page outside of the panel or renaming the file etc. they should be able to select it from the template selection dropdown when creating a page.

Is there anything I am doing wrong, so the template isn’t available?

I think you have to list the available blueprints in a page blueprint. What happens if you list the blueprint thats buried in your plugin in the blue print options? My point is i dont think they show up automatically. So in your default page blue print in the normal blueprint folder (ie… not in your plugin) have you tried declaring it like this? I’m not 100% sure, but i think the plugin blueprint folder gets merged with the normal blueprint folder, so treat them as if they were in the normal folder and explicitly declare them…

title: Default

    - thenameoftheblueprintinyourplugin

You don’t have to declare it in the changeTemplateoption, but rather the blueprint/template in a pages section has to be set to display/create pages with the template:

    type: pages
    headline: My podcast pages
      - podcasterfeed

Okay, so if I understand this right, the users of my plugin have to do so, in order to be able to use my blueprint?

Normally, if you do not limit templates, they should all be available automatically. Let me test this.

I have no limits set up locally and I see alle templates, but not the one of my plugin.

Yes, I can reproduce that. That sounds like a bug. It does show up if you set the create option

    type: pages
    create: podcasterfeed

But it should show automatically.

Okay, that’s good to know, thank you for your help!
Should I create an issue?

Yes, please.


This should now be fixed on the develop branch and will be in 3.1.3.

1 Like

This thread helped me realize I needed to prepend “pages/” to the blueprint definition in a Kirby plugin. Could I open a pull request to update the Plugin Basics documentation on this?

It’s documented in the extension: Blueprints | Kirby CMS

1 Like