1

Backstory: Ok, I have a site where users can post events, rate them, attend them (everyone can see who will attent) and such. Now I want to make it so you can add variables to users, which resembled what they did. for instance: User: Anon had a red jacket and was drunk.

Then I would like a list that is unique PER event with these variables which the users can add to their own profiles. (so everyone can see what they did/had at that specific event)

for instance: List of events: Color run, Jumping, Racing "User goes to event "color run" and there is a list with: "what resembles you at this event: -Drunk -In a group -Red jacket"

Then they select "drunk and red jacket" and submit/bookmark.

Now I want this to be saved to their profile so when they go to their own profile it will look like this:

profile>events>color run>

  • red jacket
  • drunk

and for a different event it could be that they chose something else and that would show up. Any ideas how to make this reality?

I was thinking about using blocks but I have no clue how to make the multiple select part.

1 Answer 1

1

Consider using the Profile 2 module. Excerpt from its project page:

Designed to be the successor of the core profile module, which is deprecated for Drupal 7. In contrast to the deprecated module this module provides a new, fieldable 'profile' entity - leverage the power of fields.

That project page contains a lot more interesting info, such as these Features which might help for addressing this question:

  • Multiple profile types may be created via the UI (e.g. a general profile + a customer profile), whereas the module provides separated permissions for those.
  • Optionally, profile forms are shown during user account registration.
  • Similar to the deprecated core profile module, fields may be configured to be private - thus visible only to the profile owner and administrators.
  • By default the UI behaves similar to the deprecated core profile module, thus showing each profile type in each own tab below user//edit. Via the included "Profile pages" module profiles can be viewed and edited at their own page and get their own menu link, e.g. "My profile".
  • Thanks to the foundational entity API the module integrates well with Rules as well as Features - thus profile types and the associated fields can be exported into feature modules. Once the Entity tokens module (part of the Entity API) is turned on, there are also token replacements available.
  • You may use Views and/or the Search API to provide listings or searches for profiles.

Refer to its community documentation also for more details about this module.

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.