Forum Replies Created
-
Posts
-
You mentioned that you are using the W3 total cache plugin. Did you do the following to make it compatible with the W3 total cache plugin?
For an existing subscription, it needs to be cancelled (since PayPal won’t let you change the amount of an existing subscription to prevent any kind of fraud). Then you can request the member to pay using the new payment button which will have the new subscription amount.
#1) Edit your shortcode and use the new Stripe SCA ready shortcodes as explained in the following documentation:
The correct shortcode to use is the following (once the SCA configuration is done):
[wp_pg_eStore_subscription_button id=”1″ gateway=”stripe_co_sca_subsc”]
Stripe is recommending everyone to start using the SCA ready checkout option so go ahead and start using. That is the one Stripe will be supporting in the future.
#2) To put a paypal subscription button, just use the standard paypal subscription shortcode explained in the following documentation:
How to Add/Create a Subscription Button for Recurring Payment
So you will have TWO buttons on that page. One for the PayPal subscription and one for the Stripe subscription. The customers can select the option they want to use.
#3) Once you setup the Stripe SCA subscription, do a test and let me know if you see any issue with failed payments. Keep the debug logging feature enabled when you do a test. So we can see if there was any issue with the transaction processing.
#4) If your post contains multiple links then the bbpress forum plugin (we use it for this forum) can mark that as spam.
This is a WP5.6 issue. WP has a ticket to fix this. It should go out with WP 5.6.1
https://core.trac.wordpress.org/ticket/52097
You can ignore that warning for now. It won’t prevent any functionality from working on your site.
I think you are talking about custom fields. It needs to be entered by the user or the admin via the interface of our plugin. It’s very tricky to handle custom fields. It can’t be imported from WP or from a previous plugin you may have used. Custom field/data importing is not an advertised feature of any of our plugins.
The issue will be due to the fact that you are trying to do something that doesn’t make sense in terms of how our plugin is supposed to be used.
I couldn’t fully understand what you are trying to do. So let me explain a few things and then I will ask a question:
#1) The following documentation outlines the standard registration process. this is how our plugin is supposed to operate:
#2) If a member has a user profile that is missing the “username” value, it means that the profile is not complete yet. Most likely the user didn’t receive the email (containing the special link) that was sent to them. So there is a manual option to regenerate and re-send that special link to the member so the user can try again.
#3) If you are importing a WP user, then the member’s account will already be complete as soon as it is imported. There is no need to use the “regenerate the special registration link”. So I am confused as to what you are doing here?
The following page explains how the WP import works. It simple imports the WP user record into WP eMember with the same details:
The profile is already complete at that stage.
I am not sure but to me it feels like you are trying to generate a link for a profile that is already complete as far as emember is concerned. Why are you trying to regenerate a link for a profile that is already complete?
The positive variations shouldn’t cause an issue. However, I haven’t tested the particular scenario you mentioned. So you should do a test first by creating couple of test products, putting them on a test page and then doing a test transaction.
A custom link in your menu item should work fine. It is just a URL. What happens when you click on that link in the menu?
Thank you for the log data. The script is processing everything correctly. That’s good to see. You have an email delivery issue on this server (which is why the emails are not getting to the inbox).
Fully read the following post which will be good information for you:
Use an SMTP plugin so emails from your server are sent via SMTP which will help with the delivery issue that you currently have.
Please check the eStore’s log file also which will contain more info in terms of the email sending. Check the eStore’s post payment processing log file and let us know what you see there.
Are you really using WordPress 4.8? or was that a typo? That version is about 5 to 6 years old. That version will have many issues and should be upgraded to the latest.
You can try the shortcode explained in the following page to show some of those details:
How to Retrieve and Show Specific Details of the Logged-in Member
I will take a look inside so I can check all the settings that you have set for this plugin. I will send you an email for it.
All PayPal transactions will generate the standard registration email that gets sent out from the plugin. The issue you are seeing is most likely because our plugin is not receiving the PayPal IPN notification so it is failing to process the transaction and send the email.
#1) First, check that the IPN feature is enabled in your PayPal account:
#2) Next, make sure that you don’t have any firewall or security plugin that can be blocking the PayPal’s IPN notification. Do the following test:
