My understanding is that the purpose of this module is fundamentally to make it super easy to participate on a site the first time(s).

Would like to suggest this be done in two ways:

  1. Persistance via session with no user created (current focus).
  2. Allow normal registration during node creation.

This seems like a good addition at face value, which I'm willing to get working.

The bonus with #2 is that with Email Registration and Logintoboggan you can reduce registration to just email and gain immediate login with a special role.

This pretty much creates a mode of persistance via user account with flexible user inputs leveraging existing modules.
A user can get a "session" back by running forgot password to get the password for the first time... if an admin chooses not to send the original email.
Additionally, this solves a few other issues like: using normal profiles rather building a special one, building block user functionality, etc.

Anyhow,
Looking to get synced on the general purposes and approaches.

Comments

doublejosh’s picture

BTW: It's possible this is a separate issue that should just be here: http://drupal.org/project/inline_registration

icecreamyou’s picture

Title: Additional module mode (meta question) » "Save and register" button on node/comment forms

That is an interesting workflow. I'm not sure it's a good route to potentially lock people out of their account and require them to go through the "forgot password" process when they never even set a password in the first place; if you do that a lot of people will just create new anonymous accounts or be frustrated that they can't log in. But it sounds like you can do this with other modules if you want.

I don't want to put the whole registration form inside the node/comment create form, but I'm okay with a "Save and register" button or similar. I think that's the only action item here, so changing the title to reflect that.

doublejosh’s picture

It's true that if you hide the password you REALLY need to use the Shared Email module to allow multiple registrations.
OR play up via messaging that you'll need to get your password via email (still somewhat of a norm) or play up the forgot password link as a "get password" link.

It actually looks rather nice to throw a small registration form at the bottom of the node form... but I guess that'll have to be done via inline_registration.
Probably switching to working on that.
Though this approach is nice... especially for higher volume when you want to avoid creating a bunch of unlikely-to-continue users.

doublejosh’s picture

Issue summary: View changes

typo