Content updates and caching
Why a change appears on the live site quickly after publishing, and what to do when it doesn't
When you publish a change, it usually appears on your live site within a minute or so — but sometimes a change seems to take longer. This page explains why, what controls the timing, and what to do if an update hasn't shown up yet.
The short version: publishing is what makes a change go live quickly. Saving a draft or editing without publishing doesn't refresh the public site.
Why your site is cached
Basker serves your public site through a global CDN — a network of edge servers that keep a copy of each page close to your visitors. Caching is what lets your site absorb on-sales, season launches, and other traffic spikes without slowing down. See How Basker works for the bigger picture.
The trade-off is that a cached page can be slightly behind the very latest content until the cache is refreshed. Basker manages that refresh for you — you don't need to clear anything manually.
What happens when you publish
Publishing a record — a page, event, post, blog, person, season, and most other content types — tells Basker to refresh the cache for your whole site.
You publish a record
The moment a record moves to Published (or you re-publish an already-published record), Basker queues a cache-refresh job for your site.
The refresh job runs
Basker checks for queued refreshes every minute. So a publish is normally picked up and cleared within about a minute.
The next visitor sees the update
Once the cache is refreshed, the next visit rebuilds the page from your latest content. Basker uses a "stale-while-revalidate" approach — visitors are never left waiting while a page rebuilds; they get the existing copy instantly while the fresh one is prepared in the background, and the updated copy is served from then on.
This whole-site refresh is why most edits appear on the live site very soon after you publish.
The refresh covers your entire site, not just the page you edited. That's deliberate — content often appears in more than one place (a post in a listing, an event in a smart collection), so refreshing everything keeps the whole site consistent.
Why timing can feel inconsistent
A few details explain why updates sometimes feel slower than others.
- Drafts and autosave don't refresh the live site. Basker autosaves your work as you edit, but autosaves and draft saves are intentionally not treated as a publish. If every keystroke triggered a site-wide refresh, your cache would never settle. Your change only reaches the public site when you Publish. See Drafts, preview, and publishing.
- Rapid re-publishes are grouped together. If you publish several times in quick succession, Basker doesn't queue a separate refresh for each one — recent publishes are grouped so the site isn't refreshed constantly. The change still goes out; it's just covered by the refresh already in flight.
- Time-based expiry is the fallback. If a page isn't refreshed by a publish, it still refreshes on its own as its cached copy ages out. That natural expiry can take up to an hour, which is why an update made without publishing — or a page that nothing republished — can take noticeably longer to change on its own.
If a change hasn't appeared and you didn't publish, that's usually the reason. Open the record, confirm it shows as Published, and publish again if it doesn't.
Previewing before you publish
You don't have to publish to see how a change looks. Every record has a Preview option that renders your draft exactly as it will appear on the live site — and Preview is never cached, so it always shows your most recent edit straight away.
Preview is the right first step whenever you want to check your work. You can also share a preview link with someone who doesn't have a Basker account. See Drafts, preview, and publishing.
Forcing a refresh
There's no "clear the cache" or "invalidate" button, and you shouldn't normally need one — publishing already refreshes your site within about a minute, and Preview shows unpublished work instantly.
If you ever need to force a refresh of the live site, publishing any record refreshes the whole site, so re-publishing a page is the simplest way to do it. If a change still isn't showing after that, contact sales with the page URL and what you expected to see.