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.
Problem:
When I enable WooCommerce Stripe Gateway, there are no Stripe settings. I can’t change anything in the settings, I always get the “Error Saving settings”.
Solution:
Go to wp-content/plugins/woocommerce-multilingual/classes/Rest and edit the Functions.php file. Here, just change this line:
Problem: The client is trying to register WPML on a local development site without an external URL using a dev site license. Solution: We recommend registering WPML using the local URL of the site, ensuring to include the complete URL, such as
1
http://localhost/wpml-test
or
1
http://wpmltest.local
It's important to include "http://" in the URL. If there are issues obtaining updates, the client can download the latest versions of our plugins from our downloads page. Please note that the Multilingual CMS account allows the registration of up to 3 websites, which typically includes one development and one production site per website. If the client needs further assistance, we suggest checking related known issues, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the solution provided here is outdated or not applicable, please open a new support ticket on our support forum.
Problem: The client is experiencing an issue where switching to a non-default language on their online courses website results in incorrect URLs for the courses. Additionally, the client is unable to find certain strings for translation in the WPML String Translation section.
Solution: For the URL issue, we recommended checking the theme's documentation regarding WPML compatibility, which states that languages by parameters are not supported. We advised the client to change the URL format to 'directories' in WPML > Languages > Language URL format and then resave the permalinks.
If the provided solution does not resolve the 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 in our forum: https://wpml.org/forums/forum/english-support/
Problem:
The admin string shows as Registered and locked, how can we enable it's translation?
Solution:
“Registered and locked” means that the string is already registered by the theme or via an XML configuration file. They should appear on the WPML >> String Translation page so that you can translate them.
Problem: The client is experiencing an issue with an invalid site key error and their URL has been blocked due to a high number of requests to the server.
Solution: We recommend updating all functionalities of the site to the latest versions. Once this is done, inform us so that our system specialists can proceed with unblocking the URL. The blockage is due to the high number of requests which can be mitigated by updating the site. It is important to communicate with the client to get approval for these updates. If the site remains blocked, some functionalities of WPML may not work as expected.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem:
After restoring a backup, the following error appears:
1
Fatal error: Uncaught Error: Interface 'WPML_Log'not found in /home/photopuzzle/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/xml-config/class-wpml-config-update-log.php:6
Solution:
This is probably happening due to some missing/corrupted files after the backup restore. Please try the following:
1. Delete the "sitepress-multilingual-cms" plugin folder from the plugins directory
2. Go to the WP dashboard and deactivate the other WPML plugins
3. Download a new version of the "WPML Multilingual CMS" plugin from https://wpml.org/account/downloads/
4. Extract and upload it to the plugins folder
5. Activate it
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
