andrewatfornax

Hi,
I'm not clear with "we want to default back to AdSense" this statement. What is the role of google adsense in it?

Have you tried Mod Security Commercial Rules (Web Application Firewall) or CloudFlare Web Application Firewall?

Mod Security and CloudFlare are both part of OWASP (www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project) which provide the same set of rules.

Mod Security is free, but the commercial rules I think are a one time fee of $500, while with CloudFlare (www.cloudflare.com/waf) you have to pay $200 every month.

This is probably the best and most affordable way for blocking bots and bad traffic.

Another solution is to get a hardware firewall in front of your server to filter out the bad traffic, but that may be more expensive.

to all blank (error 500 code) pages...I gets those on campaign page, and also on stats, I checked what it can be, maintenance running good, everything seems good. I was out of idea, nothing special in logs...but then, just for fun, I repaired all tables in database and viola - problem is gone.
 
I repaired it using mysql as "repair table ...;"
 
it really helps.

Make sure you have created a MySQL database inside your server. You will then need to assign permission to the database, so MySQL database and user cam connect. Once that is done, input the database info over to Revive and you're all set.

Solved.   In case anyone else needs this:  I needed to append the URL with a session id.  Mine is actually called Sessiontab.  Where the zone is defined in the JS code, I added this to it:     &sessiontab=" + document.querySelector('[name=SESSIONTAB]').value);   So this is what it would look like:       document.write ("?zoneid=6&sessiontab=" + document.querySelector('[name=SESSIONTAB]').value);     On the adserver where I enter the information for the banner, I needed to add a variable to the URL.  It looks like this:       &sessiontab={sessiontab}   I used ampersand, because I already used a ? in the string.

Hi,
Login as Administrator,Check to the installation of "Banner Deliver Logging plugin"  under Plugins tab.

Hi,
Go to Zones, particular Zone, click on Invocation code.
Under the "Tag Settings", enable this option "Don't show a banner from the same campaign again on the same page" by clicking "Yes" option.
Refresh it,use the invocation code that gets generated.

Hi all,
 
I'm trying to develop some plugins for Revive Adserver. As most of you might know, the available documentation is not very much, so every bit that can be found on the web could be helpful.
 
I had some bookmarks to the wiki on developer.openx.org and also the first page of the plugin "Developer Toolbox" points there, but since a few days, the page is not reachable any more.
 
Does anybody know if this is a temporary problem or if they shut down this page?
Will there be an appropriate page like developer.revive-adserver.com or does a page like this already exist?
 
best regards,
Andreas
 

This could have several reasons:
 
Is the campaign and the banner active?
Do you have any Delivery Limitations?
 
Sometimes it takes some time to see changes, because of caching of the banners.

you can select, which invocation-codes are allowed in the settings of the invocation-code-plugin.
 
To check this:
- switch to admin-mode (Working as Administrator)
- Plugins
- search for "Invocation Tags Plugin" and klick on "Details"
- click on "Settings" (link in last row)
 
hope that helps
Andreas

Huh. Ok. Apparently cursing at the adserver restores statistics? Who knew?! 

They're all back. Perhaps I needed to wait a bit after clearing the caches. 

Hi,
 
I am discussing this on another thread, FYI: http://forum.revive-adserver.com/topic/937-issue-with-delivering-the-amount-contracted/

Have you checked if the server meets all technical requirements?
http://www.revive-adserver.com/support/requirements/

That is a good question.
 
I will try to clean-up the database, deleting old advertisers and campaigns, and see if this gets better. Wait for a new contact by the beginning of June.
 
Thanks.

It's displaying now, thanks you

It appears your operation interval is 5 minutes. That's a pretty bad idea and I would suggest to revert back to 1hr.
 
In the tables above one can easily see that the ad was requested to deliver only ~15 imps every 5 minutes. If the zone gets let's say 1000 imps during that 5 minutes, serving twice as much (30) would be a 1.5% error which would be normally considered very good. A more than likely 5% error rate would mean serving 65 imps for that ad in that zone every 5 minutes, four times more than what it was expected to get. And you're ending up with the system trying to turn the banner on and off and misbehaving.
 
Operation Interval aside, the target for the banner might be anyway too small for Revive to accurately hit it on a high traffic zone.

The openXWorkflow and openXMarket plugins are no longer part of Revive Adserver and are supposed to be removed during a properly executed upgrade from OpenX to Revive Adserver.

Please also refer to this topic about the same subject: http://forum.revive-adserver.com/topic/9-asynchronous-loading/

Thank you for the update Andrew

You are great ... worked perfectly ... thank you!!! 

Yes. The backdoor you are talking about was fixed by OpenX Inc itself.

Since I've taken the time to find a solution which works for my website, I decided to pass along my solution.
This works in a jQuery environment, but doesn't depend on jQuery.
 
Using this Javascript library (available under the terms of the MIT License):
https://github.com/iamnoah/writeCapture/tree/writeCapture2
 
First, load the library, so you can use the function:
<script src="/path/to/element.write.js"></script> <script src="/path/to/writeCapture2.js"></script> Then simply rewrite your invocation code like so
<div id="AdPlaceholder"> <!-- ad will go here --> </div> <script> /* this function wrapper keeps global memory space clear of random variables */ (function(){       var oxSrc = (document.location.protocol === "https:" ? "https:" : "http:")          + "//example.com/ReviveAdserver/www/delivery/ajs.php"          + "?zoneid=123&block=1&blockcampaign=1&cb=" + Math.floor(Math.random()*99999999999)          + "&charset=UTF-8&loc=" + encodeURIComponent(window.location)          + (document.MAX_used !== "," ? ("&exclude=" + document.MAX_used) : "")          + (document.referrer ? ("&referer=" + encodeURIComponent(document.referrer)) : "")          + (document.context ? ("&context=" + encodeURIComponent(document.context)) : "")          + (document.mmm_fo ? "&mmm_fo=1" : "");       writeCapture.write(          document.getElementById("AdPlaceholder"),          "<scr" + "ipt src='" + oxSrc + "'></scr" + "ipt>"       ); })(); </script> If you don't need the ability to prevent displaying the same banner / campaign / advertiser on a single page, then you are done.
 
If your like me, and need campaign and advertiser blocking (to prevent duplicates), you'll have to do continue with the next step.
 
When the javascript runs the string stored in oxSrc has the current value of document.context, however subsequent ads need the revised value of document.context, to prevent duplicate ads.
 
The solution is to wrap the string creation into the javascript which is excuted asynchronously, so that the revised value of document.context is used, like so
<div id="AdPlaceholder"> <!-- ad will go here --> </div> <script> /* this function wrapper keeps global memory space clear of random variables */ (function(){ writeCapture.write( document.getElementById("AdPlaceholder"),          '<scr' + 'ipt>' +             'var oxSrc = (document.location.protocol === "https:" ? "https:" : "http:")' +             '+ "//example.com/ReviveAdserver/www/delivery/ajs.php"' +             '+ "?zoneid=123&block=1&blockcampaign=1&cb=" + Math.floor(Math.random()*99999999999)' +             '+ "&charset=UTF-8&loc=" + encodeURIComponent(window.location)' +             '+ (document.MAX_used !== "," ? ("&exclude=" + document.MAX_used) : "")' +             '+ (document.referrer ? ("&referer=" + encodeURIComponent(document.referrer)) : "")' +             '+ (document.context ? ("&context=" + encodeURIComponent(document.context)) : "")' +             '+ (document.mmm_fo ? "&mmm_fo=1" : "");' +             'document.write("<scr" +  "ipt src=\'" + oxSrc + "\'></scr" + "ipt>");' +          '</scr' + 'ipt>'       ); })(); </script> Yes, this is quite ugly code, and you'll have to be careful when editing it, as it's javascript which writes javascript.
 
I hope this is able to help people, until Revive Adserver offers a direct solution to display ads asynchronously.

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. 

The Revive Adserver team use Github to manage the project and develop the software. If you’re new to Github, and want to learn a bit more about how it all works, just head over to the new Github Guides. There are interactive modules to learn about Understanding the Github workflow, how to manage issues on Github, and how to contribute to a Github project by forking it, and much more.
Once you know a bit more about how Github works, you might appreciate browsing about the Revive Adserver project, for example by having a look at our most recent commits, the current list of open issues, and the list of contributors to the project. Hopefully we’ve inspired you to join the project on Github, and perhaps find your name on the contributor list in the future.


View the full article

I answer to myself in this topic after getting an answer to this question by Eliza through another topic:
 
"You can clear the cache and check it again or go to Configuration --> Banner Delivery Settings --> Banner Delivery Cache Settings, and reduce the time limit."
 
I hope this may also help others ;-)