Databases
StackOverflow2013
Postsdbo
PODjango will this view shown in the admin index
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango will this view shown in the admin index
    primarykey
    data
    text
    <p>Will this view shown as a link in admin index in a portion called modules? Which user can click on the link like normal admin class to view the view?</p> <p>I have a class in called ListAdmin in Admin.py:</p> <pre><code>class ListAdmin(admin.ModelAdmin): def list_view(self, request): return question_list(request) def get_urls(self): urls = super(ListAdmin, self).get_urls() list_urls = patterns('', r'^list/$', self.list_view()) return list_urls + urls </code></pre> <p>The view is in view.py</p> <pre><code>def question_list(request): #questions = Question.objects.filter(topic__icontains = 1) questions = Question.objects.all() return render_to_response('admin/question_list.html', {'questions':questions}) question_list = staff_member_required(question_list) </code></pre> <p>The problem is I don't know how to register the ListAdmin into the admin, because it does not have a list model, and the Question model is already registered.</p> <pre><code>admin.site.register(???, ListAdmin) </code></pre> <p>The possible solution is this:</p> <p><a href="https://stackoverflow.com/questions/2223375/multiplue-modeladmins-views-for-same-model-in-django-admin">Multiple ModelAdmins/views for same model in Django admin</a></p> <p>I added this into my admin.py, it succesfully added a link into the admin index:</p> <pre><code>class List(Question): class Meta: proxy = True class ListAdmin(QuestionAdmin): def list_view(self, request): return question_list(request) admin.site.register(List, ListAdmin) </code></pre> <p>I still think that it is wrong because if I take the line below out from the url.py, it will direct to the Question model:</p> <pre><code>url(r'^admin/modules/list/$', 'exam.admin.modules.views.question_list'), </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USkelvinfix
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COpossible duplicate of [Django custom view into admin page](http://stackoverflow.com/questions/5693519/django-custom-view-into-admin-page)
      singulars
      1. PODjango will this view shown in the admin index
      1. USDTing
    2. COThe view does not show in the admin index page.
      singulars
      1. PODjango will this view shown in the admin index
      1. USkelvinfix
    3. COI cannot edit the previous post already before I have clear my browser cache.
      singulars
      1. PODjango will this view shown in the admin index
      1. USkelvinfix
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload