Timeline for Using the built in summary feature when using ONLY paragraphs module for text
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 14, 2020 at 16:13 | answer | added | frontend_dev | timeline score: 0 | |
| Jan 11, 2020 at 20:05 | comment | added | frontend_dev | Yeah, but still the user needs to fill in a separate summary. Usually just taking n chars from the main body text (or in this case the first paragraph containing text) should be enough. My users are just used to that workflow (the site in question is a rebuild of an older D6 site), and I want to avoid adding additional stuff. So yeah - and I am also simply curious how that could work - I still want to kinda "emulate" the default summary functionality. That also was my question in the first place ;) Any help still greatly appreciated. | |
| Jan 11, 2020 at 18:23 | comment | added | Kevin | Mark the field required? The summary doesn't have to be identical. The point of the field is explicitly for the purpose of setting a summary - you don't have to print it in the full node template. This in essence is how teaser/full view display works out of the box. | |
| Jan 11, 2020 at 13:45 | comment | added | frontend_dev | Yeah of course I could make another field ... but I know my users ;) I.e. they would forget, or complain why they have to edit two identical pieces of text all the time. I still would like to have an "automatic" solution! Anyone? | |
| Jan 11, 2020 at 1:06 | comment | added | Kevin | Also, if the user does not create a text paragraph or they add dozens of paragraphs to the node, two things will happen. In the first scenario there would still be no summary text. In the latter, you will possibly see performance issues especially if you are listing multiple nodes in a page. It is just more practical to reduce this to a field specifically for this purpose. | |
| Jan 11, 2020 at 0:52 | comment | added | Kevin | Yes, the easy thing to do here would be to add a text field to let the user add a summary (make it required) and output it in twig before the paragraph field. Then you can lose all this logic. That basically puts it back to the way it was, you are overthinking this. | |
| Jan 10, 2020 at 21:30 | review | Close votes | |||
| Feb 2, 2020 at 3:05 | |||||
| Jan 10, 2020 at 21:15 | comment | added | leymannx | Welcome to Drupal Answers! :-) Maybe try to keep it simple and just add another textfield to be used as "Summary" on top of the Paragraphs field and use its field formatters or other features to limit characters on input or output. | |
| Jan 10, 2020 at 18:20 | review | First posts | |||
| Jan 10, 2020 at 18:20 | |||||
| Jan 10, 2020 at 18:15 | history | asked | frontend_dev | CC BY-SA 4.0 |