Problem: If you're experiencing issues where translations are not consistently appearing on your website, particularly in the French language version, this might be due to how the theme’s text domain is being loaded. Solution: We recommend checking if your theme's text domain is loaded correctly. The text domain should be loaded using the following code:
function my_theme_load_theme_textdomain() {
load_theme_textdomain('my-theme', get_template_directory() . '/languages');
}
add_action('after_setup_theme', 'my_theme_load_theme_textdomain');
Ensure that: - The text domain used in the translation functions matches the one being loaded. - The text domain is loaded during the
after_setup_theme
action. - The theme adheres to WordPress internationalization standards. For more detailed guidance, please refer to the official WordPress documentation on theme internationalization and text domains: WordPress Internationalization Documentation.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at WPML 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: You are developing a site and need to display the same content for a custom post type while only translating the taxonomy terms. You are unsure if it is possible to display the same content of a custom post type with only the taxonomy terms translated. Solution: 1) You can set the custom post type (CPT) to fallback to the default language in WPML-> Settings-> Post Type Translation section. For more details on showing untranslated content, please check this guide. 2) If the issue persists, try duplicating the CPT and check if the duplicated CPT displays correctly. You can bulk duplicate the posts via WPML-> Translation Management.
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.
Problem: You have translated an ACF field group that includes a select field with three values. While the backend displays the translated values correctly, the frontend still shows the original strings. Solution: The issue stems from your theme's template file. The 'illegal string offset' warning typically arises when attempting to access an array element with a string key, but the variable in question is not an array. This discrepancy explains why you encounter no error when 'Both' is an object (Array) and 'Label' is a string. We recommend following the ACF documentation on how to properly display fields in your theme. You can find the necessary guidelines here: ACF Documentation on Select Fields
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. We also 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.
