#24430: wildcard matching and reversing of URLs
-----------------------------+--------------------------------------
Reporter: eskhool | Owner: nobody
Type: New feature | Status: closed
Component: Core (URLs) | Version: 1.7
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by eskhool):
Replying to [comment:5 charettes]:
> [https://docs.djangoproject.com/en/1.7/ref/contrib/admin/#multiple-
admin-sites Multiple admin sites can already be deployed in same URLConf].
>
> You'd just have to create a namespaced admin site for each of you
tenants or write an URLResolver that does it for you.
Multiple admin sites are fine but seem to require each tenant to have a
code entry in the URL Conf. Problem is that we need the namespaced admin
sites to be dynamic since tenants needs to be added at any time without
code intervention.
we write a URL Resolver, how will we get Django admin to use that URL
resolver instead of the default django.core.urlresolvers.reverse etc?
this is why the wildcard support was proposed
--
Ticket URL: <https://code.djangoproject.com/ticket/24430#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.b5a35b5d93710452ed9cf70ad4b5ef21%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
