If we set a field to "just read" the user can put in information, thats bad.
And we want to set standard values for registration in some fields, but we do not wanna show these fields in registration. But if we do not show these fields in registration, CB deletes the standard values in the fields...
Read Only fields intentionally work like that. They're editable during registration, but not during profile edit. If also don't want them editable during registration then don't display it on registration. You can force default values to fields using CB Auto Actions acting on the after registration trigger and using a Field action to set the fields value to whatever you want.
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.