Closed jeremyboggs closed 11 years ago
Makes sense. We integrated the THATCamp Profile plugin into this one, so the name, Twitter, website fields are updatable in the user's profile, but you're right that the other fields are camp-specific, so it doesn't make sense for them to be on the user profile (which persists across camps).
I'm not worried about those 3 fields being editable after the first entry ( #64 ), and I think it would be a little tough to figure out how to enable that, but you're definitely right that they should be displayed on the public login form for logged-in users. When checked by the site admin, of course.
Agreed that editing after submission isn't a priority. Will send a pull request that displays those fields to authenticated users.
I did BTW realize that it does make sense to add the t-shirt size field back to the user profile. Any chance you'd do that while you're at it, you coding machine, you?
The registration form just displays the "Why you wanna come to THATCamp?" text field for authenticated users. This skips several other fields that are camp-specific: Days attending, t-shirt size, and children. There also doesn't appear to be any way for individuals to update their applications with this information after its been submitted.
I'd suggest displaying those fields so folks can complete them during the registration process, even if they already have a thatcamp.org user. Not sure the fields that would be consistent across camps—name, twitter, website—necessarily need to be shown. There could be reasons for displaying other fields too.
Any thoughts on this? Happy to send a pull request addressing this, if there's consensus on how exactly it should be addressed.