If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket.
Problema: El cliente está intentando gestionar el uso de créditos en el plan de pago por uso de WPML en su sitio y desea saber si puede establecer un límite de consumo mensual, recibir notificaciones cuando se supere un umbral de créditos, o suspender automáticamente la traducción automática al alcanzar el límite. Solución: Actualmente, no ofrecemos la opción de establecer un límite de consumo mensual, recibir notificaciones automáticas, ni suspender la traducción automática al alcanzar un límite de créditos en el plan de pago por uso. Como alternativa, recomendamos utilizar los créditos prepago, que permiten un mejor control sobre el consumo de créditos. Puede encontrar más información sobre los créditos prepago en este enlace.
Si esta solución no resuelve su problema o si la información proporcionada se ha vuelto obsoleta, le recomendamos abrir un nuevo ticket de soporte. También sugerimos revisar los problemas conocidos en esta página y confirmar que tiene instaladas las últimas versiones de los temas y plugins.
Problem: The client is experiencing 404 errors on translated versions of their websites after a recent update. The issue appears randomly when navigating between pages, such as the homepage and product pages. The problem was suspected to be related to WPML or possibly due to a hacking or malware issue. Solution: We recommended the following troubleshooting steps: 1. Create a full site backup or a staging site. 2. Update any outdated plugins and themes. 3. Flush any cache memory. 4. Deactivate all plugins, including WPML, and activate a default WordPress theme like Twenty Twenty. 5. Reactivate the WPML plugins. 6. Gradually reactivate the theme and other plugins one by one to identify the problematic plugin or theme. After following these steps, the issue was resolved, indicating that neither WPML plugins nor WooCommerce were the cause. The client was advised to activate the parent theme, then the child theme, and finally the rest of the plugins one by one to pinpoint the exact cause.
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.
Problem: After updating WPML, the product tabs from the YITH plugin are missing. Solution: If you're experiencing missing product tabs from the YITH plugin after updating WPML, we recommend the following steps: 1. Temporarily deactivate the WPML plugin to check if the product tabs from the YITH plugin reappear. 2. If the tabs reappear, this indicates a potential conflict between WPML and the YITH plugin. 3. Please provide us with debug information to help us better understand the issue. You can find instructions on how to retrieve this information from your site here. 4. Consider contacting the YITH plugin author to report the issue, as they might also be able to provide insights or a solution.
Please note that the 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 the problem persists, please open a new support ticket here.
The client is attempting to translate the strings "Geschichte", "Ziele", and "Konzept" on their webpage, but these strings are not being detected for translation. This issue is likely due to the strings being added through a custom Elementor widget that lacks WPML language configuration.
Solution:
We recommend creating a WPML language configuration file for your custom Elementor widget to enable translation. You can find detailed guidance on how to do this by visiting the following documentation links:
Ensure to back up your site before making these changes.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum.
Problem: If you're experiencing issues where debug mode reveals errors like 'Function _load_textdomain_just_in_time was called incorrectly' and translation loading for various domains is triggered too early, this indicates that some code in your plugin or theme is executing prematurely. Translations should ideally load at the 'init' action or later. Solution: We recommend checking the full error log to identify the specific plugins or themes causing these errors. The errors are likely due to plugins such as 'ultimate_vc', 'wpmf', and 'wc-aelia-foundation' loading WordPress translation files too early. You should report these errors to the respective plugin or theme authors as they need to adjust their code to prevent these errors from occurring. For more detailed information, please visit WPML Errata.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If these steps do not resolve your issue, 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 the problem persists, please open a new support ticket with us for further assistance.
Problem: The client is experiencing a critical error on their website when the WPML plugin is activated. This error occurs while trying to access the English version of a page. The error messages indicate that the translation loading for certain domains was triggered too early, suggesting a potential issue with early code execution in a plugin or theme. Solution: 1. We recommend deactivating the Thim Elementor Kit plugin temporarily to see if this resolves the issue. Before doing so, ensure to back up your database. 2. Check if the theme and related plugins are updated to their latest versions. Additionally, visit the plugin author's support forum to determine if this is a known issue.
If these steps do not resolve the problem or if the solution 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problema: El cliente está intentando cargar las traducciones en su sitio web, pero no se están mostrando correctamente. Las traducciones no cargan y los enlaces de botones como 'BEST OFFERS' no aparecen para traducir ni se traducen automáticamente. Solución: Si estás experimentando problemas similares con las traducciones que no se cargan o los enlaces que no se traducen automáticamente, te recomendamos verificar la configuración de WPML y asegurarte de que todas las traducciones están correctamente configuradas y asignadas. Además, es crucial que todos los plugins y temas estén actualizados a sus últimas versiones. Si el problema persiste, podría ser útil revisar la configuración específica de los enlaces y las traducciones automáticas dentro de WPML.
Si esta solución no resuelve tu problema o parece no ser relevante debido a que está desactualizada o no se aplica a tu caso, te sugerimos abrir un nuevo ticket de soporte. Te recomendamos encarecidamente revisar los problemas conocidos y verificar la versión del arreglo permanente. Para obtener asistencia adicional, visita nuestro foro de soporte.
Problem: Si estás experimentando problemas con el mini-carrito de WooCommerce en tu sitio web multilingüe, que se abre hacia el lado derecho y queda fuera de vista solo en Safari, el problema podría estar relacionado con el código HTML. Solution: Te recomendamos verificar el código HTML de tu sitio, especialmente asegurándote de que cada etiqueta
<li>
esté correctamente cerrada con su correspondiente
</li>
. Este detalle puede parecer menor, pero es crucial para que los elementos se muestren correctamente en diferentes navegadores, incluido Safari.
Si esta solución no resuelve el problema o si parece no estar relacionada con tu caso, te sugerimos abrir un nuevo ticket de soporte. También es altamente recomendable que revises los problemas conocidos, verifiques la versión de la solución permanente y confirmes que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, puedes visitar nuestro foro de soporte.
Problem: If you're experiencing issues with your WordPress site where problems occur in the site’s default language and WPML does not alter the content, it might not be related to WPML but to other plugins like Elementor. Solution: We recommend reaching out to the author of the Elementor widget or element you are using to display images and text, as the issue might be due to their code. Additionally, ensure that all WPML plugins are updated to the latest version. You can update your WPML plugins to version 4.7.5 by navigating to Plugins → Add New → Commercial tab.
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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
If you're experiencing a 404 error when clicking on the translated version of a page or post, it might be due to a conflict with your custom permalink structure. Specifically, if your structure includes
/index.php/%year%/%monthnum%/%day%/%postname%/
, this could be the root of the issue as WordPress does not fully support such structures.
Solution:
We recommend switching to one of the default permalink options under Settings >> Permalinks, such as "Day and name". After switching, make sure to resave the permalink settings. This adjustment has resolved similar issues in the past and should help in accessing the translated versions of your pages and posts without encountering a 404 error.
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 problems persist, please open a new support ticket.
