A translated page becoming public too early is a publication-state problem until proven otherwise. Compare its stored status, its relationship to the source, the intended publication instant and what a signed-out visitor can actually fetch. Do not start by moving every scheduled date or deleting translation jobs.
Identify the documented situations
The WPML 5.2.0 changelog lists corrections for early publication after translation review, scheduled sources publishing unfinished or trashed translations when dates are copied, and restored posts bringing draft or private translations back as published. These are distinct transitions. Match your reproduction to the relevant transition rather than treating all unexpected visibility as the same bug.
If confidential material is already visible, involve the authorized content owner immediately. Preserve minimal private evidence, correct the intended visibility through the supported editor, and verify the public response and relevant caches. A later plugin update is not a substitute for containing an active exposure. Do not put the exposed text into a public support ticket.
Make a status ledger
For one affected source and its translations, record the post IDs, language, current status, intended status, scheduled local time and UTC time. Include the actual trigger: accepting a translation review, reaching a scheduled date, or restoring a source from Trash. Record whether publication dates are configured to copy to translations.
Keep translation completion separate from publication approval. A linguist may have finished the text while the campaign owner still requires it to remain private. Write that business rule down before changing synchronization settings. Otherwise, a technically consistent configuration can still violate the release plan.
Use the WordPress timezone and scheduled-post guide if the stored instant differs from the intended time. An early status change and a late cron execution are different failures and require different evidence.
Translation completion, source scheduling and public visibility require separate approval checks. Explanatory diagram.
Reproduce each transition on private staging
Create harmless source text and translations with explicit markers. Use an environment that cannot send real campaign emails or publish to connected channels. Back up both files and database before updating, and verify that the backup can be recovered without overwriting new production work.
- Schedule a source for a future time. Complete or accept a translation review before that time and check whether its status follows the intended policy.
- Prepare an unfinished translation and, separately, a trashed translation. Let the harmless scheduled source reach its date under the same date-copy setting used by the affected site.
- Create draft and private translations, record their status, then test the relevant source trash-and-restore workflow. Check that restoration does not silently promote either translation.
These are separate fixtures, not instructions to trash live campaign pages. Record before and after values for each step. If the issue occurs only through a custom front-end form or scheduled integration, add that exact path after the ordinary editor workflow is understood.
Verify content delivery, not only an editor label
For each intended private or draft translation, check the response signed out and confirm the protected content is absent. Record the actual status and redirect behavior without assuming every private route must return the same HTTP code. An authenticated editor preview is not a valid public-access test.
For a translation that should become public, verify the correct language, approved text, canonical URL and navigation link after the scheduled event. Inspect the source and target independently. A successful source publication does not prove that a language-specific cache or menu is fresh.
Repeat the failed fixture after applying the supported WPML update in staging. Do not claim recovery solely because the version number changed. The acceptance record should demonstrate the transition that previously failed, with the original status policy preserved.
When a different guide applies
If the public address returns a 404 after a same-slug draft is created, follow the WPML URL ownership guide. That symptom is not evidence of early publication. If jobs never complete, diagnose their queue or billing state before testing release timing.
For escalation, provide versions, post IDs, languages, expected statuses, the trigger and redacted before-and-after results. HandL WP can investigate publication-state failures without resetting WPML or bulk-publishing unfinished translations. Keep a named content owner responsible for the final visibility decision.
Sources reviewed November 2, 2026. Examples and diagrams are diagnostic aids, not customer test results.