Problem: If you're experiencing issues where the translated English URL of elements like the Kadence Advanced Button reverts to the default language URL after making edits to the German version of your page, this might be due to incorrect XML configuration for translating URLs within Gutenberg blocks. Solution: We recommend updating the Custom XML configuration for the Kadence Blocks. Here's the updated XML you should use:
<wpml-config><br /> <gutenberg-blocks><br /> <gutenberg-block type="kadence/singlebtn" translate="1"><br /> <key name="link" type="link"></key><br /> <key name="text"></key><br /> </gutenberg-block><br /> <gutenberg-block type="kadence/advancedheading" translate="1"><br /><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><br /> <xpath type="link">//a/@href</xpath><br /></gutenberg-block><br /> </gutenberg-blocks><br /></wpml-config>
Please insert this XML in WPML > Settings > Custom XML. After updating, make a minor edit to the original post and save it. Check the translation again; the internal links should now automatically translate and not appear inside the translation editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should the problem persist, please open a new support ticket.
**Problem:** The client was experiencing issues with translating Kadence forms on their website. Despite making the forms and custom fields translatable, the 'send' button was missing, and the forms were not displaying correctly in different languages. The client suspected that the blocks were not registered in WPML and was unsure how to select the correct form in the Advanced Translation Editor (ATE).
**Solution:** We addressed the issue by incorporating a custom XML configuration to ensure that the Kadence blocks are recognized and translatable by WPML. Here is the XML configuration we used:
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. We also highly recommend checking related known issues at [https://wpml.org/known-issues/](https://wpml.org/known-issues/), verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at [https://wpml.org/forums/forum/english-support/](https://wpml.org/forums/forum/english-support/).
Problem: You are developing a site and have set German as the default language. However, you encounter an error stating: 'Your default language German must be assigned to a supported language in order to use automatic translation.' You are unsure what is wrong with your settings. Solution: If you're using WPML AI for automatic translation, it's important to note that this feature currently supports translations from English to German, Spanish, French, Portuguese, and Italian. Therefore, you need to set English as the default language for your site to utilize the automatic translation feature effectively. For more details on WPML AI, please visit WPML AI - Superior Translation Engine for WordPress.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.
