Ryan
Forum Replies Created
-
Hello @andrewza – just to feedback and also for anyone else who might want to follow this method, the suggested plugin does not function as advised.
I created a discount code with a subscription delay setting of
2020-07-26and an individual used that code today when purchasing their annual renewing membership.PMPro is showing that the start date for the membership is today’s date (
2021-03-23) and Stripe is showing the date for the next transaction is a year from today (2022-03-23) rather than a year from membership starting (2021-07-26).So unfortunately the plugin is unable to backdate membership.
Hello @andrewza
Thanks for the heads-up regarding the Subscription Delay Add-On, this looks ideal. Just to clarify my understanding, let’s assume I have a member called Jane Doe, who should have taken up an annually renewing membership on 1st June 2020.
I create a one time use disount code especially for her with a subscription delay value of
2020-06-01– she would pay the full amount, but her membership will backdate to when she should have taken it up.What date is sent to Stripe for processing the next annual payment? Will it be 1st June 2021 or will it be a year on from the date of transaction?
Many thanks!
Hi @lschuyler!
Thanks for the response – I mistakenly posted this before realising you had a support contact form so I’ve also had some correspondence there with a chap named “Trevor M” – perhaps you can liaise your findings with him?
Here are the requested screenshots, as well as just the text copy & pasted (figured it might be handy unless you’re fluent in Chinese!)
Taxonomy Screenshots:
https://drive.google.com/file/d/0ByzkxAgCyPvNUHRid2lZZnhVaFU/view?usp=sharing
https://drive.google.com/file/d/0ByzkxAgCyPvNLVVIQ0dFUWd6clk/view?usp=sharingText (copy & pasted):
https://docs.google.com/document/d/1LiX_875Exqhdz7pTEJ_WzKWdG3-D1xi024uy8v16IxM/edit?usp=sharingTrevor appears to have suggested the only way to resolve this problem is by using roman characters only in the name, but that is not possible for me as the website is intended to be used in Taiwan by native Chinese speakers.
From what I can tell, the anchor tags and their associated ID’s are using the taxonomy name rather than the slug, which is throwing up the issue. It would seem to me that using the slug would be the better choice all-around as they are inherently url friendly, unlike the name, which would be of benefit to all non-roman languages out there.
Thanks in advance!