Problem: 1. Die Übersetzung in der spanischen Sprache schließt nicht ab, und das Zahnrad-Symbol bleibt permanent sichtbar. Manuelle Speicherversuche im Editor werden nicht korrekt übernommen. 2. Die Funktion „Automatische Übersetzung“ lässt sich in den WPML-Einstellungen nicht deaktivieren. 3. Die Fehlermeldung „WPML All Import requires WP All Import Pro or Free and WPML Multilingual CMS“ wird angezeigt. Solution: 1. Das Problem mit der nicht abschließenden Übersetzung könnte ein temporäres Problem unseres Übersetzungsservers gewesen sein. Bitte versuchen Sie es erneut, da es nun wieder funktionieren sollte. 2. Die Fehlermeldung bezüglich „WPML All Import“ erscheint, wenn das Add-on aktiviert ist, aber das erforderliche Plugin „WP All Import“ nicht installiert ist. Wenn Sie „WP All Import“ nicht verwenden, ist es nicht notwendig, das „WPML All Import“ Add-on zu installieren.
Falls diese Lösungen veraltet sind oder nicht auf Ihr Problem zutreffen, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.
Problem: The client has a Custom Post Type (CPT) with Jet Engine for real estate properties on their website. Although the template is translated into English, when accessing the English version of the property page, it displays the French template instead of the English one. Solution: We suggested checking if the template applied to the untranslated property is 'single property fr – ElBuilder'. This template might not have been translated yet, which could explain why the English page is showing the French template. If this was not the case, we offered to install the Duplicator plugin to create a copy of the website for a detailed investigation in a controlled environment. However, the client realized they had misidentified the template to be translated, translated it correctly, and resolved the issue.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please contact our support team for further assistance.
Problem: El cliente estaba experimentando problemas al traducir productos y páginas en su sitio WooCommerce utilizando el plugin WPML. Los productos no se traducían correctamente y al intentar traducir las páginas, aparecía un mensaje indicando que WPML no podía enviar parte del contenido para traducir. Solution: 1. Se solicitó al cliente que compartiera la información de depuración del sitio siguiendo los pasos de la guía de WPML (https://wpml.org/es/faq/como-puedo-proporcionar-mi-informacion-de-depuracion-para-obtener-soporte-mas-rapido/). 2. Se revisó la configuración y se identificó que faltaban traducciones en las plantillas de productos y en los productos agrupados. Una vez traducidos, el problema con los productos se resolvió. 3. Se recomendó al cliente actualizar todos los plugins y temas desactualizados para evitar conflictos en el código (https://www.irepairs.es/marketCLON/wp-admin/update-core.php). Además, se aconsejó crear una copia de seguridad antes de realizar las actualizaciones. 4. Se proporcionó un video al cliente describiendo los pasos para traducir las páginas correctamente.
Si la solución proporcionada no resuelve su problema o si encuentra que la información está desactualizada, le 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 e instalar las últimas versiones de temas y plugins.
Problema: Nella Dashboard di Traduzione, impostando i filtri per tradurre dall'inglese all'italiano, i post pubblicati e non completati, il cliente vede nell'elenco anche i post di altre lingue. Questo impedisce di selezionare tutti i post in inglese non ancora tradotti in italiano per la traduzione automatica. Soluzione: Abbiamo identificato che il plugin 'Page Links To' potrebbe causare il problema di visualizzazione errata dei post nella Translation Dashboard. Questo plugin viene utilizzato per impostare URL personalizzati per i post, il che potrebbe creare discrepanze tra il titolo mostrato in WPML e l'URL effettivo. Consigliamo di verificare le impostazioni di 'Page Links To' per i post problematici e assicurarsi che le impostazioni corrispondano alla lingua e al contenuto desiderati.
Se la soluzione proposta non risolve il problema o se sembra non essere più rilevante, vi invitiamo a visitare la pagina dei problemi noti e a verificare che abbiate installato le versioni più recenti dei temi e dei plugin. In caso di ulteriori difficoltà, non esitate a aprire un nuovo ticket di supporto.
Problem: The language switcher flag is aligned to the top of the mobile header instead of the middle, unlike other icons. Solution: We recommend adjusting the CSS for the mobile language switcher. Specifically, you should modify the CSS to remove the bottom margin from the
line, the switcher should align properly in the middle of the mobile header.
Please note that this 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 issue persists, please open a new support ticket.
Problem: The client is experiencing issues with displaying the WPML language switcher in a custom header space created with Elementor and the Saasive theme. Solution: 1. Edit Your Header Template with Elementor: Access your WordPress admin, navigate to Templates → Theme Builder, and edit your header with Elementor. 2. Add the WPML Language Switcher Widget: In the Elementor editor, search for the WPML Language Switcher widget and add it to your header. 3. Customize and Publish: Customize the appearance of the language switcher and publish the changes. 4. Translate the Header: Ensure the header template is translated for all languages using WPML’s Translation Dashboard. 5. If the issue persists, consider adding the language switcher to the main menu for better visibility across all devices. You can manage this in WPML -> Languages -> Menu language switcher. 6. Adjust the style of the language switcher using CSS at WPML -> Languages -> Language switcher options -> Additional CSS.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please open a new support ticket. We also 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. For further assistance, you can contact us directly at WPML support forum.
Problem: The client reported that Google only indexes the English pages of their multilingual site, even when manually indexing other languages. The '/EN/' slug appears despite other languages being set up, and WPML is configured correctly.
Solution: We recommended the following steps to address the issue: 1. Ensure the WPML SEO Add-on is active by checking under Plugins → Installed Plugins. If not present, install and activate it from Plugins → Add New → Commercial tab. 2. Verify the presence and correctness of 'hreflang' tags on translated pages by viewing the page source and searching for 'hreflang'. 3. Check the WPML's Language URL format under WPML → Languages and ensure 'Different languages in directories' is selected. 4. Disable the Browser Language Redirect temporarily under WPML → Languages to avoid confusion during indexing. 5. Re-save permalinks under Settings → Permalinks and re-submit sitemaps in Google Search Console.
Additionally, we advised against using the Browser Language Redirect feature as it does not distinguish between users and search engine bots, which can affect SEO and indexing. This is documented in our guides:
If these steps do not resolve the issue or if the information seems outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum.
Problem: If you're experiencing issues with image alignment in a multilingual site using WPML and Elementor, where images within Hebrew (RTL) text are not aligning as expected compared to their English (LTR) counterparts. Solution: We recommend checking how your theme or page builder, such as Elementor, handles RTL layouts. WPML sets the language direction, but the actual layout response, including image alignment, is controlled by Elementor and your theme. You might need to adjust the Elementor widgets and templates manually or apply CSS that uses logical properties for alignment, rather than fixed directional values. For further assistance, consider reaching out to Elementor Support.
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 personalized assistance.
Problème : Le site canaropa.com est devenu très lent et parfois inaccessible. Le client a demandé une analyse pour déterminer si les plugins WPML contribuaient à ces problèmes de performance. Solution : Nous avons constaté que la mémoire et le CPU étaient entièrement utilisés, ce qui indique une surcharge des ressources. Plusieurs plugins ont été identifiés comme sources d'erreurs et de requêtes lentes, ce qui contribue à la lenteur du site. Bien que l'augmentation des ressources serveur puisse aider, nous recommandons de réaliser un audit complet du site pour identifier et éliminer les éléments inutiles. Il est également conseillé de vérifier la base de données pour identifier les tables les plus lourdes et évaluer leur taille appropriée. Nous avons temporairement désactivé WPML pour les tests, et il semble que la mémoire soit toujours très utilisée, bien que jamais entièrement. Pour la configuration actuelle du site et son contenu multilingue, 3 Go de RAM devraient suffire, mais le processeur pourrait nécessiter une évaluation plus approfondie.
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous invitons à ouvrir un nouveau ticket de support. Nous vous recommandons également de consulter les problèmes connus et de vérifier que vous avez installé les dernières versions des thèmes et plugins.
Problem: After implementing WPML Multilingual CMS on a WordPress site with Elementor Pro and Advanced Custom Fields Multilingual, some content disappeared, and errors such as 'setting validation failed. title: invalid_value' appeared. Additionally, there were multiple errors in the WPML error log. The client resolved the issue temporarily by resetting WPML and deleting all translations from pages, ACF custom fields, and taxonomies, which restored the normal functionality of the site. Solution: We first need to confirm if the issue is directly related to WPML. We recommend deactivating WPML to see if the issue persists. If the problem remains, it suggests that the issue might not be solely related to WPML. If you have a backup from before the issue occurred, try restoring it to verify if the custom fields work correctly without WPML. If they do, this could indicate a potential conflict or misconfiguration during the WPML setup or translation process.
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 at WPML support forum for further assistance.
Problem: En la página de traducción al inglés, la imagen principal no se visualiza y las imágenes no se agrandan al hacer clic, a diferencia de la versión en español. A pesar de aumentar la memoria y marcar la opción de traducción automática, el problema persiste en ciertas páginas, como https://karlagutierrez.design/en/claudio-coello/. Además, se identificó un error al intentar abrir la publicación original en el Editor Divi: Uncaught (in promise) InvalidValueError: ETBuilderInitGoogleMaps is not a function. Solution: El problema está relacionado con un error en el módulo de Google Maps de Divi, no con WPML. Este error impide que WPML cree una traducción correcta. Se recomienda: 1. Consultar con el equipo de Divi para resolver el error de Google Maps. 2. Una vez resuelto el error en la publicación original, actualizar la traducción en WPML.
Si esta solución no resuelve el problema o si parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, visita nuestro foro de soporte.
Problem: The client has been unable to activate the WPML plugin on a simple single landing page website hosted on GoDaddy. Despite following previous advice to add a specific code snippet to the wp-config.php file, the plugin still does not activate or allow registration. Attempts to manually force database table creation through theme functions also failed, and the client is unable to change hosting providers. Solution: We recommend starting with a manual inspection of the file and database for incomplete WPML table creation or permissions issues, as standard and forced activation processes have failed. It's important to check the site environment for unusual file/folder permissions, database connection errors, or server restrictions, particularly with GoDaddy's known limitations. Avoid repeating previous unsuccessful methods such as modifying wp-config.php or using theme functions.php workarounds. Instead, consider direct intervention steps like requesting temporary admin access, reviewing system logs if possible, and ensuring proper communication with WPML registration servers.
If this solution does not resolve your issue or 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problème : Sur iPhone et iPad, la police de votre site ne se charge pas correctement lorsque le plugin WPML est activé. Une erreur de type 'downloadable font: Glyph bbox was incorrect' apparaît dans la console. Solution : Ce problème est souvent lié à la configuration du serveur plutôt qu'à WPML directement. Nous vous recommandons d'activer CORS (Access-Control-Allow-Origin) sur votre serveur. Une autre solution consiste à modifier le fichier .htaccess pour permettre le chargement correct des polices. Vous pouvez trouver des instructions détaillées sur la manière de procéder sur notre forum WPML : https://wpml.org/forums/topic/split-access-to-font-at-from-origin-has-been-blocked-by-cors-policy/
Si cette solution ne résout pas votre problème ou si elle semble obsolète, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent et de confirmer 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 : https://wpml.org/fr/forums/forum/assistance-en-francais/.
