-
Notifications
You must be signed in to change notification settings - Fork 1
Description
there is already an "nav fieldtype" but it can only select a nav... not a nav item.
Why doing that ?
Because ... it could be useful for building complexe breadcrumbs where there is no correlation between the entry url and the displayed breadcrumb.
A use case : imagine a "tips" collection where for seo reasons, all entry slugs are just behind the /tips/ url
ie :
/tips/cooking-tip
/tips/whatever
/tips/how-to-cook-with-children
But on some entry (ie : how-to-cook-with-children) I want to be able to replicate a hierarchy which does not exist in the url.
breadcrumb like :
tips > cooking-tip > how-to-cook-with-children
If I could map an entry to a nav Item, I could rebuild a dedicated nav for breacrumbs and be totally free of the url structure.
What do you think ?