About editing a page at the same time as another admin
This page explains what happens when two admins edit the same page around the same time, and why MapleGather never quietly throws away one person’s work.
The short version
Section titled “The short version”If another admin recently edited a page you open, MapleGather warns you before you start. If you both save close together, MapleGather stops and asks you to review their changes before yours go in — it never silently overwrites. Every save is also kept in the page’s version history, so nothing is truly lost.
How it works
Section titled “How it works”MapleGather uses a gentle, two-part safety net rather than locking a page while someone edits it:
- A heads-up when you open the page. If another admin saved the page very recently, the editor opens read-only with a warning naming who edited it. You can select Edit anyway to take over editing. This is a courtesy warning — it’s based on recent saves, so an admin who has the page open but hasn’t saved yet won’t show up here.
- A review step when saves collide. If you save (or the automatic save fires) after someone else has already saved since you opened the page, MapleGather shows a Review before saving message. It summarizes what changed — the title, blocks, or settings — and gives you two clear choices: Reload their version (keep their save and drop your unsaved edits) or Overwrite anyway (keep your edits). This step is always there, so a stale save can never quietly replace newer work.
Because restoring and saving always add to the page’s history rather than erasing it, choosing Overwrite anyway is safe: the other admin’s save is still available in version history if you need it back.
Why it works this way
Section titled “Why it works this way”Locking a page while one person edits is frustrating in a small organization where a couple of volunteers might tidy up the same page on the same evening. MapleGather instead lets everyone keep working and makes conflicts visible and reversible. The goal is that collaboration never causes data loss — and that no one ever discovers, too late, that their changes vanished.
Edge cases & boundaries
Section titled “Edge cases & boundaries”- The warning is best-effort; the review step is the real guarantee. The open-page warning can miss someone who hasn’t saved yet. The save-time review is always present and is what actually protects your work.
- Automatic saves are covered too. The review step can appear during a background autosave, not just when you select a button — it still won’t overwrite a newer save without asking.
- History is capped at 25 versions. Older automatic saves are pruned first once a page passes 25 versions; versions you published or restored to are kept preferentially.