-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
[gatsby-source-wordpress] multilingual support (WPML) #1648
Comments
An easy fix would be to have one Gatsby site per language with a root url of |
Reopening this for now. We have a PR running that enables custom route with query params to fetch translated WPML posts. |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
Hello again. Using WPML only the default language is fetched with:
http://website.com/wp-json/wp/v2/posts
it is possible to get posts in another language like so:
http://website.com/de/wp-json/wp/v2/posts
Setting the baseUrl like
website.com/de
will fetch the German posts.The goal would be to serve EN posts at
http://website.com/post/name-of-post
and DE posts athttp://website.com/de/post/name-of-post
How would this best be approached??
The text was updated successfully, but these errors were encountered: