Skip to content

FluentCommunity Integration ​

With FluentCommunity active, FluentEvent can run inside the community portal: events are posted in discussion spaces, members RSVP from the feed, and the portal gets an Events section.

Turning It On ​

The integration starts only when an administrator turns on FluentEvent in FluentCommunity → Settings → Features. FluentCommunity then fires fluent_community/fluent_event/init, and FluentEvent registers its portal, feed and space handlers (Modules/FluentCommunity/Bootstrap.php). With the feature off, FluentEvent runs standalone and the Community Portal API refuses every request.

The portal section lives under a base slug set in FluentCommunity's FluentEvent settings (default events).

Events Are Posts ​

An event in the portal is an ordinary FluentCommunity post with content_type = 'event' and the event ID in meta.event_id. FluentCommunity owns the post; FluentEvent keeps the event in step through FluentCommunity's hooks.

The link is kept in both directions: meta.event_id on the post, and an fe_meta row (object_type = event, meta_key = fcom_feed_id) on the event.

In the portalWhat FluentEvent does
An admin posts an event in a spaceValidates the event fields, creates the event in the space's calendar, links both ways, fires fluent_event/event/created. If anything fails, the post is deleted too.
An admin posts an event outside any spaceSame, in the shared Community calendar. Needs FluentCommunity's global posts setting on.
The post is editedKeeps content_type and meta.event_id on the post, whatever else changes.
The post moves to another spaceMoves the event (and its guests) to that space's calendar, fires fluent_event/event/updated.
The post is deletedThe event becomes a draft and keeps its guests. An admin decides whether to delete it.
The space is deletedIts calendar becomes a draft and loses its space link; every event in it becomes a draft.

Only users with manage_options can post events, and only in discussion spaces (type = community), not in course spaces.

One Calendar per Space ​

The first event posted in a space creates that space's calendar (meta.fcom_space_id), titled after the space and fired through fluent_event/calendar/created. Events posted outside any space go to one shared calendar (meta.fcom_global = true). Space calendars start private, so their events stay off the public WordPress pages.

Moving an event to another calendar in the admin moves its post too:

  • to a space calendar → the post moves to that space (its topics are dropped, since topics belong to a space);
  • to the Community calendar → the post moves out of any space;
  • to a calendar with no space → the post lets go of the event and stays as a plain post.

Who Sees What ​

Visibility follows the post. A member sees an event when they can see its post: the post is published, its author's profile is active, and the member can see the space (or the portal feed, for an event outside any space). Draft events never appear.

Entry typeLogged-in memberVisitor (portal open to visitors)
rsvpGoing / not going, and can change itSees the event; cannot RSVP
openRegister (name prefilled, email locked), can say not going and register againRegister by name and email; final
noneView only, meeting link includedView only

The meeting link of an online event shows only to guests who hold a seat (going or checked_in), except on none events.

Portal Routes ​

FluentEvent adds these portal routes. Filter them with fluent_event/community/route_paths:

KeyDefault path
eventsevents
create_eventevents/create
edit_eventevents/:event_slug/edit
event_viewevents/:event_slug
space_eventsevents (inside a space)
space_event_viewevents/:event_slug (inside a space)

It also adds an Events item to the main and mobile menus, and an Events tab to each discussion space header.

Hooks Worth Knowing ​

FluentEvent developer documentation