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.

Marcus (aka @msykes)

Marcus

Pixelite

<p>This plugin helps make <a href="https://wordpress.org/extend/plugins/events-manager/" rel="ugc">Events Manager</a> and <a href="http://wpml.org" rel="nofollow ugc">WPML</a> work better together by allowing translation of all event-related features:</p>
<p>** Version 2.0 is a major revamp that fixes <em>all known issues</em>, nuances and limitiation. 2.0 enables <em>full compatiblity</em> with <a href="https://wordpress.org/extend/plugins/events-manager/" rel="ugc">Events Manager</a> and <a href="https://eventsmanagerpro.com" rel="nofollow ugc">Events Manager Pro Add-ons</a> **</p>
<ul>
<li>Detects translated pages of specific EM pages (assigned in Events > Settings > Pages) and displays relevant language content</li>
<li>Searching locations and events within the context of the current language being viewed.</li>
<li>Recurring events can be created in multiple languages, recurrence translations are correctly created.</li>
<li>Event translations will share relevant information across all translations, including
<ul>
<li>Event Times</li>
<li>Location Information</li>
<li>If translations for the location exist, translated events will show/link to location of the same language, if not the original location translation.</li>
<li>Bookings and Booking Forms</li>
<li>If you delete an event that is the originally translated event, booking and other meta info is transferred to default language or next available language translation.</li>
</ul>
</li>
<li>Location address information can be translated, whilst sharing coordinate, country/zip information accross translations.</li>
<li>Event-related text can be translated for each language including:
<ul>
<li>Custom texts, emails templates and formats on the settings page.</li>
<li>Booking and attendee custom forms (available in Pro)</li>
<li>Custom event and gateway emails (available in Pro)</li>
</ul>
</li>
<li>MultiSite cross-site support, including showing events from other blogs in your network when EM Global Tables Mode is enabled.</li>
<li>Displaying untranslated items in lists or hiding them, according to WPML settings.</li>
</ul>
<h4>Special Installation Steps</h4>
<p>Please ensure that WPML 4.2 and EM 5.6.7 or higher are installed BEFORE updating or activating this plugin.</p>
<p>When setting up EM and WPML, you should create translated versions of the event, location, category, tag, etc. pages assigned in Events > Settings > Pages of your admin area. Duplicating them using WPML is enough.</p>
<p>Given the flexibiltiy of both plugins, there is an huge number of possible setting/language combinations to test, and despite our rigorous testing it is impossible to test every setting combination and scenario. To the best of our knowledge, we have achieved 100% compatibility, but should you come across on your setup and we’ll do our best to fix them as time permits.</p>


Events Manager and WPML Compatibility

If you have WPML and use Events Manager, this is a must. Works perfect. There are some (very few) parts that are not translatable yet, but 95% of the strings are translatable.

Must-have

Integrates the Events Manager and WPML plugins together to provide a smoother multilingual experience (Requires Events Manager and WPML activated)

Theme and plugin translation for Polylang (TTfP) vs Events Manager and WPML Compatibility