Custom Work

Problem:
You have a custom plugin with a custom post type. When the site's current language is set to a non-default language, such as Dutch, and you create a custom post type, it is only associated with the current language. You tried using

'lang' => 'all'

in WP_Query parameters without success. The issue is that when performing a WP_Query for the custom post type, only records in the default language are shown, filtering out records in other languages.
Solution:
To include custom post types in all languages in your WP_Query, you need to use the

suppress_filters

argument in your query. Here's how you can modify your WP_Query:
1. Set

suppress_filters = true

to fetch posts from all languages.
2. Set

suppress_filters = false

to get posts only in the currently viewed language.
For more detailed information, you can visit the WPML documentation on achieving compatibility for themes and plugins at https://wpml.org/documentation/support/achieving-wpml-compatibility-for-your-themes-and-plugins/#filter-correct-ids.

Please note that this solution 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 issue persists, please open a new support ticket at our support forum.

Problem:

The client wants to show the default language in the /en/ subdirectory on their site. Although the page loading works with this structure, the internal links for the original language do not include the /en/ directory, which breaks the internal linking structure.

Solution:

We recommended the client to first resave the Language URL settings under WPML >> Languages >> Language URL format, then go to Settings >> Permalinks and resave those settings as well. After these steps, it's crucial to clear all types of caches to check if the issue persists.

If internal links still do not reflect the /en/ directory, we suggested editing the homepage in English and making minor content changes to see if the links update accordingly.

If this does not resolve the issue, using a plugin like Better Search Replace was advised as a last resort, with a strong recommendation to take a full site backup before attempting this.

Please note that this solution 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 do not hesitate to open a new support ticket for further assistance.

Problem:
You need to set different labels and URLs for each language in the 'Return to the shop' snippet in a WooCommerce site using WPML.
Solution:
We recommend using one of the WPML hooks to dynamically change the URL based on the current language. You can use the

wpml_current_language

hook to detect the current language and then set the URL accordingly. Here is an example of how you can implement this:

function wc_empty_cart_redirect_url() {<br />  if(ICL_LANGUAGE_CODE == 'en') {<br />    return 'custom-url-EN';<br />  } elseif(ICL_LANGUAGE_CODE == 'fr') {<br />    return 'custom-url-FR';<br />  } else {<br />    return 'custom-url-DE';<br />  }<br />}<br />add_filter('woocommerce_return_to_shop_redirect', 'wc_empty_cart_redirect_url');

For more details, check the documentation on wpml_current_language and wpml_object_id.

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.

Problem:
You are using the Xstore theme on your WordPress site and have uploaded custom fonts. While these fonts work perfectly on the original domain, they do not display correctly on the translated domain, reverting to default fonts like Times New Roman. This issue is also visible in the backend theme editor.
Solution:
We recommend checking the admin texts where theme option terms are typically saved. For instance, if your custom font is 'Jost', search for 'Jost' in the admin texts. Once found, add it to the string translation table. Ensure that the string for the font name is consistent across all languages. This approach should help in correctly displaying your custom fonts on the translated domains. If this solution does not resolve the 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 do not hesitate to open a new support ticket with us for further assistance at WPML support forum.