annotate gpp/gcalendar/urls.py @ 507:8631d32e6b16

Some users are still having problems with the pop-up login. I think they are actually getting 403s because of the CSRF protection. So I have modified the base template to always have a javascript variable called csrf_token available when they aren't logged in. The ajax_login.js script was then modified to send this value with the ajax post. Fingers crossed.
author Brian Neal <bgneal@gmail.com>
date Sun, 04 Dec 2011 03:05:21 +0000
parents dbd703f7d63a
children ddd69a8e07c7
rev   line source
gremmie@1 1 """
gremmie@1 2 URLs for the gcalendar application.
gremmie@1 3 """
gremmie@1 4 from django.conf.urls.defaults import *
gremmie@1 5
gremmie@1 6 urlpatterns = patterns('gcalendar.views',
gremmie@1 7 url(r'^$', 'index', name='gcalendar-index'),
gremmie@1 8 url(r'^add/$', 'add_event', name='gcalendar-add'),
gremmie@1 9 url(r'^change/$', 'edit_events', name='gcalendar-edit_events'),
gremmie@1 10 url(r'^change/(\d+)/$', 'edit_event', name='gcalendar-edit_event'),
gremmie@1 11 url(r'^delete/$', 'delete_event', name='gcalendar-delete'),
gremmie@1 12 url(r'^thanks/add/$', 'add_thanks', name='gcalendar-add_thanks'),
gremmie@1 13 url(r'^thanks/change/$', 'edit_thanks', name='gcalendar-edit_thanks'),
gremmie@1 14 )
gremmie@1 15 # vim: ts=4 sw=4