translatepress-email-notification-compatibility

TranslatePress Email And Notification Compatibility

TranslatePress can translate wp_mail() subject/body, store a user's preferred language, and translate WooCommerce emails in the customer/admin language. Plugin code must render emails in a stable language context and avoid one-email-many-languages shortcuts.

When to use this skill

Trigger when ANY of the following is true:

• A plugin/theme sends user-facing email or notification content through wp_mail(), WooCommerce emails, custom mail transports, cron, WP-CLI, webhooks, or async jobs.
• Code renders email templates before calling wp_mail() or sends directly through an API that bypasses wp_mail().
• The task mentions preferred user language, trp_language, trp_always_use_this_language, trp_translate(), trp_switch_language(), trp_restore_language(), trp_switch_to_preffered_language(), trp_whitelisted_shortcodes_for_wp_mail, trp_woo_email_language, WooCommerce Store API checkout emails, HPOS order meta, or "email text" in String Translation.

Baseline checks

Verify the installed stack:

wp plugin list --fields=name,status,version | grep -E 'translatepress|woocommerce'
wp eval 'echo defined( "TRP_PLUGIN_VERSION" ) ? TRP_PLUGIN_VERSION : "missing";'
wp option get trp_settings --format=json

TranslatePress Multilingual 3.2.1 hooks wp_mail at priority 1 through TRP_Translation_Render::wp_mail_filter(). WooCommerce email language support is initialized on init and requires WC_VERSION >= 6.8.0.

Prefer wp_mail for normal emails

If the plugin can use wp_mail(), do that. TranslatePress filters subject and message, runs whitelisted conditional language shortcodes, and switches to the first recipient's preferred language when that recipient is a registered user.

Good pattern:

$subject = __( 'Your certificate is ready', 'myplugin' );
$message = myplugin_render_email_template( $certificate_id );

wp_mail( $user->user_email, $subject, $message, array( 'Content-Type: text/html; charset=UTF-8' ) );