[Resolved] WPML Translated URLs Not Reflecting on Front End for Secondary Language Pages

Hello,

Thank you for reaching out!

Every Custom Gutenberg Block needs a proper XML configuration to be translatable with the WPML Translation Editor.

Authors of plugins can provide such configs inside the wpml-config.xml file.

Guide:
https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/

You can also create a config yourself and save it in WPML > Settings on the tab "Custom XML Configuration".

The following plugin can assist you in creating such configs:
https://wpml.org/documentation/support/multilingual-tools/

If you need further assistance, I can offer a WPML test site on which we can try to replicate the issue using the same plugins and then work towards a solution.

It would be very important to know which blocks are affected and which plugins are responsible for those blocks.

Best regards
Andreas

Is the responsible plugin the following one?
https://wordpress.org/plugins/greenshift-animation-and-page-builder-blocks/

Which are the blocks are having issues regarding link translation?

Please provide exact details, and I will try to replicate the issue on a test site.
This way we can confirm if this is a general issue and work towards a solution.

Thank you very much for the video!

Each Custom Block needs a proper XML configuration to become translatable with the Advanced Translation Editor.

The Greenshift plugin already includes a config:

<gutenberg-block type="greenshift-blocks/element" translate="1" label="Elements">
  <xpath>//*[text()]/text()</xpath>
    <key name="textContent" />
    <key name="tooltipText" />
    <key name="alt" />
    <key name="href" />
    <key name="title" />
    <key name="textAnimated">
      <key name="*" />
    </key>
</gutenberg-block>

The problem with this config is that it is not capturing links.

Please save this config at WPML > Settings on the tab "Custom XML Configuration":

<wpml-config>
    <gutenberg-blocks>
      <gutenberg-block type="greenshift-blocks/element" translate="1" label="Elements">
        <xpath>//*[text()]/text()</xpath>
        <xpath>//a</xpath>
        <xpath type="link">//a/@href</xpath>
        <key name="textContent" />
        <key name="tooltipText" />
        <key name="alt" />
        <key name="href" />
        <key name="title" />
        <key name="textAnimated">
          <key name="*" />
        </key>
     </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

After that, edit the block on the original content, save the page and then update the translation.

Note that this will make the link available on the Advanced Translation Editor, but you will not need to translate it. You can use the same URL in both languages, and WPML will adjust internal links automatically.

I am further escalating this issue to our compatilbity team, so that they can reach out to Greenshift on this matter.

Hello,

Thank you for the video.

I noticed that in your example you are only entering the relative URL. Could you please try adding the full URL instead, for example:

hidden link

After that, save the page, open the translation again, complete it to 100%, and save the translation.

Please let me know if the full URL is then translated correctly on the translated page.

Best regards,
Dražen

Hello,

Since you mentioned that no updates are appearing on the frontend, could you please temporarily disable any caching and security plugins you may have installed?

After that, make a small change to the title of the page in the default language, save it, and then try updating the translation again.

Please let me know if that helps.

Best regards,
Dražen

Hello,

Thank you for the update.

This appears to be a different issue from the one my colleague was previously investigating. In the original case, the XML configuration should have helped, but from what you've described, this seems to be a new problem where changes are not being saved or reflected at all.

To keep things organized and avoid mixing separate issues, I have opened a new ticket for this matter. Let's continue the investigation there:

- https://wpml.org/forums/topic/split-updated-translation-is-still-not-reflected-on-the-frontend/

Best regards,
Dražen