Skip to main content
8 events
when toggle format what by license comment
Jun 18, 2017 at 17:21 comment added JAyenGreen I've added some clarifying information to the end of the description up top...it's a more interesting problem that I first thought.
May 22, 2017 at 20:57 comment added JAyenGreen I take that last comment back. I just checked the db and the subjects are trimmed body, which in itself is interesting because no one explicitly entered a subject, but in any event, the comment body entries are complete, so it appears that it's just that {{content}} in the twig file is not being populated at all.
May 22, 2017 at 20:46 comment added JAyenGreen What's more, the markup shows each trimmed comment as a h3 link, which I suspect is meant to hold the comment subject. There is a <content> tag indented below it, which is empty in each comment.
May 22, 2017 at 20:42 comment added JAyenGreen That doesn't seem to be it. I was going to create a Full (comment.full) mode, but there already is one. The comment type display settings only offers default and trimmed, but the comment field on the content type settings is set to default and has full available. When I select that and clear cache, there is no difference.
May 22, 2017 at 14:56 comment added Julien FRATICELLI My best guess is that "trimmed" and "default" settings are created within the comment module which is part of drupal core. Maybe you could try creating a new view mode (/admin/structure/display-modes/view/add/node), set it up on your article display page and see if you have the same problem in that mode (you can change the view used when you preview a node).
May 22, 2017 at 13:52 comment added JAyenGreen It is set to 'default,' as opposed to 'trimmed.' That does beg the question of from where the meaning of 'default' is determined.
May 22, 2017 at 13:13 review First posts
May 22, 2017 at 15:28
May 22, 2017 at 13:08 history answered Julien FRATICELLI CC BY-SA 3.0