Spectra - Some Blocks Are Not Translatable

Waiting for author

Overview of the issue

When using Spectra with WPML, you might experience the following issue: some Spectra blocks do not appear in the Advanced Translation Editor (ATE), or their content remains untranslated on the front end even after translating.

Workaround

Go to WPML > Settings > Custom XML Configuration in your WordPress dashboard.

Add the following XML configuration and save:

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="uagb/info-box" translate="1">
      <xpath>//*[contains(@class, "uagb-ifb-title")]</xpath>
      <xpath>//p[contains(@class, "uagb-ifb-desc")]</xpath>
      <xpath>//span[contains(@class, "uagb-inline-editing")]</xpath>
      <key name="tempHeadingDesc" />
      <key name="ctaText" />
    </gutenberg-block>
    <gutenberg-block type="uagb/image-gallery" translate="1">
      <key name="mediaGallery">
        <key name="*">
          <key name="id"/>
          <key name="url" type="link" />
          <key name="alt" />
          <key name="link" type="link" />
          <key name="caption" />
        </key>
      </key>
      <key name="mediaIDs">
        <key name="*" />
      </key>
    </gutenberg-block>
    <gutenberg-block type="uagb/tabs" translate="1">
      <key name="tabHeaders" />
      <xpath>//*[contains(@class, "uagb-tab")]/a/div</xpath>
    </gutenberg-block>
    <gutenberg-block type="uagb/tabs-child" translate="1">
      <key name="header" />
      <key name="tabHeaders">
        <key name="*" />
      </key>
    </gutenberg-block>
    <gutenberg-block type="uagb/modal" translate="1">
      <xpath>//span[contains(@class, "uagb-inline-editing")]</xpath>
      <xpath type="link">//a[contains(@class, "uagb-modal-button-link")]/@href</xpath>
      <key name="buttonText"/>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

2 Responses to “Spectra - Some Blocks Are Not Translatable”

muhammet-serhatY says:

July 6, 2026 at 5:22 am

Hello,
I tested the XML from this errata page.
I found something that may help identify the issue.
On my Home page, Paragraph blocks are correctly detected by WPML and appear in the Advanced Translation Editor.
However, Heading (H2) blocks are not detected and therefore remain untranslated.
As a test, I converted one Heading block into a Paragraph block without changing its text. Immediately after doing this, the text appeared in the Advanced Translation Editor and translated correctly.
This suggests the issue is related specifically to Spectra Heading blocks rather than the translation package itself.
Could you please check whether the current XML configuration is missing support for Spectra Heading blocks?
Thank you.

Reply
- Nicolas V. says:
  
  July 7, 2026 at 2:16 pm
  
  Hello Muhammet,
  
  Converting the Heading block to a Paragraph block was a great way to narrow down the issue.
  
  I believe the XML configuration for the Spectra Heading block (uagb/advanced-heading) should already be included. It should look something like this.
  
  If you’re an advanced user, you can also use our Multilingual Tools plugin to register missing blocks yourself by following this documentation.
  
  If you’re still experiencing this issue, please open a new support ticket. We’ll be happy to investigate further and provide the correct XML configuration if needed.
  
  Reply

Overview of the issue

Workaround

2 Responses to “Spectra - Some Blocks Are Not Translatable”

Leave a Reply