In this article we go over what to do when members are being registered to the membership site and assigned to the correct membership level, but are not being automatically logged-in.
This article is relevant to the following plugins:
Before we go over what is causing the problem and how to solve it, please make sure you have set members to be logged-in after the registration inside the plugin’s settings.
You will find explanations on how to define the login after registration settings in each of the above plugins right below:
Quick Navigation
Wishlist 1-Click Registration
The first thing you need to check is that the registration link / signup form you created using Wishlist 1-Click Registration includes the automatic logging setting.
Go to the Generator tab > Login After Registration and make sure it is set to “Yes”.
If the login after registration is set to “No”, you will need to change it to “Yes”m generate a new link and test it by following the below steps:
- Go to Wishlist 1-Click Registration under the Generator tab
- Generate a new link / signup form and make sure that the “Login after Registration” is set to Yes
- Now complete a test registration using the link / signup form you generated
If the automatic login still doesn’t work, continue reading “What is Causing Members not to be Logged-In?”
Wishlist Registration Widget
To check that the automatic login after registration setting is active go to the WordPress menu > Appearance > Widgets > Relevant sidebar where the Wishlist Registration Widget was added and make sure the “Log in after registration” is checked.
If the automatic login still doesn’t work, continue reading “What is Causing Members not to be Logged-In?”
Wishlist Greeting Registration
To check that the automatic login after registration setting is active go to the WordPress menu > Wishlist Greeting Registration plugin > Registration tab and make sure that the “Login After Registration” is checked.
If the automatic login still doesn’t work, continue reading “What is Causing Members not to be Logged-In?”
What is Causing Members not to be Logged-In?
Because members are registered to the membership site and assigned to the correct membership level, it indicates that the registration process has been processed correctly.
This issue is not related to any plugin that is using an auto-login feature, but it is related to how the WordPress users authentication system works.
This log-in system uses browser cookies that are being placed on the computer and authenticate the user as a logged-in user.
Because this system uses cookies, it must be called before any information is sent to the user’s browser.
Because the automatic login is not operated correctly, we can assume that an information was sent to the user’s browser before the authentication cookies were set.
This can only be caused by a plugin or theme that is not coded correctly and does not follow the WordPress coding standards.
Steps to Solving the Problem
Step #1:
In order to try and eliminate the problem please change your theme temporarily to the default WordPress theme and test the registration again.
If the problem is solved – Please contact the theme’s developers and let them know about the problem as they should know how to solve it (you can refer them to this article for further explanation).
If the problem is not solved – Please continue to the next step.
Step #2:
Try to disable all plugins except for Wishlist Member and Wishlist 1-Click Registration and test the registration process.
If the problem is solved – It means that one or more of the other plugins is causing the problem and now you need to find which plugin is it. To do it, enable the plugins one by one and test the registration after every plugin you enable. After finding the plugin, please contact the plugin’s developers and let them know about the problem as they should know how to solve it (you can refer them to this article for further explanation)
In almost all cases, one of the above steps will solve the problem.
Important Note
Please contact us and let us know about the theme or plugin that is causing the problem. Although we cannot solve it, as only the developer needs to change the code, we want to know about any plugin conflict for improving our support service.