Problem: The client was setting up their website hosted on SiteGround to have each language point to a different domain. They encountered an issue where WPML could not validate the domains due to a 'www' redirection rule automatically added by SiteGround in the .htaccess file. Solution: To resolve the issue, the client removed the automatic 'www' redirection rule from the .htaccess file. This change allowed WPML to successfully verify all multilingual domains, enabling the site to function as expected. It is important to note that it is not necessary to remove 'www' from the main site URL; the key is to avoid forcing 'www' for parked or language-specific domains.
If you're experiencing similar issues, we recommend checking your .htaccess file for any forced 'www' redirection rules and removing them if present. For further guidance, you can refer to our documentation on setting up different domains per language.
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.
Problem: The client is trying to translate Elementor header templates and is experiencing issues with typographical confusion and missing CSS styles on translated pages. Solution: We recommend following up on the existing support ticket where this issue is already being addressed. You can find the ongoing discussion and potential solutions here: https://wpml.org/forums/topic/unable-to-translate-elementor-header-templates-translated-language-web-pages-typographical-confusi/. Please mark the current ticket as resolved to keep the support process organized and ensure your original ticket remains a priority.
If this solution does not resolve your 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 necessary, please open a new support ticket for further assistance.
Problem: The client needed help estimating the cost of automatic translation for their site. They had downloaded their bill and the automatic translation usage report but were unable to determine the cost for each site. Solution: We advised the client to get a total word count for the site to estimate the automatic translation credits by selecting the posts/pages from WPML > Translation Management. For detailed steps, we recommended following this guide: Getting a Word Count of Your WordPress Site. Additionally, we provided the total credits used for the mentioned site for the month, which amounted to 1,583,989 credits. We explained that this total was calculated by summing up all the credits from the CSV file of the credits usage. We also guided the client to find their Automatic Translation Usage Report by navigating to WPML > Translation Management > Tools > Payment and settings > Automatic Translation Usage Reports.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
