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

**URL:** <https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927>\
**Category:** Elements CMS\
**Created:** [July 6, 2026, 5:11pm UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927 "2026-07-06T17:11:53Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![BrettHannam](https://avatars.discourse-cdn.com/v4/letter/b/858c86/32.png) [@BrettHannam](https://forums.realmacsoftware.com/u/BrettHannam)\
**Post date:** [July 6, 2026, 5:11pm UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/1 "2026-07-06T17:11:53Z")

</div>

## **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**

- **Screenshot 1:** Post after the initial save, showing the empty field stored correctly.  

- **Screenshot 2:** Post after the second save, showing the empty field changed to `[]`.  

- **Screenshot 3:** Post after entering text, showing the value stored as an array element.

---

<div class="post-metadata">

**Author:** ![Pegasus](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/pegasus/32/25035_2.png) [@Pegasus](https://forums.realmacsoftware.com/u/Pegasus)\
**Post date:** [July 7, 2026, 5:51am UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/2 "2026-07-07T05:51:35Z")

</div>

The first rule in the elements CMS Club is:

Put your data fields in the frontmatter in quotation marks.

This applies especially to:

```auto
title: "Bracket Test 4"
headline: "Headline"
sub_title: "Subtitle"

```

If you want to output `headline` and `sub_title` with brackets, write them like this:

```auto
headline: "[Headline]"
sub_title: "[Subtitle]"

```

The use of brackets only works in this way for:

```auto
tags
categories

```

---

<div class="post-metadata">

**Author:** ![rbhannam](https://avatars.discourse-cdn.com/v4/letter/r/41988e/32.png) [@rbhannam](https://forums.realmacsoftware.com/u/rbhannam)\
**Post date:** [July 7, 2026, 6:25am UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/3 "2026-07-07T06:25:45Z")

</div>

Thanks, but this is the action of the CMS editor, not me! The bug is that the editor adds the spurious brackets. It also decides when to add quotation marks (when there are characters that need to be escaped) and also, on occasion, removes quotation marks that it assesses are unnecessary.

---

<div class="post-metadata">

**Author:** ![Pegasus](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/pegasus/32/25035_2.png) [@Pegasus](https://forums.realmacsoftware.com/u/Pegasus)\
**Post date:** [July 7, 2026, 6:36am UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/4 "2026-07-07T06:36:41Z")

</div>

Sorry, my mistake. I skimmed through it a bit too quickly.

In that case, it looks like there are indeed a few more issues with the CMS online editor. I actually don’t use it myself.

We should probably bring this post to the attention of @Ben or @Dan, so hopefully you can either get a bug fix soon or at least some information about a useful workaround or similar solution.

---

<div class="post-metadata">

**Author:** ![rbhannam](https://avatars.discourse-cdn.com/v4/letter/r/41988e/32.png) [@rbhannam](https://forums.realmacsoftware.com/u/rbhannam)\
**Post date:** [July 7, 2026, 6:51am UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/5 "2026-07-07T06:51:11Z")

</div>

No problem! Thanks for taking the time to reply!

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [July 8, 2026, 7:09am UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/6 "2026-07-08T07:09:57Z")

</div>

Hi @BrettHannam

Thanks for the detailed report, that really helps. I’m going to look at this issue asap, hopefully we can get it fixed in time for the next update.

---

<div class="post-metadata">

**Author:** ![rbhannam](https://avatars.discourse-cdn.com/v4/letter/r/41988e/32.png) [@rbhannam](https://forums.realmacsoftware.com/u/rbhannam)\
**Post date:** [July 8, 2026, 7:24am UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/7 "2026-07-08T07:24:43Z")

</div>

Thanks @Ben - that’s very helpful.

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [July 8, 2026, 11:42am UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/8 "2026-07-08T11:42:18Z")

</div>

found the issue, this will be fixed in the next build 🙂

---

<div class="post-metadata">

**Author:** ![BrettHannam](https://avatars.discourse-cdn.com/v4/letter/b/858c86/32.png) [@BrettHannam](https://forums.realmacsoftware.com/u/BrettHannam)\
**Post date:** [July 8, 2026, 3:47pm UTC](https://forums.realmacsoftware.com/t/possible-bug-in-cms-online-editor-when-empty-text-fields-are-saved/56927/9 "2026-07-08T15:47:45Z")

</div>

Terrific! Thank you very much indeed.
