-
Notifications
You must be signed in to change notification settings - Fork 583
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
Need to reopen issue 887 #1504
Comments
For me (Django 4.2 and 5.0) dumping and loading fixtures works: first the
Be aware that The next-gen django-filer will not use django-polymorphic any more (which was the root cause of the issue). Not sure what's going wrong on your side. @greyhare Can you share a minimal dump for your case? |
Yes, I'm aware that Anyway, I'll close here and continue in the original issue. |
I don't have permission to reopen issue 887. TL;DR:
dumpdata
emits thefiler_image
table in place of thefiler_file
table, resulting in a fixture with no files, duplicated images, and integrity errors when fed toloaddata
.Also I can't figure out which of the 4000+ contributors are the maintainers so I could @ them instead of making a new issue. Sorry.
The text was updated successfully, but these errors were encountered: