Bug 20464 - On public reports, the behavior of cache-expiry 0 is confusing to users
Summary: On public reports, the behavior of cache-expiry 0 is confusing to users
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Reports (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-22 22:00 UTC by Barton Chittenden
Modified: 2022-01-28 14:41 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barton Chittenden 2018-03-22 22:00:25 UTC
When a report is made public, 'cache-expiry' is the number of seconds that the results will remain cached from the last run -- *except* if this is set to 0, in which case the cache never expires.

This behavior is *very* confusing to users, who expect the cache to expire immediately if the expiry is 0, and get exactly the opposite behavior.

This is a frequent support issue -- This should at least be better labeled (perhaps with a javascript warning?), if we can't find a path toward changing the behavior.
Comment 1 Liz Rea 2018-06-29 03:02:59 UTC
This setting seems to be gone in Master.
Comment 2 Liz Rea 2018-06-29 03:03:25 UTC
Oh I lie, you have to have the caching turned on. ignore that.