Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Solution: So in fact the method was right, I have to use the <code>raw</code> filter to get my variable not escaped. I've an <code>autoescape</code> block set that englobe this particular output which is why the reason it has to be "un-escaped".</p> <p>Twig bundle of Symfony 2 provided several block to render form data, and those uses a specific block for attribute rendering called <code>{% block widget_attributes %}</code>.</p> <p>What I did is edit this block (I've a separated template file with all my customized blocks) so I can add a layer of "should this value be escaped or not":</p> <pre><code>{% block widget_attributes %} {% spaceless %} id="{{ id }}" name="{{ full_name }}"{% if read_only %} disabled="disabled"{% endif %}{% if required %} required="required"{% endif %}{% if max_length %} maxlength="{{ max_length }}"{% endif %}{% if pattern %} pattern="{{ pattern }}"{% endif %} {% for attrname,attrvalue in attr %} {# Attribute value can be defined as an array. ['data']: contains the actual value, ['escape']: boolean (true if the value HAS to be escaped)#} {% if attrvalue.data is defined %} {% if not attrvalue.escape %} {{ attrname }}="{{ attrvalue.data|raw }}" {% else %} {{ attrname }}="{{ attrvalue.data|e }}" {% endif %} {% else %} {{ attrname }}="{{ attrvalue }}" {% endif %} {% endfor %} {% endspaceless %} {% endblock widget_attributes %} </code></pre> <p>Called from my twig file:</p> <pre><code>{{ form_widget(form.displays.get('prototype').myField, {'attr': {'value': { 'data': myvalue, 'escape': false } } }) }} </code></pre> <p>The escape is done when printing the value so in the <code>{{ }}</code> twig tag, so what I was doing earlier was sending an unescaped value to a block where the print is actually called and where the value was thus escaped.</p> <p>This works for me! thanks!</p>
    singulars
    1. This table or related slice is empty.
    1. POSymfony 2, Twig: how not to escape field value (used with backbonejs & symfony 2)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAdam Elsodaney
    1. USLEM01
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSymfony 2, Twig: how not to escape field value (used with backbonejs & symfony 2)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload