Feature: When adding a new locale, allow users to set publishing status of sync'd content #883
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, thank you for this. Will do my best to get this reviewed in the coming few weeks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I am submitting a PR which enables a new feature when adding a new locale to wagtail.
When syncing a content tree from another language, the current behavior of wagtail localize is to mirror both the content and the publishing status. There is no way to override the publishing status in the UI. If an article is live in the source language, a newly synced locale and content tree will be automatically pushed live, before translation can be done. This workflow also does not give users the opportunity to configure other parts of the site, like translated navigation menus.
The new behavior added by this PR allows the user to configure the publishing status of all pages I the synced content tree. Two options are available:
Mirror: this is the current behavior and is configured as the default setting for backwards compatibility
Draft: all pages in the synced tree will be set to Draft
The code for this PR was assisted by AI. I've tested the behavior on my local machine and it works as I expected. Tests are included as well. Happy to take any feedback and make changes as needed.