Saturday 12 June 2010 7:30:32 am
I think for the scenario you describe using a javascript full-page reload, or as Andre suggested meta-tag refresh is by far the simplest solution. There are of course drawbacks, the main one being that when the full page refreshes, it will take some time, and the user will see it. Otoh the way the eZ Publish caching system, templating system and ezflow work will not help you to easily transform an existing ezflow page with rotations and overflows applied into a page where you can request the contents single blocks via ajax calls. You should be able to do that by: - using the layout/set view to set up a different pagelayout for those pages requested via ajax that will produce only the html chunks corresponding to block - use override rules and create specific templates used to render for those html chunks; attach eg. those templates to some dummy objects - inside those templates, use the node_view_gui function to display the blocks that are actually in the homepage The problem with this setup is that to make it work you will need to disable view caching for the templates generating the html chunks, and every time the ajax calls refresh in your users homepage you will be generating many many sql requests in the database...
Principal Consultant International Business
Member of the Community Project Board
|