Hey guys! I just dropped the second episode of my series How to run your client agency 100% on WordPress using Fluent Plugins!

The other episode will be coming in the next days, so don't forget to subscribe to my channel to not miss it!

Hello!

I have a problem that on iOS – when I add a PWA shortcut and enable notifications, the pushes work for 1-2 days and... then stop.

I delete the shortcut, accept notifications again, it works for 1-2 days, and so on in a loop.

This is not related to my device because everyone on the portal using iOS devices has the same issue.

Does anyone else have this? Do you have any suggestions for solving the problem?

We can use FluentPlayer when we enable video upload, but there is no option to embed an existing FluentPlayer media

I maintain the German catalogues for FluentCommunity, FluentCommunity Pro and
FluentMessaging, and I went through the new strings after updating to 2.11.0.
The space menu is a fine addition. Two things in it need a look, and the first
one is a regression.

1. Four strings never reach the translation map

The portal hands the map to the bundle as
js_vars['fluentComAdmin'] with 'i18n' => TransStrings::getStrings()
(PortalHandler.php:486 and :977), and the bundle resolves a string with
window.fluentComAdmin.i18n[t] || t. What is not a key in TransStrings.php
is therefore returned unchanged – English on an otherwise translated screen,
with no warning anywhere.

I checked every string that reaches this map from all five shipped bundles –
app.js, admin_app.js, onboarding.js, customizer_app.js and the Pro
bundle – against fresh .pot files for fluent-community,
fluent-community-pro and fluent-messaging. That includes the calls through
the minified module-local helper
(function W(e){return window.fluentComAdmin.i18n[e]||e}), which looking for
$t() alone would miss: 41 such calls in app.js, 53 in admin_app.js.

Four strings, and only four, are in no catalogue:

None of them appears in any PHP file of either plugin, so the fix is four lines
in TransStrings::getStrings() – the same map that already carries their
neighbours on the very same screen (Primary Menu, Secondary Links,
Both rows, as members will see them). Not AdminTransStrings.php: that one
is generated and serves the settings screens in wp-admin.

The fourth one is a regression. In 2.10.01 that setting was translatable,
and so was the heading above it:

// 2.10.01, app/Services/TransStrings.php
737:  'Enable group chat for this space members' => __('Enable group chat for this space members', 'fluent-community'),
887:  'Group Chat?' => __('Group Chat?', 'fluent-community'),

In 2.11.0 both keys are gone from the file, the wording changed to
Enable chat for this space's members, and the new wording was not added back.
For a German site that means a line which read "Forenchat" in 2.10.01 now reads
English. Rewording a string is fine – it costs the old translation, and that is
the translator's problem, not yours. Dropping the key on the way is what turns
it into a defect.

Worth a grep at your end: if the rename happened by editing the component and
not the map, other strings may have travelled the same way.

2. The menu preview draws the wrong space icon

The preview at the top of the Menu tab shows the space name with its icon. For
a space that uses a shape, it draws the empty-avatar placeholder instead –
a plain coloured circle, where the portal shows the shape.

FluentCommunity supports three icon sources, and a space stores exactly one of
them (logo, settings.emoji, settings.shape_svg). The portal checks all
three:

// app.js
… emoji ? <span>{emoji}</span>
: shape_svg ? <span><div innerHTML={shape_svg}/></span>
: <fallback>

The new preview checks two:

// admin_app.js, the menu preview
spaceProfile.logo ? <img src={logo}/>
: spaceProfile.settings?.emoji ? <span>{emoji}</span>
: <span/>          // empty placeholder – shape_svg is never consulted

So the preview is accurate for spaces with an uploaded logo or an emoji, and
wrong for every space using a shape. On my installation that is the space I
opened the tab from, which makes the preview look broken rather than
incomplete.

There is already a component for this. It takes
config: {emoji, logo, shape_svg} plus a fallback_mark, and its own markup
builder has the full chain:

this.emoji ? `<span style="font-size: 20px">${this.emoji.trim()}</span>`
  : this.shape_svg ? '<i class="fcom_shape el-icon">' + this.shape_svg + '</i>'
  : this.fallback_mark

Reusing it in the preview would fix this and keep the two in step the next time
a fourth source is added.

Why this matters more in the preview than elsewhere

The preview exists to answer one question: what will members see? A preview
that silently differs from the real thing is worse than no preview, because it
is trusted. Same for the hint text under "Secondary Links": it is the one line
that explains how to move a link there, and on a translated site it is the only
English sentence on the screen.

Happy to send a PR for either part.

It'd be pretty awesome to add Reddit login to FluentAuth... any chance of that happening?

Just wondering if anybody's integrated FluentAuth with FluentForms login forms or registration forms?

roadmap/feature requests - up in the header

I know there's a feature request somewhere on a website somewhere. 😁

I waited for like 12 months before pulling the trigger on which app to go with for my online film school based on Fluent Community.

TWO BIRDS CODE was the winner.

And how they delivered!

My new iOS app is live in the app store. Two Birds stuck with me through all the details until it was live. The WordPress admin side of the app is everything I need.

Extremely happy with their offering. If you've been on the fence, this is the answer.

https://www.twobirdscode.com/the-app/

I manage an online community on FluentCommunity and I've been using the Group Chat feature (FluentMessaging) introduced in 2.4.0. I have several requests related to this feature.

1. Email notification – missing group name and content control

Currently, when a member receives an email notification for a message in a group, nothing distinguishes it from a private message (DM). When several members have written in the group, the email displays multiple sender names with no context — the recipient has no idea which group it refers to or why these people are writing to them.

It would be essential for the group name to appear clearly in the notification. While exploring the code, I noticed that the $community_name variable is already declared in the email template but never seems to be populated — which suggests this may be an oversight rather than a missing feature.

Additionally, for privacy reasons and to encourage members to come back to the platform to read their messages — as major social networks do — I have personally implemented a PHP snippet to exclude message content from email notifications. This would deserve to be a native option in the settings, allowing each administrator to choose whether message content is included or not in email notifications, for both DMs and groups.

1. Distinct notification preferences

Currently, email notifications for private messages (DMs) and groups share the same setting. It would be useful to control them separately, as is already the case for Spaces:

Enable/disable notifications for DMs
Enable/disable notifications per group individually

This would allow a member to receive notifications for private messages while choosing not to be notified for a very active group, or the other way around.

1. Group visibility and discoverability

Currently, a group is only accessible if the administrator manually adds members. There is no way for a member to discover that a group exists and request access.

It would be great to have visibility levels similar to what already exists for Spaces:

Visible — the group appears in a list, members can request to join, the admin approves or declines
Secret — current behavior, the admin adds members manually

These three points form a coherent set and all build on mechanics that already exist for Spaces. This would not be starting from scratch but logically extending what already works very well.

Thank you for considering these requests. I'm happy to provide more details if needed.

I'm aware these requests may not be relevant for every type of community, but for social-oriented communities they make a significant difference in member experience and privacy.

Questions for users and the team behind FluentCommunity:

1. Are people in the EU using this software and how do they comply ?
2. Data Erasure requests. How are you handling them ?
3. How about new Age Restrictions and so on ? How are you handling these ?
4. Profile deletion. What is kept, what is anonymized?

FluentCart quickly got the legal issues adressed it seems, no ? How about FluentCommunity ?

Thank you.