2 issues with registration

I am having 2 issues with registration/profile. The first one is that one field requires a special css styling. This is already set up and working. However now it shows the same styling on registration page as well. I beleive I can solve this with css if I would know which specific id or class I need to attach the css to for profile only.

The other thing is that I am using step by step registration and due to the specific css profile styling of the field it has to reside on a tab on his own. However for registration this turns out to look weird having a registation step which consists of only one field.
So basically my question is if there is a way to put several fields from different tabs into one registration step.

I am having 2 issues with registration/profile. The first one is that one field requires a special css styling. This is already set up and working. However now it shows the same styling on registration page as well. I beleive I can solve this with css if I would know which specific id or class I need to attach the css to for profile only.

Prefix your selector with .cbProfile to specifically target profile view. All locations have a similar unique class, inspect the DOM by pressing F12 to bring up the developer console.

So basically my question is if there is a way to put several fields from different tabs into one registration step.

No, you should actually do the reverse. Have your various fields on the same tab as needed then use a delimiter field and substitution in your fields for profile view and set the delimiter field to not show on registration.

So basically my question is if there is a way to put several fields from different tabs into one registration step.

No, you should actually do the reverse. Have your various fields on the same tab as needed then use a delimiter field and substitution in your fields for profile view and set the delimiter field to not show on registration.

I was thinking about that but then it came into my mind that there might be an issue then with profile edit. The field in question is Ajax Text field. So the user will be able to change it without reloading the profile page. Now if that field is set to be a delimiter field I beleive the user is not able to change it?

Now if that field is set to be a delimiter field I beleive the user is not able to change it?

They should still be able to edit it if it's rendered with formatting. Example as follows.

[cb:userfield field="FIELD_NAME" formatting="div" /]

Please see the below tutorial for further substitution usage information.

www.joomlapolis.com/support/tutorials/107-use-cases/18353-using-substitutions-throughout-cb