Pageroute module destination parameter how/where?

as always seems to be the drupal case.. lots of cool things.. but they just don't quite fit together

so i am trying both zz's and fago's ideas here.. and here are the issues with both:

i am trying to put together a registration flow

• i think there is a big issue with pageroute in that it can only route to a node type - i.e. it can't route to a page like user/register or a view or...

so my best attempt so far uses:

• rolesignup - i have multiple roles to auto register for
• logintoboggon - since it has some things i need, plus it allows me to set redirect page
• registerprofile, usernodes, etc, etc...

so basically i have:

• basic login from logintoboggon
• 1 added nodeprofile since i have required fields (using registerprofile)
• logintoboggon redirects to my pageroute when done
• now i can fill out my 2nd usernode type

AND then when i am done i want to do what zz wants.. and go to some view

BUT.. the issues:

fago's:

• my register paths look like: user/register/role/5
• so i dont think it works to add a destination to that such as user/register/role/5?destination=usernode

zzJames:

• major basic issue - you can't route to non-nodes - i.e. you can't route to a view.. as far as i can tell

also i need 2 different page routes to go to depending on which role i am signing up for.. and logintoboggon will be broken here since it has only one redirect setting

so i either have to hack logintoboggon to handle this or hack pageroute

Peter Lindstrom
LiquidCMS

As I too have butted up against this limitation I've found a couple different approaches to this.

1) If the last page in your pageroute is one on which you are editing or creating a node, you can make the template for that node contain a button or anchor tag that contains the link to your intended destination. In my case, the last node in my registration pageroute is a page where the user is filling out a custom questionaire content type, and not something they'll ever edit again. So the template for this node view can contain whatever I want and I don't have to worry about anyone ever seeing this again. You may be able to create a custom type with no fields, assign it to the last page in your pageroute, and just have the template for this node contain a button that links to where you want. I haven't tried using an empty content type for this purpose however, I've only used an empty content type as a nodefamily head.

2) Another approach is to modify the pageroute code. The rubber meets the road in the function "pageroute_page_form_submit_redirect" round about line 213 at the time of this writing, in the "case PAGEROUTE_FORWARD" code. I found in DBG that when the code reached here, the $_REQUEST didn't have a destination anymore, so my pageroute was circling back to the start of itself. However, if you properly rearrange the encompassed condition, and do some poking around in the $page you can determine what pageroute you're on, and determine if you want to commandeer the $_REQUEST's destination. I did this successfully as a quick hack for a demo. But it's really a hack. Here's how it might look.

  case PAGEROUTE_FORWARD:
    if ($page->route->options['last_button'] && !$page->options['neighbours']['forward'] ) {
        if( isset($_REQUEST['destination']) ) {
            return ''; //let drupal_goto take care of the destination paramter
        }
        /*
         * Since the request does not have a destination, I'm putting in
         * this hack to check if we're on a registration pageroute.  If we
         * are, I'm going to assign "home" as the destination and let
         * Drupal just take care of forwarding.  "home" is the 
         * url to a view in my Drupal setup.
         */
        if( $page->route->path == 'registrationroute'  ) {
            $REQUEST[ 'destination' ] = "home";
            return ''; //let drupal_goto take care of the destination paramter
        }
    }
    $path = pageroute_create_path($page, $page->options['neighbours']['forward']);
    break;