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.

David Decker

deckerweb

wpautobahn

Creame

Pacotole

Brad Johnson

<p>Connect Polylang multilingual plugin with Elementor Page Builder: <strong>Translate your Elementor templates</strong> and show them in the correct language, native customizable <strong>Language Switcher Elementor widget</strong>, <strong>Visibility Conditions</strong> of widgets and <strong>Dynamic Tags</strong> by language and much more…</p>
<h3>What the Plugin Does</h3>
<h4>📍 Template translation and show in the correct language</h4>
<p>Create translations for your Elementor templates especially for header, footer or archive templates with <a href="https://be.elementor.com/visit/?bta=61741&brand=elementor&utm_campaign=wporg" rel="nofollow ugc"><strong>Elementor Pro Theme Builder</strong></a> <em>(affiliated link)</em>.</p>
<ul>
<li>Automatically selects the correct translation for <a href="https://elementor.com/help/template-widget-pro/" rel="nofollow ugc">“Template Widget”</a>.</li>
<li>Automatically selects the correct translation for <code>[elementor-template id="1234"]</code> shortcodes.</li>
<li>Allow Elementor Kit translation for different settings for each language.</li>
</ul>
<h4>🔄 Language Switcher</h4>
<p>A native Elementor Widget to easily build a nice and fully customizable language switcher:</p>
<ul>
<li>Show or hide flags, language name, language code.</li>
<li>Vertical list, Horizontal list or <strong>styled dropdown</strong>.</li>
<li><strong>SVG scalable flags</strong>.</li>
</ul>
<h4>👁️ Language Visibility Conditions</h4>
<p>Allow to <strong>show or hide every widget</strong>, section or column <strong>by language</strong>.</p>
<h4>🏷️ Language Dynamic Tags</h4>
<p>Use language dynamic tags (on Elementor Pro) that you can set with an specific language or the “current” one. Available tags are:</p>
<ul>
<li><strong>Language Code</strong> tag type text</li>
<li><strong>Language Name</strong> tag type text</li>
<li><strong>Language Url</strong> tag type url</li>
<li><strong>Language Flag</strong> tag type image</li>
</ul>
<h4>✏️ Elementor Editor integration</h4>
<p>Now you can view the language of the current template and change to its translations or create them <strong>from the Elementor editor</strong>.</p>
<h4>🔍 Elementor Finder integration</h4>
<p>From Elementor Finder you can access to Polylang settings pages and go the site in the selected language.</p>
<h4>🔨 Plugins integration fixes and tweaks</h4>
<ul>
<li>Automatically generate display conditions on new template translation.</li>
<li>Automatically generate Elementor CSS styles on create new template translation.</li>
<li>Fix home url to the current language on site-url Dynamic Tag and Search Form widget.</li>
<li>Add language url trailing slash.</li>
<li>Hide language on wp-admin for global widgets.</li>
<li>Other integration fixes.</li>
</ul>
<h3>How to use</h3>
<p>You can manage translated templates in two ways:</p>
<ul>
<li><strong>(recommended)</strong> create linked translations for a template and only set display conditions on the default language.</li>
<li>create separated translations for a template with their own display conditions.</li>
</ul>
<p>See an example:</p>
<pre><code>Site languages:
 - EN (main)
 - ES
 - IT

- Option 1 (linked translations only main language has display conditions):
╔═ Archive Template A (EN) -> condition category is "Red (EN)"
╠═ Archive Template A (ES) -> none (in front checks if category is ES translation of "Red (EN)")
╚═ Archive Template A (IT) -> none (in front checks if category is IT translation of "Red (EN)")

- Option 2 (not linked translations, all languages has display conditions):
══ Archive Template B (EN) -> condition category is "Red (EN)"
══ Archive Template B (ES) -> condition category is "Rojo (ES)"
══ Archive Template B (IT) -> condition category is "Rosso (IT)"
</code></pre>
<h3>Support</h3>
<ul>
<li><a href="https://wordpress.org/support/plugin/connect-polylang-elementor" rel="ugc"><strong>Plugin’s support forum</strong></a> here on WordPress.org</li>
<li><a href="https://github.com/creame/connect-polylang-elementor" rel="nofollow ugc">Github plugin repo</a></li>
<li><a href="https://www.facebook.com/groups/polylang.users/" rel="nofollow ugc">Polylang User Community Group at Facebook</a></li>
<li><strong>What is covered by our support?</strong> – All regarding <strong>THIS plugin</strong> (“Connect Polylang for Elementor”), plus the relation to <em>Polylang</em>, <em>Polylang Pro</em>, <em>Elementor</em> and <em>Elementor Pro</em> of course.</li>
<li><strong>What is NOT covered by support?</strong> – Anything general regarding multilingual topics and WordPress. Explicitely we <strong>DO NOT</strong> offer any “WPML”, “WPBakery” or “Visual Composer” support, and also not for your theme etc.!!!</li>
</ul>
<h3>Translations</h3>
<p>We have used the strings of Elementor and Polylang whenever possible to take advantage of the fact that they are translated into many languages. For the other strings a <code>.pot</code> file (<code>connect-polylang-elementor.pot</code>) for translators is also always included 🙂</p>
<p>You can collaborate with your language translations in <a href="https://translate.wordpress.org/projects/wp-plugins/connect-polylang-elementor" rel="nofollow ugc">Translating WordPress</a></p>
<h3>Credits</h3>
<p>The following code/classes are licensed under the GPL.</p>
<ul>
<li>v2. refactor and upgrade by <a href="https://profiles.wordpress.org/pacotole/" rel="nofollow ugc">Pacotole</a> at <a href="https://crea.me" rel="nofollow ugc">Creame</a></li>
<li>v2.1 Cross domain fixes based on work of <a href="https://profiles.wordpress.org/keraweb/" rel="nofollow ugc">Jory Hogeveen</a> and <a href="https://github.com/nicmare" rel="nofollow ugc">nicmare</a></li>
<li>Support <a href="https://profiles.wordpress.org/p4fbradjohnson/" rel="nofollow ugc">Brad Johnson</a></li>
<li>v1. released by <a href="https://profiles.wordpress.org/daveshine/" rel="nofollow ugc">David Decker</a></li>
<li>v1. Polylang Switcher class (Elementor Widget) and its CSS based on widget from plugin “Language Switcher for Elementor” by Solitweb (GPLv2 or later)</li>
<li>SVG flags from <a href="https://github.com/madebybowtie/FlagKit" rel="nofollow ugc">FlagKit</a> and <a href="https://wikipedia.org/" rel="nofollow ugc">Wikipedia</a></li>
</ul>
<p>Please, send your suggestions and feedback – Thank you for using or trying out this plugin!</p>


Connect Polylang for Elementor

very good

Connect Polylang with Elementor: translated templates, language switcher widget, language visibility conditions and more

Theme and plugin translation for Polylang (TTfP) vs Connect Polylang for Elementor