New Edit mode has problems with specific field types

[jcastro-dotcms]

Problem Statement

The new Edit Content mode exhibits two distinct bugs when working with content types that include specific field types. Both bugs affect the ability to correctly create and persist contentlet data. We've detected problems with three Field Types so far, but there might be more:

Bug 1 — Key/Value field: key input is split into individual characters on first entry

When a content type includes a Key/Value field and the user adds the first key/value pair, the UI splits the typed key text into its individual characters, creating one entry per character instead of treating the full string as a single key. For example, typing mykey as the key results in 5 separate entries: m, y, k, e, y. This behavior only occurs on the first entry; subsequent entries work as expected.

Bug 2 — Date and Date and Time fields: values are not persisted after publishing

When a content type includes a Date or Date and Time field, values entered for those fields are lost after the contentlet is published — the fields appear empty when the contentlet is reopened. Each field type is independently affected (does not require both to be present). Saving as draft (without publishing) works correctly.

Impact: Content editors cannot reliably create contentlets with Key/Value or Date/Date and Time fields in the new edit mode.

---

Steps to Reproduce

Note: A sample Content Type bundle is attached to this issue containing the Content Type named AAA with numerous field types. Import it via Site Browser → Push Publishing → Import Bundle before following these steps.

Bug 1 — Key/Value character splitting:

1. Import the attached bundle to get the sample content type.
2. Go to Content → New Content and select the sample content type.
3. Navigate to the Key/Value field.
4. Add the first entry: type any text as the key (e.g., mykey) and a value (e.g., myvalue), then confirm.
5. Observed: The key is split into individual characters — m, y, k, e, y — each appearing as a separate entry.
6. Expected: The full string mykey appears as a single key entry.

Bug 2 — Date / Date and Time not persisted:

1. Import the attached bundle to get the sample content type.
2. Go to Content → New Content and select the sample content type.
3. Set a value for the Date field (e.g., 2025-01-15).
4. Set a value for the Date and Time field (e.g., 2025-01-15 10:30).
5. Click Publish.
6. Reopen the published contentlet.
7. Observed: Both the Date and the Date and Time fields are empty.
8. Expected: Both fields retain the values entered before publishing.

---

Acceptance Criteria

Bug 1 — Key/Value field (character splitting)

• When typing a key string (e.g., mykey) for the first Key/Value entry and confirming it, the entire string appears as one entry — not split into individual characters.
• Subsequent Key/Value entries (second and beyond) also save the full key text without character splitting.
• The original bug scenario (first entry splits mykey into m, y, k, e, y rows) no longer reproduces.

Bug 2 — Date / Date and Time persistence

• A content type with only a Date field: after setting a value and publishing, the Date field retains its value when the contentlet is reopened.
• A content type with only a Date and Time field: after setting a value and publishing, the Date and Time field retains its value when the contentlet is reopened.
• Saving a contentlet as draft (without publishing) continues to work correctly for Date and Date and Time fields.
• The original bug scenario (Date or Date and Time field appears empty after publishing) no longer reproduces.

---

dotCMS Version

Latest from main branch

---

Severity

High - Major functionality broken

---

Links

NA

[github-actions]

PRs linked to this issue

• feat(e2e): add KeyValueField tests by @nicobytes