Custom Work

Problem:
The client added the Arabic language to their site using WPML and expected the content to display in RTL (right-to-left) format. However, the Arabic content was displaying in left-to-right format due to the use of a custom language code (ar-eg), which WPML did not recognize as RTL.
Solution:
We advised the client that the issue is controlled by the theme rather than WPML itself. For immediate testing, the client could switch to a theme that supports RTL or set Arabic as the WordPress language without WPML to confirm if the issue persists. To address the specific issue with the custom language code, we provided a code snippet to force RTL direction:

/**
 * Force RTL direction for the custom Arabic‑Egypt (ar‑eg) language.
 * Adjust the body/html tag direction when WPML's current language is ar-eg.
 */
add_filter( 'language_attributes', function ( $output ) {

	// Get WPML's current language code
	$current_lang = apply_filters( 'wpml_current_language', null );

	// If we're on ar-eg and dir="rtl" is not already in the attributes, add it
	if ( 'ar-eg' === $current_lang && false === stripos( $output, 'dir=' ) ) {
		// Remove any existing dir attribute just in case, then append rtl
		$output = preg_replace( '/\sdir=("|\")(rtl|ltr)\1/i', '', $output );
		$output .= ' dir="rtl"';
	}

	return $output;
}, 20 );

We recommended that the client ensure they have a backup before implementing this snippet as it was not tested directly.

If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 is trying to organize translated pages in the CMS, separating English pages from other languages to make management easier. They also encountered an issue where random pages appeared in the English translation tab and needed to prevent Authors from publishing translations without Admin approval.

Solution:

1. To separate and organize pages by language, check the language option in the sidebar when editing a page. If it's greyed out, the page is linked to a translation. Disconnect it from the default language page by following this guide: https://wpml.org/faq/how-to-disconnect-translations-from-the-default-language-page-or-post/, then change the page's language and reconnect it using this guide: https://wpml.org/faq/how-to-link-already-translated-pages/.

2. Ensure the Dashboard language switcher is set to the correct language when creating or editing content.

3. To restrict publishing capabilities for the Author role, use the “Save the translated post as a draft” option under WPML >> Settings >> Translated documents options. For more control, enable the “Wait for review” option under WPML >> Settings >> Automatic translation. For advanced role-based control, refer to: https://wpml.org/documentation/translating-your-contents/how-to-use-access-plugin-to-create-editors-for-specific-language/.

If these solutions do not resolve your issue or seem 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 at WPML support forum.

Problem:
The client is developing a custom plugin for a referral and commission system, which shows an error upon activation, suspecting a conflict with WPML. The client also inquired about the necessity of various WPML plugins listed in their setup.
Solution:
The error is not specifically related to WPML but to the early loading of translation files by plugins like ld-multilingual, learndash-certificate-builder, and learndash-memberpress. These plugins are loading translation files before WordPress is fully initialized, which can cause PHP notices and affect content translation and functionality. We recommend wrapping the translation file loading within an

init

action hook as follows:

add_action('init', 'my_plugin_load_textdomain');<br />function my_plugin_load_textdomain() {<br />    load_plugin_textdomain('my-plugin-slug', false, dirname(plugin_basename(__FILE__)) . '/languages');<br />}

Replace 'my-plugin-slug' with the actual text domain of your plugin and ensure the .mo/.po files are located in the /languages subdirectory.

If this solution does not resolve the issue or seems irrelevant due to updates or different circumstances, please 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. We highly recommend opening a new support ticket if the problem persists. For further assistance, visit our support forum at WPML support forum.

Problem:
The client needs to add German translations for over 1,000 existing product categories on their multilingual website, which are already translated into four languages. They attempted to import the German categories as translations of the Latvian terms using WP All Import, but the translations were not linked correctly.
Solution:
We recommend following the specific workflow outlined in our guide for importing multilingual content. Ensure that you use the WPML Export and Import add-on and adhere to the process described to correctly link the imported categories to the existing translations. You can find the guide here: Importing Multilingual Content.
If this method does not resolve the issue, another approach involves exporting all language data, ensuring the CSV file aligns with our documentation, and then re-importing each language. This should allow WPML to correctly connect the default language and its translations.
Alternatively, for manual assignment of a large number of categories, consider developing a custom code solution. Use our hook wpml_set_element_language_details to connect the German categories as translations of the default language.

If these solutions do not apply to your case, or if they 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.

Problème :
Vous souhaitez traduire des liens intégrés dans les Attributs personnalisés d'Elementor sur votre page d'accueil, mais vous ne parvenez pas à les traduire avec WPML.
Solution :
Nous avons identifié un code dans votre fichier

functions.php

qui gère les attributs

link|...

ajoutés aux colonnes Elementor. Pour résoudre ce problème, remplacez

home_url()

par le filtre WPML pour générer une URL adaptée à la langue :

$translated_url = apply_filters('wpml_home_url', home_url()) . $url;

Pour plus d'informations sur ce filtre, consultez https://wpml.org/wpml-hook/wpml_home_url/
Si vous avez besoin de compatibilité avec l'éditeur de traduction avancée de WPML, envisagez de déplacer les liens dans un champ texte ou widget standard d’Elementor et de les enregistrer via la configuration XML de WPML.
Si ces solutions ne fonctionnent pas, vous pouvez envisager d'utiliser un plugin comme https://wordpress.org/plugins/make-column-clickable-elementor/ ou de contacter un prestataire WPML pour une aide personnalisée : https://wpml.org/contractors/

Si cette solution ne vous semble pas pertinente ou si elle est 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 de support.