Problem: If you're experiencing issues with HTML tags like
<br>
showing up on the front end of your translated page instead of creating line breaks as intended, we have a solution for you. Solution: First, ensure that in WPML->Settings->XLIFF file options, the 'Do nothing – all new line characters will stay untouched' option is enabled. If this doesn't resolve the issue, we recommend adding specific XML configuration to allow HTML tags in your titles and content. Here's how you can do it:
<wpml-config><br /> <shortcodes><br /> <shortcode><br /> <tag>et_pb_fullwidth_header</tag><br /> <attributes><br /> <attribute encoding="allow_html_tags">title</attribute><br /> <attribute encoding="allow_html_tags">title_tablet</attribute><br /> <attribute encoding="allow_html_tags">title_phone</attribute><br /> <attribute encoding="allow_html_tags">subhead</attribute><br /> <attribute encoding="allow_html_tags">subhead_tablet</attribute><br /> <attribute encoding="allow_html_tags">subhead_phone</attribute><br /> <attribute>button_one_text</attribute><br /> <attribute>button_one_text_tablet</attribute><br /> <attribute>button_one_text_phone</attribute><br /> <attribute type="link">button_one_url</attribute><br /> <attribute>button_two_text</attribute><br /> <attribute>button_two_text_tablet</attribute><br /> <attribute>button_two_text_phone</attribute><br /> <attribute type="link">button_two_url</attribute><br /> <attribute>logo_alt_text</attribute><br /> <attribute>logo_title</attribute><br /> <attribute type="media-url">background_image</attribute><br /> <attribute encoding="allow_html_tags">content_tablet</attribute><br /> <attribute encoding="allow_html_tags">content_phone</attribute><br /> </attributes><br /> </shortcode><br /> </shortcodes><br /></wpml-config><br /><br />After adding this code, make a minor edit to the original page and update the translation. This should resolve the issue with HTML tags appearing incorrectly.<br /><br />If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at <a href="https://wpml.org/known-issues/">https://wpml.org/known-issues/</a>, 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 <a href="https://wpml.org/forums/forum/english-support/">WPML support forum</a>.
Problem: The client is experiencing issues with updating translations using the Classic Translation Editor in WPML. Instead of opening in the Classic Translation Editor, it redirects to the standard WordPress editor. Additionally, the English version of the page displays in Dutch, indicating a mix-up in source and translation languages. Solution: We recommend the following steps to resolve the issue: 1. Edit the Dutch language page and disconnect it from its translation. This can be done by following the instructions here: https://wpml.org/faq/how-to-disconnect-translations-from-the-default-language-page-or-post/ 2. After disconnecting, reconnect the page and set Dutch as the primary language.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.
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.
