We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31621
    • 23 Posts
    Hi,

    I use the following snippet calls which appear to be caching even thought the call indicates the snippet should not be cached. Are there any settings that I need to change at the System Level to overcome this issue?

    Get Page call using getResources:
    [[!getPage:default=`Currently there are no articles to display.  They will be up soon.`? &elementClass=`modSnippet` &element=`getResources` &parents=`4` &limit=`4` &tpl=`recentPostsOnHome` &showHidden=`true`]]


    Get Page call using Rowbaot:
    [[!getPage:default=`There are no upcoming events.`?&element=`Rowboat`&table=`dcvsborg_eventscalendar`&sortBy=`startdate`&tpl=`eventsOnHome`&limit=`5`]]


    I want the snippets to check data at each call.
      • 31621
      • 23 Posts
      There is a new issue here. Somehow I seem to have overcome the caching issue to refresh data. However, both the above getPage calls are on the same page.

      What is happening now is, that the second getPage call returns the same data as the first call. In this case, getPage using Rowboat is being called first and the second getPage call using getResouces returns the exact same response. Is there any clash with getPage calling two different sets of resources on the same page?
        • 31621
        • 23 Posts
        I updated my call of getPage with Rowboat with property &cache=`0` and it resolved the issue.