On Fri, 2008-12-05 at 03:17 -0600, James Bennett wrote:
> On Fri, Dec 5, 2008 at 2:07 AM, Florian Lindner <[EMAIL PROTECTED]> wrote:
> > Last time I used Django (pre 1.0) it was recommended to always use
> > trunk since the last released version was too outdated. Has this
> > changed?
>
> Yes.
On Fri, Dec 5, 2008 at 2:07 AM, Florian Lindner <[EMAIL PROTECTED]> wrote:
> Last time I used Django (pre 1.0) it was recommended to always use
> trunk since the last released version was too outdated. Has this
> changed?
Yes.
0.96 -> 1.0 involved a large number of backwards-incompatible
Am 04.12.2008 um 21:58 schrieb [EMAIL PROTECTED]:
>
> On 04.12-20:22, Florian Lindner wrote:
> [ ... ]
>> I use the comments framework from the newest Django SVN checkout.
>
> sorry to not be of more help (i've never used the comments framework)
> but i can only suggest that you select a
On 04.12-20:22, Florian Lindner wrote:
[ ... ]
> I use the comments framework from the newest Django SVN checkout.
sorry to not be of more help (i've never used the comments framework)
but i can only suggest that you select a release version and not the
'newest' (i'm assuming that means trunk).
Hello,
since noone replied and I still found no answer I dare to repost.
I use the comments framework from the newest Django SVN checkout.
I have in my template:
{% load comments % }
[...]
{% render_comment_form for object %}
resulting in a Invalid block tag: 'render_comment_form'
I have
5 matches
Mail list logo