Erik Geurts

Hi Richard, Thanks for your many reports about spam posts on the forums. I think you underestimate the issue. We spend a lot of time removing spam, the few bits you still see are the unfortunate cases where we're not fast enough. Ever since the forum was upgraded to a new version of the Invision Powerboard software, the spam fighting features in it have turned out to be just miserable. We've complained with the vendor but they are unwilling or unable to help. Any suggestions from the community to help make IPB more spam-proof would be highly appreciated.

Revive Adserver is definitely compatible with PHP7, this has been tested thoroughly. This item was addressed on a Github issue: https://github.com/revive-adserver/revive-adserver/issues/652 and the Requirements page at https://www.revive-adserver.com/support/requirements/ where it says:

Looks like you're installation has been hacked. See http://www.openxconsultant.com/blog/2011/10/what-to-do-when-you-suspect-your-openx-system-has-been-hacked/

You could have a look at this commercial plugin: http://www.adserverplugins.com/in-banner-video-ads-plugin-for-revive-adserver/ Full disclosure, this plugin is developed and sold by my company.

Hi there, Please start by having a look at this blog post: http://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/ Full disclosure, the paid plugin mentioned and linked in that blog post is a product of my company.

Installation instructions can be found here: http://www.revive-adserver.com/support/installation/

This sounds like a stale browser session. Have you tried a different browser? Or have you tried clearing the cache?

I assume you mean debug.log. Yes, you can delete it, it will just be created again automatically.

During an upgrade, when the upgrade wizard makes a change to one of the tables, it retains a backup of the original table. it saves that table with a name like rv_z_xxx which is what you've found. Nothing to worry about. The rv_data_bkt_* tables are not new, this has existed since version 2.6 of Revive Adserver's predecessor called OpenX source (and other names). They are use to collect raw data (we refer to it as bucket data, hence bkt) during ad delivery. Also nothing to worry about. Have you perhaps upgraded from a very old version (pre 2.6) straight to Revive Adserver?

We have a hosting platform that's capable of displaying billions of impressions per month. The architecture of the platform, albeit in a slightly simplified drawing, can be found here: http://www.reviveservers.com/revive-adserver-hosting/revive-adserver-hosting-platform-and-technology/ It's virtually impossible to describe in a few sentences what we've done to achieve this. I would not recommend storing banner images in the database, that doesn't scale very well. Also, we have a plugin (not free) that does the caching and logging using Redis (in memory) instead of in the database, and this is one of the key factors to achieve huge volumes at reasonable hardware costs.

See https://github.com/revive-adserver/revive-adserver/issues/597

What you're referring to, is perhaps an 'export & import feature'. This doesn't exist however.

Have you checked if the new Flash banners meet the requirements? See: http://www.revive-adserver.com/faq/using-flash-with-revive-adserver/

In many cases, what you call "hacked", turned out to be a case where someone managed to get their hands on the password of an administrator user. I've seen cases where they then created an extra admin user and have come back months or even years later to compromise the system. Have you checked the users table to look for anything unusual there?

Revive Adserver requires 'all privileges' during operation and during upgrades, for example to be able to create temporary or new tables. I recommend contacting your provider and recommending that they fix that one-click installer they offer.

There is no technical limit in the software for the number of targeting channels you can create.

Please have a look at http://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/

Essentially, you are considering to start a hosting business. Very good! We've been doing that for years for hundreds of customers. You should be prepared to work 24/7 from day 1. My company has developed an application called "Ad Server Hosting Dashboard", it does several things, including retrieving and displaying the relevant statistics of all the ad server instances we host for our customers. By relevant, I mean the statistics needed for invoicing. We don't do that in real time, that is silly in my opinion. Once a day slightly after midnight is sufficient. In your case, I don't see how it would be helpful to attempt blocking things if a customer goes over their monthly maximum. Think about it, you might consider them to be over their max, but the site doesn't know that and will continue to send requests to the ad server. Instead, this would be the perfect opportunity to sell them a larger plan. But the easiest model is to just charge customers for the actual usage after the end of the month.

What do you mean by: I am not able? Can you please give a specific example? Code?

Revive Adserver has a cache mechanism which is set to 20 minutes by default. The reason is performance. You could decide to go with a shorter cache time, but generally this hurts performance or might even crash your server.

You'll have to enter the width and height (mandatory). I would also recommend that you set the click tracking to "do not alter".

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?

Please have a look at the recent blog post outlining the options for VAST2 in Revive Adserver: http://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/

Can you explain what you mean by "auto linking"?

If you see that the server is returning 500 Internal Server Error, the best approach is to look in the Apache error_log file on the server, since the exact details and cause of the error will be recorded in that file.