Issue with Public Display of Names in Community Builder

Hello,

After a migration from J3 to J5, I encountered an issue with a public list that displayed a bit too much information, such as email addresses.

I had to act quickly by restricting access to the list to members only.After updating to the latest version of Community Builder with a pro license (each of my clients has their own license), the public version works, but now I can only see the first and last names when logged in. For other fields, there’s no issue—it's strange!

I’ve checked the field and list permissions but can’t find anything unusual. I usually manage things on my own, but this time I really need to get things back on track to maintain the site on Joomla and CB, and I need help.

The entire list became public when it previously wasn't? or fields start displaying on it that previously didn't? I'm not sure why Joomla migration would have any impact on CBs userlists as Joomla version is largely irrelevant to CB since it's designed to be heavily version agnostic.

Sounds like maybe you were protecting specific fields with CB Privacy or maybe CB Conditional and either of those stopped working? If that's the case you'd need to login with an account with a valid subscription and post in the support forums, but both are confirmed working on Joomla 5.

If you're not using either of those plugins then field access permission is entirely based off their tabs in CB > Tab Management as individual fields don't have access permissions beyond location based yes/no toggles.

Indeed, I have both plugins installed and everything is up-to-date with the Pro version of CB.Eureka! It was the "account" tab that was restricted to the "members" user group. I simply switched it to "public access." After adjusting a few details, everything is working perfectly.Normally, I would have found this sooner, but for some reason, I double-checked everything except the tabs.Note: I encountered an error with the captcha image during account registration. I simply reset the setting by re-saving in cb_antispam, and that also resolved the issue.Perfect! Thank you, Kyle.