Method name must be a string file: strange panel error

The CMS Questions
1

Experiencing an issue that doesn’t seem to have been resolved. As I fill a field in my blueprint, I get the following error in a popup:

Method name must be a string in file: C:\xampp\htdocs\pathfinders.care\panel\app\src\panel\models\page\changes.php on line: 71

After refreshing, I’m thrown on the debug Kirby page:

method name must be a string
method name must be a string2560×1440 212 KB

The whole blueprint:

title:
  en: Home
  fr: Accueil
  nl: Home
pages: false
files: true
fields:
  title:
    label: Title (HTML Title Tag)
    type: text

  meta-desc:
    label: Meta description
    type: textarea
    buttons: false
    minLenght: 155
    maxLenght: 160
    help: Meta description is the text showed in search engine results. Please enter a text between 155 and 160 chars.

  featured-options:
    label: Featured content
    type: headline

  info-featured-content:
    label: Sur le contenu mis en valeur
    type: info
    text: >
      Ces champs sont réservés à mettre en valeur un contenu récent. Qu'il s'agisse d'un article, d'une expo ou d'autre chose, il est possible de faire un lien avec
      ce contenu depuis la page d'accueuil via ce formulaire. Il n'est pas automatique afin de nous laisser plus de souplesse et faire des annonces comme bon nous semble.
      Le bouton ci-dessous permet d'éliminer tous les éléments mis en valeur de la page d'accueuil. Les éléments sont masquables, option par option, afin de faciliter la mise 
      en page des posters et autres images.
    
  show-featured-content:
    label: Show featured content
    type: toggle
    translate: false
    help: N'utiliser que s'il n'y a pas de contenu mis en valeur (N'est pas lisible par les robots ni par les dispositifs pour aveugles.)

  featured-image:
    label: Front page image
    type: image
    translate: false
    width: 1/2

  mask-featured-image:
    label: Mask featured image
    type: toggle
    translate: false
    width: 1/2

  featured-page-link:
    label: Featured page link
    type: page
    translate: false
    width: 1/2

  mask-featured-page-link:
    label: Mask featured page link?
    type: toggle
    translate: false
    width: 1/2

  featured-text-title:
    label: Featured title
    type: text
    width: 1/2

  mask-featured-text-title:
    label: Mask featured title?
    type: toggle
    translate: false
    width: 1/2

  featured-text-subtitle:
    label: featured-subtitle
    type: text
    width: 1/2

  mask-featured-text-subtitle
    label: Mask featured text subtitle?
    type: toggle
    translate: false
    width: 1/2

  featured-dates:
    label: featured-dates
    type: text
    width: 1/2

  mask-featured-dates:
    label: Mask featured dates?
    type: toggle
    translate: false
    width: 1/2
    
  info-featured-content-mask-options:
    label: À propos du contenu mis en valeur
    type: info
    text: >
      Chers Pathfindistes,
      Veuillez noter que, même lorsque le contenu texte est masqué, il convient de remplir les champs demandés dans les trois langues.
      Ceci afin de pouvoir répondre aux normes du web et de permettre aux robots — ainsi qu'aux malvoyants via leur liseuse! de déchiffrer le contenu.
      Merci d'en tenir compte.

After I disconnect from the panel, I can come back to the page for editing but the field is not updated. And the problem shows again. This affects all fields in page. I wish to find a solution for this as the featured content is a crucial element of this website.
I suspected in a first time special chars in info fields to produce the error, but after deleting them all the problem still persists. Other pages also contain help and info fields without experiencing any issue.

2

Do not use dashes in field names, replace with underscores: https://getkirby.com/docs/panel/blueprints/form-fields#field-names

3

I’ll give this solution a try (as for calling them afterwards it’s also more simple an I feel it as more elegant), but I just can’t explain myself why other pages that have dashes in their field names behave normally.

Thank you anyway for taking the time to answer!

Greets,

4

Just spotted the problem: I labelled fields with the same name as the field title.

  featured-dates:
    label: featured-dates
    type: text
    width: 1/2

This also happens with the form

   featured_dates:
    label: featured-dates
    type: text
    width: 1/2

So everything is all right now. Sorry for taking your time with simple labelling mistakes!

5

I just ran into this error. In my case, I did not put a : after the field name. However, fixing this typo alone did not fix the error; I had to log out and back in for it to work.