Wednesday 30 April 2008 2:40:45 pm
Ah, thanks. Now I understand. This does seem a little odd to me though. I appreciate what is trying to be done here (ie cache only those areas of the site that need to be, allowing still for some dynamic interaction) but this removes the possibility of being able to 'cache' the <i>entire</i> site. Plone CMS has had this functionality for about 4 or 5 years and the new kid on the block, here in NZ at least is Silverstripe (www.silverstripe.com) which is having this functionality built into it as I write. As you can see from my use-case above, I really need to be able to 'cache' ('cook') dynamic content into static HTML, CSS and images in order to deploy an entire site remotely. I will try and modify the code to deal with the link issue and of course to grab the images. Otherwise I'll have to use a manual 'scrape' or try out another CMS. The ability to 'cache' was one of the main things that brought me to eZ - but it doesn't seem to work in the same way one might expect it to.
Many thanks for your time. Russ
Russell Michell, Wellington, New Zealand.
We're building! http://www.theruss.com/blog/
I'm on Twitter: http://twitter.com/therussdotcom
Believe nothing, consider everything.
|