Ivan Paulin

<p>Custom field addon for Advanced Custom Fields plugin which provides a list of used WPML languages on website.<br />
Possibility to have multiple choices, or just one.</p>
<p>It will not work if WPML plugin is not activated.</p>
<p>Return type is array which holds the language code(it, en, fr, de, etc..).</p>
<h4>Compatibility</h4>
<p>This ACF field type is compatible with:<br />
* ACF 4<br />
* ACF 5</p>


Advanced Custom Fields: WPML Language Selector Field

Custom field addon for Advanced Custom Fields plugin which provides a list of used WPML languages on website.

Teemu Suoranta

<h4>Why this plugin exists?</h4>
<h4>Changing post’s or term’s language when it has translations messes things up</h4>
<p>Basically the translations are unlinked and there is no warning for this. You may need to change post’s language for example when you start to write a new post and notice that it’s in wrong language. When translations are involved, there’s really no use for changing the language.</p>
<h4>Users confuse adding translations and changing post’s language</h4>
<p>I’ve seen that users have multiple times changed post’s language when they meant to navigate to translation. Smartly disabling the select enhances the UI.</p>
<h4>Changing the posts language is risky business anyway</h4>
<p>Changing the language of post when it has content is prone to errors. Even though the language can be changed, the images added to content may still be in wrong language. Custom fields, relations etc are not automatically changed. Language should be changed right away before adding content.</p>
<h4>Changing the site default language is risky business anyway</h4>
<p>Changing the site default language is prone to errors. Even though the language can be changed, links in content may still be in wrong language. Custom fields, relations etc are not automatically changed. Language should be changed only if user knows what they are doing.</p>
<h4>What it does?</h4>
<ul>
<li>Checks if currently edited post or term has translations</li>
<li>If it has, hides select and shows the name of current language with CSS and vanilla JS</li>
<li>Removes option to change default language unless the user does not provide <code>iknowwhatimdoing</code> GET-parameter or allows it via filter</li>
</ul>
<h4>Composer:</h4>
<pre><code>$ composer require aucor/polylang-smart-language-select-disabler
</code></pre>
<h4>With composer.json:</h4>
<pre><code>{
  "require": {
    "aucor/polylang-smart-language-select-disabler": "*"
  },
  "extra": {
    "installer-paths": {
      "htdocs/wp-content/plugins/{$name}/": ["type:wordpress-plugin"]
    }
  }
}
</code></pre>
<h4>Filters</h4>
<p>You can disable select always or build some fancy custom logic:</p>
<pre><code>function my_polylang_disable_language_select($disable_select, $current_screen) {
    return true;
}
add_filter('polylang-disable-language-select', 'my_polylang_disable_language_select', 10, 2);
</code></pre>
<p>Allow default language change:</p>
<pre><code>add_filter('polylang-disable-default-language-select', '__return_true');
</code></pre>
<p>= Issues=</p>
<ul>
<li>No disabling for media (to-do)</li>
</ul>


Advanced Custom Fields: WPML Language Selector Field vs Smart Language Select Disabler for Polylang