Skip to content
Memberside Docs

A feature is greyed out

A greyed-out card in Available Features means the WordPress plugin that feature is built from is not active on the connected site.

This is not a plan limit. Every feature is available on every plan — the screen has nothing to read.

Fix it

Section titled “Fix it”
  1. Find the plugin name on the card. Each card names the plugin it needs underneath the feature name.
  2. Install and activate that plugin on your WordPress site.
  3. Reload the builder.

The card becomes draggable. See the feature-to-plugin matrix for the full mapping.

Some features need two plugins

Section titled “Some features need two plugins”

Badges needs both myCred and Ultimate Member - myCred. One without the other leaves the card greyed out, and the card names whichever is missing.

The same is true of the WooCommerce account screens, which need both WooCommerce and Ultimate Member - WooCommerce.

When every card is greyed out

Section titled “When every card is greyed out”

The builder could not read your site’s plugin list at all.

  • The Site endpoint group is off. Enable it under Memberside → REST API.
  • The connection is broken. Check the Connection tab and reconnect.

When every card stays draggable and a banner appears

Section titled “When every card stays draggable and a banner appears”

The opposite case. If the builder cannot reach the plugin list, it fails open — every card stays draggable and a banner tells you why.

That is deliberate: a network blip should not empty your feature sidebar. But it does mean a card being draggable is not proof the plugin is there. If you place a feature during a banner and its screen is empty, check the plugin.

A chat feature that will not drop

Section titled “A chat feature that will not drop”

Not greyed out, but refused on drop. An app uses one chat backend or the other — either Ultimate Member’s Private Messages or Better Messages, never both.

Remove the chat feature you already placed before placing the other.

A background feature that will not drop

Section titled “A background feature that will not drop”

Refused with “already added — only one is allowed”. Background features are singletons: one Single Post, one Single Page, one Activity Thread.

Check the Background tab; it is already there.

Every BuddyPress card is greyed out on a BuddyBoss site

Section titled “Every BuddyPress card is greyed out on a BuddyBoss site”

Fixed in Memberside 2.53.0. If you are on an older version, this is what you were seeing, and updating the plugin is the fix.

BuddyBoss Platform is BuddyPress and bbPress forked and merged, so the eleven BuddyPress screens work on it — but the builder checks your site’s plugin list for “BuddyPress”, and on a BuddyBoss site that plugin is not installed. Every card read “Requires the BuddyPress plugin” while the endpoints behind them answered perfectly well.

From 2.53.0 those cards accept either plugin, and the card names whichever one your site actually runs. The component check still applies, and BuddyBoss ships most of its optional components off — the message names the component using BuddyBoss’s own wording, so the row it tells you to switch on under Settings → BuddyBoss → Components is the one you will find there.

The bbPress cards are greyed out on a BuddyBoss site

Section titled “The bbPress cards are greyed out on a BuddyBoss site”

Working as intended. BuddyBoss reports bbPress as active to the rest of WordPress even though the bbPress plugin is not installed — it bundles a fork of it. Those cards are built for the bbPress plugin’s own surface, so offering them for a fork they have not been tested against would produce screens that half work.

BuddyBoss’s Discussion Forums will get their own feature cards. Until then, the forums are not available as native screens on a BuddyBoss site.

Section titled “Related”