Per Søderlind

richardevcom

<p>Add Polylang support for Customizer</p>
<p>This plugin adds Polylang support for WordPress Customizer.</p>
<h3>Support</h3>
<p>We provide direct support via our <a href="https://discord.gg/ZptSdXMPrM" rel="nofollow ugc">Frontbee Discord server</a></p>
<h3>Features</h3>
<ul>
<li>Language switcher in Customizer.</li>
<li>Localized theme_mods and options for both default and custom made Customizer values.</li>
<li>Enable/disable forcing “The language is set from content” setting in Language->Settings->URL modifications</li>
</ul>
<h3>Prerequisite</h3>
<ol>
<li>Polylang must be installed and activated.</li>
<li>Languages must be set in <strong>Admin > Languages</strong>.</li>
<li><em>If you have a static front page</em>:
<ol>
<li><em>Create a front page per each language.</em></li>
<li><em>Select the front page in <strong>Admin > Settings > Reading</strong> per language.</em></li>
</ol>
</li>
<li>
<p>Expect customizer to use setting type = <code>theme_mod</code> (default) as in:</p>
<p>$wp_customize->add_setting( ‘setting_id’, [ ‘type’ => ‘theme_mod’, ] );</p>
<h3>License</h3>
<p>This plugin is licensed under the GPL v2 or later.</p>
</li>
</ol>
<blockquote>
<p>This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License, version 2, as published by the Free Software Foundation.</p>
<p>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.</p>
<p>You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA</p>
</blockquote>
<p>A copy of the license is included in the root of the plugin’s directory. The file is named <code>LICENSE</code>.</p>
<h3>Important Notes</h3>
<h3>Licensing</h3>
<p>This plugin is licensed under the GPL v2 or later; however, if you opt to use third-party code that is not compatible with v2, then you may need to switch to using code that is GPL v3 compatible.</p>
<p>Credits</p>
<p>Original solution made by <a href="https://github.com/soderlind" rel="nofollow ugc">@soderlind</a> is available <a href="https://github.com/soderlind/customizer-polylang" rel="nofollow ugc">here</a>. Share some love! This is WordPress plugin version of his solution.</p>


Add Polylang support for Customizer

I've been running around nuts searching for decent plugin-ready solution to add Polylang functionality to WordPress Customizer and ran across GitHub repository which had this solution. So I polished it and converted it to plugin.

Since then I have no need to manually add hooks, filters and additional scripts to add Polylang language support to Customizer.

This plugin does what it is supposed to do.

This plugin adds Polylang support for WordPress Customizer.

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.

Add Polylang support for Customizer vs Theme and plugin translation for Polylang (TTfP)