Forum Replies Created
-
Posts
-
The value to use should have a prefix of “price_”. Let’s make sure you are doing what the following documentation says:
https://simple-membership-plugin.com/sca-compliant-stripe-subscription-button/That is the new API that Stripe wants users to use going forward. So follow that one and let me know if you can create a subscription button correctly.
The following can be ignored:
[2021/06/02 17:54:30] – FAILURE: swpm_handle_wp_user_registration() – SWPM member account with this username already exists! No new account will be created for this user.The following is the real issue. That is the response from the MailChimp API. This is an error from mailchimp that you need to resolve with MailChimp. MailChimp may have added that email to their banned list and not letting you add that email. Try with a completely different email address.
[2021/06/02 17:54:31] – FAILURE: [MailChimp] Unable to subscribe. [2021/06/02 17:54:31] – FAILURE: Error=400: xxx@gmail.com was permanently deleted and cannot be re-imported. The contact must re-subscribe to get back on the list.Before doing a test, go to WP Users menu and Members menu and do a search with the email address to make sure there is nothing with that email.
That feature looks to be conflicting with your setup unfortunately. I have tested the feature myself and it works fine (when nothing else is affecting it). External/Conflict related issues are beyond the scope of this free support forum. Please try a different plugin and hopefully that will work better for your current setup.
The plugin is definitely triggering the following filter:
swpm_account_status_for_subscription_start_date_updateMaybe the custom code that you added to override the status is not visible (in the context of that operation). If the theme’s functions.php file is not loading when the IPN message is being received (since the IPN HTTP post a background operation) then it won’t really execute your custom code tweak. I will need to test this theory.
Hi, This will need to be handled using a paid support ticket so I can allocate some dedicated time to investigate your particular setup.
Hi, Sorry but any custom coding related stuff needs to be handled as a custom development job so dedicated time can be allocated by the developer and a proper response can be given. Otherwise, we won’t be able to really investigate the requirement and check the code then respond with a solution.
No, this wont’ be possible with our plugin’s simple payment button.
If the checkbox for a terms and conditions, that can handled using the following feature (not with the payment button):
https://simple-membership-plugin.com/adding-a-terms-and-conditions-and-privacy-policy-to-member-registration-page/It will get cleaned out after 24 hours (roughly). The email activation is a feature that is meant to be used while the user is actively registering/setting up the account.
The normal use case is the following:
The user should be submitting the registration form, then looking for the email to click on the activation URL.
The first thing to check is to make sure all the required pages are in place. See the following page for details:
https://simple-membership-plugin.com/recreating-required-pages-simple-membership-plugin/Next, check that the registration flow is setup correctly. If you are using free registration then you have enabled that option. If you are using paid membership then you have that configured also:
https://simple-membership-plugin.com/membership-registration-process-overview/Looks like the shortcode is being wrapped around with some hidden HTML code which is causing the weird formatting issue.
Please edit that page and view the block using HTML so you can see any hidden HTML code that is wrapped around the shortcode.
Remove any of those hidden HTML code that is wrapped around the shortcode (only keep the shortcode there). Save and update that page.
That should make the formatting be normal.
You can’t change any existing subscription agreement (for someone who has already agreed to it and it is ongoing). PayPal doesn’t let you make changes to prevent fraudulent activities. I will give you a simple: someone can make a user signup for a subscription showing a low amount, then change it secretly to charge a higher amount later. That will not be fair since the user didn’t agree to that subscription details at the time of the checkout.
If you make changes to a subscription button, it ONLY affects the future sign ups. The existing recurring payments will continue at whatever was agreed already (when they signed up).
A good practice is to make a NEW subscription payment button and then the new users can start to use that. The older users are grandfathered in (so they continue to pay the amount that they agreed at the time of checkout). If you want to force existing users to change the payment, then you have to cancel the subscription. They can signup using the NEW button and they will agree to the NEW subscription details in the process (in a transparent manner).
I have updated the plugin’s code so that the {membership_level_name} email merge tag can work for the “Notify User” feature. It will go out with the next release of the plugin.
Something else happened on your site (some kind of hiccup/conflict somewhere) for that user’s profile to behave that way.
I have explained a little more in terms of how it works below so you can understand why we don’t need to look at the “charge.failed” event for the recurring payments.
Normally, the plugin waits for a SUCCESS charge. Only then it will extend the duration by updating the start date. If a successful charge is not received in time, then the profile gets set to “inactive”. It doesn’t matter if “charge is failed” because they won’t get the additional time until a successful payment is received.
It is normal for a subscription charge to fail sometimes (it can happen for a variety of reasons). Stripe will retry that charge again after 24 hours or so. After a few failures, the subscription will be cancelled which will trigger the other notification that the plugin will use to “block” the profile.
Unfortunately, what you are looking for is not available in our simple plugin. You need to use a more heavy weight plugin that has the option you require. That’s the short answer.
Normally, the login page is supposed to show the “login details” of the member (that is the intended behavior). It keeps things simple. Some of our users customize the login page’s content to show “additional” information on that page. For example, the following addon has a shortcode can show the “welcome page/landing page” of the logged in member. The shortcode I am referring to can be found in the “Show the Member’s After Login Page’s Link” section of the following page:
https://simple-membership-plugin.com/simple-membership-miscellaneous-shortcodes-addon/
The shortcode can also be put on the sidebar widget of the site. This allows a visitor of the site to easily browse to the “landing page”.
The main thing is that our plugin are used in many different ways. Not everyone even has a landing page. So just trying to show landing page when a logged-in member goes to the “login page” won’t work for every setup of this plugin. It creates a complex “permutations and combinations” type issue. Instead, we have a shortcode that some users can use (if they want an easy way to show the welcome page to the members).
