Problem: You are unable to change the language flag icon to a custom SVG, PNG, or any other type of icon, and it is showing as a broken link. Solution: We recommend checking the file name of the flag image you are uploading. If the file name is long or contains special characters, try renaming it to something simpler, such as
flag_us.png
. After renaming, test to see if the issue is resolved. If you still experience problems, please try the following steps: 1. Use an even shorter file name. 2. Ensure the image size does not exceed 32×32 pixels. 3. Make sure the file name contains only lowercase letters, numbers, and underscores (no spaces or special characters).
If these steps do not resolve the issue, the 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
The client is facing an issue where slugs for French, Spanish, and Portuguese pages are being translated instead of being copied from the original English slug, despite enabling the 'Copy from original language if translation language uses encoded URLs' setting in WPML. This setting worked for Arabic but not for other languages.
Solution:
We recommend trying the following steps after ensuring you have a full site backup:
1) Navigate to WPML >> Languages >> Site Languages. 2) Click on the Edit Languages link. 3) In the table that appears, locate the "Encode URLs" column. 4) Set "Encode URLs" to "Yes" for all secondary languages, but leave the main language unchanged. 5) Click Save and clear all types of caches. 6) Test the setting by translating a new page to see if the slugs are copied correctly.
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 the problem persists, please open a new support ticket.
Problem: The client was experiencing issues with WPML's auto-translate functionality where URLs were not correctly translated to reflect the new language, and certain English keywords were being automatically translated when they needed to remain untranslated.
Solution: 1. To ensure URLs are correctly translated, we recommended following the steps in our guide on translating page slugs, which can be found here: Translating Page Slugs Guide. 2. To prevent specific English keywords from being translated, we advised adding them as terms in the Glossary. Detailed instructions are available here: How to Create and Manage Glossary Entries. 3. For issues with untranslated elements in Elementor, we provided an XML configuration to register the necessary widgets and fields. This involved adding custom XML code under WPML -> Settings -> Custom XML Configuration tab.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: You are trying to translate pages using WPML, but the translation editor is not loading and keeps loading indefinitely. Solution: We recommend that you test the translation editor again to see if it is now functioning properly. 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 open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to translate the specification tab and custom tabs on your website using the Elessi theme, but the translations are not displaying. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML-> Settings-> Custom Fields Translation section. 2. Set the following custom fields to 'Copy': -
_nasa_ct_tabs
-
_custom_tab_content
3. Set the 'wc_productdata_options' field to 'Translate'. 4. Click 'Save'. 5. Edit the product in English. 6. Make a minor edit and update it. 7. Update the translation using the WPML translation editor.
Please note that the specifications themselves need to be translated in the translation editor if they haven't been translated yet.
This solution might be irrelevant if it's outdated or not applicable 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. If the issue persists, please open a new support ticket.
Problem: The client is facing an issue where, after a recent update, most of the Arabic translations in their WooCommerce store are not showing, despite being previously translated. They are concerned about the persistence of translations after updates and how to recover missing translations. Solution: 1. Navigate to WPML > String translation to ensure all strings are translated. 2. Open the theme's functions.php file and locate line 53. 3. Replace the existing code:
unload_textdomain('elessi-theme');
with:
unload_textdomain('elessi-theme', true);
This change should resolve the issue with missing translations. If some strings are still not reflected, it's recommended to check if they are translated in WPML. For ongoing issues, consider contacting us directly via chat for quicker resolution. Note: The current fix is a workaround due to a bug in the new WordPress version. You might need to reapply this fix after future theme updates until a permanent solution is implemented by the theme author. Stay updated on this issue by following the related errata: WPML Errata.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. 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, you can also visit our support forum at WPML Support Forum.
Problem: The client needs to migrate 145 Arabic translations of blog posts and link them to the corresponding English posts on a newly developed website. The client tried following tutorials and videos but faced many complications. Solution: We recommend the following steps to simplify the migration process: 1. Backup your site or save an XML copy of the posts. 2. Delete the English posts and categories from the new site, as the content was imported independently, which might have broken the language connections. 3. Ensure the WPML Import/Export plugin is installed on the old site. 4. Export all posts from the old site. 5. Import all posts into the new site. 6. Run the WPML import/export settings to establish the correct language connections. 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 further assistance is needed, please open a new support ticket at WPML support forum.
