Problem:
Language switcher almost disappear from the menu on mobile. Solution:
It seems there is some CSS conflict which causing this issue and can be solved by using the below CSS:
@media(max-width:992px) {
.menu-item.wpml-ls-item ul.sub-menu, ul#mobile_menu1 .menu-item.wpml-ls-item ul {
border: none !important;
padding: 0 !important;
}
.wpml-ls-item ul li {
margin-bottom: 0 !important;
text-align: left !important;
}
.wpml-ls-item {
display: block !important;
}
}
Problem: The client is experiencing an issue where the page https://productdepartment.nl/en/product-blog/ displays a 'No results found' message, and they want to either not show this page at all or have the projects translated into English.
Solution: We recommend two options: 1) Translate the Project posts into the English language.
OR
2) Use the default language as a fallback for untranslated content for the 'Projecten(project)' Post Type. To do this, follow these steps:
Take a full site backup.
Go to WPML>>Settings>>Post Type Translation.
Select 'Translatable – use translation if available or fallback to default language' for the 'Projecten(project)' Post Type.
Save the changes.
Navigate to Settings>>Permalinks and resave the settings.
Additionally, if you are listing Project Posts using Project Category terms, ensure you also choose the 'Translatable – use translation if available or fallback to default language' option for the 'Project Categories' from WPML>>Settings>>Taxonomy Translation.
Please note that the solution provided 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 WPML 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 wants to change the URL slug from '/el/katastima/' to '/el/shop/' on the Greek version of their site.
Client isn't using WCML plugin.
Solution: 1. Navigate to the Pages section. 2. Edit the shop page in the default language. 3. Switch to Greek using the top admin bar. 4. In the sidebar, click on the "URL" and change the slug as desired. 5. Save the changes.
Alternatively, you can: 1. Go to WPML -> Settings -> Translated documents options -> Page URL. 2. Change the setting from "Auto-generate from title (default)" to "Translate". 3. This will allow you to translate the slug in the Advanced Translation Editor (ATE) when adding or updating the translation.
As another alternate, if you're using WCML, you can use WooCommerce > WooCommerce Multilingual & Multicurrency > Status tab > WooCommerce Store Pages section.
If this solution does not apply to your situation, or if it seems outdated, we recommend checking the related known issues and verifying the version of the permanent fix. Ensure 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 was experiencing a 'Forbidden' error when switching languages on their website. They were concerned that updating plugins might cause the issue to recur.
Solution: We first asked the client to check if the issue still occurred, suggesting it might have been a temporary caching problem. If the problem persisted, we recommended a step-by-step troubleshooting process: 1. Ensure a full backup of the website and database. 2. Deactivate all plugins except for WPML and its addons, then check if the issue still occurs. 3. Reactivate each plugin one by one, checking for the error after each activation to identify any conflicting plugin. 4. If the issue continued, we advised repeating the steps with a default WordPress theme.
Please note that the solution provided might be 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.
Problema:
El cliente tiene preguntas sobre la redirección automática de usuarios a la versión del sitio web en su idioma, basándose en su ubicación geográfica, y cómo afecta esto a usuarios de diferentes regiones que hablan el mismo idioma.
Solución:
Si estás experimentando dudas sobre la redirección automática basada en la ubicación geográfica de tus usuarios, te recomendamos no utilizar este enfoque. Nuestra funcionalidad de redirección se basa en el idioma del navegador del usuario, no en su país de origen. Por ejemplo, si un usuario en Italia tiene su navegador en inglés, será redirigido a la versión en inglés del sitio, no a una posible versión italiana. Lo mismo ocurre con los usuarios de Portugal que, si tienen su navegador en portugués, serán redirigidos a la versión en portugués del sitio, independientemente de la variante regional del idioma.
Es posible que esta solución no sea relevante para tu caso, ya sea porque la información está desactualizada o simplemente no se aplica a tu situación. Si es así, te sugerimos abrir un nuevo ticket de soporte. También te recomendamos encarecidamente revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins.
Problem: 1. Existing attributes set up before installing WPML are not translatable. 2. New attributes have names in English, but types appear in Hungarian and there is no visible setting to change this.
Solution: 1. Navigate to Products-> Attributes-> Configure "Room Type" terms and ensure that the terms are added in English. 2. Go to WPML-> Settings-> Taxonomy Translation section, and verify that these attributes are set to be translatable.
If the solution provided here does not apply to your situation, or if it seems outdated, we encourage you to check the related known issues and confirm that you have the latest versions of themes and plugins installed. If you still encounter issues, please do not hesitate to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client's website, with Dutch as the default language and English added via WPML, was displaying Dutch blog posts correctly, but the English translation page showed 'No result found'. Additionally, in the WordPress backend, all Dutch posts disappeared, showing only the default 'hello world' post.
Solution: First, we recommended the client to back up their site and database. Then, we instructed them to navigate to WPML -> Support -> Troubleshooting and perform the following actions:
Synchronize posts taxonomies
Clear the cache in WPML
Remove ghost entries from the translation tables
Fix element_type collation
Set language information
Synchronize local job IDs
Fix Terms count
Fix post assignment for translations
After these steps, we asked if the posts were visible in the backend with WPML active.
Upon further investigation, we found that some posts had titles in English but content in Dutch. We asked the client to confirm if they had translated these posts into English. We also clarified that the posts in question were under the 'Project' post type and provided a screencast for detailed guidance.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If you're experiencing similar issues and the provided steps do not resolve them, 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 problem persists, please open a new support ticket with us.
Problem: The client was experiencing an error indicating that the
product_type
field was set incorrectly for some product translations due to the
product_type
taxonomy being translated.
Solution: We advised the client to first take a full backup of their site. Then, to resolve the issue, we instructed them to navigate to the WooCommerce Multilingual troubleshooting page and click on the "Start" button under "Fix product_type taxonomy terms". We also confirmed that the client's settings for the
product_type
taxonomy were now correct according to the screenshot they provided. Additionally, we clarified that the warning in their screenshot was a reminder to back up their site before proceeding with any troubleshooting steps. For more details, we provided a link to our documentation: WPML Troubleshooting Options.
Please note that if this solution does not apply to your case, or if it is outdated, we recommend checking the 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 do not hesitate to open a new support ticket with us.
Problem: The client was experiencing a fatal error when trying to translate a page that uses 'flexible content' blocks from ACF. The error occurred on the backend when switching to the English version of the page, and also when visiting the page on the frontend.
If the solution provided is not relevant 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 issue persists, please open a new support ticket: Contact WPML Support.
Problema: El cliente tiene un sitio habilitado con ATE y desea saber si es posible exportar XLIFF, traducirlo externamente e importarlo de nuevo a WPML, y si la traducción se importará a ATE o cambiará a CTE. Solución: Si estás experimentando esto, te recomendamos usar CTE al importar las traducciones a través de XLIFF, ya que CTE capturará los datos importados de XLIFF y podrás editar las traducciones desde el servicio. Con ATE, no podrás hacer esto. Si importas la traducción a través de XLIFF y usas ATE, perderás las traducciones y necesitarás volver a traducir el contenido. Por lo tanto, si vas a importar las traducciones a través de XLIFF, puedes usar CTE o cambiar a traducción manual para poder editar las traducciones.
Es posible que esta solución sea irrelevante, ya sea porque está desactualizada o porque no se aplica a tu caso. Si es así, te sugerimos abrir un nuevo ticket de soporte. También recomendamos encarecidamente revisar los problemas conocidos relacionados, verificar la versión de la solución permanente y confirmar que has instalado las últimas versiones de temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en el foro de soporte de WPML.
Problem:
Some translated pages or posts are redirecting to the homepage even though the translations exist. Solution:
If you're experiencing redirects of translated pages or posts to the homepage, we recommend updating the post in the translated language. Here's how you can do it:
1. Edit the post in the translated language.
2. Click on 'Update' to save the changes.
3. Check if the post is now accessible on the frontend.
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 problem continues, do not hesitate to open a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client had an issue where their WPML account showed zero automatic translation credits despite having renewed their subscription and not using the credits. They needed to restore the credits to their WPML account and assign them to a new project. Solution: We found that the client's '152380' credits were stuck on their site. We returned those credits to the client's WPML.org account. We then advised the client to assign the credits to any site by following the documentation: How to assign automatic translation credits to your sites. We also asked the client to inform us if the issue was resolved or if they required further assistance.
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 help, please don't hesitate to open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client has a multilingual WPForm in English and Spanish and wants all form submissions to be exported in English, even though the form might be submitted in Spanish. Currently, email notifications are in English, but the entries viewed in WPForms > View Entry and exported as an XLSX file are in Spanish. Solution: We explained that it is not possible to change the language of the exported entries out of the box, as the export function will export the content in the language it was submitted. The reason email notifications are in English is likely because the admin user's language is set to English, and thus admin notification emails are received in English.
If you're experiencing this issue and the provided solution does not apply to your case, or if it's outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum.
Problem: The client was experiencing issues with Media Translation not working in Gutenberg, specifically with anchors not showing up for translation.
Solution: We recommended that the client incorporate a custom XML configuration into WPML. Here is the step-by-step process: 1. Navigate to WPML > Settings > Custom XML Configuration tab. 2. Insert the following custom XML configuration:
3. Make slight adjustments to the primary language page and re-translate it. 4. In the advanced Translation Editor, attempt to locate the image name.
If the solution provided 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, 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 experiencing issues with WPML prompts after moving their site from a staging to a live environment, despite using the same site key for both environments.
Solution: We recommend the following steps to resolve the issue: 1. Go to WPML → Support in your WordPress dashboard. 2. Click on the Troubleshooting link. 3. On the WPML Troubleshooting page, click the button labeled 'Force-enable WPML’s Advanced Translation Editor'. 4. You can now use WPML’s Advanced Translation Editor to add, edit, and manage translations on both domains without seeing the migration wizard.
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 necessary, please open a new support ticket at 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