Problem: The client created a custom post type with associated custom fields using ACF, translated via WPML. They then used Ninja Table to display these fields. While it works in French, in English, the custom field values still appear in French, and the shortcodes added to the table do not display any content.
Solution: We recommended modifying the function to dynamically retrieve the post type of the
$post_id
instead of hardcoding it. We also suggested adding error handling for missing fields and allowing dynamic shortcode attributes. Here is the revised code:
// Function to get translated ACF fields using WPML
function get_translated_acf_fields($post_id, $language_code = null) {
if (!$language_code) {
$language_code = apply_filters('wpml_current_language', null);
}
$translated_post_id = apply_filters('wpml_object_id', $post_id, get_post_type($post_id), false, $language_code);
if (!$translated_post_id) {
return null;
}
$fields = array(
'ville' => get_field('ville', $translated_post_id),
'publics' => get_field('publics', $translated_post_id),
'programmes' => get_field('programmes', $translated_post_id),
);
return $fields;
}
add_shortcode('ville_field', 'display_ville_field');
add_shortcode('publics_field', 'display_publics_field');
add_shortcode('programmes_field', 'display_programmes_field');
Additionally, we suggested testing the code without Ninja Table first and ensuring that Ninja Table is set as "Translatable" in WPML > Settings > Post Type Translation, then translating the tables and using their respective shortcodes in each language.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is unable to find labels from a View created with the Advanced Custom Views Framework in the WPML String Translation. The labels were set up in a View linked to custom fields and a custom post type created using the Advanced Custom Fields (ACF) plugin. Although the labels are included in a language file generated in the child theme, they do not appear in String Translation. Solution: We recommend the following steps to make the labels from the Custom Views Framework translatable: 1) Modify one string in the View to ensure it includes a text domain. 2) Check the generated file in your child theme to see if it updates with the new string. 3) Rescan the child theme in WPML -> Themes & Plugin Localization. 4) Verify if the strings now appear in WPML -> String Translation.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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 at WPML support forum.
Problem: You are using the Timeline Block For Gutenberg to present timelines on your site. When translating the page, everything including dates can be translated, but the dates still appear in French on the English page. This issue arises because the date is not from the core blocks and is not supported for string translation. Solution: We recommend using a custom XML configuration code to register the date for translation. After translating, the date should display correctly in the frontend. Here is an example code:
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 at our support forum.
Problem: You are using the LH Archived Post Post Status plugin to archive pages and want to translate a custom archiving message set in the plugin's settings page, but it does not appear in the string translations. Solution: First, ensure you have deleted any existing translations of the default message in WPML > String Translation. Then, scan the LH Archived Post Status plugin for strings by navigating to WPML > Plugin and Theme localization. If the custom message still doesn't appear, use the 'Translate texts from admin screens' option in WPML > String Translation. If the message is still not available for translation, adjust the translation preferences by going to WPML > Settings and enabling 'Show System Field' under 'Custom Field Translation'. Search for 'post_status_message' and set its translation preference to 'Translate'. After saving the message again in the settings, switch to another language using the language switcher on the topbar, add the message manually for that language, and save the changes. For detailed guidance, please refer to this guide.
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 needed, please open a new support ticket for further assistance at WPML support forum.
Problem: The client was experiencing issues with translating slugs for a custom post type slug that comes from the plugin Citadela, that was showing up on WPML->Settings->Post Types Translation.
Solution: Firstly, we recommended that any code changes should indeed be made in the child theme to prevent them from being overwritten during plugin updates. Regarding the slug translation issue, we provided the following steps:
4. After making the change, go to WPML -> Settings -> Custom post type translation -> Items (citadela-item), enter the translation for "lieu", and click "Save".
We also emphasized the importance of having a full backup of the website before making any updates or changes.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: If you're experiencing issues with Media Translation not working consistently, particularly with the Gutenberg "File" block where the translated page still shows the original language file instead of the translated file, even after making small edits to the page and its translation.
Solution: We recommend trying the following steps: 1. Increase the WP memory limit. For more details, check the minimum requirements documentation. 2. Enable a minimal environment by deactivating all non-WPML plugins and switching to a standard WordPress theme. IMPORTANT: Please backup your database and website before proceeding. You can use the Duplicator plugin for this purpose.
If the issue persists, apply this workaround: 1. Add the following custom XML configuration code to WPML > Settings > Custom XML Configuration tab to register the file URL for translation:
2. Edit the page in the original language, make a small change to the content, save, and then update the translation in the Advanced Translation Editor (ATE). 3. In ATE, search for the keyword "http" and translate the file URL. To get the file URL, go to Media > Library > Edit the file > File URL. For further guidance, refer to the documentation on making custom Gutenberg blocks translatable and how to translate URLs using ATE.
Problem: The client installed ACF Multilingual and set an ACF group field to be the same across all languages. Despite translating the fields in string translation, the field still appeared in French on the English page. Solution: We recommended ensuring that the 'Return Format' for the 'Select' field in ACF is set to 'Label'. The steps to do this are: 1. Go to 'ACF > Field Groups' and open the relevant field group. 2. Click on the specific field. 3. Scroll down to the 'Return Format' option and select 'Label'. 4. Save the changes. After saving the changes, the client should update both the default page and its translation. If this solution does not resolve the issue, we invite the client to open a new support ticket.
