If I include the body field in a view, there doesn't appear to be any way to get the safe summary as a replacement token.
Steps:
1. Create a website on simplytest.me using alpha14
2. Click manage
3. Click views
4. Click Add new view
5. View name test
6. Check Create a page
7. Click Save and edit
8. For show, click Content
9. Select Fields
10. Click Apply (all displays)
11. Click Apply
12. In the Fields section, click Add
13. In the search field, type body
14. Check Content: Body
15. Click Apply (all displays)
16. Expand Rewrite results
17. Check Override the output of this field with custom text
18. Click Replacement patterns
Actual results: Tokens available include the following for the body:
[body] == Body
[body-value] == Raw value
[body-summary] == Raw summary
[body-format] == Raw format
Expected results: Tokens available include the following for the body:
[body] == Body
[body-value] == Raw value
[body-summary] == Raw summary
[body-processed-summary] == Processed summary
[body-format] == Raw format
Comments
Comment #1
dawehnerWhat is a safe summary? Isn't that also rendered via check_markup already?
Comment #2
Charles BelovIn Drupal 7.x, if I display a content node using Devel, it is showing that Body has both safe and raw versions of the summary field, not just of the body field. If there's no need for a safe summary, then why would there be such an existing field. That said, it is possible that Drupal 8 does not have a safe summary field, in which case this issue would not apply to Drupal 8.
I see by Removed _text_sanitize() and safe_value/safe_summary in favor of processed/summary_processed. That still leaves the issue that I am only being offered the raw summary in views and not the processed summary.
Or are you saying that Views always renders through Check markup so everything by definition is safe when rendered by Views? That is, what Views is calling raw in the token description is not truly raw?
Comment #3
Charles Belov