Magento 2 “we can't find products matching the selection” page cache invalidates












3















Update: I believe this issue may have been caused by a crossover between the cron:run & indexer:reindex cron jobs running every minute, I have changed the reindex job to run every hour instead of every minute and so far the FPC has not invalidated



Magento 2.1.7 installation



Cron jobs set to run every minute (cache clear, reindex etc)
Using either built-in or Varnish (TTL attribute removed from XML due to disappearing navbar)



It seems that the something is causing the "no products" message regardless of whether the full page cache is enabled or disabled, as soon as the cache is cleared (manually or by cron) then the products will reappear upon refresh.



But it is not good for the customers to be browsing pages and then be shown an empty page.



The cache is invalidating regardless of whether changes are made to the catalog or not. Perhaps one of the other cron jobs is invalidating the cache?



List of cron jobs:



/public_html/update/cron.php > /dev/null
/public_html/bin/magento cron:run > /dev/null
/public_html/bin/magento indexer:reindex > /dev/null
/public_html/bin/magento cache:clean > /dev/null
/public_html/bin/magento setup:cron:run > /dev/null


Hoping someone has suffered a similar issue with a fix



RM










share|improve this question





























    3















    Update: I believe this issue may have been caused by a crossover between the cron:run & indexer:reindex cron jobs running every minute, I have changed the reindex job to run every hour instead of every minute and so far the FPC has not invalidated



    Magento 2.1.7 installation



    Cron jobs set to run every minute (cache clear, reindex etc)
    Using either built-in or Varnish (TTL attribute removed from XML due to disappearing navbar)



    It seems that the something is causing the "no products" message regardless of whether the full page cache is enabled or disabled, as soon as the cache is cleared (manually or by cron) then the products will reappear upon refresh.



    But it is not good for the customers to be browsing pages and then be shown an empty page.



    The cache is invalidating regardless of whether changes are made to the catalog or not. Perhaps one of the other cron jobs is invalidating the cache?



    List of cron jobs:



    /public_html/update/cron.php > /dev/null
    /public_html/bin/magento cron:run > /dev/null
    /public_html/bin/magento indexer:reindex > /dev/null
    /public_html/bin/magento cache:clean > /dev/null
    /public_html/bin/magento setup:cron:run > /dev/null


    Hoping someone has suffered a similar issue with a fix



    RM










    share|improve this question



























      3












      3








      3








      Update: I believe this issue may have been caused by a crossover between the cron:run & indexer:reindex cron jobs running every minute, I have changed the reindex job to run every hour instead of every minute and so far the FPC has not invalidated



      Magento 2.1.7 installation



      Cron jobs set to run every minute (cache clear, reindex etc)
      Using either built-in or Varnish (TTL attribute removed from XML due to disappearing navbar)



      It seems that the something is causing the "no products" message regardless of whether the full page cache is enabled or disabled, as soon as the cache is cleared (manually or by cron) then the products will reappear upon refresh.



      But it is not good for the customers to be browsing pages and then be shown an empty page.



      The cache is invalidating regardless of whether changes are made to the catalog or not. Perhaps one of the other cron jobs is invalidating the cache?



      List of cron jobs:



      /public_html/update/cron.php > /dev/null
      /public_html/bin/magento cron:run > /dev/null
      /public_html/bin/magento indexer:reindex > /dev/null
      /public_html/bin/magento cache:clean > /dev/null
      /public_html/bin/magento setup:cron:run > /dev/null


      Hoping someone has suffered a similar issue with a fix



      RM










      share|improve this question
















      Update: I believe this issue may have been caused by a crossover between the cron:run & indexer:reindex cron jobs running every minute, I have changed the reindex job to run every hour instead of every minute and so far the FPC has not invalidated



      Magento 2.1.7 installation



      Cron jobs set to run every minute (cache clear, reindex etc)
      Using either built-in or Varnish (TTL attribute removed from XML due to disappearing navbar)



      It seems that the something is causing the "no products" message regardless of whether the full page cache is enabled or disabled, as soon as the cache is cleared (manually or by cron) then the products will reappear upon refresh.



      But it is not good for the customers to be browsing pages and then be shown an empty page.



      The cache is invalidating regardless of whether changes are made to the catalog or not. Perhaps one of the other cron jobs is invalidating the cache?



      List of cron jobs:



      /public_html/update/cron.php > /dev/null
      /public_html/bin/magento cron:run > /dev/null
      /public_html/bin/magento indexer:reindex > /dev/null
      /public_html/bin/magento cache:clean > /dev/null
      /public_html/bin/magento setup:cron:run > /dev/null


      Hoping someone has suffered a similar issue with a fix



      RM







      magento2 full-page-cache






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 29 '17 at 10:20







      Richard-Sinnis

















      asked Aug 29 '17 at 9:56









      Richard-SinnisRichard-Sinnis

      1815




      1815






















          2 Answers
          2






          active

          oldest

          votes


















          3














          It seems to be a known issue with Magento2



          https://github.com/magento/magento2/issues/8189



          Still an open issue am afraid :(






          share|improve this answer
























          • Thank you very much, hopefully that will be resolved soon!

            – Richard-Sinnis
            Aug 29 '17 at 13:17











          • Please include the release this bug would have been fixed in, so that people know if this issue no longer applies to their situation.

            – J. M. Becker
            Dec 16 '18 at 19:09



















          0














          I also Got same text by using SM Market Theme,



          I figure it how to solve the problem(may be help)



          1- enable template hints for frontends



          ex.app/design/frontend/Sm/market/Sm_FilterProducts/templates/default-sidebar.phtml


          2- refresh the page with the error



          3- get the template file path, then remove the unwanted div



          My Code As Below:



           <!--  <div class="message info empty">
          <div>
          <?php /* @escapeNotVerified */
          //echo __('We can't find products matching the selection.')
          ?>
          </div>
          </div>-->





          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%2f191010%2fmagento-2-we-cant-find-products-matching-the-selection-page-cache-invalidates%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            It seems to be a known issue with Magento2



            https://github.com/magento/magento2/issues/8189



            Still an open issue am afraid :(






            share|improve this answer
























            • Thank you very much, hopefully that will be resolved soon!

              – Richard-Sinnis
              Aug 29 '17 at 13:17











            • Please include the release this bug would have been fixed in, so that people know if this issue no longer applies to their situation.

              – J. M. Becker
              Dec 16 '18 at 19:09
















            3














            It seems to be a known issue with Magento2



            https://github.com/magento/magento2/issues/8189



            Still an open issue am afraid :(






            share|improve this answer
























            • Thank you very much, hopefully that will be resolved soon!

              – Richard-Sinnis
              Aug 29 '17 at 13:17











            • Please include the release this bug would have been fixed in, so that people know if this issue no longer applies to their situation.

              – J. M. Becker
              Dec 16 '18 at 19:09














            3












            3








            3







            It seems to be a known issue with Magento2



            https://github.com/magento/magento2/issues/8189



            Still an open issue am afraid :(






            share|improve this answer













            It seems to be a known issue with Magento2



            https://github.com/magento/magento2/issues/8189



            Still an open issue am afraid :(







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Aug 29 '17 at 10:46









            Atish GoswamiAtish Goswami

            3,27431645




            3,27431645













            • Thank you very much, hopefully that will be resolved soon!

              – Richard-Sinnis
              Aug 29 '17 at 13:17











            • Please include the release this bug would have been fixed in, so that people know if this issue no longer applies to their situation.

              – J. M. Becker
              Dec 16 '18 at 19:09



















            • Thank you very much, hopefully that will be resolved soon!

              – Richard-Sinnis
              Aug 29 '17 at 13:17











            • Please include the release this bug would have been fixed in, so that people know if this issue no longer applies to their situation.

              – J. M. Becker
              Dec 16 '18 at 19:09

















            Thank you very much, hopefully that will be resolved soon!

            – Richard-Sinnis
            Aug 29 '17 at 13:17





            Thank you very much, hopefully that will be resolved soon!

            – Richard-Sinnis
            Aug 29 '17 at 13:17













            Please include the release this bug would have been fixed in, so that people know if this issue no longer applies to their situation.

            – J. M. Becker
            Dec 16 '18 at 19:09





            Please include the release this bug would have been fixed in, so that people know if this issue no longer applies to their situation.

            – J. M. Becker
            Dec 16 '18 at 19:09













            0














            I also Got same text by using SM Market Theme,



            I figure it how to solve the problem(may be help)



            1- enable template hints for frontends



            ex.app/design/frontend/Sm/market/Sm_FilterProducts/templates/default-sidebar.phtml


            2- refresh the page with the error



            3- get the template file path, then remove the unwanted div



            My Code As Below:



             <!--  <div class="message info empty">
            <div>
            <?php /* @escapeNotVerified */
            //echo __('We can't find products matching the selection.')
            ?>
            </div>
            </div>-->





            share|improve this answer




























              0














              I also Got same text by using SM Market Theme,



              I figure it how to solve the problem(may be help)



              1- enable template hints for frontends



              ex.app/design/frontend/Sm/market/Sm_FilterProducts/templates/default-sidebar.phtml


              2- refresh the page with the error



              3- get the template file path, then remove the unwanted div



              My Code As Below:



               <!--  <div class="message info empty">
              <div>
              <?php /* @escapeNotVerified */
              //echo __('We can't find products matching the selection.')
              ?>
              </div>
              </div>-->





              share|improve this answer


























                0












                0








                0







                I also Got same text by using SM Market Theme,



                I figure it how to solve the problem(may be help)



                1- enable template hints for frontends



                ex.app/design/frontend/Sm/market/Sm_FilterProducts/templates/default-sidebar.phtml


                2- refresh the page with the error



                3- get the template file path, then remove the unwanted div



                My Code As Below:



                 <!--  <div class="message info empty">
                <div>
                <?php /* @escapeNotVerified */
                //echo __('We can't find products matching the selection.')
                ?>
                </div>
                </div>-->





                share|improve this answer













                I also Got same text by using SM Market Theme,



                I figure it how to solve the problem(may be help)



                1- enable template hints for frontends



                ex.app/design/frontend/Sm/market/Sm_FilterProducts/templates/default-sidebar.phtml


                2- refresh the page with the error



                3- get the template file path, then remove the unwanted div



                My Code As Below:



                 <!--  <div class="message info empty">
                <div>
                <?php /* @escapeNotVerified */
                //echo __('We can't find products matching the selection.')
                ?>
                </div>
                </div>-->






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 16 at 12:14









                matinictmatinict

                73011029




                73011029






























                    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%2f191010%2fmagento-2-we-cant-find-products-matching-the-selection-page-cache-invalidates%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

                    1300-talet

                    1300-talet

                    Display a custom attribute below product name in the front-end Magento 1.9.3.8