andrewatfornax

Yep, the MaxMind GeoIP plugins let you do that.

Thanks, let us know how things go after you've unlinked old campaigns etc. and let us know if that has improved things...

Does this still happen in later versions? Just wondering if this is still a bug that needs fixing?

I have a feeling that, depending how the direct selection has been configured, the code may well happily ignore anything like if the campaign is active or has limits or not, and deliver the banner(s) that you've said you really want to deliver. Can you provide more details on how you're doing the direct selection please?

Sorry, I forget I know what OI is, but not everyone else. OI = Operation Interval. If you're running just once an hour (and it's configured to 60 minutes, which it will be unless you have been fiddling in the config file), then that's fine. I wonder if that bug is really really fixed? I wrote a lot of the prioritisation code back in the OpenX days, and I would be a lot of fun to be able to completely re-build it all from scratch, and see if it could be made better. Maybe when I win the lottery :-)

Most likely reason I think for something breaking with the upgrade is incorrect permissions on the filesystem, or a corrupted database....?

The only way I think I will ever be able to figure these reports out is if someone who has the problem is willing to give me login access to their server. I simply don't see these PHP warning issues, even with old versions of PHP, because the Revive Adserver code specifically tells PHP to not worry about these. So, there's something in people's setup that prevents this happening - but unfortunately, I have no idea what.

So (I guess) cpanel has some kind of issue with that being the case, and you need to fix it!

Definitely not like that! You do not want to use a JavaScript tag in an email. Most email clients will not allow JavaScript tags to be executed. Look at the specific zone type that exists for emails & newsletters in the documentation, and use that.

Unfortunately, no. The "data_raw_%" tables are a hangover from the really old days, when data was logged in non-aggregate (i.e. raw) format - but the overheads of doing so meant that (for the vast majority of users), the software simply didn't scale. So, we moved to aggregate logging. I believe there may be (external) plugins available to provide some degree of functionality here?

Yes please! Pull requests in GitHub are very much the preferred way for proposed code changes. (Pretty much anything else is guaranteed to be very low on the list!)

Unfortunately, a good diff UI is about the best way.

Can you please post details of your webserver log? We really need to know what pages are being hit over and over to understand more.

No, sorry. See the system requirements: http://www.revive-adserver.com/support/requirements/

Same question about the log files, though, please - what do they say about what the maintenance script is doing?

Yes, there is. Firstly, set up the campaign that you want to have always served as a pair, with the banners for zones 1 & 2. Configure that campaign for companion positioning. Then, set up any other campaigns that you need, with the banners for zones 1 through 5. Don't configure those for companion positioning. That's it! Whenever zone 1 has a banner from the companion campaign selected, then zone 2 will also be the banner from that campaign. Whenever zone 1 has a banner from any other campaign, then zone 2 will be able to be any banner from any other campaign too. Zones 3 - 5 will simply always be a banner from any campaign.

For your "ExternalId" limitation, maybe try "equals", rather than "contains"? Also, try dropping the "Culture" limitation, as it makes no difference (as you use the same one on each banner)?

Why not just have multiple banners, with appropriate delivery limitations set?

Okay. How long has the zone been active for? And are you running the default OI of 60 minutes, or a modified (reduced) OI value?

If you want to set up scheduled maintenance, you need to pass in the correct domain name as a parameter to the script. Please see the documentation: http://documentation.revive-adserver.com/display/DOCS/Running+Maintenance

In general, adding ads is the same no matter what device the user is viewing it on. The documentation at http://documentation.revive-adserver.com/display/DOCS/User+Guide is still under development, but there should be enough there now if you read it through to understand how to add banners and get them displaying.

When you generate the zone invocation tag, those tag types that support it have an option called "Don't show a banner from the same campaign again on the same page". That does exactly what it says it does, and does exactly what you're asking for -- it stops another banner from the same campaign showing up again on the same page.

When you access a page on your webserver from the iPhone you are testing with, have you inspected the useragent details in your webserver log file (you may need to increase the logging level) to see what useragent is actually being passed through to Revive Adserver?

Yes! Revive Adserver can do a number of things with multiple domains: 1. You can have multiple, but completely independent installations running out of one code base (but with different databases); or more commonly (and usefully) 2. You can have one installation running, but deliver the UI and/or banners on different domains.

Sorry - you want to not serve requests when WHAT? increases to some limit?