title: ezplatform render links with url and object name from multi-relational content item in content type
body: <p>does anyone know now to create a custom view type for ez platform? The default 3 have been exhausted and we need a new one for 'link'
  Alternatively, does anyone know how to use the <code>render( controller(</code> with a custom template as this would also resolve out block right now.</p>
  
  <p>Basically, we have a multi-relational field in a content object used and we need to print links to all the related contentIds, path works great but we cannot find a way to extract the name of the content object for the link without doing some fairly funky tpl logic of passing in params. </p>
  
  <p>EG: As a hack for now we can pass in "embed_type" as a custom param with the <code>render(controller("ez_content:viewAction"</code> to pull in an alternate view for the content object for a specific content type and view type.</p>
  
  <pre><code>{% if embed_type is defined %}
      {% include "embed/#{embed_type}.html.twig" %}
  {% else %}
          &lt;h1&gt;{{ ez_field_value( content, 'name') }}&lt;/h1&gt;
  {% endif %}
  </code></pre>
  
  <p>However, this is very ugly and all we really want to do is use 1 template for all content types, so all we need to do is loop through the relational field and print links (as the only thing available in the content field: "destination ids"). I am sure there used to be this option in the docs but i cannot find it anymore eg:</p>
  
  <pre><code>{% set links =  ez_field_value( footer, "first_links_row" ).destinationContentIds%}
  {% for id in links %}
     {{ render(controller("ez_content:viewAction", {"contentId": id, "template": "link.html.twig"})) }}
  {% endfor %}
  </code></pre>
  
  <p>Where the link.html.twig would simple print the link:</p>
  
  <pre><code>&lt;a href="{{ path( "ez_urlalias", {"contentId": id} ) }}"&gt;
     {{ ez_field_value( content, "name" ) }}
  &lt;/a&gt;
  </code></pre>
  
  <p>If using a custom tpl is not possible with the <code>render (controller (</code> helper then a new custom view type would also fix this issue, but i cannot find documentation for either.</p>