[admin]

You can’t just hide the cart button since WooCommerce won’t process that partial protection shortcode the same way a WordPress post or page will.

The closest option would be to protect the product or cart page entirely using the following option:
https://simple-membership-plugin.com/full-page-protection-addon-simple-membership/

Once you fully read that page, you can check the following feature to see if that can work for you to protect the “checkout and cart” pages:

Locking Down Multiple URLs using URL Patterns

[admin]

Thank you. We will update this on the next release of the plugin.

[admin]

It’s uses for a particularity setup with the stripe subscription process. That code you are referring to isn’t used for PayPal at all.

Can you tell me what action is not working on your site so we can reproduce the issue?

[admin]

I just tested that feature and it is working correctly. Something is conflicting somewhere on this site or there is a setup issue. Are you using the email activation feature?

Also, are the members registering from the front-end or are the members being added manually from the admin dashboard side?

Did you double check to see if there is an email address value entered in the “Admin Email Address” field? If that field is empty then it won’t be able to send anything. One time we had an user who enabled that feature but kept the “Admin Email Address” field empty. So the plugin had nowhere to send the notification email to.

[admin]

Thank you. I have updated the code for this. It will go out with the next release of the plugin.

[admin]

A user cannot log into another user’s account. That’s just not possible. The issue is related to some kind of caching.

Please note that your hosting provider can also apply caching to your site without you knowing about it. This normally happens for shared hosting.

The following is what causes the issue:

The membership functionality needs a dynamic page being shown to the members. A cached page simply shows a static cached page (our plugin doesn’t get a chance to apply the conditions to that page). When a cached page is being shown, the user is not actually being shown a page which can read the login status of the user then show/hide the page’s content accordingly. That’s what causes the issue with membership type setup because membership type site is not the same as a blog type site. Caching is normally fine with a Blog type site where there is no need to show content based on a member’s login status.

[admin]

Solution #1) Add the following custom CSS to your site to hide that entire message using CSS:

.registration_hidden_to_logged_users_msg{
display: none;
}

Solution #2) Create a custom translation file for your site so you can customize all the texts and messages displayed by this plugin. That allows you to also customize that message for your site using that language file. This is suitable for users who want more customization for the text to exactly what they want.

If you want to learn about creating a translation file, the following page maybe helpful:
https://simple-membership-plugin.com/translate-simple-membership-plugin/

[admin]

That action hook is working fine. I tested it myself again just to verify it. That action hook gets triggered when the SWPM plugin has processed the login authentication. That hook DOES NOT get triggered after the login redirection.

It is likely that you are wanting a NEW hook to be triggered AFTER the redirection. But the plugin can’t trigger a hook after the user goes to a NEW URL. When you want to do/manage your own redirection, you need to override the redirection completely (instead of trying to use that addon and doing your own custom redirection on top of that). You can’t do half and half with this.

Another possibility is that you need a NEW action hook to be triggered from the After login redirection addon. You can suggest what action hook should be added and where in that addon. Send us the suggested code modification for that addon and we will look at incorporating that into the addon. We are always open to adding new action or filter hooks to the plugin or an addon.

Please note that any PHP coding related things fall under customization and are beyond the scope of free support. You are free to do whatever customization you want to do but we won’t be able to offer free support to troubleshoot customization/coding related things for your project:
https://simple-membership-plugin.com/message-from-the-simple-membership-team/

[admin]

Hi Guy, Yes, you need to use the “Expire After” option if you want the account to not be cancelled immediately.

So given that you want to offer 2 subscription payment options, definitely setup to TWO separate membership levels for them. That way the “Expiry After” field can be configured according the subscription payment for that level.

[admin]

I don’t believe that addon will be a full solution for you.

The expiry condition is handled via the membership level. That’s how our plugin works:
https://simple-membership-plugin.com/adding-membership-access-levels-site/

You can edit an individual member’s profile and adjust the “access start date” to manually adjust the expiry condition a little bit. If you fully read the following post, it maybe helpful for you to understand how that works:
https://simple-membership-plugin.com/manually-activating-expired-members-account/

It is likely that you will need to use a different plugin that offers the kind of expiry condition that you are looking for.

[admin]

Hi,

Few things to check:

#1) Please make sure that you are not mixing up the test mode and live mode subscriptions. Read the section “Live Mode Vs Test Mode” from the following documentation just to make sure that everything is setup correctly for ONE mode:
https://s-plugins.com/stripe-subscription-payments-addon/

#2) For membership payment, the actual membership registration related email will be handled by the Simple Membership plugin. The registration process and the email it sends is explained here:
https://simple-membership-plugin.com/membership-registration-process-overview/

#3) The stripe payments plugin will also send the standard notification email about the transaction. That doesn’t have anything to do with our simple membership plugin. Looks like you can customize the notification email of the stripe payments plugin using email merge tags. Make sure the correct tags are using in that plugin’s email settings:
https://s-plugins.com/email-merge-tags-email-shortcodes-email-customization/

#4) When testing, don’t test it from a browser when you are logged-in as an admin to the site. That won’t create the perfect test scenario that your members will see. In a browser (different to the one you are logged into as admin) open the page/post where you have the payment button. Then do a transaction. This will allow the plugin to treat this as a NEW transaction from a NEW user (otherwise, if you are logged-into the site, it will treat that as a payment from an existing user).

#5) Enable the debug logging feature in both the plugins so you can see what it is doing after the transaction. This can be very helpful in understanding where things could be going wrong.

#6) Make sure there is not caching on this site that is making things all confusing. The membership functionality needs a dynamic page being shown to the members. A cached page simply shows a static cached page (our plugin doesn’t get a chance to apply the conditions to that page). When a cached page is being shown, the user is not actually being shown a page which can read the login status of the user then show/hide the page’s content accordingly.

Check the cache plugin compatibility section of our documentation to see if there is an integration with the cache plugin you maybe using:
https://simple-membership-plugin.com/simple-membership-documentation/

Let me know how you go after that.

[admin]

No. The available options are explained in the following documentation:

Towards the bottom of the following page:
https://simple-membership-plugin.com/adding-membership-access-levels-site/

This one is generally good to read for some general knowledge in terms of how you can manually activate an expired account (if needed):
https://simple-membership-plugin.com/manually-activating-expired-members-account/

[admin]

Hi, We will look into adding a new shortcode for this potentially.

[admin]

We are in the process of adding a new option in that cancel shortcode to allow opening of the window in a new tab.

It will have a new available parameter “new_window” in the shortcode like the following example:

[swpm_paypal_subscription_cancel_link merchant_id="ABC123XYZ" anchor_text="Cancel Subscription from PayPal" new_window="1"]

[admin]

Are you using the following Stripe buy now button?
https://simple-membership-plugin.com/sca-compliant-stripe-buy-now-button/

If not, then please use that. That one uses the new Stripe API. It will handle the actual credit card checkout on Stripe’s site and you shouldn’t have a site specific conflict causing an issue with the checkout process.

[Author]

Posts