#22852 closed Bug (duplicate)
WHY: (admin.E013) The value of 'fields' cannot include the ManyToManyField 'make_types', because that field manually specifies a relationship model?
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | contrib.admin | Version: | dev |
| Severity: | Normal | Keywords: | M2M, admin, through, through_fields |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Will any one tell me why checks.py throws this error if I've manually defined the M2M relation table using through?
What's the difference in auto created and manually defined models class?
What's the wrong is if we're adding parameters through and through_fields? Surely auto created model/table need a class and two fields. So, manually created model/table also has same thing!
Change History (4)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
No, I'm not asking question. Rather, I want to know is there any specific reason to throw Error if we've defined M2M relations manually. Whereas we're padding parameters through and through_fields?
I don't think there should be any exception throw if we're defining M2M manually.
Please fix!
comment:3 by , 10 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
You can read about the reasoning in #12203.
comment:4 by , 10 years ago
| Resolution: | invalid → duplicate |
|---|
Note:
See TracTickets
for help on using tickets.
Hi, if you believe there is a bug, please provide code to reproduce the issue.
If you are just asking a question please close this ticket and use our support channels. Thanks.