BuddyNext Pro Eventonomy
BuddyNext + Eventonomy
Events your members RSVP to without leaving the feed.
What happens when someone uses it
One action, everywhere it lands
A member taps Going on an event card in the feed
- The event card The headcount goes up for everyone looking at it
- The feed An "is attending" card, so other members see who is coming
- The organiser A notification naming who is going, grouped per event
- Their profile The event moves into their Going bucket
The bridge self-guards on Eventonomy and quietly does nothing when it is not installed, so none of this appears until you turn it on.
What it changes
Your community with Eventonomy in it
Each of these is something a member can do the day you turn it on, and what it changes for whoever runs the place.
-
RSVP from the feed, without opening the event page.
What changes
The drop-off between seeing an event and committing to it disappears, because there is no page load in between.
-
See how many people are already going before deciding.
What changes
Events fill the way they do on the platforms members already use, where the headcount is the thing that convinces them.
-
Find every event they organise or attend on their own profile.
What changes
Nobody has to keep a separate calendar to remember what they signed up for, which is where attendance usually leaks.
-
Get told when an event is moved, cancelled or they come off the waitlist.
What changes
The reminders arrive in the same bell as everything else, so a rescheduled event does not depend on somebody reading an email.
How it works
The flow, step by step
- 1 Someone publishes an event in Eventonomy. The bridge posts a typed event card stamped with the space it belongs to and adds it to community search.
- 2 A member hits Going on the card. The RSVP posts to BuddyNext, the headcount refreshes for everyone, and an attending card goes to the feed.
- 3 The organiser gets a notification naming who is going. Repeat RSVPs merge into that one row instead of arriving separately.
- 4 Editing the event refreshes the card in place rather than leaving a stale one. Cancelling it withdraws the organiser card and every attendee card with it.
For developers
The bridge self-guards on the partner plugin and no-ops when it is absent. Key hooks: evnm_after_create_event, evnm_after_create_rsvp, evnm_notification_dispatch.
If Eventonomy is not installed
Nothing renders and nothing breaks. The bridge checks for Eventonomy before it registers anything, so on a site without it the Events tabs, the rail link and the sidebar widget simply do not exist. The inline RSVP buttons have a second check of their own: if the RSVP service is not reachable the card shows a "View event" link instead, rather than buttons that fail when pressed.
What to check once it is on
Publish a test event in a public space and confirm the card reaches the feed with its cover image and date. RSVP as a second member and watch the headcount change without reloading, then check the organiser received one notification naming that member. Finally cancel the event and confirm both the organiser card and the attendee cards disappear, since that is the path most likely to leave debris.
Eventonomy questions
- Do members have to leave the feed to RSVP?
- No, and that is the main reason this bridge exists. A signed-in member sees Going and Maybe on the card itself for any future event, and the headcount updates for everyone without a page load. Guests and past events get a link to the event page instead.
- Does every RSVP post to the feed?
- Only "going". Maybe and Interested do not post a card, and changing your answer away from going retracts the card you already posted. Interested stays private to the member on their own profile.
- Will members get told twice about the same event?
- No. Five notification types are mirrored into BuddyNext: reminders, reschedules, updates, cancellations and waitlist promotions. The RSVP confirmation is deliberately left with Eventonomy, because it already sends that one.
- What happens to feed cards when an event is cancelled?
- They are removed, including every attendee card, not just the organiser one. That matters because attendee cards are posted per member, so a cancellation that only cleaned up the original would leave the feed full of people attending an event that is not happening.
- Is the events tab on every space?
- It appears on a space only when that space has at least one upcoming event, so a space that does not run events is not given an empty tab.
- Does this work in the mobile app?
- Yes. The same event buckets are exposed over REST, so the app renders the member Events view from the same data as the website.
Turn it on
Setup
Default on. Install Eventonomy and the bridge wires itself up; no BuddyNext setting to switch. Event, RSVP and calendar behaviour stays in Eventonomy.