Problem: You are trying to implement languages on subdomains for your site, but the subdomain redirects to the main site despite DNS records being correct. Solution: First, we recommend disabling WPML to check if the subdomain still redirects to the main site. If the redirection persists, it indicates that the issue is not related to WPML but may stem from another source. Possible causes could be the Redirection plugin or the Nginx configuration file.
If this solution does not resolve your issue or seems outdated, please visit our known issues page and verify that you have the latest versions of themes and plugins installed. If the problem continues, we highly recommend opening a new support ticket here.
Problem: The client reported that after translating Category or Page created using the Elementor Pro "Posts" widget with WPML, the product directory created with the "Posts" widget was missing on the translated page. Solution: We recommended adjusting the "Query" settings in Elementor Pro. The client followed our guidance, adjusted the "Query", and confirmed that the product listings on the category and page sections are now displaying correctly.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client noticed that WPML inserts hreflang tags for translated pages, and was concerned about the presence of the x-default tag, which defaults to the English page. Solution: We explained that it is not possible to modify the hreflang code. The x-default tag is necessary when users access the site with a browser that is neither in English nor in Italian. According to Google's guidelines, the x-default hreflang value is used to specify a neutral language and region URL for content when the site does not support the user's language and region. It is used alongside other hreflang values that specify a URL version targeted at a specific language and region. Therefore, removing this tag would be detrimental.
Additionally, hreflang tags appear in all languages regardless of the page's language. For example, if you visit the English version, you will see the hreflang for the Italian version, which is correct.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed to translate product descriptions from Greek to Bulgarian while keeping English words unchanged. They also inquired about the behavior of the translation memory when deleting and retranslating products. Solution: We explained that when the client translates descriptions for products using automatic translation, these translations are saved into the translation memory. If the client edits and corrects a translation for a product, this updated translation is stored in the translation memory. For any new product created with the same description, it will automatically use the newly edited translation. However, for existing products, the client will need to manually update the description to apply the changes from the edited translation. Regarding the deletion and retranslation of products, the client can delete their translated products and retranslate them without using any credits, provided they do not delete the "primary" language of a product. We advised the client to perform a backup before proceeding.
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 the problem persists, please open a new support ticket.
Problem: The client is experiencing an issue where all 'saved' layouts from the media library are appearing in the translation list, even though this information is already on the pages, and they only show as not found when clicked. Solution: We recommend that the Translation Manager use the filter available in the Translation Manager interface. By selecting "Pages" from the "All Types" dropdown and clicking the 'Filter' button, they can view only the pages in the list. This method helps manage which content appears in the translation list, although it is not possible to control which post-type content is available to each Translation Manager.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket here.
Problema: El cliente no puede editar una plantilla usando el theme builder debido a un error PHP:
Fatal error: Uncaught ArgumentCountError: Too few arguments to function SitePress::get_terms_args_filter(), 1 passed and exactly 2 expected
. Solución: Para resolver este problema, primero recomendamos crear un sitio de staging para no afectar el sitio en producción. Luego, desactiva todos los plugins excepto los de WPML y activa el tema Divi (padre). Si el problema desaparece, el siguiente paso es activar el tema y los plugins uno por uno para identificar cuál está causando el conflicto. Una vez identificado el plugin o tema problemático, puedes buscar una solución específica para ese componente o contactar al soporte del mismo.
Es posible que esta solución ya no sea relevante debido a actualizaciones o porque no se ajusta exactamente a tu caso. Si después de seguir estos pasos el problema persiste, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: El cliente está utilizando SEranking para el control SEO de su sitio web y ha recibido un error relacionado con los atributos hreflang que apuntan a versiones no canónicas de la página, lo cual puede confundir a los motores de búsqueda. Solution: Primero, verificamos si la herramienta SEO hace referencia al atributo hreflang="x-default". Si no es así, solicitamos al cliente que nos envíe una captura de pantalla desde WPML > Idiomas > Editar idiomas para revisar la configuración. Además, proporcionamos información sobre el uso del atributo "x-default" como una recomendación de Google, que puede consultarse en los siguientes enlaces:
Si la solución proporcionada no resuelve el problema o si la información parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problème : Le client a rencontré un problème de 'pagina non trovata' après avoir traduit la page 'nos produits' en italien en utilisant l'éditeur WordPress au lieu de l'éditeur de traduction WPML. Les pages traduites n'avaient pas de titre et utilisaient un titre par défaut basé sur l'ID de la page, ce qui a affecté les slugs (URLs). Solution : Nous avons identifié deux approches possibles pour résoudre ce problème : 1. Utiliser l'éditeur de traduction WPML pour assurer que les traductions utilisent correctement les titres et les slugs. 2. Si le client préfère continuer à utiliser l'éditeur WordPress, il est crucial d'éditer les pages italiennes pour leur donner un titre et un slug appropriés.
Si cette solution ne résout pas le problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, de confirmer que vous avez installé les dernières versions des thèmes et plugins, et d'ouvrir un nouveau ticket de support si nécessaire. Pour plus d'assistance, visitez notre forum de support.
Problem: The client's website is in English and Chinese, and they are using WPML to manage translations. They observed that WPML creates a separate Chinese version of every English web page and product, which automatically appears when switching to Chinese. However, the layout of the copied web page does not fully match the English version, requiring significant adjustments. Solution: We confirmed that WPML indeed creates a separate version of the primary language page for translations. For instance, the English homepage at https://365onsale.com/ will have a Chinese counterpart at https://365onsale.com/zh-hans/. This setup means that in the backend, there are two versions of the homepage, each in a different language. To understand more about why WPML operates this way and its benefits over other plugins, you can read our comparison guide here: https://wpml.org/home/comparing-wpml-free-paid-alternatives/.
If this solution does not fully address your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
