Using variables from inside symfony 2 / twig blocks

Question

I have this

base.html.twig

<html>
  {% block template_scope_vars %}
  {% endblock %}
  <head></head>
  <body>
    {% block content %}
    {% endblock %}
  </body>
</html>

user.html.twig

extends base...
{%block template_scope_vars %}
   {% set test= "bippo" %}
{%endblock%}

{%block content %}
   {{ test }}
{% endblock %}

Error

Variable "test" does not exist

Ok please please don't tell me that I don't have to use blocks for this, the use case is more difficult than this simple example obviously. The idea is that test gets available in the base.html.twig as well, as well as any sub-templates of it that I might be using in future

Not going to work the way you want it to. Blocks are pretty much independent. — Cerad
– Cerad, Commented May 21, 2014 at 0:11
@Cerad well that sucks big time. Is there something similar I could use? or some workaround? — Toskan
– Toskan, Commented May 21, 2014 at 0:21
@Cerad that is like shooting a pigeon with a nuclear bomb. Besides, it doesn't solve basic use cases where you have to do just a tiny bit of logic. Hmm a real big shortcoming which makes this templating mechanism a lot weaker than say, JSF from java — Toskan
– Toskan, Commented May 21, 2014 at 1:12
@Cerad looking at this: twig.sensiolabs.org/doc/tags/include.html probably I can create a new twig, where I only write {% set test="foobar" %} {% include 'user.html.twig' %} reading the doc, this should work. But I have to create a new file, which is stupid — Toskan
– Toskan, Commented May 21, 2014 at 1:26

Toskan · Accepted Answer · 2014-05-25 05:52:46Z

for the special use case I had I could use this. It is a shame though, there is no neater solution. All other solution I could come up with, would require to create a new file for each set of template scope variables. Which plain sucks

base.html.twig

<div id="menu"> //this is like a sidebar menu
                    <div class="menuitem  {% block foo %}{% endblock %}">
                    <a href="{{ path('MyBundle_my_routing_name_foo' }}">Foo</a>
                </div>
                    <div class="menuitem  {% block bar %}{% endblock %}">
                    <a href="{{ path('MyBundle_my_routing_name_bar' }}">Bar</a>
                </div>
<div>
{% block content %}
{% endblock %}

Then in

foo.html.twig

{% extends "MyBundle::base.html.twig" %}

{% block foo %}active{% endblock %}

{% block content %}
Some content specific for foo
{% endblock %}

bar.html.twig

{% extends "MyBundle::base.html.twig" %}

{% block bar%}active{% endblock %}

{% block content %}
Some content specific for bar
{% endblock %}

and then you set the css for the background of e.g.

CSS

menuitem.active {
background-color: red;
}

keyboardSmasher · Accepted Answer · 2014-05-25 15:31:42Z

0

base.html.twig

<div id="menu"> //this is like a sidebar menu
    <div class="menuitem{{ active == 'foo' ? ' active' : '' }}">
        <a href="{{ path('MyBundle_my_routing_name_foo') }}">Foo</a>
    </div>
    <div class="menuitem{{ active == 'bar' ? ' active' : '' }}">
        <a href="{{ path('MyBundle_my_routing_name_bar') }}">Bar</a>
    </div>
<div>
{% block content %}
{% endblock %}

foo.html.twig

{% extends "MyBundle:Whatever:base.html.twig" %}

{% block content %}
    {{ content }}
{% endblock %}

Controller

/**
 * @Route("/foo", defaults={"param" = null}, name="foo")
 * @Route("/foo/{param}", name="foo_with_param")
 * @Template()
 */
public function fooAction($param)
{
    // This would really be getting data from the Model
    if ($param == 'something') {
        $content = 'Some content';
        $active = 'foo';
    } else {
        $content = 'Different content';
        $active = 'bar';
    }

    return array(
        'content'=> $content,
        'active' => $active,
    );
}

When rendering foo.html.twig, base.html.twig will get the variable "active".

edited May 25, 2014 at 15:31

answered May 24, 2014 at 4:59

keyboardSmasher

2,83122 silver badges24 bronze badges

7 Comments

keyboardSmasher Over a year ago

@Toskan Which part? The annotations? At any rate, it's all in the symfony docs. I won't insult your intelligence by posting a link to them. You should probably set active once at the top of base.html.twig (In case it's not passed) E.g.: {% set active = active|default(false) %}, then you can shorten the other code a bit. {{ active == 'foo' ? ' active' : '' }}

Toskan Over a year ago

in case you get several return statements, e.g. redirects after persisting or after failed checks, you'll end up copy pasting this return array all over the place.

keyboardSmasher Over a year ago

@Toskan I don't think you get it. You HAVE to send data to the template. That's the whole point of MVC.

Toskan Over a year ago

feel free to explain why you have to send this data to the template. Does this ever change when the template does not change? Does it need to be controlled? No. This is template styling, nothing else. Template styling should not be part of the controller.

keyboardSmasher Over a year ago

@Toskan You talk about DRY, and then you say you want to create new almost identical template file for every active menu item? That is completely insane. foo.html.twig, bar.html.twig, baz.html.twig, etc. You just need one twig template for the menu and even just one controller that tells the template which menu item to highlight (among all of the other data that will be passed to it anyway).

|

Collectives™ on Stack Overflow

Using variables from inside symfony 2 / twig blocks

2 Answers 2

Comments

7 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

7 Comments

Your Answer

Sign up or log in

Post as a guest

Related