[BUG](v5) When creating a Wrapper with nested items it is not possible to add, remove, or reorder

[liqueflies]

Hello,

I tried last v5 version. After adding an item (type wrapper) I added sub items and saved menu. When i need to add sub items, or reorder / delete is not possible until I delete the parent element and recreate the whole tree.

Here is the video:

https://github.com/user-attachments/assets/e2ee4769-aad8-4f19-81ef-bd6d144b5931

[mateusz-kleszcz]

Hi @liqueflies, it looks like the issue is caused by the fact that some of your nested navigation items share the same url. The server requires each item's path to be unique, and when duplicate URLs are detected, it throws a validation error. Please ensure that each url is unique among nested items and try again. Let us know if you're still encountering issues afterward.

[liqueflies]

Hello @mateusz-kleszcz

Yes, after upgrading each url (that i feel is not "right" because i resolve internally to my application based on pagetype and eventually any variables) they made a triple entry of my last item.

Then i cannot save again...

[mateusz-kleszcz]

@liqueflies could you please share URLs you upgraded and the server logs that appear right after you try to save your navigation?

I’ve tried to reproduce the issue on my end, but haven’t been able to do it so far.

[CodeVoyager]

@liqueflies Recently newest version of plugin was released. It deals with saving issues. Have a look, please.

[brianjd]

I'm encountering this issue on 3.0.13

[mateusz-kleszcz]

Hi @liqueflies, @brianjd,

Could you please try the latest version of the plugin (v3.2.0) and check if you're still experiencing any issues with saving navigation items? If the problem persists, could you share the steps to reproduce it and any relevant error logs so we can investigate further? Thanks!

[mateusz-kleszcz]

Since there has been no recent feedback on this issue, we will close it as stale for now. If anyone still encounters this problem, please feel free to reopen the issue or open a new one.

[liqueflies]

Hello @mateusz-kleszcz, sorry I lost the conversation. I confirm that now the only error i get (I suppose is wanted) is that you need to have different path for each subItem. To me it's not a good pattern (for example if you do not compile "path" and let the front-end resolve the routing with the "type"), but let me know what do you think!