Thread

I’m building an EE 1.6.9-based site for which we’re setting up a number of different member groups; some are to be used by our clients who will be running the site and inputting content, while others will be for different types of customers. These customer member groups need to use different sets of custom profile fields, but near as I can tell, any custom profile field you create will be added to all of the different member groups.

Does anybody know of a way to include custom profile fields only on specific member groups, or to create custom profile field groups and assign them to member groups (basically the same way it’s done for weblogs)? Or, if there’s an existing add-on that handles this that I somehow haven’t tracked down, I’d be grateful if somebody could point me to it.

I’ve been spending the past two hours or so digging around on add-on catalogs (like http://www.devot-ee.com) and in various forums (including this one), I and haven’t found anything that could help me out with this, so I figured I would ask here and hope somebody would be able to provide me with an answer. Sorry if this is a commonly raised issue or if there’s something really obvious I’ve overlooked.

Sounds like you need the Solspace User Module - that will allow you to create your own profile edit templates. You still only have one set of profile fields, but by using templates and a few conditionals you can customise what each user group is allowed to modify.

Thanks for the assist, Rob.

EAInstitute35, does that help?

I ended up creating a solution that was a hyrbid of using the User module from Solspace (which we already had installed), and an implementation of a solution similar to this one: http://ellislab.com/forums/viewthread/162068/

Essentially it involves creating custom edit profile forms via the User module, with a weblog entries tag that searches for posts by the currently logged in user, and serves up links to the appropriate “Create New” or “Edit” SAEFs based on whether it finds anything or not.

The experience for the user on the front-end is totally seamless, but by setting the more advanced “profiles” we wanted up as weblogs, we can now leverage more custom field types (such as multi-select lists or multiple image uploads, to name just two), and we can restrict each set of custom fields to the appropriate weblog (or “Profile” type) based on the member group of the logged in user.

Sounds like a neat solution. Feel free to start a new thread if you have any more questions.