Plugin releases

Everything about which version of the Memberside plugin your site runs: where releases come from, how updates reach you, how to put an older one back, and what the tested-version ranges on each release mean.

The plugin is distributed privately rather than through the wordpress.org plugin directory. That has one consequence worth stating plainly: nothing outside your account can hand you the file, and searching Plugins → Add New on your site will never find it.

Where releases live

Downloads, in the header once you are signed in. It holds:

• The current version, with its download, its size and its release date.
• What each version requires — the WordPress range it was tested across and the minimum PHP.
• Which versions of each integrated plugin the release was tested against.
• A tab per release with that release’s notes, and its own download.
• Every older version, behind Older versions.
• Beta releases, collapsed, covered in Beta access.

How updates reach your site

Through the ordinary WordPress updater. The plugin asks whether a newer version exists twice a day and, when one does, offers it on Plugins and Dashboard → Updates like any other plugin, with the notes under View version details.

So you download from Downloads twice: the first install, and any deliberate rollback. Everything in between is the updater.

Note

The update check needs outbound HTTPS from your server. A site behind a firewall that blocks it keeps working and never learns a new version exists — the symptom is a plugin that stays on one version for months while the release notes move on.

Installing an older version

Sometimes a release breaks something for you and the fix is to go back while it is investigated.

1. On Downloads, open Older versions and find the version you want.
2. Select its Download.
3. In WordPress, deactivate and delete the Memberside plugin. Deleting the plugin does not delete its settings — those live in the database, and your endpoint choices and API keys survive.
4. Upload the older .zip under Plugins → Add New → Upload Plugin and activate it.

The updater will offer you the newer version again on its next check, because a newer version genuinely exists. Leave the update alone until the release you are avoiding has been superseded.

Rolling back below a build's namespace

Version 2.0.0 renamed the plugin from um-rest-api and moved its REST namespace from um/v1 to memberside/v1 with no alias. An app built against memberside/v1 cannot talk to a 1.x plugin at all, so a rollback across that boundary breaks every screen rather than degrading. Do not go below 2.0.0 for an app built since.

What “tested with” means

Each release records the versions of each integrated plugin it was tested against, and Downloads shows them for the current release. A range like BuddyPress 12.0.0 – 14.5.2 says testing covered those versions. It is a statement about testing, not a gate:

• Nothing is blocked by a mismatch. The app behaves exactly as it would have anyway.
• Below the minimum, your site reports below minimum and the plugin’s Dashboard says so.
• Above the maximum, it reports untested. Usually nothing is wrong; it means a newer release exists than anything we have exercised.

Either way it tells you where to look first when a screen behaves oddly. See A feature is greyed out and Plugin version warnings.

Two places that look like the same table

They answer different questions, and their numbers can differ without either being wrong.

Where	Question it answers
Downloads → Tested with	Which plugin versions this release of Memberside was tested against
Site Health, in an app’s builder	Which versions your connected site is actually running, and whether they fall in that range

A release’s own ranges are fixed the day it is published. Your site’s versions change whenever you update a plugin.

Where the release notes come from

The plugin keeps one changelog, in its readme.txt. Each release’s notes are lifted from it unchanged, which is why the same words appear on Downloads, under View version details in WordPress, and on the public changelog.

There is no second, tidier summary written for customers. One source means the notes cannot drift from what shipped.

When it does not work

Symptom	Cause	Fix
Downloads lists no releases	You are signed in to an account that has just been created, during a window where nothing is published	Refresh. If it persists, open a ticket
A download starts and the zip will not install	WordPress rejects a partial download, usually a proxy truncating it	Download again, and check the file is around a megabyte before uploading
WordPress never offers an update	The site cannot reach us over HTTPS, or an update check is cached	Confirm outbound HTTPS, then wait twelve hours or visit Dashboard → Updates, which forces a check
An update installs and asks to be installed again	You are on a release that was superseded within the hour	Install the second one. Two releases close together genuinely means two updates
A beta shows no download	Its build did not produce an installable file	Nothing to do — that release is not available. The next one supersedes it

Next

Install the plugin if you have not yet, or Supported plugins for what each integration adds.