Just a quick question about the route prefixes system that has been implemented, which look really nice:
It looks like the mapping is done in only one direction, you can map a route prefix to a controller and it's action.
But what if I have a controller and an action and I want to build a link for it?
There doesn't seem to be such a thing as a "default route prefix".
If you use the buildPublicLink method, it will try to find a mapped controller, if it doesn't find it, it just goes ahead and uses the "basic" build method
An example: when someone changes the "members" route prefix to "users", they will have to change all the references in the templates and the code to that prefix (eg. tabs.members.href) in "navigation" template or (XenForo_Dependencies_Public->_getNavigationContainerParams()).
This would not be needed if each controller had a "default route prefix", which in this case could be changed to "users" while "members" would still exist and work (maybe just redirect it to "users")
Is that correct or am I missing something?
Also: in what situations would someone want to have more than 1 route prefix pointing to the same controller?
It looks like the mapping is done in only one direction, you can map a route prefix to a controller and it's action.
But what if I have a controller and an action and I want to build a link for it?
There doesn't seem to be such a thing as a "default route prefix".
If you use the buildPublicLink method, it will try to find a mapped controller, if it doesn't find it, it just goes ahead and uses the "basic" build method
An example: when someone changes the "members" route prefix to "users", they will have to change all the references in the templates and the code to that prefix (eg. tabs.members.href) in "navigation" template or (XenForo_Dependencies_Public->_getNavigationContainerParams()).
This would not be needed if each controller had a "default route prefix", which in this case could be changed to "users" while "members" would still exist and work (maybe just redirect it to "users")
Is that correct or am I missing something?
Also: in what situations would someone want to have more than 1 route prefix pointing to the same controller?