Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Hm...bug or "feature" ?
Right now it's a "feature": the "default" value is only set as a proposed value during registration for fields shown on registration.
So if a field is *not* on the registration form, CB doesn't put that default value for the user "behind his back"
What are community thoughts on this ?
Please Log in to join the conversation.
Please Log in to join the conversation.