On Wed, Jun 2, 2010 at 9:35 AM, Carl Nobile <carl.nob...@gmail.com> wrote: > Nothing has changed at all. I was just going through the steps to > migrate my code base to Django 1.2.1 and this stopped working. If I > comment out the decorator everything works just fine minus the > protection of cause. The internal wrapper (closure) in the decorator > is failing when it tries to get 'request.user'. Also I see that > Django 1.2.1 now comes with jQuery 1.4.2 by default. I'm now including > it twice, so I need to fix this also and move my JavaScript to later > in the <script> tags.
Loading a JavaScript twice can cause problems. I'd be tempted to fix this first. Too, if you can run under the development server, putting a pdb.set_trace() in your AJAX view will let you examine the request to see if the cookie is there. Good luck, Bill -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
