On Mar 5, 6:50 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> In the meantime, use the url(...) form for your url patterns and give
> each one that might cause confusion a unique name. That way you can
> refer to them uniquely in the {% url ... %} tag.
Ok, I'll do that when the next Django
On Tue, 2008-03-04 at 18:30 -0800, msoulier wrote:
> So, my urlconf is
>
> urlpatterns = patterns('teleworker.clients.views',
> (r'create/$', 'create'),
> (r'modify/(?P\d+)/$', 'modify'),
> (r'delete/(?P\d+)/$', 'delete'),
> (r'page/(?P\d+)/(?P\w+)/(?P\w+)/$',
> 'list'),
>
More than one match for one {% url view args %} doesn't sound right,
you can name your patterns to clear up any ambiguity -
http://www.djangoproject.com/documentation/url_dispatch/#naming-url-patterns
On Mar 5, 2:30 am, msoulier <[EMAIL PROTECTED]> wrote:
> So, my urlconf is
>
> urlpatterns =
So, my urlconf is
urlpatterns = patterns('teleworker.clients.views',
(r'create/$', 'create'),
(r'modify/(?P\d+)/$', 'modify'),
(r'delete/(?P\d+)/$', 'delete'),
(r'page/(?P\d+)/(?P\w+)/(?P\w+)/$',
'list'),
(r'page/(?P\d+)/$', 'list'),
(r'^$', 'list'),
)
The list function
4 matches
Mail list logo