Why does the link to the next page always route to the root index page? #408
-
|
On all my docs pages, the button for navigating to the next page at the bottom always routes to the uppermost root/landing page of my docs. What could be causing this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
Could you provide more info to debug? |
Beta Was this translation helpful? Give feedback.
-
|
Sure, sorry. I have the following page tree: {
"name": "Introduction",
"children": [
{
"type": "page",
"name": "Introduction",
"url": "/docs"
},
{
"type": "page",
"name": "API",
"url": "/docs/api-docs"
},
{
"type": "page",
"name": "Lines",
"url": "/docs/lines"
},
{
"type": "folder",
"name": "PLCs",
"index": {
"type": "page",
"name": "PLCs",
"url": "/docs/plcs"
},
"children": [
{
"type": "page",
"name": "Edit",
"url": "/docs/plcs/edit"
},
{
"type": "page",
"name": "Export",
"url": "/docs/plcs/export"
},
{
"type": "page",
"name": "Import",
"url": "/docs/plcs/import"
},
{
"type": "page",
"name": "Navigation",
"url": "/docs/plcs/navigation"
}
]
},
{
"type": "page",
"name": "Standard Workflow",
"url": "/docs/standard-workflow"
},
{
"type": "page",
"name": "Terminology",
"url": "/docs/terminology"
}
]
}On all of the pages at the bottom, the "next page" link always links back to the top-most "Introduction" page, regardless of which page I am on. I would expect instead that it would go to the next page in the list. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
The page tree looks fine, probably you have some problems in your code. Please provide a minimal reproducible example. |
Beta Was this translation helpful? Give feedback.
-
|
I figured it out. I've had to deal with a slew of issues getting it to work properly in my existing Next.js project. It had to do with the localization locale prefix throwing off the urls during search. |
Beta Was this translation helpful? Give feedback.
I figured it out. I've had to deal with a slew of issues getting it to work properly in my existing Next.js project. It had to do with the localization locale prefix throwing off the urls during search.