How to read compatibility status
A plugin name on this page is not automatically a promise of deep integration. Verified means the release suite exercises that product or API. Native means BP Builder Addons contains a dedicated adapter. Standards-based means the products can work together through WordPress, BuddyPress, bbPress, REST, shortcode, or storage contracts. Validation pending means the combination belongs to the compatibility roadmap and should be tested before production.
- Verified: automated clean-install or functional release evidence
- Native adapter: dedicated detection, data mapping, controls, or fallback behavior
- Standards-based: shared public APIs with no private coupling
- Validation pending: no production compatibility claim yet
Verified community and forum platforms
- BuddyPress 12+: verified platform and lifecycle suite, including current member, notification, message-thread, group, and directory URL APIs with a zero-deprecation runtime gate
- BuddyBoss Platform 3.1.1: verified clean-install package gate
- bbPress and BuddyBoss Forum Discussions: detected through bbPress-compatible APIs
- Native BuddyPress members, extended profiles, activity, groups, friendships, messages, and notifications remain canonical
Verified builders and presentation systems
- Elementor 3.20+: 94 native widgets; Elementor Pro is not required
- WordPress block editor: 94 dynamic server-rendered blocks
- Divi: 94 native modules with registration and render gates
- Shortcodes: all 94 components for builders and templates that execute WordPress shortcodes
- Bricks, Beaver Builder, Breakdance, and Oxygen: shortcode workflow; dedicated visual controls are not claimed
Native and standards-based service integrations
- myCred and GamiPress: legacy balance and badge fallback when native Engagement Studio is disabled
- Cloudflare Turnstile: native server-side verification
- Amazon S3 and Cloudflare R2: object-storage workflows with protected-media requirements
- LiteSpeed and other WordPress page caches: private REST responses use no-store behavior; member-facing routes still require cache exclusion rules
- Standards-based Web Push: site-managed VAPID without a Firebase requirement
Membership and learning access adapters
The visual Access Policy Studio can list provider resources and normalize active-access decisions through dedicated adapters for MemberPress, Paid Memberships Pro, WooCommerce Memberships, LearnDash, LifterLMS, and Tutor LMS. An executable contract gate verifies detection, exact resource catalogs, active and inactive decisions, any/all policy relations, unknown-provider behavior, and adapter extension hooks. Clean-install version certification remains a separate release matrix.
- MemberPress active product subscriptions
- Paid Memberships Pro membership levels
- WooCommerce Memberships active plans
- LearnDash course access
- LifterLMS course enrollment
- Tutor LMS enrollment
Commerce and multilingual boundaries
WooCommerce account and order hooks are detected but no checkout or order UI replacement is claimed. WPML and Polylang use WordPress string APIs and remain validation-required until translated routes, fields, Studio labels, saved filters, and language-specific Email Studio journeys have versioned fixtures.
- Validate registration, account, access-denied, cancellation, and expiry journeys for every membership release
- Validate course groups, learner profiles, activity events, and navigation for learning plugins
- Validate translated routes, profile fields, Studio labels, saved filters, and email locales for multilingual plugins
- Publish versioned results and known limitations after each integration joins the certified matrix
Request or report an integration
A useful compatibility report includes exact plugin versions, active community platform, builder, affected route, member role, expected result, actual result, and a reproducible sequence. Specific evidence lets an integration become a tested adapter instead of a vague compatibility claim.