Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Problem/Motivation
By definition the Time ago formatter should never be render cached.
It currently gets render cached.
Proposed resolution
?
Remaining tasks
User interface changes
None.
API changes
None.
Beta phase evaluation
Issue category | Bug because outdated information can be displayed |
---|---|
Issue priority | Normal because the data is not corrupt and also this can only be triggered by manually using the Time ago formatter |
Prioritized changes | Prioritized because it is a bug |
Disruption | No disruption |
Comments
Comment #1
tstoecklerComment #2
dawehnerDoes that mean we should define a post_render_cache thing for the timestamp ago formatter?
Comment #11
catchMarking duplicate of #2921810: Allow TimestampFormatter to show as a fully cacheable time difference with JS which has a patch.