Version 1.7.13 of Paid Memberships Pro is out with a da_DK localization file (Thanks, Mikael) and couple of very important bug fixes. These bugs have the potential to hinder sales if you are using Stripe with the “don’t show billing address” option set or to affect the dates of trials and other dates in the system. Please upgrade.

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

The full list of updates is below.

    • Added Danish (da_DK) translation. (Thanks, Mikael)
  • Fixed bugs with timestamps in various places (especially around trial dates) introduced in 1.7.12
  • Another fix to keep PMPro from sending “undefined undefined” as the name to Stripe when the ‘don’t show billing fields’ option is chosen.
  • $pmpro_stripe_verify_address flag defaults to same value of Stripe’s showbillingaddress option now.
  • Changed the priority of pmpro_applydiscountcode_init hooking on init to 11 so pmpro_init() will run before and setup pmpro_currency_symbol among other things. (Thanks, semyou on GitHub.)
  • Explicitly setting $current_user->membership_level in a few places to avoid issues where current_user is overwritten between init and when we try to use it.
  • Avoiding a warning in pmpro_getMetavalues() function. (Thanks, Scott Sousa)
  • Added target=”_blank” to help links on admin pages. (Thanks, AntonVrba on GitHub)

Comments (9)

Hi Jason, great plugin really ! Keep up the good work πŸ˜‰ Here are my 2 questions :

1) I’m using pmpro in french, and i need the euro symbol to be on the right side of the price. Can you advise me on this one ?

2) Something really important too : i need to remove the comas and dots in prices. For example, i have a lifetime membership level for 1000 euros. It displays like this : €1,000.00. In french, its a big issue because it looks like one million euros lol ! (even if its 6 zeros i know lol).

Thanks for your help πŸ™‚

πŸ™‚ We’ve be asked about this before and looked into it. It’s such a small thing, but would actually take us a bit of effort (at least 4-8 hours) to go through the entire plugin to support both of these things. It’s on our list, but not something we’ll get to before the v2.0 release. If you have a developer to loan us, we can direct the work or if you have some money, we can go 50/50 on the cost and expedite this feature.

Sorry if this is holding you back. We hope to get to it soon.

Coleman, i’d sent to Jim Coleman a lot of issues with portuguese translate. I sent this issues at January, 23th, but all new releases don’t have my changes. Can you check it? Thanks!

Hi, guys. We don’t have any plans to implement Pagseguro right now. If you can pull together some funding, we can work it into the schedule. I appreciate that you would like support for this gateway, but please don’t “spam” the comments like this every time we post. Thanks.

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 *