Problem: If you're trying to translate a global element created with Bricks Builder and are encountering issues where the translation does not appear correctly on the frontend.
Solution: We recommend following these steps: 1. Apply the fix from the WPML errata page for Bricks Builder issues. You can find it here: Bricks translated content not showing on frontend. 2. Edit the home page in the default language using Bricks Builder and make necessary text changes. 3. Save your changes and exit to WordPress. 4. Update the translations in the Advanced Translation Editor (ATE), ensuring all text is present and translated. 5. If some elements still don't display correctly, go to WPML -> String Translation. Search for the strings that are not showing correctly, correct their language if necessary, and translate them. For guidance on changing the language of a string, visit: How to change the source language of strings. 6. Note that if you are using plugins like 'Max Addons for Bricks' which are not compatible with WPML, you might need to manually translate some elements using the WP Editor. For more information on using different translation editors, see: Using different translation editors for different pages.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.
Problem: You are trying to translate Bricks Builder pages and some Custom Post Types (CPT) created with JetEngine, but the design of the Bricks Builder pages disappears, and you are unable to find some meta fields in the translated version. Solution: For the issue with Bricks Builder pages losing design upon translation, please refer to our Errata page for a known issue and workaround: Bricks translated content not showing on frontend. To translate shortcodes from the translation editor, you need to register the shortcode for translation. Follow the guide here: Translate custom shortcodes with WPML. For translating JetEngine meta fields, navigate to "WPML > Settings → Custom Field Translation" and set the translation preference for those fields to 'Translatable'. For more details, check the Crocoblock guide: Translate Meta Boxes & Meta Fields. If you encounter issues translating the ID within a shortcode, use the String Translation to translate the entire shortcode. Navigate to "WPML > String Translation", search for the shortcode, and update the ID for translation as needed.
If the solution provided here does not resolve your issue or seems outdated, we 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. For further assistance, please visit our support forum: WPML Support Forum.
