Updates and the version check

Last updated November 5, 2026

The Pavilion version panel on the Support screen shows what is installed and asks the hub what the current release is. Re-check now forces a fresh look; otherwise the answer is cached for an hour, so expect a lag between a release being published and an untouched site noticing.

Pavilion tells the hub three things: which product it is, which version is installed, and which package is on disk — Basic, Standard or Premium. It also says whether Pavilion Pro is running, so ModuleFest sends the right updates.

It is advisory. What a club is entitled to is decided by the licence, never by what the site claims about itself.

Common questions

"The endpoint responded, but with no version.": Everything on this side worked — the hub was reached, the site token was accepted, and the reply was valid. It simply did not name a current release, which means none is published for Pavilion on the hub. That is a hub-side matter rather than a fault here, and it is sometimes deliberate: a release may be uploaded but deliberately held back from the update channel.
It says the hub would serve a different package.: The licence entitles the club to one package and a different one is installed. Nothing is broken meanwhile — the licence decides what is switched on, whichever files are present — and the next update moves the site across on its own.
Why does a free club get updates at all?: Registering with the hub is what entitles a site to updates; the licence only decides which package it receives. A free Basic club must keep getting fixes.
Every page said "Call to undefined function dbDelta()" after an install or update.: Fixed in 10.59.0. Pavilion’s one-off table jobs used a WordPress function that only exists once an admin page has been opened, so if the first page anybody visited after installing or updating was the front end, the login screen or an automatic update overnight, every page of the site failed until somebody opened /wp-admin/. Opening it once is still the immediate cure on an older version; updating to 10.59.0 stops it happening.
No update is offered but I know there is a newer one.: Press Re-check now rather than waiting — it bypasses the cache and rewrites WordPress’s own update record. If it still says nothing, the panel gives the specific reason, which is usually that the site is not linked to the hub or that no release is marked current.

Was this helpful?

Still need help? Sign in to your account and raise a support ticket. The people who wrote the code will help, and most tickets are answered the same working day.