- 🇨🇦Canada joseph.olstad
Thanks to @DamienMcKenna for the related project https://www.drupal.org/project/features_menu_uuid →
we can now close this issue .
Automatically closed - issue fixed for 2 weeks with no activity.
The current menu links features integration is flawed.
Menu links do not have a machine name or uuid natively, they are identified by auto-increment mlid.
The current implementation circumvents this limitation by crafting a string id from values found in the menu link, such as the link path.
This is not an ideal solution.
Fixing the 'menu_links' component itself would be difficult if we want to keep backwards compatibility.
It was proposed in
#3085880-33: Revisit UUID handling for menu links →
to introduce a new sub-module (or standalone contrib module) features_menu_uuid, which:
- would add a 'uuid' column to the 'menu_links' table via hook_schema_alter()
- add a features component 'menu_links_uuid' as an alternative to the old 'menu_links' component, which uses the uuid.
I am going to leave it to the author (DamienMcKenna) to upload files and patches here.
This new submodule would be unlike previous functionality in features:
- This would be the first submodule we add. So far, everything was done in the base module.
- This would be the first time that a part of features actually changes a database schema.
We need to determine the pros and cons of keeping this within features.
But even if it becomes a dedicated separate contrib module, we can still use this issue for initial preparation - if you want.
Fixed
2.0
Menu
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Thanks to @DamienMcKenna for the related project https://www.drupal.org/project/features_menu_uuid →
we can now close this issue .
Automatically closed - issue fixed for 2 weeks with no activity.