Problem: You are updating to the latest WPML on a server with a case-sensitive filesystem (e.g., Ubuntu) and encounter a file/folder naming issue with the Yoast/whip vendor library. The folders are named lowercase on disk, but the code refers to them with capitalized names, causing a 500 Critical Error due to libraries not loading. Solution: If you're experiencing this issue, we recommend checking if you are using an older version of the files that might not have been overwritten during the update. In WPML version 4.6.13, the folder names should match the case used in the code. You can verify this by comparing your current folder structure with the official repository at Yoast/whip Configs and Yoast/whip Facades. If the mismatch persists, creating symbolic links from the uppercase to lowercase versions as a temporary fix might be necessary, but this is not a long-term solution.
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 WPML 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 is trying to synchronize the post/page status between the original version and its translated version. They want to auto-translate pages but keep both versions unpublished until the translation is complete. They are facing issues because auto-translation only triggers once a page is published. Additionally, they want to ensure that when updates are made to the English content, the French translation is auto-translated but held for review before it goes live.
Solution: We explained that the automatic translation feature does not translate unpublished draft posts. However, draft posts can be sent to automatic translation manually from WPML > Translation Management. To publish the translation when the original post is published, go to WPML > Settings > Translated documents options > When you publish the original post: Publish the post translations.
Problem: The client needed to import a large spreadsheet of over 40,000 glossary terms into their WPML installation for a translation project, but discovered that WPML does not support direct import of glossary terms. Solution: We clarified the difference between a glossary and a translation memory. A glossary is a list of specific terms with their translations, while a translation memory stores complete text segments and their translations. We informed the client that the Advanced Translation Editor (ATE) does not support direct import of translation memories but allows sharing of translation memory across multiple sites using the same automatic translation account. We advised against importing the spreadsheet as a glossary to prevent inconsistencies and potential damage to the quality of translations. For further guidance, we provided links to our documentation:
