Hi Amir,
I am sorry, I haven’t been able to properly spend time on it and reproduce it.Please allow me till Monday morning. I will spend time on it today/tomorrow and post by Monday morning.
Thank you
BrajeshHi Amir,
Thank you for the patience.I have tested it now.
I am using “Single Member type” field on registration.
I have mapped a member type to 2 groups. On account activation, the user gets added to both the Learn dash groups correctly.
I also tested the same by changing another user’s member type from the Dashboard->Users screen and it worked too.
Is there any chance that you are using some configuration in Learndash or any Learndash addon that restricts maximum group to 1?
That seems the only plausible reason for this issue.
Regards
BrajeshHi Brajesh,
Thank you for investigating. I do not use any kind of restriction for maximum LD groups.
I think there is a difference in the workflow you tested and what I experience.
In our case, a user is associated with more than one single-member-types during the registration process.
Each single member type is associated with a single LearnDash group.
The end result is that the user ends up associated with all the required member types but only to the last LD group.Please advise.
Thanks,
Amir.Hi Amir,
Thank you for the reply.I will look into it in 1-2 hour and reply.
Is there any chance that on the member type page, under Learndash you have the option “Sync” enabled. That seems the only reason for it.
The member types are applied/added sequentially and if the sync is on, only groups from last member type will be kept.
Please check.
Regards
BrajeshHi Brajesh,
Do you mean the ‘Remove Extra Groups’ setting?
If so, it is not checked in our member types setting pages.
https://i.ibb.co/k5K9KGy/Snag-369fe3.pngThanks,
Amir.Hi Amir,
yes, That was the setting. Let me try it with your configuration and get back to you in 30 minutes.Regards
BrajeshHi Amir,
Thank you for the patience.Yes, It was a bug when using Multi Member type field, the groups were always synced.
Please upgrade to 1.4.4. It fixes the issue.
Regards
BrajeshThank you. I look forward to your feedback.
Regards
Brajesh
You must be logged in to reply to this topic.