On Mon, 2006-07-10 at 11:05 +0000, [EMAIL PROTECTED] wrote:
> Hi Adrian, thanks for replying. The project's urls.py does include the
> urls.py I've shown, but here they are:
> 
> cat urls.py
> from django.conf.urls.defaults import *
> 
> urlpatterns = patterns('',
>     # Uncomment this for admin:
>     (r'^admin/', include('django.contrib.admin.urls')),
>     (r'^user/login/$',
> 'django.contrib.auth.views.login',{'template_name':'user/login.html'}),
>     (r'^user/logout/$',
> 'django.contrib.auth.views.logout',{'template_name':'user/logout.html'}),
>     (r'^.*$', include('lisa.forge.urls')),

This reg-exp ("^.*$") will chew up everything in the URL before passing
the remainder (which is now nothing) onto the next section. The Django
URL matching strips off the first pieces it matches before passing down
to an "include" section. This makes sense, when you think about it,
because then the lower levels don't need to know what the first parts of
the URL path are and you can rename/reorganise easily as you re-use
apps.

If you want "everything else" to be passed off to lisa.forge.urls,
something like '' as your match string should do the trick (matches
every string, without consuming anything).

Regards,
Malcolm



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to