Opened 4 years ago
Closed 4 years ago
#31123 closed New feature (fixed)
Add option to remove_stale_contenttypes to remove entries for nonexistent apps.
| Reported by: | Gowtham Kommineni | Owned by: | Gowtham Kommineni |
|---|---|---|---|
| Component: | contrib.contenttypes | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Add an option (disabled by default) to remove_stale_contenttypes command to remove entries also for nonexistent apps.
Based on discussion.
Change History (6)
comment:1 by , 4 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
| Summary: | remove_stale_contenttypes doesn't remove entries for stale apps → remove_stale_contenttypes doesn't remove entries for nonexistent apps. |
comment:2 by , 4 years ago
| Description: | modified (diff) |
|---|---|
| Has patch: | unset |
| Resolution: | wontfix |
| Status: | closed → new |
| Summary: | remove_stale_contenttypes doesn't remove entries for nonexistent apps. → Add option to remove_stale_contenttypes to remove entries for nonexistent apps. |
| Triage Stage: | Unreviewed → Accepted |
| Type: | Bug → New feature |
| Version: | 3.0 → master |
Accepted based on discussion .
comment:3 by , 4 years ago
| Description: | modified (diff) |
|---|---|
| Has patch: | set |
Version 0, edited 4 years ago by (next)
comment:4 by , 4 years ago
| Needs documentation: | set |
|---|---|
| Owner: | changed from to |
| Patch needs improvement: | set |
| Status: | new → assigned |
comment:5 by , 4 years ago
| Needs documentation: | unset |
|---|---|
| Patch needs improvement: | unset |
| Triage Stage: | Accepted → Ready for checkin |
Note:
See TracTickets
for help on using tickets.
I don't think that
remove_stale_contenttypesshould remove content types for nonexistent apps. We don't automatically remove models for nonexistent apps and I don't think we should do this with content types. This can also cause a data loss for a custom content types (not related to real apps). You can start a discussion on DevelopersMailingList if you don't agree.