Problem: You are trying to translate content created with Elementor and the CharityWP theme, which includes custom Elementor elements from the Thim Core Plugin. These elements are not translatable using the usual methods such as the Advanced Translation Editor. Solution: We recommend ensuring that every custom Elementor widget has an XML configuration so it can be translated using the WPML Translation Editor. This configuration should ideally be provided by the theme author and included in a
If these solutions do not apply or become outdated, or if you encounter further issues, 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 needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/ for further assistance.
Problem: If you're using Bricks Builder with WPML and notice that elements are not appearing in the correct order within the Advanced Translation Editor, especially on pages with a large number of elements. Solution: We have identified that this issue occurs under specific circumstances and have communicated with the Bricks Builder development team. They have acknowledged the bug and are currently working on a fix. While waiting for the update, we recommend manually creating content rather than using copy/paste or block duplication, as this has shown to work correctly in our tests. Please note that the solution provided here might not be applicable to your situation if it's outdated or not relevant to your specific case. We highly recommend checking the related known issues, verifying the version of the permanent fix, and ensuring that you have the latest versions of themes and plugins installed. If the issue persists, please do not hesitate to open a new support ticket with us.
Problem:
Bricks 404 template doesn't work on secondary languages
Solution:
Please follow the steps and see if it helps:
- Go to WPML > Settings > Custom Fields.
- Click on show system fields
- Change your settings to its initial state for the following: do nothing.
_bricks_template_settings
_bricks_template_type:
- Go to Bricks templates, switch to the secondary language: Delete the template translation.
- Translate the template again.
You may need to open the original template again using Bricks editor.
Problem: The client was experiencing a crash with the Advanced Translation Editor (ATE) when trying to translate a page built with BricksBuilder. A specific field that had been translated before was showing as untranslated, and any attempt to select it would cause ATE to crash, resulting in a 'TypeError: Cannot read properties of null (reading 'split')' error message. Solution: We resolved the issue by updating the page title and retranslating it. We recommend the client to verify if the solution worked on their end.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still encountering issues, we encourage you to open a new support ticket. We also 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. If further assistance is needed, please contact us through the WPML support forum.
