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
I'm (re-)digging into your plug-in and think of few functionalities that might be of interest.
Civi provide the possibility to "auto-renew" membership, and I've set up a contribution page to create/renew ones membership which offer this option to the user.
The member shortcodes are super nice to provide a feedback on front end to the logged in user.
As far as my little experiment could reveal, the member "expire date" and "renewal date" remain the same whether auto-renewal is on or off. This is what we may expect, no worries, however it would be great if we could have a shortcode that return the "auto-renewal" statut of the member. This would enable to provide a more complete feedback to the user and avoid any confusion.
Regards
The text was updated successfully, but these errors were encountered:
Just noting here that you could solve this problem by setting up a Data Processor for the membership and display any of the membership fields you wanted. Then it's a matter of using the ux_civicrm_listing shortcode to display the results on the page.
Hi,
Thank's for this usefull plug-in.
I'm (re-)digging into your plug-in and think of few functionalities that might be of interest.
Civi provide the possibility to "auto-renew" membership, and I've set up a contribution page to create/renew ones membership which offer this option to the user.
The member shortcodes are super nice to provide a feedback on front end to the logged in user.
As far as my little experiment could reveal, the member "expire date" and "renewal date" remain the same whether auto-renewal is on or off. This is what we may expect, no worries, however it would be great if we could have a shortcode that return the "auto-renewal" statut of the member. This would enable to provide a more complete feedback to the user and avoid any confusion.
Regards
The text was updated successfully, but these errors were encountered: