David Parker
David Parker
This is not implemented in PMPro v3.0, but is now possible.
Closing as next payment dates can now be retrieved via the PMPro_Subscription class released with PMPro v3.0.
As of PMPro v3.0, you can now get the subscription for an order, and then the next payment date for the subscription.
As of 3.0, next payment dates should be retrieved by getting the subscription for the user and getting the next payment date from that Subscription object.
Closing as the `pmpro_profile_start_date` filter is now included in the `pmpro_calculate_profile_start_date()` function, which is now considered a "standard" across gateways for calculating the profile start date.
Closing in favor of #2945 which fixes this same issue and simplifies the rest of the function's logic.
I was working on this issue a while back, not sure how far I got and would want to review the changes before continuing this update: https://github.com/dparker1005/pmpro-multiple-memberships-per-user/tree/issue_60
When implementing, see "API" section of this article: https://mailchimp.com/help/gdpr-faq/#API
Request for this behavior: https://github.com/strangerstudios/pmpro-mailchimp/issues/97
By default, the `FNAME` and `LNAME` merge fields should be sent to Mailchimp here: https://github.com/strangerstudios/pmpro-mailchimp/blob/49d0378880b68bceb72070ee950fc6f1e2c86279/includes/api-wrapper.php#L114-L117 Can you please ensure that this issue is still occurring? If it is, can you...