martinshopland

<ul>
<li>Sticky posts are ordered the same way as non-sticky posts.</li>
<li>Sticky posts do not reappear on subsequent pages.</li>
<li>The first page of home will contain exactly the requested number of posts, rather than the requested number of posts plus the number of sticky posts.</li>
<li>Allows more than one page of sticky posts.</li>
</ul>
<p>Simply injects the sticky post IDs into the actual mySQL order by clause,<br />
causing posts to be ordered by sticky status then by what ever order is<br />
specified, usually post_date DESC, and not to repeat on subsequent pages.<br />
I can’t actually figure out why it isn’t done like this by WP, perhaps<br />
earlier versions of mySQL don’t support this. WP’s default sticky ordering<br />
craziness is turned off by returning an empty array for the next call to<br />
get_option(‘sticky_posts’) which happens in WP_Query->get_posts().</p>
<p>There is currently a ticket awaiting review on the WordPress trac system to roll this functionality into the WordPress core: https://core.trac.wordpress.org/ticket/21986</p>


Mend Sticky Posts

Wordpress's Sticky Posts behaviour is still incomprehensible, let's fix it.

Pedro Mendonça

<h3>Use any Locale, with or without Language Packs</h3>
<p>With core Language Packs you can easily change the language of your WordPress install.</p>
<p>The Language Packs used to be provided only for 100% translated Locales.</p>
<p>To give teams with less contributors a better chance to get WordPress released into their Locale, since <a href="https://make.wordpress.org/polyglots/2021/02/22/wordpress-5-7-ready-to-be-translated/" rel="nofollow ugc">22nd February 2021</a> the required translation status for core Language Packs to be built are as follows:</p>
<ul>
<li>The <a href="https://translate.wordpress.org/projects/wp/dev/" rel="nofollow ugc">Front-end project</a> needs to be translated at least <strong>90%</strong>.</li>
<li>The <a href="https://translate.wordpress.org/projects/wp/dev/admin/" rel="nofollow ugc">Administration project</a> needs to be translated at least <strong>75%</strong>.</li>
<li>The <a href="https://translate.wordpress.org/projects/wp/dev/admin/network/" rel="nofollow ugc">Network Admin</a> and <a href="https://translate.wordpress.org/projects/wp/dev/cc/" rel="nofollow ugc">Continent & Cities</a> projects are not included in the threshold calculation.</li>
</ul>
<p>If you need a Locale that has no Language Packs yet, this tool helps you by enabling ALL Locales on the list of the available languages.</p>
<h3>Compatible with plugin <a href="https://wordpress.org/plugins/preferred-languages/" rel="ugc">Preferred Languages</a></h3>
<p>The plugin <a href="https://wordpress.org/plugins/preferred-languages/" rel="ugc">Preferred Languages</a> overrides the standard languages field for site and user languages.</p>
<p>All the features added by Translation Tools are available for Preferred Languages users.</p>
<h3>Update your WordPress, Plugins or Themes translation, on demand</h3>
<p>If you need to update your WordPress core, Plugins or Themes translations on demand without waiting for a language pack to be generated, this tool allows you to manually update all the needed files for the installed version, with one click, in a few seconds.</p>
<p>Go to “Translations” on the Updates screen and choose what you want to update.</p>
<h4>All WordPress core sub-projects</h4>
<ul>
<li>Development</li>
<li>Continents & Cities</li>
<li>Administration</li>
<li>Network Admin</li>
</ul>
<h4>All translation files</h4>
<ul>
<li>.po (editable translation files)</li>
<li>.mo (binary translation files)</li>
<li>.l10n.php (PHP performant translation files)</li>
<li>.json (JavaScript translation files)</li>
</ul>
<h3>WordPress Translations tests and info in Site Health</h3>
<p>Check your WordPress core translations in Site Health tests page.</p>
<p>The Site Health debug info shows the selected site and user languages, including multiple languages from the plugin Preferred Languages.</p>


Translation Tools

A fundamental tool for translators (and not only), works flawlessly.

Essential

The big difficulty when a plugin uses mostly JS is that the source files are minified. It is therefore very difficult to understand exactly where the string to be translated is.
This plugin allows to start the translation by validating and testing the strings locally little by little. Without waiting for 90%.

Essential plugin for translating plugins that use the block editor


This is a function that Wordpress should bring natively!


Excellent work

Translation tools for your WordPress install.

Mend Sticky Posts vs Translation Tools