You could make it read only. They'd then be able to check it during registration, but won't be able to during profile edit. The alternative is you could try conditioning its own self and hiding if its value is equal to 1 using CB Conditional, but this could cause a very strange loop.
Ideally you'd just set the field as Required. They'd be required to check it and they won't be able to uncheck it as they wouldn't be able to then update their profile.
Sorry, just don't understand the need for this without further explanation as to what you're trying to do.
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.
Thanks for your reply. Yes it is a little bit stainge. Let me explain.
We decided all users should allow automatic incasso of their club contribution. So members are allowed to set OK for that but should not be able to reset it after that.
I tried the hide condition but I was not able to hide it also in edit mode. In some way the hide in edit mode does not work for CB Confitionals. I also noticed that for other conditions. Is this a known issue or do I do something wrong?
CB Conditions works perfectly fine, but a fields own value conditioning it self is really weird and may not behave right. You need to first ensure CB Conditional is up to date though (latest being 4.0.5). I'm not sure what more to advise though as it's a really weird scenario. CB Conditional should be able to cover it, but I've no idea if it'll work with a field conditioning its own self.
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
