Please Log in or Create an account to join the conversation.
That validation for non-core email address fields is just the ajax validation. It's not enforced (only core email address is enforced) and does not utilize a wildcard so your scenario wouldn't happen for CBs email fields. They can still save their profile perfectly fine by ignoring it. It also does not check against every email address field. It only checks against email addresses within that fields column. Nor does CB store its fields in _users beyond core Joomla username, name, email, and password. Are you sure you're talking about CBs profile edit and not Joomlas?I love that I can declare a field as type "Email Address" and CB will validate it against every other email address in the database, including the ones in the #__users table. HOWEVER, I think there may be an issue in the algorithm being used to do that validation. I have a user whose profile includes an alternative email address field that contains an address that differs by a single-letter prefix from the account email (e.g., account email is abc@mydomain.com and the alternate in the CB field is m.abc@mydomain.com). CB will not let the profile be saved because it thinks there is a duplicate address somewhere (there isn't...I checked...thoroughly). User is frustrated and I have to maintain this user's profile myself via backend manual database updates or change the field to a regular text box, losing the otherwise very useful CB validation. User cannot change account password (bad).
Your field must've been a select, radio, or multicheckbox at some point where you had options specified for it. It was then changed to a terms and conditions field, which does not have options. That error is saying options exist in _comprofiler_field_values for a fieldtype that shouldn't have options. You can safely ignore it or manually remove those entries in _comprofiler_field_values.The second issue has to do with the "terms" field type. There are two fieldid values associated with this field type, one indicating the user has accepted and one the opposite. When I run the "Check Community Builder Database" tool in the back end, I get the following warning. Not sure what to do about it since I'm pretty sure CB set this up (I did not). Looking at the two fieldvalueid values, they are the same (154) which is type "term". This seems correct to me, so I don't understand this warning.
Please Log in or Create an account to join the conversation.