Skip to content
D
Documentation

Validating Saving and Reviewing Content Changes

10 min readUpdated

Preparing the editor before you save

Before you click Save, take a moment to review exactly what you changed in the content editor. In Sherkety ERP & Website Platform, this usually means checking the text fields, language-specific fields, and any structured content blocks you edited earlier. If you worked on repeated items or grouped fields, use Editing Structured Content and Repeating Items to confirm that each item is complete before you save.

Focus first on fields that are most likely to block saving. Look for visible labels such as Title, Summary, Body, Slug, and any settings or metadata fields shown in the editor panel. If a field is required, the editor may mark it clearly before you save. Review every field that has been changed, especially if the save button has become active after your edits.

Pay attention to visual signs that the page still has unsaved work. Depending on the screen, you may notice:

  • changed-field highlighting
  • a save button that becomes enabled only after edits
  • an unsaved changes warning when moving away
  • inline notices beside fields that still need attention

Also check whether the fields you are editing are available to your role. In Sherkety ERP & Website Platform, some admin areas are protected by role, and certain users may be able to edit content but not all settings. If a field looks locked, missing, or cannot be changed, that usually means your current access level does not allow that action on this screen.

A careful review before saving helps you catch missing values early and reduces repeated save attempts caused by preventable validation messages.

Saving changes and responding to validation messages

  1. When you are ready, click the main Save button in the editor toolbar or action area. In Sherkety ERP & Website Platform, the button may briefly change state while your update is being processed. You may see a loading label, a disabled button, or another visual sign that the save is in progress. Avoid clicking Save repeatedly while that indicator is active.

  2. If the save is blocked, look first at the fields you just edited. Validation messages usually appear close to the input that needs attention. For example, a required field may show an error directly under the field, or a formatting problem may be highlighted beside the value you entered. If you changed a Slug or similar identifying field, the editor may also warn you when that value cannot be accepted.

  3. Check for broader messages at the top of the editor or in a toast notification. Sherkety ERP & Website Platform uses on-screen feedback to tell you whether the save succeeded or failed. A field-level message points to one specific input, while a banner or toast usually means the whole save was blocked until one or more issues are fixed.

  4. Correct the highlighted fields, then click Save again. Repeat this process until the editor shows a success message instead of an error. If several fields are involved, work through them one by one rather than changing everything at once.

If you are unsure why a field is failing, compare the field label, helper text, and any nearby warning message. The clearest explanation is usually shown directly next to the blocked input.

Checking the preview before you confirm the update

  1. Use the editor’s Preview option to see how your changes will appear outside the editing form. This is the fastest way to confirm that your text, layout, and content structure look right before you rely on the saved result. If you already reviewed the preview workflow earlier, see Previewing Changes Before Saving Content.

  2. In the preview, compare the edited content against what you intended to publish or keep as draft. Check visible page elements such as headings, paragraph spacing, lists, links, image placement, and repeated content sections. If you updated multilingual content, make sure you are looking at the correct language version before judging the result.

  3. If you changed structural fields such as a Slug, section title, or navigation label, verify that the preview still opens the expected page and shows the correct page heading. For content that appears in shared areas like homepage sections, service highlights, or ERP module pages, confirm that the updated wording appears in the right place and in the right order.

  4. Return to the editor if anything looks off. Fix spacing, wording, missing items, or misplaced content blocks, then preview again. It is much easier to correct display issues before you move on than to discover them after saving and leaving the screen.

Preview is especially useful after editing rich content or grouped items. A field may look correct in the form but still appear awkward once rendered on the page. Use preview to catch those visual issues before you finalize the update.

Confirming that the save completed successfully

  1. After you click Save, look for a clear success signal in Sherkety ERP & Website Platform. This may appear as a toast notification, a confirmation banner, or a saved status in the editor itself. The important point is that the editor should show positive feedback, not simply stop loading.

  2. Check whether the editor updates any save-related details on screen. Depending on the page, you may see information such as a refreshed Last saved time, updated status text, or other save confirmation details. If those details change immediately after saving, that is a strong sign your update was stored successfully.

  3. If the editor shows more than one status, make sure you understand which one you are seeing. A saved draft is not the same as a published update. Likewise, a temporary preview state is different from a completed save. Read the status label carefully before leaving the page, especially when working on public-facing content such as service pages, company type pages, or ERP app pages.

  4. Test navigation away from the editor. If your save completed successfully, Sherkety ERP & Website Platform should no longer warn you about unsaved changes when you move to another admin screen. If the warning still appears, return to the editor and review the fields again.

A successful save should leave you with three signs: the loading state ends, a success message appears, and the editor no longer behaves as though there are unsaved edits.

Reviewing what changed after saving

  1. Re-open the same content entry or refresh the editor screen after saving. This helps confirm that the values now shown in the fields are the values you intended to keep. Review the main content areas first, such as Title, Summary, Body, and any structured sections you edited.

  2. Open any side panels or settings areas that were part of your update. If you changed page details, labels, or organization settings within the editor, confirm that those values remain in place after the refresh. This is especially important when you edited several areas in one session.

  3. Compare the saved content with the page preview or visible website output. Make sure the saved version still matches the formatting, order, and wording you approved. For repeated items, verify that no item disappeared, duplicated, or shifted position after the save.

  4. If your admin view includes change tracking details, review them after saving. Some screens may show updated save information or other record details that help confirm the latest edit was recorded. Administrators should also watch for any workflow-related status changes shown in the editor after the save completes.

A quick post-save review is the best way to catch problems early. It confirms not only that the save succeeded, but that the correct version of the content is now stored and displayed.

Fixing common save and review problems

If the Save button is unavailable, start with the simplest checks. One or more required fields may still be empty, or a field with an error may need attention before saving is allowed. Review the editor from top to bottom and look for highlighted inputs, warning text, or helper messages. If a field is visible but cannot be edited, your role may not allow changes to that part of the content.

If your changes appear in the editor but not in preview or on the page, first confirm that you are looking at the correct version and language. In Sherkety ERP & Website Platform, multilingual content and draft-style editing can make it easy to review the wrong variation by mistake. Refresh the preview, reopen the page, and check that the updated content is being viewed in the same language and section you edited.

If you saw a success message but the values return to older content after a reload, reopen the entry and inspect each changed field carefully. This usually means the save did not fully complete, another edit replaced your version, or part of the update was not accepted. Save again only after checking for any warning message that may have appeared briefly.

When a validation message is unclear, do not guess. Look at:

  • the highlighted field
  • the text directly under that field
  • any banner at the top of the editor
  • any toast message shown after clicking Save

If the problem continues, narrow it down by changing one field at a time and saving again. That makes it easier to identify the exact input causing the block.

Overview

This guide focuses on the point where editing turns into a confirmed update. In Sherkety ERP & Website Platform, saving content is more than clicking Save once. You need to check that the editor accepts your changes, that validation messages are resolved, that preview output matches your expectations, and that the saved version remains correct after refresh.

The workflow in this guide is most useful when you are updating website content from the content editor, including multilingual page sections, structured content groups, and repeated items. It does not repeat how to edit those fields in detail. If you need help with the editing process itself, use Managing Multilingual Fields in the Content Editor and Editing Structured Content and Repeating Items.

You will use this guide when:

  • the Save button becomes active and you want to confirm the update safely
  • the editor shows a field error or validation message
  • preview looks different from what you expected
  • you need to verify that your changes were actually stored
  • the editor still behaves as if changes are unsaved

The steps here are practical and screen-focused. They help you read the editor state, respond to warnings, and confirm the final result using the same content screens you already work in. This is especially important for public-facing pages where a small mistake in wording, structure, or language selection can affect what visitors see.

The next document in this sequence is Using Live Preview to Check Page Updates, which goes deeper into reviewing page output after your edits.

Prerequisites

Before you follow this save-and-review workflow in Sherkety ERP & Website Platform, make sure the basics are already in place:

It also helps to be familiar with common on-screen feedback in Sherkety ERP & Website Platform, such as toast messages, warning banners, and unsaved change prompts. If those messages are new to you, see Understanding Toast Messages and Action Feedback and Recognizing Warnings Errors and Dismissible Notices.

Once these pieces are in place, you can move through the save process with fewer surprises and confirm your updates with confidence.

Was this page helpful?

Download as PDF
ADocs generated by Atloria — from the code, always in sync →
Validating Saving and Reviewing Content Changes — Sherkety Bytes Align