[clearscopedesign]

The text reads as follows:

“Please choose your username and password below to complete the registration.”

Thank you

[clearscopedesign]

Could we please request that a CSS class or ID be added to the <p> tag that wraps the default text that appears above the registration form for the auto-reg process, so that said text may be styled? I am referring to the default text / <p> element that appears above the registration form, after the user has clicked the link from the “Complete your registration” email. Presently there is no way to target that text/element with CSS.

Thank you!

[clearscopedesign]

Got it, thank you for the follow up and confirmation on this. We will just stick to ‘1 year’ for the duration in that case. Thanks again for all of your help and support.

[clearscopedesign]

Ok so I updated our eStore and eMember plugins to the most recent versions, but that did not resolve the issue.

I then tested everything on a separate website on a separate server, and the same issue appeared there. So that confirmed that the issue is not related to a conflict that is specific to the original site.

I then tested with different PayPal credentials, and the same issue still occurred. So that confirmed that the issue is not related to any settings within the associated PayPal account.

After more testing and trial and error, I was able to pinpoint the issue:

The issue seems to be related to the ‘Recurring Billing Cycle’ setting within the product, if ‘Days’ are used for the unit of the recurring billing cycle duration, and if it is a recurring subscription / auto-renew, not a one-time purchase.

After testing over and over, it seems that if ‘Days’ are used for the unit of the ‘Recurring Billing Cycle’, and if it is set to more than 90 ‘Days’, then the error appears on the PayPal end. If the ‘Recurring Billing Cycle’ is set to less than 90 ‘Days’, then the error does not appear and the purchase is allowed to go through properly.

But if ‘Year’ is used for the unit and if the the ‘Recurring Billing Cycle’ is set to ‘1 Year’, then there is no issue/error. It is only if too many ‘Days’ are used for the cycle (again, at least presently, it seems that ’90’ is the cutoff for that).

The problem for our end is that we have been using (and still wish to use) 372 Days as our ‘Recurring Billing Cycle’ duration (we would use 53 weeks, but since ‘Weeks’ is not an option under the ‘Recurring Billing Cycle’ settings, we use ‘Days’ instead). So, unless you have a solution for this issue, it seems we will have no choice now but to change the cycle to ‘1 Year’ instead, and thus not be able to provide that extra week of membership to our members.

Also, I should clarify that my previous note about the subscription button from within eMember not having the same issue was incorrect. If a PayPal subscription button is created from within eMember, using the same duration and figures as described above (i.e more than 90 ‘Days’), then the same issue/error does in fact occur.

However, as mentioned previously, the issue does NOT occur if it is a one-time purchase (?wp_eStore_buy_now=). Only when it is a recurring / auto-renew subscription (?wp_eStore_subscribe=).

So therein lies the issue. If it is a PayPal recurring subscription (auto-renew), and if ‘Days’ are used as the unit for the ‘Recurring Billing Cycle’, and if it is set to too many days (it seems that the cutoff point is 90), then the issue/error appears. And so, because of this, it doesn’t seem possible presently to use ‘Days’ as the unit, for a recurring subscription with a longer term as such.

So all of this would seem to indicate that there is a problem with how PayPal is calculating the recurring / auto-renew billing cycle, or how eStore / eMember is sending its data to PayPal for that calculation. And it seems that something may have changed about this in the recent past, because this issue did not exist up until recently.

[clearscopedesign]

Thank you –

I’ve now gone through the checklist in the referenced article, but none of the possible reasons listed there seem to apply. We have also double checked the ‘Encrypted Website Payments’ setting in PayPal, but that was already set to ‘Off’.

I have also verified that the PayPal account email address is correct.

What is interesting about this issue is that it is only occurring for those links/buttons we are using for the auto-renew subscription purchase (using the ?wp_eStore_subscribe=(eStore product ID) format). The issue does not occur at all for the links/buttons which are for a one-time subscription purchase. And both of those types of products (auto-renew subscription and one-time purchase) are using the same PayPal merchant email address in the eStore settings.

Also I don’t believe that any other settings have changed from when it was working properly to when the issue appeared.

Should I try re-installing and updating eStore to its most recent version?

Also to answer the other question that was sent previously – yes, the users are required to be logged-in with their member account before they can use these links.

Thanks

[clearscopedesign]

Thank you for your reply –

Yes, we have eStore debug logs enabled. And yes there is data in the logs, but I’m not sure what to look for.

These are for people who already have a membership account, but who do not already have an auto-renew subscription. So yes, they are creating a “new” subscription in that sense. But the same error seems to occur whether trying whilst logged-in to an account or not.

Here is a URL where you can click the button to see the issue: [mindfulnessinschools.org/test]

I’ve just tried by creating a PayPal subscription button from within eMember, and with that kind of button the same issue does not occur.

Thank you

[clearscopedesign]

Got it, thank you for the clarification.

The reason that we want to be able to use nested content protection is in order to display content based on combinations of membership levels (for example if the user has both level 2 and level 3).

Would it be possible for us to create a duplicate content protection shortcode with a different name to enable nesting, as suggested by the other customer in reply #63749 above?

Thank you!

[clearscopedesign]

Thank you –

For some reason my reply doesn’t seem to be appearing so I am trying to post it again:

We do have multiple membership levels turned on.

However, it doesn’t seem to fully work for us. The second closing [/emember_protected] tag appears as text in the content on the front end of the page.

Here is a screenshot that shows both the back end code and how the front end content appears with the second closing [/emember_protected] tag as text: [ibb.co/VCQjJKq]

Could you please tell me what we are doing wrong?

[clearscopedesign]

Hi,

Just following up here. Can you please tell me if it is possible to use nested content protection, as indicated in reply #63752 above? Or do we need to create a duplicate shortcode with a different name to enable nesting, as had been stated by the customer who started this thread?

Thank you!

[clearscopedesign]

Hi,

We have encountered another instance of a member renewal with previously paid time lost, this time with debug enabled. Could we please ask you to take a look at the debug log?

Thank you!

[clearscopedesign]

Hi,

We are trying to use nested content protection with shortcodes, per reply #63752 above (to make some content available only to members who have both level 1 and level 2). I copied the exact code from that reply and just changed the membership level ID’s accordingly. However, it does not seem to work for us. The second closing [/emember_protected] tag appears as text, and the content doesn’t quite get protected. Could you please help me sort out what we are doing wrong? Do we need to create a duplicate shortcode with a different name to enable nesting, as had been stated by the customer who started this thread?

Thank you!

[clearscopedesign]

We have this exact same need (and I apologize for my other questions about dropping the original membership level when an account is upgraded, as I should have thought to ask this first instead).

We also have the same need stated here: to show particular content to membership level 2, but to hide the content if the member also has membership level 3, for example.

However, as has been explained above, it does not seem to be possible to have nested [emember_protected] shortcodes (only to use the page-level protection in conjunction with a content protection shortcode). But since this is for our renewal page, we are unable to use page-level protection for it.

I then had the thought that maybe we could use the not_for=”” parameter in conjunction with the for=”” parameter together. For example: [emember_protected for=”2″ not_for=”3″]. However, I tested this but it does not seem to work (if the user has level 3, they still end up seeing the content if they also have level 2).

So I am wondering: would it be at all possible to request an implemented update to eMember that would allow for the not_for=”” parameter to take precedence over the for=”” parameter, if both are used? That way, using the not_for=”” parameter would allow for hiding content from a given membership level whenever necessary.

If this would be possible, we would be open to paying for this development if need be.

Otherwise, if that would not be possible, then are there any other options for displaying conditional content based on multiple membership levels, without depending on page-level protection? i.e. to display content to level 2, but to hide that content if the user has level 3?

Thank you kindly for all of your help, and my apologies again for not thinking to ask this from the start.

[clearscopedesign]

Right, the issue there is that, because upgrades to Plus retain the Basic membership level as a secondary, those users still see the message that is intended only for Basic.

I guess to simplify the previous question, we were just hoping there might be a way, using section protection, to display a message that only appears for users if they have the given membership level as their primary, but not as their secondary.

No worries, we will just make due with the present config.

Thank you kindly for all of your help

[clearscopedesign]

Ok got it, thank you.

Unfortunately we cannot disable the multiple membership capability because we need to be able to apply secondary membership levels as ‘access’ levels to different content, based on various criteria.

In our case the ‘Plus’ membership is not supposed to lose access to the ‘Basic’ level material. Rather it’s related to just one particular instance – we have a couple different messages on the renewal page; one message is for the ‘Basic’ folks, and another different message is for the ‘Plus’ folks. For this we use the content section protection shortcode. But the issue is that, since the ‘Plus’ members maintain ‘Basic’ as a secondary after they upgrade, they then end up seeing both of those messages instead of only the ‘Plus’ message.

So I guess the other question would be – is it possible to apply the section protection shortcode only for a primary membership level (and not for a secondary)? This would then solve our issue because it would allow us to specify the messages on the renewal page only for those primary membership levels (and thus the ‘Basic’ message would only appear for those who have ‘Basic’ as a primary level and not as a secondary level).

I couldn’t find an option for this in the documentation, but figured I would ask just in case.

For example, something like: [emember_protected scope=”primary_membership” for=”2″]

If not, then we will just live with the ‘Plus’ members seeing the ‘Basic’ message on the renewal page.

Thank you!

[clearscopedesign]

Apologies if this is the wrong place to post this, I wasn’t sure if I should start a new topic or not.

A couple questions:

1) As I understand it, based on some of the other posts in the forum, we could use the eStore action hooks to custom code an integration between eStore and Zapier, in order to catpure eStore transactions into a CRM, is that correct?

2) Is it within the realm of possibility to do the same for eMember (to custom code an integration between eMember and Zapier)? The goal with this one would be to capture eMember membership actions such as ‘Membership Expired’ into the CRM.

Thank you!

[Author]

Posts