Problema: Estás intentando editar tus atributos de productos en diferentes idiomas, específicamente las diferentes entradas del atributo de producto. Solución: Si estás experimentando este problema, te recomendamos cambiar a un tema por defecto para verificar si el problema persiste. Hemos identificado que el problema está relacionado con el tema actual, ya que al cambiar a un tema por defecto, la edición de atributos funciona correctamente. Esto indica que el problema podría estar en la configuración o en la compatibilidad del tema que estás utilizando.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto irrelevante, te sugerimos abrir un nuevo ticket de soporte. También te recomendamos revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para obtener más ayuda, visita nuestro foro de soporte.
Problem: You are trying to display categories as a drop-down list on the translated Thai property page using WPML, but the categories do not display at all, unlike the English page where they appear correctly. Solution: 1. Ensure that all categories are fully translated. Navigate to WPML > Taxonomy Translation, select categories from the drop-down menu, and verify that all categories are translated. For more information, visit Translating Post Categories and Custom Taxonomies. 2. Confirm that the widget used to display the categories is translated. This can be done using the String Translation or by using a separate widget for each language. Detailed guidance can be found here: Translating Widgets. 3. Check for any known compatibility issues that might be affecting the display of categories. Currently, there is an open issue related to this problem, which can be tracked on the WPML Errata page: WP Residence - No Results Found in Advanced Search.
If these steps do not resolve your issue or if the solution becomes 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 open a new support ticket.
Problem: You are facing an issue where translated products do not appear in their respective categories on the translated version of your website. Additionally, the slug for the translated version is different, requiring '-en' to be added to the category slug. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WooCommerce --> WooCommerce Multilingual --> Multicurrency. 2. Uncheck the option "Show only products with custom prices in secondary currencies". This should make all products appear correctly in their translated categories.
Please note that this solution might be irrelevant if it's 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.
The client installed WordPress in German (Sie) and then WPML, which switched to German (Du). In the meta tags, 'german-formal' appears, which the client believes is not good for SEO. They need to tag the website as being in German while using formal German with WPML.
Solution:
We recommend adding a function to the theme's child functions.php file to modify the HTML language attribute for German. Here is the code you should use:
add_filter('language_attributes', 'modify_language_attributes_for_german');
function modify_language_attributes_for_german($lang) {
// Check if the current language is German
$my_current_lang = apply_filters( 'wpml_current_language', NULL );
if ($my_current_lang === 'de') {
// Replace the language code for German
return 'lang="de-DE"';
}
return $lang; // Keep default language attributes for other 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: После перевода сайта с использованием WPML возникли проблемы с пользовательскими полями, добавляемыми плагином WPC Frequently Bought Together for WooCommerce. Solution: 1. Установите пользовательские поля в настройку "Copy" через WPML → Settings → Custom Fields Translation или активируйте опцию "Show "Multilingual Content Setup" meta box on post edit screen" для отображения на странице редактирования товара. 2. Вставьте следующий код в файл functions.php вашей темы:
Не забудьте сделать резервные копии перед внесением изменений.
Если данное решение окажется неактуальным или не поможет в вашем случае, рекомендуем открыть новый тикет поддержки. Также рекомендуем проверить известные проблемы, убедиться в актуальности версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Problema: Estás intentando traducir variaciones de productos de WooCommerce usando el editor viejo en WPML y te encuentras con que los atributos siguen bloqueados a pesar de haber desbloqueado ciertos atributos específicos. Solución: 1. Los atributos de productos no se pueden traducir manualmente usando el editor de WordPress. Para traducir los atributos, sigue los pasos en esta guía: Documentación de traducción de taxonomías. 2. Incrementa el límite de memoria de WordPress a un mínimo de 128Mb para mejorar el rendimiento. Puedes hacerlo añadiendo el siguiente código en tu archivo wp-config.php:
Asegúrate de añadirlo encima de la línea /* That's all, stop editing! Happy blogging. */. 3. Si los atributos fueron creados directamente en la pantalla de edición del producto, estos no serán globales y solo aplicables al producto específico. Para que sean globales y traducibles, debes crearlos en Productos -> Atributos.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: The client's website, which is multilingual, encountered an issue where product URLs in the French version were incorrect, leading to 404 errors. Solution: First, we suggested that the client tests the issue on a staging site using the default WordPress theme and only WPML and WooCommerce plugins enabled, ensuring all other plugins were disabled. This step was to isolate the problem and confirm it was not caused by a theme or another plugin. Upon further investigation, we discovered that the translation of the custom product base in French was incorrect. We corrected the base to match the other languages, which resolved the issue and the URLs began working correctly.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your 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 the problem persists, please open a new support ticket.
Problem: The client was unable to translate product attributes using WPML as the save icon kept loading indefinitely. Additionally, they needed guidance on translating WooCommerce emails and had issues with the contact forms.
Solution: For the attribute translation issue, we recommended checking the browser console for errors and disabling all plugins except WooCommerce, Elementor, WPML, and its addons to identify any conflicts. If the problem persisted, we suggested switching to a default theme like Twenty Twenty-One and reactivating plugins one by one to pinpoint the issue.
To resolve the attribute loading issue, we set the translation preference for product attributes to "Translatable" in WPML > Settings > Taxonomies Translation, corrected the translation preference for the "product_type" taxonomy in WooCommerce > WooCommerce Multilingual > Troubleshooting, and refreshed each attribute in Products > Attributes.
For translating WooCommerce emails, we advised checking the email templates and filling out the necessary fields, then following the guide on how to translate WooCommerce emails.
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. If further assistance is needed, 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.
