Is there any method to nest groups (at least one deep)? I'd love to add subgroups within a group. 🙏

The wpmanagenaija community has an app.

Please I will like to have app on my community too...

Shahjahan Jewel, please which app do you recommend, cos I only install plugins you recommend

Hi, how to exclude the Fluentcommunity plugin from the Perfmatters plugin?

Hi everyone, hitting a login issue on my FluentCommunity site and looking for confirmation from anyone who's seen this before.

Symptom: users enter correct credentials but get "wrong credentials" error. Not a redirect loop, not a spinner — a clear error from the form. Affects everyone (paying members, admins, new accounts), happens both in browser and PWA.

Setup:

• WordPress + FluentCommunity (login at /?fcom_action=auth)
• Hosted on Rocket.net (server-side cache active)
• Cloudflare DNS-only, not proxied
• No caching plugin

My theory: the FluentCommunity login form is protected by a WP nonce (24h lifetime). I think the server cache is serving a stale version of the /?fcom_action=auth page with an expired nonce. WordPress rejects the POST, and FluentCommunity returns a generic "wrong credentials" error (doesn't expose nonce failures for security).

Evidence:

• Worked fine for several days, then suddenly broke
• Disabling/reconnecting plugins temporarily fixes it (probably purges some cache as a side effect)
• Matches the "Nonce has been renewed" pattern reported in other Fluent threads

Questions:

1. Has anyone hit this exact "wrong credentials" issue with FluentCommunity?
2. Is there a known list of URL patterns / nonce names to exclude from server cache for FC to work properly?
3. Does FC expose the underlying error somewhere (logs, hooks) so I can confirm it's a nonce failure?
4. Any way to refresh the nonce via JS before submission, or extend its lifetime for auth?

Already opened a ticket with my host to exclude /?fcom_action=* from cache. If anyone has been here before, I'd love to skip ahead to the solution.

Thanks!

New version out today. I had planned to release sooner, but the newest version of FCom delayed it... and it was worth it because I was able to extend one feature into the new Group Chat.

This one is mostly about giving community managers more control over how members use Fluent Messaging — who can reach staff directly, and how group conversations get started. Both new features are completely free. Join my community, download the plugin, and they're yours.

Here is what is new in v1.4.4:

DM Restrictions. Fluent Messaging gives you two choices for who can initiate a one-to-one message — any community member, or only mods and admins. If you want members messaging each other, you have to allow it for everyone. This bridges that gap. Set it to "Any Community Member" and then use DM Restrictions to prevent regular members from initiating threads with your admins, moderators, and/or space staff specifically. You choose which roles are protected — the three checkboxes are independent, so you can lock down community admins without touching space mods, or vice versa. Staff can always reach anyone, and members can still reply in threads that staff start with them. Requires Fluent Messaging.

Group Chat Controls. Fluent Messaging restricts group chat creation to moderators by default. This opens it up to regular members, with built-in oversight — designate one or more staff members who are automatically added to every member-created group. They show up visibly, can not be removed by other members, and the "Admin" label in group chat is relabeled "Owner" so the terminology actually makes sense. DM Restrictions also extends to group member add actions, so members can not sidestep the role blocks by adding restricted staff to a group instead. Requires Fluent Messaging 2.4.0+.

Both features live under a new Messaging Controls section in the Enhancements tab — no license needed, no paywall. Just join the community and grab the latest download.

Also in this release: space lock icon size fixed in Menu Styling, additional i18n coverage, and some code cleanup.

Full details in the changelog and the updated manual.

I have a site that has FluentCart and FluentCRM and I want to add a FluentCommunity with private and public spaces and courses.

There will be free courses and spaces available to all my WordPress users and paid courses and spaces accessible to all previous FluentCart customers.

All my existing users are already tagged with "free", "paid" and "pro" level tags.

What is the best way to get my existing and future customers and WordPress users into the community?

Do they need a new login for the community? or can I simply control access to the spaces and courses with their existing tags?

1. Mobile layout is everything for customers these days, does anyone else feel we’re losing too much to menus that should be hidden on scroll for user UX?
2. Also having the ability to shorten the ‘show more’ especially for more visual image/video communities? Currently a user post with a first comment could be 3,000 characters.. that’s with a show more on the users post

I got the groups migrating but the users are not migrating: "What criteria does the BuddyPress migration tool use to identify and import members? Does it require BuddyPress to be active? Does it look at specific roles, xprofile data, or group membership tables?"

but I could not get it to migrate the users. Strangely it only migrated the first few users that ever signed up out of 2700. I am wondering if this has to do with migrating from buddyboss to buddypress. BuddyBoss is not cool so we got off of it. Is there anyway I can sync the members?

We had a few issues in our last update (2.4.0), so here is a minor patch update. Nothing urgent, just some styling and CSS sanitization fixes.

Changelog:

• Fixed: Issue with custom CSS sanitization
• Fixed: Issue with FluentPlayer video upload
• Fixed: Checkbox checkmark not centered inside the box
• Fixed: Icon selector hidden for system menu items in Menu Group settings

Thanks for reporting the issues. Have a great weekend ahead!