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

fix(gatsby-source-wordpress): WordPress does not properly encode its media urls #15593 #15835

Merged
merged 1 commit into from
Jul 22, 2019

Conversation

TitanNano
Copy link
Contributor

Description

If WordPress media URLs contain non-ASCII characters, then they will not get properly encoded by WordPress. This makes them invalid URLs, and they get ignored by gatsby-source-filesystem. This causes the media files to not exist locally.

Related Issues

Fixes #15593

If wordpress media URLs contain non-ASCII characters, then they will not
get properly encoded by wordpress. This makes them invalid URLs and they
get ignored by `gatsby-source-filesystem`. This causes the media files
to not exist locally.
@wardpeet
Copy link
Contributor

wardpeet commented Jul 19, 2019

This is awesome! 👏 Thank you for doing this.

could you provide an example project/api so we can have a proper test run?

@gu-stav
Copy link
Contributor

gu-stav commented Jul 22, 2019

This would probably also fix #12684. 🙌🏼

Copy link
Contributor

@pieh pieh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified locally with some image containing non-ASCII characters. Thanks @TitanNano!

@pieh pieh merged commit f4af142 into gatsbyjs:master Jul 22, 2019
@gatsbot
Copy link

gatsbot bot commented Jul 22, 2019

Holy buckets, @TitanNano — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

  1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. We’ve got Gatsby t-shirts, stickers, hats, scrunchies, and much more. (You can also unlock even more free swag with 5 contributions — wink wink nudge nudge.) See gatsby.dev/swag for details.
  2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!

@TitanNano TitanNano deleted the topics/escape-wordpress-media-urls branch July 23, 2019 07:46
johno pushed a commit to johno/gatsby that referenced this pull request Jul 29, 2019
…byjs#15835)

If wordpress media URLs contain non-ASCII characters, then they will not
get properly encoded by wordpress. This makes them invalid URLs and they
get ignored by `gatsby-source-filesystem`. This causes the media files
to not exist locally.
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

Successfully merging this pull request may close these issues.

[gatsby-source-wordpress] media files with non-ASCII characters in their names are not downloaded
4 participants