Problem: The client inquired about the compatibility of Heroic Knowledge Base and Ultimate FAQ with WPML, specifically concerning the FAQs section. Solution: We confirmed that Heroic Knowledge Base states compatibility with WPML, but it is not officially tested by us. For more details, visit Hero Themes WPML Guide. You can also check our list of officially compatible plugins at WPML Compatible Plugins. Regarding the FAQs in Heroic Knowledge Base, using a Custom XML Configuration will not resolve the issue. We recommend contacting the plugin/theme author for compatibility checks and potential cooperation for proper WPML integration. As for Ultimate FAQ, we currently do not have confirmed information about its compatibility with WPML. We advise checking directly with the plugin author to confirm support for multilingual setups.
If these solutions become irrelevant due to updates or if they do not apply to your case, we highly recommend checking related known issues at WPML 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 feel free to open a new support ticket at WPML Support Forum.
Problem: The client reported an issue where the FAQ page translated using WPML still displayed in English on the German version of their site. Additionally, there were problems with the FAQ group showing a message that no items were present in German, despite being fully populated in English. The client uses the Heroic FAQs plugin. Solution: We identified a compatibility issue between the Heroic FAQs plugin and WPML. We recommended reaching out to the plugin's developers to report the issue and suggest their participation in the WPML Go Global Program to enhance compatibility. As a temporary workaround, we suggested setting the FAQ group to 'Not translatable', creating a separate FAQ group for German, and manually assigning this new group to the German page. This method was tested and confirmed to work on a staging site.
If this solution does not resolve your issue, 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 the problem persist, please do not hesitate to open a new support ticket at our support forum.
Problem: The client is experiencing two main issues with their WPML setup on different sites. First, the FAQ page translated via WPML is still displaying in English on the website. Second, there is a conflict error with the WPML site key on the production site, which has disrupted the ATE connection and is preventing translation jobs from being processed. Solution: 1. For the issue with the FAQ page not displaying translations, we have opened a separate support ticket to address this specific problem. You can follow the updates and find detailed guidance here: https://wpml.org/forums/topic/split-faq-not-translated/. 2. Regarding the ATE connection issue, it is crucial to clarify the terminology and setup regarding what is referred to as a 'hub'. In WPML, this typically involves the Advanced Translation Editor (ATE) where multiple sites can share translation credits, memory, and glossaries. It is important to confirm whether the 'hub' mentioned refers to this ATE setup or something specific within your infrastructure. Understanding this will help us provide a precise and safe recommendation for resolving the connection issues.
If these solutions do not resolve your issues or if they seem 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 further assistance be needed, please do not hesitate to open a new support ticket. For additional support, visit our support forum at https://wpml.org/forums/.
Problem: The client was experiencing issues with video embedding on their multilingual site using WPML. The videos were not displaying correctly in the German version, and there were outdated translations on the page certificate despite attempts to update them through the WPML dashboard. Solution: We investigated the issues and identified that the Perfmatters plugin, which is not officially compatible with WPML, was causing the video embedding problem. Disabling the Perfmatters plugin resolved the issue, allowing videos to display correctly in both languages. For the outdated translations, we recommend re-translating the content manually if automatic updates through the WPML dashboard do not reflect the changes. For caching solutions that are compatible with WPML, we suggest checking the list of officially supported cache plugins here: https://wpml.org/plugin-functionality/caching/
Please note that this solution might be outdated or not applicable to your specific case. If the issue 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, please open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing an issue where an image in a carousel on their German page remains in English, despite being added to the WPML media library. The problem seems to be due to the use of different image sizes in different languages, causing WPML not to recognize them as the same image. Solution: We recommend installing a plugin like Regenerate Thumbnails and running it to ensure all image sizes are properly generated across languages. This should allow the correct (translated) image to appear on the frontend. If the issue persists after trying this solution, please check our 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 solution provided here does not resolve the issue or seems outdated, we encourage you to open a new support ticket for further assistance. You can do so at our support forum.
Problem: You are missing the second button on your page, and it is not visible in the WPML editor. Solution: The missing button originates from a pattern/template rather than the page itself. To resolve this, you need to translate the template separately. Once translated, the content, including the button, will display correctly on the frontend.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client was facing issues with outdated translations on their 'Page certificate' and missing elements on the 'Front page' and 'About us page' in different languages using WPML. Solution: For the outdated translation on the 'Page certificate', we recommended re-translating the content manually if automatic translation did not update the text. For the front page issues, it was discovered that the settings were not being synced to the secondary language due to the custom field '_generate-disable-post-image' being set to 'Do not translate'. We changed this setting to 'Copy' under WPML > Settings and then resaved the default language page. Additionally, for the image translation issue, we added the following XML configuration in WPML > Settings to ensure images are translated correctly:
We also advised the client to contact the theme author to ensure proper WPML configuration for these fields.
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 issue persists, please open a new support ticket.
