Incode Translate Master
| 开发者 | adrianincode |
|---|---|
| 更新时间 | 2026年9月4日 21:12 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Incode Translate Master makes your site bilingual from the front end — no account, no license key, no sign-up. Install it, pick your translation language, and start translating your real pages by clicking on the text you want to change, while you look at the actual design. A translation never breaks a button or a heading again.
A built-in keyless engine translates out of the box, so you can go from a single-language site to a published second language in minutes. Prefer your own provider? Plug in a DeepL, Google or Gemini key whenever you like and you pay the provider directly.
✨ Why you'll like it
- 🖱️ Translate what you see. Click text on your own page and translate it in context — headings, buttons, menus, image captions.
- 🔑 Works with zero setup. A free keyless engine translates immediately. No API key, no credit card, no account.
- 🚀 Not a trial. Everything described here is fully functional and never expires. Nothing is disabled waiting for a payment.
- 🔎 SEO-ready. Translations publish on their own URL prefix with reciprocal hreflang tags and a self-referencing canonical, so Google indexes them.
- ⚡ Fast. Translations live in your database and are served as plain HTML — no API call while a visitor loads the page.
- 🖊️ Visual front-end editor. Open your page, click any string, and edit the machine translation in the side panel while seeing the real layout.
- 📦 Batch translation. Send all pending strings with one click. The queue runs in batches, resumes where it stopped and never translates the same string twice.
- 🔬 Full-site scan. Extract every translatable string from your posts and pages at once and manage them from one screen.
- 💾 Auto-translate on save. New and changed texts of a post can be translated automatically in the background when you save, so the translation never lags behind the original.
- 🏷️ SEO title translation. With Yoast SEO installed, each page's meta title is translated so your translated pages show a title in their own language on search results.
- 🌐 Translation engines. Free keyless engine, or bring your own key for Google Translate, DeepL or Gemini. Switch engines any time without losing what's already translated.
- 🔀 Language switcher. Dropdown, list, flags or inline — as a shortcode, a theme widget, a menu item or an Elementor widget.
- 🧠 Translation memory. Every translated string is stored in your own database. If the same sentence appears in two hundred pages, the engine is called once.
- 🧱 Works with your stack. Any theme, Elementor and Elementor Pro, WooCommerce product and page text, and the usual caching plugins.
安装:
- Upload the plugin folder to
/wp-content/plugins/, or install the ZIP from Plugins → Add New → Upload Plugin. - Activate the plugin through the Plugins menu in WordPress.
- Go to Incode Translate Master → Languages and choose your translation language.
- Open any page of your site and use the toolbar link to start translating, or run a scan and translate in batch from Incode Translate Master → Strings.
屏幕截图:
常见问题:
Is this plugin a trial version?
No. Everything described here works with no key, no account and no expiry date. Nothing is time-limited or disabled waiting for a payment.
Is there a paid version?
Yes, and it changes nothing about this one. The free plugin is complete and permanent: original language plus one translation language, with every feature listed above. Pro adds more simultaneous languages, translated slugs, visitor language detection, a multilingual sitemap, Rank Math support and email translation. You can see it at wptranslate.es.
Do I need an API key?
No. A built-in keyless engine translates with no configuration. If you prefer, you can add your own key for Google Translate, DeepL or Gemini in Settings, so the translation cost is billed to you directly by the provider.
What languages does my site end up with?
Two: the original language your content is written in, plus the translation language you choose. The translation is published under its own URL prefix, and you can change the translation language whenever you want from the Languages screen.
Will Google index the translated versions?
Yes. The translated version is published under its own URL prefix, with reciprocal hreflang tags and a self-referencing canonical.
Does it slow the site down?
No. Translations are stored in your database and served as regular HTML. There is no API call while a visitor loads the page.
Does it work with Elementor and WooCommerce?
Yes. Elementor designs are read from their own JSON so no string is missed, including Elementor Pro widgets. For WooCommerce it covers product and page texts.
What happens to my translations if I remove the plugin?
They are yours. You can export them before uninstalling, and the uninstall routine asks whether to keep or delete the plugin tables.
更新日志:
2.9.1
- New (optional): the primary language can now be served under its own URL prefix, exactly like the secondary languages — for example the Spanish home at /es/ instead of /. The canonical, the hreflang x-default, the per-language sitemap and a 301 that consolidates the old unprefixed addresses all follow the prefixed URL, so a site migrating from another multilingual plugin that already publishes its primary language on a prefixed URL keeps the exact same structure and its existing indexing. Off by default: sites that serve the primary language at the root are completely unaffected.
- Fixed: the SEO integration could crash the Elementor editor. Yoast passes null through its title, description, canonical and OG-URL filters when there is no queried object — a Theme Builder template, the editor preview — and a non-nullable type hint turned that into a fatal error on PHP 8.
- Fixed: saving an API key could show "Settings saved!" and, right underneath, "Not configured" — with the key actually saved. The screen re-read the settings in a second request and, when that request failed, the failure was discarded silently and the old state was painted back.
- Fixed: the plugin never checked that its settings had really reached the database. It now re-reads them after writing and reports an honest error if they did not.
- Fixed: opening Settings fired seven requests at once. On shared hosting some of them lost their turn and the screen was painted half empty. It is now a single request.
- Changed: a failure to read the settings is now shown on screen instead of being mistaken for "nothing is configured".
- Changed: API settings are no longer loaded on every visit to the public site.
- Changed: the Pro notice now takes you straight to the licence it is offering, with it ready in the basket, instead of to a page of plans. Nothing changes in how the plugin translates.
- Fixed: on most pages the plugin was not telling Google that a translated version existed, so those translations were left out of the search index. The check that decided it counted only the strings currently filed under that page, and that filing moves on its own as the site is scanned.
- Fixed: "page not found" screens and search results announced a translated version of a page that does not exist.
- Fixed: pages built with Elementor filed their texts under a different key than the rest of the plugin, so the same sentence could be stored — and paid for — twice. Existing duplicates are merged automatically when you update.
- Fixed: bold text and links inside a paragraph were being stripped out when the paragraph was translated. Formatting is now put back into the translated sentence. If a link cannot be placed with certainty, the paragraph is left in the original language instead of published without its link.
- Fixed: any address containing the word "sitemap" was skipped, so pages like /blog/how-to-create-a-sitemap/ were never translated and never got a language prefix. Only real sitemap files are skipped now.
- Fixed: the visual editor showed strings as pending even when they were already translated, which invited overwriting good work. It now normalises text the same way the server does, and falls back to the context-free index.
- Fixed: auto-translate on save never ran in the block editor, which saves through the REST API. It now runs there too. Elementor keeps its own path and is unaffected.
- Fixed: the Pro notice was invisible on the plugin's own screens. It is now printed as an inline notice, so WordPress no longer moves it inside the app container where it was being wiped out on the first repaint.
- The notice shows the launch offer for Pro while it lasts, with a live countdown to the end date. When the offer is over the notice goes back to its normal text on its own, with no update needed.
- Countdown is driven by the server clock, so a wrong clock on the visitor's computer cannot make it run fast or slow.
- The new strings are translated into Spanish, French, German, Italian and Brazilian Portuguese.
- Added a dismissible notice about the Pro version, shown only to administrators, only on the Dashboard, the Plugins screen and the plugin's own screens, and only after the plugin has been installed for a week.
- The notice honours "prefers-reduced-motion" and remembers your choice per user: "Maybe later" hides it for 30 days and the ✕ hides it for good. Both preferences are removed when the plugin is uninstalled.
- Added a "Go Pro" link to the plugin's row in the Plugins list.
- 🌍 New: The whole plugin is now translatable, and ships translated into Spanish, French, German, Italian and Brazilian Portuguese.
- The admin interface, the setup wizard and the front-end visual editor now follow your WordPress language instead of always showing the same texts.
- Every user-facing string is internationalized with the
incode-translate-mastertext domain, including the JavaScript, so translate.wordpress.org contributors can translate it into any other language.
- Clearer bilingual model: the site has its original language plus one translation language, and changing it is now an explicit, documented action in the Languages screen.
- The memory limit is only raised while processing a confirmed large page or a heavy scan task, never globally.
- Hardened output escaping in the language switcher (wp_kses allowlist) and CSS color sanitization.
- The plugin is now called "Incode Translate Master".
- ✨ New: Auto-translate on save — new and changed texts of a post are translated automatically in the background when you save it.
- 🏷️ New: Yoast SEO integration — the meta title of each page is translated.
- 🌐 Improved: Translation engines — built-in keyless engine, or your own Google Translate, DeepL or Gemini API key, switchable any time.
- 🧭 Improved: Simpler language management.
- 🧙 New: Setup wizard on activation — pick your source language, choose the free engine (or your own key) and run the first scan, all in guided steps.
- 🎉 First release: front-end visual editor, full-site scan, batch translation, keyless free engine, translation memory, language switcher, and Elementor / WooCommerce support.