magento 1.9.x / turpentine 0.7.10 / Varnish 4.x - block inside cms page not flushing












0















I am trying to flush a cms block I have added to a page as seen in the picture below.





Now I have put the code on the last screen inside the cms page under the "design" tab. and in the turpentine_esi.xml. None of them seem to be working.



I am flushing with a custom flush event "car_select" that is working since it flushes other references perfectly.
What am I missing, or what am I doing wrong?
If so sorry and please provide a link.










share|improve this question

























  • Disable varnish cache and check or do you want that cms block display without caching right?

    – Nits
    Feb 9 '17 at 10:53













  • do you see this block name in debug log?

    – MagenX
    Feb 9 '17 at 12:21











  • @Nits the block/page is cached right. But when a car is selected the block should be refreshed. But it doesn't. So it doesn't whole punch.

    – Bram Hammer
    Feb 9 '17 at 12:28











  • @MagenX will check right away, good one !

    – Bram Hammer
    Feb 9 '17 at 12:28











  • @BramHammer you should set that block or call that block via xml layout and after that whole punch that block via block name. I was faced this kind of issue.

    – Nits
    Feb 9 '17 at 12:31
















0















I am trying to flush a cms block I have added to a page as seen in the picture below.





Now I have put the code on the last screen inside the cms page under the "design" tab. and in the turpentine_esi.xml. None of them seem to be working.



I am flushing with a custom flush event "car_select" that is working since it flushes other references perfectly.
What am I missing, or what am I doing wrong?
If so sorry and please provide a link.










share|improve this question

























  • Disable varnish cache and check or do you want that cms block display without caching right?

    – Nits
    Feb 9 '17 at 10:53













  • do you see this block name in debug log?

    – MagenX
    Feb 9 '17 at 12:21











  • @Nits the block/page is cached right. But when a car is selected the block should be refreshed. But it doesn't. So it doesn't whole punch.

    – Bram Hammer
    Feb 9 '17 at 12:28











  • @MagenX will check right away, good one !

    – Bram Hammer
    Feb 9 '17 at 12:28











  • @BramHammer you should set that block or call that block via xml layout and after that whole punch that block via block name. I was faced this kind of issue.

    – Nits
    Feb 9 '17 at 12:31














0












0








0








I am trying to flush a cms block I have added to a page as seen in the picture below.





Now I have put the code on the last screen inside the cms page under the "design" tab. and in the turpentine_esi.xml. None of them seem to be working.



I am flushing with a custom flush event "car_select" that is working since it flushes other references perfectly.
What am I missing, or what am I doing wrong?
If so sorry and please provide a link.










share|improve this question
















I am trying to flush a cms block I have added to a page as seen in the picture below.





Now I have put the code on the last screen inside the cms page under the "design" tab. and in the turpentine_esi.xml. None of them seem to be working.



I am flushing with a custom flush event "car_select" that is working since it flushes other references perfectly.
What am I missing, or what am I doing wrong?
If so sorry and please provide a link.







magento-1.9 php varnish turpentine






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 16 mins ago









Teja Bhagavan Kollepara

2,94841847




2,94841847










asked Feb 9 '17 at 10:36









Bram HammerBram Hammer

4911




4911













  • Disable varnish cache and check or do you want that cms block display without caching right?

    – Nits
    Feb 9 '17 at 10:53













  • do you see this block name in debug log?

    – MagenX
    Feb 9 '17 at 12:21











  • @Nits the block/page is cached right. But when a car is selected the block should be refreshed. But it doesn't. So it doesn't whole punch.

    – Bram Hammer
    Feb 9 '17 at 12:28











  • @MagenX will check right away, good one !

    – Bram Hammer
    Feb 9 '17 at 12:28











  • @BramHammer you should set that block or call that block via xml layout and after that whole punch that block via block name. I was faced this kind of issue.

    – Nits
    Feb 9 '17 at 12:31



















  • Disable varnish cache and check or do you want that cms block display without caching right?

    – Nits
    Feb 9 '17 at 10:53













  • do you see this block name in debug log?

    – MagenX
    Feb 9 '17 at 12:21











  • @Nits the block/page is cached right. But when a car is selected the block should be refreshed. But it doesn't. So it doesn't whole punch.

    – Bram Hammer
    Feb 9 '17 at 12:28











  • @MagenX will check right away, good one !

    – Bram Hammer
    Feb 9 '17 at 12:28











  • @BramHammer you should set that block or call that block via xml layout and after that whole punch that block via block name. I was faced this kind of issue.

    – Nits
    Feb 9 '17 at 12:31

















Disable varnish cache and check or do you want that cms block display without caching right?

– Nits
Feb 9 '17 at 10:53







Disable varnish cache and check or do you want that cms block display without caching right?

– Nits
Feb 9 '17 at 10:53















do you see this block name in debug log?

– MagenX
Feb 9 '17 at 12:21





do you see this block name in debug log?

– MagenX
Feb 9 '17 at 12:21













@Nits the block/page is cached right. But when a car is selected the block should be refreshed. But it doesn't. So it doesn't whole punch.

– Bram Hammer
Feb 9 '17 at 12:28





@Nits the block/page is cached right. But when a car is selected the block should be refreshed. But it doesn't. So it doesn't whole punch.

– Bram Hammer
Feb 9 '17 at 12:28













@MagenX will check right away, good one !

– Bram Hammer
Feb 9 '17 at 12:28





@MagenX will check right away, good one !

– Bram Hammer
Feb 9 '17 at 12:28













@BramHammer you should set that block or call that block via xml layout and after that whole punch that block via block name. I was faced this kind of issue.

– Nits
Feb 9 '17 at 12:31





@BramHammer you should set that block or call that block via xml layout and after that whole punch that block via block name. I was faced this kind of issue.

– Nits
Feb 9 '17 at 12:31










2 Answers
2






active

oldest

votes


















1














There is no way to invalidate the cache inside a cms page.
So cache entire cms block or don't cache it at all..






share|improve this answer































    0














    Please add below code in your Page.xml or varnish layout file.



    <cms_index_index>
    <reference name="carfitment">
    <action method="setEsiOptions">
    <params>
    <access>private</access>
    <scope>page</scope>
    <ttl>0</ttl>
    </params>
    </action>
    </reference>
    </cms_index_index>


    Add below code in cms block design and other code from it



    <reference name="content">
    <block type="core/template" name="carfitment" as="carfitment" template="showoff/fitment/index.phtml" />
    </reference>


    Save cms page and try to refresh varnish cache.



    I Hope it will help you.






    share|improve this answer
























    • Sadly enough it doesn't work :( It does show up on the turpentine.log.

      – Bram Hammer
      Feb 9 '17 at 14:21











    • Hmm okey, now i know why it showed up on the log. There was another block with the same name. I changed it to a unique name and now i get the error " No block node found with @name="carfitment_home"". So it doesn't see a block inside a cms page?

      – Bram Hammer
      Feb 13 '17 at 9:43











    • Yes, Now your issue resolved?

      – Nits
      Feb 15 '17 at 4:49











    • in short, no. There is no way to invalidate the cache inside a cms page. So will have to find some thing else for it.

      – Bram Hammer
      Feb 15 '17 at 8:22











    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%2f158976%2fmagento-1-9-x-turpentine-0-7-10-varnish-4-x-block-inside-cms-page-not-flus%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









    1














    There is no way to invalidate the cache inside a cms page.
    So cache entire cms block or don't cache it at all..






    share|improve this answer




























      1














      There is no way to invalidate the cache inside a cms page.
      So cache entire cms block or don't cache it at all..






      share|improve this answer


























        1












        1








        1







        There is no way to invalidate the cache inside a cms page.
        So cache entire cms block or don't cache it at all..






        share|improve this answer













        There is no way to invalidate the cache inside a cms page.
        So cache entire cms block or don't cache it at all..







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jul 19 '17 at 8:26









        Bram HammerBram Hammer

        4911




        4911

























            0














            Please add below code in your Page.xml or varnish layout file.



            <cms_index_index>
            <reference name="carfitment">
            <action method="setEsiOptions">
            <params>
            <access>private</access>
            <scope>page</scope>
            <ttl>0</ttl>
            </params>
            </action>
            </reference>
            </cms_index_index>


            Add below code in cms block design and other code from it



            <reference name="content">
            <block type="core/template" name="carfitment" as="carfitment" template="showoff/fitment/index.phtml" />
            </reference>


            Save cms page and try to refresh varnish cache.



            I Hope it will help you.






            share|improve this answer
























            • Sadly enough it doesn't work :( It does show up on the turpentine.log.

              – Bram Hammer
              Feb 9 '17 at 14:21











            • Hmm okey, now i know why it showed up on the log. There was another block with the same name. I changed it to a unique name and now i get the error " No block node found with @name="carfitment_home"". So it doesn't see a block inside a cms page?

              – Bram Hammer
              Feb 13 '17 at 9:43











            • Yes, Now your issue resolved?

              – Nits
              Feb 15 '17 at 4:49











            • in short, no. There is no way to invalidate the cache inside a cms page. So will have to find some thing else for it.

              – Bram Hammer
              Feb 15 '17 at 8:22
















            0














            Please add below code in your Page.xml or varnish layout file.



            <cms_index_index>
            <reference name="carfitment">
            <action method="setEsiOptions">
            <params>
            <access>private</access>
            <scope>page</scope>
            <ttl>0</ttl>
            </params>
            </action>
            </reference>
            </cms_index_index>


            Add below code in cms block design and other code from it



            <reference name="content">
            <block type="core/template" name="carfitment" as="carfitment" template="showoff/fitment/index.phtml" />
            </reference>


            Save cms page and try to refresh varnish cache.



            I Hope it will help you.






            share|improve this answer
























            • Sadly enough it doesn't work :( It does show up on the turpentine.log.

              – Bram Hammer
              Feb 9 '17 at 14:21











            • Hmm okey, now i know why it showed up on the log. There was another block with the same name. I changed it to a unique name and now i get the error " No block node found with @name="carfitment_home"". So it doesn't see a block inside a cms page?

              – Bram Hammer
              Feb 13 '17 at 9:43











            • Yes, Now your issue resolved?

              – Nits
              Feb 15 '17 at 4:49











            • in short, no. There is no way to invalidate the cache inside a cms page. So will have to find some thing else for it.

              – Bram Hammer
              Feb 15 '17 at 8:22














            0












            0








            0







            Please add below code in your Page.xml or varnish layout file.



            <cms_index_index>
            <reference name="carfitment">
            <action method="setEsiOptions">
            <params>
            <access>private</access>
            <scope>page</scope>
            <ttl>0</ttl>
            </params>
            </action>
            </reference>
            </cms_index_index>


            Add below code in cms block design and other code from it



            <reference name="content">
            <block type="core/template" name="carfitment" as="carfitment" template="showoff/fitment/index.phtml" />
            </reference>


            Save cms page and try to refresh varnish cache.



            I Hope it will help you.






            share|improve this answer













            Please add below code in your Page.xml or varnish layout file.



            <cms_index_index>
            <reference name="carfitment">
            <action method="setEsiOptions">
            <params>
            <access>private</access>
            <scope>page</scope>
            <ttl>0</ttl>
            </params>
            </action>
            </reference>
            </cms_index_index>


            Add below code in cms block design and other code from it



            <reference name="content">
            <block type="core/template" name="carfitment" as="carfitment" template="showoff/fitment/index.phtml" />
            </reference>


            Save cms page and try to refresh varnish cache.



            I Hope it will help you.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Feb 9 '17 at 13:46









            NitsNits

            1,248314




            1,248314













            • Sadly enough it doesn't work :( It does show up on the turpentine.log.

              – Bram Hammer
              Feb 9 '17 at 14:21











            • Hmm okey, now i know why it showed up on the log. There was another block with the same name. I changed it to a unique name and now i get the error " No block node found with @name="carfitment_home"". So it doesn't see a block inside a cms page?

              – Bram Hammer
              Feb 13 '17 at 9:43











            • Yes, Now your issue resolved?

              – Nits
              Feb 15 '17 at 4:49











            • in short, no. There is no way to invalidate the cache inside a cms page. So will have to find some thing else for it.

              – Bram Hammer
              Feb 15 '17 at 8:22



















            • Sadly enough it doesn't work :( It does show up on the turpentine.log.

              – Bram Hammer
              Feb 9 '17 at 14:21











            • Hmm okey, now i know why it showed up on the log. There was another block with the same name. I changed it to a unique name and now i get the error " No block node found with @name="carfitment_home"". So it doesn't see a block inside a cms page?

              – Bram Hammer
              Feb 13 '17 at 9:43











            • Yes, Now your issue resolved?

              – Nits
              Feb 15 '17 at 4:49











            • in short, no. There is no way to invalidate the cache inside a cms page. So will have to find some thing else for it.

              – Bram Hammer
              Feb 15 '17 at 8:22

















            Sadly enough it doesn't work :( It does show up on the turpentine.log.

            – Bram Hammer
            Feb 9 '17 at 14:21





            Sadly enough it doesn't work :( It does show up on the turpentine.log.

            – Bram Hammer
            Feb 9 '17 at 14:21













            Hmm okey, now i know why it showed up on the log. There was another block with the same name. I changed it to a unique name and now i get the error " No block node found with @name="carfitment_home"". So it doesn't see a block inside a cms page?

            – Bram Hammer
            Feb 13 '17 at 9:43





            Hmm okey, now i know why it showed up on the log. There was another block with the same name. I changed it to a unique name and now i get the error " No block node found with @name="carfitment_home"". So it doesn't see a block inside a cms page?

            – Bram Hammer
            Feb 13 '17 at 9:43













            Yes, Now your issue resolved?

            – Nits
            Feb 15 '17 at 4:49





            Yes, Now your issue resolved?

            – Nits
            Feb 15 '17 at 4:49













            in short, no. There is no way to invalidate the cache inside a cms page. So will have to find some thing else for it.

            – Bram Hammer
            Feb 15 '17 at 8:22





            in short, no. There is no way to invalidate the cache inside a cms page. So will have to find some thing else for it.

            – Bram Hammer
            Feb 15 '17 at 8:22


















            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%2f158976%2fmagento-1-9-x-turpentine-0-7-10-varnish-4-x-block-inside-cms-page-not-flus%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

            Polycentropodidae

            Magento 2 Error message: Invalid state change requested

            Paulmy