Counter block and views should have appropriate cache metadata set in order for it to refresh data after invalidation as well as provide user control of when the data should be refreshed.

Comments

gauravmanerkar created an issue. See original summary.

gaurav_manerkar’s picture

gaurav_manerkar commented
Issue summary: View changes
gaurav.kapoor’s picture

gaurav.kapoor commented
Title: Counter data gets cached » Set proper cache tags and other settings for the counter block and views.
Issue summary: View changes
Issue tags: -

Modified issue summary to resolve the original issue as well as improve overall performance on the Counter block.

  • gaurav.kapoor authored 5b12d64 on 8.x-1.x 
    Issue #2790405 by gaurav.kapoor: Set proper cache tags and other...
gaurav.kapoor’s picture

gaurav.kapoor commented
Status: Active » Fixed

For now, I have added cache tags related to counter configuration and a custom cache tag. The block gets refreshed whenever the configuration is changed or the custom tag is invalidated programmatically. Also, added a setting and cron job which will ensure custom cache tags get invalidated on every cron run.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.