---
title: "Content Editing & UI Workflows"
description: "Resolve common CMS UI issues, including versioning behavior, concurrent edit conflicts, drag-and-drop restrictions, and date field resets."
url: "https://www.contentstack.com/docs/headless-cms/content-editing-ui-workflows"
product: "Contentstack"
doc_type: "guide"
audience:
  - developers
  - admins
version: "current"
last_updated: "2026-04-22"
---

# Content Editing & UI Workflows

## 1\. Cannot Modify a Historical Entry Version (Versioning Behavior)

When attempting to update a previously saved version of an entry, the system does not allow direct modification of that historical version. Any changes made through the CMS UI or Content Management API result in the creation of a new latest version instead of altering the selected older version.

**Root Cause**

Contentstack enforces immutable versioning by design.

*   Each time an entry is updated, a new version is created.
*   Historical versions are retained as read-only snapshots for audit and rollback purposes.
*   The Content Management API (CMA) and CMS UI only allow updates to the current/latest entry state.
*   Older versions cannot be edited directly to preserve content integrity and version history accuracy.

This behavior ensures traceability, audit compliance, and content recovery safety.

**Resolution**

Do not attempt to edit historical versions directly. If content from an older version is required:

*   Use the **Version History** feature in the CMS UI.
*   Select the required version and choose **Restore** (this creates a new latest version based on that snapshot).

**For API-based workflows:**

*   Retrieve the latest entry version via CMA.
*   Apply updates to the current version only.
*   Allow the system to generate the next version automatically.

Check the entry version number before making changes and perform an update via CMS UI or CMA.

**Confirm:**

*   A new version number is generated.
*   The previous historical version remains unchanged.
*   The updated content exists only in the new latest version.

* * *

## 2\. Entry Version Warning Showing Older Version

Warnings such as “Published before localization” or indicators of older versions appear even after publishing.

**Root Cause**

A Release stores a snapshot of specific entry versions. Publishing a newer version outside the Release does not automatically update the Release reference.

**Resolution**

1.  Open the affected Release.
2.  Update the entries to their latest versions.
3.  Deploy.

Open the Release and confirm that all referenced entries use the latest version and that the warning is no longer displayed.

* * *

## 3\. Managing Concurrent Entry Edits Without Merge Functionality

Multiple contributors working on the same entry may overwrite each other's changes because the platform does not support merging entry versions. This prevents the simultaneous consolidation of updates from different users into a single version.

**Root Cause**

The platform's versioning architecture is designed for linear tracking and does not include a native merge feature.

**Resolution**

1.  Use Workflows to manage the progression of entry edits and handoffs between users.
2.  Add Field Notes to provide context or instructions to other contributors.
3.  Coordinate with team members to ensure only one user is editing a specific entry version at a time.

After implementing a workflow-based editing process, check the version history of an entry. If updates are saved sequentially without data loss from overwrites, the coordination strategy is effective.

* * *

## 4\. Cross-Section Card Drag-and-Drop Not Supported in CMS UI

Reordering card components in the CMS UI may be restricted to the section in which they are placed. This prevents moving individual cards directly from one section to another via drag-and-drop.

**Root Cause**

The current drag-and-drop functionality only supports reordering elements within a single section.

**Resolution**

1.  Move cards within their specific section using the drag handles.
2.  Reorder entire sections if the project requires moving a group of components.
3.  Refer to the product team to submit a feature enhancement request for cross-section dragging.

After attempting to drag a card within its parent section, check the vertical order. If the card moves within its section but cannot be dropped into a different section, the behavior is expected.

* * *

## 5\. Date Field Time Settings Reset During Entry Save

Saving an entry in the CMS may cause the time settings in a date field to reset or shift from the originally entered values. This prevents maintaining a fixed time independent of the user's local timezone.

**Root Cause**

The date field automatically adjusts its value to follow the current local timezone of the user performing the save operation.

**Resolution**

1.  Verify the local timezone settings of the user account performing the entry save.
2.  Ensure team members are aware that saved times reflect the local timezone of the last editor.
3.  Refer to upcoming product enhancements for improved handling of fixed timezone settings.

After entering a specific time and saving the entry, check the date field value. If the time displays an adjustment consistent with the local timezone, the behavior is operating as currently designed.