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
IndexError When Trying to Translate Page #760
Comments
Is If you run this locally with Debug = True, can you expand the error page context around
to see the value of Also, what Wagtail and wagtail-localize versions are you on? |
Yes, I think it is since it's within the tree hierarchy of the Spanish Locale. The only notable log lines from the rqworker are two at the beginning:
Otherwise, it it just a series of page and alias created messages with no other errors or warnings.
I am on Wagtail version 5.0.5 and wagtail_localize version 1.7. |
hmm I take it Can you run the following in the Django shell? from wagtail.models import Page
from wagtail_localize.models import Translation
page = Page.objects.get(pk=1315)
translation = Translation.objects.get(
source__object_id=page.translation_key,
target_locale_id=page.locale_id,
enabled=True,
)
print(translation.source.locale.language_code) re: orphaned pages. |
Yeah, the above snippet gives me |
and I just noticed you said "3. Choose "Translate Page" on one of the created Spanish Pages". Can you record a short screencast of the process with another page, if possible? |
Yes it is!
Screen.Recording.2024-01-04.at.12.46.52.PM.mov |
Hmm, could I be causing an issue by having English as
Edit: To answer my own question, no, that does not seem to make a difference. I see the same behavior with LANGUAGE_CODE set to |
I have noticed the This can be fixed by defining The issue is with the following classes in class CreateView(...)
class EditView(...)
class DeleteView(...) |
I am getting the following error when trying to translate a page just after creating a new Locale via the admin interface:
My steps to reproduce are:
Some potentially related oddities I'm seeing are that when creating the Locale, the Django success message says
Locale '{0}' created.
. Also, from the top level view of the Locales, the newly created Locale will list a usage of 527 pages when the source Locale is 763 Pages.The text was updated successfully, but these errors were encountered: