Panel doesn't use the right blueprint for creating a new article

Kirby 3 Issues 🐛
1

I have created the following blueprints based and modified on the great blog recipe:

/blueprints/pages/blog.yml

title: Blog
icon: layers

columns:
  left:
    width: 1/4
    sections:
      meta:
        type: fields
        fields:
          cover:
            label: Titelbild
            type: files
            max: 1
            multiple: false
            layout: cards
            query: page.images
            image:
              cover: true
              ratio: 16/9
  leftright:
    width: 1/4
    sections:
      drafts:
        extends: sections/articles
        headline: Drafts
        status: draft

      unlisted:
        extends: sections/articles
        headline: In Review
        status: unlisted

  right:
    width: 1/2
    sections:
      listed:
        extends: sections/articles
        headline: Published
        status: listed

/blueprints/sections/articles.yml

type: pages
headline: Articles
info: "{{ page.date.toDate('%d.%m.%Y') }}"
template: article
empty: No articles yet
sortBy: date desc
layout: cardlets

/blueprints/pages/article.yml

title: Article
num: '{{ page.date.toDate("%Y%m%d") }}'
icon: book

status:
  draft:
    label: Draft
    text: The article is still in draft mode. It can only be seen by editors with panel access.
  unlisted:
    label: In Review
    text: The article is online and can be visited with the direct URL. The team must still give the final go to publish it.
  listed:
    label: Published
    text: The article is online and listed in the blog

columns:
  main:
    width: 2/3
    fields:
      author:
        type: users
        label: Autor
        width: 1/2
      modified:
        type: info 
        label: Letzte Änderung
        theme: none
        text: "{{ page.modified('%d.%m.%Y %H:%M') }}"
        width: 1/2
        align: right
      intro: 
        type: text
        label: Intro
      text: 
        type: blocks
        label: Artikel
        autofocus: true
        default:
          - type: text

  sidebar:
    width: 1/3
    sections:
      meta:
        type: fields
        fields:
          date:
            type: date
            time: true
            default: now
            label: Datum
          autopublish:
            label: Autopublish
            type: date
            time: true
            default: now
          cover:
            label: Artikelbild
            type: files
            max: 1
            multiple: false
            layout: cards
            query: page.images
            image:
              cover: true
              ratio: 16/9
          caption:
            type: text
            label: Bildunterschrift
          featured:
            type: toggle
          tags:
            type: tags
            options: query
            query: site.index.pluck("tags", ",", true)
          taglist:
            type: info
            theme: none
            text: "{{ page.taglist }}"
      matomo:
        type: matomo-page
        overview: true
      komments:
        extends: sections/komments

Whenever I now click on the “Add/Create” button on the blog page I don’t see the article page blueprint but the default page blueprint instead.
Why is that and how can I solve it? I am running Kirby 3.6.0.alpha-4 at the moment.
Thanks in advance.

2

Does the blog page actually use the blog blueprint?

3

Yes and if I create a new page there the URL changes to /panel/pages/blog+titleofmynewpost

4

Hm, there’s nothing wrong with your template and in my quick test (just to make sure I didn’t overlook something), when I create a blog page with the blog blueprint then the only children I can create are article type children.

5

It worked some days ago, strange. I only changed the order to a vertical layout instead of the default horizontal one. I have sent you a link with a test environment. Would you be able to give it a try there?

6

See answer in PM

1 Like
7
8

The Matomo error is caused by a JS error in index.js in the komments plugin. If you disable that plugin, the Matomo tab will show up correctly. Always watch your browser console for errors if stuff like that happens.

1 Like
9

Great, thanks for the hint.
I created an issue on GitHub about it: Not compatible with kirby-matomo plugin · Issue #22 · mauricerenck/komments · GitHub
@mauricehh

10

Thank you for the hint. I answered on GitHub. In general: I am working on compatibility for Kirby 3.6, but this will still take some time, because I have to change a lot for the panel part.

1 Like