next button does not redirect

Yo,

I'm using the 5 version and getting something similar. While editing a node the next button does not work.

[update] turns out that this only happens when directed to editing the node using the admin_hover menu. The menu links to http://mysite/node/124/edit?destination=node%2F124, instead of http://mysite/node/124/edit, which for some reason doesn't allow redirection to the next fieldgroup.

I should file this as a separate issue, but should I be looking for help from admin_hover peeps to fix my issue? Obviously edit?destination=node%2F124/2 won't work with multistep.

I have the same problem in 5.x and I'm not using admin_hover.

I changed it so that it will not redirect when using the &destination URL parameter. It should work now from wherever you call the edit form. It's part of the new development snapshot, please update and let me know if this solves you issue.

To do: change it so that it will redirect to the original intended destination *after* submitting all the steps of the form.

hi,

we using the multistep module with profilesetup(http://www.drupal.org/project/profile_setup) and page route.
while in the route in doesn't switch to next group, it goes to the next page assigned in the route.
Could you please check this.

Regards
Sagar

If I understand correctly, you want a pageroute of multiple multistep nodes? It's not something I've ever tried.

So, the problem is that instead of doing all the steps in a node type before moving on to the next node type in the route, it's redirecting to the next node type in the route without going through all the steps of a single node type?

Hi,
Thats correct, the multistep form doesn't work with the pageroute. The next step ideally should go to the next group of the content type however it goes to the next page configure in that route.

Okay, I finally got to try the pageroute module. The problem happens because the multistep module relies on the step being part of the URL parameters, whereas pageroute creates an alias for a particular route, thus hiding the step parameter.

For these two modules to work together, there are two possible solutions:

1. Changing multistep's approach of using URL arguments. This will render the step menu useless and you wouldn't be able to jump between non-consecutive steps.
2. Somehow modifying pageroute to respect URL arguments while changing from page to page. This will also entail a slight change in the multistep module, but I'm willing to do it if it solves the problem.

One other solution that I can think of would be to not use the pageroute module, but create a multistep form and add a Path Redirect to the URL of the last step, so that it redirects you to the next part of your "route".

I am experiencing the same issue in both the latest stable and development releases of Multistep for Drupal 6. When I edit a node with multiple steps, the [ < Previous ] and [ Next > ] buttons simply reload the current page, whereas the Multistep block links all work fine.

Why isn't this working? It seems pretty critical to this module.

Working with Form Block still doesn't work.