Membership in multiple groups - do we have something mis-configured?

So, would you advise I set Joomla | Users | New User Registration Group to "Free" - or is it better to set it to "Public"?

Leave it as Registered.

I'm not sure what's going on behind the scenes - but could imagine some potential mixups if we use Free as a default group... for example, CBSubs adding in "Paid" group in parallel to Joomla's "Free" when a new subscriber signs up as "paid" right from the start. Is there logic built in to prevent that? Does CBSubs user membership get added before or after the Joomla one? Or is the Joomla default user group value just passed to CB to start with, and Joomla does nothing?

Joomla Store > CB Store > CBSubs Store is the save order. Joomla user always stores and validates first, then CB user, then CBSubs data. If you use the CB Auto Actions usage as instructed in my previous reply it occurs when their CBSubs subscription becomes active (or expired).

One other thing... what is the correct syntax for the Replace UserGroups mode?

You just select "Replace Usergroups" for "Mode" and select the groups you want to give the user.

Is there some collected user-friendly documentation on all this somewhere?

Incubator projects do not come with documentation. They are in a constant changing state so it's not possible to maintain documentation for them. We have a few tutorials for various usecases though, which you can find below.

www.joomlapolis.com/support/tutorials/107-use-cases

And the "replace" function, it only gives one dropdown... this doesn't make sense - so where do I specify what replaces what?

You don't specify what replaces what. You're replacing the users current usergroups with the usergroups you've selected.


You don't need the usetype usage. That's just an example for assigning usergroups based off a fields value. I gave you the exact configuration for usergroups based off plan state. All you need to do is replace PLAN_ID_HERE with your actual plan id found in CBSubs > Plans (far right ID column) and select the groups you want to adjust based off the state. Please review my previous reply carefully exact parameter values.

OK, I understand now, Thanks.

I'm not able to test it though - apparently doing a manual unsubscribe/resubscribe through the CB usermanager either doesn't trigger these actions - or those usermanager actions just replace the permissions my AutoAction had just set.

Things work a bit different when editing and saving a user in backend. The reason for that is in backend CBSubs triggers before CB stores the user. So Usergroup changes end up being overwritten. Be sure to test the usage on frontend using the dummy gateway or offline gateway should work too when paying the basket.