MediaVerse and BuddyNext
media inside your community
This is the deepest pairing MediaVerse has, and the only one where it removes its own interface rather than adding to yours.
How the pairing works
- MediaVerse withdraws its own UIA filter called mvs_buddynext_active tells MediaVerse that BuddyNext is running the community. It stops loading its own assets, hides its panels, and switches off its notification bell. Your members see one interface because there is only one.
- Media attaches to BuddyNext objects directlyPhotos link to a BuddyNext post through a provider-neutral linkage rather than a BuddyPress-shaped one, so a photo on a community post is the same kind of record as a photo anywhere else.
- Uploads and albums surface on profiles and feedsWhich is the registry line word for word: media uploads and albums visible on member profiles and in activity feeds.
What you can build with both
- A community where members post photos into the feed and build a personal album alongside their profile.
- One notification stream rather than two competing bells.
- Privacy that carries: a members-only photo stays members-only wherever it appears.
MediaVerse names this pairing in its own companion register, where the entry reads: Media uploads and albums visible on member profiles and in activity feeds.
You do not need it
MediaVerse runs standalone with its own member library, profiles and galleries. BuddyNext is detected at runtime: present, MediaVerse hands over; absent, none of this appears and nothing breaks.
More about BuddyNext is on buddynext.com.
Run BuddyNext? Add the media layer.
The free plugin covers uploads, albums, privacy, galleries and moderation. Nothing expires and nobody counts your members.