Add option to not append parent URL to child URL

[TithSambath]

Hello,

Is there anyway we can exclude parent URL from child URL?

[mateusz-kleszcz]

Hi @TithSambath, at the moment, we don’t have an option to hide the menu item path. Could you share the reason you’d like to hide it?
The path is intentionally shown because it’s important context - it helps differentiate similar items, and long values are already trimmed in the UI. Because adding a dedicated setting would introduce extra maintenance, we’d only implement it if there’s a strong use case for it.

[TithSambath]

Hi @mateusz-kleszcz,

Sometime child routes do not include any parent route. The user can move Navigation around without think about path (as path or slug can be define inside Collections)

The navigation UI on frontend just want to group thing to make it clear to navigation but sometimes all page paths are just flag path with no group.

We can have a new option to not append any parent to child URL and just use the URL field only when response in API.

Example:

# Currently all child URL inherit parent URL (no option to exclude parent URL)

├── Group A (/group-a)
│ ├── Sub Group B (/group-a/sub-a)
│ ├── Sub Group A (/group-a/sub-b)
│ ├── Other Subs (/group-a/other-sub)
│
├── Resource (/resource) 
│ ├── Docs (/resource/docs)
│ ├── About (/resource/about)
│ ├── Contact (/resource/contact)
│ ├── Support (/resource/support)

# What we want in API is just URL field without append any parent URL.

├── Group A (/group-a)
│ ├── Sub Group B (/group-a/sub-a)
│ ├── Sub Group A (/group-a/sub-b)
│ ├── Other Subs (/other-sub)
│
├── Resource (/resource) 
│ ├── Docs (/docs)
│ ├── About (/about)
│ ├── Contact (/contact)
│ ├── Support (/support)

[TithSambath]

@mateusz-kleszcz, sorry we have update the issue description. please review again.

[mateusz-kleszcz]

Thanks for the detailed explanation - I understand what you’re trying to achieve now.

What you’re asking for is not only hiding the path in the admin UI, but changing how the plugin generates URLs in the API (i.e., stopping child items from inheriting/being prefixed by the parent path). That would be a pretty big change, and in many existing setups, it would be a breaking change because people rely on the current parent.

In general, the wrapper elements are meant to represent the URL hierarchy. If you want grouping purely for UI/organization without affecting URLs, we could consider adding a non-breaking feature in the future, like a “category” field (or similar) for grouping, or an optional per-item setting for absolute paths - but it would need to be designed carefully and introduced in a backward-compatible way.

[luxor37]

I also would like to see this feature for the same reason!

To make it non-breaking could you not simply add an additional field that is the isolated slug and isolated path (exclude parent)? This way we can make more custom routing configuration when rendering.

I like the ui navigation to organize the items visually for my non-coder colleagues but the routing logic in my case is just /[pageSlug] and they are all unique so having the parent appended to the slug is a hindrance here.