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.
Problem: If you're experiencing issues on your WooCommerce multilingual site where users get redirected to the same page instead of the payment screen when trying to place an order in the English version, while other languages like Spanish and French work fine, this might be due to multiple endpoints being registered with the main string in Spanish.
Solution: First, ensure that the 'Order received' endpoint in WooCommerce -> Settings -> Advanced is set to 'order-received'. Then, go to WPML -> String Translation and delete all strings related to 'pedido-recibido' and 'order-received' endpoints. After that, translate 'order-received' to other languages as needed, for example, 'pedido-recibido' for Spanish. Additionally, check other endpoints like 'order-pay' and ensure they are set correctly in WooCommerce settings and translated appropriately in String Translation. Follow the steps provided in our errata for detailed instructions: Incorrect content displayed when WooCommerce endpoints are translated from non-English to English.
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 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 issue persists, please open a new support ticket with us: WPML support forum.
Problem: The client was trying to translate Avada portfolio element filters from CAT to ESP and ENG. While the filters displayed correctly in ENG, they were not displaying correctly in ESP. Additionally, an unselected tag "Concerned Citizen" was showing up as a filter, despite being correctly set in the backend. Solution: We recommended a workaround for this issue, which is due to a compatibility conflict with the Avada theme. We advised the client to first perform a full site backup, which is mandatory before attempting the workaround. The workaround can be found in our errata page: Avada Theme Portfolio Tag Filter Missing in Secondary Languages We also informed the client that our compatibility team is in contact with Avada developers to address this issue, and a permanent fix will be included in future versions of the theme.
Please note that the solution provided might be outdated or not applicable to your case. If the workaround does not resolve your issue, 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 you still need assistance, please open a new support ticket.
Problem: The client is trying to translate an Avada form from English to French. The issue is that the "Checkbox fields (with conditional logic)" for the "SERVICE" field are not being displayed on the frontend of the French translation, even though the form appears as 100% translated in the Advanced Translation Editor (ATE). Solution: We recommend checking the specific errata page for a workaround regarding Avada forms where checkbox fields with conditional logic are not displaying in translated forms. You can find the workaround here: https://wpml.org/errata/avada-forms-checkbox-fields-with-conditional-logic-not-displaying-in-translated-forms/.
Please note that the solution provided might be outdated or not applicable to your case. If after following the steps the issue persists, 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 you still need assistance, please open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
