## Problem Import and Settings menu items generated by the ModelerApiMenuLink deriver are appearing orphaned in the Drupal admin menu without proper parent nesting. The items should appear as children of their collection menu items, but instead appear at the root level of the menu tree and cannot be managed through Drupal's menu UI. ## Root Cause The import and settings derivatives reference their collection parent using only the derivative ID suffix (e.g., `entity.my_type.collection`), but the menu link plugin system requires the full plugin ID format (e.g., `modeler_api:entity.my_type.collection`). This mismatch causes the menu system to fail to resolve the parent relationship. ## Solution - Store the base plugin ID from the menu link definition in the deriver class - Construct the full plugin ID by combining the base plugin ID with the derivative ID suffix - Use the full plugin ID when setting parent references for child derivatives ## Changes Made - Added `$basePluginId` property to `ModelerApiMenuLink` class - Modified `create()` method to capture and store the base plugin ID from plugin discovery - Updated parent references in import and settings derivatives to use the full plugin ID format ## Files Modified - `src/Plugin/Derivative/ModelerApiMenuLink.php` ## Testing Clear the Drupal cache and verify in the admin menu structure that: - Collection menu items appear under their configured parent (typically "Workflow" or similar) - Import and Settings items appear as children under their respective collection - The menu tree hierarchy is correct and items cannot be orphaned ## Related This fix ensures menu derivatives properly integrate with Drupal's menu link plugin system and follow the expected parent-child relationships in the admin menu tree.