SimplePoTranslate -- WordPress 插件

开发者	simplepotranslate
更新时间	2026年6月17日 03:53
PHP版本:	8.0 及以上
WordPress版本:	7.0
版权:	GPLv2 or later
版权网址:	版权信息

SimplePoTranslate is the safest way to translate WordPress themes and plugins with AI — directly from your dashboard. It auto-detects every translatable theme and plugin on your site, translates into 39 languages, and writes ready-to-use .po/.mo files without touching a single line of your theme or plugin code. Unlike generic AI translators, SimplePoTranslate is built for gettext: it is designed to keep placeholders (%s, %1$s), HTML tags, and plural forms intact, so your strings stay valid after translation. Why developers and agencies choose it:

Auto-detect everything — Recursively scans every active theme and plugin and finds .po, .pot, and untranslated projects, with 3-layer name resolution that handles non-standard slugs (e.g. ACF Pro).
Translate many languages at once — Each language runs as its own job, so if one fails the rest still complete.
Built for gettext — Designed to preserve placeholders (%s, %1$s), HTML tags, and plural forms during translation.
Manual or automatic — Download, translate and upload the files yourself, or add an API key and click Auto Translate.
Inline string editor — Fix fuzzy and untranslated strings in your browser, filter by status, and save with one click.
POT file generation — Scan your plugin or theme source code and generate a fresh .pot template.
Safe imports — Upload a ZIP or a bare .po; an automatic backup is taken before every import and the .mo is compiled for you.
No subscription lock-in — A free tier plus an optional one-time plan; no recurring fee required.

Perfect for: Theme and plugin developers, freelancers, and agencies localizing WordPress, WooCommerce, LMS plugins (LearnDash, LifterLMS), and membership sites. Supported Languages: Turkish, Spanish, German, French, Italian, Portuguese (Brazil), Russian, Japanese, Chinese (Simplified), Korean, Arabic, Dutch, Polish, Ukrainian, Czech, Swedish, Danish, Finnish, Hungarian, Romanian, Greek, Thai, Vietnamese, Hebrew, Indonesian, Malay, Filipino, Hindi, Bengali, Urdu, Persian, Serbian, Croatian, Slovak, Bulgarian, Lithuanian, Latvian, Estonian, and Slovenian. How It Works:

Install and activate the plugin.
Navigate to SimplePoTranslate in the admin menu.
Scan your site to discover all translation files.
Choose your target languages and translate — either via the API or manually.
Import the translated files and your site is localized!

Upload the simplepo-translator folder to the /wp-content/plugins/ directory, or install the plugin through the WordPress plugins screen directly.
Activate the plugin through the 'Plugins' screen in WordPress.
Navigate to SimplePoTranslate in your admin menu to start scanning and translating.

For API-powered translations:

Go to SimplePoTranslate → Settings.
Enter your API key from simplepotranslate.com.
Return to the Scanner page and click Auto Translate to begin.

1.0.9 Security and data-integrity hardening release. No changes to the user interface or normal workflow.

Security: the translated-file download now refuses any address that is not the expected public HTTPS endpoint — internal/loopback/link-local targets are blocked, redirects are no longer followed, the download size is capped, and the API key is only ever sent to the API host. This prevents a compromised or spoofed API response from making the site request internal resources or leak the key (SSRF hardening).
Security: translation imports can no longer be tricked into writing a .po/.mo outside the plugin's own uploads directory via a crafted X-Domain header in an uploaded/translated file.
Security: deleting a translation is now restricted to files the plugin actually created (its uploads directory or recorded import jobs), so the delete action can never remove unrelated .po/.mo files elsewhere in the site.
Security: the String Editor now fully escapes translation text when rendering it, closing a cross-site-scripting vector that a maliciously crafted bundled .po file could otherwise trigger when an admin opened it for editing.
Security: "Full Reset", uninstall cleanup, and "Copy to system directory" now ignore symlinks inside the uploads directory, so a planted symlink can't cause a file outside the plugin's data to be deleted or copied.
Security: oversized files inside an imported ZIP are now rejected before extraction (decompression-bomb guard).
Fix: translations are no longer corrupted when editing/saving Windows-style (CRLF) .po files, which previously could be mis-parsed as a single block.
Fix: multi-line translations entered in the String Editor are now preserved (written as proper \n escapes) instead of being flattened or producing a malformed entry.
Fix: approving a fuzzy plural entry no longer overwrites every plural form with the same value; distinct plural forms are kept.
Fix: a translation job whose remote side stops responding is now automatically marked failed after several hours instead of keeping the background poller running indefinitely, and concurrent imports of the same job are prevented atomically.
Hardening: extra scan directories are validated to live inside wp-content/ before being saved.

1.0.8

Source-language .po files (e.g. a bundled en_US.po shipped by some plugins) are no longer treated as "untranslated" work. English is the source language and is intentionally not a translation target, so such files now show a neutral Source badge instead of a misleading 0%, are excluded from the "Has untranslated" group label, the menu status dot, the dashboard "all translated" check, and no longer offer an Auto Translate (wrench) action that would just error out. You can still open them in the String Editor to override the original wording. Auto Translate to en_US was already rejected server-side; this cleans up the confusing UI around it.
Fixed dashicon vertical alignment inside plugin buttons (Rescan, the API-key show/hide toggle, and similar). The icons could appear shifted/overflowing depending on the active WordPress version's button styling; they are now reliably centered next to their labels.

1.0.7

Confirmed compatibility with WordPress 7.0 — "Tested up to" raised to 7.0. The plugin's translation-loading hooks (load_textdomain_mofile, pre_load_textdomain, override_load_textdomain) and PO/MO handling were verified against WordPress 7.0's internationalization pipeline; no changes were required. Verified clean on PHP 8.0 through 8.5.
Fixed a String Editor bug where approving or saving a fuzzy entry whose #, flag line listed fuzzy after another flag (e.g. #, php-format, fuzzy) did not actually clear the fuzzy flag, so the entry kept re-appearing as fuzzy. The flag is now removed regardless of its position. The same hardening was applied to the import/merge path, and in both places a msgid or translation that literally contains the word "fuzzy" is never altered.
Performance: the scan results cache is no longer autoloaded — it is only needed on the plugin's admin pages, so it is kept out of the options data WordPress loads into memory on every front-end and admin request.
New admin notice when your saved API key can no longer be decrypted — this happens when the site's secret keys/salts are rotated (e.g. wp config shuffle-salts). Previously the key silently became unreadable and Auto Translate failed with a confusing "No API key" error; now you get a clear prompt to re-enter it.
Performance: the translation loader no longer re-scans the uploads directory twice per page load — the two safety-net passes now share a single directory scan.
Import diagnostics logging can now be turned off on production (define SIMPLEPO_DISABLE_IMPORT_LOG or add the simplepo_import_logging filter); it remains on by default so failures stay greppable in debug.log.
The background job poller now runs on demand: it is scheduled when you start a translation and automatically unschedules itself once no jobs are pending, so an idle site no longer runs an every-minute WP-Cron event (and database query) for nothing. Responsiveness while jobs are in flight is unchanged.
Minor internal hardening of the job-polling AJAX handler for consistency with the other endpoints (no functional change).
New one-time review prompt: after your first successful translation import, a dismissible notice on the plugin's own admin pages invites you to leave a review. It appears once, can be closed permanently, and never shows again after that.

1.0.6

New readme FAQ on translating the plugin's interface — points users to the official translate.wordpress.org project for community translations and shows how to use the plugin's own Auto Translate flow on its POT file as a fallback while their locale is still being translated.
Suppressed a Cannot modify header information PHP warning that could appear in debug.log on sites running with WP_DEBUG enabled. The plugin's admin pages now check headers_sent() before emitting the LiteSpeed cache-bypass header, so the header is sent when possible and quietly skipped when output has already begun (no functional impact either way).

1.0.5

Fixed a silent-failure case where a translation job that completed on the API side never had its .po/.mo written into the plugin uploads directory — e.g. after a PHP timeout, memory-limit exhaustion during ZIP extraction, or the browser tab being closed mid-import. Previously the affected job became an invisible "zombie" (status marked completed but no file on disk, hidden from the Translations page). v1.0.5 keeps the download URL on the row until the write is confirmed, wraps the entire import pipeline in try/catch so any fatal surfaces as a Failed row with an error message, and uses a transient lock to prevent duplicate imports.
New Retry Import action in the Translations page for any job whose file did not make it into the uploads directory (including jobs stuck by earlier versions). One click refetches a fresh download URL from the API and re-runs the import.
The Active Jobs panel now stays visible for at least 1.5 seconds even when the API responds instantly, so users always see that their translation was submitted.
Every step of the import pipeline (download, extract, resolve, write, recompile, DB update) is logged to wp-content/debug.log with a [SimplePoTranslate import] prefix, making failure diagnosis straightforward.
Scan Files and Translations pages now correctly group uploaded translation files under the parent plugin (not under a generic "plugins" header) and show a proper Uploads location badge.
String Editor now saves fuzzy entries whose suggested translation the user left unchanged (previously the save silently skipped them because the text hadn't been edited).
Manually-edited translations now show a delete icon on the Translations page (previously only API-imported files were deletable).
Translations page auto-runs a fresh scan when the cache is empty instead of showing a blank table.
Compatibility shim for plugins that bypass WordPress' translation API with their own custom MO loader (currently Smart Slider 3 Free and Pro, which use the Nextend framework's private Localization::$l10n cache and an {locale}.mo filename convention). The plugin does not write outside the uploads directory to support them; instead, after the third-party plugin has finished booting, we read our own uploads .mo and replace their in-memory translation cache via PHP reflection so our translations take effect on the frontend. The shim is scoped to one class, wrapped in try/catch, and a silent no-op on sites without Smart Slider 3 installed.

1.0.4

Removed every direct reference to the discouraged WordPress path constants (WP_PLUGIN_DIR, WP_CONTENT_DIR, WP_LANG_DIR, and WPINC). All filesystem paths are now derived from plugin_dir_path( __FILE__ ) and the public wp_upload_dir() / get_theme_root() APIs, which work correctly under relocated wp-content layouts, symlinked plugins, and Bedrock-style installs.
Translation API compatibility: fixed a backend provider issue that previously caused translation jobs to fail with "API reported status=failed" in some locales.

1.0.3

String Editor now supports editing .po files from any scanned location. When you edit a file stored in a plugin/theme bundle directory or in the v1.0.1 legacy system directory (wp-content/languages/), the plugin automatically copies it into the plugin uploads working area on first edit — your edits live there, the original file is never modified.
The Translations page now shows the underlying reason when a translation job fails (instead of just a "Failed" badge with no detail).
Import failures now update the job's DB row with a clear error message, making it possible to diagnose failed jobs without enabling WP_DEBUG.
Every step of the import pipeline now writes a structured [SimplePoTranslate import] log line to WordPress's error log, so the cause of any future import failure can be inspected with a single grep.
Dashboard surfaces a warning when the plugin cannot write to the uploads directory at activation (previously silent).

1.0.2

All generated .pot, .po, and .mo files are now written exclusively to wp-content/uploads/simplepo-translator/ (per WordPress.org plugin team guidance). The plugin no longer writes to wp-content/languages/ or any plugin/theme bundle directory during normal operation.
Translations activate transparently while the plugin is active: the built-in translation loader redirects WordPress's load_textdomain_mofile and pre_load_textdomain filters to the uploads location, so plugins with custom translation loaders (e.g. Smart Slider 3) continue to work.
New — Copy translations to WordPress system directory (Settings → Preserve translations): a one-click action that copies the contents of the plugin's uploads directory into wp-content/languages/plugins/ and wp-content/languages/themes/. Click this before deactivating or removing the plugin if you want your translations to keep loading afterwards. This is the only code path that writes outside the uploads area, and it runs only when the administrator explicitly triggers it.
Previous "bundle copy" compatibility feature removed; superseded by the translation loader redirect above.
Backup files now live in wp-content/uploads/simplepo-translator/backups/ (rotated per-file, 5 most recent kept).
Path-handling consolidated into a single internal helper (SimplePOTranslator\Paths); direct WP_PLUGIN_DIR / WP_CONTENT_DIR references reduced to 3 security/enumeration call sites with inline justifications.
String Editor now restricts in-place edits to files inside the uploads directory. v1.0.1 translations at wp-content/languages/plugins/ remain loadable but are read-only in the editor — re-import them to move into the new location.
Full Reset (Danger Zone) and uninstall now remove the uploads directory only; legacy wp-content/languages/ files are preserved in case WordPress core / GlotPress language packs share the directory.
Deactivation notice on the Plugins page now warns that translations in the uploads directory stop loading once the plugin is inactive and points the user to the new Copy-to-system action.

1.0.1

Disclosure: added External services and Privacy sections to the readme documenting the optional SimplePoTranslate API (what data is sent, when, and links to Terms and Privacy Policy).
Generated .pot files are now written to the WordPress system translations directory (wp-content/languages/plugins/ or wp-content/languages/themes/) so they survive plugin and theme updates.
Imported .po/.mo files from the Auto Translate API are always routed to the WordPress system translations directory; removed a fallback that could write to a plugin's bundle folder when a locale could not be derived.
Tightened the inline string editor's file path validation: edits are now restricted to files inside wp-content/languages/ or files discovered by a prior scan.

1.0.0

Initial release.
One-click file scanning for PO/POT files.
API-powered automatic translation for 39 languages.
Manual translation workflow with upload support.
Inline string editor for fuzzy and untranslated entries.
POT file generation from plugin/theme source code.
Multi-language simultaneous translation.
Automatic backup before import operations.
Safe uninstall — preserves all translation files.

SimplePoTranslate

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: