Use this guide when an edit appears in Cedros but the public website still shows old content, a missing page, or a different version. Check the exact page and whether the change was published, then narrow down any preview, access, or browser difference.
Before reloading the editor, copy any unsaved work you need to keep. Use a separate tab for public-site checks.
Start with the symptom
| What you see | Check first |
|---|---|
| The edit appears only in the builder | Whether the change was saved and published. |
| A saved preview is correct, but the public page is old | The published version and any scheduled release. |
| The page works by its address, but not through a menu | The menu's destination and saved links. |
| You see a missing page, redirect, or holding screen | The exact address, publication state, and site access mode. |
| Only one browser shows old content | A fresh public-page load and browser-specific differences. |
| Only one language, device, or section looks wrong | Translations, visibility, shared layouts, or the feature supplying that content. |
Choose a specific detail to compare, such as the new headline or button destination. “The headline still says Summer hours instead of Winter hours” is easier to diagnose than “The page looks old.”
Confirm you are checking the right page
- In Site → Pages, open the page you edited and note its title and route.
- Confirm you are in the intended site's admin, especially if you manage several sites or use staging and production environments.
- Enter the full public address directly in another tab. Use the intended domain and path, not an admin or saved-preview link.
- Check where the browser actually lands. A redirect, language prefix, bookmark, or menu can take you to a different address.
- Compare the same language and sign-in state before deciding the content is stale.
For example, editing /services will not change a separate page at /services-old, even if both use the title “Our services.”
If the direct address works but a menu takes you elsewhere, follow Editing desktop and mobile navigation or Updating your footer and site-wide links.
If the address recently changed, check both old and new paths using Changing a page address without breaking links. Do not rename the page again as a troubleshooting shortcut.
Check whether the change was saved and published
Cedros can have an unsaved editor view, a saved current draft, and a published version of the same page. They can contain different content.
- Unsaved edits exist in the editing session. Seeing them in the builder does not establish that they were saved.
- A saved draft records the change for further work. A draft-only save does not publish its page content.
- A published version is the content released for visitors. The page can still have newer unpublished work.
For a visual page, the action depends on its existing publication state:
- New or unpublished page: Save draft saves the work. Use Publish when the whole page is ready.
- Already-published page: Save saves and publishes the update. Save and exit also publishes. Wait for publication confirmation, then check the public address.
- Scheduled page: check the saved schedule and current revision; saving the draft does not release it immediately.
A Published label alone does not prove that the newest edit is live. Check the actual content and revision information in the editor's main Publishing tab. History can help identify the latest saved change and when it was made.
If you need to preserve an unfinished update privately on a published visual page, ask your site administrator or an authorized Cedros assistant for a draft-only save. Do not use the builder's Save just to create a private checkpoint, and do not unpublish a working page to test whether publication is the problem.
For the full workflow, see Creating and publishing a website page.
Read the result of the last save or publish
Look for the confirmation or error from the action you took.
Draft saved means a draft save completed. Page published, Published page saved, or another explicit publication confirmation indicates a successful release action. A spinner ending or a preview opening is not the same confirmation.
If you see an error:
- Copy the exact message and note the action and time.
- Check whether it concerns saving, publication, preview generation, or loading history.
- Preserve unsaved work before reloading.
- Reopen the saved page and inspect its content, status, and History.
- Correct the stated cause, review the intended revision, and retry the relevant action.
A combined save-and-publish action can save the draft before publication fails. A warning that revision history could not refresh does not necessarily mean the save failed. Check the saved and public states rather than assuming the whole operation succeeded or failed together.
Common causes include:
- Another editor saved a newer revision: preserve your work, reload the latest version, and coordinate the changes.
- An address conflict: confirm which page or installed feature owns the route. Do not delete another page just to clear the message.
- Invalid content or a missing template: repair the named field or dependency and review the result.
- Missing permission or an expired session: sign back in if prompted, or ask your administrator to check your access.
- A review requirement: complete the requested preview or review for the current saved version. An older review may no longer apply.
If Save or Publish is unavailable, read its explanation and any visible status message. Avoid repeatedly clicking another release control to get around the problem.
Compare the editor, saved preview, and public page
The builder's Preview lets you inspect the editing view. A saved preview represents a saved revision. The public URL shows what visitors can access. Opening one does not publish the others.
In the editor's main Publishing tab:
- Check the current revision and saved-preview information.
- Use Generate Saved Preview or Update Saved Preview, whichever appears, when the saved page is ready for review.
- Open the current preview link instead of reusing an older preview tab.
- Compare the specific changed text, image, or link with the public page.
- If Cedros requests a live comparison, complete it for the current saved version after inspecting both.
If the change appears in the builder but not the saved preview, check whether it was saved after that preview was generated. For a published visual page, remember that Save publishes; use the draft-only workflow if you still need private review.
If the saved preview is correct but the public page is old, focus on the release result, schedule, and public address. Refreshing a preview does not release it.
A private preview link can expire. Generate a fresh one when needed, and do not distribute it as the permanent customer-facing page address.
Check a scheduled release
Open Publishing and inspect the saved schedule, not just a date you typed into the picker.
Check:
- The date and time, including whether you entered the intended day.
- The local time zone of the computer/browser used to set it; the editor's date-time field uses local time.
- Whether the current saved revision was reviewed after the most recent edit.
- Any validation issue affecting the page or a connected shared template.
- The actual public result after the scheduled time.
Edits made after review can leave a scheduled page waiting for a review of the newer revision. Validation can also prevent a due page from being released. Reloading the public URL does not trigger publication.
Decide whether the page should go live now or later before refreshing its review. If a scheduled time has already passed, completing the missing review can make the page eligible for immediate release. To keep control of the release time, clear the pending schedule while preserving any existing live page, fix the draft, and review it. Then set a new future schedule or publish now when ready, and confirm the resulting state.
If the scheduled time has passed and the page still is not live despite the correct revision and completed checks, contact your site administrator with the scheduled time and time zone. Do not keep moving the date or making unrelated edits to force it through.
Check access, language, and shared content
If visitors see a maintenance, waitlist, presale, sign-in, or restricted-access screen, page publication may not be the issue. Site access settings and visitor permissions can determine what is shown. Follow Controlling when your site is public; review the intended rules before changing them.
If only part of the page is wrong, check what supplies that part:
- Header or footer: edit and save the relevant menu or appearance setting.
- Shared layout: a template draft needs its own publication; publishing one page does not publish an unfinished template design.
- Product, form, booking, or other connected feature: inspect that feature's own saved configuration and availability.
- One block: check its Visibility, content, media, and selected preview mode.
- Another language: inspect the translated fields and published result. Existing translations do not automatically become current when you change source text.
Use Reusing a shared layout across pages, Building a page with the visual editor, or Setting up a multilingual website for the relevant controls.
Rule out an old browser view
Do this after checking the page's address and release state:
- Reload the public page in its own tab.
- Open the exact same public address in a private window or another browser.
- Compare on a second device if available, using the same language and equivalent visitor access.
- Note whether the difference affects one browser or every tested visitor.
A private window usually starts signed out, so an access difference can explain a different result. A matching fresh view makes an old browser view more likely, but does not identify the cause by itself.
If only one browser is wrong, preserve any local drafts and try closing and reopening that public tab. Ask your site maintainer for browser-specific help before clearing stored site data that may contain unsaved work.
If fresh browsers still show old content after confirmed publication, ask your site maintainer to check delivery caching, redirects, and domain routing. If the site uses an external cache or proxy, its settings may need investigation. Do not change DNS, disable access controls, or purge unrelated data as a first response.
Search listings and social link previews are separate from the page itself. An old search snippet or shared-link image does not prove the live page failed to update; first verify the direct public URL.
Recover or get help
If the wrong content was published, use Restoring an earlier page revision. Restoring saves an earlier version as the current draft; review and release the correction deliberately, and check any address changes.
If the issue remains, follow Getting help and reporting a problem. Include:
- The exact public URL and affected site.
- The specific expected change and what appears instead.
- Whether the change appears in the editor, current saved preview, and public page.
- The last save or publish message and time, including time zone.
- The current revision and scheduled release time, if relevant.
- Browser, device, language, sign-in state, and results from a fresh browser.
- A screenshot of the error or visible difference, with private information removed.
Keep private preview links, customer information, and credentials out of public reports. Preserve the page's current work while the problem is investigated.