3

Django newbie here. Following the documentation, I am trying the following to get a link to the admin site from the homepage of the public site I'm building:

{% load admin_urls %}
<p>Go to the <a href="{% url opts|admin_urlname:'add' %}">admin</a>.</p>

I am getting the error: 

NoReverseMatch at /
u'opts|admin_urlname' is not a registered namespace

I am including the URLs properly:

    url(r'^admin/', include(admin.site.urls)),

My template loaders are in the right order.

I've tried a few different variations on this, and they all throw namespace errors.

Any ideas? Thanks!

Community
  • 1
  • 1
TAH
  • 1,658
  • 1
  • 19
  • 37

3 Answers3

5

After 30 minutes with Daniel Roseman / Django docs in one screen and my code in the other, I come up with this simple solution:

In your views.py, add the opts context with the _meta of the model (that includes the required app_label and model_name):

class YourModelDetailView(DetailView):
    def get_context_data(self, **kwargs):
        context = super(YourModelDetailView, self).get_context_data(**kwargs)
        context["opts"] = YourModel._meta
        return context

In your templates:

{% url opts|admin_urlname:'change' object.pk %}

Where change can be any action in the reverse admin urls documentation page.

xbello
  • 7,223
  • 3
  • 28
  • 41
5

While the above answers were helpful about the code I was calling, there is a much easier way. I'm using this instead:

{% url 'admin:index' %}

This works for custom admin views as well, like:

{% url 'admin:myapp_mymodel_<keyword>' object.id %}

Where keyword is from the named parameters listed here (i.e. add, change, delete).

Lucas03
  • 2,267
  • 2
  • 32
  • 60
TAH
  • 1,658
  • 1
  • 19
  • 37
  • 2
    This worked nicely for me but needed quotes (perhaps a Django change since this answer was posted): ``{% url 'admin:myproject_myapp_user_change' user.id %}`` – Andrew E Nov 08 '14 at 13:21
0

You are almost certainly using the released 1.4 version, rather than the development version. As the documentation for that version shows, you need to use {% load url from future %} before you can use that syntax.

Daniel Roseman
  • 588,541
  • 66
  • 880
  • 895
  • Thanks for the response! First of all, what is up w/ the friggin Django documentation -- there are multiple versions of the same pages?! The only difference btw. my link and yours is that one line, and there is no indication even in the 1.4 link about that change. But back to the point, now I am getting `AttributeError at /, 'str' object has no attribute 'app_label'` -- ??? – TAH Oct 14 '12 at 17:15
  • I can't understand your objection. Obviously, as changes are made to Django in subsequent versions over the years, there need to be new versions of the docs - I've no idea why you would find that strange. – Daniel Roseman Oct 14 '12 at 17:38
  • Your comment spurred me to look closer at the page to see for the first time that nav in the lower-right to change the documentation version. Well, glad to have finally noticed that, though it is awfully subtle. Anyway, thoughts on that `AttributeError`? ;-) – TAH Oct 14 '12 at 18:25
  • What are you passing as `opts`? Seems like you're passing a string, whereas the docs say it should be an object with `app_label` and `module_name` attributes. – Daniel Roseman Oct 14 '12 at 22:04
  • @DanielRoseman Please look at this question [http://stackoverflow.com/questions/12890935/how-to-translate-an-app-template] if you have any idea please post your answer there **thanks** – Inforian Oct 15 '12 at 12:02
  • Yes, it turns out, I was passing opts as a string -- misunderstood what the docs were saying about what opts is. – TAH Oct 23 '12 at 13:47