tex0gen

<p>Translate your WordPress multisite network into multiple languages using AI language models.<br />
This plugin allows you to easily translate content across all sites in your WordPress multisite network while retaining the original formatting and structure.</p>
<p>It works out of the box with Gutenberg blocks and classic editor content, ensuring that all your content is translated accurately and efficiently.</p>
<p>Please note that this plugin requires the WordPress 7.0 AI Services API.<br />
The AI Services API requires an API key from any one of the supported providers and could incur costs based on usage. This plugin is designed to be a powerful tool for multilingual content management, but users should be aware of the potential costs associated with AI translation services.<br />
AI is not perfect and can make mistakes. Translations may not be perfect and should be reviewed for accuracy, especially for critical content. We recommend a full backup of your site before using the translation features, as translations overwrite existing content and cannot be undone without restoring a backup.</p>
<h3>ACF/ACF PRO Extension – Coming Soon</h3>
<p>If you are using Advanced Custom Fields (ACF) and want to translate custom fields, you will need to install the ACF extension for this plugin.<br />
This extension adds support for translating all ACF fields, including ACF Pro fields such as repeaters and flexible content.</p>
<h3>DIVI Extension – Coming Soon</h3>
<h3>Elementor Extension – Coming Soon</h3>
<h3>Filters and Actions for Developers</h3>
<p>This plugin includes several filters and actions that developers can use to extend its functionality. Plugin documentation will be available soon with details on how to use these hooks to customise the translation process, add support for additional content types, and integrate with other plugins and themes.</p>
<p>By default, only posts and pages are included in the bulk translation process. Developers can use the <code>aimstr_translatable_post_types</code> filter to restrict or extend the post types included in the translation process. This allows for greater flexibility and customisation when translating content across a WordPress multisite network.</p>
<p>To translate only posts (skipping pages and all custom post types):</p>
<pre><code>add_filter( 'aimstr_translatable_post_types', function( $post_types, $site_id ) {
    return [ 'post' ]; // Only translate posts, skip pages and CPTs
}, 10, 2 );
</code></pre>
<p>To include an additional custom post type (e.g. “service”):</p>
<pre><code>add_filter( 'aimstr_translatable_post_types', function( $post_types, $site_id ) {
    $post_types[] = 'service';
    return $post_types;
}, 10, 2 );
</code></pre>
<p>The <code>$site_id</code> parameter allows different post types to be specified per site, which is useful on networks where subsites have different custom post types registered.</p>


AI Multisite Translate

This plugin allows you to easily translate content across all sites in your WordPress multisite network.

Marcin Kazmierski

<h4>What is “Theme and plugin translation for Polylang”?</h4>
<p>Extension for Polylang plugin (Polylang is an extension to make multilingual WordPress websites.).<br />
Plugin is needed to translate the WordPress themes and plugins by Polylang.</p>
<h4>How to configure it?</h4>
<p>Select themes and plugins to find texts for translation by Polylang.<br />
In admin dashboard:</p>
<pre><code>Languages -> TTfP Settings
</code></pre>
<h4>How it is work?</h4>
<p>“Theme and plugin translation for Polylang” automatically searches all files of WordPress themes and plugins. It chooses from this file only those files with extensions:</p>
<ul>
<li>php</li>
<li>inc</li>
<li>twig</li>
</ul>
<p>In addition, is implemented the integration with Timber library (read more: http://timber.upstatement.com) – which allows to translate twig’s skins in simple way.<br />
Plugin in searched skins or plugins chooses texts from Polylang functions, such as:</p>
<ul>
<li>_e(string $text, string $domain = ‘default’);</li>
<li>__(string $text, string $domain = ‘default’);</li>
<li>_x(string $text, string $context, string $domain = ‘default’);</li>
<li>pll_e(string $text);</li>
<li>pll__(string $text);</li>
<li>esc_html(string $text);</li>
<li>esc_html_e(string $text, string $domain = ‘default’);</li>
<li>esc_html__(string $text, string $domain = ‘default’);</li>
<li>_n(string $single, string $plural, int $number, string $domain = ‘default’);</li>
<li>esc_attr_e(string $text, string $domain = ‘default’);</li>
<li>esc_attr__(string $text, string $domain = ‘default’);</li>
</ul>
<p>In your function.php, themes or plugins.</p>
<p>For example:</p>
<pre><code><p><?php pll_e('My text'); ?></p>

<p><?php _e('My another text', 'my_theme'); ?></p>
</code></pre>
<p>On the timber context declare this functions like:</p>
<pre><code>$context['pll_e'] = TimberHelper::function_wrapper('pll_e');

$context['pll_'] = TimberHelper::function_wrapper('pll_');
</code></pre>
<p>See more on: <code>https://polylang.wordpress.com/documentation/documentation-for-developers/functions-reference/</code><br />
These functions are defined by Polylang plugin for printing translations.<br />
Thanks “Theme and plugin translation for Polylang” you can find these strings to translate and add to Polylang register on very simple way.<br />
And then you can translate these texts from the admin dashboard.<br />
The scan result can be seen on the tab with translations:</p>
<pre><code>Settings -> Languages -> String translation
</code></pre>
<p>or</p>
<pre><code>Languages -> String translation
</code></pre>
<p>You don’t need programs like poedit – you don’t change files with extensions like: <code>.pot</code>, <code>.po</code>, <code>.mo</code>.<br />
“Theme and plugin translation for Polylang” is highly efficient because the scanner is worked only on admin dashboard in tab:<br />
In dashboard:</p>
<pre><code>Settings -> Languages -> String translation
</code></pre>
<p>or</p>
<pre><code>Languages -> String translation
</code></pre>
<h4>Export and import string translation</h4>
<p>In dashboard:</p>
<pre><code>Languages -> TTfP Settings
</code></pre>
<h4>Filter reference</h4>
<pre><code>ttfp_domains
</code></pre>
<p>Allows plugins and themes (in functions.php) to modify list of text domains (unique identifier for retrieving translated strings).<br />
List of text domains is displayed on “TTfP Settings” page to select them for translation by polylang engine.</p>
<p>Example:</p>
<pre><code>add_filter('ttfp_domains', 'custom_ttfp_domains', 10, 1);
function custom_ttfp_domains(array $domains):array
 {
     $domains[] = "my-custom-domain";
     return $domains;
 }
</code></pre>
<h4>Filter reference</h4>
<pre><code>ttfp_translation_access
</code></pre>
<p>Returns whether the user has capability to view and edit translations provided by TTfP.</p>
<p>Example:</p>
<pre><code>add_filter('ttfp_translation_access', 'custom_ttfp_translation_access', 10, 1);
function custom_ttfp_translation_access(bool $hasAccess):bool
 {
     return current_user_can('edit_posts');
 }
</code></pre>


Theme and plugin translation for Polylang (TTfP)


Great plugin and DEV, nothing more to say.


Great plugin and DEV


Works perfectly and very simple to use!


Works perfectly!

Theme and plugin translation using Polylang for WordPress. Extension for Polylang plugin.

AI Multisite Translate vs Theme and plugin translation for Polylang (TTfP)