'ello! Our current situation is that logic related to ads is handled directly in the templates instead of defined in views.xml. This logic consists of several parts:
* How many ads to display * Different ad sources / search commands * Different positions * Different offset's depending on ads shown at an earlier stage (e.g. "if we've shown ads 1-3 from source1 in template1 then show ads 4-5 in template2") * Source precedence. (e.g. "if we have ads from source1, show those. If not, show ads from source2, ...) As far as I know there's no (good) way of moving this kind of logic into views.xml. A similar approach as for enrichments would be nice, where one can define positions for enrichments, and have EnrichmentDirective figure out if a given enrichment should be placed at a given position. -- Magne _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
