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:
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 needed to translate archive pages for custom post types (CPTs) and deactivate/delete unwanted indexed translated archive pages. Solution: We recommended manually registering the CPTs to avoid issues with translations and indexing. Additionally, the client provided a custom code snippet to disable the archive slug for some CPTs in all languages other than the default. Here is the code snippet:
will fetch posts only in the specific language by bypassing WPML filters.
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 further assistance is needed, 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.
Problem: You have multiple MB text fields on your homepage, but some are not visible in the WPML Advanced Translation Editor screen, even though they are set to 'Translate' in WPML > Settings > Custom Fields Translation. Solution: We recommend adding the following line to your functions.php file:
After adding this code, edit the page in the default language, make a minor edit, and then update it. This should allow the missing fields to appear when using the search field in the Advanced Translation Editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client needed to modify the hreflang links for dynamic pages that exist only in the main language (FR) and wanted to know if there is a hook to filter or remove these links. Solution: We recommended using the
wpml_hreflangs
hook to change or remove the alternate hreflang links. We provided examples of how to implement this filter with links to relevant documentation:
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, please 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, you can contact us directly at WPML support forum.
Problem: The client needs PHP filters or functions with WPML to retrieve the ID of translated media attached to a Meta Box field group on their homepage. Solution: We recommend using the
wpml_object_id
hook to obtain the ID of a translated media. Here is an example of how to use this hook to get the German translation ID for an attachment:
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 you still need assistance, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing difficulty in finding specific strings in WPML > String Translation due to the abundance of bricks-* or gutenberg-* domains. Solution: Currently, it is not possible to hide bricks-* or gutenberg-* domains directly in WPML > String Translation. To address this issue, you would need to implement custom coding. However, this solution falls outside our support scope, and we do not have a ready-made code snippet available.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum.
Problem: The client changed the default locale from 'en_US' to 'en_GB' in WPML, and the translations for 'Gridbuilder ᵂᴾ' are not appearing on the English pages despite being visible in WPML > String Translation. Solution: We recommend regenerating the MO files to ensure WPML pulls the strings from the correct locale. Please navigate to WPML -> Support -> Troubleshooting and click the 'Show custom MO Files Pre-generation' dialog box button. Then, click the blue button to regenerate custom MO files. If this does not resolve the issue, it may be necessary to manually create and rename copies of the MO files to match the new language locale. For detailed steps, please visit https://wpml.org/errata/string-translations-are-not-displayed-when-a-language-locale-is-changed/.
If the solution provided does not apply or is 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. Should you need additional assistance, please do not hesitate to open a new support ticket.
Problem: The client was unable to add Dutch (Belgium) with the locale code 'nl_BE' to their WPML languages, receiving an error that the default locale already exists, despite it not being visible in the WPML > Languages > Add / Remove languages section. Solution: We recommended the client to check their database table
_icl_languages
for any entries with a default locale set to 'nl_BE'. Upon inspection, it was found that the locale should have been 'nl_NL'. The client corrected these values in their database, which resolved the issue and allowed them to add Dutch (Belgium) as a custom language.
If this solution does not apply to your case, or if it seems outdated, we 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 issues persist, please open a new support ticket.
