Problème : Vous tentez de traduire des variations de produits. En français, cela fonctionne parfaitement, mais en anglais, les produits apparaissent sans variations. Aucun sélecteur de variation n'est visible sur la page anglaise du produit. Solution : 1. Assurez-vous que chaque variation de produit ait son propre SKU. Par exemple, ajoutez les SKUs 12001-1 et 12001-2 pour les variations françaises. 2. Ouvrez la traduction du produit dans l'éditeur WordPress. 3. Dans la barre latérale à droite, section "Langue", choisissez "Ceci est la traduction de: VIDE" pour détacher la traduction de l'original. 4. Cliquez sur "Connecter les traductions" et choisissez le produit en français, en vous assurant de décocher la case qui rend l'anglais langue source. Cela permet de reconnecter la traduction avec la source française et de re-synchroniser tous les champs correctement. Pour plus de détails, consultez la documentation sur comment déconnecter les traductions.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: If you're trying to manage translations and encounter an empty page when accessing the WPML > Translations page, it might be due to a stuck translation job. Solution: We recommend checking for any old or stuck translation jobs at WPML > Translation Management > Jobs. In this specific case, we identified and resolved an issue with a translation job from March 2024 that was causing the problem. You should now be able to access the WPML > Translations page without issues.
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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client needed help translating Fluentform, noting that it seemed incompatible with WPML. Solution: We recommend trying the operation again as we have implemented a temporary workaround that should now allow Fluentform to work with WPML.
Add this to WPML > Settings > Custom XML Configuration and re-translate the page. Add correct translated form ID.
1
2
3
4
5
6
7
8
9
10
<wpml-config>
<shortcodes>
<shortcode>
<tag>fluentform</tag>
<attributes>
<attribute>ID</attribute>
</attributes>
</shortcode>
</shortcodes>
</wpml-config>
If you're still experiencing issues, 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 solution provided here becomes irrelevant or does not resolve your issue, please do not hesitate to open a new support ticket. You can do so at WPML support forum.
Problem: The client is trying to translate media to English, but most of their media are originally in English due to a possible error during migration from Polylang. They need to change the original language for media and link English images to their French counterparts without re-uploading them. Solution: We explained that currently, there is no way to change the original language of media in WPML. If the client needs to use different images in different languages, they should upload the image they want to switch in WPML -> Media Translation. We also advised that if they switched the image in WPML -> Media Translation after the post had been translated, they need to make a small change in the original language post and update it. This will trigger a change in the translation, and after updating the translation, the new image should appear. We recommended clearing any site caching after these changes. Additionally, we provided a link to our Media Translation guide for further assistance: https://wpml.org/documentation/getting-started-guide/media-translation/
If this solution is not relevant due to being outdated or not applicable to your case, we encourage you to open a new support ticket. 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 need further assistance, please contact us in the WPML support forum: https://wpml.org/forums/forum/english-support/.
Problem:
The client was unable to see and edit the English menu after creating it from the French menu. The English menu disappeared from the menu section upon returning to it. Additionally, the French menus appeared to be duplicated. Solution:
We recommended the client to perform a conflict test by disabling all plugins except for WPML to see if the issue persists. This is a common step to isolate the problem and determine if there is a conflict with another plugin. We also pointed out that a similar issue was being addressed by our colleague Carlos in another support ticket, and suggested to follow that conversation if it was related. It is important to back up the database before making any changes to prevent data loss. https://wpml.org/forums/topic/menu-translation-error-in-the-db/
If you're experiencing this issue, we recommend you try the above steps. However, keep in mind that the solution might be irrelevant due to it being outdated or not applicable to your case. If the problem persists, 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 open a new support ticket at our support forum.
Problem: The client is experiencing 404 errors when setting 'boutique' and 'shop' as Product category prefixes for their French and English WooCommerce shop pages, respectively. The desired URLs are: - French: /boutique/cat_name - English: en/shop/cat_name
Solution: We recommend not using the same slug for the shop base and the product category base, as this causes conflicts in WooCommerce's custom permalink structure. WordPress requires unique slugs to distinguish between categories and products. Therefore, the client should choose a different base for the product category to ensure the category page works correctly on the frontend.
If this solution does not apply to your situation, or if it seems outdated, we highly recommend checking the 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 encounter issues, please do not hesitate to open a new support ticket with us.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
