The client is using Advanced Custom Fields (ACF) with WPML and has set up the Advanced Custom Fields Multilingual. However, the field choices are not being translated in the frontend despite translating the labels in WPML>>String Translation. The features section with bullet points is not translated across all languages.
Solution:
We recommended using the
get_field_object
function instead of
get_field
to fetch the field data correctly. This change should allow the field choices to display the translated values.
Here is the modified code snippet to implement in the functions.php file of the child theme:
// Create shortcodes for individual fields without titles
function generate_individual_field_shortcodes_no_title() {
// List of fields to create shortcodes for
$fields = [
'living_area',
'views',
'laundry',
'bathroom',
'kitchen_and_dining',
'bedroom',
'media_and_entertainment',
'miscellaneous',
'home_safety',
'outdoor_spaces',
'family-friendly',
'parking_and_facilities',
'languages_spoken',
'nearby',
'house_rules',
'cancellation_prepayment',
'refundable_damage_deposit',
'payment_methods'
];
foreach ($fields as $field) {
// Dynamically generate shortcode callback for each field
add_shortcode($field . '_list', function() use ($field) {
ob_start(); // Start output buffering
$fields = get_field_object($field); //Get field data
$options = $fields['value'];
// Display labels.
if( $options ): ?>
<ul>
<?php foreach( $options as $option ): ?>
<li><?php echo $fields['choices'][$option]; ?></li>
<?php endforeach; ?>
</ul>
<?php endif;
return ob_get_clean(); // Return the output and end buffering
});
}
}
add_action('init', 'generate_individual_field_shortcodes_no_title');
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 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 experiencing issues with translations not saving after reaching 100% and clicking 'Complete' on their homepage using WPML. Additionally, they are unable to translate Advanced Custom Fields (ACF) using WPML. Solution: For the issue of translations not saving, we recommend making a small change in the default language, such as updating the title, and then saving the changes. After this, re-translate the page using the WPML Advanced Translation Editor and save again. This approach can help refresh the translation jobs and apply the new changes correctly. Regarding the translation of Advanced Custom Fields, since this issue is complex and specific, we advise opening a new support ticket dedicated to this problem for a more detailed investigation and assistance.
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 issue persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problema: Si estás intentando aplicar descuentos a categorías de productos en WooCommerce Memberships y notas que el menú desplegable para seleccionar las categorías queda en blanco cuando el plugin WPML String Translation está activado, este resumen es para ti. Solución: 1. Asegúrate de que el plugin WooCommerce Memberships es compatible con WPML revisando esta documentación. 2. Verifica la configuración de Traducción de taxonomías en WPML -> Configuración y asegúrate de que las categorías están correctamente traducidas. 3. Incrementa el límite de memoria de WordPress a un mínimo de 256M añadiendo el siguiente código en tu archivo wp-config.php:
4. Actualiza todos los plugins desactualizados, especialmente 'WooCommerce Subscriptions'. 5. Actualiza los plugins de WPML a la última versión para evitar problemas conocidos. Puedes hacerlo desde este enlace. 6. Si el problema persiste, considera crear un sitio staging y replicar el problema para un análisis más detallado.
Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos relacionados, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problem: The client was experiencing an issue where a loading wheel displayed instead of the usual translation marker when trying to translate a training course. Clicking on the wheel led to a strange page instead of the usual translation block. This issue persisted even after deleting and re-adding text blocks and clearing caches. Solution: We recommended creating a staging site to safely test solutions without affecting the live site. After gaining access to the staging site, we identified and fixed a database issue related to language settings. We advised the client to: 1. Edit the homepage in the original language. 2. Make a minor change to the content. 3. Save these changes and update the translation. This process resolved the issue. We assured the client that this problem was likely a one-time issue caused during the WPML installation and should not recur. Additionally, we provided a video tutorial demonstrating the steps to update the translation correctly.
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. If problems persist, please open a new support ticket.
Problem: The client is experiencing issues with the currency switcher on their website. The currency switcher does not work on the homepage and behaves unpredictably when changing languages or navigating different pages like cart, checkout, about, and home, especially when a performance plugin with cache is enabled. Solution: 1. Verify that the website is accessible and loading correctly. If not, check with the hosting provider. 2. Flush the cache memory and temporarily deactivate the cache plugin to see if the issue with the currency switcher persists. 3. Ensure that the WordPress memory limit is sufficient. It is recommended to set it to at least 128M. This can be done by adding the following line to the wp-config.php file:
Place it above the line /* That's all, stop editing! Happy blogging. */. 4. If the issue disappears when the Breeze cache plugin is disabled, consider switching to a cache plugin that is compatible with WPML, such as LiteSpeed Cache.
If these steps do not resolve the issue or if the solution 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. If the problem persists, please open a new support ticket.
Problem: You are experiencing issues where adjustments made on a translated page in Elementor are lost when the original page is updated. This happens because WPML overwrites manual adjustments if it thinks you are using the WPML editor. Solution: To prevent losing your manual adjustments on the translated page, you need to switch to the WordPress editor for making these changes. This way, WPML will not overwrite your manual work when the original page is updated. For detailed guidance, please refer to our documentation on using different translation editors for different pages: Using Different Translation Editors for Different Pages.
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.
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. If needed, please open a new support ticket at WPML support forum.
Problem: The client is looking to use WPML AI to translate their website from Dutch (NL) to French (FR) and is inquiring about the availability of this feature for 15,000 posts. Solution: We have scheduled the deployment of the NL to FR translation feature via WPML AI for around February next year. This timeline ensures that we can thoroughly test and ensure everything functions correctly before its release.
Please note that this solution might be outdated or not applicable to your specific case. 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 this does not resolve your issue, please open a new support ticket.
Problem: The client is trying to translate the WooCommerce Quote or Enquiry Contact Form 7 plugin on their site but the content on product pages is not being translated into English. Solution: We took the following steps to resolve the issue: 1. Cleared both the Object Cache and WP Rocket caches. 2. Navigated to WPML > Languages, enabled Language filtering for AJAX operations, and saved the changes. 3. Went to Settings > Permalinks and resaved the permalink structure. 4. Cleared all caches again and tested the form as an incognito user and as a non-logged-in user. The form is now displaying correctly in all languages.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is facing an issue where transaction emails sent via the Germanized plugin for their site are in English instead of German, despite updating string translations and deleting the wp-content/languages/wpml folder as suggested by the Germanized plugin vendor, Vendidero. Solution: We recommend ensuring that you are using the latest versions of the WPML String Translation and the Germanized plugin. Then, go to WPML's String Translation and re-validate or add the translations for the email titles ("Payment received for order" and "Confirmation of your order") and save the changes. This approach resolved the issue in a test case, where the email language correctly switched to German.
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. If the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is trying to add translations to their page using WPML and the Avada builder. They have successfully translated another site previously but are facing issues with translations not showing on the page and permalink structure changes. Solution: 1. Ensure that all posts are fully translated. The issue might be due to some posts being marked as 'In Progress'. Complete these translations and verify if the issue resolves. 2. Check a translated post to ensure it opens correctly. For example, verify the post at https://iwakiaircomdev.wpenginepowered.com/products/serie-1-4-tc-x050/?lang=es to see if it displays as expected.
If these steps do not resolve your issue or if the solution 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.
Problem: You are trying to translate a page using WPML, but you encountered an issue because the job exceeds the file size limit of 1MB. Solution: We recommend ensuring that the content you are trying to translate is properly added. You can do this by pasting it into a regular text editor as an update. If this solution does not resolve your issue, or if it seems outdated or not applicable 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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is trying to translate a page to 100% completion, but after saving, the translation progress reverts to 98%. Solution: We recommend checking if the default text includes any formatting markers that might not have been applied or if the segments were not saved properly. It's also important to note that we use TinyMCE, the same editor used by WordPress, which might affect how text formatting is handled. For more detailed guidance, please visit https://wpml.org/forums/topic/wpml_linebreak/#post-16292641.
If this solution does not resolve your 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate your WooCommerce shop page, but it turns blank when you attempt to translate it. Solution: We recommend navigating to WooCommerce → Settings, then open the Products tab and go to Display. Here, you can define a shop page for the default language. Use the top-bar language switcher to ensure a corresponding page is selected for the translation.
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: You are trying to resolve an issue where the updated PLN prices via BaseLinker's API are visible in the WooCommerce product backend but do not reflect on the frontend without manual updates. This behavior differs from EUR prices, which update immediately. Solution: Firstly, BaseLinker is not officially compatible with WPML, which might be causing the issue. We recommend contacting BaseLinker's authors to consider joining our GoGlobal program to work towards compatibility: https://wpml.org/documentation/support/go-global-program/ If PLN is your second currency and you are updating it, WPML synchronizes changes when the post is saved. You might need to trigger a re-save of the post using hooks like
save_post
or
update_post
. This approach may require additional custom coding. For custom coding, consider hiring a contractor from WPML: https://wpml.org/contractors/
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 for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
