⬇ Download TranslateRocket v1.1.3
.zip · WordPress 5.6+ · PHP 7.4+ · GPLv2 · WordPress.org によって提供
1分でインストール
- WordPressの管理画面で、次のページに移動してください。 プラグイン→新規追加 そして検索してください TranslateRocket — または、ダウンロードした zip を次の方法でアップロードします。 プラグインのアップロード.
- クリック 今すぐインストール.
- 有効にする、開く TranslateRocket → 設定、言語を選んでください — 完了です。
What’s new in 1.1.3
- Fix: opening the media library to pick an image for a language left the little "Choose image" buttons — and the image window itself — floating on top of it, over an apparently empty panel. They now step out of the way while the library is open and come back when it closes, Escape included.
別のプラグインから来ていますか?移行ガイド: WPML · TranslatePress · Polylang.
ご質問や不具合については、こちらへ サポート — 実際の人間が対応します。
📦 変更履歴
積極的に開発中 — リリースされた内容は以下の通りです（新しいものから順に）。
v1.1.3
- Fix: opening the media library to pick an image for a language left the little "Choose image" buttons — and the image window itself — floating on top of it, over an apparently empty panel. They now step out of the way while the library is open and come back when it closes, Escape included.
v1.1.2
- Fix: a save that got no answer used to spin for ever. If your site did not reply — a proxy holding the connection, a dropped network, a security layer swallowing the request — the buttons kept turning with nothing on screen to explain it, and the sentence you had just written was lost if you gave up and closed the box. Requests now stop waiting after thirty seconds, your text stays in the box, and the message tells you whether the site refused the request (with the code) or did not answer at all.
- Fix: the window for swapping an image now opens in the middle of the screen and can be dragged, with the same title bar as the text editor. It used to appear glued to the picture — which for a full-width photo at the top of a page meant squashed against the top edge — and its header was drawn with styles that did not exist, so the title, the move handle and the close button ran into each other.
v1.1.1
- New: a language you add now starts offline. Until now, ticking a language and pressing save made it public that same second — in the switcher, in your sitemap, in your hreflang tags — with nothing translated in it yet. Now it arrives with its switch grey, and you turn it green when you are ready. A language that was already on your site keeps the state it had.
- New: the dashboard tells you when a page changed after it was last read. Text is detected while you look at a page while logged in — so if you edited a page in the block editor and never opened it again, its new sentences were never collected: they did not show up in your list of strings to translate, and on the translated pages they quietly stayed in your source language. That silence is over: the pages are listed by name, with a scan one click away, and the warning clears itself as soon as each page is read.
- Fix: on the Languages screen the per-language progress bar was drawn without a colour, so it looked empty even at 98%. It now runs red to green like every other bar in the plugin.
v1.1.0
- New: add a language now, publish it when it is ready. Next to every language you enable there is a switch: green means your visitors see it, grey means only you do. While a language is offline it stays out of the switcher, out of your sitemap and out of the hreflang tags, and anyone landing on one of its URLs is sent to your default language — but you keep working on it on the real pages, because whoever can preview still sees everything. Nothing half-translated ever reaches your visitors or Google.
- New: the SEO panel in the visual editor now holds everything search engines read, in one order: the address, the page title, the meta description, the social preview (Open Graph and X), the keywords, then every image on the page and every translatable attribute — titles, placeholders, ARIA labels. Each line takes you to the element: the page scrolls to it, it flashes, and the right editor opens. For a photo that means the image chooser; for its alt text, the text editor.
- Fix: the social texts were never translated. If a SEO plugin such as Yoast or Rank Math set an
og:title, anog:descriptionor atwitter:card of its own — a different text from the page title, which is the normal case — that text was never collected, so it could never be translated: every share of a translated page went out in the source language. Those texts are now collected like any other, and they show up in the SEO panel. - Thanks to Simona, for the first donation TranslateRocket ever received.
v1.0.0
- New: import from Bogo. It keeps one post per language, linked by two post meta values, so the pairing is exact — title, excerpt and body all come across.
- New: import from Multilanguage by BestWebSoft, read straight from its two tables, including category and tag names.
- New: import the translations you wrote by hand with Loco Translate — the
.po/.mofiles inwp-content/languages/loco/. Only your own work is read, not the language packs WordPress downloads by itself: those are thousands of strings nobody on your site chose, and they would bury the useful ones. Entries still marked "fuzzy" are skipped, because nobody has checked them yet. - New: a different image for each language. In the visual editor every picture carries a small button: click it and choose another image from the media library for that language. The picture is swapped on the translated page,
srcsetincluded — without that the browser quietly reloads the original and the change looks broken. Image addresses are kept apart from the text and are never sent to a translator: a URL comes back mangled and the picture disappears from the page. - Fix: the Import screen no longer scans every post each time it is opened. It asked each importer whether it had anything, and the qTranslate one had to look inside the posts to answer — on a large site that made the screen crawl. The answer is now remembered for an hour.
- Fix: in the switcher's live preview the dropdown was stuck open. You could see the menu's colours, but never how it opens — which is half of what a dropdown does. The preview now uses the same markup and CSS as the real switcher, so it opens and closes on click exactly like the one on your site.
- Fix: the three settings that only apply to the dropdown layout — how it opens, the arrow, the opening animation — are now switched off when you choose the inline or list layout, instead of looking live while doing nothing. Their values are kept, so changing layout no longer resets them.
- Fix: the live preview now follows you as you scroll the switcher settings, instead of scrolling away after the first section.
- With this release the plugin imports from ten other plugins, plus CSV and TMX.
v0.10.0
- New: import from the qTranslate family — qTranslate-X, qTranslate-XT, WPGlobus and WP Multilang. These keep every language inside the post itself, separated by markers, so the translations are read from your posts and not from the other plugin's tables: the import works even on sites whose plugin was deactivated or deleted years ago, which is the usual case for qTranslate. All four marker styles are recognised, including the HTML-escaped one. Titles, excerpts and body text come across; a post with no section in your source language is left alone rather than guessed at.
v0.9.9
- Change: on a phone the "translate in this browser" button is now shown but switched off, instead of hidden. Chrome and Edge only carry the on-device translator on a desktop, so the button cannot work there — but hiding it meant nobody browsing from a phone knew the feature existed at all. Tapping it now explains where to use it, and the copy-and-paste route beside it still works on a phone.
v0.9.8
- Fix: a browser translation run could reach the end of the progress bar having saved almost nothing. Chrome sometimes discards the on-device translator while a long run is going; from that moment every remaining phrase failed, silently. Measured on a 58-phrase page: 5 translated and 53 failed. The translator is now rebuilt on the first failure and the phrase retried, so the same run finishes 57 of 58 even when the browser drops it eleven times. On the bulk page the counter used to freeze ("Translating 5 of 498...") for the rest of the run; it now keeps going.
v0.9.7
- Fix: the "translate in this browser" button was offered on phones, where it cannot work — the browser translation API only exists on desktop Chrome and Edge. It showed up in the visual editor toolbar, in the phrase popup and on the bulk page, and tapping it got you nothing. The button is now hidden on phones and tablets; on the bulk page the copy-and-paste route stays available, since that one works everywhere.
v0.9.6
- Fix: on a phone, four of the plugin's nine screens ran off the side and the last columns of the tables were simply gone — progress per language, the list of pages, the AI summary. Measured at 390 pixels they overflowed by 116 to 220 pixels. The tables now use less padding and a smaller type on narrow screens, and whatever still does not fit scrolls inside the table itself instead of pushing the whole page sideways.
v0.9.5
- Fix: on a phone, the line that tells you which language your site is written in ran off the right edge of the toolbar, cut in half. It is the sentence that makes the whole bar make sense, so it now gets a row of its own and wraps like ordinary text instead of being clipped.
v0.9.4
- Fix: on a phone the editor toolbar had to be dragged sideways to reach its own buttons — with four languages and the controls it ran past a thousand pixels inside a screen of under four hundred. It now wraps onto as many rows as it needs, and the page below shifts by the toolbar's real height instead of a fixed 46 pixels.
- Change: the Live Preview demo is built for phones too — the cover text no longer sits on top of the photo, where it overflowed the frame and clipped the title and the second button.
有料プラグインから乗り換えますか。正直な比較をどうぞ: WPML の代わりに · TranslatePress の代わりに · Weglot の代わりに · GTranslate の代わりに
サイトのお手伝いが必要ですか? 私が引き受けます
私はフェデリコ、TranslateRocket を書いた者です。そして WordPress サイトを作って翻訳することが私の生業です。このプラグインが無料でいられるのはそのためです。アップグレードを売るために機能を削った版ではなく、報酬をいただいている仕事で毎日使っている道具そのものです。
ゼロから作る新しい多言語サイト、立て直すデザイン、いまあるサイトを一言語から十言語へ、目的に合わせた開発、見直した翻訳、毎月課金してくるプラグインからの移行。必要なことを教えてください。私が適任かどうか、正直にお答えします。相手をするのはサポートの行列ではなく、この仕組みを書いた本人です。
