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.
Problem: After syncing strings in WPML, most translations are not visible on the website, although they are still translated in WPML. This issue is not related to cache problems. Solution: We recommend enabling WP DEBUG to check for any current errors that might be affecting the visibility of translations. You can enable WP DEBUG by following the instructions here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ Look for errors such as "Notice: Function _load_textdomain_just_in_time was called incorrectly." If you find such errors, please provide us with the details. If you are unsure how to use WP DEBUG, please let us know, and we will assist you further.
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, we encourage you to open a new support ticket for personalized assistance at WPML support forum.
Problem: The client translated the homepage into English and German using WPML, expecting the URLs to be nissei.nl/en and nissei.nl/de respectively. However, both URLs redirected to the original Dutch URL, nissei.nl, as did the URL nissei.nl/en/machines/, which redirected to nissei.nl/machines/. Solution: We identified that the redirection issue was caused by settings in the Yoast SEO plugin. We recommended checking and adjusting the redirection settings within the Yoast plugin to resolve the problem. Additionally, we advised updating WPML and its add-ons to their latest versions to ensure compatibility and functionality, especially if further investigation into the issue was required. We also emphasized the importance of making a full site backup before making any changes.
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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problema: Si estás experimentando problemas con botones creados usando Ultimate Addons de Beaver Builder, donde los enlaces no redirigen a la página traducida sino a la original, y estás utilizando el plugin BB Portfolio que ya no recibe actualizaciones, tenemos una solución para ti. Solución: 1. Añade el siguiente código XML a tu configuración de WPML para hacer que los enlaces de los botones estén disponibles en el editor de traducción de WPML:
<field type="UABB Button: Link URL"editor_type="LINK">link</field>
</fields>
</widget>
</beaver-builder-widgets>
</wpml-config>
2. Después de añadir este código, deberás editar los campos de enlace en el contenido original y guardar el contenido nuevamente para que las URL aparezcan en el editor de traducción. 3. Si configuras el enlace dinámicamente, como se muestra en la captura de pantalla proporcionada por nuestro equipo de soporte, no tendrás que traducirlo manualmente.
Es posible que esta solución pueda ser irrelevante debido a actualizaciones futuras o porque no se ajusta exactamente a tu caso. Si después de probar estos pasos sigues teniendo problemas, te recomendamos abrir un nuevo ticket de soporte en nuestro foro de soporte. También te sugerimos 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.
Problema: Stai cercando di programmare articoli in tedesco, ma non vengono pubblicati automaticamente nonostante l'uso di un cron job lato server per eseguire gli eventi di WP Cron. Gli articoli rimangono programmati e non visibili, e l'evento programmato
1
action_scheduler_run_queue
tarda ad essere eseguito. Soluzione: Il problema potrebbe derivare dal fatto che il cron job configurato sul tuo server controlla solo i post in italiano e non aggiorna automaticamente lo stato delle traduzioni da bozza a pubblicato. Questo comportamento è quello atteso senza una configurazione specifica che includa le traduzioni. Ti consigliamo di verificare la configurazione del cron job per assicurarti che includa anche le traduzioni nei vari linguaggi.
Se questa soluzione non risolve il problema o se le informazioni risultano obsolete o non applicabili al tuo caso, ti invitiamo a consultare la pagina dei problemi noti e a verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Inoltre, se necessario, apri un nuovo ticket di supporto sul forum di supporto WPML per assistenza ulteriore.
Problem: The client is experiencing a critical error when accessing the 'Theme and plugins localization' option in the WPML menu and issues with modifying, adding, or deleting widgets in the Footer columns and the TopBar widget. Solution: First, we recommend changing the database collation to utf8mb4_unicode_520_ci to ensure compatibility with all characters. You can convert the tables using the following SQL query:
1
ALTER TABLE your_table_name CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci;
Next, address the widget-related errors by increasing the PHP memory limit as indicated by the error logs showing memory exhaustion. Additionally, in the WPML → String Translation section, filter by Widgets and delete the excessive unneeded entries, as most are duplicates and only a few are translated.
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 problem persists, please open a new support ticket.
Problem: El cliente no puede editar ni eliminar las traducciones existentes en su sitio web y tiene problemas con el límite de memoria de WordPress y el idioma del backend. Solution: 1. Para eliminar traducciones, sigue los pasos para eliminar cualquier contenido en WordPress, filtrando por el idioma secundario. Por ejemplo, para eliminar una página traducida, ve a Páginas -> Filtrar por el idioma secundario -> Seleccionar la página y hacer click en 'Mover a la papelera'. Luego, elimina la página desde la Papelera en el idioma secundario. 2. Para incrementar el límite de memoria de WordPress a un mínimo de 128Mb, agrega el siguiente código en el archivo wp-config.php:
Coloca este código encima de la línea /* That's all, stop editing! Happy blogging. */. Verifica el límite de memoria en WPML -> Soporte. 3. Para cambiar el idioma del backend del sitio, si no tienes instalado WPML, sigue las instrucciones en este enlace. Si has vuelto a instalar/activar los plugins de WPML, sigue las instrucciones en este otro enlace.
Si esta solución no resuelve tu problema o parece desactualizada, 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 temas y plugins. Para más ayuda, visita nuestro foro de soporte en https://wpml.org/es/forums/forum/ayuda-en-espanol/.
Problem: You are experiencing an issue where accessing a specific product page on your WordPress site using WPML redirects you to an unexpected page. Solution: We have identified that this redirection is caused by the WordPress core, not by WPML plugins. To resolve this, we recommend editing the product page and modifying the slug. Here is a step-by-step guide: 1. Go to the product page: /it/shop/cellulari-ricambi-phone-parts/motorola/81700/ (in Italian). 2. Change the slug from '81700' to '81700-it'. This modification should prevent the WordPress core from executing the unwanted redirection.
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 needed, please open a new support ticket at our support forum for further assistance.
Problem: The client is facing an issue where the text in the WPML Advanced Translation Editor (ATE) does not match what appears on the frontend. This discrepancy persists even after updating the content via ATE. The problem is suspected to be linked to the Speed Optimizer plugin, which might not be compatible with WPML. Solution: We recommend contacting the support team or developers of the Speed Optimizer plugin to inquire about its compatibility with WPML. If the plugin is found to be incompatible, suggest that the developers join our Go Global program, where our Compatibility developers will assist in making their product fully compatible with WPML at no cost.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket here.
Problem: The client is experiencing issues with header settings being lost upon activating the WPML plugin. The issue persists even though the theme developer recommended WPML, stating it was tested for compatibility. The problem also occurred with other translation plugins like Polylang and Weglot. Solution: We advised the client that if the issue also appeared with other plugins, it is likely not caused by WPML. The responsibility to resolve this lies with the theme author, especially if they claim compatibility. We also mentioned that we could investigate further if the client can demonstrate that the problem is specific to WPML. Additionally, we reminded the client not to share credentials outside designated secure areas due to GDPR regulations.
If this solution does not resolve your issue or seems outdated, we recommend checking for related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and ensuring you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.