Available Solutions

Problem:
The client wants to shorten the language names in the default language switcher to display as 'EN' for English and 'FR' for French instead of the full language names.
Solution:
We recommend creating a full backup of your website first. Then, navigate to WPML > Languages > Edit Languages. Here, you can edit the values in the "Translation" column by replacing the full language name with the language code (e.g., 'EN' for English, 'FR' for French).

Please be aware that these changes will affect all the language switchers on your site.

If this solution doesn't look relevant to your issue, please open a new support ticket with us.

Problem:
The client is trying to display the language selector in the mobile menu of their DIVI theme website in one line, instead of stacked vertically like the other menu items.

Solution:
We attempted to resolve the issue with custom CSS code. However, due to a significant amount of custom coding from the theme or one of the active plugins, the default WPML CSS properties were being overwritten, preventing the language selector from aligning horizontally in the mobile menu. We provided the following custom CSS code, but it did not achieve the desired result:

Since the custom CSS did not resolve the issue, we recommend hiring a front-end developer or a WPML contractor to perform the necessary custom work. Our colleagues also confirmed that custom work is required due to interference from other custom codes.

If this solution does not seem relevant to your situation, please open a new support ticket with us.

Problem:
The client is trying to auto-detect user location and show pricing accordingly using WooCommerce's GeoLocate. They are also using WP Rocket for caching. The issue is that the home page shows incorrect currencies, and only after some hard refreshes does it show the correct currency.
Solution:
1. We asked the client to provide debug information by following this documentation: https://wpml.org/faq/provide-debug-information-faster-support/.
2. We recommended testing the feature without WP Rocket by clearing the WP Rocket cache and deactivating it, then clearing the browser cache and testing the result.
3. We reminded the client that WooCommerce Multilingual only supports MaxMind Geolocation and that they need to acquire the proper key, as detailed in our documentation: https://wpml.org/documentation/related-projects/woocommerce-multilingual/multi-currency-support-woocommerce/#currencies-per-location.
4. The client found a solution by using a WP Rocket extension that handles cookies with high accuracy, which resolved the issue: https://docs.wp-rocket.me/article/1313-create-different-cache-files-with-dynamic-and-mandatory-cookies#helper-plugin.

If this solution doesn't look relevant to your issue, please open a new support ticket here: WPML Support Forum.

Problem:
The client is receiving a message indicating a problem with the String Translation table that could become critical in the future.
Solution:
First, we recommend making a full backup of your site. Next, follow the workaround provided in the WPML errata page.
Then, remove the option

from the options table in your database (typically named wp_options, where "wp_" is your database prefix).
After completing these steps, verify that your database contains all the following tables with the correct prefix ("wp_" by default):

• icl_strings
• icl_string_translations
• icl_string_packages
• icl_string_pages
• icl_string_positions
• icl_string_status

If you have followed these steps and the issue persists, or if this solution does not seem relevant to your problem, please open a new support ticket with us.