Home/ Questions/Q 905207
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T16:10:47+00:00

Is there an intrinsic reason why I can’t, in routes.php, route a user based

  • 0

Is there an intrinsic reason why I can’t, in routes.php, route a user based on the contents of a session variable? e.g.

Router::connect('/dashboard',
    array('controller'=>'users','action'=>'dash',1)
);

works okay, but, replacing the 1 with $_SESSION[‘userid’] doesn’t.

Am I missing something important about session variables here?

Alternative suggestions for rerouting a logged-in user from /dashboard to /controller/view/$userid without using a session variable would be equally appreciated!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The session is not yet started when the routes are parsed. If you’re using Cake’s session handling, they’re started by the Session component, which only loads together with a controller, which happens after routing.

    You shouldn’t make routes dynamic either, since they’re used for reverse routing:

    Router::connect('/dashboard', array('controller'=>'users', 'action'=>'dash'));
$html->link('…', array('controller'=>'users', 'action'=>'dash'));
// -> /dashboard

    If you’d make this dynamic, this wouldn’t work as expected anymore:

    Router::connect('/dashboard',
    array('controller'=>'users', 'action'=>'dash', $_SESSION['user']));

$html->link('…', array('controller'=>'users', 'action'=>'dash', 1));
// -> /dashboard

$html->link('…', array('controller'=>'users', 'action'=>'dash', 2));
// -> /users/dash/2

    Routes should be a static affair. Routes define your applications URL schema, like a map. It’s simply not the place to do any “real work”. Everything dynamic is happening in controllers.

    • 0