SkyLang Auto Translator for Polylang
| 开发者 | siteskyline |
|---|---|
| 更新时间 | 2026年5月18日 02:44 |
| PHP版本: | 5.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
SkyLang is an essential tool for any website using the Polylang plugin. It eliminates the tedious process of manually creating translations for your content. With a single click, you can generate translations for all your languages directly from the posts screen.
Key Features
- One-Click Auto-Translation: Translate any post or page into all your Polylang languages with a single click.
- Bulk Translation: Translate multiple posts at once from posts screen or the dedicated Bulk Editor.
- Bulk Editor: Full-featured bulk editing interface with folder filtering (post types, categories, tags, product categories, product tags, product brands), pagination, multi-language progress view, and inline controls.
- WooCommerce Support: Auto-translate products, product categories, product tags, brands, and product variation descriptions alongside standard content.
- Elementor Compatible: Deep copy preserves Elementor layouts, custom fields, categories, tags, and featured images.
- SEO Meta Translation: Automatically translate meta descriptions and titles from Yoast SEO, Rank Math, and All in One SEO.
- String Translation: Automatically translate strings from your theme and plugins.
- Category & Tag Sync: Auto-assign translated categories/tags/product taxonomies during translation or run a one-shot sync across all posts and products. New terms created in target language if no translation exists.
- Menu Sync: Duplicate navigation menus across all Polylang languages. Links to posts, pages, and categories map to their translations.
- Translator Mode: Quickly regenerate un-translated posts for any language with the translator modal from the posts screen.
- Configurable Post Types: Enable/disable which post types appear in SkyLang via settings.
安装:
- Upload the
skylang-auto-translatorfolder to the/wp-content/plugins/directory. - Activate the plugin through the 'Plugins' menu in WordPress.
- Go to Settings > SkyLang: Auto translator for Polylang and choose your translation engine.
常见问题:
Where can I get an API key?
The free version uses Google Translate and does not require an API key. If you upgrade to SkyLang Pro, you can connect your own AI providers:
- Google Gemini: https://aistudio.google.com/
- OpenAI: https://platform.openai.com/api-keys
- Anthropic: https://console.anthropic.com/settings/keys
Is the API free to use?
The free version includes Google Translate with no separate AI API setup required. If you use Pro AI engines, pricing depends on the provider you connect, such as Google Gemini, OpenAI, or Anthropic.
Does this work with other page builders?
Yes, SkyLang is designed to work with any page builder that stores its data in custom fields. It has been tested with Elementor, but it should work with other popular page builders as well.
更新日志:
2.0.2
- New: WooCommerce Support — Full integration for WooCommerce product translation
- New: Products appear in Bulk Editor folder filter alongside posts and pages for easy translation
- New: Product categories (
product_cat), product tags (product_tag), and product brands (product_brand) added as term-mode folders with full bulk actions - New: Product variation short descriptions auto-translated when translating a product
- New: WooCommerce taxonomies included in Category, Tag & Product Taxonomy Sync tool
- Enhancement: Settings labels and tool descriptions updated when WooCommerce is detected
- Enhancement: Taxonomy Sync now processes product taxonomies alongside categories and tags
- New: Menu Sync tool — duplicate navigation menus across all Polylang languages with automatic mapping of posts, pages, and categories to their translations
- New: Menu Sync button in Bulk Editor toolbar and Tools tab for one-shot sync
- Enhancement: Menu items keep original link when no translation exists for the linked content
- Enhancement: Polylang language switcher menu items preserved during sync
- New: Categories and Tags in Bulk Editor — filterable alongside posts and pages with full bulk actions (translate, delete, reassign language)
- New: Auto-sync categories & tags during translation — optional setting in SkyLang Settings tab to automatically create and assign translated category/tag terms when translating posts
- Enhancement: Categories column removed from Bulk Editor table for cleaner layout
- Fix: Auto-sync now correctly assigns created terms to translated posts (language is set before taxonomy sync)
- Fix: Category/Tag filter in Bulk Editor now shows only default-language terms, matching post/page filter behavior
- New: Full post_content AI translation mode — sends complete post content to AI for context-aware translation while preserving Gutenberg blocks, HTML, and inline styles
- New: OpenRouter provider support (Pro) — bring your own OpenRouter API key and model selection
- New: OpenAI-compatible URL provider support (Pro) — connect any OpenAI-compatible endpoint
- New: Custom base URLs for OpenAI and Anthropic (Pro) — use proxy endpoints or self-hosted gateways
- New: Bulk delete translations — remove all non-source translations for selected posts in Bulk Editor
- New: Bulk language reassignment — change Polylang language for selected posts in Bulk Editor
- New: Configurable post type support — enable/disable which post types appear in SkyLang via settings
- New: Translation mode selector in settings — toggle between safe string extraction and full AI translation
- New: HTML comment preservation — comments in content are preserved during translation
- New: Translation URL links in Bulk Editor — translated language pills link directly to the translated post
- Enhancement: Expandable debug panel in Bulk Editor — inspect raw query counts and post type data
- Enhancement: Bulk Editor pagination — navigate multi-page results with per-page options (10/20/50/100)
- Enhancement: Bulk Editor folder filter — filter by post type directly in the Bulk Editor toolbar
- Fix: Improved error handling in license manager — array error messages from API are now properly parsed