Re: url problems

[Herman Schistad]

> the current url (path) is C:\Users\Dagon\mysite. Everything is relative to
> mysite.

Make sure you read the guide once more, and that you have "runserver"
up and running (issue the command: python manage.py runserver"
Then you go to the following URL: localhost:8000/polls and you will
hopefully get another result.

-- 
With regards, Herman Schistad

-- 
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 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: url problems

[Daniel Roseman]

What? URLs have nothing to do with file paths.

There is nothing wrong here at all. The tutorial got you to define some URLs 
beginning with 'polls'. You have to go to one of those URLs. Going to the root 
of the site won't work, because you haven't set up a URL for it.
-- 
DR.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/vUZU7XRU_rcJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: url problems

[charles]

On 11/07/04 17:14, Michał Sawicz wrote:

Dnia 2011-07-04, pon o godzinie 16:50 -0500, charles pisze:

The current URL, , didn't match any of these.

And the current URL was?
the current url (path) is C:\Users\Dagon\mysite. Everything is relative 
to mysite.


--
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 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: url problems

[Michał Sawicz]

Dnia 2011-07-04, pon o godzinie 16:50 -0500, charles pisze:
> The current URL, , didn't match any of these.

And the current URL was?
-- 
Michał (Saviq) Sawicz 


signature.asc
Description: This is a digitally signed message part

url problems

[charles]

I am trying to work through the 3rd part of the tutorial and I have a 
problem. When I copy and past


urlpatterns  =  patterns('',
(r'^polls/$',  'polls.views.index'),
(r'^polls/(?P\d+)/$',  'polls.views.detail'),
(r'^polls/(?P\d+)/results/$',  'polls.views.results'),
(r'^polls/(?P\d+)/vote/$',  'polls.views.vote'),
(r'^admin/',  include(admin.site.urls)),
)

into mysite.urls I receive the following error message:


Using the URLconf defined in |mysite.urls|, Django tried these URL 
patterns, in this order:


  1. ^polls/$
  2. ^polls/(?P\d+)/$
  3. ^polls/(?P\d+)/results/$
  4. ^polls/(?P\d+)/vote/$
  5. ^admin/

The current URL, ||, didn't match any of these.

I am using Python 2.7.1 and Windows Vista. Does the url code work 
differently on Vista? or is there something I am missing? What do I need 
to fix the code, or is there a work around?


Charles




--
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 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Best Practices for debugging URL problems

[Adam Nelson]

I recently had what is a common issue for many Django developers:

"No module named urls"

What turned out to be the issue is that I had deleted one of the
urls.py files accidentally because I deleted an app that I thought I
was no longer being used but was in fact being called by the top level
urls.py.

Is there any good way to diagnose this class of problems?  There is
nowhere either through the interactive debugger or the debugging page
that would have shown this issue because the url error is thrown with
the first call to {{ url }}.  In the end I had to revert to previous
revisions and just find out which one caused the problem by trial and
error.

Thanks,
Adam
--~--~-~--~~~---~--~~
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 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: URL problems after newforms admin migration

[Karen Tracey]

On Tue, Jul 22, 2008 at 2:17 PM, Matthew <[EMAIL PROTECTED]> wrote:

>
> Hey everyone, I recently updated a development version of my Django
> site to use the newforms admin, following the tutorial here
>
> http://oebfare.com/blog/2008/jul/20/newforms-admin-migration-and-screencast/
> It all went fairly well, but I do have one major problem though, and I
> don't know whether its connected to this. I suspect it is anyway
> because it only arose after migration.
>
> The problem is that whenever I am editing in the admin site, and I
> click on a 'Save' button for instance, I get a 404 error.
>
> "Page not found (404)
> Request Method: GET
> Request URL:
> http://10.2.140.72:2013/main.fcgi/main.fcgi/admin/events/event/2/;
>
> Obviously it appears that the admin is trying to redirect me to an
> address such as /main.fcgi/main.fcgi/admin/events/event/2/ rather
> than /admin/events/event/2/
>
> After getting the 404, if I remove the /main.fcgi/ from the address
> and go to /admin/events/event/2/ I get to the correct page. The
> changes that are to be saved are actually being saved too, but
> obviously this is a big hindrance to a smooth site running.
>
> Can anyone help, or is this something unrelated to the newforms admin?
>

Not sure, but it might be related to this change:

http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#ChangedthewayURLpathsaredetermined

rather than newforms-admin.

Karen

--~--~-~--~~~---~--~~
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: URL problems after newforms admin migration

[Matthew]

Hmm, unfortunately I'm running this test environment on a Media Temple
Gridserver container, so I have no access to the httpd.conf for
changing stuff like that :( I'm not too bothered with the problem
whilst I'm testing it, but I wouldn't want this to crop up when I'm
trying to move it all across to my "production" server :\

That link does seem similar to trouble I'm having though, thanks for
that Karen.

On 22 Jul, 21:30, "Karen Tracey" <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 22, 2008 at 2:17 PM, Matthew <[EMAIL PROTECTED]> wrote:
>
> > Hey everyone, I recently updated a development version of my Django
> > site to use the newforms admin, following the tutorial here
>
> >http://oebfare.com/blog/2008/jul/20/newforms-admin-migration-and-scre...
> > It all went fairly well, but I do have one major problem though, and I
> > don't know whether its connected to this. I suspect it is anyway
> > because it only arose after migration.
>
> > The problem is that whenever I am editing in the admin site, and I
> > click on a 'Save' button for instance, I get a 404 error.
>
> > "Page not found (404)
> > Request Method:         GET
> > Request URL:
> >http://10.2.140.72:2013/main.fcgi/main.fcgi/admin/events/event/2/;
>
> > Obviously it appears that the admin is trying to redirect me to an
> > address such as /main.fcgi/main.fcgi/admin/events/event/2/ rather
> > than /admin/events/event/2/
>
> > After getting the 404, if I remove the /main.fcgi/ from the address
> > and go to /admin/events/event/2/ I get to the correct page. The
> > changes that are to be saved are actually being saved too, but
> > obviously this is a big hindrance to a smooth site running.
>
> > Can anyone help, or is this something unrelated to the newforms admin?
>
> Not sure, but it might be related to this change:
>
> http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Chang...
>
> rather than newforms-admin.
>
> Karen
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---