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
- 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+: 93 native widgets; Elementor Pro is not required
- WordPress block editor: 93 dynamic server-rendered blocks
- Divi: 93 native modules with registration and render gates
- Shortcodes: all 93 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, learning, commerce, and multilingual roadmap
MemberPress, Paid Memberships Pro, WooCommerce Memberships, LearnDash, LifterLMS, Tutor LMS, WPML, and Polylang are priority validation targets. BP Builder Addons currently preserves normal WordPress and BuddyPress hooks, but this documentation does not claim dedicated adapters until automated fixtures and end-to-end journeys exist.
- Validate registration, account, access-denied, cancellation, and expiry journeys for membership plugins
- Validate course groups, learner profiles, activity events, and navigation for learning plugins
- Validate translated routes, profile fields, studio labels, and saved filters for multilingual plugins
- Publish versioned results and known limitations after each integration joins the release 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.