-
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
Create static pages based on WPML translation #6961
Comments
Due to the high volume of issues, we're closing out older ones without recent activity. Please open a new issue if you need help! |
There is a PR for adding custom routes. This includes fetching full WPML translations. Hope this get merged soon. |
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! |
I want to create pages structure based on translation on WPML.
For example, I want to create a static page
/about
for default languages and/:lang/about
for other languages.Every page has
wpml_translations
with the ID of the translated page, but how can I get these pages (by ID) and add to the nodes?I would be grateful if you could help me :)
UPDATE:
I've figured out, that
gatsby-source-wordpress
doesn't fetch translations which I need it. I think I could add option to plugin (e.g.{ translation: ['de', 'fr', ...] }
) and extend it in order to fetch translations.The text was updated successfully, but these errors were encountered: