Problem: The client needs assistance making the Divi module link URL translatable or linking to its translated pages. The URL does not appear in the WPML Advanced Translation Editor, and there is no option to automatically translate or sync it to its translated page. Solution: If you're experiencing this issue, we recommend searching and translating the link as explained in the following documentation: Translating Links with Advanced Translation Editor. For links to be automatically adjusted to translated ones, they need to be full HTTPS links, and the Divi modules need to be compatible. If you are using third-party Divi modules, they might require additional XML configuration. Please check the following documentation for maintaining Divi Builder compatibility with WPML: Maintaining Divi Builder Compatibility with WPML.
Ultimately, customer was able to fix it by enabling the option "Make themes work multilingual" in WPML -> Languages
Problem: The client is experiencing an error screen when a specific admin tries to log in, which is suspected to be caused by the WPML plugin. Solution: We recommend checking if the affected admin user has their name, surname, and email correctly set up in their wp-admin profile page. Additionally, log in with a different admin account and navigate to WPML -> Translation Management > Translators. Here, verify if the problematic user is set up as a translator and ensure they have at least one language pair assigned.
If this solution does not resolve the 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 at WPML support forum for further assistance.
Problem: The client needs assistance with disabling the 'pay as you go' option and removing credit card information from WPML. Solution: If you're experiencing this, we recommend you follow these steps to disable the 'pay as you go' subscription: 1. Navigate to WPML → Translation Management. 2. Click on the Tools tab. 3. In the Pay-as-you-go account details section, click the 'Stop using pay-as-you-go' link. You will receive a final bill for any credits used since your last invoice. Since WPML does not store your credit card information, disabling 'pay as you go' will also remove this information. Payments are processed securely via Stripe.
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 at WPML support forum.
Problem:
I am trying to translate theme strings, but I can't register any. It doesn't matter if I try to do it with function like do_action( 'wpml_register_single_string', 'stegu', 'enter_search_terms', 'Enter search terms' ); or simply using __ . Also, options text fields page from ACF options page can't be translated (it works for acf fields in posts or pages). Link to a page where the issue can be seen: https://test.stegu.pl/
Solution:
For some reasons some of icl tables had positions with id 0. after removing them all works as a charm.
Problem: The client is experiencing an issue with WooCommerce email translations not being correctly applied to custom texts in customer emails. The emails are being sent in the default Greek language instead of the translated language, despite the strings being scanned and translated. Solution: We recommend isolating the issue by moving the custom code related to email translations to a different section of the theme, such as
header.php
, to verify its functionality. Since our support policy does not cover assistance with custom coding, we suggest setting up an isolated test environment. This will allow us to review the code without affecting the live site. If the problem persists, please check our related known issues and ensure you have the latest versions of themes and plugins installed.
If this solution does not resolve the issue or seems outdated, we highly recommend opening a new support ticket. You can do so here: WPML support forum.
Problem: If you're trying to install WPML on a new site and encounter the error 'not allowed to view this page' at step 7, it's likely a permissions issue. Solution: We recommend following these steps to resolve the issue: 1. Create a full website backup. 2. Disable all plugins except for WPML and its add-ons. 3. Check if the issue persists. 4. If the issue does not reoccur, reactivate your plugins one by one to identify the problematic plugin. 5. If the issue persists even with non-WPML plugins disabled: - Keep all non-WPML plugins deactivated. - Switch to a default theme, such as TwentySeventeen. - Attempt to recreate the issue. It is advisable to perform these steps in a staging environment if possible.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: You need help translating text in the cart shipping section of your website using WPML. Solution: To translate strings effectively, it depends on how they are implemented in your theme or plugin. Try the following methods: Method 1: Navigate to WPML > String Translation. At the bottom of the page, check the box labeled "Look for strings while pages are rendered". After enabling this, visit the front end of your site where the string appears, then return to WPML > String Translation and search for the string. Method 2: If the string is not found in WPML > String Translation, it might be categorized as an admin text string. Follow the process outlined here to find and translate admin text strings: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also advise 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: You are experiencing an issue where products are not showing in a category when using the English language. Solution: This issue has already been reported and is currently being addressed in an existing support ticket. We recommend that you follow the progress and updates in the original ticket. Please avoid opening multiple tickets for the same issue as it can affect the priority and handling of your case. You can check the status of the existing ticket here: https://wpml.org/forums/topic/im-faceing-an-issue-products-not-showing-on-category. Additionally, if this solution becomes irrelevant due to updates or if it does not apply 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 you still need assistance, please open a new support ticket.
Problem: The client lost previous translations for WooCommerce products after updating them in the WPML translation editor. Specifically, the issue occurred after editing the original product and updating the translation. Solution: 1. Check Translation Revisions: Look for previous versions in WPML > Translation Management > Jobs. 2. Re-sync Translations: Please take a look here: https://wpml.org/forums/topic/sync-resave-all-products-translations/ 3. Restore from Backup: If you have a site backup, consider restoring from it. Alternatively, resend the content for translation to potentially simplify the recovery process. We have compensated for the lost translations by adding additional credits to your account.
If this solution does not resolve your issue or seems outdated, we 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.
Problema: Se você está enfrentando problemas com o WPML Advanced Translation Editor, onde os termos do glossário não estão sendo aplicados corretamente nas traduções automáticas, mesmo após defini-los antes de iniciar novas traduções. Solução: Os termos do glossário são sensíveis a maiúsculas e minúsculas. Certifique-se de que a 'caixa' ou 'case' das palavras esteja correta ao definir os termos no glossário. Além disso, estamos desenvolvendo um recurso para substituir os termos do glossário em traduções já existentes, que provavelmente estará disponível na próxima versão. Se você precisar de mais assistência, recomendamos que faça um backup completo do seu site antes de fornecer informações de acesso para suporte. Para mais informações sobre privacidade e segurança ao fornecer informações de debug, visite https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/.
Se esta solução não for relevante para o seu caso, porque pode estar desatualizada ou não se aplicar, sugerimos que abra um novo ticket de suporte. Recomendamos também verificar problemas conhecidos em https://wpml.org/known-issues/, verificar a versão do fix permanente e confirmar que você instalou as versões mais recentes de temas e plugins.
Problem: The client is experiencing issues with WPML on their site. Specifically, the translated values of custom fields are not showing in the default WordPress editor, despite being set to translate in the settings. Additionally, shortcodes registered in WPML > Settings > Custom XML Configuration are not automatically translated. Solution: For the issue with custom fields not displaying in the default WordPress editor, we recommend checking our documentation on enabling text translation for themes not compatible with WPML, which can be found here: https://wpml.org/documentation/support/enabling-text-translation-for-themes-not-compatible-with-wpml/. Regarding the shortcodes not being automatically translated, it's important to note that our technical support primarily covers default WPML functionalities and not custom code. If these solutions do not resolve the issues or if the documentation does not cover your specific case, we highly recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
Problem: You are trying to translate pages from English to Arabic and encountering an issue with approving translations for the post 'My Members'. Solution: We recommend you navigate to your WordPress Dashboard, then go to WPML > Support > Troubleshooting. Here, click the Remove ghost entries from the translation tables button. After this, please re-send the page for translation.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: When using the Vikrentcar plugin with WPML on your site, the language automatically changes during the ordering process at step 3. Solution: To address this issue, you need to modify the code in the Vikrentcar plugin. Follow these steps: 1. Open the file at
around line 192. 3. Replace the existing code snippet within the function with the following code:
if ($post_id) {<br /> // WPML Workaround for compsupp-7493<br /> $post_id = apply_filters('wpml_object_id', $post_id, get_post_type($post_id), TRUE);<br /> $wpml_post_lang = apply_filters('wpml_post_language_details', null, $post_id);<br /> if ($wpml_post_lang) {<br /> // WPML supported, go ahead<br /> return apply_filters('wpml_permalink', get_permalink($post_id), $wpml_post_lang['language_code']);<br /> }<br /> // WPML not supported, fallback to the default behavior<br /> return get_permalink($post_id);<br />}
Please note that this is a temporary workaround. We recommend contacting the Vikrentcar plugin developer for a permanent solution.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: The client is experiencing slow website and backend speeds, suspecting that WPML and its translated content might be causing conflicts or using excessive processing/data/storage space. Additionally, there is concern about a large error log related to WPML. Solution: We reviewed the wp-config.php file via FTP and confirmed that the debug.log was enabled but did not show any serious issues with WPML. To prevent the file from growing and potentially causing storage problems, we deactivated the debug.log. We also clarified that the link provided by the client (https://revoltbikes.nl/wp-admin/admin.php?page=sitepress-multilingual-cms%2Fmenu%2Fdebug-information.php) is not an error log but a debug information page useful for our support team. After checking the site's frontend and backend, we did not observe any significant performance issues. We recommend the client specify where the performance issue is noticeable and why WPML is suspected to be the cause for further assistance.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: As administrators, you are unable to create new translations or access existing ones in WordPress, receiving a '403 Forbidden' error. This issue persists even after resetting the plugin and coincides with a recent update to 'Better Docs'. Solution: We recommend increasing the WordPress memory limit. You can do this by adding the following lines to your wp-config.php file:
define('WP_MEMORY_LIMIT', '1024M');
define('WP_MAX_MEMORY_LIMIT', '1024M');
This adjustment has resolved similar issues in the past.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at the WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
