<p>If the navigation section is strictly for structuring your navigation I would disable 'Entries in this section have their own URLs' and add a entries relation field to connect your content with the navigation items.</p>

<p>A standalone plugin could also help you out: <a href="https://github.com/am-impact/amnav" rel="nofollow">https://github.com/am-impact/amnav</a></p>

CC BY-SA 3.0
2016-03-01T14:39:58.977Z
2016-03-01T14:39:58.977Z
Maarten de Graaf
<p>I am trying to setup a navigation on a site. I am using a Structure Section called "pages", however, when I changed the "Top-Level Entries" to just <code>{slug}</code> and the nested levels to <code>{parent.uri}/{slug}</code>, I am getting URLs like <code>about/profile-1</code> and <code>about/biography-1</code>. </p>

<p>I am guessing the reason why I am getting <code>-1</code> is due to the fact that the entry already exists in my About channel. </p>

<p>Any thoughts on how to resolve this?</p>

<structure><navigation>
Navigation Slug Issue (Structure Section)
# Navigation Slug Issue (Structure Section)

(Asked by: username_0 on 2016-03-01)

I am trying to setup a navigation on a site. I am using a Structure Section called "pages", however, when I changed the "Top-Level Entries" to just `{slug}` and the nested levels to `{parent.uri}/{slug}`, I am getting URLs like `about/profile-1` and `about/biography-1`.

I am guessing the reason why I am getting `-1` is due to the fact that the entry already exists in my About channel.

Any thoughts on how to resolve this?

**Tags:** structure, navigation

---

## 1 answers

### Answer by username_1 on 2016-03-01. Score: 1

If the navigation section is strictly for structuring your navigation I would disable 'Entries in this section have their own URLs' and add a entries relation field to connect your content with the navigation items.

A standalone plugin could also help you out: <https://github.com/am-impact/amnav>


---

