Problem: You are trying to display posts on your blog page in the translated version of your site, but the blog page does not display the posts in the translated version. Solution: We found that the issue was due to certain admin strings being incorrectly translated. Specifically, the strings that caused the issue are:
[theme_mods_tripgo-child]blog_template
page_for_posts
[sidebars_widgets]
Please ensure these strings are not translated in the WPML String Translation section. If you're experiencing this issue, we recommend checking these strings.
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 problem persists, please open a new support ticket.
Problem: The client is experiencing an issue where the 'UPC #' field(it is created using 'Product Code for WooCommerce' plugin), previously known as 'SKU #', does not copy to the French translation of products. Solution: We recommended checking the translation preference for the 'Product Code' field in WPML>>Settings>>Custom Fields section. It should be set to 'Copy'. For more details, refer to our documentation on translating custom fields and view the image guide at custom field translation preferences
If the issue persists, we advised the client to set the translation preference for the '_product_code' field to 'Copy' after a site backup, update the existing products by making a minor change in the contents to refresh the translation settings, and then verify if the issue still exists.
If this solution does not resolve the issue or seems irrelevant due to updates or different circumstances, 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: You are using AHREFS to optimize your site and it has identified numerous hreflang problems, including 215 pages with missing reciprocal hreflang and 14 pages with hreflang leading to redirects or broken pages. Solution: We reviewed the reported issues and found that the pages do indeed have the necessary hreflang tags, including the 'x-default' tag. Additionally, the links that were reported to lead to broken pages or redirects were checked and all returned a 200 status, indicating they are functioning correctly. It appears that the issues reported by AHREFS might be false positives or outdated. You can verify the status of these links yourself using https://www.redirect-checker.org/index.php.
If this solution does not resolve your issue or seems irrelevant due to it being outdated or not applicable to your case, we recommend opening a new support ticket. We also 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, please contact us at our support forum.
Problem: You are experiencing an issue where the string translation on your site remains in the 'Translation in Progress' status. Solution: We recommend the following steps to resolve this issue: Navigate to WPML -> Translations. Here, you can take the job and continue translating strings using the Advanced Translation Editor.
Problem: The client is trying to translate a Woocommerce coupon on their website. Solution: We recommend not setting coupons as translatable because they are unique for each shop and not based on language. However, if you decide to translate them, you should go to WPML -> Settings -> Post Type Translation and change the coupons' translation preference.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also highly recommend checking related known issues here, 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 contact us directly through our support forum.
Problem: The client was unable to translate certain texts into Arabic, including the word 'SHOP' and phrases in the top bar of their website. Additionally, Arabic characters in the Slider Revolution were displaying backwards and separated. Solution: For the Slider Revolution issue, we recommended accessing WP Admin -> Slider Revolution and editing the 'Demo-rtl 1' slider used for Arabic. The client should remove the text layers and add them again without applying animation effects that break the words into individual letters. For the text in the top bar, which is managed by the 'Thim Elementor Kit' plugin (not WPML-compatible), we attempted standard methods to find the text through string translation but were unsuccessful. We offered to download a clone/snapshot of the website to further investigate how the plugin manages this text. For the image accordion issue, we made the fields translatable by adding custom XML configuration to the WPML settings. The client should open the page in the default language, make a minor edit to refresh the elements detected by WPML, and then proceed with the translation.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to remove all remnants of the RankMath plugin from your WPML translations after switching to Yoast, but despite deleting the plugin, its remnants still appear in WPML translations. Solution: The remnants of RankMath are still present in your database, which is why WPML continues to offer these fields for translation. To completely remove these remnants, follow the steps similar to those used for removing old custom fields from Yoast, which can be found in our forum discussion: https://wpml.org/forums/topic/split-how-can-i-remove-old-unused-custom-fields/ and https://wpml.org/forums/topic/delete-used-fields/. Make sure to search for 'Rank Math' fields specifically when prompted for the field name. It is crucial to create a backup of your database before proceeding with the removal.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem: After changing the default language from Italian to English on a bilingual website, the availability calendars stopped functioning. Solution: We recommend two potential solutions: 1) Modify the database: - Access your database manager, such as PhpMyAdmin. - Execute the following SQL query:
SELECT * FROM `wp_postmeta` WHERE `meta_key` LIKE '%room_type_id%'
- Replace the IDs as necessary based on your results. 2) Create new content in the English language: - Develop a new accommodation type for the English version. - Add accommodations and configure rates for this new type. You may need to remove the old Accommodation Types and Rates.
If these steps do not resolve your issue or if the solution 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 is using the 'WooCommerce Product Tabs' plugin and is unable to find the new string for product tab titles in WPML > String Translation. Additionally, many 'WooCommerce Product Tabs' strings are marked as 'pending with the hourglass' and are not appearing elsewhere. Solution: We recommend following these steps to resolve the issue: 1- Go to Products -> Product Tabs and access the trash (or click the link to your trash directory). 2- Delete the French product tabs. 3- Open the file .../wp-content/plugins/woocommerce-product-tabs/src/Product_Tabs.php. 4- Locate line 60 and replace the code:
5- Go to WPML > String Translation, enable the option 'look for strings while pages are rendered' at the bottom of the page, and visit a product with the tabs so WPML includes the new strings. 6- Go to WPML > String Translation, search for the tabs titles, and translate them.
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: You are trying to update the WPML plugin, but the WordPress updater shows an error message that the zip file is corrupt. Additionally, when attempting to download the plugin manually from your account, you receive an HTML file stating 'Error: you are not allowed to download this file'. Solution: 1. Temporarily remove your website here: https://wpml.org/account/sites/. This action won't affect your translation credits or translation memory but will force WPML to refresh the license status. 2. Add your website again and copy the newly generated key. Ensure you use the exact same format as shown in your wp-admin under Settings > General (e.g., http or https, www or non-www). 3. Navigate to Plugins -> Add New -> Commercial in your WordPress dashboard. 4. If visible, click on 'Unregister WPML'. 5. Click on 'Register WPML' and enter the new key. 6. Click on the 'Check for updates' button in the WPML section. 7. Select every plugin marked in red and click on 'Download' at the bottom of the grid. If these steps do not resolve the issue, our Systems can investigate to see if there could be an internal issue. If the solution provided here becomes irrelevant due to updates or does not apply 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 open a new support ticket at WPML support forum.
Problem: The client needs to set a transparent or semi-transparent background color for the language switcher button in WPML but found no documentation on how to achieve this. Solution: We recommend applying custom CSS to achieve the desired transparency effect. Here is the CSS code you can use:
Please test the changes on a staging site before applying them to your live site. If you need further assistance, consider hiring a professional from our contractors' page.
This solution might be 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 this does not resolve your issue, please open a new support ticket.
Problem: You are trying to set 'Set prices in other currencies manually' as the default choice on the product page for variations, but the WooCommerce Multilingual plugin defaults to 'Calculate prices in other currencies automatically', causing manually set prices to be ignored. Solution: Since there is no central feature in the WooCommerce Multilingual plugin to switch to the manual price option for variations, you need to use custom coding. Add the following code to the functions.php file of your theme to set 'Set prices in other currencies manually' as the default for new product variations:
function set_default_manual_currency_pricing($post_id) {<br /> if (get_post_type($post_id) === 'product_variation') {<br /> update_post_meta($post_id, '_wcml_custom_prices_status', '1');<br /> }<br />}<br />add_action('save_post', 'set_default_manual_currency_pricing', 20, 1);
To apply this change to existing product variations, add this code, run it once, and then remove or comment it out:
If you need further assistance with custom coding, consider hiring a professional developer. You can find one experienced in customizing WPML and its add-ons at https://wpml.org/contractors/.
Please note that 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 this does not resolve your issue, please open a new support ticket.
Problem: The client needs the ES menu links to point to the corresponding WPML-translated ES pages, but they are pointing to the EN pages instead. This issue is occurring in the ES Footer menu, and changes in the ES theme Appearance > Editor affect the EN pattern as well. The client wants to fix this issue and learn how to prevent it in the future. Solution: 1. Delete the existing header and footer navigation menus and templates. 2. Create new navigation menus and templates in the primary language. 3. Use WPML Translation Management to create second language instances of these menus and templates. 4. Switch to the second language in the WP Admin console. 5. Open the second language instances of each element via Appearance > Editor > Template etc. 6. Remove each page link from the second language navigation menu, and replace it with a link to the corresponding page in the second language. This process ensures that both the primary and second language navigation menus have the correct labels and page links. Additionally, ensure you have translated your Menu template from WPML > Translation Management.
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. If further assistance is needed, please open a new support ticket.
Problem:
I am working on a site under development and trying to translate internal link of the button using WPML, but the internal links do not show up in the Advanced Translation page.
If you need to translate the slug of the page itself, use these steps: 1) Activate the option "Translate (this will include the slug in the translation and not create it automatically from the title)" in WPML → Settings → Translated documents options. 2) Then, edit the page. Make a minor modification to the page, save it, and navigate to the WPML translation editor. The slug will be added to the translation. Translate or change it and save it.
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 this does not resolve your issue, please open a new support ticket.
Problem: The client is unable to approve translation reviews on the translations queue page due to a console error: TypeError: Failed to construct 'URL': Invalid URL. Additionally, there were issues with the WordPress memory limit settings. Solution: We recommended the client to perform a conflict test by: 1. Setting a default WordPress theme. 2. Keeping only WPML Plugins and essential plugins active. 3. Disabling all other plugins. This step helps in identifying if there's any theme or plugin conflict. We also advised ensuring a full backup before making any changes. Furthermore, we noticed that the WordPress Memory Limit was below the minimum requirement for WPML. We suggested increasing the memory limit by adding the following code in the wp-config.php file:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 open a new support ticket at WPML support forum.
Esta página incluye los tickets de soporte resueltos y documentados. ¿Buscas tickets que estén «en curso»? Visita el archivo completo de tickets de soporte
