Installing Fluent Community
I am currently creating a membership site running the Thrive Themes suite and Fluent CRM, and I an concious of various automations and loading on the WordPress installation. Is it prudent to install the community plugin onto a new installation of WordPress? in either a sub domain or sub folder?
I think it is. Every person who has an account on your WordPress site is a potential security vulnerability. That's because sometimes there are plugins or other issues that open opportunities for XSS attacks,SQL injection, etc. They can allow an attacker to elevate a user (Subscriber) permissions to Administrator. Social Warfare is a good example of a plugin that had a fault and allowed such escalation.
So I have a blog site and another WordPress installation for community, support, FluentCRM, FluentBoards, and anything where a user account is necessary.
Subdomain, not folder, because I want a separate WordPress instance.
William BeemΒ - in order to do that, then do you need to setup Webhooks or how is the information passed from the members site to the Subdomain containing the community and FluentCRM?
Chris ColeΒ In my case, the subdomain is the members site. Everything is on the same WordPress installation.
Now an exception would be if I have a signup form on my blog site that signs someone up to FluentCRM on my community site. That problem is no different than having a form on your blog that signs up someone to Mailchimp or Kit. People do it all the time.
William BeemΒ does this mean you can't display live community stats and content on your main wordpress site?
Ross HΒ Why would I want to do that? The main site is a publishing platform. I have two other WordPress installations for one of the domains - a community site and a client site.
I run FluentCRM and FluentBoards on the community and client sites. That's because my audience (community) is separate from my clients. It's just easier to give each group their own space so I don't have to worry about internal gymnastics with emails, boards, and CRM for different purposes. I don't run a community on my client site.
William BeemΒ just curious as to your use case. Quite a few requests from users to be able to show courses and spaces and stats from the community on their front end wordpress site. It's only really possible if they share a database. I don't need this either so will be running FC on a subdomain.
Ross HΒ I keep all the user interaction on the user installation. For clients, they can use FluentBoards front-end portal to see how their projects are going, add notes, etc.
If I wanted to allow community users to see those stats, I'd do it on the community site because all of the data is there. The primary domain is for blog posts, articles, and things like that. It's for the visiting audience who found me by SEO, YouTube, or social media posts.
Once on that site, my objective is to convert them into either a client or a community member. The client part is working and I'm still building the community site.
William BeemΒ - How do you connect your members site to the other WordPress installation (webhooks?)
So subdomain for members site
Root domain for Sales or Public pages
another subdomain for the Fluent Plugins etc?
Chris ColeΒ I don't connect the members to any other installation. There is a subdomain for community members. That has all the stuff they need to interact (FluentCommunity, Fluent Roadmap, FluentCRM).
The root domain is a blog. I publish articles there. Comments are open, so you don't need to be a registered user there. The only thing I need to connect is an email sign-up form that talks to FluentCRM on the community site to add them to my email list.
However, I decided that I'm not even going to do that anymore. Instead, my call to action on the blog will be to get people to join the community. I'm going to start them off for a LTD at $10 to help me build a base and also shape how the community comes together.
When I feel it's far enough along, the people who come later can subscribe for $5/month. All I need to do is put the registration link on the primary domain so they go to the community registration page.
It's sort of similar to how people push their Patreon page.
Chris ColeΒ Stop the confusion and put everything in one basket, if you keep creating subdomains, soon you will have 25 subdomain. Imagine the stress of log in and out to manage each and everyone of them. So keep it simple, plug everything into the root domain. It will make your life easier.
My rule is, anything that doesn't fit into my root domain, I don't install period.
I use Thrive Suits and other plugins as well. And all are housed in one domain.
Bryan WilliamΒ Thank you and I am now in agreement. I was unsire, but afte discussion here and a little research, I have decided to just go ahead and build into all into the one domain.
Marie Denee This is the thread you requested I tag you. There are other relevant conversations about using a primary or subdomain. Go to Search, check the option to search in comments, and use "subdomain" for the query.
There are voices on both sides of the issue. I'm in favor of subdomains for security, function, and resources.