| 开发者 | federicodev |
|---|---|
| 更新时间 | 2026年7月30日 22:33 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/it/, /de/) — friendly to SEO and to page caches.
You translate however you like:
/it/chi-siamo/) and hreflang tags.[translaterocket_switcher], a Gutenberg block, or a widget — inline, dropdown, or a scrollable bar with ‹ › arrows for many languages — with original SVG flags that render everywhere (including Windows). Show a switcher on desktop only, on mobile only, or both, to style a different menu for each.translate-rocket folder to /wp-content/plugins/, or install it from the Plugins screen.[translaterocket_switcher] shortcode, the block, or the widget.Yes. All translation features and unlimited languages are free, with no paid tier inside the plugin. You only ever pay your own AI provider, directly, if you choose to use AI.
No. You can translate entirely by hand, or for free using the built-in copy & paste with Google Translate. AI keys are optional and only used when you ask.
Yes. Translations are stored in your own WordPress database. Text is only sent to the AI provider you configure, at the moment you ask for a translation.
Yes. Each language lives under its own URL (e.g. /it/), so page caches store each language separately and automatically.
Yes — use TranslateRocket → Import to bring over your existing translations. The WPML import covers both its string translations and its post-based translations (titles, slugs and matching body text), and reads directly from WPML's tables, so it works even when WPML is already deactivated. Coming from Weglot (a hosted service)? Export your translations from the Weglot dashboard as a CSV and upload the file on the same Import screen — the columns are detected automatically and mapped to your target languages. To review the result safely, turn on Preview mode ("Who sees the translations" in Settings): you browse the fully translated site while visitors keep seeing the default language, and one click publishes it when you are happy.
Open the page and use the "Language visibility" box to redirect it, show a custom message, or return a 404 — per language.
<script>, <style> and <textarea> could lose its closing tags. Inline JavaScript that builds HTML ('<span><i></i></span>', .append('<li>…</li>'), document.write(…)) came out broken, and CSS using inline SVG data URIs (mask-image, background-image) lost the closing </svg>, so the shape silently failed to render. The page HTML parser treats those elements as raw text, and any </name> inside them was being dropped; their contents are now passed through untouched.trrocket_preview_capability filter lets you open the preview to other roles.translate="no" regions are now excluded from link localization./about/, or absolute with the site's own domain — common on migrated sites) are now localized on translated pages, so visitors no longer drop back into the source language on the first click. System paths (/wp-*), direct file links and URLs already carrying a language prefix are left untouched. Disable with the trrocket_localize_content_links filter.wp_kses() and an allowlist covering the plugin's SVG flags, icons and controls; the switcher's colour and size settings are validated at save time (hex colours, numeric-only sizes) so a value can never inject CSS; and the bulk string/translation deletes build their IN()/LIKE clauses through $wpdb->prepare().trrocket_page_collected action is available for add-ons.wp_enqueue_*, wp_add_inline_script, wp_add_inline_style) instead of being printed inline.libxml_disable_entity_loader() call and the no-longer-needed load_plugin_textdomain() (WordPress loads translations automatically).trrocket_flush_caches action for anything else — so a changed translation appears right away instead of waiting out their TTL.[translaterocket_poweredby] shortcode.