Problem: After updating WordPress and WPML, texts including standard paragraph blocks are missing on the translation page for patterns. Solution: We identified that the Arabic pattern was broken after the update. We have fixed the issue. Please verify if the texts are now appearing correctly on your translation page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: You have installed a plugin to translate your German website into English, but the product category is missing on the English translation page. Solution: We recommend checking the English language portfolios to see if the custom field "id_field" exists. This issue might be due to the "Order By" custom field condition not working correctly on the English language page. If the field is missing, adding it should resolve the problem.
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.
Problem: The client is experiencing issues with a 3rd party plugin widget not translating correctly. Specifically, the titles on product filters and the 'Search Products...' placeholder are not appearing in the correct language. Additionally, the client mentioned that posts set to publish when the original is published are being published prematurely. Solution: For the translation issues with the widget, we recommend duplicating the category filter and assigning the appropriate language to each duplicate. This method should help ensure that the widget displays correctly in each language. For the issue of posts being published prematurely, ensure that the 'Publish the translated post when the original is also published' option is correctly configured to match your scheduling needs.
If these solutions do not resolve your issues or if they seem 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. Should further assistance be needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to translate customized fields using WPML but encounters an issue where the translations do not appear on the frontend. The client used a custom hook and registered labels to WPML, translating them successfully. However, despite following documentation and using code examples, the translations are not visible on the frontend. Solution: 1. Ensure the text domain is correct. According to WordPress documentation, the text domain must use dashes, be lowercase, and have no spaces. 2. When using variables in translated strings, use the
printf()
function instead of echoing the variable directly. For example, change:
<p id="popup-title"><?= $popuptitle ?></p>
to:
<p id="popup-title"><?php echo __('Subscribe Now, Save 10%', 'storefront') ?></p>
After making these changes, re-scan the strings in the child theme, translate the string, and check if the translation displays on the frontend. 3. If using a custom text domain like "popup", register it with the following function in your theme's
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please visit our support forum.
Problem: You are experiencing an issue where WPML is not translating the WPBakery Page Builder templates correctly, and the translations are not appearing on the live website despite following the documentation at https://wpml.org/documentation/plugins-compatibility/how-to-build-multilingual-sites-with-wpbakery-page-builder-and-wpml/. Solution: 1. Ensure that you are using the WPML Translation Editor to translate your content. Post types such as pages, posts, and page builder content cannot be translated directly at WPML > String Translation. 2. Go to WPML > Settings > Post Type Translation and set the WPBakery Templates to "Translatable - only show translated items". 3. Translate the templates using the WPML Translation Editor, similar to how you would translate pages and posts. 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 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.
Problema: Utilizzi Gravity Form con l'addon ufficiale per creare articoli su WordPress in un sito multilingua (italiano, inglese, francese), ma quando un form viene compilato in inglese, l'articolo risultante viene creato in inglese anziché in italiano, la lingua base del sito. Soluzione: Questo è il comportamento atteso di Gravity Form quando utilizzato in un contesto multilingua. Una possibile soluzione è non tradurre il form o impostare il tipo di post risultante come non traducibile. Questo potrebbe far sì che gli articoli vengano creati sempre in italiano, indipendentemente dalla lingua in cui il form è stato compilato. Se questa soluzione non dovesse essere adeguata, l'unica alternativa sarebbe creare del codice personalizzato, che però non possiamo fornire.
Se questa soluzione non risolve il problema o se è inapplicabile al tuo caso, ti consigliamo di verificare i problemi noti e di assicurarti di avere installato le versioni più recenti dei temi e dei plugin. Se il problema persiste, ti invitiamo a aprire un nuovo ticket di supporto.
Problem: The client wants to change the URL structure to include the category slug, but only for the Norwegian language on their multilingual site. They are using WPML and currently have a different structure for Danish. Solution: We have determined that it is not possible to have different URL structures for each language when using WPML, as the content needs to be linked properly across languages. Additionally, attempting to force this change through code modifications is likely to cause issues and is not recommended.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we encourage you to 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. For further assistance, please visit our support forum at https://wpml.org/forums/.
Problem: If you're using the WordPress Focal Point plugin to set focal points on images and have noticed that the 'bg_pos_desktop' meta field is not being copied to new translations despite being set to 'Copy', you might be facing a compatibility issue. Solution: First, ensure that you can view the meta field within the media when editing it in the backend. Remember that media IDs differ per language, which might affect the copying process. Unfortunately, the Image Background Focus Position plugin is not officially compatible with WPML. We recommend contacting the plugin author to join our Compatibility program to facilitate compatibility. Meanwhile, you can manually adjust the focal point by: 1. Going to the Media Library. 2. Using the language switcher at the top to switch to the secondary language. 3. Editing the media and adding a focal point manually. This workaround allows you to set a focal point that could be the same or different per language. For a visual guide on these steps, you can watch this screencast: Workaround steps.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
