Nested Sub menu items

A request in three parts,
one: please consider allowing nested sub items in menu’s
two: allow us to create a Top Level menu item that leads nowhere just to be able to add content as a sub menue (not a huge deal, can always create landing pages)

The third part is a bit of a bug report

🐞 Bug: Nested menus lose functionality and cannot be reordered

Summary
When you drag an existing nested menu into another existing nested menu (i.e., you merge one dropdown under another), the submenu items stop rendering in the interface. They also become impossible to move back out, there’s no way to promote them back to root or top-level position.

Steps to reproduce

1. Create at least two nested (dropdown) menu items (let's call them Dropdown A and Dropdown B), each containing one or more submenu items. In my case I tried to move “venues” to underneath library.

2. Use the drag-and-drop interface to move Dropdown A under Dropdown B—thus making A a child of B.

3. Observe that the submenu items originally under Dropdown A no longer display at all (even when you expand B).

4. Attempt to move those submenu items back to root or top level — there is no drag-handle or option to re-position them upward.

Actual behavior

• Submenu items are no longer visible after the move.

• They cannot be dragged or promoted out of their new parent container.

• No UI handles or hierarchy controls appear to let you restore them to top level.

Expected behavior

• Submenu items remain visible and movable after nesting.

• You should be able to drag any menu item (including nested submenu) freely at any hierarchy level, both downward and upward.

• The interface should preserve visibility and allow restructuring of the menu tree.

Impact

• Users lose visibility of menu items accidentally demoted under another menu.

• It becomes impossible to reorganize menus without re-creating items manually.

• Risk of lost menu entries in published events or navigation. In our case all venues.