Problem: The client is experiencing an issue where the main language is Latvian, and while translating forms into English and Russian using WPML, the Gravity Form is being overwritten to English. Solution: We recommend the following steps to resolve this issue: 1. Edit the file at
3. Update the form and try to reproduce the issue.
If this solution does not resolve your issue or seems irrelevant due to being 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 at WPML support forum.
Problem:
The client was experiencing two issues on the WooCommerce checkout page with WPML:
1) The product title on the order-pay endpoint page was not translating to the current page language but remained in the language the order was made in.
2) On the order-received page, the permalink slug for certain variable products with multiple attributes was in the wrong language.
Solution:
We recommended the following steps:
1) Go to WooCommerce > WooCommerce Multilingual > Status and complete any missing steps.
2) Navigate to WooCommerce > WooCommerce Multilingual > Store URLs and ensure that:
- Slugs are unique and not repeated across translations.
- Translations do not have the same slug as the original language.
If these steps are completed and the issue persists, we provided a code snippet to temporarily change the order language to English, retrieve the product information, and then revert the language back to the original. The client should add this snippet to their functions.php file. (fond here: https://wpml.org/forums/topic/woocommerce-product-title-etc-on-pay-order-checkout-page-in-wrong-language/page/2/#post-10513689 )
Please note that this solution might be 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. If necessary, please open a new support ticket with us."}
Problem: 1) The client is experiencing an issue with joining segments in translations, which requires redoing the joins every time an edit is made in the original language. 2) The client wants to preserve the URL slug in the original language for translations, but the slug is being automatically generated based on the translated title.
Solution: 1) We acknowledge the inconvenience caused by the joining segments issue and confirm that our development team is currently working on a solution. 2) To ensure the URL slug is copied from the original language, please follow these steps: - Go to WPML -> Settings -> Translated documents options -> Page URL - Select
1
Copyfrom original language iftranslation language uses encoded URLs
- Navigate to WPML -> Languages -> Edit languages - Set
1
Encode URLs
to
1
Yes
- Test this configuration by creating a new page and translating it to see if the issue is resolved.
Please note that the solution provided might be irrelevant due to being 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 do not hesitate to open a new support ticket. You can reach out to us through the WPML support forum.
Problem:
If you're experiencing an issue where an Elementor button points to a page and does not switch to the respective language when changing languages, staying directed at the default English language instead.
Solution:
First, ensure that the template containing the button is translated. Follow these steps:
1. Navigate to Templates -> All -> Header in your WordPress dashboard.
2. Use the translation editor to translate the header template.
After translating the header template, the button should correctly point to the translated post. For further guidance, we recommend checking our guide on translating Elementor templates.
If the button still does not work correctly after these steps, or if you encounter additional issues such as with the query loop, we suggest opening a new support ticket for each separate issue.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. We highly recommend checking related known issues on the WPML known issues page, 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.
If these steps do not resolve your issue, or if the solution 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problema: El cliente tenía problemas con la descripción de productos que no aparecían traducidos en el idioma secundario. Solución: 1. Pedimos al cliente que actualizara todos los plugins y temas desactualizados para evitar conflictos en el código. 2. Tradujimos dos cadenas de texto específicas y pedimos al cliente que confirmara si el problema se había resuelto. 3. Actualizamos la traducción al 100% de un producto y sugerimos al cliente que hiciera lo mismo con otro producto como prueba, asegurándose de descartar la traducción en la sección de traducción de cadenas por el momento.
Si estás experimentando este mismo problema, te recomendamos que sigas los pasos anteriores. Sin embargo, la solución podría no ser relevante para tu caso si es obsoleta o no aplicable. En ese caso, te sugerimos abrir un nuevo ticket de soporte. También recomendamos encarecidamente revisar los problemas conocidos, 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: You are trying to list all of your pages and posts that have not been translated from English using SQL. Solution: We recommend referring to our documentation on WPML tables and language information: WPML Tables Documentation. To find posts that have not been translated, you can use the following SQL code:
1
SELECT *<br />FROM wp_icl_translations<br />WHERE trid IN (SELECT trid<br />FROM wp_icl_translations GROUP BY trid having count(trid) = 1)
If you need to filter by a specific post type, such as 'Pages', modify the SQL like this:
1
SELECT *<br />FROM wp_icl_translations<br />WHERE trid IN (SELECT trid<br />FROM wp_icl_translations GROUP BY trid having count(trid) = 1) andelement_type LIKE 'post_page'
Remember to prefix the post type with 'post_'.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML 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: The client was unable to save translations for custom post type slugs created with JetEngine when using WPML. After setting the slugs for languages and saving, the page would refresh and the fields would remain empty. Solution: We discovered that the Redis Object Cache Plugin was preventing the settings from being saved. We recommend disabling the Redis Object Cache Plugin temporarily to save the settings. We have now translated the slugs for the client, and the translations are functioning correctly. If the client continues to experience issues, we suggest disabling the Redis Object Cache Plugin momentarily to adjust the settings. Additionally, we offered to set up a test site to further investigate the issue and asked the client to provide the latest version of the JetEngine plugins for this purpose.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client noticed an unexpected x-default tag on their pages and wondered if it was due to a recent WPML plugin version upgrade. They asked if there was a way to deactivate it through the plugin interface or if there was a hook available for controlling it programmatically. Solution: We confirmed that the x-default tag was indeed automatically added in the WPML version 4.5.0 and that there is no built-in option in the WPML interface to switch it on or off. However, we provided a custom hook that can be used to control the x-default tag. Here is the code that the client can use:
This code should be added to the theme's functions.php file or a custom plugin to remove the x-default tag.
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 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 open a new support ticket.
Solution:
Yes, in order to enable this language URL format, it's necessary that all domains have the SSL certificate. If you check the "What you will need" section on the documentation that you mentioned, you'll see that the last item is:
- You should have an SSL certificate for each site translation, or one multi-domain SSL certificate.
Problem: The client is using the Kadence theme with WooCommerce and has encountered an issue where a Kadence element that was translated into German disappeared from the product page. However, the element appears in the original language on the Italian product page, which has not been translated.
Solution: We recommend the following steps to resolve the issue:
Create the Kadence element and in the Language section, uncheck the
1
'Use WPML's Translation Editor'
option.
Check the
1
'Duplicate'
option checkbox.
Press the
1
'Duplicate'
button.
Edit the duplicated translation and press the
1
'Translate independently'
option to release the translation from being a duplication of the original element. You can find more details in our guide on manually translating a page or a post at this link.
Edit the original element again and reactivate the
1
'Use WPML's Translation Editor'
option to make the Advanced Translation Editor active again for translating the element.
Translate the element with the Advanced Translation Editor and complete the translation.
Repeat steps 1-6 for the product to which the element is assigned.
After following these steps, the translated element should display on the translated product page.
**** Important! Please make a full site backup (files and DB) before you proceed with those steps**** If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us here.
Problem: The client is unable to edit French pages on their website. Solution: We recommend translating Cornerstone content using the WPML Translation Editor. Follow these steps: 1) Always translate from the original content language to the second language using the WPML Translation Editor. 2) If a post was created in English, translate it to French using the WPML Translation Editor. Any changes in the English version will require an update to the translation. 3) If translations were created directly in Cornerstone, disable the WPML Translation Editor for this content. This option is available on the original content inside the right sidebar of the WordPress Editor.
It's crucial to disable the WPML Translation Editor for content manually translated in Cornerstone to prevent overwriting.
If you need to edit the English version manually: - Determine why manual edits are necessary. - Identify if there are issues with content translation or if translations are not appearing on the front end. - Narrow down the issue to a specific Cornerstone Widget, if possible.
If the content was manually created in Cornerstone, disable the WPML Translation Editor on the French page and try editing the English version again manually. Do not apply current translations in the WPML Translation Editor as they could overwrite your content.
Additionally, if you're working directly in Cornerstone, ensure you set the content language correctly in Cornerstone's bottom right corner. Mixing translations from Cornerstone and the WPML Translation Editor is not recommended; choose one method and stick with it.
Problem:
We are trying to set up a user role for translators on our site that gives them the permissions to edit and translate the content, but not to access plugins and theme options.
Solution:
Just add this code to the functions.php file:
Problem: The client is using WPML with Advanced Custom Fields (ACF) and the Advanced Custom Fields Multilingual plugin. Automatic translation adds content to WordPress, but the frontend does not display the translated content unless the client updates the page manually by clicking the "Update" button.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
쿠키 동의 관리하기
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
