Latest Changelog
Paid Memberships Pro 3.9 – October 27, 2026
Release-note summary from the official changelog.
- Brings delayed recurring payments and fixed expiration dates into core.
- Adds percentage and fixed-amount discount types.
- Extends captcha protection to login and password-reset flows.
- Introduces gateway migration tools, CLI/API capabilities and Elementor v4 support.
Download details: The download is Paid Memberships Pro 3.9 core. Separate paid add-ons, gateway accounts and vendor services are not bundled.
What This Update Means
This release changes membership rules rather than merely polishing their editor. Moving date controls into core should reduce reliance on separate scheduling add-ons. Existing renewal dates still deserve inspection before changing a live plan. A percentage discount also needs testing against initial and recurring charges separately. Login protection now reaches more of the account journey. Gateway migration should begin with its preview rather than an immediate conversion. New automation interfaces make permission review more important, not less. A test membership should cover signup, renewal and expiration before rollout.
Paid Memberships Pro’s 3.8 series made membership emails less dependent on remembering template variables. In its release announcement, the developer describes a WordPress visual/text email editor with autocomplete for Liquid variables. The download below is now version 3.9; this earlier section describes the 3.8 email-editor changes.
The distinction is worth keeping: Liquid-style email syntax arrived in 3.7, while 3.8 revised the editing experience. Suggestions include descriptions of variables available to the template being edited, reducing the need to switch between an email and a separate reference list.
An email is part of the membership record
The 3.8 announcement also discusses email-logging coverage for SMTP plugins that bypass the usual WordPress success and failure hooks. It is an administrative improvement, not a guarantee that a recipient’s mail provider will place a message in the inbox.
For a membership site, previewing the layout is only the first check. Send a test using an account with realistic data, then inspect the rendered membership name, price and links. Repeat it with optional fields left empty. An attractive template can still give a new member incomplete instructions if its variables are wrong.
Level groups need an explicit policy
The current membership-level documentation allows a user to hold multiple levels, with groups defining whether selections are exclusive or can coexist. That difference affects how an upgrade should be tested: replacing one access tier and adding a separate membership are not interchangeable operations.
Write down which outcome the site intends before changing group settings. Then check the member’s access and subscription records after a test purchase. This is particularly useful when an installation combines older custom code with newer membership settings.
What the 3.9 download includes
Paid Memberships Pro is the product’s name; the main plugin is available as free core software. The file below is that core, with 3.9 confirmed in its header. It does not include the premium add-on catalogue. Calling this free core nulled would obscure that distinction rather than explain it.
