Of course MODx supports friendly URLs and ressource aliases. But the "alias path" handling is poor. If turned on, the web developer faces several problems:
* Wayfinder links are broken on 2nd-level pages and above, because they render no leading slash. You have to manually modify the Wayfinder templates and add a / before every href value.
* Same goes for several other add-ons
* The leading slash is not rendered by the
<a href="[[~42]]">Internal link syntax</a>
. You must write it
<a href="/[[~42]]">this way</a>
* The official reference tells you to use <base href="/"> to fix those problems (http://rtfm.modx.com/display/revolution20/Using+Friendly+URLs
) Well, this is kind of old-fashioned. And it does not work with internal anchor jump links (They lead to the start page). It’s a lame solution :-(
It is important to have not only friendly, but also semantically correct URLs - and MODx should offer a less complicated way to use nested URL schemes.