#22779 closed New feature (needsinfo)
Swappable Site
| Reported by: | German M. Bravo | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.sites | Version: | 1.6 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
As noted by #15089 and #21381, it'd be nice to have more flexibility regarding the sites contrib app. I'm attaching a patch that makes django.contrib.sites Site model swappable under v1.6. The patch requires an accepted ticket (#21391) abut lazy signals (I backported it from 1.7 to 1.6), and with that it passes all tests.
Attachments (1)
Change History (4)
by , 11 years ago
| Attachment: | #22779-swappable_sites.diff added |
|---|
comment:1 by , 11 years ago
| Component: | Uncategorized → contrib.sites |
|---|---|
| Type: | Uncategorized → New feature |
comment:2 by , 10 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
Closing as "needs info" until the required discussion happens.
comment:3 by , 8 years ago
This would be really useful to allow customization of SiteManager and get_current method and adding new fields. Many companies and customers asked me to do that during these years. Most of the times I was forced to roll my own sites app, that's the reason why I have contributed too. My ticket is currently closed as it is a duplicate (https://code.djangoproject.com/ticket/27784). Do you have any plan to merge this patch on master branch soon?
Interesting idea. Can you explain your use case and why you're suggestion this solution on django-developers?