Better alias path handling - My Forums

Re: Better alias path handling

Fildefer57 — May 01, 2016, 05:34 AM

with modx url are simple to handle as long as you put a tag in your html.

for Named anchors, solution is pretty straightforward and given in the documentation page
https://rtfm.modx.com/revolution/2.x/making-sites-with-modx/structuring-your-site/resources/named-anchor
under the Using a Plugin to automatically add the URL when using anchors section of the page

Re: Better alias path handling

exside — Nov 20, 2011, 10:00 AM

Got also the issue with the jumplinks...something like

Jump

won't work...is there a way to solve this?

Re: Better alias path handling

markh — May 28, 2011, 08:58 PM

To me it says "Feedback"? Not sure what you’re looking at.

Re: Better alias path handling

krisj — May 28, 2011, 08:50 PM

so, i see the bug has not been fixed... in fact the status says something along the lines of "deleted" huh?

Re: Better alias path handling

markh — Dec 17, 2010, 05:21 PM

makeUrl has a scheme parameter which can be used to automatically prefix the link with the site_url or base_url. (see http://rtfm.modx.com/display/revolution20/modX.makeUrl)

I think you could use this:

[[~42? &scheme=`full`]] to force it to use that scheme.

Perhaps a concrete suggestion to improve alias path handling is a system setting you can use to determine the default scheme makeUrl uses. That way you can choose to use relative paths and base href, or use absolute paths and don’t have to bother about it.

As far as I can imagine right now, that would be as simple as making the makeUrl function check the system setting and base the default behaviour on that. I think the default should stay what it is now though, as most websites have probably accepted it the way it was and worked around it. So then an upgrade would break it.

( Bug report about this: http://bugs.modx.com/issues/2726 )

Re: Better alias path handling

chucktrukk — Dec 16, 2010, 12:37 AM

I really like the idea of adding the site_url in front of the url when parsing.

Is there any real good reason not to?

It would keep us from having to create a plugin to get #targets to work.

Better alias path handling

gerritvanaaken — Oct 05, 2010, 05:05 PM

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

Internal link syntax

. You must write it

this way

* The official reference tells you to use 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.