Use case:
Said site has upwards of 60 zones that are used all over the site, on various pages. On any given page, at most 11 zones load. If we use the current logic, all 60 zones will be passed to OpenX, and if there are potential matches for all of those zones, this adds significant wasted bandwidth.

I suggest we create a hook_openx_filter_zones to run before zones are defined in the JS array that is referenced by OpenX. This way, other modules can refine the list of zones. Would be useful to develop an openx_context module to implement this hook when ad zones are placed via context.

Anyway, at the very least, would make sense to create this hook so other modules can add logic to this process.

Will toss up a patch tomorrow for review/discussion.

Comments

istryker’s picture

istryker commented

I tried to add a openx zone block to context and it didn't work. I'm going to create a separate issue for this

introfini’s picture

introfini commented

There's another problem with this implementation. Because all zones are loaded the Companion positioning option in the campaigns doesn't work if you don't have banners for all the zones defined.

When OpenX delivers one banner from a companion campaign, then all of the other zones on the page must have banners from the companion campaign.

from http://www.openxtips.com/2009/09/tip-29-understand-companion-positioning/

wuinfo - bill wu’s picture

wuinfo - bill wu commented
Issue summary: View changes
Status: Active » Fixed

This is done. Duplicated with #358775

wuinfo - bill wu’s picture

wuinfo - bill wu commented
Status: Fixed » Needs work

This is only done on 7.x version. Not on 6.x version.