You are not logged in.
Version 0.2.8 download link / homepage
Caching all inside <txp:aks_cache id="unique block id"> Any content with TxP tags </txp:aks_cache>
Good practice:
cloud tagsmain page or cache some ‘slow’ pages with many TXP tags.Bad practice:
body every page
To freeze random content
Docs and Successful story
Last edited by makss (2012-01-23 21:52:30)
aks_cron : Cron inside Textpattern | aks_article : extended article_custom tag
aks_cache : cache for TxP | aks_meta | aks_header : Compress your pages on the fly
Offline
New version aks_cache 0.2.1
Changes:
Last edited by makss (2010-04-19 11:40:07)
aks_cron : Cron inside Textpattern | aks_article : extended article_custom tag
aks_cache : cache for TxP | aks_meta | aks_header : Compress your pages on the fly
Offline
Just tried this on my “Most Popular” and a “Top Referrers” list on my website and it seems to work like a charm! This + aks_header has made my website faster than ever so… thanks! :D
Offline
I use actually zem_cache and your new plugin seems to be more comfortable to use, but is it possible to distinguish between “global” cache and cache per page?
To clearify: zem_cache had a ‘ctx’ and a ‘id’ parameter
id – Use this if you’re using multiple zem_cache tags per page. Each tag should have a different id. It doesn’t matter what the id is set to – a number is fine – as long as each one is different.
ctx – Use this to cache a single copy of something globally across all pages, rather than once per page. For example, <txp:zem_cache ctx=“recent1”><txp:recent_articles /></txp:zem_cache>
thanks
Offline
whocarez wrote:
I use actually zem_cache and your new plugin seems to be more comfortable to use, but is it possible to distinguish between “global” cache and cache per page?
To clearify: zem_cache had a ‘ctx’ and a ‘id’ parameter
aks_cache use one parameter id for “global” or cache per page.
Sample cache two blocks in one page per section:
<txp:aks_cache id='<txp:section />_block1'> Content block1. </txp:aks_cache> Some... <txp:aks_cache id='<txp:section />_block2'> Content block2. </txp:aks_cache>
aks_cron : Cron inside Textpattern | aks_article : extended article_custom tag
aks_cache : cache for TxP | aks_meta | aks_header : Compress your pages on the fly
Offline
New version aks_cache 0.2.3
Changes:
Last edited by makss (2010-04-19 11:10:55)
aks_cron : Cron inside Textpattern | aks_article : extended article_custom tag
aks_cache : cache for TxP | aks_meta | aks_header : Compress your pages on the fly
Offline
aks_cron : Cron inside Textpattern | aks_article : extended article_custom tag
aks_cache : cache for TxP | aks_meta | aks_header : Compress your pages on the fly
Offline
I tested aks_cache on my site and discovered, that it is only partly usable for me. Maybe I use the parameters not in the right way.
For example: I used zem_cache to cache “keywords” and “related articles” and also for “meta descriptions”. They are different for every article.
When I put aks_cache with id=“related” in the code, then there is only one cache for “related” articles and it shows these “related articles” under every article which is showed up, so it is not the intentioned use. So, if I used it in the right way, the aks_cache plugin is yet only for global caches usable.
Offline
Although I’ve never used the plugin (I’m planning to use it on a current project), you could try something like this:
id='related-<txp:article_id />'.
This way, you will have one cache for each article.
Please, tell us if that works. Thanks :)
Offline