If I understand correctly, without refreshing, in backend the K2 usergroup is there? However, on frontend it's acting as if it isn't? If that's the case then the K2 usergroup is probably stored to the users database session. In this scenario the session isn't being updated until the page has reloaded and the session has re-established. This would then make more sense why this is happening and the CB Auto Actions K2 action would be what's bugged as it would need to reload the user session after changing the K2 usergroup.
Kyle (Krileon)
Community Builder Team Member
Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums
CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
krileon
