When using the Time-based (vs Tag-based) Views cache plugin, one can either use predefined durations (why isn't there a "1 day" duration, BTW ?), or use a custom duration, for which one has to input a duration in seconds.
However, these values are interpreted as 0 when saving the view.
frontpage. cache/options/(result|output)_lifespan properties are set to 0 for the fields set to a custom value, which suggests this is the mechanism meant to be used to identify the presence of custom values.When manually editing a view to set cache/options/(result|output)_lifespan[_custom], we can observe that the result displayed in the UI after importing the edited views is always the value of the cache/options/(result|output)_lifespan property, not cache/options/(result|output)_lifespan_custom one. This show the problem to be twofold:
Closed: duplicate
10.1 ✨
Last updated
Same underlying issue as 🐛 Time-based custom caching is broken since configuration expects an integer. Needs work which is older and has a patch, so marking this one as a duplicate although it contains other details.