Untested plugin versions

The builder checks the plugins on your connected site against a tested version range and warns in two directions. Neither warning blocks you.

Below the minimum

The plugin is older than the version Memberside supports.

The screens built from it may be missing data, or missing entirely, because they read fields and endpoints that older version does not provide.

Update the plugin. This warning is worth acting on — it names a real difference between what the app expects and what your site provides.

Newer than tested

The plugin is newer than anything Memberside has been tested against.

Usually nothing is wrong. It means the plugin released after the last compatibility pass, not that a problem is known.

Treat it as a place to look first, not as something to fix. If a screen from that plugin misbehaves, this warning tells you where to start; if everything works, it is noise.

Why they do not block anything

Blocking on a version mismatch would break working apps every time a plugin shipped a routine release. The warning tells you what changed and leaves the judgement with you.

When a screen breaks after a plugin update

The likely order of causes:

The plugin renamed or removed a field the app reads. The screen renders with gaps.
The plugin changed its REST behaviour. The screen is empty rather than partial.
The plugin deactivated itself because of a dependency. Then the feature card is greyed out, which is a different symptom.

Rolling the plugin back to the last version that worked confirms which. If it does, get in touch with the plugin name and both version numbers.

Where to see the warnings

Two places:

The builder, as a dialog listing every plugin outside the range.
Memberside → Dashboard on your WordPress site, which lists detected plugins and their versions.