[geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10

[Tom]

Hi Joe,

Yup I have used Marks work as an example and I have seen how instances are
created based on the user, language, theme , etc... I plan to add the topic
ids in this way as well

The difference with the way the story caching is done (when compared to the
other way of using the functions directly ie
CACHE_check_instance($cacheInstance) as with the What's New Block) is that
it caches it directly into the template cache file. This means if template
caching is turned off in the Configuration then the story caching is turned
off as well. I am currently trying to find a way around this which probably
means a few updates to the template class or by using the functions
directly. I have a few ideas yet which I will try out this weekend.

Tom


-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello
Sent: October-17-13 11:00 PM
To: Geeklog Development
Subject: Re: [geeklog-devel] geeklog-devel Digest, Vol 85, Issue 10

> CACHE_check_instance($cacheInstance)

Unfortunately I have completely forgotten the specifics behind how to do the
cache stuff so if you need an example, look at the glFusion code.
Caching of articles was the first use of the instance cache stuff. IIRC
there's an if and if the cache is "fresh" you set the 4-6 variables that
can't be cached and it pulls the article from cache. If the else path is
taken, you build the whole article, setting those 4-6 variables as $nocache
and add the instance to the cache.

I think the devil in the details was naming the instance. You might name it
uniquely per topic or have anonymous versions separate from non-anon
versions. Generating the instance name correctly took Mark a few tries.

_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://eight.pairlist.net/mailman/listinfo/geeklog-devel