Problem: You are using the Xstore theme on your WordPress site and have uploaded custom fonts. While these fonts work perfectly on the original domain, they do not display correctly on the translated domain, reverting to default fonts like Times New Roman. This issue is also visible in the backend theme editor. Solution: We recommend checking the admin texts where theme option terms are typically saved. For instance, if your custom font is 'Jost', search for 'Jost' in the admin texts. Once found, add it to the string translation table. Ensure that the string for the font name is consistent across all languages. This approach should help in correctly displaying your custom fonts on the translated domains. If this solution does not resolve the issue or 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 the problem persists, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Problem: You are using the Xstore theme and WPML for translations on your site and have noticed that some theme text fonts differ from the original language on translated pages. The issue appears to be that the font is not found for the translations and defaults to a different font. Solution: First, verify if the font issue is related to the specific characters of the language by deactivating WPML and viewing the page in another language using a primary domain. This can help determine if the problem persists without WPML. If the issue remains, it suggests that the problem might be with the FUTURA font itself, rather than WPML. Consider checking the font settings in your theme or consulting with the theme provider for more specific guidance on font management.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your case, 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 contact us through our support forum at WPML support forum.
Problem: You have set up WPML to use different domains for different languages, and after doing so, images are not displaying on the translated domains. You have attempted to run media duplication for different languages, but the issue persists. Solution: We recommend deactivating the All-In-One Security (AIOS) plugin and then testing the issue again. This action resolved a similar issue on a testing site by allowing images to display correctly on the second domain. If this solution resolves the problem, it may confirm that the AIOS plugin is causing a conflict with WPML's media handling on translated domains.
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 at WPML support forum for further assistance.
Problem: The client is experiencing an issue where Google search results prioritize English pages over Estonian pages when searching for 'timberelement' in Estonia, despite using WPML. Solution: 1. We recommend checking your Google Search Console for insights on how Google is indexing your pages, which might reveal why English pages are prioritized. 2. Review any custom redirects set by the Redirection plugin on your site, as these might be influencing the prioritization of English pages in search results. 3. We have verified that the WPML setup is correctly configured for language handling, indicating no issues from WPML's side. 4. Consider hiring an SEO expert for a detailed analysis. You can find trusted partners at WPML Contractors who specialize in SEO and multilingual setups.
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 open a new support ticket at WPML support forum.
Problem: The client wants to add a Russian translation to their website, which currently has Finnish and English translations on separate domains (nordtimber.fi and nordtimber.ee respectively). The client wishes to place the Russian translation in a subdirectory (nordtimber.ee/ru) while keeping the other languages on their separate domains. Solution: We explained that WPML currently supports only one Language URL format at a time. Therefore, it is not possible to have a mix of different URL formats, such as domains for some languages and a subdirectory for another, within the same website. If you're experiencing a similar issue, we recommend considering the use of either domains or subdirectories for all languages to maintain consistency.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you encounter difficulties or this solution does not fit your needs, we encourage you to open a new support ticket. We also 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 further assistance is needed, please contact us through the WPML support forum.
