Hi! I found an iPad-specific sidebar issue in FluentCommunity.

On iPad in portrait mode, the sidebar opens as an overlay. If the sidebar content is longer than the screen and I try to scroll down inside it, the page behind the sidebar scrolls as well, which causes the sidebar to close.

In landscape mode, the sidebar stays fixed on the left and works normally.

Tested in both Safari and Chrome on iPad, with the same result.

It seems that scrolling inside the mobile/tablet sidebar is propagating to the underlying page instead of being contained within the sidebar.

(Flunt Community 2.8.0 version)

It would be helpful to have more control over the sitemap. Option to exclude selected spaces and topics from the sitemap and assign priority levels. This could help to save crawl budget, allowing high-quality, valuable posts to be indexed faster, remain in organic search results longer, and achieve higher rankings in serp.

Shahjahan Jewel  The "Install app" button is not showing when on mobile with Firefox (on Android). I had no problem to see it in Chrome and install it on my phone.

I am looking for an expert to migrate my entire stack (Learndash + Buddyboss + some Automator workflows) to FluentCommunity. We already use FluentCRM and FluentForms. If you know someone to recommend, please kindly DM me.

Sorry if this is the wrong forum

There is a huge gap between 'Install App' button and 'Feed' if we set it to 'Sidebar Top' position.

Test device width is 384 px.

When navigating to a space, the pinned item does not appear to follow the selected Layout View settings. It continues to display in Timeline or full‑post view even after switching the layout. As shown in my uploaded image, I have already set the layout to List. If this behavior is intentional, I kindly hope you might consider adding an option to adjust it. For longer posts, users need to scroll quite far to reach the next item, which can be inconvenient and results in a less optimal user experience.

Posting this as a translator rather than a bug hunter: I maintain the German
catalogues for FluentCommunity, FluentCommunity Pro, FluentMessaging and
FluentPlayer (about 5,000 strings), and after updating to 2.8.0 I went through
every new and changed string. A handful of English source strings look
unintentional. All line numbers are from 2.8.0 / Pro 2.8.0.

Happy to send a PR for any of these if that is easier for you.

New in 2.8.0

1. A placeholder key is shipped as its own text

fluent-community/app/Services/AdminTransStrings.php:143

'__FLUENT_CART_DESC__' => __('__FLUENT_CART_DESC__', 'fluent-community'),

The UI shows the literal string __FLUENT_CART_DESC__ where the FluentCart
description used to be.

In 2.7.7 the same block held real text one line further down than the FluentCRM
description: AdminTransStrings.php:107 carried Send targeted onboarding
emails… and :108 carried Monetize your courses and spaces by creating and
selling products directly in your community using FluentCart. In 2.8.0 the
block sits at :141–:145, __FLUENT_CRM_DESC__ still has its sentence at
:142, and __FLUENT_CART_DESC__ at :143 has been replaced by its own key.

The neighbouring keys (__COMMUNITY_ACCESS_LABEL__, __EMAIL_SUB_DESC__,
__FLUENT_CRM_DESC__, __IMPROVE_DESC__, __PERMALINK_CHANGE_DESC__) are all
intact, so this looks like a single lost line rather than a pattern change.

2. Singular where the previous wording had a plural

AdminTransStrings.php:55 — Get Feature Update via email

This was Get Feature Updates via email at AdminTransStrings.php:43 in 2.7.7.
The checkbox subscribes to a stream of updates, so the plural reads better; more
importantly, changing it dropped the existing translation in every language.

3. Hyphen used as a dash

AdminTransStrings.php:130

You are in a grace period, so everything keeps working for now. Updates and
support will end soon - renew your license to keep them.

A hyphen-minus between spaces. An em dash, en dash or semicolon would be
typographically correct, and translators tend to copy whatever the source does.

Older, still present in 2.8.0

4. A missing first letter

fluent-community/app/Hooks/Handlers/CustomizerHander.php:81

'order color of the secondary sections' => __('order color of the secondary sections', 'fluent-community'),

Should be Border color of the secondary sections. The line directly above it
reads Border color of the main sections, and this one is the description for
the Secondary Border Color field, so the intent is unambiguous.

(While in that file: the filename itself is CustomizerHander.php, missing the
l in Handler. Cosmetic, but it makes the file hard to grep for.)

5. A sentence with an orphaned comma, a wrong verb form and a stray word

fluent-community-pro/app/Services/Integrations/FluentCRM/AddBadgeAction.php:71

If you enable this, . The newly created user will get the welcome email send
by WordPress to with the login info & password reset link

Three things at once: the , . after "this", send where sent belongs, and
to with where only with belongs. Suggested:

If you enable this, the newly created user will get the welcome email sent by
WordPress with the login info and password reset link.

6. Subject-verb disagreement, four times

fluent-community-pro/app/Services/Integrations/FluentCRM/ContactAdvancedFilter.php

7. Missing verb

fluent-community/app/Http/Controllers/SettingController.php:314

FluentPlayer is required pro version of FluentCommunity. Please install
FluentCommunity Pro first.

Suggested: FluentPlayer requires the Pro version of FluentCommunity. The
parallel message for FluentMessaging six lines above is already correct.

8. Stray capital and a dangling preposition

AdminTransStrings.php:88 — Please Provide a license key of

Four lines below sits Please provide a license key, correctly cased and
complete. The of suggests a product name is concatenated onto the end at
runtime — see the note on fragments below.

9. Wrong preposition

fluent-community/app/Services/TransStrings.php:569 — Describe about this quiz

Suggested: Describe this quiz.

10. Inconsistent ellipses

TransStrings.php mixes dot counts in otherwise parallel strings:
Loading..... (five), Please wait.... (four), Loading editor. Please wait.... (four), Please wait while we redirect you to the appropriate page..
(two), against the correct three-dot form used everywhere else. Each variant is
a separate catalogue entry that has to be translated separately.

One structural request: please avoid split sentences

Several strings are sentence fragments that get a value concatenated onto them
at runtime:

• Are you sure you want to change the URL of your portal to + URL
  (AdminTransStrings.php:17)
• Please Provide a license key of + product name (AdminTransStrings.php:88)
• The Blazing-Fast ⚡️ Community Solution for + name (AdminTransStrings.php:111)
• license has been and expired at as two separate strings
  (fluent-community-pro/app/Services/PluginManager/FluentLicensing.php:316)

German, and most other languages, cannot always keep the value at the end of
the sentence — word order and case endings depend on what follows. A single
string with a %s placeholder solves this completely:

// instead of two fragments plus concatenation
sprintf(__('Are you sure you want to change the URL of your portal to %s?', 'fluent-community'), $url)

And a thank you

2.8.0 changed Item %d of %d to Item %1$s of %2$s and did the same for
Photo. Positional placeholders are exactly what translators need, because the
order of the two numbers is not the same in every language. More of that,
please — and the new aria-label strings in this release are very welcome too.

Currently, when a user updates their profile picture in FluentCommunity, it automatically updates their contact profile picture in FluentCRM, which is GREAT.

It would be really nice if the same synchronization also applied to Fluent Boards.

That way, when a user changes their profile picture in FluentCommunity, the new picture would automatically be reflected across the whole Fluent ecosystem:

FluentCommunity → FluentCRM → Fluent Boards

A small integration, but a really nice touch for keeping user profiles consistent across all Fluent products. 🙌

This one has been on the wishlist for a long time, and it is finally here.

Your members can now install your community on their phone. Not a bookmark. An actual PWA app. Your icon on their home screen, your name under it, and no browser bar wrapped around your content. They tap it and they are in.

The way it works is simple. There is a new Install App entry in the portal sidebar. Your member taps it once and that is the whole setup. No app store, no review process, no waiting for approval from anyone.

You get to decide how it looks. Set your App Name, a Short Name for the label under the icon, a Splash Screen Color for the moment it loads, and upload your own App Icon. The icon uploader checks the dimensions for you, so what you upload is what installs cleanly. The app follows your community theme too, light mode or dark, and the title bar keeps up.

Think about what this changes. Your community stops being a tab someone forgets to open. It sits on the home screen next to everything else they use every day.

Also in 2.8.0:

• Unlisted posts. Hidden from every feed and listing, but the direct link works fine. Good for meeting notes, drafts, and things you only share when asked.
• Sort direction on member and student lists. Oldest members first, newest first, A to Z, your call. It remembers what you picked.
• FluentCRM bounce suppression. Community emails skip addresses your CRM has marked bounced or complained, and members get a re-confirm button to switch notifications back on.
• Signed plugin updates. From now on, your site verifies that an update really came from us before it installs anything. Read more in the release post.
• Over twenty bug fixes, a full access control audit, and WordPress 7.1 compatibility.

Check out all the new features with screenshots here: https://fluentcommunity.co/blog/fluentcommunity-2-8-0/

More cooking 🙌

Are we able to restrict a space to a limit of members?

For example, only 12 members can join this group.

When a person leaves, or is kicked out by admin, then another can join.

I can do it if I paywall a product, and put a limit on the product.

but I want to create a donations page for a specific space, And after the donation, they join the space. But capped to a number.

Is this possible, if not, can we make it possible asap?

Thanks