Opened 14 years ago

Closed 9 years ago

#14485 closed New feature (wontfix)

New Site.root field

Reported by: George Sakkis Owned by: nobody
Component: contrib.sites Version: dev
Severity: Normal Keywords:
Cc: g.szczepanczyk@… Triage Stage: Someday/Maybe
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I'd like to propose a new 'root' field for django.contrib.sites.models.Site, useful for sites that are deployed under a subdirectory, e.g. "​http://example.com/mysite/"; Site.root here would be "mysite". The obvious use case is for exposing full urls instead of absolute paths that Django produces and consumes internally, but it may have other usages.

Change History (8)

comment:1 by Daniel F Moisset, 14 years ago

Triage Stage: Unreviewed → Design decision needed

Adding this will break old apps on upgrade, so it's not a trivial addition.

comment:2 by Gabriel Hurley, 14 years ago

Component: Contrib apps → contrib.sites

comment:3 by Julien Phalip, 14 years ago

Severity: → Normal
Type: → New feature

comment:4 by Chris Beaven, 13 years ago

Easy pickings: unset
milestone: 1.3
Triage Stage: Design decision needed → Someday/Maybe
UI/UX: unset

Not a bad idea, but we'd have to wait until some method in core for updating before adding a field to a core model (for a relatively edge use case) is acceptable.

comment:5 by Chris Beaven, 13 years ago

Summary: New Site.root field [feature request] → New Site.root field

comment:6 by Aymeric Augustin, 12 years ago

An alternative might be pluggable sites models. See also #2618.

comment:7 by Grzegorz Szczepańczyk, 12 years ago

Cc: g.szczepanczyk@… added

comment:8 by Tim Graham, 9 years ago

Resolution: → wontfix
Status: new → closed

I think it would be a better use of time to try moving the Site model to a setting ​as discussed on the mailing list.

Note: See TracTickets for help on using tickets.
Back to Top