Problem: The client is using the Advanced Translation Editor (ATE) in WPML and has content that does not require translation. Despite setting the translation priority to 'Not needed' for specific pages, these pages still appear as 'not translated' in the translation management dashboard. The client is seeking ways to automatically exclude such items from translation processes, especially when using the 'Translate Everything Automatically' feature. Solution: Currently, WPML does not support the automatic exclusion of items marked as 'Not needed' from the translation process when using the 'Translate Everything Automatically' feature. Our team has reviewed the request to deselect some content from the translation editor, but as of now, this is not a popular request, and there are no plans to implement it in the near future. We recommend manually managing items that do not need translation and not including them in the 'Translate Everything Automatically' setup.
If this solution does not fully address your issue or if it becomes 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client enabled the Advanced Translation Editor (ATE) on a site that previously used the Classic Translation Editor (CTE). They configured it to keep old CTE translations, only use ATE for new translations, and publish them without review. However, after restoring a backup and re-enabling ATE, the translations were stuck at 'In Progress' and not being published. Solution: We resolved the issue by cancelling and resending the specific translation task (in this case, from Dutch to Portuguese) for automatic translation. This action should resolve the publishing delay.
If you're experiencing similar issues with ATE translations not being published, we recommend trying to cancel and resend the translation tasks. If this solution does not apply to your case, or if it seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify you have the latest versions of themes and plugins, and confirm the version of the permanent fix. If the problem persists, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client reported that pages previously translated using the Classic Translation Editor (CTE) were unexpectedly redirected to the Advanced Translation Editor (ATE), resulting in the loss of professional translations.
Solution: We discovered that an alteration in the database might have caused this issue. We recommend running the following SQL query to address the problem:
1
UPDATE `wp_icl_translate_job` SET `editor` = 'wpml'WHERE `editor_job_id` IS NULL;
Before executing this query, ensure you have a full backup of your site and database. If there were structural changes to the content (fields changed, added, or removed), some translations might appear incomplete in the CTE, and you will need to manually complete these translations.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that two Divi modules were not being translated on the front end, despite the translations being present in the Advanced Translation Editor (ATE). The issue was observed after adding translations for Arabic, Japanese, Portuguese, and Korean. Solution: We investigated the issue and discovered that the problem was caused by an emoji (🌿) within the text. This emoji interfered with the translation display. We removed the emoji from the text and re-translated the page into Japanese, which resolved the issue. Additionally, we noticed that the database collation sequence had reverted to utf8mb3_unicode_ci, which could potentially cause issues with character encoding. We corrected this by changing the collation back to utf8mb4_unicode_ci.
If you're experiencing similar issues, we recommend checking for any special characters or emojis in your translations that might be causing display issues. Also, verify the database collation settings to ensure they support extended character sets. For more detailed guidance, please visit our documentation on WPML documentation.
Please note that this solution might be outdated or not applicable to your specific 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. If necessary, do not hesitate to open a new support ticket with us for further assistance.
Problem: You are a website designer using WPML and have connected all your sites to share a single pool of credits, which results in shared translation memory and glossary across all sites. You are looking for a way to share credits but keep the translation memory separated by website. Solution: Currently, there is no option available to share credits while keeping translation memories and glossaries separate for each website. All connected sites to a specific automatic translation account will share the glossary, credits, and translation memory. We have noted your request and will mention it to our developers as a potential feature for future updates.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is using website management software that lists all available updates with links to the repository, but these links don't work for WPML because it is commercial software. The client requested adding links to the WPML release notes in the WordPress repository. Solution: We explained that WPML uses an installer plugin embedded within WPML itself, which manages updates. This process is complex and involves WordPress hooks and our remote server that provides the updates. The links in the Dashboard -> Updates section are generated by these hooks, and the update information is fetched periodically from our site and stored in the client's database based on their subscription.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening 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. For further assistance, please visit our support forum at WPML Support Forum.
אנו משתמשים בקובצי Cookie כדי לייעל את האתר והשירותים שלנו. הסכמתך מאפשרת לנו לעבד נתונים כגון התנהגות גלישה. אי הסכמה עשויה להשפיע על תכונות מסוימות.
פונקציונלי
תמיד פעיל
נדרש כדי שהאתר שלנו יפעל ויתקשר בצורה נכונה.
העדפות
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
סטטיסטיקה
אנו משתמשים בהם כדי לנתח את הנתונים הסטטיסטיים של האתר שלנו. המידע שנאסף הוא אנונימי לחלוטין. האחסון או הגישה הטכנית שמשמשים באופן בלעדי לצרכים סטטיסטיים אנונימיים. ללא זימון, הסכמה וולונטרית מצד ספק שירותי האינטרנט שלך, או רשומות נוספות מצד שלישי, המידע המאוחסן או המוחזר למטרה זו בלבד לא ניתן בדרך כלל לשימוש לצורך זיהויך.
שיווק
קובצי Cookie אלה עוקבים אחר הגלישה שלך כדי לספק מודעות רלוונטיות עבורך.
