Possible Bug in CMS Online Editor When Empty Text Fields Are Saved

Elements CMS
1

Description

When creating a new post that contains front matter fields of type TEXT, leaving one of these fields empty and saving the post multiple times causes the field value to change unexpectedly.

The first save behaves correctly. However, after the post is saved a second time, the previously empty field is written as [] instead of remaining empty.

This creates an empty array. When the field is rendered on the website, the value is displayed as “Array” rather than as an empty string.

If text is subsequently entered into the field, it is stored as an element within the array instead of as a normal text value.

Expected behaviour

  • Saving a post with an empty TEXT field should leave the field empty.
  • Saving the post multiple times should not change the field type or value.
  • If text is entered later, it should be stored as a normal text string.

Actual behaviour

  • After the post is saved a second time, an empty TEXT field is changed to [].
  • If text is later entered into the field, it is stored as an array element rather than as plain text.
  • When rendered on the website, the field displays “Array” instead of the expected text.

Steps to reproduce

  1. Create a new post.
  2. Leave a TEXT field empty.
  3. Save the post.
  4. Make any change to the post (or simply save it again).
  5. Save the post a second time.
  6. Observe that the previously empty field now contains [].
  7. Enter text into that field and save again.
  8. Observe that the text is stored as an array element rather than as plain text.

File Contents