Deepglot
| 开发者 | helpstring |
|---|---|
| 更新时间 | 2026年8月21日 01:40 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Deepglot translates rendered WordPress pages through the Deepglot translation API and serves each visitor a localized site without duplicating posts.
- Translates text, metadata, accessibility attributes, and JSON-LD structured data.
- Rewrites internal links and SaaS-managed translated URL slugs for path-prefix or subdomain routing.
- Adds canonical and
hreflangtags plus a multilingual sitemap. - Provides shortcode, block, widget, nav-menu, and automatic language switchers.
- Caches translations locally and serves cached translations to crawlers without spending quota.
- Optionally translates dynamically loaded content through a same-origin WordPress REST endpoint.
安装:
- Upload the release ZIP under
Plugins -> Add New -> Upload Plugin. - Activate Deepglot.
- Open
Settings -> Deepglotand enter the API base URL and API key. - Choose the source language, target languages, routing, switcher, and exclusions.
常见问题:
Do I need a Deepglot account?
Yes. Use an account at https://deepglot.ai or configure a compatible self-hosted Deepglot service.
Does the plugin duplicate posts?
No. Translation happens on rendered output. Source content remains in the original WordPress posts and pages.
What happens when the quota is exhausted?
Cached translations remain available. Uncached content falls back to the source language, and administrators see a quota notice.
Why can the first translated page view still show the source language?
Since version 0.12.0, ordinary page requests do not wait for a slow translation provider. The first view queues uncached text for an immediately due WP-Cron job. After the job succeeds, Deepglot stores the translations locally and purges affected URLs in WP Rocket, W3 Total Cache, LiteSpeed Cache, and WP Super Cache. If later views remain in the source language, verify that WP-Cron or the host's system cron is running and purge any other page-cache plugin manually.
更新日志:
0.12.2
- Uses the WordPress 6.9 template enhancement buffer and explicitly closes the legacy fallback buffer on older supported WordPress versions.
- Uses uniquely prefixed translation transients and keeps legacy Yoast compatibility without declaring a Deepglot-owned global.
- Removed arbitrary custom CSS input from language-switcher settings and runtime configuration.
- Loaded admin and nav-menu assets through WordPress enqueue APIs and attached generated responsive and flag rules through the registered switcher stylesheet.
- Ordinary page rendering no longer waits for fresh translations. Uncached segments are translated by a background job, so the first cold view is fast and later views converge after WP-Cron succeeds.
- Added bounded, atomically locked background cache warming. Failed and partial results remain queued, and supported full-page caches are purged after warming completes.
- Kept visual-editor previews and WooCommerce HTML emails synchronous because those one-off outputs cannot converge on a later page request.
- Added the
deepglot_max_sync_batchesfilter to translate inline again on fast providers, anddeepglot_api_timeoutto tune the request budget.
- Added a fail-safe final translated-HTML filter for trusted site-specific localization such as language-specific media embeds.
- Split content-heavy cold pages into ordered parallel requests bounded by 2,000 UTF-8 source bytes and 200 strings.
- Extended the bounded translation request window to 60 seconds so valid cold large-page batches do not fall back to untranslated content.
- Preserved numeric-looking source-slug mappings after persistence so existing translated routes remain resolvable.
- Hardened reciprocal canonical, hreflang, and multilingual sitemap output across source and translated routes.
- Redirected stale translated slugs to current localized URLs, preserved semantic query routing, and suppressed source-only Avada AJAX suggestions on target-language pages.
- Allowed 30 seconds for translation batches and rejected malformed provider responses instead of accepting partial results.
- Detected a revoked or invalid API key (HTTP 401) and stopped retrying it on every page view.
- Added a wp-admin error notice and an "API-Key ungültig" settings status instead of a misleading active state.
- Cleared the invalid-key state immediately when a new API key or backend URL is saved.
- Preserved whitespace-prefixed
mailto:andtel:action links during URL rewriting. - Restored full-language descriptions when the switcher displays ISO-code labels.
- Cleared WordPress.org Plugin Check errors for URL parsing, direct access, escaping, and translator comments.
- Added SaaS-managed translated URL slugs for forward and reverse request routing.
- Added bounded runtime-config refresh and dedicated persisted slug mappings.
- Excluded WordPress infrastructure paths from translation routing.
- Added the refreshed Deepglot admin branding, packaged logo, and orange visual-editor accents.
- Updated dashboard links and localized setup copy from deepglot.app to deepglot.ai.
- Prevented intermediary caches from preserving stale virtual
robots.txtresponses.
- Kept multilingual sitemap discovery when late renderers such as Yoast SEO replace
robots.txtoutput.
- Preserved raw UTF-8 through DOM serialization, including emoji and umlauts in scripts and styles.
- Excluded switcher CSS from WP Rocket used-CSS and minification pipelines.
- Added independent switcher instances, templates, visual placement, AMP handling, and a multilingual sitemap.