On May 28, 2009, at 3:17 PM, Kevin Fullerton wrote:
> > On Thu, May 28, 2009 01:50, Eric Abrahamsen wrote: >> >> On May 28, 2009, at 4:02 AM, Kevin Fullerton wrote: >> >>> >>> I'm working with django.contrib.comments at the moment, and so far >>> most >>> things are working as expected. > > <snip> > >> >> It's a known problem and the patch for this is already in trunk – >> update to r10418 or later, or you can stick the patch in yourself >> (it's a pretty clean one-liner). >> >> HTH, >> Eric >> > > Thanks Eric, I'm running r10858 and having this problem - I've > removed any > comments templates I've overridden in my application and still > getting the > same problem - when the next parameter is passed in, it gets > ignored :( The default comment form does not include a next parameter, so if you don't override the builtin comment templates you won't get any next parameters in the forms. The most sure way of doing this is using a custom comment form with a next field – that way the form will include the field no matter where it is used in your project. Otherwise, you can use custom comment form and preview form templates – I'm guessing you originally didn't have a custom preview template, which meant it was using the builtin one, which meant... no next parameter in the html form. Hopefully something in there will work! Eric > > Many thanks > > Kevin > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
