Problem:
The client was unable to change the 'read more' and search placeholder texts in the Dutch language using the Kadence Builder, despite the strings being translated in WPML's String Translation section.
Solution:
We discovered that the issue was related to how Kadence Builder's custom fields were registered with WPML. To resolve this, our team created a custom XML configuration to ensure these fields are recognized and translatable by WPML. Here are the steps we followed:
1. We examined the content inside the database of the main query post type to understand how the blocks were structured.
2. We created a custom XML configuration and added it to WPML > Settings > XML config tab. The XML code used was:
<wpml-config>
<gutenberg-blocks>
<gutenberg-block type="kadence/query-filter-search" translate="1">
<key name="placeholder"></key>
<key name="label"></key>
</gutenberg-block>
<gutenberg-block type="kadence/query-filter" translate="1">
<key name="placeholder"></key>
<key name="label"></key>
</gutenberg-block>
<gutenberg-block type="kadence/query-filter-reset" translate="1">
<key name="text"></key>
</gutenberg-block>
<gutenberg-block type="kadence/query" translate="1">
<key type="post-ids" name="id"></key>
</gutenberg-block>
</gutenberg-blocks>
</wpml-config>
3. After saving the XML configuration, we made a small edit and saved the default language edit page, then updated the translated version with the correct placeholder text.
This solution allowed the 'read more' and search placeholder texts to display correctly in both languages on their respective pages.
If this solution does not apply to your case, or if it seems outdated, we highly recommend 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. If issues persist, please open a new support ticket at WPML support forum.
