On Sep 21, 10:37 am, Daniel Roseman wrote:
>
> Anything in a child template that is outside of a
> {% block %} is ignored.
>
I usually have a few {% load %} tags in child templates above {% block
%} to bring in needed template tags.
BN
--~--~-~--~~~---~--~~
You r
> No, you are correct. Anything in a child template that is outside of a
> {% block %} is ignored
What about inside a {% block %}? Is it allowed to define an "override"
inside another block. In other words would wrapping the offending
construct in another block like in:
=== Derived Template
On Mon, Sep 21, 2009 at 11:25 AM, Michael Feingold wrote:
>
> I am somewhat confused about the semantics for nested block
> definitions.Let me explain:
> {% block %} tag serves two purposes a) define a hole (along with the
> default value) to be filled later and b) define the content to replace
>
I am somewhat confused about the semantics for nested block
definitions.Let me explain:
{% block %} tag serves two purposes a) define a hole (along with the
default value) to be filled later and b) define the content to replace
the current value of the hole.
As long as we are talking about a) I p
On Sep 21, 4:25 pm, Michael Feingold wrote:
> I am somewhat confused about the semantics for nested block
> definitions.Let me explain:
> {% block %} tag serves two purposes a) define a hole (along with the
> default value) to be filled later and b) define the content to replace
> the current val
5 matches
Mail list logo
