adrienR-5

Problem:
You need to translate a Meta Box Post field under a User profile and select a Custom Post Type (CPT) 'franchise' for every translation of your WordPress website.
Solution:
First, ensure that you unset or set as 'Not translate' any of the mb- type of options in WPML > Settings.
Next, add the following code to your functions.php file to make the 'franchise_associated' user custom field translatable:

add_filter( 'wpml_translatable_user_meta_fields', function( $fields ) {<br />    $fields[] = 'franchise_associated';<br />    return $fields;<br />} );

Then, navigate to WPML > String Translation. Search for 'franchise_associated' and translate the CPT numerical id. For example, in the provided Sandbox site, translate from 68 to 70.
For detailed guidance, review the documentation on Translating User Meta Information with WPML.

If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket.

Problem:
The client is experiencing hreflang conflicts when auditing their site with SEMRush, specifically issues with missing self-referencing hreflang tags and incorrect hreflang attributes for pages created with custom code. They are using WPML and SEOPress Pro.
Solution:
We recommended ensuring that the option to display alternative languages in the HEAD section is checked and set to 'as early as possible' in WPML->Languages->SEO options. This setting helps WPML to manage hreflang tags automatically. For more detailed guidance on managing hreflang with WPML, visit General Documentation on WPML & Hreflangs.
If these settings do not resolve the issue, or if the hreflang tags need specific adjustments due to custom-coded pages, we may need to investigate further by requesting temporary access to the site to diagnose the issue directly.

Please note that the solution provided might be outdated or not applicable to your specific case. 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.