bjoerne

WordPress plugin which redirects from the root site of a multisite project to a language specific network site.
Please Note: This plugin doesn’t allow content on the root site! Please read this description carefully to see if this works for you.
The decision which language should be used is based in the browser language of the user which is usually sent as ‘Accept-Language’ header (PHP: $_SERVER[‘HTTP_ACCEPT_LANGUAGE’]).
The plugin provides a configuration page where supported languages, redirect targets and the default language can be configured.
The plugin should be activated only on the root site. It shouldn’t be active on the language specific network site.
The plugin is developed on <a href="https://github.com/bjoerne2/language-redirect" rel="nofollow ugc">Github</a>. Feel free to fork the project or create pull requests.
This plugin was originally developed for <a href="http://www.monkkee.com/" rel="nofollow ugc">monkkee</a> and is inspired by <a href="http://oncleben31.cc" rel="nofollow ugc">oncleben31.cc</a>

Language Redirect

Great extension to Multilingual Press...
Just make sure you read correctly. Don't network activate the plugin. Only activate it at the root blog.



Works fine!

Redirects from the root site of a multisite project to a language specific network site.

Marcin Kazmierski

<h4>What is “Theme and plugin translation for Polylang”?</h4>
Extension for Polylang plugin (Polylang is an extension to make multilingual WordPress websites.). 
Plugin is needed to translate the WordPress themes and plugins by Polylang.
<h4>How to configure it?</h4>
Select themes and plugins to find texts for translation by Polylang. 
In admin dashboard:
<pre><code>Languages -> TTfP Settings
</code></pre>
<h4>How it is work?</h4>
“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:
<ul>
<li>php</li>
<li>inc</li>
<li>twig</li>
</ul>
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. 
Plugin in searched skins or plugins chooses texts from Polylang functions, such as:
<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>
In your function.php, themes or plugins.
For example:
<pre><code><?php pll_e('My text'); ?>

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

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

Language Redirect vs Theme and plugin translation for Polylang (TTfP)