Problem: You are trying to set the width of the language selector in the menu to less than the default minimum width of 200 px when using flags only. This issue arises because the 'Menu language switcher' configuration in the 'Languages' section does not apply changes when adding a language switcher to the beginning or end of an existing menu. Additionally, the menu selector does not detect and list new navigation blocks. Solution: The client inserted a class in an outer element of the language selector and applying custom CSS to adjust the width. This approach allows you to override the default settings and achieve the desired width for your language selector. If you're experiencing difficulties with this solution or if it does not fully address your issue, please check our related known issues and verify that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at our support forum.
Problema: Il cliente desidera rendere cliccabile la bandierina della seconda lingua nella top bar del suo sito. Attualmente, è possibile cliccare solo il 'padding' attorno alla bandierina, ma non direttamente su di essa. Soluzione: Innanzitutto, è consigliabile verificare se il problema deriva dal tema attualmente in uso, cambiando tema per vedere se il comportamento del selettore di lingua cambia. Se il problema persiste, si può applicare il seguente codice CSS per rendere la bandierina cliccabile:
/* Rendi cliccabile tutta l'area della bandiera */<br />.wpml-ls-flag {<br /> pointer-events: auto;<br /> z-index: 10;<br /> position: relative;<br />}<br /><br />/* Evita che l'icona della freccia intercetti i clic */<br />.sub-arrow {<br /> pointer-events: none;<br />}<br /><br />/* Aumenta lo spazio cliccabile intorno alla bandiera */<br />.wpml-ls-flag {<br /> padding: 4px;<br /> display: inline-block;<br />}
Se il codice non risolve il problema, si consiglia di contattare il supporto del tema per assistenza su codice personalizzato.
Questa soluzione potrebbe non essere più rilevante a causa di aggiornamenti o modifiche future. Se il problema persiste, si consiglia di visitare la pagina dei problemi noti, verificare la versione della soluzione permanente e assicurarsi di avere installato le ultime versioni di temi e plugin. In caso di ulteriori difficoltà, si prega di aprire un nuovo ticket di supporto.
Problème : Vous souhaitez intégrer un switch WPML dans un menu créé avec le widget 'menu' d'Elementor, qui ne supporte pas nativement cette fonctionnalité. Vous avez rencontré des difficultés pour configurer le switch et pour qu'il se découpe en éléments de menu distincts pour chaque langue. Solution : 1. Utilisez un widget 'Shortcode' pour insérer le shortcode du sélecteur de langue WPML. Suivez les instructions sur cette page pour configurer le shortcode : Language Switcher Shortcodes. 2. Si vous souhaitez une intégration plus avancée, envisagez d'ajouter le sélecteur de langue en utilisant PHP en modifiant les fichiers d'en-tête de votre thème, ou en ajoutant le megamenu dans un template Elementor dans une colonne séparée. 3. Pour une solution personnalisée, créez un nouveau shortcode pour chaque langue en ajoutant le code suivant dans le fichier functions.php de votre thème enfant :
Appelez le shortcode pour chaque langue comme suit :
[wpml_switcher lang="en"]
ou
[wpml_switcher lang="fr"]
.
Si cette solution ne résout pas votre problème ou semble obsolète, nous vous recommandons de vérifier les problèmes connus, 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 de support.
Problème: Le client a rencontré un problème de traduction incorrecte sur son site multilingue, où certains boutons et éléments du footer s'affichaient en anglais au lieu du français, malgré le fonctionnement correct dans d'autres langues. Le problème persistait même après la mise à jour des plugins WPML. Solution: Nous avons recommandé au client de mettre à jour WPML et ses extensions en suivant ces étapes : 1. Créer une sauvegarde du site. 2. Aller à 'Tableau de bord WordPress > Extensions > Ajouter > Commercial' et cliquer sur 'Rechercher les mises à jour'. 3. Mettre à jour WPML et ses extensions. Pour plus d'informations, visitez https://wpml.org/faq/install-wpml/#automated-updates Ensuite, nous avons guidé le client à travers le processus de dépannage de WPML en lui demandant de suivre les étapes dans 'WPML > Assistance > Dépannage' et de cliquer sur les boutons indiqués pour résoudre les problèmes de traduction. Finalement, nous avons ajusté les chaînes de traduction dans le fichier footer.php pour assurer la cohérence de la langue source, ce qui a résolu le problème.
Si cette solution ne s'applique pas à votre cas, ou semble dépassée, nous vous recommandons vivement de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version des corrections permanentes, 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 de support.
Problem: Sie möchten einen individuellen Sprachumschalter für Ihre Website erstellen, der als Icon im Menü erscheint und bei Hover ein Drop-Down mit den Sprachoptionen English und Deutsch anzeigt. Solution: Wir können diesen spezifischen Dienst leider nicht direkt anbieten. Wir empfehlen Ihnen jedoch, unsere Dokumentation zum Erstellen eines benutzerdefinierten Sprachumschalters zu konsultieren: Custom Language Switcher. Falls Sie weitere Unterstützung benötigen, können Sie erfahrene Entwickler über WPML Contractors finden.
Bitte beachten Sie, dass diese Lösung möglicherweise veraltet oder nicht auf Ihren Fall zutreffend ist. Wir empfehlen Ihnen, die bekannten Probleme 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. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie hierfür unser Support-Forum.
Problem: You are experiencing issues with your logo not displaying correctly in the translated version of your site. Specifically, the logo appears black instead of transparent in German, and the translation pen loads indefinitely when changes are made. Solution: We applied custom CSS to address the logo display issue. Please add the following CSS code to your site by navigating to WP > Appearance > Customize > Additional CSS:
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.
The client is experiencing unusually long delays in automatic translations using the WPML plugin on a custom theme site. They are concerned about whether their theme's development is compatible with WPML.
Solution:
We recommend the following steps to diagnose and potentially resolve the issue:
1) Ensure a full site backup is taken. 2) Temporarily switch to the default Twenty Twenty-Five theme. 3) Attempt to translate a page using the Advanced Translation Editor and check for completion. 4) If the translation completes successfully with the default theme, it indicates that the issue may be related to the custom theme.
For the custom theme to work properly with WPML:
1) Ensure custom blocks are registered using
register_block_type()
. 2) Add a
wpml-config.xml
file to the theme folder to specify which block attributes should be translatable. Example:
3) Translate template parts or patterns from WPML → Translation Management. 4) Use translation functions in theme files and ensure the theme's text domain is loaded. 5) Set pages and custom post types to 'Translatable' in WPML → Settings → Post Types Translation.
For further guidance, consult the following documentation:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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.
Problem: The client is attempting to send multiple custom emails triggered by user interactions on their site using a specific code snippet to switch the email language based on the user's settings. Despite the translations being available in WPML->String Translations, the emails are only sent in German instead of the user's language. Solution: We reviewed the provided code and confirmed it aligns with our documentation on sending emails with WPML. We suggested testing the function
get_periodic_quiz_email_content
that retrieves the email content to ensure it returns translated content correctly. We recommended replacing the code for retrieving the email subject and body with hardcoded strings, which should be scanned and translated using the String Translation feature:
$message = __('The email body message', 'plugin-text-domain');
Additionally, we advised registering a shortcode to test if the function returns the correct translations by placing it on a test page and checking the translations in different languages. If these steps do not resolve the issue, the problem might lie within what
get_periodic_quiz_email_content
returns, or there could be another issue with the setup.
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. Should you need further assistance, please open a new support ticket.
Problem: The client wants to prevent WPML from automatically creating strings for the Blog Title and Tagline every time the General Settings page is saved. These strings are shared across sites but should remain unique and untranslated for each site. Despite attempts to delete these strings from the WPML interface, they reappear after settings are saved. Solution: We explained that WPML does not provide a hook to prevent the registration of default WordPress strings like Blog Title and Tagline in the WPML String Translation. These strings are automatically saved once option values are updated in WordPress. The client can delete the strings at WPML > String Translation or adjust their translation as needed. Additionally, the actions triggered when these options are updated are:
For more details on WPML hooks, visit WPML Hooks Reference. Please note, we do not support custom code modifications and cannot take responsibility for issues arising from custom implementations. For our support policy, see WPML Support Policy.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please visit our support forum at WPML Support Forum.
Problema: El cliente está intentando eliminar el slug '/portfolio-item/' de su sitio web multilingüe y ha añadido código personalizado en el archivo functions.php para modificar los permalinks y ajustar el selector de idioma de WPML. Sin embargo, el selector de idioma no funciona correctamente y elimina el prefijo '/ca/' para el idioma catalán, resultando en un error 404. Solución: 1. Modificar el código para ajustar el selector de idioma de WPML. Aquí está el código recomendado que no hemos probado, pero podría ser útil:
Si la solución propuesta no resuelve el problema o si el código es irrelevante debido a actualizaciones o diferencias en la configuración, recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que se han instalado las últimas versiones de los temas y plugins. Si necesita asistencia adicional, puede contactar a nuestros partners certificados en https://wpml.org/contractors/.
Problem: The client is attempting to auto-translate their entire site but encounters issues where post titles are translated, but not the content. Only some taxonomies are translated, and content on some pages is completely missed by the auto translator. Additionally, the client asked if there is a quick way to sync the translated post dates with the originals. Solution: We recommended two approaches to address the translation issues: 1. We provided a custom XML configuration to be added in WPML > Settings > Custom XML Configuration. This configuration ensures that more elements such as paragraphs, headers, and list items are translatable. Here is the XML code to use:
2. For posts that were not correctly translated, we advised manually triggering the translations. This involves editing the problematic posts, saving them, and then using the "pencil" icon in the sidebar translation option to retranslate the posts.
If these solutions do not resolve your issue or seem 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 the problem persists, please open a new support ticket.
Problem: The client is experiencing an issue where a specific URL on their site is being incorrectly redirected to a different URL, even though they are different pages. The client tried disabling WPML redirects and modifying the database and server settings, but the issue persisted. The client observed that the issue does not occur when WPML is disabled. Solution: We investigated the issue and found that the redirection problem persists even when WPML is disabled, indicating that the issue is not related to WPML. It was suggested that the problem might be due to WordPress or the server trying to guess the correct page based on similar slugs. We recommended that the client consult with their developer to explore further, possibly by using unique slugs for each page to prevent incorrect guessing by WordPress or the server. Additionally, we advised that our support for custom-coded solutions is limited, and for issues related to custom code, the client might consider hiring a contractor from https://wpml.org/contractors/.
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 the problem persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
