move the cache block to before the {let test=fetch... this will create a php cache of the results of the database calls - rather speeds things up :)
also, try this type of cache-block instruction. instead of caching just a single variation of your page it will work if you have dynamic pages that depend on changes between the node.
thanks for your help. I now understand what you were saying about wanting to use a different kind of caching for dynamic content- here you mentioned this call:
You should replace 'stories' with your own variables when you use the cache-block. Remember, this is an id so its not a good idea to use the same id more than once otherwise the id may index the same cached file...
Dont replace the $DesignKeys as that is an ez variable used when cache is on.
However, saying that, the particular example i gave works well since its allows your variable to be indexed. For example, if you have dynamic content for each node it may be seen as {stories, 1}, {stories, 2}, etc, and there will be a cached page for each.
One upshot of this is that more disk space will be used for cache (for each node) but you get better performance.
We are still experimenting with this so hopefully will learn the ins and outs with time :)
