This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » eZ Publish 5 Platform » routing.yml per siteaccess

routing.yml per siteaccess

routing.yml per siteaccess

Tuesday 23 July 2013 4:35:18 pm - 6 replies



is there a way to use different routing.yml file for each siteaccess?

I would like to make a route not accessible for a certain siteaccess.




Tuesday 27 August 2013 3:40:53 pm


so the usecase is following:

we have for example a contact form which is a symfouny route, lets's say /Service/Contact. In eZ backend I have a node called Service. Below this I create a new node called Form. The new node get's the url /Service/Form and is shown in the Menu. In Frontend if I click on this menu point I get to the symfony route. The problem is that the same happens in the backend. 

So there would be the question if it is possible to disable this route for the backend siteaccess.



Thursday 19 September 2013 12:41:08 pm


did you find a solution for this because i have the very same problem?

thx &br

Thursday 26 September 2013 4:44:39 pm

Hi Konstantinos

You're talking about both /Service/Contact and /Service/Form. I guess you were mixing URIs and wanted to talk about the same route ?

It's true that this case is not covered and is actually an annoying issue. My take would be that if we're in legacy_mode: true (which is the case for admin), we should bypass both URLAliasRouter AND Symfony router. Currently, only URLAliasRouter is bypassed.

Thursday 26 September 2013 5:03:04 pm

Issue reported:

Modified on Monday 30 September 2013 2:19:20 pm by Jérôme Vieilledent

Monday 30 September 2013 2:18:51 pm

Pull-request for review:

Monday 07 October 2013 1:53:02 pm

Fixed in master:

Please be sure to also read the BC note.

Modified on Monday 07 October 2013 1:53:41 pm by Jérôme Vieilledent


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from