Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -
- 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 20:00 – 23:00 -

Supporter timezone: Asia/Singapore (GMT+08:00)

This topic contains 7 replies, has 0 voices.

Last updated by Kor 6 months, 1 week ago.

Assisted by: Kor.

Author Posts
October 29, 2025 at 3:18 pm #17530120

Sietse

Background of the issue:
I am trying to translate the label inside the Adv Header block of Kadence. Your support had a solution for this with the use of 'Adv Heading' XML, but that overwrites the entire Row Layout/Column structure and does not translate anything else for the Adv Heading. I need a more robust method for this. The issue can be seen at: hidden link

Symptoms:
The Menu label should be 'Menü' but it is not properly working. Instead, I see the English word 'Menu'.

Questions:
How can I translate the menu label inside the Kadence Adv Header block without overwriting the entire Row Layout/Column structure?

October 30, 2025 at 1:02 am #17530994

Kor

Thanks for contacting us. Sorry to hear that the solution I provided earlier did not help. I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.

Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.

Your upcoming reply will be treated with confidentiality and will only be visible to you and me.

✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.

October 31, 2025 at 9:26 am #17535252

Kor

Thanks for your reply. I've checked and I can see that you've removed the custom XML configuration below that I've applied earlier.

<gutenberg-block type="kadence/advancedheading" translate="1">
      <xpath>//span</xpath>
    </gutenberg-block>

May I know why and this custom XML configuration is affecting the header template translation?

November 3, 2025 at 11:24 am #17540679

Sietse

Hi Kor,

This conflicted with the Row Layout and Column Adv Headings as it is now only set to translate a // span inside the Adv Heading, which is also happening inside the Row Layout on other pages. So perhaps we need to specify this block that it's the Adv Heading inside a Header block?

Kind regards,
Joost

November 3, 2025 at 4:33 pm #17542670

Sietse

I read through some other articles and found this:
<gutenberg-block type="kadence/advancedheading" translate="1">
<xpath>//*[self::h1 or self::h2 or self::h3 or self::h4 or self::h5 or self::h6 or self::p or self::div or self::span.wp-block-kadence-advancedheading]</xpath>
<xpath type="link">//a/@href</xpath>
</gutenberg-block>

https://wpml.org/errata/kadence-block-advanced-button-internal-link-translation-not-applied-automatically/

Right now we set the Adv Heading block to only translate //span, but there are other blocks that use it as a H1 or a H2, or even a P. Could this be the solution?

November 4, 2025 at 11:49 am #17545259

Kor

Thanks for getting back to me. I’ll need to see a clear example where the custom XML configuration is affecting the Row Layout and Column Advanced Headings. Could you please clone the site to a staging environment and try to reproduce the issue there? Once replicated, I can review it and adjust the custom XML configuration accordingly.

November 4, 2025 at 12:37 pm #17545478

Sietse

Hi Kor! I am not able to replicate the issue on a staging environment without a whitelist (as per our server configuration). Are you able to make a clone?

It seems like this xml markup could do the trick:
<gutenberg-block type="kadence/advancedheading" translate="1">
<xpath>//*[self::h1 or self::h2 or self::h3 or self::h4 or self::h5 or self::h6 or self::p or self::div or self::span.wp-block-kadence-advancedheading]</xpath>
<xpath type="link">//a/@href</xpath>
</gutenberg-block>

With span, you are actually saying that only the //span for each Adv Heading block can be translated. Since there are other Adv Heading blocks used throughout the website, this is logical behavior and I think using the above solution (which is in your documentation) could work, what do you think?

November 5, 2025 at 12:46 am #17547976

Kor

Thanks for your reply. I've checked your custom XML configuration and it is used to fix the Internal Link Translation. You can refer to this section of the documentation https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/ .

The one that I've provided should be correct. Could you share a screen recording showing me what breaks when you use the custom XML configuration that I've provided?

The topic ‘[Closed] Menu label inside Kadence Adv Header block does not translate (but get’s picked up in ATE)’ is closed to new replies.