Content disappears when saved

Kirby 3 Solved ✅
1

Hello,
First, thanks for this beautiful CMS.

I created a blueprint for my long about page, with tabs for each section. In the panel, the blueprint is displayed as expected, but when I save my modifications, everything disappears. I checked the .txt file and nothing is saved here. I tried to write directly in the .txt file, it is saved but nothing is displayed in the panel.
For the other blueprint I created (project, a simpler one without tab), everything works fine. I can modify content in the .txt file and in the panel and it saves as expected.

I’m working locally with WAMP, it uses PHP 7.2.10. This is the last version of Kirby, 3.2.5.

I have no Multi-language nor plugins for now.

Also, I didn’t modify for now the templates, so there is nothing on the pages right now, even with content. I think I can work directly with the .txt for this template, but I hope to do this in the panel. Can you help me? Thanks!

2

Sounds like a session issue… have you tried another browser or clearing the cache?

Perhaps there is something about the content that it does not like. You say it isn’t multi language, but is it in a language with special characters? You could try to add the content a bit at a time to see what it doesn’t like.

It could also be that as you have manually edited, the content file might not be in the right format now. Does it work if you delete the page and only work in the panel?

3

Could you please post your blueprint?

4

Thanks for the quick answers.
Here is my blueprint:

# Each page blueprint must have a title, the title may be different from the file name
title: Qui suis-je ?

# Each page can have an icon that is shown in page listings when no preview image is available.
icon: 👀

tabs:

  quisuisje:

    label: Qui suis-je ? 👀
    icon: 👀

    columns:
      - width: 1/3
        fields:
          quisuisje-photo:
            label: Photo
            type: files
          quisuisje-button:
            label: Texte du bouton
            type: text
          quisuisje-link:
            label: Lien du bouton
            type: url
      - width: 2/3
        fields:
          quisuisje-content:
            label: Contenu
            type: textarea
            size: huge

  parcours:
    label: Mon parcours 🎓
    icon: 🎓
    columns:
      - width: 1/3
        fields:
            parcours-cv:
              label: Mini-CV
              type: textarea
            parcours-button:
              label: Bouton
              type: text
            parcours-link:
              label: Lien du bouton
              type: url
      - width: 2/3
        fields:
          parcours-content:
            label: Contenu
            type: textarea
            size: huge

  valeurs:
    label: Mes valeurs 🙏🏽
    icon: 🙏🏽
    columns:
      - width: 1/3
        fields:
          valeurs-button:
            label: Bouton
            type: text
          valeurs-link:
            label: Lien du bouton
            type: url
      - width: 2/3
        fields:
          valeurs-content:
            label: Contenu
            type: textarea
            size: huge

  wishlist:
    label: Ma wishlist 🎁
    icon: 🎁
    columns:
      - width: 1/3
        fields:
          wishlist-button:
            label: Bouton
            type: text
          wishlist-link:
            label: Lien du bouton
            type: url
      - width: 2/3
        fields:
          wishlist-content:
            label: Contenu
            type: textarea
            size: huge

Yep, tried Firefox and Chrome and it still doesn’t work.

I tried with only a few basic characters, nothing changes.

I deleted several times the page and created a new one without result.

5

Please remove the dashes from your field names, they are not allowed: https://getkirby.com/docs/guide/blueprints/fields#naming-fields

3 Likes
6

Oh thank you, I feel dumb!
Do you know if field names support camelCase?

7

Yes, camelCase shouldn’t be a problem. I personally prefer camelCase to underscores. camelCase is not stored in the text files, though.

So your field camelCase in blueprint becomes Camelcase in your content file, i.e. case is ignored, also when calling these fields in your templates.