- πΊπΈUnited States mlncn Minneapolis, MN, USA
Expose title and base fields in Manage Display are visible on the horizon! Without much squinting needed, even.
- π¦πΉAustria plepe
I extended the module by twig templates. There's a switch in the configuration, where you can select between tokens or twig templates. I haven't created a patch (yet), for now it is available on Github.
Examples, how you can use it:
{{ entity.field_name[0].value }}
{% for v in entity.field_name %}{{ v.value|upper }} {% endfor %}
How shall we proceed? Shall this modification be merged into the module? Shall I create a separate issue with the merge request?
- π«π·France dqd London | N.Y.C | Paris | Hamburg | Berlin
Sorry @marcvangend #10 π± Custom label logic with Twig or plugins (as replacement for 'Use PHP') Active that I changed the title too hasty in that busy days. You added the PHP notice for users missing the PHP option to find this issue regarding the comment above (reverted back with hopefully more detail that it replaces the "use PHP" functionality from before).
For those who still do not understand why this formerly "use PHP" feature had to be removed, please read the very well layed out comments of @dww regarding security here above for example in #16 and #12. Additionally: Big thanks to @dww for working on it here and elsewhere in Drupal.
@AdamPS Regarding base fields: is https://www.drupal.org/project/manage_display β still relevant and can it be used side by side with cores slidely implementation?
Apart from the awesome concepts, ideas and thoughts have been put in here over the time to move forward (many thanks to all the input) can we elaborate on the question I tried to raise in #19 π± Custom label logic with Twig or plugins (as replacement for 'Use PHP') Active please? It was meant as a help for those who put a lot of efforts in here while core changes in parts of this projects scope.
Problem/Motivation for followers: This issue is about a massive work on a new plugin or Twig implementation and it needs to be secured that there are no efforts waisted. There is a big change in Drupal core coming regarding base fields and this can change the scope or way of this project.