Problem: The client needed to implement a language switcher with specific styling requirements, including inserting a "/" between languages and styling the selected language in a different color. Solution: We recommended using CSS to achieve the desired styling. To add a "/" between language switcher items, custom CSS can be applied. For styling the current language, the client can use the following CSS code:
.wpml-ls-item.wpml-ls-current-language a span {
color: #d00 !important;
}
If this solution does not apply or is outdated, or if you have a different issue, 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 in our forum: WPML support forum.
Problem: The client was unable to proceed with the configuration wizard of the "WooCommerce Multilingual & Multicurrency" plugin as there was no button or link to continue the process. Solution: 1. We recommended that the client temporarily deactivate all plugins except for WPML, WooCommerce, and WooCommerce Multilingual to check if there is a conflict with another plugin. 2. We instructed the client to back up their database before making any changes. 3. We asked the client to provide us with debug information by following the instructions on our documentation page: http://wpml.org/faq/provide-debug-information-faster-support/.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, we encourage you to open 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. If you need further assistance, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing issues with saving and creating multi-language products with several hundred variations, which was taking a long time to complete. Solution: 1. We confirmed that the issue had been tested on a site clone and the changes were working. 2. We instructed the client to edit a specific file by navigating to "Plugins -> Plugin Editor" and overwriting the mentioned code lines, emphasizing the importance of making a backup before making any changes. 3. We informed the client that we could not provide an ETA for the release that includes these changes, as the priority might be lower due to the lack of similar reports from other clients. 4. We updated the files on the client's site and asked the client to try saving the product again, noting that it should now take around 30 seconds without getting "stuck".
If you're experiencing a similar issue, we recommend you try the steps mentioned above. However, please be aware that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related 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 with us.
Problem: The client is seeing a message stating 'WPML detected a new address for this site' despite not having changed anything in the last three years. Additionally, the WPML editor is no longer available in their pages, products, etc. Solution: If you're experiencing a similar issue where you see a message about WPML detecting a new address for your site, and you find that the WPML editor is missing from your pages and products, we recommend the following steps: 1. Go to WPML > Settings > Translation Editor. 2. Here, you can switch back to using the Classic Translation Editor if you prefer it over the Advanced Translation Editor. For a guide on how to switch editors, please visit the following documentation: Translation Editor Options.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking the related 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 do not hesitate to open a new support ticket. You can reach out to us on the WPML support forum.
Problem: The client wanted to know if it's possible for the main language (Armenian) to show its language code 'hy' in the URL slug, similar to how the Russian version shows 'ru'.
Solution: We recommended adding PHP code to the client's theme to redirect the root domain to the directory of the default language. Here are the steps: 1. Create a PHP template file for the site's theme, preferably in a child theme. 2. Add the following PHP code to the new template file:
3. Edit the root page and select the newly created template from the Summary section in the right sidebar. 4. Update the page to ensure the root page now redirects to the default language directory.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket with us.
Problem: The client reported an issue where the header and footer were not displaying on a specific page of their site when changing the language to English or Italian. The page was created with WP editor, and they were using the Elementor Header & Footer Builder plugin with the 'Post Types Translation' option in WPML set to 'Translatable'. No translations for the header and footer were available in Elementor Header & Footer Builder, and creating translations resulted in the header and footer showing twice on all pages except the problematic one.
Solution: We recommended the following steps: 1. Ensure that all Elementor templates are translated. For guidance, see how to translate Elementor templates. 2. Follow the solution provided in a related support forum post: Help with Elementor Header & Footer. 3. Increase the WordPress memory limit to meet WPML's minimum requirements by adding the following code to the wp-config.php file:
If these steps do not resolve the issue, we asked the client to provide detailed steps on how they created and translated the header, and how they are adding the menu on the rest of the pages.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client was experiencing a 404 error when trying to access the Italian translation of the BuddyPress members page. The expected Italian page was not found, but a version with an untranslated title was accessible at a different URL. The issue was not present in the development version of the site.
Solution: We identified that the slugs were not translated, which likely caused the 404 error on the Italian members page. Additionally, we mentioned that a low memory limit could contribute to the site not functioning as expected. If you're experiencing this, we recommend translating the slugs for the BuddyPress pages and ensuring that your site has an adequate memory limit.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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.
Problem: The client was unable to change the site URL in their WPML account due to a 'Site key not matching' error after migrating their website from one URL to another.
Solution:
Upon investigation by our team, we found that the client started as an end user account by taking ownership of the website. And then acquired a Blog account.
We removed the end user link from our side and now the client is able to use their Blog account by following these steps:
- Go to the Account > Sites page after login to the respective wpml.org account.
- Remove the previous site registration.
- Add a new one generating a new site key that should be used on the site.
If you still need assistance, we highly recommend opening a new support ticket in the WPML support forum.
Problem: The client has translated their categories but the URLs are not translated as desired. The issue is that the translated category slugs are appending a language code at the end, which the client wants to remove.
Solution: We explained that WordPress requires each taxonomy term's slug to be globally unique, which means one taxonomy term cannot have a matching slug with another taxonomy term across all taxonomies. To allow for duplicate slugs in different languages, we recommended checking out a post that provides a solution for allowing duplicate taxonomy slugs in WordPress. Here is the link to the post: https://stackoverflow.com/questions/12806409/allow-duplicate-taxonomy-slugs-wordpress
Please note that the solution provided might be outdated or not applicable to your case. If after checking the known issues and confirming that you have the latest versions of themes and plugins installed, the problem persists, we highly recommend opening a new support ticket. For further assistance, please visit our support forum.
Problem: The client needed assistance with aligning text to the right for the Dhivehi language, which is read from right to left. They also encountered issues with phone numbers, email addresses, and punctuation marks appearing reversed in the translation editor. Solution: We recommended checking the theme's CSS rules for RTL (right-to-left) content display, as WPML does not control the RTL layout. For custom languages, we advised following this guide to add RTL support: https://wpml.org/documentation/getting-started-guide/language-setup/editing-wpmls-languages-table/#adding-rtl-right-to-left-support-to-a-custom-language If the issue persists, we suggested using custom CSS with the ":lang()" selector to set the text direction to RTL. For more details, we provided external documentation links:
For the translation editor, we instructed the client to: - Go to WPML > Languages > Edit Languages - Map the language to the closest RTL language - Save the changes
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you need further assistance, please open a new support ticket at our support forum.
Problem: The client is experiencing performance issues with WPML on their e-commerce site, particularly when WPML plugins are activated, resulting in increased load times.
Solution: We suggested checking if the auto_adjust_ids setting under WPML > Languages > Make themes work multilingual is enabled, as this can impact performance, and if so disabling it.
We advised that debugging tools like Query Monitor should be disabled after testing, as they can also affect performance.
For a more complete checklist of steps you can take to improve performance, visit this ticket/.
Es posible que esta solución sea irrelevante si está desactualizada o no se aplica a tu caso. Si después de seguir estos pasos el problema persiste, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins. Si necesitas asistencia adicional, por favor, contacta con nosotros en el foro de soporte de WPML.
Problem: The client was experiencing an issue where the WooCommerce Subtotal was showing in English as "Subtotal" instead of the expected Traditional Chinese "小計" when WPML String Translation was activated. Additionally, the "Free Shipping" text on the Cart page was not translating correctly after performing the "Theme and plugins localization" with WPML.
Solution: For the Subtotal issue: 1. Edit the "cart" page in Chinese. 2. Click on the three-striped icon to view the different blocks on the page. 3. Select the "empty cart" block to reveal its contents. 4. Manually translate the text within the block. 5. Save the changes.
For the Free Shipping issue: 1. Go to WooCommerce > Settings > Shipping. 2. Edit the label for the free shipping to something unique. 3. Search for the new label in WPML's String Translation. 4. Translate the label and save the changes.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we recommend opening a new support ticket. We also highly recommend checking related 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 reach out to us on the WPML support forum.
Problem: The client needed to keep the main menus in English while having the menus in the widget area translated into the language of the page. Solution: We recommend manually creating or adjusting the menus in the second language to fit your needs. Although WPML automatically translates pages and their menus, you can control the translation of your menus by following these steps: 1. Go to the WordPress menu section. 2. Create or edit the menus for the second language as desired. For detailed instructions on how to translate menus manually, please visit our documentation: Translating Menus Manually.
Please note that this solution might not apply to your case if it's outdated or not relevant to your specific situation. If this is the case, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please don't hesitate to open a new support ticket in our support forum.
Problem: The client is experiencing an issue where Dynamic Rules for hiding/showing content in Elementor and Anywhere Elementor Templates are not translating correctly after translating a French site into English. Specifically, flags next to product names are not appearing on the English version of the site.
Solution: We recommend the following steps to resolve the issue: 1. Navigate to the
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
