<p>A really simple to use plugin which provides support for additional languages for your pages and posts. Does not work with custom post types and some themes.</p>
<p>Adds title and content edit boxes for each additional language on edit pages for posts and pages. Translation indicator available for post list on admin panel (can be turned off).</p>
<p>Includes widget and shortcode to generate language selection.</p>
<p>When a language is selected, displays all pages, posts and menus based on selected language. Different actions for untranslated content available in the settings.</p>


A Simple Multilanguage Plugin

Multilanguage support for pages and posts. Displays content based on selected language. Includes widget and shortcode for language selection.

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.

A Simple Multilanguage Plugin vs Theme and plugin translation for Polylang (TTfP)