When a child menu item has the same name as its parent, the generated system path is wrong. Possibly only when the parent is a taxonomy path, as that's the only case I've tested.

To regenerate:

  • Make a menu import file similar to attached menu-import-bug-demo.txt.
  • Settings as in menu-import-settings.PNG, which I don't think matters, anyway.
  • In the preview (menu-import-preview.PNG) the menu structure is kept, but parent items with identically named children, yellow rows, get the wrong system path. Different naming, green rows, results in expected system path.
  • When the menu is imported (menu-import-resulting-menu.PNG) even the structure is messed up, probably because the system doesn't like a taxonomy path pointing to a node.

Core 7.10, module- and theme versions in version-info.txt.

Apart from that, thanks for a great module I couldn't do without!

CommentFileSizeAuthor
#2 menu-import-bug-demo_0.txt218 byteslex0r
#2 Selection_002.png32.42 KBlex0r
#2 Selection_003.png34.76 KBlex0r
version-info.txt872 bytesArvid Herfjord
menu-import-resulting-menu.PNG27.12 KBArvid Herfjord
menu-import-preview.PNG36.94 KBArvid Herfjord
menu-import-settings.PNG18.37 KBArvid Herfjord
menu-import-bug-demo.txt764 bytesArvid Herfjord

Comments

lex0r’s picture

lex0r commented
Assigned: Unassigned » lex0r

Thanks for the report, will fix asap...

lex0r’s picture

lex0r commented
Status: Active » Postponed (maintainer needs more info)
StatusFileSize
new Selection_003.png34.76 KB
new Selection_002.png32.42 KB
new menu-import-bug-demo_0.txt218 bytes

I tried to reproduce the issue and here are the results:

  • I created terms and nodes for experiment, and a relevant text file (menu-import-bug-demo_0.txt)
  • I used the same import options as you did (Selection_002.png)
  • I got no errors (Selection_003.png)

It looks like I need a full DB dump to be able to catch the issue. I inspected the code again, but found no problems like uninitialized variables, that could lead to wrong links.

Arvid Herfjord’s picture

Arvid Herfjord commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

OK, before making a DB dump, I thought I better make sure I still have the issue. But I don't! It's gone, evaporated!

Since last time, there's been updates and changes on my site, not to mention Xmas and a new year. And new URL-aliases for my stuff.

One funny thing when I tried the original import file (#1, menu-import-bug-demo.txt) was that some of the old path aliases still were mapped to the right node in the import, even though the aliases no longer existed in the url_alias table.

And when I now try to use a path alias in the import, like /en/product-group/about-changing-tables, it only maps to <front>. node/[node-no] works perfect, so no problem.

I guess this means case closed and a Happy New Year!