CiviCRM Community Forums (archive)

why wouldn't you be able to wrap all three in a fieldset and make sure they're not in the included files? that would be my first suggestion.

i believe a fieldset may only have one legend, and it should be the first tag after the fieldset tag. so i'm not sure you're sample would work.

FWIW -- I run into the issue where the email chunk looks odd because it's separate from the rest and not contained in a fieldset, so the styling looks weird. I usually just wrap it in it's own fieldset with legend to retain consistency.

you know, another option to look at --
I believe that the form on those pages unsets the primary email address if it's included in the profile (so you don't have duplicate primary email address fields). it would make more sense to hide the hardcoded email address block IF the primary email address is included in the profile. may not be a big deal to switch that around. that at least gives you the flexibility to control the location of the email within the profile.

Pete,
i wasn't suggesting leaving out the included files --
just modifying them so that they didn't have the fieldset tags. that's how i read your initial post.
i guess the concern would be that they might be included elsewhere, and the lack of fieldsets would throw off formatting. but i'm pretty sure Civi does a decent job keeping the contrib page templates separate from others.
-B

Knowing that the more thorough write up could be a way off ;-) here is the summary

In order to get the Username, Email and Profile all in the same fieldset required the following

1/ reorder the includes in the Main.tpl

2/ comment out the fieldsets in the CRM/common/CMSUser.tpl

3/ comment out the fieldsets in a customised CRM/UF/Form/BlockXX.tpl

4/ recode the include file in Main.tpl to look for the above customised BlockXX.tpl (so the deleted fieldset doesn't affect other places that Block.tpl is used)