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>


Multilingual Polylang

Jamie O

<p>See <a href="https://wordpress.org/extend/plugins/wpml2wpmsls/" rel="ugc">https://wordpress.org/extend/plugins/wpml2wpmsls/</a></p>
<p><a href="http://wpml.org" rel="nofollow ugc">WPML</a> stores each entry as a separate post and uses some custom tables to connect the translations.<br />
If you de-activate the plugin or have issues with functionality related to version updates, you get one site with multi-lingual confusion.<br />
See <a href="http://www.slideshare.net/r3df/getting-word-press-to-speak-your-langauge/" rel="nofollow ugc">Getting WordPress to speak your language</a> for more details how /<br />
why using a WordPress MultiSite / Network is becomming the recommended strategy for multilingual sites. At least until it is fully supported in core.</p>
<p>This plugin:</p>
<ul>
<li>Converts the WPML translation records into meta fields on actual posts or post types</li>
<li>Helps with the export/import to your new WPMS site the data.</li>
<li>Restores the meta data back to options so that <a href="https://wordpress.org/plugins/multisite-language-switcher/" rel="ugc">Multisite Language Switcher</a> will recognize all your translations.</li>
</ul>
<p>You will need to handle conversion of any strings, .po files or other language elements separately.</p>
<h3>Download</h3>
<p>You can download the latest stable version of WPML2WPMSLS from the WordPress<br />
Plugin Repository at <a href="https://wordpress.org/plugins/WPML2WPMSLS/" rel="ugc">https://wordpress.org/plugins/WPML2WPMSLS/</a>></p>
<h3>Help and Support</h3>
<p>Please post questions, request for help to the WordPress plugin forum dedicated to it: <a href="https://wordpress.org/support/plugin/WPML2WPMSLS" rel="ugc">https://wordpress.org/support/plugin/WPML2WPMSLS</a>.</p>
<h3>TO-DO’s</h3>
<p>= Complete the enhancements for WordPress export. =<br />
Currently, if you have 100 posts translated into 3 languages, you would export all posts once, import that same .xml file into 3 sites and delete the 200 from each<br />
site which are not the corresponding language. Then, you would be able to run steps 7 and 8 of the usage instructions above. With an enhanced WordPress export feature<br />
built into this plugin you would be able to specify the language for export to filter files. In that same scenario, you would run 3 exports (100 posts each of unique<br />
language) and import each language-based export file into the new sites before running the same steps 11 thru 13 above.</p>
<h3>Source and Development</h3>
<p>WPML2WPMSLS welcomes friendly contributors wanting to lend a hand, be it in<br />
the form of code through SVN patches, user support, platform portability<br />
testing, security consulting, localization help, etc.</p>
<p>The [current] goal is to keep the plugin self-contained (ie: no 3rd-party lib)<br />
for easier security maintenance, while keeping the code clean and extensible.</p>
<p>Active development for the plugin is handled via GitHub with releases being published to the WordPress Plugin Repository:</p>
<ul>
<li>Development: <a href="https://github.com/Idealien/wpml2wpmsls/" rel="nofollow ugc">https://github.com/Idealien/wpml2wpmsls/</a></li>
<li>Stable:     <a href="http://svn.wp-plugins.org/wpml2wpmsls/trunk/" rel="nofollow ugc">http://svn.wp-plugins.org/wpml2wpmsls/trunk/</a></li>
</ul>
<h3>Project History</h3>
<p>Originally started because, well, you know…<a href="http://www.howtogeek.com/102420/geeks-versus-non-geeks-when-doing-repetitive-tasks-funny-chart/" rel="nofollow ugc">Efficiency or lazyness – your pick</a>.</p>


WPML2WPMSLS

Convert posts from an existing WPML multilingual site via WP Import/Export to a WPMS (Network) with Language Switcher so easily it feels like magic!

Multilingual Polylang vs WPML2WPMSLS