hmm, I should rephrase that. It appears that those variables two are now
getting picked up in the metadata, as they should. Additionally, in the
application.objectbroker['ruleEventsCalendar'].stWebskins['displayTeaserCalendar']
, I can see two objects, one with nothing in the webskincacheid, and the
other with:
stParam[AEVENTS]:{complex},stParam[BALLOWTRACE]:true,stParam[QEVENTS]:{complex},url.month:06,url.year:2009,which seems to imply that its picking up the caching variables (along with some I did not set), but it is not caching it correctly. This is after resetting the application. I know that the url parameters are getting picked up by the webskin (i have <cfparam name="url.month"> with a default value within the webskin of the 'displayTeaserCalendar', since it's getting dumped with a var="#url#" call. However, if caching happens before the webskin is called, then it wouldn't catch the url values. In either case, I've noticed that the rules I have which output a page reference (<ft:pagination>) are also not getting cached correctly, even though these are explicitly set to cacheByVars using fapi.setCacheByVar etc. I guess all of that is to say I'm now even more confused as to what's going wrong than before. Any further ideas would be great on how to trace this down. Tomek On Sun, May 31, 2009 at 8:55 AM, Tomek Kott <[email protected]> wrote: > the problem is tha it should be cacheByVars, plural vars! > > I'll update the wiki when i get the chance. > > > On Thu, May 28, 2009 at 7:18 PM, Blair McKenzie <[email protected]> wrote: > >> As far as I know that should work. I'll pass the question along to the guy >> who wrote it. >> >> >> On Fri, May 29, 2009 at 2:13 AM, Tomek Kott <[email protected]> wrote: >> >>> So I tried putting >>> >>> <!--- @@cacheStatus: 1 ---> >>> <!--- @@cacheTimeout: 1400 ---> >>> <!--- @@cacheByVar: url.year,url.month ---> >>> >>> and updating the app, but the caching still doesn't work. Do I need >>> >>> <!--- @@cacheStatus: 1 ---> >>> <!--- @@cacheTimeout: 1400 ---> >>> <!--- @@cacheByVar: "url.year","url.month" ---> >>> >>> or something? Or is there another way to add to the cacheByVar scope? >>> >>> Thanks, >>> >>> Tomek >>> >>> On Wed, May 27, 2009 at 7:42 PM, Blair McKenzie <[email protected]>wrote: >>> >>>> You would need to specify url.year, etc. >>>> >>>> The caching stuff can only use variables in a scope (e.g. application, >>>> form). These variables are used to check the cache before the webskin. >>>> There >>>> is no way around that, as the goal is to avoid running the webskin >>>> unnecessarily. >>>> >>>> Blair >>>> >>>> >>>> On Wed, May 27, 2009 at 12:43 PM, Tomek Kott <[email protected]>wrote: >>>> >>>>> Hi All, >>>>> >>>>> I'm a little confused by the cacheByVar implementation. I am trying to >>>>> use it on the displayEventsCalendar rule page, and the two variables that >>>>> I >>>>> want to hash on are the 'month' and 'year' url variables. so I just did >>>>> the >>>>> naive thing >>>>> >>>>> <!--- @@cacheByVar: year,month ---> >>>>> >>>>> That didn't seem to work by putting in the displayEventsCalendar. At >>>>> which level of the caching mechanism do I need to put that code in? Does >>>>> it >>>>> go in that file (which is a rule display page) or does it go in the dmHTML >>>>> page that holds it, or the container, or do I need to do url.year and >>>>> url.month as the variables, for example? >>>>> >>>>> Thanks >>>>> >>>>> Tomek >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry -~----------~----~----~----~------~----~------~--~---
