Hello,

In the path field of the menu item addition form, if one does enter "<firstchild> " (i.e. the "<firstchild>" tag followed by any number of white spaces), then the path is considered as valid. Then, the link will point to something looking like http://www.example.com/<firstchild>%20.

We should not be able to enter an invalid path.

Best,
Julien

Comments

anrikun’s picture

anrikun commented
Issue summary: View changes

Converted < and > to < and >

anrikun’s picture

anrikun commented

Thanks for reporting.
I guess this is a bug in Core.
Menu Firstchild should not have to perform such a validation itself.
I'll have a look at this.

jlnknz’s picture

jlnknz commented

I thought this first, but if you try to enter for example "node/32 ", Drupal does complain about the trailing space, saying it's not a valid path.

However, I had a quick look to menu_firstchild sources and indeed cannot find a place where there may be a problem regarding this.

Best,
Julien

jlnknz’s picture

jlnknz commented
Issue summary: View changes

Corrected into

anrikun’s picture

anrikun commented
Issue summary: View changes
Status: Active » Closed (outdated)