This is the same site as we've been working on in recent tickets, which uses a FSE homepage with gutenberg static blocks and custom dynamic blocks.
All the content is translating fine, our problem is that when we create a link in (for example) the homepage footer to an existing page, that link isn't translated when viewing the homepage in a different language. So if I switch to Spanish the link still links to the english version of the post.
I can see the url in the advanced translation view if I filter by https or something. I can translate it explicitly. But it seems like WPML should be able to translate links to posts it has itself created. Are we doing something wrong?
I've tried using the Translate Link Targets button in settings and the translate_link_target attribute in wpml-config and modifying and re-translating the footer, but WPML still seems to want me to manually translate the links.
What's the correct workflow for creating links in a gutenberg block and having WPML translate them?
Thank you for contacting WPML support, I'd be happy to help you with this issue.
WPML can adjust the internal URL automatically on the translation page if the post/page is already translated. When registering the custom XML configuration code for the link field of a block, you can tell WPML that it is a link type. For example:
Those settings seem to work when we're referencing hrefs in core blocks, but WPML doesn't seem to want to translate hrefs in custom blocks. So we've got the following wpml-config (image 1).
This works on our core paragraphs in the footer, because the url I've linked to doesn't show up in the translation manager at all and shows up correctly on the rendered page (image 2, image 3).
With our custom blocks, though, the url *does* show up in the translation manager, which makes me think it's not being picked up as a link that can be translated (image 4). The destination URL does definitely have a translation (image 5).
This is the core problem. Our custom block text fields show up for manual translation fine when defined in the wp-config, but the links are not automatically translated.
I'm not sure what the difference could be in how WPML is handling the core paragraph block (markup in image 6) and the custom block (markup in image 7). Maybe it treats the key element different than the xpath element or doesn't like that these values are in attributes?
Can you please replicate the issue on a clean installation of WordPress? You can access the admin area with this link hidden link
Kindly follow the steps below:
- Don’t restore your site there.
- Install the block plugin.
- Try to replicate the issue with minimal steps.
- Then let me know the steps to replicate it.
OK, I've uploaded our theme, which contains all the blocks. The site exhibits the same behavior: core paragraph blocks in Footer display no links in the advanced translation editor, I assume because they have been automatically translated. (image a, image b).
Custom blocks like front-page-carousel in Front Page display links in the advanced translation editor, so it appears they have not been automatically translated (image c, image d, image e).
I see the custom block and URL in the ATE for translation. I'm asking our 2nd tier support about this case and I will update you here when I have something to share.
I got some information from our 2nd tier support: This is a limitation. We can't adjust the URL inside the block attribute automatically.
There are two options:
- Translate URL manually in Advanced Translation Editor.
- Translate URL in front-end when they render. For this, please share the code that you are using to render the block and we can suggest the changes to translate the link.
Look forward to your reply.
Thanks
The topic ‘[Closed] Can WPML automatically translate URLs?’ is closed to new replies.
