Prevent the automatic creation of Wagtail Page Aliases in other locales #15066
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.
This changeset deliberately removes the after_create_page hook from wagtail_localize.synctree to avoid the default behaviour where adding a page in a locale creates Aliases in all other locales which then serve the soure locale's content but under a different locale path (eg /en-US/test-page/'s content appears on /fr/test-page/ because of the alias)
See changes to cms.rst in this changeset for more details
Issue / Bugzilla link
Resolves #15063
Testing
main
, create a new page in the CMS, publish it.