Create a page and give it the path alias, 'fred'. Then, try to add a menu item to primary links with the title 'Fred' and the path 'fred'...

You get "The path 'fred' is either invalid or you do not have access to it."

I'm running as user 1, will full privileges, so that can't be it.

This error happens in all the beta's for 6.0 that I've tried. All have been clean installs -- not updates.

It seems like someone should have bumped into this by now -- is there some new setting somewhere that I need to change?

I'd really appreciate some help on this.

Thanks,

m

CommentFileSizeAuthor
#8 spacing.patch1.01 KBJirkaRybka
#6 normalize.txt861 bytescatch
#4 normalize.patch832 byteschx
#3 normalize.patch830 byteschx
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ScoutBaker’s picture

ScoutBaker CreditAttribution: ScoutBaker commented

Duplicated under D6 HEAD - clean install. Specifying the full URL (http://www.myexample.com/fred) for the path when creating the primary link works.

sumgai’s picture

sumgai CreditAttribution: sumgai commented

Thanks for duplicating the error and showing that using an external link works.

But, it should work as I tried, shouldn't it? Define menu item "Fred" to be path alias 'fred', should work fine...

It did in all previous versions of Drupal that I've used.

I hope this isn't some type of new "feature"...

chx’s picture

chx CreditAttribution: chx commented
Status: Active » Needs review
FileSize
normalize.patch830 bytes
chx’s picture

chx CreditAttribution: chx commented
FileSize
normalize.patch832 bytes

Bah.

sumgai’s picture

sumgai CreditAttribution: sumgai commented

So this means the path will be stored as opposed to the alias?

If so, that's not good.

Why have an alias if the menu item is going to point to the path? If I change the alias to point to a new url, everything will work fine in the pages on the site except for the menu.

This is a significant step backward!

Why can't the menu system continue to support aliases?

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented
Version: 6.0-beta3 » 6.x-dev
Status: Needs review » Reviewed & tested by the community
FileSize
normalize.txt861 bytes

Works like a charm. Since the new system does actually support display and navigation of the aliases, it just doesn't support storage of them, I've modified the patch slightly to reflect this since I reckon it could be confusing otherwise. It's a small change, so marking RTBC.

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy commented
Status: Reviewed & tested by the community » Fixed

Thanks, committed.

JirkaRybka’s picture

JirkaRybka CreditAttribution: JirkaRybka commented
Priority: Normal » Minor
Status: Fixed » Needs review
FileSize
spacing.patch1.01 KB

Follow-up: I just spotted a double space introduced here...

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy commented
Status: Needs review » Fixed

Thanks, committed.

JirkaRybka’s picture

JirkaRybka CreditAttribution: JirkaRybka commented
Priority: Minor » Normal

Back to previous status...

sumgai’s picture

sumgai CreditAttribution: sumgai commented
Status: Fixed » Active

I don't understand...

If the alias is kept as node/x and I change the alias to point to node/y does the menu item still point to node/x or does it point to node/y, i.e., does the alias work or not?

If it points to node/y when the alias is changed, then the message that you show when assigning a menu item to an aliased path is very confusing.

If the menu item still points to node/x after the alias has been modified to point to node/y then this is still broken.

Thanks for the clarification.

Gábor Hojtsy’s picture

Gábor Hojtsy
he/him
Primary language Hungarian
Location Hungary
CreditAttribution: Gábor Hojtsy commented
Status: Active » Fixed

Please do not hijack bug reports with support requests.

sumgai’s picture

sumgai CreditAttribution: sumgai commented

I'm sorry, but I don't see my comment as a support request.

Please re-read my comment. It is a continuation of the bug discussion.

JirkaRybka’s picture

JirkaRybka CreditAttribution: JirkaRybka commented

It's not intended to work that way (i.e. menu items redirected by changing aliases), menu points to a certain page (node), regardless it's path being renamed through aliasing. Alias is just a nice make-up for SEO (i.e. hiding the ugly 'node/xxx' from public), but it's the system path that really matters to Drupal (I guess that's also needed for menu internals, since all aliased paths are in Drupal rewritten to system paths, and only then processed). But I guess that you can define the path as external (full path with http:// etc to solve your special use-case).

Otherwise, you revealed a bug (seems like just along-the-way), which got fixed here, so this issue is going to be closed. If your intention was to make it work like said in #11, that's entirely different request, and is a "won't fix" because that behavior is "by design". If anyone likes to discuss that further and change perhaps, that should go to the Drupal 7.x development, as 6.x is not accepting new features anymore (frozen for nearly half a year now). In that case, open a new issue.

sumgai’s picture

sumgai CreditAttribution: sumgai commented

This is a significant change from 4.x and 5.x and a step backward in functionality.

I think you'll find that people used the path alias as as an important navigation feature in addition to a minor SEO feature.

I will open a 7.x topic on it, but I'm disappointed in the response that "we spec'd 6.x this way, so that's it."

I would agree if this were a new feature request, but I doubt many people understood (or even knew) how the change to the menu system would impact the use of path aliases.

JirkaRybka’s picture

JirkaRybka CreditAttribution: JirkaRybka commented

Hmm, I wrote the above just from what I gathered around on Drupal.org; otherwise I never attempted to use path aliases in such a way before. Now I tested on 5.x, and it's rather bizarre - after I changed the aliasing, I got unaliased link in menu, pointing to the original page still (after re-editing the item it updated somehow), perhaps caching plays with this somehow... But still I think this is not exactly what it's designed for. If you can edit your aliases, you can surely edit your menu items (or aliased nodes) directly, too...?

Edit: I don't want to look like being some big authority, I just attempted to summarize here. Feel free [others / more knowledgable] to give more feedback, if appropriate.

catch’s picture

catch
he/him
Primary language English
CreditAttribution: catch commented

If you add a link to an aliased node in the menu, then change the alias, you'd have to delete the original alias first before putting something else there. If I add a node to a menu, and alias it, I'd expect the menu item to follow the node, not link to a broken alias (if only for a minute). So this seems entirely desirable behaviour to me.

In terms of how the links are displayed to the users, there's no change, or even an improvement since afaik if you link to a node/123 then alias it, the menu system picks up the alias for display automatically. I'm less knowledgable than JirkaRybka though ;)

sumgai’s picture

sumgai CreditAttribution: sumgai commented

I'm less knowledgeable than any of you ;-) but I know I like the ability to use aliases as variables or symbolic links everywhere in my code/pages/menus, then I only have to change one place, i.e., the alias, to get all the pointers going to the right places.

For example, suppose I have "privacy" as a link in a main menu, a footer menu and hyperlinks throughout my site and I change "privacy" from node/x to node/y. I don't have to change two menu items in addition to the alias.

Anonymous’s picture

(not verified) CreditAttribution: commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.