Re: Problem with generic views in tutorial example
> Anurag, Thanks. That worked for me too. But it's hardly a solution.
> Now I can't use admin. I want both. Is that asking too much? Has
> anyone else any ideas?
OK, I've solved all my problems. It was my mistake. For some reason,
I had these two lines in urls.py in the reverse order:
(r'^admin/doc/', include('django.contrib.admindocs.urls')),
(r'^admin/(.*)', admin.site.root),
Now I can have a public and admin interface, whether or not I use a
separate admin.py file. Sorry to have bothered you. It seems generic
views work after all! But it was useful for me to learn about
admin.py - it seems a good idea to use a separate admin.py file.
Rodney
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Problem with generic views in tutorial example
I was able to implement the generic views change with yesterday's
trunk version successfully. I did not have to do anything special (no
separate admin.py, no get_absolute_url())
I did however, do something that the tutorial did not ask to do - i.e.
delete all references to the admin in mysite/urls.py, which looks like
this:
--begin--
from django.conf.urls.defaults import *
from mysite.polls.models import Poll
info_dict = {
'queryset': Poll.objects.all(),
}
urlpatterns = patterns('',
(r'^$',
'django.views.generic.list_detail.object_list',
info_dict),
(r'^(?P\d+)/$',
'django.views.generic.list_detail.object_detail',
info_dict),
url(r'^(?P\d+)/results/$',
'django.views.generic.list_detail.object_detail',
dict(info_dict, template_name='polls/
results.html'),
'poll_results'),
(r'^(?P\d+)/vote/$',
'mysite.polls.views.vote'),
)
--end--
Hope this helps.
-Anurag
On Aug 21, 10:45 pm, Rodney Topor <[EMAIL PROTECTED]> wrote:
> I'm having trouble modifying the tutorial example to use generic
> views. (My implementation without generic views works fine.) I've
> registered the class Poll with admin in a separate admin.py module as
> described in ticket 8181. I've provided names for all url patterns in
> app polls. I've defined get_absolute_url() for class Poll using the
> name for the poll detail pattern. I've implemented view vote() as
> described in the tutorial, Yet when I cast a vote in the form with
> action = /polls/n/vote/, I get the following error:
>
> The model Poll is already registered
>
> Any suggestions?
>
> (And this is separate from the reverse lookup failures I get with
> generic views using named patterns in url template tags...)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Problem with generic views in tutorial example
On Aug 22, 4:18 pm, Anurag Goel <[EMAIL PROTECTED]> wrote: > I was able to implement the generic views change with yesterday's > trunk version successfully. I did not have to do anything special (no > separate admin.py, no get_absolute_url()) > > I did however, do something that the tutorial did not ask to do - i.e. > delete all references to the admin in mysite/urls.py, which looks like > this: > Anurag, Thanks. That worked for me too. But it's hardly a solution. Now I can't use admin. I want both. Is that asking too much? Has anyone else any ideas? > On Aug 21, 10:45 pm, Rodney Topor <[EMAIL PROTECTED]> wrote: > > > I'm having trouble modifying the tutorial example to use generic > > views. (My implementation without generic views works fine.) I've > > registered the class Poll with admin in a separate admin.py module as > > described in ticket 8181. I've provided names for all url patterns in > > app polls. I've defined get_absolute_url() for class Poll using the > > name for the poll detail pattern. I've implemented view vote() as > > described in the tutorial, Yet when I cast a vote in the form with > > action = /polls/n/vote/, I get the following error: > > > The model Poll is already registered > > > Any suggestions? > > > (And this is separate from the reverse lookup failures I get with > > generic views using named patterns in url template tags...) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Problem with generic views in tutorial example
On Fri, Aug 22, 2008 at 4:38 AM, Rodney Topor <[EMAIL PROTECTED]> wrote: > > On Aug 22, 4:18 pm, Anurag Goel <[EMAIL PROTECTED]> wrote: > > I was able to implement the generic views change with yesterday's > > trunk version successfully. I did not have to do anything special (no > > separate admin.py, no get_absolute_url()) > > > > I did however, do something that the tutorial did not ask to do - i.e. > > delete all references to the admin in mysite/urls.py, which looks like > > this: > > > Anurag, Thanks. That worked for me too. But it's hardly a solution. > Now I can't use admin. I want both. Is that asking too much? Has > anyone else any ideas? > Your urls.py file should have admin.autodiscover(). You should not have any admin.site.register calls for Poll except for what you have in the admin.py you created. The duplicate registration message you get makes it sound like you have another registration getting called from somewhere. Did you not remove it from models.py when you created admin.py? Karen > > > On Aug 21, 10:45 pm, Rodney Topor <[EMAIL PROTECTED]> wrote: > > > > > I'm having trouble modifying the tutorial example to use generic > > > views. (My implementation without generic views works fine.) I've > > > registered the class Poll with admin in a separate admin.py module as > > > described in ticket 8181. I've provided names for all url patterns in > > > app polls. I've defined get_absolute_url() for class Poll using the > > > name for the poll detail pattern. I've implemented view vote() as > > > described in the tutorial, Yet when I cast a vote in the form with > > > action = /polls/n/vote/, I get the following error: > > > > > The model Poll is already registered > > > > > Any suggestions? > > > > > (And this is separate from the reverse lookup failures I get with > > > generic views using named patterns in url template tags...) > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: Problem with generic views in tutorial example
Apologies - I did not mention that my original urls.py (under mysite/,
at the same level as polls/) still exists (the urls.py has to be
copied over as opposed to moved), and it contains the following code:
--mysite/urls.py begin--
from django.conf.urls.defaults import *
# Uncomment the next two lines to enable the admin:
from django.contrib import admin
admin.autodiscover()
urlpatterns = patterns('mysite.polls.views',
#enables admin and poll/urls.py
(r'^polls/', include('mysite.polls.urls')),
(r'^admin/(.*)', admin.site.root),
)
--end mysite/urls.py--
Again, no need for any additional changes.
On Aug 22, 1:38 am, Rodney Topor <[EMAIL PROTECTED]> wrote:
> On Aug 22, 4:18 pm, Anurag Goel <[EMAIL PROTECTED]> wrote:> I was able to
> implement the generic views change with yesterday's
> > trunk version successfully. I did not have to do anything special (no
> > separate admin.py, no get_absolute_url())
>
> > I did however, do something that the tutorial did not ask to do - i.e.
> > delete all references to the admin in mysite/urls.py, which looks like
> > this:
>
> Anurag, Thanks. That worked for me too. But it's hardly a solution.
> Now I can't use admin. I want both. Is that asking too much? Has
> anyone else any ideas?
>
> > On Aug 21, 10:45 pm, Rodney Topor <[EMAIL PROTECTED]> wrote:
>
> > > I'm having trouble modifying the tutorial example to use generic
> > > views. (My implementation without generic views works fine.) I've
> > > registered the class Poll with admin in a separate admin.py module as
> > > described in ticket 8181. I've provided names for all url patterns in
> > > app polls. I've defined get_absolute_url() for class Poll using the
> > > name for the poll detail pattern. I've implemented view vote() as
> > > described in the tutorial, Yet when I cast a vote in the form with
> > > action = /polls/n/vote/, I get the following error:
>
> > > The model Poll is already registered
>
> > > Any suggestions?
>
> > > (And this is separate from the reverse lookup failures I get with
> > > generic views using named patterns in url template tags...)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Problem with generic views in tutorial example
And in my first reply, I meant 'mysite/polls/urls.py' when I said: ' . I did however, do something that the tutorial did not ask to do - i.e. delete all references to the admin in mysite/urls.py, which looks like this ' On Aug 22, 1:38 am, Rodney Topor <[EMAIL PROTECTED]> wrote: > On Aug 22, 4:18 pm, Anurag Goel <[EMAIL PROTECTED]> wrote:> I was able to > implement the generic views change with yesterday's > > trunk version successfully. I did not have to do anything special (no > > separate admin.py, no get_absolute_url()) > > > I did however, do something that the tutorial did not ask to do - i.e. > > delete all references to the admin in mysite/urls.py, which looks like > > this: > > Anurag, Thanks. That worked for me too. But it's hardly a solution. > Now I can't use admin. I want both. Is that asking too much? Has > anyone else any ideas? > > > On Aug 21, 10:45 pm, Rodney Topor <[EMAIL PROTECTED]> wrote: > > > > I'm having trouble modifying the tutorial example to use generic > > > views. (My implementation without generic views works fine.) I've > > > registered the class Poll with admin in a separate admin.py module as > > > described in ticket 8181. I've provided names for all url patterns in > > > app polls. I've defined get_absolute_url() for class Poll using the > > > name for the poll detail pattern. I've implemented view vote() as > > > described in the tutorial, Yet when I cast a vote in the form with > > > action = /polls/n/vote/, I get the following error: > > > > The model Poll is already registered > > > > Any suggestions? > > > > (And this is separate from the reverse lookup failures I get with > > > generic views using named patterns in url template tags...) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
