Problème : Vous travaillez sur un site en développement et utilisez l'API Rest de WordPress pour la création et la mise à jour de posts. Vous souhaitez connaître la langue d'un post via l'API Rest et créer un post pour l'associer en tant que traduction d'un autre post. Solution : Pour récupérer la langue d'un post, utilisez ce hook : https://wpml.org/fr/faq/how-to-get-current-language-with-wpml/ Si vous utilisez WooCommerce avec l'API REST, consultez cette documentation : https://wpml.org/documentation/related-projects/woocommerce-multilingual/using-wordpress-rest-api-woocommerce-multilingual/ Pour lier des traductions de posts ou de pages via l'API Rest, une solution personnalisée est nécessaire. Un utilisateur de WPML a partagé un code qui a bien fonctionné pour d'autres utilisateurs, mais gardez à l'esprit que ce n'est pas une fonctionnalité intégrée à WPML et que nous ne pouvons pas offrir de support pour ce code. Voici le code :
Le processus consiste à créer le premier post dans une langue, créer le second post dans une autre langue, puis les lier via un endpoint personnalisé.
Si cette solution ne vous convient pas ou semble obsolète, ou si elle ne correspond pas à votre cas, 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 nécessaire, n'hésitez pas à ouvrir un nouveau ticket de support sur le forum de support WPML.
Problem: The client is experiencing issues with the MegaMenu on a multilingual WordPress site using WPML. In the German version, the Products menu item shows categories but no products, and clicking on a category leads to an incorrect URL. Solution: 1. We reviewed the MegaMenu code and found that the product categories were added but were pointing to the wrong URLs. We updated the code to be language-aware by adding a WPML language parameter and setting the language before querying products. 2. We also checked the slug translation issue and found that WordPress does not allow duplicate slugs across languages, which is not controlled by WPML. 3. We recommended setting up a staging site and activating a default WordPress theme to confirm if the issue is caused by the custom menu walker in the theme. If the problem persists, it may require custom development.
Please note that this solution might be 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 at WPML support forum.
Problem: The client was experiencing multiple critical issues with Custom Post Type (CPT) translations and permalink generation in WPML across different language subdomains. The specific problems included permalinks only working in the language they were last saved, incorrect redirects for CPT archive pages, an error message when editing CPT posts in Russian, and domain mapping issues with the Russian subdomain.
Solution: We identified that the client was incorrectly setting the slug for their CPTs, which affected the translatability of archive slugs. We recommended setting the rewrite array correctly in the
1
register_post_type()
function, specifically ensuring that the 'slug' key is correctly defined to make the archive slug translatable. For example:
1
rewrite' => array('slug' => 'book'),
This adjustment allows the slug to be translated according to WPML's standard procedures. We also suggested checking our documentation on translating slugs for custom post type archives for further guidance: Translating Slugs for Custom Post Type Archives
If this solution does not fully resolve the issues or seems outdated, we recommend opening a new support ticket. Additionally, we highly advise 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's developer noticed that the site's code is filled with direct references to specific languages, which is not scalable for adding multiple languages. Solution: We recommend using WPML hooks to manage language dynamically. Specifically, you can use
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 do not hesitate to open a new support ticket or visit our support forum.
Problem: The client needs to ensure that image meta fields are automatically translated in such a way that the image remains the same across all languages, both when using automatic translation and when manually translating posts or taxonomies. Solution: 1. To ensure images are available in all languages when using automatic translation, navigate to WPML > Settings > Media translation. Verify that the images exist in all languages by checking in Media > All and switching between languages. This setting uses the same file but ensures the image exists in the database for all languages. 2. For manual translations where you want the image to be set automatically, go to WPML > Settings > Custom fields, find your custom field, and set it to COPY. This will copy the same image IDs to your translated posts.
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 issues persist, please open a new support ticket at WPML support forum.
