Problem: El cliente está intentando traducir el slug de una taxonomía en su sitio web, pero al hacerlo, las páginas bajo esta sección se rompen. El cliente ha personalizado el archivo functions.php para que las taxonomías hijas aparezcan bajo la categoría padre en la URL. Solution: Primero, hemos revisado que la estructura de URLs deseada no requiere código personalizado si se configura correctamente desde el inicio. Se sugirió al cliente revisar un sitio de prueba donde se demostró que la estructura padre/hijo funciona sin personalizaciones adicionales. Se recomendó al cliente cambiar la estructura de enlaces permanentes a 'Post name' para ver si resuelve el problema. Además, se identificó que el problema podría estar en una configuración del tema o en el código personalizado utilizado para generar la taxonomía, lo cual está fuera del alcance del soporte de WPML. Se aconsejó contactar a los desarrolladores del tema o del código personalizado para ajustar este utilizando los hooks de WPML como referencia. Si esta solución no es relevante debido a que está desactualizada o no se aplica a su caso, le recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos y confirmar que tiene instaladas las últimas versiones de temas y plugins.
Problem: The client needs PHP filters or functions with WPML to retrieve the ID of translated media attached to a Meta Box field group on their homepage. Solution: We recommend using the
wpml_object_id
hook to obtain the ID of a translated media. Here is an example of how to use this hook to get the German translation ID for an attachment:
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 you still need assistance, please open a new support ticket at WPML Support Forum.
Problem: The client is experiencing an issue where the header on the Swedish version of their website does not function correctly. Solution: We discovered that the problem is due to custom JavaScript code in the header. We recommend removing this module JS code and instead adding it to the theme's options. Specifically, navigate to Divi > Theme Options > Integration and add the code to the
<head>
of your blog. This adjustment should resolve the issue.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking for 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 the problem persist, please do not hesitate to open a new support ticket with us for further assistance at WPML support forum.
Если данное решение оказалось неактуальным или не подходит для вашего случая, мы настоятельно рекомендуем открыть новый тикет поддержки. Также рекомендуем проверить известные проблемы, убедиться в версии исправления и подтвердить, что у вас установлены последние версии тем и плагинов.
Problem: The client was unable to preview a post on the French domain of their site, receiving an error message 'Sorry, you are not allowed to preview drafts'. They tried solutions from a WPML forum thread but none resolved the issue. Solution: We recommended that the client ensure they are using a secondary domain or sub-domain that mirrors the main site's setup to accurately reproduce the issue. Specifically, we advised: 1. Log in to the secondary domain at https://musee-guerre.cinnamonstaging.ca/wp-admin 2. Edit the post intended for preview. 3. Attempt to preview the post again.
If this solution does not resolve the 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 the problem persists, please open a new support ticket.
Problem: You are experiencing difficulty in finding specific strings in WPML > String Translation due to the abundance of bricks-* or gutenberg-* domains. Solution: Currently, it is not possible to hide bricks-* or gutenberg-* domains directly in WPML > String Translation. To address this issue, you would need to implement custom coding. However, this solution falls outside our support scope, and we do not have a ready-made code snippet available.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum.
Problem: The client reported that a French blog post was incorrectly displaying on an English page on their website, despite both versions appearing identical in the WP admin and front end. Additionally, there was an odd layout and error message at the bottom of the post. Solution: We discovered that the issue stemmed from the query used in the template file for the 'Related News' section, which lacked a language filter. To resolve this, we added the
'suppress_filters' => false
argument to the query, ensuring that only posts corresponding to the current language are displayed. This adjustment fixed the display issue on the English 'Aerospace' page. For the error on the French News page, it was caused by a problem with how the contributor images were saved in the translation. We corrected this by opening and updating each contributor's profile in the French version without making any changes, which resolved the layout and error message.
If you're experiencing similar issues, we recommend checking your queries to ensure they include appropriate language filters and verifying that all content elements are correctly saved in their respective translations. If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, please visit our support forum to open a new support ticket. Additionally, 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.
Problem: The client reported that strings on their WPML-powered site, which have been translated correctly, occasionally and randomly revert to the untranslated version. This issue occurs without any specific action taken within WPML. Adjusting the memory usage did not resolve the issue. Solution: Take note, that if the language files of a plugin or theme are added to WordPress or those files are being altered while working on the site, you will need to run a dialog which will appear on top of the page WPML > Theme & Plugin Localization. This dialog indicates that WPML found a new theme or plugins and needs to generate the custom language needed by WPML to translate the site. Those files will be saved at /wp-content/languages/wpml.< br/>< br/> We also identified some issues with GetText Calls inside the theme, like for example that the 'Learn More' link on the homepage was not using the correct GetText call. We recommended using esc_html__ for cases, in which the string is part of an HTML element which is detailed here: https://developer.wordpress.org/reference/functions/esc_html__ Additionally, we noticed multiple text domains being used within the theme, which could also lead to translation inconsistencies. We advised standardizing the text domain to 'rainforest-alliance' across all theme strings, as it is the one declared in styles.css. The text domain should always match the name of the theme or plugin's folder. More information on text domains can be found here: https://wpml.org/faq/what-are-text-domains/
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client has created a field with ACF called Tags, which is a taxonomy for tags matched to images attached to posts. Although these tags are translated, they are not displayed in the Italian version of the site.
Solution: We found that due to some custom coding the issue arises because when media is added in the default language and tagged, the tags are stored in the postmeta table. However, when switching to the secondary language and editing the media, the translated tags do not have a corresponding entry in the postmeta table. To resolve this, the client should edit the media in the secondary language, remove any pre-filled tags, and add them again to ensure the postmeta table is updated correctly for the secondary language.
If this solution does not resolve your issue, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problème : Vous avez ajouté beaucoup de code personnalisé dans le function.php de votre thème enfant en utilisant la fonction
__()
de WordPress, mais vous n'arrivez pas à traduire ces chaînes. Solution : Nous vous recommandons de rescanner votre thème pour que WPML String Translation puisse découvrir et ajouter ces chaînes à la traduction. Suivez ces étapes : 1. Allez dans "WPML > Localisation du thème et des plugins", sélectionnez votre thème puis cliquez sur "Analyser les thèmes sélectionnés pour les chaînes". 2. Attendez que l'analyse se termine. 3. Retournez dans "WPML > Traduction de chaînes" pour traduire les chaînes découvertes. Voici quelques documentations qui peuvent aider :
Si cette solution ne s'applique pas à votre cas ou semble obsolète, 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 de vérifier la version du correctif permanent. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.
