Paul Barthmaier (pbrocks)

Hi Aaron,

Thanks for using Paid Memberships Pro. I can confirm that this recipe works in that I just helped someone with a concern about its use. But can you clarify what you mean by “stopped working”? Are you saying that it’s not restricting access or it’s not redirecting to the login or what? Did your hosting change? Specifically, was it working with Apache, but not with nginx?

Hi there,

Thanks for the question and for using PMPro. This sounds like an annoying thing happening on your site, but I’m not aware of any such link. Given the link you gave above, however, if looks like the page that was set for your Password Reset link page is a child page of the Membership Account page. Can you check that this page does not have any parent specified in the page editor?

Hi there,

Thanks for looking into Paid Memberships Pro. We have plenty of users who are implementing what you describe, some of whom also use BuddyPress with our BuddyPress Add On to further enhance their experience. We can handle paying at registration and restricting content based on levels, or remain open to all once the registration is handled.

It’s probably because the CPT you are referring to is set to Private

Hi Jesse,

Thanks for the info and for using Paid Memberships Pro? Can you try adding this to your WP Customizer CSS?

#pmpro_levels_table {
    background: transparent;
}

Your issue involves one of the new enhancements that came from a user. We are working on a complete rewrite anyway, so of course it’s in the works. The point here is that you aren’t losing anything by commenting out that line that I suggested. You can rest assured that Paid Memberships Pro will continue to improve AND remain open source.

Hi there,

Will need to look into this more closely, but for now, can you try to comment out this line:

add_filter( 'manage_users_sortable_columns', 'pmpro_sortable_column' );

That is, put two slashes in front of it like:

// add_filter( 'manage_users_sortable_columns', 'pmpro_sortable_column' );

In my file it is line 284 of the paid-membership-pro/includes/init.php

Hi there,

I think I’d recommend using utf8mb4 for your encoding and you can do this in phpMyAdmin like so:

Link to Screencast to adjust character encoding

Everything about PMPro is built around the User and I can’t see that there is a way to circumvent this. It’s true that it’s a very flexible plugin with many Add Ons, but it all begins with individuation of the WP user.

Great answer. Thanks for clarifying. In that case, then I don’t that PMPro is needed at all. There are easier ways to handle this. I’m thinking of things like just putting a PayPal button on a web page or maybe even just a Gravity form so something. What are you seeking to accomplish with PMPro, ie a plugin that is designed to limit access to content?

Hi there,

Thanks for using Paid memberships Pro. There are a lot of reasons why this might not be working and likely most are avoidable with a developer who knows WordPress well. If your original site was WordPress and you still have access to the original database, then the passwords and user information should be recoverable. If not, your members should be able to set a new password via the Lost Password function. I don’t think there is a way to disable passwords and can’t think of why you would want to do that. I wouldn’t take this lightly. If a user can’t reset a password, the site will be rife with other problems.

Hi Federico,

A couple of things for you to check is giving your Register Helper field a better key. In general, avoid using capital letters, but in this case you might try member_first_name. What often is the issue when one field isn’t being saved is that there already exists and usermeta entry with that key. Also, the field type shouldn’t be capitalized. Hope this helps.

Hi there,

Thanks for using he plugin and glad to hear that things are working on staging. I’m sorry to hear that you are having trouble with your production site. Typically when we hear of symptoms like this, it points to caching or minification. Hosts will often have caching turned on for your production site to be at its optimum speed, but this doesn’t play nicely with dynamic pages like what the plugin needs. Staging sites usually won’t have the caching turned on and it’s possible that your javascript isn’t minified. What I’d recommend is seeing if you can exclude the PMPro pages from caching. This may be possible with a plugin setting or something for which you may need to contact your host.

Hi there,

Thanks for the kind words about the plugin and its developer. If you made changes to the plugin templates in a recommended way, which means using either filter functions or copies of the pages in your active theme, then you will be fine when updates occur. You mentioned changes to text, if you altered text with a function, then again you will be fine. Hopefully, you have done so and are able to update the plugin.

Hi there,

There is going to be some setup to Paid Memberships Pro, like setting up the levels and payment gateway, etc. If you’ve done all that, then it could be your theme. If you are using a theme that requires a page builder, you may need to adjust the priority of the wp_content filter to ensure that PMPro filters the content after the page builder.