Problem:
The client is experiencing unusually long delays in automatic translations using the WPML plugin on a custom theme site. They are concerned about whether their theme's development is compatible with WPML.
Solution:
We recommend the following steps to diagnose and potentially resolve the issue:
1) Ensure a full site backup is taken.
2) Temporarily switch to the default Twenty Twenty-Five theme.
3) Attempt to translate a page using the Advanced Translation Editor and check for completion.
4) If the translation completes successfully with the default theme, it indicates that the issue may be related to the custom theme.
For the custom theme to work properly with WPML:
1) Ensure custom blocks are registered using
.
2) Add a
file to the theme folder to specify which block attributes should be translatable. Example:
<wpml-config>
<gutenberg-blocks>
<block type="yourtheme/hero-block">
<translate>attributes/title</translate>
<translate>attributes/text</translate>
</block>
</gutenberg-blocks>
</wpml-config>
3) Translate template parts or patterns from WPML → Translation Management.
4) Use translation functions in theme files and ensure the theme's text domain is loaded.
5) Set pages and custom post types to 'Translatable' in WPML → Settings → Post Types Translation.
For further guidance, consult the following documentation:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, we highly recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
