Hi. Last year I made a registration form for an artist group for their yearly event. I made a content profile (called it artist_profile) and as the artists filled out the form for registration, they were filling out their artist profile. I created a view that was populated as each registration was completed. (http://www.maoas.com/dev/drupal/participants2010) It all worked fine. But I didn't think ahead! This is an event that will happen every year. So....
I need to create a new registration for this year.
I need the new view to be created for this year's artists.
I need last year's view to not disappear.
I need this to be easy to re-do, every year.
(Later, I also have to get it moved so the dev/drupal is not in the URL, but I don't want to mess with that until after the registration is live since I'm late getting that done.)
Does anyone have any advice for me? I'm hoping it's an easy solution that I'm just not thinking of, since I'm relatively new to Drupal.
I had one idea - create another artist profile, and call it something else (artist_profile_2011?). But I'm not so sure that's the best solution.
Thank you for any help... I appreciate your time.
Comments
If the year is the only thing
If the year is the only thing changing between profiles, you could just add a field (or vocabulary) to track the year, allowing multiple values for participants in multiple years. Then your view can accept an argument for the year and filter based on that.
If some of the artists
If some of the artists register year after year, then how would that work? Their address for example, may or may not change. Their uploaded image may or may not change... I think your idea would work if there were always new artists each year. But I'm not sure, for repeaters. Maybe I'm just not seeing it, though... what do you think?
I'm still not seeing a
I'm still not seeing a problem with adding a year to the profile content type. You'll have to backfill the year for all existing profiles, that's about it. For example, artist A registered in 2010 and has an existing profile. You go back in and fill in their year for that node to be 2010. This year, artist A registers again and now that profile tied to a new registration has a year of 2011 (you can make this a hidden field). In your view, you still filter by value.
Now, if you're using the word "register" in a different meaning than in Drupal, to mean that they don't actually create a new account but instead just sign up for the current year with an existing account, you'll need a new content type for each year's profile. Then you can do a different Page display for each year and set the path to whatever you want, like /artists/2011. You could also do it by having the content type be an argument, but your content type machine name is likely not user friendly, so that would make an ugly URL. You could also use a custom module with hook_menu() and a callback to parse the URL and convert the appropriate URL part to a content type name and use views_embed_view() to render the view programmatically, but given that you said you were relatively new to Drupal and that this only happens yearly, I wouldn't bother. The site will be rewritten long before this becomes an issue.
Yes, it's an "event"
Yes, it's an "event" registration form, as I mentioned in my original post. I should have made it more clear though that it is separate from the site registration. I created a content profile, and those registered on the site may or may not have registered for the event. And what you said after "you could make a custom module..." - you're right - I can't go there yet! That's in the future.
Thanks for helping me think this through! I think I'll go forward with the new artist profile for this year.
Why not just add a filter for
Why not just add a filter for publish date?
The other option is to make a new content type.
Ryan Price
DrupalEasy Podcast