Looking at the way other widgets are getting cached, I think you can implement the same on this one, I've tried to do it myself but didn't have much time to get it all working
from what I have figured, all you need to do is get the widget id, generate the hash key, store the output using the widget id as an index/key, define time to live (ttl), write the whole thing into the cache using "vB_cache" thing, and the rest will be handled by the CMS, I know that because I stored the wrong info into the cache, set 5 as ttl and the widget showed up the first time I loaded the page, the next time it only showed the wrong data I cached
|