Skip to main content

The release line

A product page usually says which version is current, what it needs and what it has been tested with. Typed by hand, that line is out of date the day the next release goes out. The release line reads it from Freemius instead, from the same product and the same token as the prices.

Version 1.4.0 · Requires WordPress 6.2 and PHP 7.4 · Tested up to 7.1

Insert the Freemius release block, under Widgets in the inserter, or write [pflp_release].

What it shows​

Four parts, each read from the latest release Freemius holds for the product:

Partshow wordReadsFrom Freemius
VersionversionVersion 1.4.0the version you deployed
RequiresrequiresRequires WordPress 6.2 and PHP 7.4the minimum WordPress and PHP versions
Tested up totestedTested up to 7.1the WordPress version you tested with
ReleaseddateReleased 2 September 2026the date the release reached Freemius

The first three show by default. Pick your own with show, in the order you want them:

[pflp_release] -> Version 1.4.0 · Requires WordPress 6.2 and PHP 7.4 · Tested up to 7.1
[pflp_release show="version"] -> Version 1.4.0
[pflp_release show="tested,version"] -> Tested up to 7.1 · Version 1.4.0
[pflp_release show="version,date"] -> Version 1.4.0 · Released 2 September 2026
[pflp_release separator=" | "] -> Version 1.4.0 | Requires WordPress 6.2 and PHP 7.4 | Tested up to 7.1
[pflp_release show="date" date_format="Y-m-d"] -> Released 2026-09-02

In the block, Show is four tick boxes, and Separator and Date format sit under them. The date uses your site's own date format unless you give it one of its own.

"Requires" is one part: it names WordPress and PHP together when Freemius has both, and whichever one it has when it has one.

Which release​

Only a released version shows. A version you have deployed to Freemius but not released, or released as a beta, never appears on the page.

"Tested up to" is the value you gave Freemius, such as 7.1. WordPress.org shows the same value expanded to the latest point release, 7.1.2, so the two can read differently while meaning the same thing.

The date is the moment the release reached Freemius. If you upload to Freemius and then release on WordPress.org, it is usually the same day and a few minutes earlier.

When there is nothing to show​

A product with no releases on Freemius shows nothing at all: no line, no empty space, nothing in the page source. An app or a service sold through Freemius has no WordPress releases, so this is expected for one. The editor says so in place of the preview:

This product has no releases on Freemius, so nothing shows on the page.

There is no fallback text on purpose. A version typed as a fallback is the stale copy this line exists to replace. For a product Freemius has no releases for, write the line yourself.

A part Freemius has no value for is left out with its separator. A release with no PHP version reads "Requires WordPress 6.2"; one with no tested-up-to version leaves that part off the end. If every part you asked for is empty, nothing shows.

If a refresh fails, the last release fetched stays on the page. Nothing is ever cleared because Freemius could not be reached; the only thing that clears a release is Freemius saying there are none.

When it changes​

The release is fetched whenever the prices are: when you save the product, press Refresh now, on the regular refresh, and on the daily check. The webhook the plugin registers listens for new releases too, so a release in the Freemius dashboard reaches the page within seconds. It listens for a release being suspended as well: the line then shows the latest version still released, or nothing if none is. A site updated from an earlier version brings its webhook up to date on its own, once.

The product's Status card shows the release it holds, such as "1.4.0, released 2 September 2026", or "None published on Freemius".

Inside a pricing card​

The release block follows the card's product, like everything else in a card. It is not part of the pricing card pattern: add it from the inserter where you want it.

Layout and styling​

As a shortcode the line is inline, so it can sit in a sentence:

The current version is [pflp_release show="version"].

align="left", "center" or "right" puts it on a line of its own. As a block it is always a line of its own, and takes the block editor's own Typography, Colour, Spacing and Border panels, as the plan text does.

Each part is a span of its own, so you can style one without the others: .pflp-release wraps the line, and .pflp-release-version, .pflp-release-requires, .pflp-release-tested, .pflp-release-date and .pflp-release-separator are its parts.

Every attribute is in the Reference.