Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Upgrading SilverStripe /

Ask questions about upgrading SilverStripe to the latest version.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Upgrade to SS 3.2 , problem with Routing to Controllers extending from Page_Controller

Go to End

3 Posts   2002 Views


Community Member, 791 Posts

5 November 2015 at 11:23pm


In a few of my old sites, I'm using controllers that extend from Page_Controller , without pages.

I usually created a route to map a URL to the appropriate Controller.

Now, In the SS 3.2 , this stopped functioning , the docs say:
Please access any custom controllers exclusively through self-defined routes. For controllers extending Page_Controller, simply use the provided page URLs.

I do not need a page for this Controller in the sitetree , but do need to extend from Page_Controller. Probably, I'm missing something, but I can't really figure out how to get this to work.

Thanks !


Forum Moderator, 267 Posts

13 November 2015 at 3:26pm

Hey Fuzz10, this is likely related to this change in 3.2
You may need to explicitly add a route to access your controller action.


Community Member, 44 Posts

2 December 2015 at 3:58am

It's definitely related to that change camfindlay pointed out, but fuzz10: I can't find a solution for routing url's to controllers that are extended from Page_Controller either. I'd like to bump this thread, running into this issue myself.