pmpro-multiple-memberships-per-user
pmpro-multiple-memberships-per-user copied to clipboard
strangerstudios
wrong expiration date
Hi all :)
First, I will describe the behavior without this addition, only PMP. There is Renew option, eg if I have a course that expires after 5 days, when I buy the level again, it will expire after 10 days. The days will be summed up.
I wanted to use it with this add on. If I buy a course again, on the expiry date I have only 5 days (it sholud be 10days). It looks like the same my level is doubled. If I click on Cacnel, it removes my one of two same levels and the expiration date changes to 10 days, so days were summed up, but are "at the bottom". Can you make that the most important expiration date is like at the very top?
On a new membership level purchase through WooCommerce, the expiration is not set (no expiration). Changing the expiration in the user profile as site administrator fails to save on first user profile update but succeeds on second user profile update.
Hi @ipokkel I have been testing this version. But I also noticed that the expiration date is not updated as configured at the subscription level. I took his advice and manually changed the user's profile to the correct date, but I simulated two more user purchases in the hope that autocomplete will occur, and it's not possible. In all associations the expiration item is empty, and when I enter the user profile I see that it is set to "no". Is there a function to solve this?
On a new membership level purchase through WooCommerce, the expiration is not set (no expiration). Changing the expiration in the user profile as site administrator fails to save on first user profile update but succeeds on second user profile update.
Is this a deliberate behavior for this extension, That expiration be empty after WooCommerce membership purchases?
Why, if so?
It works as expected using the core PMPro plugin but goes empty after purchases once this plugin is active.
The idea of updating users' profiles isn't convenient.
Like @tiicaa asked, is there a function to solve this?
And I really do think this behavior needs reconsideration.
