Timeline for Accessing content variables through the page variable
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2016 at 3:54 | comment | added | tanbog | I still do not have a working solution for this. Shawn Conn's answer does not work all the time and often triggers the error I outlined above. | |
| Sep 16, 2016 at 3:53 | vote | accept | tanbog | ||
| Sep 16, 2016 at 3:53 | |||||
| Aug 13, 2016 at 6:10 | comment | added | tanbog |
When I try print out a field consisting of a taxonomy term: eg {{ node.field_tax_term.value }} I get a user error: User error: "target_id" is an invalid render array key in Drupal\Core\Render\Element::children() (line 97 of core/lib/Drupal/Core/Render/Element.php). If I print it out on the node the same field works fine. Do taxonomy terms behave differently?
|
|
| Aug 7, 2016 at 13:29 | vote | accept | tanbog | ||
| Sep 16, 2016 at 3:53 | |||||
| Aug 7, 2016 at 7:35 | comment | added | Berdir | Correct but note that this does not include the rendered fields that are available as content in the node template. You can only access the raw values. You can use the view() API method on the fields to prepare rendered fields yourself or you can use an entity view block, e.g. provided by the ctools module to display some fields somewhere in a block. | |
| Aug 7, 2016 at 7:23 | history | answered | Shawn Conn | CC BY-SA 3.0 |