Publish changes
Publishing turns your current translations into the files visitors load.
What happens#
- The product builds a new version of your bundle: one file per language and a signed manifest.
- It checks the bundle against the format rules before it uploads anything.
- For each delivery target it uploads the language files, checks that each one arrived, and writes the manifest last.
Writing the manifest last means a visitor never sees a manifest that points at files which have not arrived yet.
Start a publish#
On the site page choose Publish now. The editor has a publish button too. Editors, admins and owners can publish. Viewers cannot. The button is disabled until something has been translated. Reviewers can publish only if your team allowed it. See Reviewers and translators.
Read the status#
The site list shows:
- Live and a version number: every target has the new version.
- Partly updated: at least one target failed. A target that failed keeps its previous complete version. Others move on. The job retries with the same version number.
- Not published: nothing has been published yet.
The site page shows the job state: queued, running with a percentage, succeeded or failed. If it failed, the error is shown. The page checks progress by itself and announces changes to screen readers.
When visitors see it#
The manifest may be cached for about a minute, and caches may serve the older one for a while longer when the origin is slow. On WordPress, the plugin copies the new files on its next scheduled sync, or when you press Sync now. See WordPress.
Limits#
- A lapsed licence blocks publishing. Files already published keep serving. See Cancel, lapse and grace.
- Publishing automatically after each translation run is off by default: OPEN.
- You can get a message on your own server when a publish finishes. See Webhooks and the audit log.