Restrict wordpress content based on client Mindbody account details. Create two access levels based on MBO membership details.
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records MZ MBO Access version 2.1.6 as active, updated 5y ago and tested up to WordPress 5.7.
Install and you can limit content based on user MBO memberships:
[mbo-client-access access_levels=”1, 2″]
RESTRICTED CONTENT HERE
[/mbo-client-access]
You can also redirect users based on their access level.
Until later in 2020, requires access to MBOs v5 (not v6) API.
None yet. Hopefully will work well.
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 5.7.
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.
