Translating Slugs
I understand that someone might eventually provide a solution — even though the support hasn’t been the most responsive (no offense). That said, I’m facing a few minor issues with this otherwise great product.
Since not all communities will be for English speakers only, I was wondering how I can translate the slugs, as my community is in another language. I believe being able to translate or change the slugs is quite important.
For example, in my language, having “groups” inside “spaces” makes sense, but not the other way around. So the current structure doesn't work well linguistically. That’s why I’d really like to customize the slugs to fit the logic and language of my audience.
So, my question is: how can I change (possibly all) the slugs into my native language?
IMPORTANT: Changing the slugs should not impact search engines, the sitemap, or SEO in general.
Kind regards! ✌️
Changing slugs will break things as it's rooted in the core.
Shahjahan Jewel So, this product is for English speakers only?
Radu Not sure how the slug is a problem for non-speaking users? Facebook or other SAAS solutions are accessible for non-English users, right? And they all use English slugs in their URLs, and I think it does not matter.
All the strings in FluentCommunity are 99.99% translatable, and your users can see all the strings in the language you choose.
Shahjahan Jewel Facebook is multi-language. Not all communities are is English or multi-language. If a site is for Spanish speakers on a .es domain, how English slugs is a normal thing?
Anyway, from your answer there is no plan on fixing this. Maybe tell people this before they purchase the product. Because of this I cannot use the product anymore. Too bad, I really love this product.
Radu as I said, it will create lots of complexity if we make the slugs non English. By the way, for which slug you want to change? Any example?
Radu If you want to change slugs to a different language, use a plugin that does that. That is what they are for. This would be for any product out there. You must be kidding yourself.
Personally I don't care about the slugs, since like I said before, few users care. The ones that do tend to be tech savvy, so they don't care either. ;)
J V I got the impression that you were treating me like a hater. Trust me, I own all WPMN products with valid licenses. I'm simply trying to find a solution to my needs directly from the source, instead of searching Google for possible answers. Honestly, I don't think that I'm the only one with this issue. I don't know what to do to be honest, I don't want to go back to Discourse or similar softwares. 🫠
Radu Just adding a note, our internal url structure like /members /courses /leaderboards can't be changed with any plugin. These are hard coded.
Shahjahan Jewel Yes, I knew that.
J V WPMN is WPManageNinja, and as you can see the man himself Shahjahan Jewel cannot provide a solution, a php htaccess etc. workaround or something. As you said before, yes, many software does not give direct options on changing slugs, but they provide different tweaks and tricks to do so.
Not gonna lie, I'm heartbroken because this product is perfect in so many ways, and I cannot use it. It is what it is.
While searching for information on how to do exactly the same thing as Radu , I found this thread. It's clear that if the tool doesn't allow it, it's not the end of the world, but I think that if we're professionals, asking why it's needed isn't the best approach. So, I'll leave my explanation here, respectfully of course.
I appreciate the perspective regarding how platforms like Facebook handle slugs. However, I believe there’s a fundamental difference in use cases here.
While Facebook is a global social network, Fluent Community is a tool for creators to build branded, localized experiences. For non-English speaking communities (such as Spanish speakers), having hardcoded slugs like /courses/ or /spaces/ creates unnecessary friction and breaks the user immersion.
Localizing the UI is great, but if the URL structure doesn't match the language, the experience feels incomplete. It’s not just about aesthetics—it’s about user trust and accessibility. Providing the flexibility to customize these slugs would significantly improve the UX for international markets and help us maintain a professional, cohesive brand identity.
That said, we can work without any problem; as I said before, it's not the end of the world, especially in a globalized world. But it's true that after doing some testing, I've reached the same point as my colleague. 😎