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.

Aptivate

<p>This plugin, which requires <a href="https://wordpress.org/plugins/polylang/" rel="ugc">polylang</a><br />
provides the means to include posts that have no translation in the current<br />
language on pages of posts.</p>
<h4>Usage</h4>
<p>Multilingual Polylang provides two public functions:</p>
<p>The function <code>MultilingualPolylang::get_query()</code> returns a <code>WP_Query</code> object with posts from<br />
all languages but where there is a translated post, only the post in the current<br />
language will be included</p>
<p>The function <code>MultilingualPolylang::get_permalink()</code> can be used as a drop-in replacement to<br />
    get_permalink(). This will replace the language in a post URL so that a post<br />
can be viewed in a language different to that of the rest of the interface.</p>
<p><a href="https://github.com/aptivate/multilingual-polylang" rel="nofollow ugc">Follow this project on GitHub</a></p>
<h3>Development</h3>
<p>This plugin uses <a href="http://wp-cli.org/" rel="nofollow ugc">wp-cli</a> and <a href="https://phpunit.de/" rel="nofollow ugc">PHPUnit</a> for testing.</p>
<h4>Download the source code from GitHub</h4>
<pre><code>$ git clone git@github.com:aptivate/multilingual-polylang.git
</code></pre>
<h4>Install wp-cli</h4>
<p>If not already present, install <a href="http://wp-cli.org/#install" rel="nofollow ugc">wp-cli</a></p>
<h4>Install PHPUnit</h4>
<p>If not already present, install <a href="https://phpunit.de/" rel="nofollow ugc">PHPUnit</a></p>
<h4>Install the test WordPress environment</h4>
<pre><code>$ cd multilingual-polylang
$ bash bin/install-wp-tests.sh test_db_name db_user 'db_password' db_host version
</code></pre>
<p>where:</p>
<ul>
<li> <code>test_db_name</code> is the name of your <strong>temporary</strong> test WordPress database</li>
<li> <code>db_user</code> is the database user name</li>
<li> <code>db_password</code> is the password</li>
<li> <code>db_host</code> is the database host (eg <code>localhost</code>)</li>
<li> <code>version</code> is the version of WordPress (eg <code>4.7.5</code> or <code>latest</code>)</li>
</ul>
<h4>Run the tests</h4>
<p>From the plugin directory:</p>
<pre><code>$ phpunit
</code></pre>


Add Polylang support for Customizer vs Multilingual Polylang