- Issue created by @aaron gil martinez
- Merge request !7Issue #3462698 Field cache is not preserved → (Merged) created by aaron gil martinez
- Issue was unassigned.
- Status changed to Needs review
7 months ago 6:37am 22 July 2024 - Status changed to RTBC
7 months ago 3:46pm 26 July 2024 - First commit to issue fork.
- 🇩🇪Germany Grevil
Looks great!
Thanks a lot for the great test coverage! RTBC + 1 🙂👍
Only did some deprecation adjustments, as this module is D11 ready now!
-
grevil →
committed 42d00718 on 2.0.x authored by
Aaron Gil Martinez →
Issue #3462698 Field cache is not preserved
-
grevil →
committed 42d00718 on 2.0.x authored by
Aaron Gil Martinez →
- Status changed to Fixed
6 months ago 9:25am 27 August 2024 Automatically closed - issue fixed for 2 weeks with no activity.
- 🇨🇦Canada m4olivei Grimsby, ON
Hey there 👋. Just curious, does this update to the module mean that the following docs on the project page no longer apply? That is to say, on a quick read of the 2.x code it looks like cacheability metadata is now properly accounted for when using
field_raw
andfield_target_entity
Cache warning
The field_raw and field_target_entity filters do not provide any cache information. Without additional measures content printed with these filters will not be update when changed in the backend. You can workaround this by rendering the field in your template but not display the result. For example: {% set catch_cache = content.field_image|render %}