Matt Glover

Team there is bug in MAX_commonConstructDeliveryUrl - as you can see it hard codes the http prefix rather than using the request header value. In my case, this was the cause of a CORS issue meaning we couldn't serve async ads from an insecure website. I hard coded mine to be https but in the bugfix it should be updated to use the X-Forwarded-Proto et al request headers and return the appropriate field. We lost 3 man days over this one!!! but glad to have it sorted. /** * A function to generate the URL for delivery scripts. * * @param string $file The file name of the delivery script. * @return string The URL to the delivery script. */ function MAX_commonConstructDeliveryUrl($file) { $conf = $GLOBALS['_MAX']['CONF']; return 'http://' . $conf['webpath']['delivery'] . '/' . $file; }

thanks for the solve.

Not at all - thanks for the tips and direction!

I think what it being suggested here is that you make a decision about which div to include - perhaps server side. So if you are using PHP you would make a decision about which div to render and only render the one you want to use based on the user device. Alternatively you could do it client side with javascript - make the decision at run time, inline, and append the chosen invocation code. Something like $("#myad").append('<ins blah blah blah'>); The trick would be to do that BEFORE the async call executes and looks for active zones.

Now that makes a whole lot of sense! I love the fact that Revive is accessible for everyone and personally would hate to see that lost. Thank you for the informative response by the way. We're reserving about 2M impressions a week through our instance now, and its growing and my need for reporting on browser types, geolocation etc across multiple, dynamic groupings of advertisers/campaigns/zones is growing with it. We've forked the revive repo and started getting our heads around the codebase. What would you recommend is the simplest way to be able to get access to the client browser info via a plugin if possible? Is there an event subscription model we can hook into? understood - at that scale I understand that some kind of incremental bucket system is needed for browser info and location counts. For now we are still small enough (2M/week) to be able to take a less "normalised" approach. Its a matter of needing near real time info to guage reader engagement across 40 print and digital assets to enable the marketing and product teams to scale revenue and invest in the right places.

Great - is there a hotfix for this in the form of a patch or something else?

What version is your "Invocation Tags Plugin" - see https://matt-sparkeleven.tinytake.com/sf/NTMxMTk3XzI3NzQzMzY If you go into the settings of this module - is asynch enabled? See: https://matt-sparkeleven.tinytake.com/sf/NTMxMTk4XzI3NzQzMzc

Presuming you have the "maintenance" process running automatically, the stats will show up in the "Statistics" tab. See: https://matt-sparkeleven.tinytake.com/sf/NTMxMTk2XzI3NzQzMjU

Erik, I disagree! ;) It sales well, it just doesn't scale easily. I really need to be able to cut statistics across verticals and groups verticals for different purposes and for that reason need to be able to work with the raw data in a data mining environment. I'm trying to get my head around the codebase now to work out whether we can write a plugin to add this feature back in or whether we need to modify the core. The current "whiteboard" plan looks like using a redis array to accumulate then have independent workers (not on the revive front ends) serialising the data into a secondary mysql instance(s). Is there a neat way to hook into the server and click events to capture the referrer info from a plugin.

bump

Hi all, I'm currently looking at implementing Revive but I need raw impressions and click stats which I understand (reading the forums) was originally part of OpenX but has now been removed in favour of the stats bucket system. Is there an easy way to reenable the recording of raw stats that will include things such as browser type and geo information where available. Thanks, Matt