Jason Coleman

Hi, CommonTater. Thanks for using PMPro. Sorry for the issue you’ve run int.

so I turned off that level

What do you mean by this? Did you update the price? Or set the level to hidden? When you do either of those things, PMPro does NOT automatically cancel the associated subscriptions for users who previously signed up for the level.

To cancel those subscriptions, you can edit the users and then change their level from the edit user page, and check the box to “cancel the existing subscription at the gateway”. This will change the user’s level and cancel their subscription.

You can also find the subscriptions at the gateway and cancel them there. This will cancel the subscription, then send an IPN/webhook to your site that PMPro should read and cancel their membership on the site. If you want them to retain access, but just cancel the payment part, then using the method above is better

Why would a subscriber be charged for a renewal in 2023, given that they were not charged in 2022?

Depending on how your levels are set up with trials, prorating, our cancel on next payment date add on, there are cases where a user checking out pays for the current and following years. We’d have to see your setup to figure out exactly what happened.

How can I ensure that this does not happen again?

You should log into PayPal and look for subscription there that you don’t want to have and make sure they are cancelled at the gateway. The recurring orders are initiated by PayPal.

Can I delete a membership level that has subscribers? And would this prevent them from being charged again? What level would they have?

You can delete levels. It WON’T delete the associated subscriptions. (It used to, but more often people were accidentally cancelling those subs they didn’t want to.) If you delete a user’s level, they won’t have any level.

You can use the PMPro Toolkit add on to both cancel all of the subs and move those users from one level to another. You can find the add on on GitHub as well if you don’t have access through our site.

https://www.paidmembershipspro.com/add-ons/pmpro-toolkit/

Look for these options under Tools > Toolkit Scripts after activating the plugin.

• Cancel all members with ____ level ID . WILL also cancel any recurring subscriptions.
• Give all non-members ____ level ID .

Some more information on deleting levels here: https://www.paidmembershipspro.com/documentation/membership-levels/delete-membership-level/

This is a Paid plugin.

The plugin (and all of our code) is made available for free on .org here or on GitHub. If you are paying member through our website, I encourage you to request a refund through our contact form.

Generally, you want to create new pages for each of the PMPro functions/pages. Go to Memberships > Settings > Page Settings and make sure there is a page for each, with the appropriate shortcode on each page.

Then the typically flow is to send folks to the levels page, let them choose a level, then they checkout, then they simultaneously are registered as a WP user and get a PMPro membership.

You can put some of the shortcodes on individual pages, but things will break if you don’t have a stand alone page for each function.

Once you set PMPro up with all the pages, you can put the pmpro_checkout shortcode/block on any page and set a default level for it. This will then show a checkout form inline there.

Our add on for Sign Up shortcodes has some additional features to create abbreviated versions of the registration form. You can check it out here: https://www.paidmembershipspro.com/add-ons/pmpro-signup-shortcode/

Let me know if this helps.

If you need it, we have an article on troubleshooting cron issues. https://www.paidmembershipspro.com/troubleshooting-issues-with-wp-cron-and-other-scheduled-services/

Good luck with the project. I’m going to resolve this thread. If you need further help, feel free to open a new one.

If you get into writing custom code for this, often the most challenging bit is figuring out where to hook in your limit and how to notify the user of the limit. That’s going to depend on what a “download” really is, what plugin you are using to manage them.

But once you do that coding the limit per level is fairly straightforward. You can set up an array to store the limits or a big if/then/switch like:

// Get the limit based on their membership level.
if ( pmpro_hasMembershipLevel( array( 1, 2 ) ) ) {
    // Levels 1 and 2 get 5 downloads.
    $limit = 5;
} elseif ( pmpro_hasMembershipLevel( 3 ) ) {
    // Level 3 has "unlimited" downloads.
    $limit = 99999;
} else {
    // Default to no downloads.
    $limit = 0;
}

// Get (from user meta or plugin DBs) how many downloads used.
$used = ...;

// Check vs limit.
if ( $used >= $limit ) {
    // Throw a warning somehow
} else {
    // Do nothing. Allow the download.
}

Make sure you have a checkout page set in the Memberships > Settings > Page Settings page. All pages there should be set.

Have your lawyers contact us.

Good luck with the site.

That is correct. You should see that recaptcha logo in the bottom right of the screen.

We did refactor how we load recaptcha’s at checkout. This shouldn’t have affected things on your site, but it’s possible there is a conflict now that wasn’t there before. (A lot of the complexity of our recaptcha code is making sure it works if there are other plugins on your site that also want to use recaptcha/etc.)

If you share the URL of your site, I can take a look. It might be a visual bug.

If you use the debug bar in a browser like Chrome, you can see if the page is loading scripts from recaptcha. Right click on the site, click “inspect element”. Then go to the “Sources” tab of the debug bar. Then find http://www.google.com in the list, click the caret to open it up and look for recaptcha there.

If you see that, then the page is at least *trying* to load the recaptcha scripts. There might still be some other issue blocking things.

Also test a checkout to see if you are getting “recaptcha required” type warnings.

Thanks for your understanding. I hope we can figure this out quickly for you.

So currently, there is no way to add multiple levels, until they modify the Members Only Tickets add on?

Correct. The form needs to be updated to save an array of level ids or include that extra code to convert something like “1,2,3” to an array. The PMPro function doesn’t accept things like “1,2,3” by default.

Because I was on a roll here, I wrote a gist that should use the PMPro filters to support calls like pmpro_hasMembershipLevel(“1,2”)/etc.

This is untested. Let me know if it works. You can add the code via the Code Snippets plugin or in a custom plugin.

https://gist.github.com/ideadude/756cfd6d8b60993552b6146db900ce38

I wouldn’t plan to use that code ongoing. TEC should update their add on. You can see how to split the string into an array in there.