On Jan 16, 3:41 am, stryderjzw <[EMAIL PROTECTED]> wrote:
> Thanks, everyone.
>
> I like this idea. That really helped. I hope this gets considered.
>
> Cheers,
> Justin
Ok, as soon as I get a chance, I'll get some docs and tests done and
post a ticket with a patch. That should greatly improve
Thanks, everyone.
I like this idea. That really helped. I hope this gets considered.
Cheers,
Justin
On Jan 3, 1:16 pm, AmanKow <[EMAIL PROTECTED]> wrote:
> I posted a diff on dpaste: http://dpaste.com/hold/29777/
>
> This is for a change to django/template/loader_tags.py
>
> This change would
I posted a diff on dpaste: http://dpaste.com/hold/29777/
This is for a change to django/template/loader_tags.py
This change would add an explicit reuse_block tag.
{% block menu %} ... {% endblock %}
...
{% reuse_block menu %}
This change will actually reuse the parsed block. It does not cr
> Use the user defined inclusion template tag or {% include %} standard
> taghttp://www.djangoproject.com/documentation/templates_python/#inclusio...
@Alex: That's not what he was asking for. He wants to be able to have
multiple blocks with the same name in a parent template and have them
get the
Use the user defined inclusion template tag or {% include %} standard
tag
http://www.djangoproject.com/documentation/templates_python/#inclusion-tags
On 3 янв, 01:52, stryderjzw <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have the same situation as a thread (http://groups.google.com/group/
> django-us
Hi,
I have the same situation as a thread (http://groups.google.com/group/
django-users/browse_thread/thread/2dbb2b7f01951a2/efbeb1f74be6e454?
lnk=gst&q=multiple+template+block) started in 2005. The idea is that
in my template, I want to use the same template block for both the
and tags.
I did
Alice wrote:
> thanks :)
>
> did anything ever come of it?
>
> I agree that if a clean implementation cannot be done, it shouldn't.
> There was another interesting idea that a block could be referenced as
> a variable
>
> {% block content %}
> {% endblock %}
>
> {{ content }}
>
> or perhaps
>
On 10/14/05, Alice <[EMAIL PROTECTED]> wrote:
> did anything ever come of it?
>
> I agree that if a clean implementation cannot be done, it shouldn't.
> There was another interesting idea that a block could be referenced as
> a variable
>
> {% block content %}
> {% endblock %}
>
> {{ content }}
>
thanks :)
did anything ever come of it?
I agree that if a clean implementation cannot be done, it shouldn't.
There was another interesting idea that a block could be referenced as
a variable
{% block content %}
{% endblock %}
{{ content }}
or perhaps
{{ __content__ }}
any feedback on this?
On 10/14/05, Alice <[EMAIL PROTECTED]> wrote:
> I thought it would be neat to have my main menu also displayed in the
> footer but formatted differently
Hey Alice,
See this previous discussion:
http://groups.google.com/group/django-users/browse_thread/thread/b2809610dcf8fa3e/6d8503293554cece
A
I thought it would be neat to have my main menu also displayed in the
footer but formatted differently
{% block main_menu %}
...
{% endblock %}
{% block main_menu %}
...
{% endblock %}
however I got this error
"TemplateSyntaxError: 'block' tag with name 'main_menu' appears more
than once"
11 matches
Mail list logo
