- Issue created by @ressa
- 🇷🇴Romania bbu23
Agree about looking into Views, because I don't remember/know if they are MenuLinkContent, but Taxonomy Menu will never happen because they don't use MenuLinkContent, they have their own entity and it's generated/updated when taxonomies are added/updated. It's impossible to do that, and my module (as stated in the description) only handled MenuLinkContent.
The only thing that could involve the Taxonomy Menu is if the taxonomy menu tree is below a MenuLinkContent, which is a case that I am having, but not sure yet if this can be handled. We'll see. Thanks for updating the issues.
- 🇩🇰Denmark ressa Copenhagen
Thanks for clarifying, I'll remove Taxonomy from the issue.
- Status changed to Closed: won't fix
7 months ago 5:52pm 29 April 2024 - 🇷🇴Romania bbu23
After investigating, the Views menu links are not MenuLinkContent, they are ViewsMenuLink plugins, similar to taxonomy menus, therefore this is out of scope as this module strictly covers MenuLinkContent entities. As discussed previously, people are advised to manually create the menu items instead of going through views if they wish to have them included in the export/import hierarchy.
- 🇩🇰Denmark ressa Copenhagen
Thanks for investigating this @bbu23. Not defining menus in Views is a totally acceptable workaround, in order to have a great, well functioning menu export-import tool.