Stalelingo – Outdated Translation Tracker for Multilingual Sites

开发者
更新时间	2026年10月2日 21:15
PHP版本:	8.1 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0

详情介绍:

When the source version of a post changes, its translations silently go out of date. Stalelingo fingerprints the source content every time a translation is marked as up to date. When the source changes, it flags each affected translation as outdated and shows exactly which fields changed. Stalelingo works with Polylang (including the free version) and WPML. One of them must be active. What it tracks

Title, content, excerpt, and optionally the slug and featured image.
Custom fields you choose, including ACF fields set to be translated.
Visible Elementor text (headings, text editors, buttons). Styling-only changes are ignored.
Formatting-only edits, such as whitespace or block attribute changes, are ignored unless you turn on strict mode.

Where you see it

A dashboard under Tools → Stalelingo, with a matrix of posts and languages, filters, bulk actions and CSV export.
A status column with one badge per language in your post lists.
A panel in the block editor (and a metabox in the classic editor) with a field-by-field diff and a Mark as up to date button.
An admin bar counter, and daily or weekly email digests for each translator.
WP-CLI commands for reports and bulk updates.

Stalelingo is completely free. There is no paid version, no license key and no tracking, and it makes no external requests. Privacy Stalelingo stores the ID of the user who marked a translation as up to date, and of the user whose action changed a translation's status. This data stays in your database. The plugin registers personal data exporters and an eraser (which removes the user from these records) and suggests text for your privacy policy. If you turn on email digests, the translators' email addresses are used to send them.

安装:

Install and activate Polylang or WPML, and set up your languages.
Install and activate Stalelingo.
Go to Settings → Stalelingo and choose the post types and fields to track.
Stalelingo builds a baseline in the background and treats every existing translation as up to date. After that, any change to a source post flags its translations.

屏幕截图:

升级注意事项:

1.0.0 First public release.

常见问题:

Which multilingual plugins are supported?

Polylang (free and Pro) and WPML. Stalelingo shows a notice on the Plugins screen if neither is active.

Why are all my translations "up to date" right after activation?

Stalelingo can't know what changed before it was installed, so the first baseline treats every existing translation as current. Changes are tracked from that point on.

Does it slow down saving posts?

No. Statuses are recalculated in the background after the save, using Action Scheduler when another plugin provides it, or WP-Cron otherwise.

Does it translate content?

No. Stalelingo tells you what needs updating. You or your translators update the translation as usual.

Which language is the source with Polylang?

Polylang treats translations as equals, so Stalelingo uses the source language from its settings, which defaults to Polylang's default language. You can override it for a single post.

How do email digests work?

In Settings → Stalelingo, assign translators to each language and choose a daily or weekly digest. Each translator gets a list of the outdated translations in their languages, with links to edit them. Addresses in "Also send the digest to" get every language. You can also email translators as soon as a translation of chosen post types goes out of date. Emails are sent with WordPress's own mail function, so an SMTP plugin applies to them too.

Which WP-CLI commands are there?

wp stalelingo report lists translations and their status (as a table, CSV or JSON), wp stalelingo mark-synced marks translations as up to date by ID or all at once, wp stalelingo baseline builds the baseline now (add --dry-run to preview it), and wp stalelingo recalc recalculates every status. Run wp help stalelingo for details.

Does it work on multisite?

Yes. Activate it on single sites, or network-activate it to set up every site, including sites created later. Each site has its own settings and data.

What happens to my data if I delete the plugin?

Nothing is deleted unless you turn on "Delete data on uninstall" in the settings. With it on, deleting the plugin removes its tables, settings and capability on that site.

Where is the source code of the JavaScript and CSS?

The src folder of the plugin holds the readable TypeScript and SCSS source of everything in build, which is compiled with @wordpress/scripts. The PHP code in includes is not compiled.

更新日志: