-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Wagtail search index issue | list index out of range #12996
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
Comments
Can you post the full traceback of the error? This would help determine whether this a Wagtail or wagtail-localize issue |
@Aalian123 Can you provide the exact steps to reproduce this issue? Are you adding the locale through the Wagtail admin or via a script? Also, does this happen for all page types or only specific ones? |
I am adding through wagtail admin and it is random as far I know. Steps to reproduce are below:
As I have content field as searchable field, content field contains different blocks so it tries to create index on that and gives error. Signal is wagtail's builtin signal Traceback
|
Based on the error stack trace and the code I've examined, Probable Fix: # Ensure all lists are of equal length to prevent IndexError and #Add empty SQL entries if needed |
… by testing various scenarios with unequal list lengths that previously caused IndexError.
Issue Summary
When adding locale and synchronizing pages with existing locale , on some pages I am getting error list index out of range. while some Specifically, when adding a locale and synchronizing pages with an existing locale, I receive a "list index out of range" error on some pages, while others are indexed correctly. I updated Python, Django, and Wagtail versions.
-->
Current Code is below
Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
Technical details
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.
The text was updated successfully, but these errors were encountered: