Best practices for FluentCommunity + WP User account creation/sync?
- TLDR; General thoughts on the "create user in WP" checkbox option? What did you choose and are you glad you did?
I am trying to wrap my head around whether or not I should check the "create a user in Wordpress"
Is there an easy way to decide which is the appropriate option?
My initial thought was: "of course, there should be a main authority list for everything" and that should be the list of Wordpress Users (Community members would be a subsection of those people)
But now I'm thinking, maybe I don't even need that? Maybe it's fine if most or even all community members are not registered Wordpress users. What is the advantage to them being both?
Adding wp users when I don't have to is probably never a good idea (I have a site with over 150,000 users and I know how it slows Wordpress) so maybe I need to understand why I would want to add them.
But I can't seem to think through all the scenarios and implications.
There is so much to consider.
- What if Community members think they are Wordpress site users and then don't have access to things on the site that Wordpress users do.
- What happens to their Wordpress account if they leave the community?
Or vice versa? - If I don't check "yes", will it be confusing to manage two sets of users, Wordpress and Community members? Isn't it easier to manage them all as wp users?
- Will I risk people being 'spammed' because they thought they quit the site but still get emails from the community or Wordpress blog post notifications?
- What happens to the community account if they are synced and a Wordpress user changes their email?
- Does it only add a user when there is a tag added? Is it possible to join the community without a tag being added? (If so, then not all community members will get Wordpress accounts, so why bother)
- etc,etc,etc...
I'm leaning towards not checking the box but the list of my questions is endless 😅
I'm not expecting answers to all these questions, but I'm hoping someone can recommend a video or article that discusses all the implications and pros and cons of creating wp users from community signups.
I am not sure if this will help but I dont want you to explode with too many questions in your head 😗
If you would like to avoid spammy accounts (created by bots) then its it better to do not select the checkbox: create user in WP and create users via your Woo store only (you can sell fCommunity access for $1 and bots wont cross this line: store etc). But this case scenario is not always the best.
More registered WP users (and their emails) = more possibilities for you when it comes to targeting them with your offer and making money.
What if Community members think they are Wordpress site users and then don't have access to things on the site that Wordpress users do.
All fCommunity logged-in members are Wordpress users with the Subscriber role (in general). You can limit access to pages/content for users by using tags (WP Fusion) and you dont need to display fCommunity Users your WP pages when they dont have your access tags (WP Fusion).
What happens to their Wordpress account if they leave the community? Or vice versa?
Users cannot just "leave" the fCommunity on their own. Once they are being logged with the fCommunity for the first time they will be able to access your /portal until their WP User account is being deleted or their fCommunity access is being blocked by the Admin/fAdmin (fComm > Members > Users List >Block).
If I don't check "yes", will it be confusing to manage two sets of users, Wordpress and Community members? Isn't it easier to manage them all as wp users?
There is only one set of WP users (wp-admin user is the basic entity) and everything else is glued to that user profile.
You can manage your users access with assigning them tags (WP Fusion+FluentCRM) and based on tags provide them access to pages as you set this up.
Will I risk people being 'spammed' because they thought they quit the site but still get emails from the community or Wordpress blog post notifications?
When you delete WP User account then they wont receive any notifications however users will stay in your WP Users (directory/list) then they will need to manage their notifications. When your users will be fCommunity users too other users can tag/mention them - users can configure what kind of notifications they want to get from fCommunity etc (/portal/u/UserName/notification-settings).
What happens to the community account if they are synced and a Wordpress user changes their email?
When you sync your fCommunity account with WP User/fCRM then the user wp-admin profile will be in sync - When a user change FirstName then that WP/wp-admin>user account will be sync (same with fCRM). When it comes to changing email you dont need to sync it just because a user has only one email assigned to the account (email will be sync automatically: wp-admin>Users + fCommunity + fCRM)
Does it only add a user when there is a tag added? Is it possible to join the community without a tag being added? (If so, then not all community members will get Wordpress accounts, so why bother)
You cannot join the community without WP User Account (unless you are talking about Public fCommunity and posts preview option without the possibility of commenting etc).
I am not sure about what Tag you are talking about: about fCRM tag? WP Fusion tag? DB fComm tag/flag (responsible for adding user access to fCommunity?
As Mat mentioned above, it is also my understanding that FluentCommunity users must exist as regular WordPress users.
Mat has already been very complete, but one thing that is annoying for users is that the account may be made but it comes without a password. So now you need to have them resetting their password first time they want in. As a user I prefer to just set up my account myself.
J V Something weird happened to me today regarding passwords.
I use Fluent Forms for user registration. The user can choose their username and password, which I pass along to WordPress by using the Fluent Forms integration with WordPress.
It's never worked until today. For a glorious moment, everything worked exactly as it should. The user registers and upon payment, they get redirected inside of my community. When they logout, they can login again using the password that they chose.
Then I made some change, not even knowing what, and it stopped working. I don't know what's interfering with it, as it SHOULD work.
So now I'm back to removing the password field and giving them a conditional redirect in Fluent Forms on successful payment which tells them to click a button leading to my password reset page.
I tried to recreate the successful method, but it eludes me. Now it's worse because I know it's possible for it to work correctly.
William Beem Oh that is just the worst. This terrible tease should not have happened. I feel for you.