Installing plugin on a separate WP
Syncing two separated WP Instances users
For those of you who are thinking about separating fCommunity from your core WP Instance (Primary) and splitting these instances between two domains (Primary and Secondary instances) I encourage you to check the below solutions for that but also read this Starter Guide if you are just starting with this Fluent Community plugin.
Note: I am not sure if we can easily install fCommunity of the naked/apex domain without the /portal slug - in this case the /portal slug wouldnt be needed at all since the separated fCommunity WP instance would be responsible only for fCommunity.
Note: splitting fCommunity on a separate WP instance might be a great approach for some security reasons (you can easily protect your FluentCRM data in the Primary WP Instance) - this case is a little bit different from Multisite installation but I guess you got my point here.
If you are looking for Pros and Cons of using a Subdomain for fCommunity read this external article - I like that guy post.
- WP Remote Users Sync plugin - demo link
- Share Logins - I wish the Fluent Auth would have all those features so no additional plugin is needed to link and sync WP users on a separated instances - demo link
I am also awating for any hint from the fTeam: how the separate WP instance can be implemented - what is the best practice.
Let me know what are your thoughs or you can share any other way how you connect your splitted WP instances with one WP core (Primary) instance = Singe Source of Truth
+1
The thing is that you cannot set portal as homepage on wp instance because portal doesn't appear in pages as a regular page. If you could do that, it would be easy to use fluent community plugin only on a separate site avoiding using any theme at all. It would be perfect but I guess it won't happen. Alternatively you could iframe portal from subdomain on a main domain site, and syncing users with remote user sync plugin works, but I guess it wouldn't sync fluent community users on each site until the user logs in on each site, unless there is some wp profile meta for fluent community users and then these metas could be synced with remote users plugin too. I'm using remote user sync plugin for a long time and it's great, you can sync many things from users meta if they're coded properly. But logging in and out synchronization wouldn't work as smooth as it does with /portal solution.
Rosvaldas Nudas, probably there could be some tweak done with .htaccess RewriteCond/RedirectMatch rules but as you mentioned above this is the way it is.
Just adding a link to a post here for using fCommunity without /slug
Just make sure you install the fCommunity first with the default /portal slug and then add the code snippet to get rid of the slug and have your community with your apex/naked domain
Note: in case of 404 error just save your wp-admin > permalinks again - it should fix this issue