Problem: The client was experiencing issues with WPML not translating the 'post-card' element filters in the Avada theme, despite the post-card and all tags-categories being translated. Additionally, the client could not translate the 'all' filters button, the 'More...' buttons, and the button hover texts on the header's layouts.
Solution: We corrected the configuration for the filters in the Spanish language setup. We also advised the client that our support policy allows handling only one issue per ticket to maintain focus and efficiency. Therefore, we split the tickets to address each issue separately: 1. For the 'all' and 'More...' buttons, we created a separate ticket: https://wpml.org/forums/topic/cannot-translate-all-filters-button-and-the-more-buttons/ 2. For the button hover texts translation, another ticket was created: https://wpml.org/forums/topic/cannot-translate-the-button-hover-texts/ We applied a custom XML configuration to potentially solve the issue with the filters not translating correctly. The client was asked to translate the English language page to see if it resolves the issue of overwriting the filters in the Spanish 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: The client was unable to translate the "button hover texts" on the header's layouts despite trying all recommendations found on the forum and using Ai agents. Solution: We added a custom XML configuration to enable the translation of the buttons/hover buttons. We advised the client to go to the translation management page, click on the "refresh" icon, and update the translations. After updating, we recommended checking the front-end to ensure the translations were applied correctly.
If this solution does not resolve your issue, or if it seems 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 persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported that the workaround for translating the 'All' filters and 'More..' buttons was lost after updating the translation. They were unable to find these elements in the translation editor. Solution: We recommended translating the 'All' texts through the WPML String Translation page. For the 'More..' button, we provided a custom XML configuration to ensure it is translatable. Here is the XML code you need to add:
If this solution does not resolve your issue, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client was experiencing issues with translating posts from English to Spanish using the Avada theme on their WordPress site. The main problems were that the featured image displayed incorrectly, side margins were not respected, and the background color was missing in the translated version. Additionally, the Avada post page settings were not being copied to the translation. Solution: We recommended translating the 'Custom Content Layouts' for the posts in question. This involved accessing the Avada layout sections in the WordPress admin and ensuring that the layouts were correctly assigned and translated. We also suggested adjusting the layout conditions to include specific posts or categories to ensure that the design settings apply correctly across different languages. After these adjustments, the client confirmed that the layout appeared correctly in the translated posts.
Please note that this solution might be outdated or not applicable to your specific case. If you're experiencing similar issues, 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 was unable to translate CSS IDs for anchor links in different language versions of their website. The CSS IDs were not appearing in the WPML editor for translation, and manual translations were resetting whenever the default language was updated. Additionally, there were issues with untranslated internal links in the English version, which were not pointing to the correct translated pages. Solution: Clear the site's cache. Ensure that you are using the latest versions of WPML and all related plugins and themes.
It's important to note that this solution might be outdated or not applicable to your specific case. If the problem persists, please visit our support forum to open a new 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.
Problem: If you're experiencing issues where selecting 'I prefer bigger segments' in the ATE editor causes line breaks to disappear in both normal text and Toggle element text, resulting in multiple paragraphs merging into one. Solution: We recommend manually adding line breaks in the Spanish translation within the ATE segment. This adjustment should help maintain the intended text formatting and prevent paragraphs from merging. 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 highly recommend opening a new support ticket for further assistance. You can do so here: WPML Support Forum.
Problem: The client is experiencing issues while translating a page from English to Spanish using the new ATE interface. The problems include the inability to complete the translation due to formatting markers, parts of the translation resetting upon reopening, and the old ATE interface ignoring
<br />
markers and splitting paragraphs into multiple lines. Solution: We have resolved the initial issue with the HTML markers. However, the new editor still erases text line breaks when the "I prefer bigger segments" option is selected, affecting both normal text and text within the Toggle element. To address the issue with the line breaks, we have created a new support ticket which you can follow here: https://wpml.org/forums/topic/split-line-breaks-in-new-ate/
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was trying to translate portfolio links in a post using the Advanced Translation Editor (ATE). They expected the links to translate automatically or manually, but instead, the links redirected to the same post where the hyperlink was, without translating to the intended language.
Solution: 1. We identified that the issue was a bug within ATE, where adding both bold and italic HTML markers to a link text caused problems. 2. To resolve this, we recommended removing the italic text markup from the links and retranslating the content. 3. We confirmed that the issue with line breaks when using HTML markers in ATE that include a link and at least one style element should now be resolved, as we could not recreate it on a new test site. 4. For existing affected content, we advised the client to update the original content and run the translation again.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're experiencing similar issues, we highly recommend checking the related 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 with us.
Problem: The client was trying to translate the phone number in the header content from Catalan to Spanish and English using the Avada theme options, but the translations were not displaying correctly. The string was translated in WPML String Translation, but the issue persisted with incorrect translations showing or the fields being empty.
Solution: 1. Navigate to Avada-> Options-> Header. 2. Switch the language using the top admin bar. 3. Enter the translated phone string for the respective language. 4. Save the settings.
Additionally, the English string was incorrectly flagged as Catalan in the String Translation. We corrected the source language, which resolved the issue.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket.
