Neutrope Translate Ease
| 开发者 | neutropeinc |
|---|---|
| 更新时间 | 2026年10月24日 12:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
TranslateEase helps WordPress site owners create and manage English translations without turning the whole site into a complex multilingual system.
It is designed for small sites that want to translate a limited number of Japanese pages or posts into English, review the translation, and publish only when ready.
Main features
- Create paired English translations for pages and posts.
- Manage original and English content from a dedicated Content Translations screen.
- Search original and English content by title or slug, and start translating from post and page lists.
- Edit translations in a side-by-side Translation Workspace.
- Use manual translation without any external API key.
- Optionally create English draft translations with DeepL API.
- Keep automatic translation output as draft until reviewed.
- Show a JP / EN language switcher on paired published content.
- Output hreflang alternates for paired published content.
- Preserve Gutenberg block structure during automatic translation.
- Preserve list structure and shortcode-only blocks such as form embeds.
- Service: DeepL API
- API endpoint used for Free keys: https://api-free.deepl.com/v2/translate
- API endpoint used for Pro keys: https://api.deepl.com/v2/translate
- DeepL Privacy Policy: https://www.deepl.com/privacy
- DeepL Terms: https://www.deepl.com/pro-license
安装:
- Upload the
neutrope-translate-easefolder to the/wp-content/plugins/directory, or install the plugin ZIP from the WordPress admin screen. - Activate TranslateEase from the Plugins screen. If the older TranslateEase plugin is active, deactivate it first. Existing translations and settings are reused. Do not delete the old plugin while its data deletion option is enabled.
- Go to TranslateEase > Settings.
- Enable TranslateEase.
- Use TranslateEase > Content Translations to create English translations.
- Optional: choose DeepL and enter a DeepL API key to enable automatic draft translation.
屏幕截图:
常见问题:
Do I need a DeepL API key?
No. You can create and edit English translations manually. A DeepL API key is only required for automatic draft translation.
Is content automatically published after translation?
No. Workspace automatic translation keeps the English version as a draft so you can review it before publishing.
Does TranslateEase translate the entire site automatically?
No. TranslateEase is designed for reviewed page-by-page and post-by-post translation. Translation covers page and post titles, content and excerpts. Text embedded in theme templates, custom data arrays or JSON, JavaScript-rendered views and custom URLs without a post are outside this scope. Preview the English version before publishing: a template may ignore the translated post content. Theme and custom data changes must be handled separately.
Can I use browser language redirection with a CDN or page cache?
TranslateEase sends cache prevention headers for language-dependent responses. A cache that serves a response before WordPress runs cannot be controlled by the plugin. Exclude affected URLs from caching or verify that the cache respects these headers. In a test environment, check Japanese and English visitors, saved language preferences and search bots, and ensure that one visitor's page or redirect is not served to another. TranslateEase does not change your cache configuration.
Does TranslateEase send visitor data to DeepL?
No. DeepL requests are only made from the WordPress admin area when an authorized administrator explicitly runs automatic translation.
Which languages are supported in the free version?
The free version is focused on Japanese source content and English translations.
Does TranslateEase support Contact Form 7 shortcodes?
TranslateEase preserves shortcode-only Gutenberg blocks during automatic translation so form shortcodes are not translated or modified.
更新日志:
0.8.7
- Explain translation scope and the need to preview theme and custom data output before publishing.
- Add CDN and page cache guidance beside browser language redirection settings.
- Explicitly prevent storage of language-dependent responses on older supported WordPress versions as well.
- Explain that disabling or deleting the plugin leaves published translations public, with a read-only review list.
- Show the /en/ parent status and editing and publication guidance without changing existing content.
- Correct Rank Math OG locale for managed English translations while preserving existing English regional locales.
- Respect the frontend OFF setting for language cookies and redirects.
- Default browser language redirection to OFF for new installations; preserve existing saved settings.
- Exclude known crawlers from automatic redirects and prevent caching of language-dependent responses.
- Set English HTML language attributes for managed translations.
- Output reciprocal hreflang links for published page and post pairs.
- Explain that a saved DeepL API key requires selecting the DeepL translation provider and saving settings.
- Show a warning when a key is saved but the provider is none, and a save reminder after selecting DeepL.
- Prevent duplicate constants, classes, and hooks when the legacy TranslateEase package is also active, including network activation.
- Show an administrator notice explaining how to switch from the legacy plugin without deleting translation data.
- Renamed the public plugin listing to Neutrope Translate Ease for WordPress.org review.
- Updated the plugin slug, text domain, and package root to neutrope-translate-ease.
- Replaced inline script output with WordPress enqueue and inline script APIs.
- Re-audited nonce and permission checks for admin actions.
- Updated WordPress.org submission metadata.
- Updated Tested up to value.
- Adjusted the public plugin title to align the intended translate-ease slug and text domain.
- Add title and slug search to the Content Translations screen.
- Show the post type name and slug for each item on the Content Translations screen.
- Add Create, Continue, and Edit English version row actions to post and page lists for original content.
- Add a workspace note reminding editors that form field shortcodes are managed by the form plugin.
- Prepare WordPress.org packaging and address Plugin Check findings.
- Update request handling in the Translation Workspace.
- Prefix uninstall variables.
- Update Tested up to header.
- Preserve shortcode-only Gutenberg blocks during DeepL translation to protect form embeds and similar shortcodes.
- Preserve list wrapper tags during DeepL translation so list items remain inside ul and ol elements.
- Protect Gutenberg block comments during DeepL translation so block structure is preserved.
- Translate content text segments while keeping wp:block markers unchanged.
- Decode DeepL HTML entities before saving translated title, content, and excerpt so the workspace stays readable.
- Add a safer workspace automatic translation handler with draft-only output.
- Return DeepL API errors to the workspace as admin notices instead of stopping on an error page.
- Add workspace guidance explaining that original title, content, and excerpt are sent to DeepL when auto-translation is used.
- Add contextual guidance, front-end links, and input placeholders to the Translation Workspace.
- Avoid front-end slug conflicts while English post translations are still drafts.
- Add a side-by-side Translation Workspace for posts and pages.
- Route Content Translations actions to the workspace.
- Support manual English draft editing, draft save, publish, and DeepL full auto-translate from the workspace.
- Add no-cost/manual setup guidance and switcher style previews.
- Add provider setup links to the automatic translation wizard.
- Add a beginner-friendly automatic translation setup wizard for DeepL.
- Add one-click create-and-translate actions to the Content Translations dashboard.
- Localize split metabox labels for Japanese admin users.
- Localize Content Translations and post editor metabox labels for Japanese admin users.
- Localize Settings body text and field labels for Japanese admin users.
- Localize remaining Settings section headings for Japanese admin users.
- Add live DeepL translation for titles, content, and excerpts.
- Apply the selected translation publishing mode after automatic translation.
- Keep Google provider reserved for a later version.
- Add a Content Translations dashboard for pages and posts.
- Show original content and English status side by side.
- Replace the old page-only translation menu label with a content-focused view.
- Hide translation entries from normal post and page lists by default.
- Add show and hide translation list links.
- Replace unavailable automatic translation actions with guidance when no provider is configured.
- Add translation publishing mode setting.
- Copy source content into English drafts.
- Add standard post support.
- Initial MVP skeleton.