Changing the "alias" label

+1 markhurd

Alias is good too.

With the awesome documentation coming along, and the always active communauty, they will have an answer right away.

IMO, alias is too pervasive throughout the literature and code associated with the project. Changing at this juncture doesn’t seem to prudent to me. This is what the description should explain.

Another alias for alias would be a bad alias...

Totally agree that it needs to be hinted better for non-web folks (clients)... here’s another suggestion to throw into the mix:

Alias (Friendly URL): [______________]

Quote from: debussy at Sep 21, 2009, 12:34 PM

Totally agree that it needs to be hinted better for non-web folks (clients)... here’s another suggestion to throw into the mix:

Alias (Friendly URL): [______________]

But it is not, by itself, the friendly URL for the Resource, i.e. if using friendly_alias_paths it would be concantenated with all of the parent alias’ + a content type extension. I think it would be great to show this in a read-only field as well, but it is not the same, in and of itself, as the alias.

The alias can be used for other things as well, so I think it’s better in this case to educate and provide informative descriptions for the field.

It may be a good idea to give a direct hint on how the complete page link will look like with the current setting.

If friendly URL is not activated, the div show http://www.mywebsite/index.php?currentid

If activated the div would show the current alias: http://www.mywebsite/myalias.htm

It could be above or under the alias textbox or just under the page title.

I vote for not changing it.

I agree that keeping it as alias is probably a good idea due to the fact that this term is familiar to most users, and as mentioned, is pervasive in all the documentation and forums. Besides, alias makes sense, because that’s what it is, an alias (another name for).

I vote for not changing it.

I agree that keeping it as alias is probably a good idea due to the fact that this term is familiar to most users, and as mentioned, is pervasive in all the documentation and forums. Besides, alias makes sense, because that’s what it is, an alias (another name for).

second that

Why not switch to "Web URL" instead of "alias", which more people will understand.

the non tech-savvy clients i know struggle even more with the term "url"

Just a thought:

"Alias" has to stay, simply because it’s everywhere in the documentation and updating it would be a chore not worth the effort. However, "URL Alias" works for both making it a tiny bit easier to understand and requires no documentation updates since "Alias" is it’s short form.

I thought about:

Alias (FURL Title)

But I really think just plain Alias is as good as it will get. Everyone knows that an alias is another title for something and that’s what it is.

Here’s a preview from the book showing (IMO) how well alias works:

Documents in MODx are very similar [to MS Word Documents] but are adapted for use in web pages. For example, they have more than one title. There is a short title (Title), a longer title often used as a page heading (Long Title), a title for use in menus (Menu Title), and a title for use in URLs that point to the document (Alias).