Timeline for Routing and path aliases
Current License: CC BY-SA 3.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 10, 2017 at 17:40 | answer | added | Jes Constantine | timeline score: 2 | |
Jul 27, 2016 at 12:25 | answer | added | 4uk4 | timeline score: 1 | |
Jul 27, 2016 at 11:37 | comment | added | Clive♦ |
{node} refers to the node's ID, which is then upcast to a node object for the controller. It doesn't refer to any URL alias you may have for the node. To get what you're looking for, you'd need a custom upcaster that searched for and found the node based on its alias
|
|
Jul 27, 2016 at 11:12 | history | edited | MrUpsidown | CC BY-SA 3.0 |
added 51 characters in body
|
Jul 27, 2016 at 11:01 | comment | added | MrUpsidown | @4k4 could you please elaborate a bit more? I don't much understand your comment. Also please see my edit in the question where I explain the goals. | |
Jul 27, 2016 at 11:00 | history | edited | MrUpsidown | CC BY-SA 3.0 |
added 320 characters in body
|
Jul 27, 2016 at 10:27 | history | edited | avpaderno♦ | CC BY-SA 3.0 |
improved grammar and formatting
|
Jul 27, 2016 at 10:15 | comment | added | 4uk4 |
The aliases is only valid for the full url, not parts of it. If you want /dossiers/my-custom-path/dossier to work, you have to use the complete url as alias.
|
|
Jul 27, 2016 at 10:02 | comment | added | MrUpsidown |
Since the path alias already contains the /dossiers part of the path, I also tried with path: '/{node}/dossier' but that didn't work either.
|
|
Jul 27, 2016 at 9:57 | history | asked | MrUpsidown | CC BY-SA 3.0 |