On Feb 6, 9:43 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> It already results in a broken site, we're now just being a lot clearer
> about that.
Actually, it only resulted previously in a broken site if the extended
template was being used in more than one depth of inheritance.
>
>
My take on this.
Each BoundField already has 'as_' methods for widgets so 'as_p' would
not belong there.
But you can override __getitem__ in the Form/ BaseForm to return your
own version of BoundField that has a 'as_p' method.
On Feb 5, 6:46 am, David Cramer <[EMAIL PROTECTED]> wrote:
> We've
Solved : adding editable=False to the total field stops this
behaviour, so it was something I was doing wrong ;) Although I didn't
expect the posted data to override the data I set in save() ...
Cheers,
Mike
On Feb 5, 3:01 pm, MikeH <[EMAIL PROTECTED]> wrote:
> However, when I do the
On Wed, 2008-02-06 at 09:26 +0100, David Larlet wrote:
>
> Le 5 févr. 08 à 22:05, Malcolm Tredinnick a écrit :
>
> >
> >
> > On Tue, 2008-02-05 at 16:14 +0100, David Larlet wrote:
> >> Hello,
> >>
> >> I'd just updated my local version of django and it raises errors due
> >> to 7084 changeset
Le 5 févr. 08 à 22:05, Malcolm Tredinnick a écrit :
>
>
> On Tue, 2008-02-05 at 16:14 +0100, David Larlet wrote:
>> Hello,
>>
>> I'd just updated my local version of django and it raises errors due
>> to 7084 changeset (extends should be the first tag). I put all my
>> extends tags above all my
