[Resolved] Prevent WPML from translating ACF Pro variables inside Bricks Builder

Problem:
You are experiencing issues with WPML translating ACF Pro variables within Bricks Builder, causing layout disruptions upon updating translations.
Solution:
Note that this issue was already resolved in one of the latest updates for the Advanced Translation Editor. The tags might still show up inside the translation editor, but automatic translation should not affect them.

Alternative workarounds:
1. Use the Glossary Feature in the Advanced Translation Editor to declare dynamic tags as general terms to prevent them from being translated. For guidance, visit How to get better translations using WPML Glossary.
2. Alternatively, consider using a different theme and displaying fields with PHP. For more information, check Displaying custom field values in your theme.
3. To exclude ACF Pro variables from being translated in Bricks Builder, add the following code to the end of the functions.php file of your Bricks Theme:

add_filter( 'wpml_tm_job_field_is_translatable', 'wpmltriage_skip_acfdynamic_fields_in_bricks', 10, 2 );<br /><br />function wpmltriage_skip_acfdynamic_fields_in_bricks( $is_translatable, $job_translate ) {<br />    $data = $job_translate['field_data'];<br />    if ( 'base64' === $job_translate['field_format'] ) {<br />        $data = base64_decode( $data );<br />    }<br />    if (isset($data) && strpos($data, '{acf_') === 0) {<br />      return false;<br />  }<br /><br />  return true;<br />}

If this solution does not resolve your issue or seems outdated, we 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 further assistance is needed, please open a new support ticket at WPML support forum.