Alexandre Gaboriau

<p>Automatic Translate Posts & Pages with <a href="https://www.deepl.com/" rel="nofollow ugc">Deepl</a>.</p>
<p>You need a Deepl API key to apply translations.</p>
<p>You can :</p>
<ul>
<li>Set your Deepl API key</li>
<li>Choose betweeen 9 languages : English, German, French, Spanish, Portuguese, Italian, Dutch, Polish, Russian</li>
<li>Translate chosen posts</li>
<li>Translate chosen pages</li>
<li>Translate chosen custom post type</li>
<li>Translate all posts in a category</li>
</ul>
<p><a href="https://www.deepl.com/privacy.html" rel="nofollow ugc">Privacy Terms of Deepl</a></p>
<h3>Translations</h3>
<ul>
<li>English</li>
<li>French</li>
</ul>
<h3>Support the plugin</h3>
<p>If you’ve found the plugin useful, please consider <a href="https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=contact%40magic-post-thumbnail.com&item_name=Donation+for+Magic+Post+Thumbnail&currency_code=EUR&source=url" rel="nofollow ugc">making a donation</a>. You can also visit my <a href="http://amzn.eu/cDuEDyU" rel="nofollow ugc">Amazon Wishlist</a>. Thank you for your support !</p>


Magic Post Translate

Automatic Translate Posts & Pages with Deepl

Yard | Digital Agency

Mike van den Hoek

<p>This plugin registers secure API endpoints that allow you to request translations directly from DeepL without exposing your Deepl API-key. These endpoints are only accessible when a valid nonce is provided. When providing translations to website visitors, you can configure which languages are supported for translation.</p>
<h3>Caching Mechanism</h3>
<p>Each object that is translated will store its cached translation in the <code>wp_postmeta</code> table within the database. This caching mechanism ensures that translations are efficiently reused, reducing unnecessary API requests to DeepL and saving costs.</p>
<ul>
<li>Serving Cached Translations: If a cached translation is newer than the <code>post_modified</code> date of the object, the cached version is served.</li>
<li>Fetching New Translations: When the <code>post_modified</code> date of the object is more recent than the cached translation, a new translation is fetched from DeepL. Once retrieved, this translation is immediately cached for future use.</li>
<li>Cache Authorization: Only logged-in users with the <code>edit_posts</code> capability (or a custom capability configured via the <code>yard::deepl/cache_capability</code> filter) are permitted to create new cache entries. Requests from users without this capability will still return a translation from DeepL, but the result will not be stored in the cache.</li>
</ul>
<p>This approach minimizes the number of API calls to DeepL, ensuring translations are kept up to date only when necessary.</p>
<h4>Admin: Cache Metabox</h4>
<p>A metabox labeled Yard DeepL is displayed on the edit screen of supported post types (default: page). It provides two options:</p>
<ul>
<li>Disable translation cache: When checked, the cache is bypassed for this object. Useful for posts with dynamic content that should always be translated fresh.</li>
<li>Clear translation cache: When checked and the post is saved, all cached translations for this object are deleted.</li>
</ul>
<h4>Admin: Translation Cache Column</h4>
<p>A Translation cache column is added to the post list screen of all supported post types. Its purpose is to notify editors which posts should be cached as soon as possible to avoid unnecessary DeepL API costs.</p>
<ul>
<li>Green badge per language (e.g. NL, EN-US): a valid, up-to-date cached translation exists for that language. Visitor requests are served from cache at no cost.</li>
<li>Grey badge with a count per language (e.g. EN-US 42): no cache exists for that language and visitors have triggered that many live DeepL API calls. Hovering the badge shows the full count as a tooltip. These posts are the most urgent to cache.</li>
<li>—: the post has never been requested for translation, or caching is disabled for this post.</li>
</ul>
<p>The uncached call count is only incremented for visitor requests (users without cache-write capability) and is automatically reset per language once a cache entry is stored. Posts with the Disable translation cache option enabled are excluded from the column entirely.</p>
<h3>External Services</h3>
<p>This plugin connects to the DeepL API to provide translations for content.</p>
<ul>
<li><strong>Service:</strong> DeepL API (https://www.deepl.com)</li>
<li><strong>Purpose:</strong> To translate text from one language to another based on the provided target language.</li>
<li><strong>Data Sent:</strong> Text content for translation, the target language code, and the DeepL API key (handled securely and never exposed to users).</li>
<li><strong>Conditions:</strong> Data is sent when a request for translation is initiated.</li>
<li><strong>Privacy Policy:</strong> <a href="https://www.deepl.com/privacy" rel="nofollow ugc">DeepL Privacy Policy</a></li>
<li><strong>Terms of Service:</strong> <a href="https://www.deepl.com/pro-license" rel="nofollow ugc">DeepL Terms of Service</a></li>
</ul>
<h3>Usage</h3>
<h4>Security</h4>
<p>The API endpoints registered by this plugin are secured using a WordPress nonce. The nonce is passed to the front-end using the <code>wp_localize_script</code> function and is stored in a global JavaScript object <code>ydpl</code> which contains the following properties:</p>
<ul>
<li><code>ydpl_translate_post_id</code>: The ID of the post to be translated.</li>
<li><code>ydpl_rest_translate_url</code>: The URL of the API endpoint for translation requests.</li>
<li><code>ydpl_supported_languages</code>: The list of languages supported for translation.</li>
<li><code>ydpl_api_request_nonce</code>: The nonce used for API validation.</li>
</ul>
<p>When making requests to the API, ensure that the nonce is included in the request headers. The header should be named <code>X-WP-Nonce</code>, and it should contain a nonce created with the <code>wp_rest</code> action (available via <code>ydpl.ydpl_api_request_nonce</code> on the front-end).</p>
<p>Rate limiting: Unauthenticated requests (or requests from users without the cache capability) are limited to 3 requests per 60 seconds per IP address. Authenticated users with the required cache capability (default: edit_posts) are exempt from this rate limit.</p>
<p>Cache capability: Only users with the <code>edit_posts</code> capability can trigger cache creation. This can be customized using the <code>yard::deepl/cache_capability</code> filter.</p>
<h4>Example</h4>
<p>Request:</p>
<pre><code>var xhr = new XMLHttpRequest();
xhr.open('POST', ydpl.ydpl_rest_translate_url, true);

// Set request headers
xhr.setRequestHeader('Content-Type', 'application/json');
xhr.setRequestHeader('X-WP-Nonce', ydpl.ydpl_api_request_nonce);

// Handle response
xhr.onreadystatechange = function () {
    if (xhr.readyState === 4 && xhr.status === 200) {
        console.log('Translation:', JSON.parse(xhr.responseText));
    } else if (xhr.readyState === 4) {
        console.error('Error:', xhr.statusText);
    }
};

// Prepare and send the request body
var data = JSON.stringify({
    text: ["Look another test"],
    target_lang: "DE"
});

xhr.send(data);
</code></pre>
<p>Response:</p>
<pre><code>[
    {
        "text": "Look another test!",
        "translation": "Sehen Sie sich einen weiteren Test an!"
    }
]<h3>Filters</h3>
</code></pre>
<p>* <code>yard::deepl/cache_capability</code> (default: <code>edit_posts</code>) — The WordPress capability required to create cache entries. Users without this capability receive translations but results are not cached.<br />
* <code>yard::deepl/cache_metabox_post_types</code> (default: <code>['page']</code>) — Post types on which the Yard DeepL cache metabox is displayed.<br />
* <code>yard::deepl/disable_cache_metabox_post_types</code> — Deprecated. Use <code>yard::deepl/cache_metabox_post_types</code> instead.</p>


Yard DeepL

This plugin registers secure API endpoints that allow you to request translations directly from DeepL without exposing your DeepL API-key.

Magic Post Translate vs Yard DeepL