2

I've noticed that our Blocks HTML output cache regularly needs to be refreshed, every day even when no one has been working on the Backend of Magento?

Why would this cache become invalid so frequently when no one has been updating CMS pages, static blocks, products etc?

What happens when the cache is invalid? Does Magento go to the file system rather than the cache when a cache is invalid?

We're using redis Backend cache, I'm thinking that perhaps redis does not have enough memory allocated to it.

Could this have something to do with this bug regarding Blocks HTML output cache on 1.9 https://www.magentocommerce.com/bug-tracking/issue/index/id/870

  • Have you looked at magento.stackexchange.com/questions/50064/… ? – Prateek Nov 16 '15 at 12:56
  • @Prateek, yes but it doesn't really answer what I'ma asking – Holly Nov 16 '15 at 12:59
  • Yes, it doesn't answer all the parts of your question, but it does have answer for "What happens when the cache is invalid? Does Magento go to the file system rather than the cache when a cache is invalid?" – Prateek Nov 16 '15 at 13:00
  • @Holy Block caching is used for more than just CMS pages. Are you making updates to products or categories? – brentwpeterson Nov 16 '15 at 16:24
  • @brentwpeterson, no it needs to be refreshed every morning after about 14 hours of no one touching the backend. – Holly Nov 16 '15 at 19:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.