Problema: Estás intentando traducir un post del inglés al español usando el editor avanzado clásico, pero el post traducido no se genera correctamente. En el backend de WordPress, aparece un icono de engranaje que indica que el proceso de traducción no se completó, y se presentan errores en el registro del editor de traducción avanzado. Solución: 1. Desactiva el plugin 'amazon-s3-and-cloudfront-pro' y verifica si el problema se resuelve. 2. Asegúrate de crear una copia de seguridad del sitio completo. 3. Actualiza todos los plugins y temas desactualizados desde este enlace. 4. Si el problema persiste, comparte un video mostrando el problema para un análisis más detallado. 5. Verifica que las credenciales de acceso al sitio estén correctas para permitir una revisión más profunda si es necesario.
Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: If you're using WPML with WooCommerce and have enabled automatic translation, you might encounter an issue where duplicating a published WooCommerce product causes it to start translating immediately, even though you want the duplicated product to remain as 'drafts' and not be translated until it is published. Solution: Currently, there isn't a direct option in WPML to prevent automatic translation for duplicated products that are still in 'draft' status. A potential workaround is to disable automatic translation for the product post type until the product is ready to be published. 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 more personalized assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing a 404 error when trying to view a product translated using WPML in Finnish. The issue arises even after translating the permalinks in WooCommerce Multilingual & Multicurrency. Solution: The 404 error is not directly related to WPML. If you disable WPML, you will notice that the same issue persists because you have used the same slug for your Product category base and Custom base in WordPress settings. This duplication causes conflicts within WordPress as it requires unique slugs for proper functionality. We recommend changing one of the slugs to ensure they are unique. You can adjust your permalink settings by visiting your WordPress dashboard and navigating to the permalink options at https://sh-teksor.fi/wp-admin/options-permalink.php.
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, 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 if the problem persists. You can do so at WPML support forum.
Problème : Vous avez configuré la traduction des centres avec WPML et JetEngine, mais vous rencontrez une erreur 404 sur les pages traduites des centres. Vous avez bien paramétré les centres comme traduisibles et spécifié quels champs devaient être copiés ou traduits. Solution : Nous avons identifié que le problème est lié aux pages traduites qui se trouvent dans la corbeille. Pour résoudre ce problème, vous devez soit restaurer ces pages depuis la corbeille, soit les supprimer définitivement de la corbeille et ensuite refaire la traduction. Si vous continuez à rencontrer des problèmes, nous vous recommandons de vérifier les problèmes connus et de vous assurer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problema: O cliente estava enfrentando um problema na página de finalização de compras do seu site. Não estava claro o que era esperado versus o que estava sendo exibido, mas o problema foi identificado como um conflito com um código CSS. Solução: Após a análise, descobrimos que o problema era um conflito com um código CSS. Recomendamos verificar e ajustar o CSS em questão para resolver o problema. Se você estiver enfrentando um problema semelhante, recomendamos que verifique o código CSS do seu site para possíveis conflitos.
Se esta solução não for relevante para o seu caso, ou se ela estiver desatualizada, sugerimos abrir um novo ticket de suporte. Recomendamos fortemente que verifique os problemas conhecidos, confirme a versão da correção permanente e verifique se você instalou as versões mais recentes de temas e plugins. Para assistência adicional, visite nosso fórum de suporte.
Problem: The client is unable to activate the OTGS Installer after renewing WPML and is having trouble installing the license key. Solution: 1. Remove your site from the allowed list by visiting https://wpml.org/account/sites/ and selecting 'Remove your site'. 2. In your site's backend, navigate to Plugins -> Add new -> Commercial tab, and click on 'Unregister WPML from this site'. 3. Click on the link below the field to enter the new registration key, which will redirect you back to your wpml.org account to generate a new registration key. 4. Paste the new registration key in Plugins -> Add new -> Commercial tab.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is using the Jobzilla Theme with WPML and has set German as a different language. They expected the default language home page to be 'http://nicl12.sg-host.com/', but it redirects to 'http://nicl12.sg-host.com/de/'. The client wants the default language home page to not include '/de/'. Solution: We advised the client to go to WPML -> Languages -> Language URL format and deactivate the option to show a directory for the default language. After this, they should save the changes and re-save the permalinks. This action should resolve the issue of the default language home page redirecting incorrectly. Additionally, we clarified that WPML cannot remove the language directory only for the frontpage of the default language. Instead, we suggested creating a root page, which is different from the frontpage in the default language, as described in our guide: Setting up a root page. If the client needs behavior outside the scope of WPML's standard features, such as custom coding, we recommended contacting one of our certified partners at WPML Contractors.
Please note that this solution might be outdated or not applicable 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 the issue persists, please open a new support ticket with us for further assistance.
Problem: El cliente está utilizando WPML y desea que solo los blogs en español se indexen en Google, evitando la indexación de los blogs en inglés y catalán que no están traducidos. Los posts no traducidos se estaban indexando, generando problemas potenciales de contenido duplicado en SEO. Solution: Para evitar la traducción y la indexación de los posts en idiomas secundarios, recomendamos configurar los posts como 'No traducible'. Esto evitará que se muestren en los idiomas secundarios. Además, para gestionar las redirecciones al idioma original, es necesario utilizar un plugin de redirección, ya que WPML no ofrece opciones para redirecciones directas. También sugerimos instalar un plugin de SEO como RankMath o Yoast SEO junto con nuestro plugin WPML SEO para indicar a Google que el contenido no está traducido. Puedes encontrar más información sobre cómo configurar WPML SEO en este enlace: https://wpml.org/documentation/how-to-set-up-multilingual-seo-on-your-website/
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto irrelevante, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Si necesitas más ayuda, no dudes en contactarnos en nuestro foro de soporte.
Problem: The client is unable to translate the Weight & Dimensions for WooCommerce Variable Product Variations into different languages, despite having the necessary plugins and setting the Custom Fields Translation to 'Translate'. Solution: 1. We confirmed that numbers are generally not translated but copied over into the secondary language, and variations with different dimensions are considered different products. 2. We created a sandbox for testing and confirmed that dimensions cannot be translated using the WordPress Editor, only the Translation Editor. 3. We escalated the issue to our second-tier support for further investigation. 4. We conducted a test to add dimensions in an Asian language directly in the product without translating, to see if the issue persists. 5. We concluded that this is a limitation of WordPress, not WPML, and recommended checking WordPress/WooCommerce forums for potential workarounds.
If this solution does not resolve your issue or seems outdated, please visit our known issues page to check for any updates or related issues. We also recommend ensuring that you have the latest versions of themes and plugins installed. If the problem persists, do not hesitate to open a new support ticket.
Problem: You are using WPML on your site and want to ensure that selected pages or posts are not indexed by Google after their translation is completed. However, you are unable to find a built-in feature in WPML that automatically sets pages or posts to noindex after translation. Solution: WPML does not directly control whether pages are indexed or not. Instead, it works alongside SEO plugins like Yoast SEO or Rank Math. To automatically set translated pages or posts to noindex, you will need to use these SEO plugins. We recommend using the WPML SEO add-on to enhance compatibility between WPML and SEO plugins. You can read more about WPML SEO here: https://wpml.org/documentation/related-projects/wpml-seo/ Additionally, if you have Yoast SEO or Rank Math SEO installed, you can translate meta tags and fields. For guidance on translating meta information with Yoast using WPML, visit: https://wpml.org/documentation/plugins-compatibility/using-wordpress-seo-with-wpml/
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 open a new support ticket at our support forum.
