Forum Replies Created
-
Posts
-
Do you WANT to offer a free membership level?
https://simple-membership-plugin.com/offer-customers-free-membership/Gotcha, didn’t immediately see those tabs…
The button behaves in the manner you described… nothing happens. When I inspect the (Buy Now) code for the PayPal VS Stripe buttons… I noticed that the Stripe buttons don’t seem to have any “submit” action in the button code!
Did you correctly copy all of the button code?
https://simple-membership-plugin.com/create-stripe-buy-now-button-for-membership-payment/Have you always had that tabbed payment page? Have you tried putting the payment buttons on different pages?
@Sam, as of this morning, the button works “as expected” for me:
https://pasteboard.co/HctgS2X.png
Windows 10 Pro, and Chrome.When the debug option is checked, does it affect the way the plug-in works in any way?
The only effect of having debug turned on, is that it uses disk space on your server; as it records the plugin’s activities.
I noticed in your documentation that there is way to setup WP Super Cache and W3 Total Cache so that they work with Simple Membership. I’m currently using WP Fastest Cache, but do you think there may be a similar setup issue with that one that could be causing the PayPal problem?
The idea with the caching plugin adjustments, is to not cache pages that use the swpm_in_use and wptouch_switch_toggle cookies. This affects content protection, and proper detection of whether or not a member is logged in.
Also do you know of any known issues between MailPoet 3 and your plug-in?
Are you using any particular SWPM addons?
What O/S, browser and version are you using? Please provide links and instructions on how to recreate the issue.
You (the Admin) must log into the Stripe Dashboard and manually cancel the subscription for the member. It’s a “Stripe thing.”
The “normal” registration flow for SWPM is for the user to pay for their membership first, then the registration link is sent to whatever email address is given to PayPal:
https://simple-membership-plugin.com/wp-content/uploads/2018/02/standard-membership-registration-process-1.jpgAlternatively, they can register first, pay for their membership, and PayPal tells the plugin to “upgrade” them to the appropriate level:
https://simple-membership-plugin.com/wp-content/uploads/2018/02/membership-registration-option-2-flow-chart.jpgIn order to implement the second scenario, follow these instructions:
https://simple-membership-plugin.com/allowing-members-create-account-prior-completing-membership-payment/You can use combinations of these PHP “tweaks,” to selectively show menu content. However, you’ll have to “get your hands dirty” and do some PHP coding.
https://simple-membership-plugin.com/simple-membership-miscellaneous-php-tweaks/The primary obstacle to implementing redirection as an option, is reliability. Whatever solution offered has to work 100% of the time, across every platform.
Using a Meta refresh to redirect requires placing an http-equiv Meta tag in the Head section of every protected page. However, this method is browser dependent; and the “brief flashing” of the screen may induce an epileptic seizure in the user.
Using JavaScript redirects is not fool-proof either. The action may give a false positive to a browser’s ad-blocker or popup-blocker.
PHP redirects will always work; but must be positioned in the code, before any other markup codes or characters are sent to the user’s browser. A poorly designed theme or “rogue CSS” will cause the browser to display a “white screen of death,” with a 1 line error message, saying that headers have already been sent (or equivalent).
And of course, there are various server and scripting language dependent solutions as well…
You use sandbox mode to test the payment transaction part, between PayPal and the plugin. That is the sole purpose of the sandbox mode in the plugin.
You create a free membership level and test the signup/registration process that way. And you will receive all of your expected emails.
When “going live,” the same code segments are used. Yes, it’s a pain to some people and may appear to be clunky. But really, how many times, or how often, does a person have to run something in sandbox mode to be satisfied they have it configured correctly?
…I have never seen paypal send out activation emails to create accounts on external websites…
“Activation emails” are sent by the plugin, not by PayPal. Payment receipts are sent by PayPal.
By reading the following threads, you will determine that the “normal” Sandbox behavior is for PayPal to send an IPN to the plugin; which ends the transaction testing between PayPal and the plugin. But because the plugin itself is in sandbox mode, the IPN validation will fail; which is why no activation emails are sent.
The purpose of Sandbox testing, in the plugin, is to ensure the communications between PayPal and the plugin are working correctly. Sandbox testing does not test the emails; because PayPal sandbox addresses cannot receive external emails.
You must have PayPal IPN properly setup:
https://simple-membership-plugin.com/enabling-paypal-ipn-feature-in-your-paypal-account/
You should also have the debug logs turned on, and the plugin in “Sandbox” mode.Please be more specific.
1. “Events Manager” is a plugin?
2. Is “Force Sync” a plugin or setting someplace?
3. What “does not work” when you turn sync on?
4. What is “WP User?”
Please check:
WP Membership –> General Settings –> Pages Settings- For each of the 5 fields, especially “Registration Page URL ” there should be something filled in.
- And on the WordPress “Pages” screen, there should be matching pages for each of those fields.
- For each of the 5 fields, especially “Registration Page URL ” there should be something filled in.
