The user is logged in. The user want's to register for an event. Instead of needing to write and submit the form, they just click a registration button, and we get the necessary info from the user's profile.

I know this is mixing two user types (anonymous and authenticated users), so it might not be an easy thing. But as a logged-in user I do find it strange that I have to input my info again.

Possible solution for both anonymous and authenticated users:
The form for anonymous users should contain the same or a subset of the info on the user's profile. The module maps info from the profile, if a field is empty, the module display a form for the missing info. For anonymous users the module would display the entire form like today. This would mean the data from the two user types would be the same and could be merge nicely in a view.

Another solution that is a bit of a hack. If all the fields has been filled by default values from tokens, hide the form and change the text on the submit button.

Comments

jpontani’s picture

jpontani commented

One problem: there are custom fields on the registration form that might not otherwise be part of the user profile, and these custom fields might be set as required. If this is the case, you are unable to auto-fill the form.

Having them fill the form out again serves as a verification of their data. What if a user registered with one email, but wants to register for an event with a different email?

Or what if a person wants to register more than a single entry for the event if it's allowed on the entity? You don't get to see the field for the number of entries anymore.

SlashCrew’s picture

SlashCrew commented

Absolutely true. This is not a one size fits all solution.

I would like it in my usecase, where it is mostly authenticated users that register for an event, and I am trying to make it as easy & quick as possible for the user. Pre-filling the form with values from tokens is just fine. Don't let the perfect be the enemy of the good. However I do think just clicking a simple button would be better, so if it would be an easy add-on then great! If not... well okay no problem :-)

dpi’s picture

dpi
Location Perth, Australia
commented

More thoughts: http://drupal.org/node/1308894#comment-5541112

This issue seems to border on the multiple-registrations per user problem. Ideas on implementation details would be helpful

dpi’s picture

dpi
Location Perth, Australia
commented
Status: Active » Closed (won't fix)
dpi’s picture

dpi
Location Perth, Australia
commented

Let me clarify why I closed this issue.

There is always a reason to show the form: fields on registrations. Like me, if you do not care about the email field then you should implement something like this in your site feature module:

function mymodule_form_registration_form_alter(&$form, &$form_state) {
  $form['mail']['#access'] = FALSE;
}