Forum Replies Created
-
Posts
-
The issue almost always happens when there is some incorrect data in the CSV file. So try with just a couple of user entries in the CSV file at first. So do a test run with basically the same info that’s already there. Then you can delete the member records (if you want to) that you added as a test. When you can see a basic version that works and your version that doesn’t work, you will be able to re-check the data inside the file and see which row or column has incorrect data so it can be corrected.
The fancy5 option works best when all the products are symmetric. So it is not suitable for this site.
Can you test with some of the other options to see if any of those other ones work for your current product set? For example: try the following fancy options:
Fancy 3
Fancy 11
Fancy 13
Fancy 14
Fancy 17The plugin doesn’t use any old PayPal buttons. It uses the standard PayPal checkout API. That’s the most stable and widely used product of PayPal (it always works). There are various other APIs that PayPal introduces from time to time and then they sometimes discontinue it later. For example, the smart checkout API has already been changed and renamed by PayPal to express checkout API. We created a separate plugin for it:
We generally don’t want to change our eStore’s standard PayPal API because it is the most widely used product of PayPal and it always works. We use our eStore plugin on our own sites. We have been using it for 10 plus years now. For us, stability is more important than a fancy look that may or may not be there after couple of years.
Sidenote: the description, video and screenshots on the WP eStore’s landing page shows exactly how that plugin works. It will do exactly that. The description says that our eStore plugin uses the Standard PayPal checkout API.
Please copy and paste the exact text/message (to make sure we are looking at the correct message) that needs a CSS class or ID. We will take a look and work on it.
The “underscore” character issue you explained is a theme related issue (due to the font it is using). You can do the following test to verify it:
Then you can request the theme developer for potential solutions (if the CSS tweak you added isn’t helping).
Are you referring to the custom fields you created? Custom fields as email merge tag will not work if they have non-alphanumeric characters. Which post did you follow to create that email merge tag for your custom fields? Please post the link that you followed here so I have a reference.
First thing I noticed is that you have some redirects set up on this site which needs to be turned off. These redirects (if not done correctly or if they are creating a conflict) can create a loop and cause login issues. Please deactivate all plugins and disable any redirects you have configured (maybe using a .htaccess file or via cPanel).
Is there any caching happening on this site? I will take a look at the setup to see if I can spot anything else. I will send you an email for it.
I will try to recreate the issue on your test site which might help me get additional clues about this. I will send you an email for it.
Do you have any URLs in the settings or in the after login redirection configuration that is mixing up “http” and “https”? If you go from “http” to “https”, the login session will drop for security reasons. Sometimes when a site switches to using an SSL certificate, there are some URLs in the configuration (saved previously) that are still using the old “http” format which will cause the issue. So make sure to check all the emember configuration pages and update the URLs if it applies to you.
Also, are you using the following feature? If you are, temporarily deactivate it to make sure it is not conflicting with another plugin:
Using eMember with Another Plugin That Uses the WordPress User Roles
You may have enabled the “Disable Simultaneous Member Login” option. That option can also cause this type of issue on some server configuration (where the IP address is not being passed correctly to the plugin). Try disabling that option.
The following messages are actually a response from the MailPoet plugin. Our plugin calls their signup function and then if there is an error, it shows what error MailPoet replied with:
FAILURE :MailPoet signup error: Can't subscribe to a WordPress Users list with ID 1.FAILURE :MailPoet signup error: This subscriber already exists.So this is somewhat setup/configuration related issue. MailPoet won’t let you subscriber the same user twice. So if you are testing with an email address that is already on the list, they will give that error. I think their plugin has an option where you can allow the duplicate subscription to go forward (and not generate that error).
