Skip to content
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

Input Path To Url plugin has trouble with spaces (encoded or not) and diacritics #3583

Closed
Lamecarlate opened this issue Dec 11, 2024 · 2 comments

Comments

@Lamecarlate
Copy link

Operating system

Ubuntu Linux 24.04

Eleventy

3.0.0

Describe the bug

When a markdown link contains spaces (within <>) or encoded spaces (%20) or diacritics (example: hypothèse), InputPathToUrlTransformPlugin does not work as intended.

From a file name hypothèse.md, instead of generating "/hypothèse", for example, it outputs /hypothèse.md.

Generated files are OK, and an html link to "/hypothèse" is working. This is only about markdown links.

Reproduction steps

  1. Get the archive, extract it, npm install in it, and npx @11ty/eleventy --serve.
  2. Go to home page.
  3. Click on links (the first, "Plip", is OK, the last three are html and OK, the others aren't).
  4. See a 404 error.

eleventy-sample-inputPathToUrl-test.zip

Expected behavior

I expect the links to lead to the correctly generated html files, whether they contain spaces, %20, or diacritics.

Thanks for the hard work, I'm hoping this issue is correctly written.

Reproduction URL

No response

Screenshots

No response

@zachleat
Copy link
Member

zachleat commented Dec 11, 2024

Cross linking 11ty/eleventy-img#253 (though this is a different issue!)

The fix for this one will ship with v3.0.1-alpha.1

@Lamecarlate
Copy link
Author

(yep, it's me too on eleventy-img 😅 thanks for the answer, I look forward to v3.0.1-alpha.1)

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

No branches or pull requests

2 participants