Multistep should handle entities other than nodes

I have been thinking about that for a while now... making Multistep entity-based, rather than node-based. I haven't had time lately to tackle these issues, but next week, at DrupalCon, I usually get a lot of inspiration during code sprints. I would love to get other people involved in this as well.

I would love to use this on the regular account fields or on profile2. Subscribing.

I have a module that modifies profile 2, I'll try to hack code from this module into that to make it multi step. Not sure what it takes to go from that to patching Multistep.

subscribe

sub

Sub

@thebuckst0p
@vkareh

I'm willing to pay for this fix. Would you guys be interested in this?

@all
Someone else interested in sponsoring this fix?

Strapped for cash at the moment, but would like to help with patching if I can. Sorry!

although no showstopper, this seems very sensible and important for quite some use cases.
will see if i can spare some time.

subscribing

subscribing

subscribing

subscribe thx!

This must be a feature request.
The last "subscribers": have you noticed the green "Follow" button at the top-right corner? :-)
(which is now "gray", saying "Following", since you have actually posted in this thread, but initially it is green, and that is the new way of "subscribing" to issues)

This was started back in March.... So has there been any progress on updating the module to use entities instead of nodes only?

Multistep is based on Field group, but that module now supports a new group type - multipages. Which work with Profile2.

Since the original issue was to work with Profile2, I just wanted to chime in and say using multipages as stated above worked great for me.

The combination of Profile2 plus field_group only works on a single profile type right?

@wiherek and @klucid : are you suggesting using multistep + profile2 makes the user register page capable to step through all profile types (listed on admin/structure/profiles)? Or are you suggesting multistep is _not_ needed?

This module offers many advantages over FieldGroup's new native multi-page functionality.

I am creating a user profiling site and am using FieldGroup's multi-page but would jump to this if it worked.
A status update would be great ?

I can see that it adds the multistep as feildgroup formatter option in the UI but when chosen, it does not create a step nav block or render any multistep pages in the user edit form.

just to reiterate, we are talking about user accounts - not nodes.
The move to entities does mean that this is in reach though.

Are there any updates aput that? In my eyes the advantage of this module prior to multipages is that with every step the node is saved. Multipages is just a little JavaScript deviding the whole form in separate steps but click on "next" does not any saving.

I've had a go at this and it seems to be working OK. Changed all instances of nid/node to id/entity and added entity type as an additional argument to relevant functions.

One more major change is I'm using hook_form_alter instead of hook_field_attach_form to add the multistep form elements/actions. This is because I wanted to get access to the entity form #submit key to get the entity form's submit callback (I didn't know any other way to get it from entity type / bundle - any ideas?) and couldn't access the parent entity form from the hook_field_attach_form $form (field subform). So I've added a hook_form_alter which checks if keys #entity_type, #bundle and #entity are set - is this enough to test that it's an entity form? The form alter then calls what used to be the hook_field_attach_form function.

I created this quick patch to get the user profile form to work, the above patch didn't enable this

Fix to namespace

Thanks for the patch @generalconsensus but I am getting some errors while patching.

module.patch:8: trailing whitespace.

module.patch:9: trailing whitespace.
/**
module.patch:10: trailing whitespace.
* Implements hook_form_FORM_ID_alter().
module.patch:11: trailing whitespace.
*/
module.patch:12: trailing whitespace.
function multistep_form_user_prof

I couldn't remove that patch from the post, i have another patch I'm working on that fixes a ton of the issues I originally missed. Sorry for the poor explanation

Be advised that I've created a 7.x-2.x-dev branch which solves this problem and adds additional features. Please review and let me know if this fixes it for you