Deepglot, explained clearly

Workspace activity

Your weekly digest at a glance

The weekly digest is an opt-in email per user and workspace. It reports new translations and words, manual edits, and runtime translation requests from the previous complete UTC week.

Background translation

How cold WordPress pages warm up

The first request to a cold target-language page may show source content while WP-Cron translates missing segments in the background. Deepglot retains the visitor's localized URL as the later cache target even after WordPress has internally rewritten the request to its source path.

Once the queue and due event are stored, Deepglot makes one non-blocking WP-Cron nudge per request. That nudge is skipped for DISABLE_WP_CRON and while cron is already running. WP Rocket, W3 Total Cache, and LiteSpeed Cache purge completed URLs individually. WP Super Cache exposes only a global purge, so Deepglot waits until the tracked queue is empty and pending pages stay cached. Failed or partial translations remain queued for a later cron retry.

Safe text handling

Why Deepglot rejects U+0000

PostgreSQL cannot store the U+0000 null byte in text or JSON. Deepglot therefore rejects it in API, editor, and import input with a validation error before provider calls and before translation content is persisted. Other valid Unicode characters remain unchanged.

If a translation provider response contains U+0000, that result is not stored. A configured fallback provider can take over; if the provider chain still fails, the request ends without attempting translation-content persistence. Logs contain only the boundary, field, count, and provider — never text or URLs.

WordPress

What WordPress v0.11.4–v0.11.7 changed

These four releases stabilize URL resolution, large cold pages, and trusted site-specific post-processing. They do not replace a production approval: publishing a package does not automatically install or update a customer plugin.