Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Page tree problems after translating including subtree #773

Open
leewesleyv opened this issue Feb 2, 2024 · 5 comments
Open

Page tree problems after translating including subtree #773

leewesleyv opened this issue Feb 2, 2024 · 5 comments

Comments

@leewesleyv
Copy link

When translating a page through the Wagtail admin (localize/submit/page/<page_id>) and including the subtree, the (translated) page tree is corrupt. The numchild value for the translated page stays 0, which causes the subpages to not appear in the Wagtail admin. I've been able to reproduce this on multiple Wagtail instances.

Screenshot 2024-02-02 at 09 18 57 Screenshot 2024-02-02 at 09 23 02 Screenshot 2024-02-02 at 09 23 20

Screenshot 2024-02-02 at 09 30 18

How to reproduce

On a fresh installation of Wagtail (using wagtail start), configure i18n using the Wagtail docs. Install wagtail-localize following the installation guide. Then perform the following actions:

  • Add a new locale
  • Add a subpage to the existing start page
  • Translate the start page for the newly added locale, including subpages
@zerolab
Copy link
Collaborator

zerolab commented Feb 2, 2024

Hey @leewesleyv,
Thank you for report this. Which versions of wagtail-localize/Wagtail are you on?

@leewesleyv
Copy link
Author

leewesleyv commented Feb 2, 2024

@zerolab

Currently using the following versions:

wagtail==5.2.3
wagtail-localize==1.7

Besides these versions I've tried with main (of wagtail-localize) where the problem also seems to be present.

@danthedeckie
Copy link

Does running the ./manage.py fixtree help?

@leewesleyv
Copy link
Author

@danthedeckie Running that command will indeed find and fix the problem (see 4th screenshot in #773 (comment)).

@zerolab
Copy link
Collaborator

zerolab commented Feb 12, 2024

By way of update: I was hoping to get to it last week, but I didn't get to it, sorry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants