Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
render system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Mar 2015 at 14:00 UTC
Updated:
3 Apr 2015 at 14:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
wim leersComment #2
fabianx commentedI think we miss some test coverage here, but yes straight follow-up.
Comment #4
Dragooon commentedUpdated tests for the patch
Comment #7
Dragooon commentedMissed a few cases in past patch
Comment #8
fabianx commentedComment #9
cosmicdreams commentedShould these be 0 instead of -1? In the #2443073: Add #cache[max-age] to disable caching and bubble the max-age issue I saw that setting these to 0 was effectively saying don't cache them.
Comment #11
fabianx commentedThat should be Cache::PERMANENT instead, which is == -1;
Comment #12
Dragooon commentedSo, replace -1 with Cache::PERMANENT instead?
Comment #13
wim leers#11++
#9: the default value is
Cache::PERMANENT— we assume permanent cacheability; it's up to the code building the render array to specify a non-permanent max-age and the associated cache tags to ensure it's invalidated when appropriate.Comment #14
wim leers#12: yes! And thank you very much for taking this one on :)
Comment #15
Dragooon commented#14; Okay, understood. It sets the value of max-age to Cache::PERMANENT by default instead of hardcoded -1, should've checked that before. Thanks!
Comment #16
Dragooon commentedComment #18
fabianx commentedNice work, RTBC.
This is just a straight bug fix that was overseen from a previous issue.
Comment #19
alexpottThis issue is a normal bug fix, and doesn't include any disruptive changes, so it is allowed per https://www.drupal.org/core/beta-changes. Committed cc54a48 and pushed to 8.0.x. Thanks!