You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When a member has a recurring payment level the "Membership Expires" item on the card displays "Never". This cannot be replaced with a custom value, e.g. the level's next payment date of the recurring billing cycle, as there is no filter for this value.
Describe the solution you'd like
The pmpro_membership_card_since_date filter for the start date allows customizing the value displayed for the "Member Since" item on the card, adding a filter for the end date, e.g. pmpro_membership_card_end_date, where the value is displayed for the "Membership Expires" item on the card could be a useful enhancement allowing developers to customize the value displayed here.
Describe alternatives you've considered
Use a custom template with the required functionality built-in.
Additional context
Moderators Only: #565273
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When a member has a recurring payment level the "Membership Expires" item on the card displays "Never". This cannot be replaced with a custom value, e.g. the level's next payment date of the recurring billing cycle, as there is no filter for this value.
Describe the solution you'd like
The
pmpro_membership_card_since_date
filter for the start date allows customizing the value displayed for the "Member Since" item on the card, adding a filter for the end date, e.g.pmpro_membership_card_end_date
, where the value is displayed for the "Membership Expires" item on the card could be a useful enhancement allowing developers to customize the value displayed here.Describe alternatives you've considered
Use a custom template with the required functionality built-in.
Additional context
Moderators Only: #565273
The text was updated successfully, but these errors were encountered: