- 🇬🇧United Kingdom 2dareis2do
What I would add is that trim_length is not exposed as an option if not using either trimmed or summary and trimmed setting.
When no summary is specified, token [node:summary] uses formatter settings of teaser view mode in order to generate trimmed version of body field. If 'teaser' view mode is not configured, default text_summary_or_trimmed trim lengths will be used (600 characters atm)
However, existing code does not check what formatter is being used. Instead, it checks for trim_length setting only.
When some other field formatter (like Smart trim) is being used for teasers, summary is being generated incorrectly. This happens because Smart trim uses exactly the same trim_length setting, but it can be words, not characters.
In particular case, smart trim is configured to use 30 words. Token [node:summary] gives 30 characters, instead of default 600.
Add extra check for the formatter that is being used for teaser view mode for body field.
No
No
No
Needs work
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
What I would add is that trim_length is not exposed as an option if not using either trimmed or summary and trimmed setting.