Problem
Teasers for 'Articles' are only showing the title on the front page. None of the body text. Even though, under "Manage display" for 'Teaser' for the 'Article' content type, the format is set to "Summary or trimmed" and it shows "Trimmed limit: 600 characters".
If I put text in the Summary field, it works.
For the 'Basic page' content type it seems to display the teasers fine. It has the same setting under "Manage display".
However, if I insert a <!--break-->in the 'Basic page' content, rather than break the teaser display there, it also does not show any of the body in the teaser. Only the title. Also it displays the <!--break--> literally in the body when viewing the page.
I had the problem with Drupal 8.1.7 then upgraded to 8.2.0 and still have the same problem.
OS: FreeBSD 10.2
Web server: nginx 1.10.1
PHP version: 7.0.10
mysql version: 5.7.13
Comments
Comment #2
vls commentedNew information:
It turns out that the
<!--break-->tag is working. It was my mistake. I forgot to insert it in Source mode rather than wysiwyg mode.That gives me a work around. However the main problem still exists. The 'Article' content type teaser is working if I use the break tag but it still does not show the trimmed content without it.
Comment #3
cilefen commentedHi @vls:
I can't reproduce what you have seen. What is the format configuration for the front page view page display?
Comment #4
vls commentedHi cilefen.
on /admin/structure/views/view/frontpage
It shows
And if I click "Settings" it has
Add views row classeschecked.
I hope this is what you were asking.
Comment #5
dawehnerJust moving to the node system
Comment #6
cilefen commentedYes, that is what I was asking.
Comment #7
vls commentedOne thing I might add, in case it's of any help. I have multiple Drupal 7 sites on this same machine under the same mysql and php software and they have no teaser problems.
Comment #8
cilefen commentedI am curious to know if the teasers are visible in the Views UI for the frontpage view.
Comment #9
vls commentedcilefen, They are visible now. Now it's working correctly. Apparently it was something about the test content I was using. Now I cannot remember what text I was using that caused the problem. I guess, if I can find the text I was using, I will have to follow up with how to reproduce it.
Thanks for trying to help resolve it.
Comment #10
wim leers