This project is not covered by Drupal’s security advisory policy.
Steps Performed
Created original page and published.
Added translation of the page and published.
Edited original page: added a second text block and saved it in draft mode.
Checked translated page: the newly added text block was not visible.
2. Expected Behavior
Any component added in the original language page should automatically appear in the translated page, regardless of whether the original page is in draft or published state.
The translated page should remain synchronized with the original page’s structure and components.
3. Actual Behavior
The text block added in the original page (saved as draft) did not show up in the translated page.
This indicates that the synchronization between original and translated pages is not functioning as expected when edits are saved in draft mode.
4. Impact
Editors may assume that changes in the original page will propagate to translations, but in practice, components added in draft mode are not reflected.
This can lead to inconsistent content across languages and confusion during review or publishing.
5. Possible Root Cause
Translation sync may only trigger on published changes, not drafts.
The system might be treating draft edits as “local” to the original page until they are published, preventing propagation to translations.
6. Recommendation
Review the synchronization logic for translated pages.
Ensure that components added in the original page are reflected in translations, even if the original page is in draft mode.
Alternatively, clarify in documentation that only published changes are synced to translations, so editors know what to expect.
Project information
Unsupported
Not supported (i.e. abandoned), and no longer being developed. Learn more about dealing with unsupported (abandoned) projects- Created by raajkumar.kuru on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
