Erik Geurts

Thanks for letting us know, Roy. The link has just been fixed.

Out of the box, Revive Adserver v3.x only supports the VAST1 specifications, and it does not have support for creating pre-roll ads that are essentially using VAST2 tags from third parties.
 
I would like to suggest having a look at the Advanced Video Ads plugin that you can find here:
http://www.adserverplugins.com/advanced-video-ads-plugin-for-revive-adserver/
 
This plugin will enable you to traffic a third party VAST2 tag (we call this a Network Video Ad) as a banner, and then to serve that into any VAST2 compliant video player.

Full disclosure: this product has been developed and is being sold by my company.

Revive Adserver (like its predecessor OpenX Source) comes bundled with a plugin that enables it to deliver video ads based on the VAST standard. This VAST standard has since been replaced by the VAST2 and recently even the VAST2 specs. VAST is short for Video Ad Serving Template, it's a set of specifications issued by the IAB (Interactive Advertising Bureau), an industry standards body.
 
The site mentioned by leroy_hack (who comes up with those odd names?) is a project started in 2009 by my partner Matteo Beccati and myself. We develop free and paid plugins, and one of them is called VidiX. It bumps up the VAST capabilities of OpenX Source and Revive Adserver to the VAST2 specifications. Please be aware that it is not a free plugin.

Due to the fact, that on may 25th the GDPR comes into effect, is there anything in the pipe to make Revive complying with the EU-regulation? Actual, Revive processes a whole of bunch of personal data and and the use of it will be penalized in the end through fines. I am wondering that there is not one official statement about the whole GDPR-thing, as this needs to be clearified by Eric ASAP. Else we all have to shut down our Revive-Installations or we have to face drastic fines for using it beyond may 25th.
20 days to go, plus the rest of today.

It may be that you ran into an issue that was found in the upgrade process in v4.1.0 and that was fixed in v4.1.1. Please try if using the most recent version fixes this for you. See https://www.revive-adserver.com/download/ and https://www.revive-adserver.com/blog/revive-adserver-v4-1-1-released-bug-fixes/

I think you going to need plugins like these
http://www.reviveadservermod.com

The API built into Revive Adserver has nothing to do with the actual ad delivery, it's just for the management of your inventory and for reviewing statistics.

Please don't post the same question twice.

Since this is a third party plugin, I suggest you contact the vendor for support on their product.

Please do not double post the same question.

This is a known issue in v3.1.0 which has been fixed in v3.2.0.

In case of a 500 Internal Server Error, there should be more detailed information in your Apache error log. Your hosting provider or system administrator should be able to look up this information and fix the cause.

Please follow the process described on the page at http://www.revive-adserver.com/support/upgrading/ . Upgrading and Updating is the same.
 
Do not simply copy the new files over the old files, it will result in a broken system.

An advertiser user can view the statistics of their own campaign, but they can't make any changes.

It is part of the distributed code, see here:
https://github.com/revive-adserver/revive-adserver/tree/master/www/admin/assets/js
 
Have you checked if that file is actually there on your server?

You should not make any changes to that file. Instead, make sure you set your time zone settings correctly in the configuration of your server.

All you have to do is use mailto: syntax. So instead http://www.example.com to link to a web page, you can use mailto:[email protected] to link to an e-mail address.

see https://www.revive-adserver.com/faq/geotargeting-with-revive-adserver/

Have you checked https://www.revive-adserver.com/support/requirements/ and https://www.revive-adserver.com/support/installation/ ?

Seems pretty obvious to me. You have created a database beforehand, but somehow the installer doesn't see that and tries to create another (and fails because the user doesn't have permissions to create databases). Check if your user/password and database match.

Yes, Hogiro is right. Here is an article describing exactly how to achieve this:
http://www.reviveconsultant.com/articles/how-to-test-an-ad-on-the-site-without-visitors-seeing-it/

I didn't say that. Those might actually be the active tables of your ad server.
If you started years ago with OpenX Source (prefix ox_) and over time upgraded to Revive Adserver, the table names will still have ox_ as their prefix.
What you can delete are the ox_z_ tables and the rv_z_ tables (if any of those exist).

See https://www.revive-adserver.com/blog/translations-for-revive-adserver/

Perhaps start reading about your new software here: http://documentation.revive-adserver.com/display/DOCS/User+Guide

Did you create a website and a zone yet?