Please Log in or Create an account to join the conversation.
That functionality isn't a plugin, but just a parameter under the Access tab of your plans. If you're doing this through a plugin it would be by using CB Auto Actions and its Usergroups action type.I could swear there is an option to add users to a group and then remove them or alter them when their plan is done and not renewed.
The usage under the Access tab doesn't let you select more than 1 usergroup and you can't select a usergroup to assign on expiration. The usergroup selected will be given when they become active and removed when they expire automatically. If you need more indepth control you need to use CB Auto Actions.I can find the add part (in Access) but I have looked three times (and done searches and perused the manual) and I'll be damned if I can find where a user is assigned to different group on expiration.
The functionality exists in both to an extent. If you only need to manage 1 usergroup per plan then using the usage under the Access tab of your plan is recommended.If there is no way to do that using CBSubs settings (and I am, in fact, losing my mind) then I'm assuming it can be done using AutoActions or similar. Any insight into this would be appreciated.
It sounds like you just need to add "Registered Member" group and remove it when appropriate. That's easily done using the parameter under the Access tab of your plan. If you want a more indepth usage you can use the below in CB Auto Actions for more control.What I'm attempting is to use CBSubs to change a user to "Registered Member" group and then on expiration change them back to "Registered." Registered Member would be the way event software (such as Event Booking or Matukio) would know that the user can register for the event.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Typically my work day consists of spending the morning clearing support. This could take 1hr to 8hrs (the entire day), but on average takes no more than 4hrs (half the day). The rest of the time is dedicated to development. Some days can get pretty busy on support, but since we use GIT for managing all our development it's not an issue to typically stop mid-development, switch back to master branch, fix something, and release the fix. It was A LOT more stressful when we used SVN and couldn't do that, but that was years ago.I simply don't know how you all do what you do between dev and answering these forum questions.
Absolutely and is a big part of why weekends are our downtime.Do you all have lives beyond CB????
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
It sounds like you just need to add "Registered Member" group and remove it when appropriate. That's easily done using the parameter under the Access tab of your plan. If you want a more indepth usage you can use the below in CB Auto Actions for more control.
Please Log in or Create an account to join the conversation.