Problem: The client is experiencing an issue where Advanced Custom Fields (ACF) are registered to the incorrect language (English), despite being created in Dutch. Solution: If you're experiencing issues with ACF fields being registered to the incorrect language, and you're unable to change the source language for certain strings because the option is greyed out, it's likely due to those strings being part of a String package. To resolve this, you need to select all the strings within that particular package to modify their source language. We recommend following the steps in this video to change the language of all strings under the ACF domain to the default language: https://tinyurl.com/ym9js9gq. If this solution doesn't seem relevant to your situation, please don't hesitate to open a new support ticket with us: Contact WPML Support.
Problem: If you're looking to change your WPML subscription level, for example from an Agency to a CMS account. Solution: We recommend allowing your current Agency subscription to expire. After that, you can purchase a new CMS account, as we do not offer downgrade plans. Ensure to cancel the automatic renewal of your current subscription. To switch to manual renewal, please follow the steps in our documentation:
Problem: The client is concerned about the URL encoding for Russian language links on their website, which appear with encoded characters instead of Cyrillic characters. They are worried this might negatively impact their SEO. Solution: We explained that the behavior observed is not an issue and is not related to WPML. URL encoding is a standard way for browsers to handle links containing non-ASCII characters, ensuring that search engines can read the URLs correctly. When hovering over the link with the mouse pointer, the browser will display the correct URL at the bottom. Therefore, there is no need for concern as this is the correct and expected behavior for URLs.
Problem: The client was unable to change the font for their site when translated from English to Arabic using the Divi theme. They attempted to apply custom CSS to set the font-family for the Arabic language but it did not work. Additionally, they encountered issues translating large portions of the site, particularly in widgets from plugins.
Solution: We recommended adding custom CSS code to change the font for a specific language. Here is an example of the code that should be added to the Appearance > Customizer > Custom CSS area:
The client should replace "he-IL" with the correct language code for Arabic and "Alef" with the desired font family name. We also discovered that the issue might be related to Divi Caching, which has a font set for the Arabic language that could be overriding the custom CSS. We suggested clearing the Divi cache and checking the Divi options for font settings that might be set per language. If the client was not the one who built the site, we advised consulting with the person who did for more information on how the fonts were set up.
For the issue of translating large portions of the site, we asked the client to open a new ticket, as per our Support Policy, which states that we handle only one issue per ticket.
Problem: The client is facing an issue where product variations are available in the main language but not in the translated version, preventing users from purchasing the product in the other language. Solution: We found that the attributes were not correctly set to be translatable. We corrected this by setting them to translatable in the WPML -> Settings -> Taxonomy Translation section. Then, we updated the product in the default language and its translation. If the product is a duplicate and not translated, we recommend following these steps:
Edit the product in the default language.
Change a variation's price.
Update the product.
Switch the language from the top admin bar to the translated language.
Click the update button to update the translated product.
Problem: The client was translating the Gravity Forms (GF) form from WPML >> String Translation page and and translated "-values" entries causing issues in conditional fields. Solution: We recommend using the WPML Translation Editor for translating the Gravity Form. Detailed steps can be found in our documentation: Gravity Forms Multilingual.
For string translation, focus on translating custom labels and text from the Gravity Forms plugin files by selecting the "gravityforms" domain in the WPML >> String Translation page. Avoid translating the "gravity_form-ID" domain from WPML >> String Translation page
Problem: The client was unable to preview translated pages, even though they appeared as correctly translated in the WPML editor. Solution: We identified that the issue was due to the parent page not being assigned for the 'integral-solutions' page. To fix this, we: 1. Switched to the English language version of the site. 2. Quick edited the 'Integral-Solutions' page. 3. Assigned 'Product' as its parent page. This resolved the preview issue for the translated pages.
Problem: The client wants to use WPML to auto-translate content from English to German, even though English is not the default language of the website, which is Danish. The client prefers English to German translations due to better grammar quality compared to Danish to German. Solution: We recommend following the steps from a similar request found in our forum: How can I use automatic translation from other languages? To translate content on a one-by-one basis: 1. Go to WPML > Translation Management. 2. Choose the "Translate myself" option. 3. Navigate to WPML > Translations. 4. Click on "Translate" for the content you wish to translate. For bulk translations, this feature is currently under development, and we do not have a specific release date as our development team prioritizes tasks based on various factors.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket for personalized assistance. You can do so here: WPML support forum.
Problem: The client is experiencing an issue where the WPML plugin cannot connect to the host after updating, and the website address appears different than expected. Solution: 1. We suggest that the issue might be a false positive due to server caching. The notification may be removed automatically when the cache clears. 2. To verify if it's a false positive: - Navigate to Plugins > Add new > Commercial. - Click the "check for updates" button. - If the page refreshes and WPML still shows as registered, then it's confirmed to be a false positive. If this solution doesn't seem relevant to your issue, please open a new support ticket with us.
Problem: The client needed to check if WPML was installed on a demo site that is no longer accessible and wanted to know how to remove it from their account if it was. Solution: 1. We recommend visiting your WPML account and clicking on "Register WPML on your sites" at https://wpml.org/account/sites/. 2. Look for your demo site in the list of registered sites. If you find it, click the trash icon to unregister it. 3. If the demo site is not listed, then it's not registered and there's no action needed. If this solution doesn't look relevant, please open a new support ticket.
Problem: The client is experiencing a PHP Fatal error when trying to save a page, with the error indicating an issue with the
array_filter()
function in the WPML plugin files. Solution: If you're experiencing a similar issue, we recommend you try the following steps: 1. Go to WPML → Support → Troubleshooting. 2. Run the option "Remove ghost entries from the translation tables". Please ensure you backup your database before making any changes.
Problem: The client needs to connect pages that are translations of each other after importing content from an old site. Solution: We recommend using the 'Connect with translations' feature to link pages that are translations of each other. Here are the steps to follow: 1. Go to the page that you want to connect. 2. Look for the 'Language' box on the right side. 3. Click on the 'Connect with translations' button. 4. A popup will appear where you can search for the page in the other language. 5. Connect the pages by selecting the appropriate translation. For detailed instructions, please refer to our documentation: How to link already translated pages.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem: The client is experiencing an issue where the Korean version URL is being displayed in an encoded format when copying and pasting. Solution: We explained that browsers have a feature that encodes URLs to ensure they are usable and can be accessed without issues, especially if they contain specific characters. To copy the URL as it appears, we suggested omitting one letter from the protocol part of the URL, such as 'h' from 'https', and then adding it back after pasting.
Problem: The client is trying to retrieve all posts for a single language code using WP_Query and WPML filters, specifically for the default language code 'en'. The provided code with the
and the custom function did not work, as it still retrieved posts in all languages.
Solution: We recommend using
'suppress_filters' => false
in the WP_Query arguments. This will ensure that the query retrieves posts in the current language when on the English version of the website. For further optimization, the client can specify the fields they want to retrieve, such as 'ID', 'post_title', and 'post_content'. For more information on debugging theme compatibility with WPML, please visit: Debugging theme compatibility with WPML. Additionally, for WPML hooks reference, check out: WPML hooks reference. For WordPress reference on get_posts, please see: WordPress get_posts function.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
