Backend User Edit - No fields visible

Try unpublishing all non-core plugins 1 by 1 within CB > Plugin Management until issue goes away to see if it's an installed plugin causing the issue. If issue persists PM backend super administrator login credentials and will take a look.

Also moving your topic to support forums for better visibility.

I've PM'ed you. We only had one non-core plugin installed and it was unpublished already. I also tried unpublishing several core plugins not in use, but the issue still persisted even then.

I've found the problem. A 'hidden' class had been manually applied to each of the tabs. I believe it was assumed that the class field value would only apply to the frontend. That may be a good option to add in the future, either a 'apply class to frontend/backend/both' or separate frontend and backend class fields.

Why are you trying to add hidden class to frontend? Move the tab to a not shown on profile position or set the fields on the tab to not be displayed if you don't want the tab visible. You can also use CB Conditional or CB Privacy to safely adjust displays. There are no plans for 3 parameters for adding a simple CSS class, sorry. There are classes available for custom CSS to differentiate from backend and frontend and recommend using more specific CSS classes.

We didn't want the data to be visible but we still needed it available for display in another manner. If the field and/or tab is set not to display, then the data is not available to be displayed otherwise. Likewise, with the use of CB conditional and CB privacy. Elsewhere in Joomla, a CSS class field value is only applied to the frontend. So the "Joomla Way" is to no apply a class field to the backend. It was assumed that CB was using Joomla methodology. Now we know.

We didn't want the data to be visible but we still needed it available for display in another manner.

In profile edit or on profile view? If profile view move the tab to a not shown on profile position. If profile edit you can use CB Privacy to suppress its edit display under Integrations > CB Privacy while editing the tab.

Likewise, with the use of CB conditional and CB privacy. Elsewhere in Joomla, a CSS class field value is only applied to the frontend. So the "Joomla Way" is to no apply a class field to the backend. It was assumed that CB was using Joomla methodology. Now we know.

The CSS Class for both tabs and fields are both applied to backend. At this time we've no plans to change this behavior but we likely will once we redo the field API.