Adding sub content: Nesting level too deep - recursive dependency?

Hello I am building a system where I have a contenten(contents) folder within my content folder.
This is a folder that should contain my main contenttypes like blog, recepten(recipes) and diensten(services).

In my panel it looks like this:
contentscr1

When I add 1 contenttype(page) nothing goes wrong:
addblog

I can also add my blog messages withing this blog contenttype:

It gets stored like this:
bestandslayout

When I try to add a second contenttype to my contenten map I get the error:
eroor

The file structure of the content folder now looks like this:
bestandslayout2

Does anyone know why this error occurs and/or how to fix it ?

Could you post your blueprints, please?

Contenten/content (contents) blueprints:
contentblprnt


sectioncontenten

Berichten/bericht (Blog) blueprints:


berichtenblprnt
sectionberichten

Recepten/recept (recipes) blueprints:


receptenblprnt
sectionrecepten

Hm, there is a content blueprint and a contenten blueprint. What is the content one doing there?

For now nothing but I tend to always make a single and a archive blueprint for everything in case I need to use it in the future

Ok, unfortunately I can’t test this with your code images, please always post code as code.

To display code correctly, wrap it within three backticks on a separate line before and after the code snippet.

title: Contenten
icon: 🖼

columns:
  - width: 1/3
    sections:
      berichten:
        headline: Foo Pages
        type: pagesdisplay
        query: site.index.filterBy(title, *=, msg_)




  - width: 1/3
    sections:
      blog_categorien:
        headline: -
        type: pages
        templates: blog_categorien


  - width: 1/3
    sections:
      doelgroep_categorien:
        headline: -
        type: pages
        templates: doelgroep_categorien

type: pages
headline: Contenten
parent: site.find("contenten")
info: "{{ page.date.toDate('d.m.Y') }}"
templates: 
  - berichten
  - recepten
  - diensten
empty: No contenten yet
sortBy: date desc

title: Bericht
num: date
icon: 📖

status:
  draft:
    label: Draft
    text: The note is still in draft mode. It can only be seen by editors with panel access.
  unlisted:
    label: In Review
    text: The note 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 note is online and listed in the blog

columns:
  - width: 1/2
    fields:
      text:
        label: Beschrijving
        type: textarea
        size: small
      author:
        type: users
        multiple: true
      

  - width: 1/2
    sections:
      info:
        type: info
        headline: Attention
        theme: negative
        text: |
          Check alsjeblieft goed of je image de goede grootte heeft
          voordat je hem gebruikt als cover.
      cover:
        type: files
        multiple: false

title: Berichten
icon: 🖼

columns:
  - width: 1/2
    sections:
      drafts:
        extends: sections/berichten
        headline: Drafts
        status: draft

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

  - width: 1/2
    sections:
      listed:
        extends: sections/berichten
        headline: Published
        status: listed

type: pages
headline: Berichten
parent: site.find("berichten")
info: "{{ page.date.toDate('d.m.Y') }}"
template: bericht
empty: No berichten yet
sortBy: date desc

title: Recept
num: date
icon: 📖

status:
  draft:
    label: Draft
    text: The note is still in draft mode. It can only be seen by editors with panel access.
  unlisted:
    label: In Review
    text: The note 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 note is online and listed in the blog

columns:
  - width: 1/2
    fields:
      text:
        label: Beschrijving
        type: textarea
        size: small
      author:
        type: users
        multiple: true
      

  - width: 1/2
    sections:
      info:
        type: info
        headline: Attention
        theme: negative
        text: |
          Check alsjeblieft goed of je image de goede grootte heeft
          voordat je hem gebruikt als cover.
      cover:
        type: files
        multiple: false

title: Recepten
icon: 🖼

columns:
  - width: 1/2
    sections:
      drafts:
        extends: sections/recepten
        headline: Drafts
        status: draft

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

  - width: 1/2
    sections:
      listed:
        extends: sections/recepten
        headline: Published
        status: listed

type: pages
headline: Recepten
parent: site.find("recepten")
info: "{{ page.date.toDate('d.m.Y') }}"
template: recept
empty: No recepten yet
sortBy: date desc

I still don’t get it. With the contenten blueprint, I can’t create the blog page at all… And the contenten section is only used in the content blueprint, not in the contenten one.

The content blueprint is used for a view of the contenttypes: blog, recepten etc. This view is accessed by clicking on the headline of the section in my site.yml:

- width: 1/4
   sections:
      contents: sections/contenten

The problem is that you are sorting your pages by date in the section/contenten.yml although those pages don’t have a date field to sort by.

Okay thanks,

What other way of sorting do you suggest?

For this purpose the default sorting scheme by numbers is the most appropriate, I think.

You don’t have to set anything for that.

Okay thank you very much

type: pages
headline: Contenten
parent: site.find("contenten")
info: "{{ page.date.toDate('d.m.Y') }}"
templates:
  - berichten
  - recepten
  - diensten
empty: No contenten yet

without the sorting bit is sufficient. You can then sort listed pages manually.

:ok_hand: