Timeline for Menu item path saved as node/nid instead of alias
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2013 at 22:14 | comment | added | Mołot | I would find a way to store uuid links in menu. Write a module or hack for it if I have to. Portability is the very reason of uuid existence and there is no better approach at the moment. | |
| Jun 13, 2013 at 22:07 | comment | added | August1914 | project/uuid_Links is a different use case: does not handle menu_links. We're committed to using node_export, not features, for content export. Workaround so far: exporting the affected menu with features (not content), then editing the feature, replacing the nids with aliases. Still, the menu_link parent is not respected when the feature is enabled, so we're having to specifically lookup and set the parent (menu_link_save) after the menu feature is enabled, despite setting plid. In our case, our menu can be expected to be stable, can survive kludging, but wondering, what would you do? | |
| Jun 13, 2013 at 21:58 | comment | added | August1914 | project/uuid_Links covers a different use case, does not handle with menu_links. We're pretty well committed to content export with node_export, not features. | |
| Jun 13, 2013 at 7:25 | history | answered | Mołot | CC BY-SA 3.0 |