| 开发者 | shinji3rd |
|---|---|
| 更新时间 | 2026年7月18日 10:56 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[zware_translate]./en/your-post/) with the content already translated in the HTML, so search engines can index them. Includes hreflang tags, a per-language canonical tag, and a dedicated cache so only the first visit to each translated URL needs to be translated — the rest are served straight from cache, without affecting the performance of the original site.zware-simple-translate folder to /wp-content/plugins/.No. It uses Google Translate's free widget, with no usage limits.
On purpose: so that a broken community translation can never cause a fatal error in your admin panel.
No. It only comes into play on URLs with a language prefix (/en/, /fr/, etc.). The site in its original language doesn't go through any extra processing. The first visit to each translated URL gets translated and cached; subsequent visits are served directly from that cache.
No. The plugin itself does not collect, store, or track any personal visitor data. See "External services" above for what is sent to Google when the switcher or the optional SEO mode is used.
<select> kept the color it had when the page first loaded instead of following the change, sometimes becoming unreadable (white text on a white background). The color is now continuously re-synced with the surrounding menu items as the page is scrolled.[zware_translate] shortcode, and optional automatic translation based on the visitor's browser language.hreflang and canonical tags, and a dedicated cache so the site's performance in its original language is unaffected.