Skip to content

Giving relative urls for prev/next yields unexpected results #623

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Uriziel01 opened this issue Jun 29, 2018 · 2 comments
Closed

Giving relative urls for prev/next yields unexpected results #623

Uriziel01 opened this issue Jun 29, 2018 · 2 comments

Comments

@Uriziel01
Copy link

Bug report

When plain relative (omitting dot dash notation) urls are given inside of frontmatter prev/next blocks the resulting links are targeting some random pages not the pages user expects

Version

v10.2

Steps to reproduce

Crete page with frontmatter prev/next values like (Im using json syntax):

"prev": "author-info-box",
"next": "breadcrumb"

What is expected?

Resulting prev/next links should point to 'mydomain.com/shortcodes/author-info-box' and 'mydomain.com/shortcodes/breadcrumb' pages.

What is actually happening?

Resulting prev link is some random page ("mydomain.com/shortcodes/author" in my case) and next points to the exact page Im currently on now (which is quite nonsense on its own and certainly not correct).

Modifying the values to:

"prev": "./author-info-box",
"next": "./breadcrumb"

fixes everything and generates correct links and points to mydomain.com/shortcodes/author-info-box and mydomain.com/shortcodes/breadcrumb

@ulivz ulivz added type: enhancement Request to enhance an existing feature and removed type: enhancement Request to enhance an existing feature labels Jul 3, 2018
@ulivz
Copy link
Member

ulivz commented Jul 3, 2018

My file structure:

├── README.md
├── assets.md
└── deploy.md

and I just tested:

---json
{
  "prev": "./deploy",
  "next": "deploy"
}
---

Both of them get the correct links for me.

So if it truly turns out to be a bug, please provide a reproduction link.

@ulivz
Copy link
Member

ulivz commented Aug 20, 2018

We're closing this issue as stale as it's more than 20 days without activity, and without an associated Pull Request. Please feel free to continue discussion. We'll reopen this issue if anything actionable is posted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants