This is a very small tweak: the instructions for creating a path alias are too technical.

The advice which appears onscreen in v4.5.2 says

Specify an alternative path by which this data can be accessed. Use a relative path and don't add a trailing slash or the URL alias won't work.

(emphasis added)

But the secind sentence will be confusing for non-technical users: most users don't know what a relative path is.

I suggest a better wording would be

Specify an alternative path by which this data can be accessed. Use a relative path, i.e. one which does not begin with a slash. Don't start with a slash and don't add a trailing slash, or the URL alias won't work.

At the risk of making it all too verbose, it would be nice to add a few examples:

Specify an alternative path by which this data can be accessed. Use a relative path, i.e. one which does not begin with a slash. Don't start with a slash and don't add a trailing slash, or the URL alias won't work (e.g. "help" is fine, but these are wrong:"/help", "/help/" or "help/")

The text appears twice in path.module: in function path_form() and function path_nodeapi(), at lines 178 and 211 respectively

Comments

cherylchase’s picture

Title: Clearer instructions for path alias on page creation screen » How about validating the input?
Category: task » feature

I also just had a user create a node with a leading slash in the path. This caused considerable problems -- clicking on the page produced a 404, and she *could not edit the page either*, so delete was impossible. I deleted the page for her in sql. Instead of clearer instructions, how about if the path module validates the data, and removes leading and trailing slashes?

Rick Cogley’s picture

This is the best way, I think. For a non-technical user, it's too complex and too prone to error to even have to explain it to end users.

forngren’s picture

Version: 4.5.2 » x.y.z

Fixed in later versions

forngren’s picture

Version: x.y.z » 4.5.2
Status: Active » Closed (fixed)

Why did I do that?