translatepress-output-compatibility

TranslatePress Output Compatibility

TranslatePress translates the rendered front-end page, plus gettext strings and dynamic strings it can detect. Build plugin/theme output as stable, accessible, server-rendered HTML first; then add explicit exclusions only for values that must never be translated.

When to use this skill

Trigger when ANY of the following is true:

• A plugin/theme must be "TranslatePress-compatible".
• User-facing text is generated by PHP templates, shortcodes, widgets, AJAX, REST, JS, WooCommerce templates, form builders, or page-builder integrations.
• Code uses dynamic labels, generated HTML fragments, language-specific caches, or strings that should be excluded from translation.
• The task mentions data-no-translation, data-no-dynamic-translation, data-no-auto-translation, trp_no_translate_selectors, trp_no_auto_translate_selectors, trp_skip_selectors_from_dynamic_translation, gettext strings, or TranslatePress automatic translation.

Baseline checks

Verify the installed stack before debugging compatibility:

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

TranslatePress Multilingual 3.2.1 and Business 1.8.2 are the validated versions for this skill. The Business loader blocks TranslatePress when the core version is below 2.8.7, shows a settings-redesign notice below 2.9.7, and loads add-ons from trp_add_ons_settings.

Make text discoverable

Render translatable text as real front-end text, not as opaque data:

printf(
    '<p class="myplugin-status">%s</p>',
    esc_html__( 'Your booking is confirmed.', 'myplugin' )
);

Use normal WordPress i18n functions for plugin/theme UI strings. TranslatePress can translate gettext strings, and site owners may also choose to disable TranslatePress gettext translation so .po/.mo files handle them.