Skip to content

Knowledgebase

Reviewing multiple Site Editor changes before saving

wordpress

A Site Editor session can modify several shared objects, including a template, header, navigation menu, synced pattern and global styles. Review the save panel so you understand the full scope before publishing those changes.

01 Keep the task focused

Start with a clear goal, such as changing the header logo or widening a page template. Avoid experimenting across several unrelated objects in one live session. A staging copy is a better place for broad exploration because unsaved changes can accumulate beyond the object currently visible.

Record the objects you expect to change and keep an appropriate recovery point for substantial design work.

02 Review the pending changes

  1. When ready to save, open the editor's save confirmation and read every listed item.
  2. Compare the list with the intended task. A Styles item can affect the whole site, while a shared header or pattern can affect many pages.
  3. Use the available review or selection controls to inspect and manage unintended changes rather than confirming automatically.
  4. Save the intended set only after the scope is understood.
  5. Reopen the relevant objects or public pages to confirm the saved state.

03 Test according to the scope

For a page-content change, test that page. For a shared template, test several pages using it. For global styles, inspect different block types, forms, navigation and narrow layouts. A single homepage screenshot cannot validate a site-wide typography change.

When a navigation menu changes, test the actual destination links as well as its appearance. When a synced pattern changes, check at least one other occurrence outside the current template.

What if I save an unintended Site Editor change?

Identify which object contains the unwanted change before resetting anything. Restoring a template will not necessarily undo a separate global-style edit, and resetting a shared header may discard useful work unrelated to the problem.

Use the available revision or recorded settings for the specific object, then verify the public effect. If support is needed, provide the objects shown in the save panel, the intended change and examples of pages affected unexpectedly. That makes the issue much easier to diagnose than a general report that the whole site changed.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution