Custom path requires app name in Django 1.4 about django-adminplus HOT 8 CLOSED

I can't reproduce this with Django 1.4.2, using 'somepath' works fine for me. Can you include the relevant bits of the admin.py?

from django-adminplus.

I'm using Django 1.4 (not 1.4.2). Here's my admin.py: note than neither test/ nor /test/ paths work, it has to be myapp/test/

from django.contrib import admin

admin.site.register_view('myapp/test/', my_view, name="My View", visible=True)

from django-adminplus.

I tried exactly this and couldn't reproduce the issue. I'm sorry. If
you figure it out I'm happy to look at a patch.

On Tuesday, November 06, 2012 12:44:56, saidimu apale wrote:

I'm using Django |1.4| (not |1.4.2|). Here's my |admin.py|: note than
neither |test/| nor |/test/| paths work, it has to be |myapp/test/|

|from django.contrib import admin

admin.site.register_view('myapp/test/', my_view, name="My View", visible=True)
|

—
Reply to this email directly or view it on GitHub
#6 (comment).

James Socol
Community Platforms Manager - Mozilla
[email protected]

from django-adminplus.

I have same problem, I have to put app name in path and then is working

from django-adminplus.

I still can't reproduce this issue on Django 1.4.2. Like I said, if anyone can come up with a patch I'm more than happy to dig into it, but I just can't find it.

from django-adminplus.

I've never been able to reproduce this. If someone who can is willing to create a failing test and/or a patch, I'd love to look into that and get it fixed, but until then I'm going to close this one.

from django-adminplus.

I was experiencing this issue with my project (Django 1.5.1 / adminplus 0.2.0). I'd get the issue with my development env that uses apache/mod_wsgi, but was not getting the problem with ./manage.py runserver. After playing around, switching between the two, it started working with apache/mod_wsgi too, with no changes. So it could be something like stray *.pyc files?

from django-adminplus.

@brew Like I said above, I've never been able to reproduce this on 1.4 or 1.5. I'm happy to dig into a patch if anyone who can reproduce it can figure it out.

mod_wsgi doesn't create or, as far as I know, use any bytecode files, so I doubt stray .pycs are changing its behavior anywhere.

from django-adminplus.