Navigation Menu Troubleshooting

This article consolidates the most common issues administrators encounter with Navigation Menu. Each entry follows the same format: symptom, cause, resolution. Issues specific to a single area are also documented on the corresponding configuration page.

App Management

• Symptom: Clone App fails or hangs.
  Cause: Source App has unusually large or deeply nested menus, or transient server load.
  Resolution: Reload and retry. If the problem persists, simplify the source App temporarily by trimming very large branches before cloning.
• Symptom: Default Menu Item dropdown is empty.
  Cause: The App has no non-folder Menu Items.
  Resolution: Add at least one Entity, Active Page, Link, or Web item, then set it as the default.
• Symptom: Delete action is hidden on an App.
  Cause: The App is system-provided and not deletable.
  Resolution: Clone the App to create a custom version you can modify or delete.
• Symptom: A folder named "More" appears in an App that you did not create.
  Cause: The App was migrated from the pre-v2025.8.0 navigation model. As a one-time upgrade step, items that previously sat behind an overflow indicator were grouped under a folder named More. After the upgrade, it is a regular folder.
  Resolution: Treat the More folder as any other folder. Move items out of it, rename it, or delete it once empty.

Menu Items

• Symptom: Name field rejects input beyond a certain length.
  Cause: The Name (Label) field is limited to 50 characters.
  Resolution: Shorten the Name; use Tooltip or Description for additional context.
• Symptom: Web Menu Item displays a blank iframe.
  Cause: The target site refuses framing (X-Frame-Options or Content Security Policy), or the URL is not HTTPS.
  Resolution: Use HTTPS only. Use a Link Menu Item with Open in New Window if the target refuses to be framed.
• Symptom: Item disappears after dragging.
  Cause: The drop target was not valid.
  Resolution: Reload (changes are not saved until you click Save), then drop on a Folder or top-level position.
• Symptom: Cannot delete a Menu Item.
  Cause: The item is a Feature (Standard) Menu Item.
  Resolution: Feature items cannot be deleted from the menu. Adjust the role's feature permission to hide them.
• Symptom: Active Page item shows Not Found for some users.
  Cause: The Active Page's sharing list does not include the user's role or group, or the page is unpublished.
  Resolution: Open the Active Page's sharing settings and add the appropriate role or group; publish the page if it is in draft.

Sharing

• Symptom: Share action is missing on a Menu Item.
  Cause: Sharing only applies to Web and Link items.
  Resolution: For Entity, Active Page, or Feature items, configure permissions on the underlying object instead.
• Symptom: A user is in a shared role or group but does not see the item.
  Cause: The App that contains the item is not accessible to the user's role.
  Resolution: Confirm App access first; sharing only narrows visibility further.
• Symptom: Saving sharing fails with an error.
  Cause: A previously listed role or group has been deleted from the system.
  Resolution: Reload the drawer, remove stale chips, and save again.

Visibility and Security

• Symptom: A user does not see a Menu Item you expected them to see.
  Cause: One of the security layers is denying access.
  Resolution: Walk the layers - App access, Menu Item type-specific check, per-item sharing - and find the layer that denies.
• Symptom: A user sees an item you wanted to hide.
  Cause: Per-item sharing only narrows visibility; broader permissions still apply.
  Resolution: Remove the user's role from the item's sharing list, remove them from the shared group, or restrict access at the underlying entity, Active Page, or feature level.
• Symptom: A folder appears empty for a user.
  Cause: All children evaluate to hidden for that user.
  Resolution: Grant access to one of the children, or restructure so the folder is not empty for that audience.
• Symptom: Active Page group sharing does not produce expected visibility.
  Cause: The user's session predates the change, or App access is missing.
  Resolution: Confirm App access; have the user log out and back in.

Migration from Pre-v2025.8.0 Apps

• Symptom: A folder named "More" appears in an upgraded App that you did not create.
  Cause: The upgrade grouped pre-v2025.8.0 overflow items under an auto-created folder during the one-time migration to the new hierarchical model. After the upgrade, it is a regular folder.
  Resolution: Reorganize as desired: drag items out of the More folder, rename it, or delete it once empty.
• Symptom: Old per-item visibility settings appear missing.
  Cause: Visibility settings have been migrated into the new role and group sharing model and now live on the Share drawer.
  Resolution: Open the Share drawer on the affected item and confirm the migrated entries.

When to Contact Magentrix Support

Open a support case with the following information when the issue is not resolved by the steps above:

• Portal URL.
• The exact symptom and the steps that reproduce it.
• The App and Menu Item names involved.
• The user's role name and group memberships.
• Whether the issue began after a specific change, an App clone, or a Magentrix release.

<< Navigation Menu and Security Integration