Problem: You are managing translations in the backend of your WordPress site and notice a discrepancy: the translation queue shows no translations, yet a notification indicates that one translation is waiting for review. Clicking on the notification leads to a screen with no translations. Solution: We recommend following these steps to resolve the issue: 1. Navigate to WPML -> Support -> Troubleshooting. 2. On the troubleshooting screen, sequentially press the following buttons, waiting for each process to complete before proceeding: - 'Disable cache for language switcher templates' - 'Clear the cache in WPML' - 'Remove ghost entries from the translation tables' - 'Fix element_type collation' - 'Set language information' - 'Assign translation status to duplicated content' - 'Set language information' - 'Fix terms count' - 'Fix post type assignment for translations' Then, recheck to see if the issue persists.
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 continues, please open a new support ticket at WPML support forum for further assistance.
The client discovered that the English homepage of their site had unexpectedly changed to a post published a month ago, while the Italian homepage remained correctly configured with a series of articles.
Solution:
We recommended checking the site in a minimal setup by disabling plugins and switching to default themes to rule out any conflicts.
If this solution does not resolve the 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client attempted to re-translate their entire website using DeepL after erasing previous translations, but the site behaved as if everything was still translated. Additionally, headers made with Elementor were not translating, and the company name 'Linneo' was incorrectly translated as 'Linnaeus'. Solution: Firstly, Albanian is not supported by DeepL; thus, WPML uses Google or Azure based on the site settings, which can be adjusted in WPML > Settings. Regarding the issue of not being able to re-translate, this occurs because WPML applies existing translations from its translation memory to avoid multiple charges for similar content. To re-translate, the translation memory would need to be cleared, noting that this would incur translation costs again. To prevent incorrect translation of the company name 'Linneo', it is recommended to use the glossary feature in WPML, ideally before starting the translations.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we recommend opening a new support ticket.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
