When I add an existing user (registered but not subscribed) to a plan, how to avoid a second entry in the joslv_osmembership_subscribers table?
This is what happened to me:
I added a user from the front end but forgot putting her into a plan. This creates a registered user in users table and a non subscribed user in the subscribers table.
When I realized my mistake, I used the front end again, and picked her from the user list (see first attached image) . I noticed the form didn't populate the user's first name, last name, and email from the existing user. I had to type again. I don't mind to type it again but I suspect this might be the beginning of my problem.
Then after I set her plan and saved. I saw there were two entries in the Membership List on the front end. (see 2nd attachment)
I traced the two entries in the back end, and found them in the subscribers table. (see 3rd attachment.)
Last edit: 2 weeks 10 hours ago by new pro. Reason: try to move the attachment
You are suggesting me to do it from back end Membership Pro->Subscription, which works. I could have also done it from database.
However, my goal is to let the manager to manage it from front end only, as she didn't know much about Joomla.
I have a few suggestions on front end:
1. add an configuration in Add Subscription screen, to set a default plan. This will reduce my kind of mistakes.
2. in Subscription Management menu, allow manager to select (filter) users without a plan. This way, front-end manager can delete those entries without a plan. Right now, only users with a plan show up in Subscription Management menu; therefore, the manager would have to ask me to delete those entry without a plan from back end.
(add a new filter "Without a Plan" in the red box in the screenshot)
Last edit: 1 week 6 days ago by new pro. Reason: correct typo
Thanks for your suggestion. Actually, I think the system should prevent the subscription record from being saved without choosing a plan. That should be the right way. I will have to check to see why it's not being validated and solve it in next release of the extension