Custom Work

Problem:
You are encountering an issue where both the original and updated permalinks for a translated page are functioning, leading to unexpected redirections. This occurs after changing the slug to resolve a 404 error on the translated page.
Solution:
The issue stems from custom code that modifies the URL structure. Specifically, the code segment handling 'locations' might be causing the redirection behavior. To address this, you can modify the code by commenting out the following line:

This change should ensure that only the desired URL remains active, preventing the original URL from redirecting to the updated one.

If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If the problem persists, we recommend opening a new support ticket at WPML support forum.

Problem:
You are using WPML's multi-currency feature on your WooCommerce site and want the final total amount sent to your payment gateway to remain in your primary currency, 'New Taiwan Dollar (TWD)', rather than the converted amount. However, at checkout, the system only sends 10 TWD instead of the correct total amount in TWD.
Solution:
Unfortunately, maintaining the checkout total in TWD using WPML's multi-currency feature directly is not possible without additional customization. You will need to implement some custom code similar to how currency conversion is handled in WooCommerce at checkout without WPML. If you require assistance with the custom code, we recommend consulting with 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.

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 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

function, specifically ensuring that the 'slug' key is correctly defined to make the archive slug translatable. For example:

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 is facing an issue where changing the status of a product to 'Draft' in the Dutch version does not automatically change the status in other language translations. The client desires that when the primary language product is set to 'Draft', all translated versions should automatically reflect this status.
Solution:
We explained that by default, WPML does not synchronize the post statuses across translations as per user feedback. However, to achieve the desired behavior, the client can add a custom code snippet. This code should be added to the functions.php file of a child theme or a Code Snippet Plugin. The code ensures that when the status of a product is changed in the primary language, it automatically updates the status in all other translations to match. Here is the code snippet.

If this solution does not apply or is outdated, we recommend checking 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 open a new support ticket.