I apologize if this is a stupid question. I was unable to find anything else about this on the forums. The documentation says in several places that there should be a default routing rule to map "/team/signup" to "Team_Controller::signup()", provided that controller exists. It sounds to me like you don't need to set up a Director rule to facilitate such a mapping, and when I look at the rules via ?debug=1, I see a rule on there that SHOULD map that way as far as I can tell, but I haven't been able to get it to work. Can someone confirm that the documentation is correct? I'm looking at:

http://doc.silverstripe.org/doku.php?id=recipes:controllers (under Simulate Pages with Controllers)

And also:

http://doc.silverstripe.org/doku.php?id=execution-pipeline (under Controllers and actions)

Thanks.
Mark

Thanks for the reply. You're correct that /Team_Controller/ seems to work. I would suggest the documentation be updated in the following ways:

1. On this page: http://doc.silverstripe.org/doku.php?id=execution-pipeline

Change: "You can access the following controller-method with /team/signup"
To: "You can access the following controller-method with /Team_Controller/signup"

2. On this page: http://doc.silverstripe.org/doku.php?id=recipes:controllers

The information all appears to be correct, but I would add some clarification on this line: "More native URL-Layout (”/team/create” instead of “/myteampage/create”)" - something along the lines of "More native URL-Layout (”/team/create” instead of “/myteampage/create” - Please note the default routing would be /Team_Controller/create unless you set up custom routing)".

3. There was one other place where the documentation was explicitly wrong, but I can't find it. It was actually even worse because it had controller action methods declared as "function myaction($param1, $param2){}" which, as I understand is also wrong.

Thanks,
Mark