The Version Picker & Cookie PersistenceUpdated
Once a product has versions, a version button appears in the topbar, letting readers switch between versions from anywhere in that product’s docs.
Where it appears#
The version button shows up when all of these are true:
- Versioning is turned on globally.
- The current product has at least one version.
- You’re not on the docs homepage (the index view, when showing multiple products, never shows a version button).

The button’s label always shows the currently active version’s name.
The version picker#
Clicking the button opens a modal listing every version for the current product, newest first. Each entry shows the version’s name, its description if one was set, and a checkmark next to whichever version is currently active. Every version in the list is a plain link, clicking one is a normal navigation, not a JavaScript-driven swap.

Where switching takes you#
- On a single doc page: if the doc is linked to a sibling in the target version (see Version Groups), you’re taken straight to that sibling doc. Otherwise, you’re taken to the product’s page for that version, since the current doc may not exist in the version you’re switching to.
- On a product or category page: you stay on the same page, just with the version changed.

How your choice is remembered#
When you pick a version, WP Super Docs saves it in a cookie (wpsd_v), which lasts 30 days. On your next visit to that product, you’ll land on the version you last chose rather than the product’s default version, until the cookie expires or you explicitly switch again.
The full order WP Super Docs uses to decide which version to show is:
- An explicit version in the URL (from clicking a version link)
- If you’re on a single doc page, that doc’s own assigned version
- Your saved cookie from a previous visit
- The product’s default version (see Enabling Versioning for a Product)
The cookie remembers one choice. It only applies to the product the version belongs to, so other products still open on their default version. Picking a version on another product replaces the remembered choice.
If you’re using a page cache#
You don’t need to set anything up. Version links carry the version in their address (?wpsd_v=), so caches store each version’s pages separately. A page built from a visitor’s saved choice, rather than from its address, is never stored by a page cache or CDN.
A page cache still serves everyone the same copy of a product’s plain address, built for the default version. When a visitor who picked another version gets that copy, their browser takes them to the page for their version right away.
See Page Caching and Hosting for how WP Super Docs works with cache plugins and hosts.
Was this helpful?
Thanks for your feedback!
✓ Feedback received. Thank you!