Hello, I’m looking at the Paid Memberships Pro WordPress plugin to start a membership site.
The plugin authors removed it from the WordPress.org repo, but one of its add-ons is still there, and seems to be compatible with the latest version of CP.
Has anyone tried this yet? I would like to accept payments on my site, so I was wondering if there’s anything I should keep in mind if I attempt this.
I see that plugin uses blocks, so I’d check with which version of WordPress it says it’s compatible. If it says 4.9 or lower, you should be good. If it says 5.0 or higher, I expect you’ll be out of luck.
It says it’s compatible with WP 5.2+. I installed it and it seems to be working normally.
Hopefully that means payments will work properly?
As long as payments don’t use blocks, it should work. But if it doesn’t use blocks for payment and it’s working for you so far, then I don’t know what it uses blocks for! 
If I remember correctly, it allows for restricting access to blocks based on membership level. So viewers wouldn’t see them unless they had access, and authors couldn’t use them without the right level (though I might be mixing this second thing up with a permissions-editing plugin…)
I used Paid Memberships Pro with 4 different projects. I am a big fan!
Never tried it with CP, though, but it would be awesome if it worked.
Based on the fact that they removed it from the WP repo, and the husband and wife developers seem very easy going, I would ask them to consider implementing CP support. Or adding conditional code for WP vs CP.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
@trout 2 years later, I have a PMPRo alternative:
FX Membership (free, GitHub) at a high level it’s in the same family as Paid Memberships Pro (PMPro): membership levels, paid access, checkout, member account, and recurring subscriptions. But FX Memberships is deliberately much simpler and follows a different billing model.
| Concept | PMPro | FX Memberships |
|---|---|---|
| Membership levels | Yes | Yes (slug, name, order/tiers) |
| Paid recurring access | Yes | Yes (Stripe + PayPal subscriptions) |
| Content gating | Yes | Yes — via shortcodes like [fxm_restricted] |
| Member account area | Yes | Yes — [fxm_account] |
| Admin subscriber list | Yes | Yes — Subscribers page + CSV export |
| Level tiers | Yes | Yes — higher order includes lower levels |
So if you need PMPro-style memberships, the core idea matches: sell a plan → track status → unlock content.
1. Billing lives off-site
PMPro can run checkout on your site with many gateway add-ons, local orders, invoices, and admin billing tools. FX Memberships only redirects to Stripe Checkout / PayPal approval, syncs status via webhooks, and sends members to hosted portals for billing changes. No local payment UI, no orders table.
2. Restriction is shortcode-first
PMPro can restrict whole posts/pages/categories, use blocks, and filter the_content automatically. FX Memberships restricts content you wrap in shortcodes ([fxm_restricted], [fxm_if_member], etc.). There’s no automatic “this post requires Premium” UI.
3. Plans/prices are defined in Stripe/PayPal
PMPro levels often tie to on-site pricing and checkout fields. FX Memberships levels mainly store Price ID / Plan ID from the provider dashboard — closer to EDD + external billing than a full membership suite.
4. Much smaller feature set
FX Memberships does not include (PMPro often does, natively or via add-ons):
Discount/coupon codes
Membership emails
Trial/expiry rules managed locally
Multiple concurrent memberships per user
Login/registration checkout wizard
Reports beyond a basic subscriber list
Large add-on ecosystem
Deep WordPress block/editor integration
5. Platform focus
FX Memberships targets ClassicPress and a small, functional codebase (~20 PHP files). PMPro is WordPress-centric and much larger.
FX Memberships is like a lightweight “PMPro core” for subscription sites that want Stripe/PayPal to own checkout, billing, and invoices — with shortcode-based access control instead of a full membership platform.
That’s a good fit when you want:
Minimal code and maintenance
No PCI/card handling on the site
ClassicPress compatibility
“Sell access, restrict content, let Stripe/PayPal handle the rest”
It’s not a good PMPro replacement if you need on-site checkout, rich member dashboards, emails, discounts, post-level restriction UI, or PMPro’s add-on ecosystem.