Hello!

A few issues I've noticed:

1. After customizing my community colors, the toggle bar becomes buggy on mobile. (The default dark mode, which I haven't customized, works fine.) See screenshots.
2. Could we have the option to place the right-side widgets (Featured Posts, About, etc.) and the post editor inside bordered containers as well? Not sure why it's not possible. See photo.
3. (A reminder that) links don't generate previews (I know that it has been said before).
4. Profile avatar and banner sizing is still problematic. (I had written a post about it). See photo.

Thank you!

In my community, some users would occasionally have their pics show up sideways or upside down. It has happened sporadically over the past year or so. Today, it was happening to a pic I uploaded so I was finally able to see the problem and do some troubleshooting. In the end, I had Gemini vibe code a PHP snippet for me that fixes the rotation issue.

If anyone is interested, the snippet can be found here:
https://docs.google.com/document/d/14D3bvfQ7SekNYrbdnxFA9GxbZJcOrD8dmFlfgWCKc4g/edit?usp=sharing

After some investigation I found a simple way to make Dark Mode the default for new visitors without modifying any Fluent Community files.

Fluent Community stores the selected color mode inside the browser's Local Storage (fcom_global_storage). The idea is to set the default value only if the visitor has never chosen a theme before. Existing user preferences remain untouched.

I used the following PHP snippet in FluentSnippet -> Screensho

The snippet uses the fluent_community/portal_head hook, so it doesn't require any modifications to the plugin itself and remains update-safe.

Behavior:

• ✅ First-time visitors start in Dark Mode.
• ✅ If a user switches to Light Mode, their preference is preserved.
• ✅ If they switch back to Dark Mode, that preference is also remembered.
• ✅ No plugin files need to be modified.

Maybe this helps someone else who wants to use Dark Mode as the default theme

Would it be possible to add an option in the Community settings to choose the default color mode (Light/Dark/System)? I think this would be a nice addition for future versions.

Hello,

I believe I found the root cause of the missing translation strings in Fluent Community.

After inspecting the plugin source, it appears that many interface strings are already correctly wrapped with the Vue translation function ($t()), so they are clearly intended to be translatable.

However, a number of these $t() strings are never extracted during the build process and therefore never make it into the generated POT file. Since they are missing from the POT file, they are also missing from all PO files and cannot be translated using Loco Translate or any other standard WordPress translation tool.

This is why translation files can show 100% translated, while parts of both the frontend and backend still remain in English.

eg. showing in the screenshot

From my point of view, the issue is not related to the translation files themselves, but to the JavaScript translation extraction/build process, which appears to miss some $t() definitions when generating the POT file.

Could you please check the JavaScript i18n extraction during the build process and verify that all $t() definitions are compiled into the generated POT file?

This issue has been mentioned by users several times over the years. For communities running in languages other than English, it creates an inconsistent user experience because parts of the interface remain untranslated despite a complete language file.

Thank you very much!

The more I use Fluent Community, the more small features I'd love to see implemented to make our lives a little easier and the community members experiences a little richer.

Here are a couple that I'd love to see included in future updates:

Cross post (with user level access): All approved users to be able to cross post the same post in multiple spaces without creating duplicate posts (and showing duplicates in the feed). This would need to be limited to either user roles and/or specific users to avoid abuse.

Un-publish posts: Sometimes, you create a post that is relevant for a period of time, and needs to be removed from public view (without deleting the post). I'd love to see an 'up-publish post' option included. Again, this could be locked to user roles or groups to avoid abuse.

FCRM Tag For Downloaded Content: I make exclusive content available to my members and would love to be able to tag users in FCRM who download the file(s) for future marketing/promotion/feedback through FCRM.

Multiple tags per post: I know others have asked for this, but I'll add my support for it. We need to be able to tag posts with more than one tag for filtering.

This is invaluable for Communities with a lot of posts/content and will help to make things more engaging for members and potentially avoid having to create more spaces than needed just to organise content into silos.

Looking forward to hearing others thoughts on these suggestions and hearing what Shahjahan Jewel thinks of these ideas. :)

I was writing an email telling them to go to the login page and then to click the magic url button and then check their email, but if I could just send them the link that would be so much easier. Is that possible?

How do you add gamipress to community?

Could you give us the option to archive posts instead of deleting them? NB. would be nice to have an access to the archived posts list (backend and even frontend)

What will happen if I upload photos into post and switch to video embedder and insert youtube video for example? Can FC make post with photos and video in same post or video will overwrite photos?

Is there a way to import a batch of students to a course? I want to move all my students from another platform.

I swear I saw how to do this, but searching the forum and docs hasn't been fruitful.

edit: Syed has the answer in the comments. Its also in the docs here. I don't know why I am so bad at finding stuff in the docs.