Problem: The client reported a Remote Code Execution (RCE) POP Chains vulnerability in the WPML String Translation plugin, specifically in the file located at
. This vulnerability could allow an attacker to take control of deserialized objects. Solution: We have released a new version of WPML that addresses this security issue. We recommend that you update both WPML and all WPML addons to ensure your site's security is up to date.
If this solution does not seem relevant to your current situation, or if it appears outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
apparaît dans les blocs de texte de l'éditeur Gutenberg lors de la conversion des articles depuis l'éditeur classique. Vous souhaitez savoir comment éviter cela. Solution : Ce code est un indicateur utilisé par WPML pour identifier les contenus traduits avec notre éditeur. Il apparaît lorsque vous modifiez la traduction avec un éditeur différent de celui utilisé initialement. Si vous transférez le contenu manuellement et gérez les traductions séparément pour chaque langue, cet indicateur n'est plus nécessaire. Vous pouvez ignorer ce code si vous ne l'utilisez pas pour des traductions automatiques ou assistées par WPML.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus et de vous assurer que vous utilisez les versions les plus récentes des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
Problem: Si estás experimentando un problema donde WPML Multilingual CMS está sobrescribiendo el slug base de las categorías de producto de WooCommerce, a pesar de haber cambiado la base de categorías de producto en WooCommerce de 'product-category' a 'categoria-producto', y confirmado que el cambio fue guardado correctamente en la base de datos, pero WPML CMS sigue generando las URLs como '/product-category/...', este resumen es para ti. Solution: El problema puede estar siendo causado por un conflicto con un plugin de terceros que revierte los cambios de URL realizados por WPML. Para resolverlo, te recomendamos desactivar y reactivar tus plugins uno por uno, o en grupos, para identificar cuál está causando el problema. Una vez identificado el plugin problemático, puedes mantenerlo desactivado o buscar una solución específica para ese plugin. Además, asegúrate de: 1. Ir a WPML > Settings > Taxonomy Translations y añadir el slug traducido para Product Categories. 2. Ir a WooCommerce > WCML > Store URLs y añadir la traducción para Product Category.
Si la solución proporcionada aquí no resuelve tu problema, o si crees que la información puede estar desactualizada, te recomendamos 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. Si el problema persiste, no dudes en abrir un nuevo ticket de soporte en nuestro foro de soporte.
Problem: Nach dem Update auf WPML 4.9.1 treten Fehlermeldungen auf, die auf Probleme beim Zugriff auf Array-Offsets hinweisen. Dies deutet wahrscheinlich auf eine Datenbankkorruption und fehlende Einträge in der Sprachentabelle hin. Solution: Wir empfehlen Ihnen, ein Backup Ihrer Website zu erstellen und sicherzustellen, dass Sie auf WPML Version 4.9.1 aktualisiert haben. Sollten die Probleme weiterhin bestehen, navigieren Sie bitte zu WPML > Support > Fehlerbehebung und klicken Sie auf „Sprachen zurücksetzen“. Dies sollte die Probleme beheben, wie wir es erfolgreich auf einer Kopie Ihrer Website getestet haben.
Bitte beachten Sie, dass diese Lösung möglicherweise veraltet oder nicht auf Ihr spezifisches Problem anwendbar ist. Wir empfehlen Ihnen, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu bestätigen und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie dazu unser Support-Forum.
Problem: If you're unable to see the slug translation (URL translation) in the Advanced Translation Editor (ATE) for product pages on your WooCommerce site while using WPML, but it works fine on normal pages. Solution: We recommended adding a code snippet to the site to fix the issue with percent-encoded characters in URL slugs. This solution is specifically for products that were translated automatically and removes percent-encoded characters (e.g., %80) from URL slugs during translation processing, preventing empty slugs caused by invalid UTF-8 bytes after sanitize_title() processing. Please note that this solution might be irrelevant if it's 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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You are encountering an issue where media items are not being duplicated in secondary languages when uploaded by an Editor, despite the settings in WPML → Media Translation being configured to duplicate texts (alt, caption, title) for all media and featured images across all languages. This problem does not occur with an Administrator role. Solution: We have identified that this issue may be related to the visibility settings of languages. Here are the steps we recommend: 1. Ensure that the languages are not hidden. If they are hidden, the media won't be duplicated into other languages. 2. If hiding languages is necessary for your workflow, consider setting all translations to be drafts or under review, which keeps them non-public similar to hidden languages. 3. An additional setting allows Admins to specify whether an individual user can see hidden language content. This setting is found in the user profile section and must be activated on a user-by-user basis by an Admin.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant 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 problem persists, please open a new support ticket.
Problem: The client reported a price discrepancy on their website where the Essential Grid displays a higher price for a product ('Cocktail slim ear cuff') on the product archive page than on its single product page. Despite the correct lower price showing on the single product page, the archive page displayed the price incorrectly. Solution: We analyzed the issue and found that custom code added to the site's functions.php file was intended to display only the minimum price of product variations. We replicated the setup in a sandbox environment and a local copy, where the product displayed the correct price. We recommended the client to duplicate the problematic product on their live site, as this resolved the issue in our tests. If duplicating the product does not resolve the issue, it might be due to the custom code or other site-specific configurations.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
