Problem: The client is using a child theme of the Astra theme and has added custom code that integrates with the UABB Product Slider Module. After a system update, the strings in the frontend are no longer translated, although they appear translated in the backend's String Translations table. Solution: We recommend reviewing and adjusting the custom code to ensure it is compatible with WPML. Key areas to check include: 1. Ensuring dynamic language handling for Google reviews. 2. Configuring WPML custom fields for product meta fields like stock messages. 3. Using consistent text domains across the custom code. 4. Ensuring correct WPML object-ID lookups for products. 5. Avoiding hard-coded strings and ensuring that strings are registered and translated through WPML.
Since this involves custom code, which is not typically covered by our support policies, we recommend testing these changes on a staging environment first. If issues persist, consider consulting with a developer familiar with WPML. For further assistance, you can 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.
Problem: You might be encountering an issue where valid application URLs like 'https://www.bcfi.be/nl/chapters/7?frag=5314' are incorrectly rewritten by WPML to WordPress permalinks during runtime, such as 'https://www.bcfi.be/nl/?p=7&frag=5314'. This problem occurs because WPML's 'Absolute Links' functionality misinterprets application routes as WordPress content when the numeric segment matches a WordPress post ID.
Solution: Unfortunately, handling custom application routes that do not follow WordPress standards falls outside the scope of our support. We recommend consulting with an independent developer to create a solution tailored to your specific setup. For more details on our support policy, please visit https://wpml.org/purchase/support-policy/.
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, we encourage you to open a new support ticket for further assistance.
Problem: The client is unable to permanently translate the icon texts of the Chauffeur theme from English to Greek. Solution: We added the following custom XML code to enable the translation of the icon texts:
We instructed the client to navigate to WPML > Settings > Custom XML Configuration (tab) and add this code. Afterward, the client should make a small change in the original language and save it. Then, by accessing the Advanced Translation Editor, all the icon content should be available for translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 the problem persists, please open a new support ticket.
Problem: You are using WPML with WooCommerce Multilingual & Multicurrency on a catalogue-only site without any pricing, cart, or checkout functionalities. Despite disabling multcurrency, WCML is still setting 'wcml_client_currency' and 'wcml_client_currency_language' cookies, which prevent Varnish from caching guest responses.
Solution: We recommend implementing a custom MU plugin to selectively remove these specific WCML cookies on guest WooCommerce catalogue pages, while preserving other necessary cookies like those for WPML language settings. Here's a step-by-step guide on how to do this:
This approach is safe for a catalogue-only site and does not interfere with WPML's language handling or WooCommerce's product categorization and filtering. If you find this solution not applicable due to updates or it doesn't fit your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket at WPML support forum.
Problema: Si estás experimentando que las variaciones de tus productos no aparecen en el idioma original y por defecto (español) en tu tienda WooCommerce, pero sí en otros idiomas, y has confirmado que desactivando los plugins de WPML las variaciones aparecen correctamente, el problema podría estar relacionado con la configuración de WPML o con el código personalizado en tu tema hijo. Solución: 1. Verifica y elimina los atributos duplicados o no conectados en cada idioma desde la sección de taxonomías traducidas y asegúrate de que los atributos traducidos estén conectados. Puedes hacerlo accediendo a: Administrar atributos. 2. Asegúrate de que los slugs de los atributos en cada idioma sean únicos. 3. Si el problema persiste, podría ser debido a personalizaciones en tu tema hijo, específicamente en el código personalizado que afecta las variaciones de WooCommerce. Consulta con tu desarrollador sobre este código:
Si la solución proporcionada no resuelve el problema o parece no ser relevante debido a actualizaciones o diferencias en tu caso, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.