For those confused about namespaces, I have tried to expand and clarify the
documentation: https://github.com/django/django/pull/3092
Please give it a read and add your questions there and I'll do my best to
answer them (with the caveat that you could include me in those who found
the topic con
I looked into this today and couldn't see why you'd want to have a
different `app_name`. In fact doing so would conflict with the docs: "Every
instance of a single application will have the same application namespace.
For example, Django’s admin application has the somewhat predictable
applicat
I had the same confusion that you seem to have. There is a difference
between application namespace and instance namespace. Because usually you
only have one instance of each of the installed apps, you don't need to
pass `current_app=mycoolappname_instanceX`.
In the case of multiple admin insta
Hmm, I still find it confusing. I have used namespaced urls when making a
reusable app, by using reverse(':"), but that does
enforce someone to use the correct application namespace when including my
app. I think this look more logical than prefixing all my urlnames with
'_'. Is this the right usag
>
> On Thursday, November 14, 2013 12:55:32 PM UTC-3, Amirouche Boubekki wrote:
>>
>>
>> 2013/11/14 Florian Apolloner
>>
>>> We might have to fix the docs there :)
>>>
>>
>> It's was fixed somewhat [1]. ...
>>
>
>
I think Florian refers to other part, which is indeed wrong. I just
submitted
2013/11/14 Florian Apolloner
> We might have to fix the docs there :)
>
It's was fixed somewhat [1]. The original parameter names were confusing:
url(r'^help/', include('apps.help.urls', namespace='foo', app_name='bar')),
Both namespace and app_name are namespaces. The tuple argument is easie
On Thursday, November 14, 2013 12:32:51 PM UTC+1, German Larrain wrote:
>
> So the name of the "other admin" becomes the prefix to the URL names for
> the purpose of reversing them.
>
Not prefix, the prefix is usually always "admin:", since that's the
application namespace; what you should spe
We might have to fix the docs there :)
On Thursday, November 14, 2013 12:47:31 PM UTC+1, Florian Apolloner wrote:
>
>
>
> On Thursday, November 14, 2013 12:32:51 PM UTC+1, German Larrain wrote:
>>
>> So the name of the "other admin" becomes the prefix to the URL names for
>> the purpose of revers
Hi Florian
I used to do that (pass `current_app='other_admin'` to reverse) and it
worked fine until I hit a bump road (sorry, can't remember which) where I
couldn't reverse to the admin site that I wanted by using `current_app` (it
reversed to the "main" one if the URL name existed else raised
Hi Germán,
in your case you should be using current_app; then using
reverse('admin:bla') will tell the urlresolver to reverse an admin url bla
for an AdminSite with name == current_app -- this will also work in
templates; which is good since you really don't want to change string
there… When y
Hi guys
I must say I hit this issue a few months ago (I have more than one admin
app living side by side). It was confusing, when reversing a URL name,
whether to change 'admin' in a string like this `'admin:%s_%s_change'`, or
use `current_app=self.admin_site.name`.
Since I don't like hardcode
Hi Russ,
On Wednesday, November 13, 2013 2:16:13 AM UTC+1, Russell Keith-Magee wrote:
>
> The use case was simple -- deploy two instances of admin in a single
> project. For example, you might have a truly 'access-all-areas' admin, and
> a cut down/modified admin for trusted editors that has spe
On Sun, Nov 10, 2013 at 7:47 PM, Florian Apolloner wrote:
> Hi Russ,
>
>
> On Saturday, November 9, 2013 11:34:53 PM UTC+1, Russell Keith-Magee wrote:
>>
>> I'm a little concerned about this talk about deprecation here -- the
>> app_name exists for a reason, and at time the app_name feature was ad
Hi Russ,
On Saturday, November 9, 2013 11:34:53 PM UTC+1, Russell Keith-Magee wrote:
>
> I'm a little concerned about this talk about deprecation here -- the
> app_name exists for a reason, and at time the app_name feature was added,
> it worked (to the best of my knowledge, anyway).
>
It most
On Sun, Nov 10, 2013 at 1:10 AM, Florian Apolloner wrote:
> Hi Vajrasky,
>
>
> On Saturday, November 9, 2013 4:47:35 PM UTC+1, Vajrasky Kok wrote:
>>
>> While working on this ticket, I was pondering whether we should really
>> fix this or not because one of the core developers said,
>>
>
> Imo fix
Sent from my HTC
- Reply message -
From: "Vajrasky Kok"
To:
Subject: Should AdminSite be able to handle different namespace?
Date: Sat, Nov 9, 2013 3:47 pm
Greetings, friends!
This is related with this ticket: https://code.djangoproject.com/ticket/21132
While working on t
Hi Vajrasky,
On Saturday, November 9, 2013 4:47:35 PM UTC+1, Vajrasky Kok wrote:
>
> While working on this ticket, I was pondering whether we should really fix
> this or not because one of the core developers said,
>
Imo fixing this won't be easy; see for instance how admin_urlname filter is
im
Greetings, friends!
This is related with this ticket:
https://code.djangoproject.com/ticket/21132
While working on this ticket, I was pondering whether we should really fix
this or not because one of the core developers said,
"The whole admin is currently built on the idea that the app is name
18 matches
Mail list logo
