tex0gen

Translate your WordPress multisite network into multiple languages using AI language models. 
This plugin allows you to easily translate content across all sites in your WordPress multisite network while retaining the original formatting and structure.
It works out of the box with Gutenberg blocks and classic editor content, ensuring that all your content is translated accurately and efficiently.
Please note that this plugin requires the WordPress 7.0 AI Services API. 
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. 
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.
<h3>ACF/ACF PRO Extension – Coming Soon</h3>
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. 
This extension adds support for translating all ACF fields, including ACF Pro fields such as repeaters and flexible content.
<h3>DIVI Extension – Coming Soon</h3>
<h3>Elementor Extension – Coming Soon</h3>
<h3>Filters and Actions for Developers</h3>
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.
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.
To translate only posts (skipping pages and all custom post types):
<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>
To include an additional custom post type (e.g. “service”):
<pre><code>add_filter( 'aimstr_translatable_post_types', function( $post_types, $site_id ) {
 $post_types[] = 'service';
 return $post_types;
}, 10, 2 );
</code></pre>
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.

AI Multisite Translate

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

Pascal Birchler

Thanks to language packs it’s easier than ever before to change the main language of your site. 
However, in some cases a single locale is not enough. When WordPress can’t find a translation for the active locale, it falls back to the original English strings. 
That’s a poor user experience for many non-English speakers.
This feature project aims to change that by letting users choose multiple languages for displaying WordPress in. 
That way you can set some sort of “fallback chain” where WordPress tries to load translations in your preferred order.
Please help us test this plugin and let us know if something is not working as you think it should.
Keyboard Shortcuts
<ul>
<li><code>Arrow Up</code>: Move selected locale one position up.</li>
<li><code>Arrow Down</code>: Move selected locale one position down.</li>
<li><code>Home</code>: Select first locale in the list.</li>
<li><code>End</code>: Select last locale in the list.</li>
<li><code>Backspace</code>/<code>Delete</code>: remove the selected locale from the list.</li>
<li><code>Alt+A</code>: Add the current locale from the dropdown to the list.</li>
</ul>
Note: the Preferred Languages UI needs to be focused in order for the keyboard shortcuts to work.
Merging Translations
Previously, only the first available translation for a given locale and domain will be loaded. 
However, when translations are incomplete, some strings might still be displayed in English. 
That’s a poor user experience as well.
To prevent this, Preferred Languages now automatically merges all incomplete translations in the list.
the <code>preferred_languages_merge_translations</code> filter can be used to opt out of this behavior. 
It provides three parameters:
<ol>
<li><code>$merge</code> – Whether translations should be merged. Defaults to <code>true</code>.</li>
<li><code>$domain</code> – The text domain</li>
<li><code>$current_locale</code> – The current locale.</li>
</ol>
<h4>Get Involved</h4>
Active development is taking place on <a href="https://github.com/swissspidy/preferred-languages" rel="nofollow ugc">GitHub</a>.
If you want to get involved, check out <a href="https://github.com/swissspidy/preferred-languages/issues" rel="nofollow ugc">open issues</a> and join the <a href="https://wordpress.slack.com/messages/core-i18n" rel="nofollow ugc">#core-i18n</a> channel on <a href="https://wordpress.slack.com/" rel="nofollow ugc">Slack</a>. If you don’t have a Slack account yet, you can sign up at <a href="https://make.wordpress.org/chat/" rel="nofollow ugc">make.wordpress.org/chat/</a>.

Preferred Languages

Esto es imprescindible para cualquier usuario no angloparlante. El estado de las traducciones es irregular y sería perfecto tener un segundo e incluso un tercer idioma local para cargar si algo falta en tu idioma local, y así que no salga media web en español - por ejemplo - y el resto en inglés.

Esto ya estaría en WordPress si los principales equipos de desarrollo no fuesen angloparlantes, y claro, para ellos no es una prioridad ni de lejos.

Imprescindible - Debería estar ya en WordPress

Thanks for Pascal to solve the problem of fallback languages. It is time to add it to the core and would show that WordPress is thinking globally.

In core, please

I think this should be in Core for websites with several possible languages. I like it very much! Specially I appreciate that each user can also choose languages from the selected languages. 
(I am developing a translation plugin for my own needs to use Google Translate to translate posts/pages and complement it.)

Very necessary in core


I honestly think that this should be a core feature of WP. 



The only thing wrong I notice is that when you are looking at the front end... The language of the admin bar changes into the site language but that's the only issue I have with this plugin at the time of writing. For the rest, it's a dream plugin.


Make this a core feature

Should be in the core!

Choose languages for displaying WordPress in, in order of preference.

AI Multisite Translate vs Preferred Languages