[Waiting for user confirmation] Frontpage design isnt being translated correct.

I just wanted to update you that I've resumed working on it and 'll update you soon today.

Thank you for your patience and cooperation.

Thank you for your patience and cooperation.

It turns out that WPML has support for URL Encoded Shortcodes. So now everything on the home page should be fine. I've also updated the home page translation, as well as, one Portfolio post translation. For the rest of the Portfolio posts, simply open for editing in default language, save without any change and update the translation. Please note that if you see links are not pointing well to the translated version, edit the translation and adjust manually.

The support for URL Encoded shortcodes was added by the followings:

1) Added the following code (as mentioned in the guide also) with needed fields name modifications, to the functions.php file of your active theme:

// See https://wpml.org/documentation/support/translating-urlencoded-shortcodes/#translating-values-in-urlencoded-shortcodes for details.
add_filter( 'wpml_pb_shortcode_encode', 'wpml_pb_shortcode_encode_urlencoded_json', 10, 3 );
function wpml_pb_shortcode_encode_urlencoded_json( $string, $encoding, $original_string ) {
    if ( 'urlencoded_json' === $encoding ) {
        $output = array();
        foreach ( $original_string as $combined_key => $value ) {
            $parts = explode( '_', $combined_key );
            $i = array_pop( $parts );
            $key = implode( '_', $parts );
            $output[ $i ][ $key ] = $value;
        }
        $string = urlencode( json_encode( $output ) );
    }
    return $string;
}
 
add_filter( 'wpml_pb_shortcode_decode', 'wpml_pb_shortcode_decode_urlencoded_json', 10, 3 );
function wpml_pb_shortcode_decode_urlencoded_json( $string, $encoding, $original_string ) {
    if ( 'urlencoded_json' === $encoding ) {
        $rows = json_decode( urldecode( $original_string ), true );
        $string = array();
        foreach ( $rows as $i => $row ) {
            foreach ( $row as $key => $value ) {
            if ( in_array( $key, array( 'header', 'descr', 'icon_text', 'href' ) ) ) {
                    $string[ $key . '_' . $i ] = array( 'value' => $value, 'translate' => true );
                } else {
                    $string[ $key . '_' . $i ] = array( 'value' => $value, 'translate' => false );
                }
            }
        }
    }
    return $string;
}

2) Then added encoding="urlencoded_json" to the custom XML as below:

    <shortcode>
      <tag>like_sc_block_icon</tag>
      <attributes>
        <attribute encoding="urlencoded_json">icons</attribute>
      </attributes>
    </shortcode>
    <shortcode>
      <tag>like_sc_social_icons</tag>
      <attributes>
        <attribute encoding="urlencoded_json">icons</attribute>
      </attributes>
    </shortcode>

3) And finally opened the page for editing in default language, resaved and updated the translation.

Please consider following:

1) If you want to use different images per language, you 'll need to use WPML Media Translation. However, if you want to use same images across languages, then no need of it, but in both cases there are settings in WPML -> Settings -> Media Translation which can be used to handle this.

Please see the attached image (media translation settings.jpg). First part of these settings (till the "Start" button) is a wizard which you can use to fix the said issue. This makes your uploaded image (to a page, post or featured - considered an attachment), available in all languages.

The second part controls the settings, as you want to deal with the media when uploaded.

2) Please see our guide on Translating Widgets for more details.

3) I only updated first polio as shown in the attached image (portfolio-01.jpg). You can follow these steps for rest of the portfolios:
- Go to Portfolios.
- Open the portfolio for editing in default language.
- Simply save the portfolio without making a change.
- Update the translation, ensure it is 100% and complete it.
- Clear cache and recheck.
- Repeat these steps for each portfolio which you isn't showing as translated on the frontend.

The above code enabled the recognition of these URL encode fields, so the translations need to be updated as mentioned in these steps. The same applies to every place in your site where these blocks/widgets have been used.