Block HTML output cache needs refresh from time to time












0















I am the only administrator of the store. I am doing before night a Flush Cache Storage in order to get the following issue. In the morning I visit again the backend and there is a warning message "One or more of the Cache Types are invalidated: Blocks HTML output. Click here to go to Cache Management and refresh cache types."



Blocks HTML output warning reacts once you make changes in backend. Is anyone knowing why Blocks HTML output cache needs a refresh after a few hours without touching the backend?










share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    I am the only administrator of the store. I am doing before night a Flush Cache Storage in order to get the following issue. In the morning I visit again the backend and there is a warning message "One or more of the Cache Types are invalidated: Blocks HTML output. Click here to go to Cache Management and refresh cache types."



    Blocks HTML output warning reacts once you make changes in backend. Is anyone knowing why Blocks HTML output cache needs a refresh after a few hours without touching the backend?










    share|improve this question
















    bumped to the homepage by Community 11 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      I am the only administrator of the store. I am doing before night a Flush Cache Storage in order to get the following issue. In the morning I visit again the backend and there is a warning message "One or more of the Cache Types are invalidated: Blocks HTML output. Click here to go to Cache Management and refresh cache types."



      Blocks HTML output warning reacts once you make changes in backend. Is anyone knowing why Blocks HTML output cache needs a refresh after a few hours without touching the backend?










      share|improve this question
















      I am the only administrator of the store. I am doing before night a Flush Cache Storage in order to get the following issue. In the morning I visit again the backend and there is a warning message "One or more of the Cache Types are invalidated: Blocks HTML output. Click here to go to Cache Management and refresh cache types."



      Blocks HTML output warning reacts once you make changes in backend. Is anyone knowing why Blocks HTML output cache needs a refresh after a few hours without touching the backend?







      block-cache






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 3 '16 at 13:13









      Amit Bera

      58.9k1575175




      58.9k1575175










      asked Jan 2 '16 at 19:35









      ADDISON74ADDISON74

      412514




      412514





      bumped to the homepage by Community 11 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 11 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Your cron will run at specified intervals, such as every 5 minutes.
          Magento, will throw that message if any block has been modified. This can be from products, to CMS, or anything that is in a cached block. This is expected behavior you are experiencing.
          You can look here for some reasons:
          Mage::app()->getCacheInstance()->getInvalidatedTypes();
          That is found in this class



          Mage_Core_Model_Cache

          /**
          * Get array of all invalidated cache types
          *
          * @return array
          */
          public function getInvalidatedTypes()
          {
          $invalidatedTypes = array();
          $types = $this->_getInvalidatedTypes();
          if ($types) {
          $allTypes = $this->getTypes();
          foreach ($types as $type => $flag) {
          if (isset($allTypes[$type]) && $this->canUse($type)) {
          $invalidatedTypes[$type] = $allTypes[$type];
          }
          }
          }
          return $invalidatedTypes;
          }


          There are many reason why a block may be invalidated, I guess I would not worry too much about it. However, if your customer will eventually not just take our word that things are working fine, you can create an observer that fixes the invalid blocks when an admin user logs in the site. That seems a bit much but I have had non technical customers before and sometimes its easier just to find a fix rather than try to explain the depths of Magento to a store owner.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "479"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f95721%2fblock-html-output-cache-needs-refresh-from-time-to-time%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Your cron will run at specified intervals, such as every 5 minutes.
            Magento, will throw that message if any block has been modified. This can be from products, to CMS, or anything that is in a cached block. This is expected behavior you are experiencing.
            You can look here for some reasons:
            Mage::app()->getCacheInstance()->getInvalidatedTypes();
            That is found in this class



            Mage_Core_Model_Cache

            /**
            * Get array of all invalidated cache types
            *
            * @return array
            */
            public function getInvalidatedTypes()
            {
            $invalidatedTypes = array();
            $types = $this->_getInvalidatedTypes();
            if ($types) {
            $allTypes = $this->getTypes();
            foreach ($types as $type => $flag) {
            if (isset($allTypes[$type]) && $this->canUse($type)) {
            $invalidatedTypes[$type] = $allTypes[$type];
            }
            }
            }
            return $invalidatedTypes;
            }


            There are many reason why a block may be invalidated, I guess I would not worry too much about it. However, if your customer will eventually not just take our word that things are working fine, you can create an observer that fixes the invalid blocks when an admin user logs in the site. That seems a bit much but I have had non technical customers before and sometimes its easier just to find a fix rather than try to explain the depths of Magento to a store owner.






            share|improve this answer




























              0














              Your cron will run at specified intervals, such as every 5 minutes.
              Magento, will throw that message if any block has been modified. This can be from products, to CMS, or anything that is in a cached block. This is expected behavior you are experiencing.
              You can look here for some reasons:
              Mage::app()->getCacheInstance()->getInvalidatedTypes();
              That is found in this class



              Mage_Core_Model_Cache

              /**
              * Get array of all invalidated cache types
              *
              * @return array
              */
              public function getInvalidatedTypes()
              {
              $invalidatedTypes = array();
              $types = $this->_getInvalidatedTypes();
              if ($types) {
              $allTypes = $this->getTypes();
              foreach ($types as $type => $flag) {
              if (isset($allTypes[$type]) && $this->canUse($type)) {
              $invalidatedTypes[$type] = $allTypes[$type];
              }
              }
              }
              return $invalidatedTypes;
              }


              There are many reason why a block may be invalidated, I guess I would not worry too much about it. However, if your customer will eventually not just take our word that things are working fine, you can create an observer that fixes the invalid blocks when an admin user logs in the site. That seems a bit much but I have had non technical customers before and sometimes its easier just to find a fix rather than try to explain the depths of Magento to a store owner.






              share|improve this answer


























                0












                0








                0







                Your cron will run at specified intervals, such as every 5 minutes.
                Magento, will throw that message if any block has been modified. This can be from products, to CMS, or anything that is in a cached block. This is expected behavior you are experiencing.
                You can look here for some reasons:
                Mage::app()->getCacheInstance()->getInvalidatedTypes();
                That is found in this class



                Mage_Core_Model_Cache

                /**
                * Get array of all invalidated cache types
                *
                * @return array
                */
                public function getInvalidatedTypes()
                {
                $invalidatedTypes = array();
                $types = $this->_getInvalidatedTypes();
                if ($types) {
                $allTypes = $this->getTypes();
                foreach ($types as $type => $flag) {
                if (isset($allTypes[$type]) && $this->canUse($type)) {
                $invalidatedTypes[$type] = $allTypes[$type];
                }
                }
                }
                return $invalidatedTypes;
                }


                There are many reason why a block may be invalidated, I guess I would not worry too much about it. However, if your customer will eventually not just take our word that things are working fine, you can create an observer that fixes the invalid blocks when an admin user logs in the site. That seems a bit much but I have had non technical customers before and sometimes its easier just to find a fix rather than try to explain the depths of Magento to a store owner.






                share|improve this answer













                Your cron will run at specified intervals, such as every 5 minutes.
                Magento, will throw that message if any block has been modified. This can be from products, to CMS, or anything that is in a cached block. This is expected behavior you are experiencing.
                You can look here for some reasons:
                Mage::app()->getCacheInstance()->getInvalidatedTypes();
                That is found in this class



                Mage_Core_Model_Cache

                /**
                * Get array of all invalidated cache types
                *
                * @return array
                */
                public function getInvalidatedTypes()
                {
                $invalidatedTypes = array();
                $types = $this->_getInvalidatedTypes();
                if ($types) {
                $allTypes = $this->getTypes();
                foreach ($types as $type => $flag) {
                if (isset($allTypes[$type]) && $this->canUse($type)) {
                $invalidatedTypes[$type] = $allTypes[$type];
                }
                }
                }
                return $invalidatedTypes;
                }


                There are many reason why a block may be invalidated, I guess I would not worry too much about it. However, if your customer will eventually not just take our word that things are working fine, you can create an observer that fixes the invalid blocks when an admin user logs in the site. That seems a bit much but I have had non technical customers before and sometimes its easier just to find a fix rather than try to explain the depths of Magento to a store owner.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 3 '16 at 17:10









                RussellAlbinRussellAlbin

                41437




                41437






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Magento Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f95721%2fblock-html-output-cache-needs-refresh-from-time-to-time%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    What other Star Trek series did the main TNG cast show up in?

                    Berlina muro

                    Berlina aerponto