Erik Geurts

I would strongly recommend against manually deleting any data. It will result in data inconsistency. Why do you want to delete any data in the first place?

Yes, this should work just fine with Revive Adserver as well.

Using 2 or more iframes on a single page, these iframes execute independently of each other and in parallel. As such, they are not 'aware' of each other, and therefor it is impossible to prevent the same banner from showing up in multiple iframes.

Any plugin correctly installed in the 'old' version is supposed to be migrated to the 'new' version automatically during an upgrade procedure. There is no need for any special preparations. Never manually copy anything from the old to the new folder, this should be taken care of by the upgrade wizard. The upgrade process described at http://www.revive-adserver.com/support/upgrading/ should result in zero 'down time', but it might result in a bit of missing statistics. In order to fully understand what happens when you see problems with plugins during upgrades, we'll need more information from you.

Since the Single Page Call mechanism is a dynamic process, it is unlikely a caching plugin in WordPress would interfere with it.

Have a look at http://www.openxconsultant.com/blog/2011/05/benefits-of-openx-single-page-call-for-maximum-site-speed/

Have a look at: http://www.openxconsultant.com/blog/2011/05/benefits-of-openx-single-page-call-for-maximum-site-speed/

Revive Adserver is designed to select one banner for a zone, every time a request for that zone is made. If there are multiple banners linked to the same zone, it will select one of these banners each time, according to their probabilities.

Have a look at http://www.revive-adserver.com/support/bugs/

Still, this doesn't explain why it used to work with 644 in the past, and not now.

The Delivery_dev folder is only for the developers of the core application.

Community member Ilya Behr at Black River in Toronto, Canada, wrote two extremely detailed online guides related to Conversion tracking using Revive Adserver. The Conversion Tracking tutorial explains how to enable the feature, how to setup and implement a tracker, and how to analyze and interpret the statistics recorded by these trackers. Next, the Debugging Conversion Trackers guide provides detailed instructions on how to check and validate the conversion tracking has been implemented correctly and reliably. Thank you, Ilya, well done!

This might be related to caching at the server level or an stale session. It might help to close all instances of your browser and try again. If that doesn't help, perhaps try restarting Apache.

Please refer to: http://www.revive-adserver.com/faq/using-google-adsense-with-revive-adserver/

We've compiled and published a page of instructions and tips for using Google AdSense tags in Revive Adserver. Please see Using Google AdSense with Revive Adserver on the main website.

This is not correct. It used to be a problem for the AdSense crawler to interpret a page when the ad code was delivered via an iFrame invocation code, but this was fixed by Google many many years ago. It is not an infringement of the AdSense rules to use iFrames for the zones.

When you changed the permissions of your config file in earlier versions, so before you upgraded to Revive Adserver, did you also see that the config file was still being reported as unlocked? If so, I suggest you contact your sysadmin or hosting provider and discuss with them.

We have published a page describing how to make full use of Flash banners within Revive Adserver and giving tips on how to create compatible Flash banners. Please see Using Flash banners with Revive Adserver on the main website.

Please note that Revive Adserver should work perfectly fine with eAccelerator, my company uses that on the large hosting platform we operate and it works miracles!

Revive Adserver, just like its predecessor OpenX Source v2.8, does not offer what you call 'live' statistics, and it never has. We can't restore functionality that never existed in the first place.

Which problem are you referring to?

All plugins listed on that overview are supposed to be enabled.

From what you've described, it appears that the issue may be caused by missing or inactive plugins, from when you first upgraded to v3.0.0. See here: http://www.revive-adserver.com/blog/enabling-revive-adserver-plugins-after-upgrading-to-version-3-0-0/

The audit table just contains an audit trail of what happened elsewhere in the application, there is no need to clean it. It is not used for ad delivery and is therefore invisible to a malware scanner.

The OpenX Market plugin is supposed to be disabled and removed when you upgrade from OpenX v2.8.x to Revive Adserver v3.0.x. I have done dozens of upgrades like this by now, and my fellows in the Revive Adserver team must have done hundreds. It is of course possible you have a specific case where the upgrade process did not work as intended, but it is not very likely.