[Upgrade Openx To Revive - System Do Not Recognize New Version]

@horseguards. Please make sure you follow http://www.revive-adserver.com/support/upgrading/ step by step. That should be it.

[Enabling Geotargeting Settings Doesn't Work]

can I disable that the session cookie? (I know it will affect my performance but I still need it..)

 

There use to be a similar feature, but I can't find it ATM. It looks like it was removed by accident, perhaps when the plugin framework was added.

[Enabling Geotargeting Settings Doesn't Work]

Sorry, what I meant is that the geotargeting plugin caches the information in a session cookie (that doesn't survive a browser restart).

 

If you are testing anon proxies etc, make sure you don't use the same browser for your tests.

[Enabling Geotargeting Settings Doesn't Work]

Please check your session cookies.

[Upgrade Openx To Revive - System Do Not Recognize New Version]

If you get that message, I'm afraid that it means that you didn't properly follow the instructions in the tutorial.

[Serving Ads Over Https Fails]

404 on that URL :\

 

Thanks. I've edited the post and fixed the link.

[404 Errors On Revive Adserver Admin Panel]

The webserver error logs might offer some hints. Maybe a permissions issue?

[Plugin - Custom Delivery File?]

It isn't. You should use the front controller delivery/fc.php for delivery files provided by plugins.

[Settings Key Configuration During Plugin Installation?]

Plugin installation / upgrade has been designed to be run unattended. I'm not really sure it would be wise to add a hook for what you have in mind.

 

What I did with a plugin that requires some action is adding a warning on the left bar to tell the admin user that some additional configuration is required, e.g.

 

 

Feel free to have a look: https://github.com/adserverplugins/apLoader/blob/master/www/admin/plugins/apLoader/apLoader.class.php#L37

[How To Get Single Banner From Zone In Async Code]

I'm sorry, the new async code doesn't support it as direct selection is being deprecated.

[Banner With 100% Probability Doesn't Render]

@martin.krcho if you're using file cache, I would try to rm -f .../var/cache/deliverycache* anyway

[Banner With 100% Probability Doesn't Render]

Zone 48 is in fact returing a blank. Could be permission issues with the cache files?

[Ox_Admin_Redirect Logs User Out...?]

Hi Richard, that's correct. There's nothing wrong with what you are doing and I can confirm it works here, so there must be something wrong with your test environment. I'm afraid some more debug on your end will be necessary.

[>2 Async Tags Causing Multiple Page Loads In Firefox]

I can't replicate with Firefox on your own site, performing the actions you suggested.

[Invocation Code Confusion]

What does the zone probability screen tell you?

[Problem: Delivery Limitations Reports Incorrect]

See: https://github.com/revive-adserver/revive-adserver/issues/549 (not fixed just yet)

[Multiple Zones At The Same Page]

It is safe to post the entire snippet multiple times. The browser will cache it and execute it only once anyway.

[Possible Bug: All Banners Blocked By Cookie Oacblock]

Yes. The error is caused by the fact that the Cookie header is too long. In this case, OXLIA is getting too big: it is a cookie used for conversion tracking. Add that to the other cookies for frequency capping/blocking and you can easily get this overflow situation. Please try to reduce the number of campaigns with capping and/or conversion tracking.

[Asynchronous Js Tag]

Yes, that's pretty unfortunate. We were hoping that this kind of bugs could be identified and reported during the beta period. For now, I've created a bug report: https://github.com/revive-adserver/revive-adserver/issues/529

[Asynchronous Loading]

A page explaining how it works is underway. Unfortunately I haven't had time just yet, but it will be ready soon. As for "data-revive-id", it is generated by hashing the delivery URLs, so it is supposed to be constant.

[Chrome Stops Displaying Banners After 26 Page Loads (Cookie Problem)]

@dudup - about 500 errors, your error log should point you in the right direction.

 

Also heve a look at this: http://www.reviveconsultant.com/articles/single-page-call-advanced-mplementation/

[Issue: Impressions Are Not Logged For Html Banner]

1. I just found {logurl} macro for Revive to log impressions

 

I'd suggest some clever javascript that first logs the impression, then redirects.

[Chrome Stops Displaying Banners After 26 Page Loads (Cookie Problem)]

We're using the default javascript method.

 

Not true. You're using plain remote invocation, which uses just <a href> + <img> tags and cookies to track which banner was clicked and redirect to the proper destination.

 

I'd suggest switching to JS or single page call, or the new async tags (in v3.2.0 -- now in beta).

[Hook Request Procedure?]

Hi Richard,

 

a feature request issue on github, even better a pull request. Of course with all the info on why it is required etc.

 

 

Cheers

[Serving Ads Over Https Fails]

Another installation suffering this problem here.

Using the JS invocation code. Code runs on page and requests add from

http://domain.com/revive/www/delivery/ajs.php?zoneid=2&charset=UTF-8&cb=123123123&charset=UTF-8&loc=http%3A//otherdomain.com/path/page.php

works just fine.

Make the URL https and it claims it can't find an ad to serve. The OX_random string is set just fine, and with 3.1 the beacon is served, but no ad.

Oddly though, if I change the zoneid to another valid zone, it DOES seem to serve under SSL just fine. Is there a setting regarding https delivery I'm not seeing?

 

If you have HTML banners containing http:// urls, then Revive Adserver won't serve them over SSL to avoid browser error messages. Please fix your banners, wait for the delivery cache to expire (or clean it up manually), then retry.