Version 2.0.4 of Paid Memberships Pro is out with a handful of bug fixes. These bugs have the potential to hinder sales and the performance of your site, so be sure to upgrade. Due to a technical issue, it’s also possible that those of you who updated to version 2.0.3 this weekend didn’t get all of the fixes from that update. These are included in the 2.0.4 update.

Please update Paid Memberships Pro from the plugins page of your WordPress dashboard. You can also get the latest version of PMPro here or version 2.0.4 specifically here.

The full list of updates is below.

  • BUG FIX: Fixed warning in code added in 2.0.3 that could cause issues at checkout.
  • BUG FIX: Setting priority of pmpro_check_admin_capabilities to 5 to ensure it runs before dashboard redirect.
  • BUG FIX: Removed duplicate id attribute on the Membership Account page “cancel” action link.
  • BUG FIX/PERFORMANCE: No longer enqueueing frontend.blocks.js which had no functional code, but loaded a lot of Gutenberg JS that wasn’t needed on the frontend. When/if our blogs have frontend JS, we will load it again, but also make sure the dependencies are correct.
  • BUG FIX/PERFORMANCE: No longer loading blocks.style.css. These frontend styles were redundant with CSS in css/frontend.css.
  • NOTE: The SVN repository was missing the 2.0.3 tag when that update went out. Some users may have updated or tried to update and not gotten the correct files for 2.0.3. Everyone should update to 2.0.4, which is Gucci.

Comments (4)

Hi, I’ve just updated (finally!) your fantastic plugin. I just had one question: what does the ‘token’ status mean that appears with Paypal Express sometimes (no payment transaction id or any other details so its like a transaction that hasnt been completed) I can’t find anything in the docs on what it means has happened, and why it has not moved to ‘success’ status.
Thanks

When the user goes to PayPal to pay we create an order in token status to keep track of that. If the user never comes back from PayPal, that order is orphaned in token status and never gets updated to success.

Often, users checkout again, so a later order is the successful one for them. Sometimes, the user never came back.

Leave a Reply

For faster support related to issues on your specific site please open a ticket in our members support area.

Your email address will not be published. Required fields are marked *