Available Solutions

Problem:
The client is trying to build a custom language switcher menu with custom flags and is experiencing issues with the flags being cropped and distorted in quality. Additionally, the client is inquiring about creating a combined language and currency switcher.
Solution:
To prevent WPML from resizing uploaded flag images, we recommend the following steps:
1. Access the root directory of your website and open the

file.
2. Insert the following line of code just before the "/* That's all, stop editing! Happy publishing. */" line:

3. Go to "WPML > Languages → Edit Language" and re-upload the flag image.
4. Save changes and clear any caches.
5. If necessary, adjust the flag size in "WPML > Languages > Custom Language Switcher → Customize".
Regarding the combined language and currency switcher, WPML does not have built-in functionality for this. It requires custom coding. If using WooCommerce Multilingual for multi-currency, set up currencies for each language as per the guide: Multi-currency support with WooCommerce.
Customize the language switcher by using hooks to change language names, which will also adjust the currency:

• WPML language switcher hook
• ICL LS languages hook

For custom coding, consider hiring a certified contractor from: WPML Contractors.

If this solution does not seem relevant, please open a new support ticket at WPML support forum.

Problem:
The client is experiencing issues with WP Job Manager where candidates' applications are not visible in Spanish and English, despite being visible before without translation. The client is seeking solutions to make them visible again without translating or duplicating the content and inquires about automatically duplicating job applications and resumes.
Solution:
To resolve the visibility issue without translating or duplicating content, we recommend setting resumes to display as translated by going to WPML → Settings > Post type translation, finding the resume post type, and setting it to 'Translatable – use translation if available or fallback to default language'.
There is no option to automatically duplicate content; however, there is an option to automatically translate content using the 'Translate everything' mode.

If this solution doesn't look relevant, please open a new support ticket at WPML support forum.

Problem:
If you're experiencing gibberish in the URLs of your translated pages from English to Chinese, such as

instead of a human-readable format, this is due to URL encoding, commonly known as percent-encoding.
Solution:
We recommend using the "Copy from original language if translation language uses encoded URLs" option. This will copy the original slug instead of using encoded URLs for the translated pages. You can find detailed steps on how to do this in our documentation:

• Translating Page Slugs

If this solution doesn't look relevant to your issue, please open a new support ticket and we will be happy to assist you further.

Problem:
The client changed the default language from English to French and is experiencing confusion because the WPML translation editor selection is now appearing when editing the French page, which is the new default language. For old content, the translation editor still appears on the English version, while for new content, it appears on the French version. The client wants to know how to fix this for the old content so that English is recognized as a translation of French and not the other way around.

Solution:
We explained that the behavior the client is experiencing is expected because pages and posts retain their original source language even after changing the default language. To resolve this, we recommended following a specific procedure that involves linking already translated pages. By doing so, the client will be prompted with a dialog to change the page's original language. We provided a link to the documentation for detailed steps:

• How to link already translated pages

We advised the client to review the documentation, apply the steps, and inform us of the results.

If this solution doesn't look relevant, please open a new support ticket.