Platform Support Policy

This policy covers every Signocore WordPress plugin and theme, free and commercial. It sets out which versions of PHP, WordPress and MySQL/MariaDB they run on, how those requirements change over time, and what happens to your site if your server falls behind. Our macOS applications are not covered here; their system requirements are listed on their own product pages.

Our Approach

Signocore products follow the platform versions WordPress itself recommends, as closely as we can without leaving sites behind.

• PHP and MySQL/MariaDB: we aim for the versions WordPress recommends, and a version that no longer receives security updates from its maintainers can be dropped in a following major release
• WordPress: we support at least the three most recent WordPress releases

WordPress numbers its releases sequentially rather than by semantic versioning. Releases such as 6.9 and 7.0 are consecutive and carry equal weight, not a generation apart.

This is a direction, not a schedule. We update and release continuously, and PHP and WordPress move quickly, so we raise a requirement only when it is worth it, usually with a new major release. A product that needs a newer version than the rest can require it on its own. The table below always shows what each product requires today.

Current Requirements

Both columns are minimums, so anything newer works too.

Requirements differ per product, so check the row for the one you want. These figures come straight from the server that ships the releases, which means they always match what you actually install.

MySQL/MariaDB: As required by your WordPress version.

Announced Changes

The next major release of every product will require PHP 8.2 or newer. Where a product already requires a newer version today (see the table above), that newer version continues to apply.

Sites already on these versions are not affected and see nothing. Sites below them get a dashboard notice ahead of time, as described under "How You Will Be Told". Releases published before it keep working as they are.

What Happens If Your Server Falls Behind

Your license is perpetual, and nothing is ever taken away from you.

• The version you have installed keeps working. Raising a minimum requirement affects future releases only. Your site does not change and nothing stops functioning
• You will never be sent an incompatible update. WordPress checks the requirement before offering an update. If your server does not meet it, the update is not offered at all. There is no failed install and no broken site
• Updates resume automatically. The moment your server is upgraded, the newest release appears in your dashboard as usual. You do not need to contact us, re-download anything, or buy anything again

The trade-off is straightforward: for as long as your server stays behind, the version you are running receives no further updates, including security updates. That is why we raise requirements only when it is worth it, and tell you in your dashboard first whenever we can.

How You Will Be Told

When a minimum requirement is about to rise, we tell you ahead of time whenever we can. Releases ship continuously, so we do not promise fixed dates or a fixed notice period.

The announcement arrives as a notice in your WordPress dashboard, shown only on sites that do not yet meet the new requirement. Sites that already meet it see nothing.

The release notes for the release that raises a requirement name the new minimum, and the table above always shows what is in force today.

If You Cannot Upgrade

Start with your host. On most managed and shared hosting, PHP is a dropdown in the control panel and the change takes a minute. WordPress upgrades from your own dashboard and costs nothing.

If an upgrade genuinely is not possible, here is where you stand:

• Your license does not expire, and the version you have installed keeps working
• If you need to reinstall, you can download the last release compatible with your server at any time, without asking us
• That version will not receive further updates, including security updates
• The moment your server is upgraded, access to current releases resumes with no action from you

We do not refund licenses because a minimum requirement changed. What you purchased continues to work, changes are announced ahead of time whenever we can, and the requirement in force is published here and on every product page before you buy.

Confirming that your server meets the current requirements is your responsibility before you purchase. If you are not sure where your server stands, ask us first and we will tell you.

Changes to This Policy

This policy evolves with WordPress and with our products. Material changes are announced the same way requirement changes are, and are never applied retroactively to a release that has already shipped.