Updates
New versions, how update notices appear, and what expiry actually stops.
Two ways, use either:
- From your account. Your downloads always serves the current version.
- In the installation itself, where the product supports it — an update notice appears in the normal place for that platform, the same as any other update.
No, not while your update entitlement is running. The product page states the period, and it starts on the day you bought.
A genuinely different product sold separately is a separate purchase, and its page will make that clear.
Update checks are cached. Your installation does not ask us on every page load — it asks periodically and remembers the answer for a few hours.
So a new release can take some hours to show up. This is deliberate: it protects your site's performance and our service. If you are testing and want it now, clear your platform's update cache.
Your product keeps working. It is not disabled, not degraded, and not switched off. We do not build kill switches.
What stops is new versions and support. The installation will tell you an update exists but is no longer entitled to fetch it. Renew and the entitlement returns immediately.
Clause 10 of the Licence Agreement is the authority on this.
Probably not. There is a short grace period after expiry during which updates keep being served, exactly so that a renewal a few days late — or a payment that takes time to clear — does not interrupt anything.
The length is shown in your licences.
Yes — we email the address on the order ahead of the expiry date.
That is a courtesy, though. Expiry runs off the date, not off whether the email was delivered or read, so the date in your licences is the fact.
It will overwrite our files, and anything you edited inside them goes too. It will not touch a child theme, a hooks layer, or a documented overrides folder.
Take a backup before you update. We will keep saying this because it is the single measure that turns a bad update into an inconvenience rather than an outage.
When there is something worth releasing — a security fix, a compatibility change, a bug corrected, a feature added.
We are not going to promise a schedule we cannot keep. A security fix is priority over everything else we are doing; a cosmetic change waits until there is a release worth making.
Yes, and please do — send it over. Real requests from people using the thing are how products get better.
Two honest caveats. We cannot commit to building it or to a date. And Clause 16.5 of the Terms of Service says that a suggestion sent to us can be used without payment or attribution — so if an idea needs to stay yours, write to [email protected] and we will agree terms first instead.
Your installation keeps working and your licence stands. Your download stays in your account.
We will say so on the product page rather than letting it quietly disappear. What ends is new development, not your right to use what you bought.