Problem: You are trying to update the WPML SEO plugin but encounter an error message: 'Download failed. Method Not Allowed.' This issue occurs across multiple websites. Solution: If you're experiencing this issue, we recommend checking the AWS CAPTCHA triggers. In this case, they were responsible for generating too many requests from the server's IP address, leading to HTTP 405 errors.
Please note that this solution might be 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: The client is using the shortcode [wpml_disabled_selector_widget] to display the language switcher on their site. However, when the translator, who has the subscriber role, translates content using the classic translation editor, the translated content shows the shortcode as [wpml_disabled_selector_widget] with an error message "You're not allowed to use this shortcode." in the front end. Solution: We investigated whether this issue was specific to the client's website or a general bug. We suggested testing with only the Divi parent theme and WPML plugins enabled to isolate the issue. Additionally, we identified that the problem stems from the 'unfiltered_html' permission in WordPress, which is not granted to users with the subscriber role for security reasons. This permission prevents certain users from using advanced HTML or scripts in posts. We recommended using the Advanced Translation Editor (ATE), which does not have this limitation, and ensuring all translations are re-sent and re-translated using ATE.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
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:
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.
