Forums / Developer / How changing will be done ,situation where smart view caching can't be used ,

How changing will be done ,situation where smart view caching can't be used ,

Author Message

Romeo Antony

Sunday 26 December 2010 11:22:42 am

Hi ,

Sorry to post the same thread.

http://share.ez.no/forums/developer/clear-the-view-cache-for-all-the-siblings-of-this-node-object/(language)/eng-GB

--folder(root)

------------------- --folder1

------------------- --folder2

---------------------------------- --folder3

--------------------------------------------------custom_article1

---------------------------------- --folder4

--------------------------------------------------- --article2

I need to clear the cache of any article that resides in folder3 whenever an article is published from folder4 . If here are 100's of objects , it cann0t be mangaged by smart view caching as I understand its working .

(from that thred I understood I couldn't do smart view cache clearing )

So cache block is the best way situation like above ? . Anyone please give some idea

Cache block is the best solution to clear the cache ,

Carlos Revillo

Monday 27 December 2010 4:41:53 am

Could be good to know what is your real goal here.

I mean, articles need to change completely or just some parts (maybe blocks or something) of them?

I see your situation as articles having things in common, like 'latest content added' or things like that... is that the case?

Then you can think in refactoring your pagelayout.tpl and move there the parts that need to change, usign cache-block for that. If you already have your pagelayout build and doesn't want to change it, you can also think in doing a override for pagelayout and only those articles...

But note i'm saying this without knowing your real goal, so probably this couldn't be the best option.