Matteo Beccati

If you don't have the legacy mysql extension installed, just edit the config file and use "mysqli" as database type instead.

Hi Nguyen,

This issue is due to database and in third step you should give valid data for database name / username  /password (use already created  database name).

The test setup was:
Campaign A, weight 99, single text banner, banner weight irrelevant Campaign B, weight 1, single text banner, banner weight irrelevant Text Zone 1, linked to both campaigns, chained to Zone B Text Zone 2, empty Test page with two async tags with the "do not show the same banner" flag. Zone 1 was pretty much always showing A, while Zone 2 was showing B. To be fair you don't even need chained zones: just repeat the tag for zone 1, unless you need to keep track of the "positions".

Hi, we basically went with whatever Google Adsense seemed to be using. Ads were supposed to be wrapped whithin an iframe, so the whole point is moot. We then decided to also allow ads without an iframe and I think that's where the problem comes from.
However, I believe the problem can be easily solved. Could you please create an issue on github, referencing this forum thread?

Thanks to @Erik Geurts who pointed me to this thread and this issue as well, I've been able to verify and fix the bug. The fix will apper in the next Revive Adserver release. Thanks for your report.

Or just rename all the PNG files in that folder.
Go in to the folder and :
ls | while read upName; do loName=`echo "${upName}" | tr '[:upper:]' '[:lower:]'`; mv "$upName" "$loName"; done
 

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.

Your PHP setup might not allow Revive to redifine the include path. Maybe set_include_path is disabled via your php.ini?

https://github.com/revive-adserver/revive-adserver/issues/466

If you've seen a segmentation fault, most likely you were running a PHP 5.4 version < 5.4.20, which is not compatible with Revive Adserver (See requirements on the website)

you need to put the host name as the script argument
 
e.g. php .../scripts/maintenance/maintenance.php your.adserver.com

A PHP Error?

Are you running suPHP? If so, consider switching to mod_php as suPHP doesn't play nicely with Revive plugins

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

The forum software has been upgraded. There's still some work to do on the graphics side, but I would expect that everything else is in working condition...

See the replies here. Most likely it's mod_security getting in the way.

The forum software has been upgraded. There's still some work to do on the graphics side, but I would expect that everything else is in working condition...

Fixed the error in the Country.delivery.php adding if (!function_exists('MAX_checkGeo_Country')) { and now a new error
 
Fatal error: Cannot redeclare max_checkclient_useragent() in /home/NFS-HA/vhosts/pubted.com/public_html/plugins/deliveryLimitations/Client/Useragent.delivery.php on line 28
 
Fixed, and new error
 
Fatal error: Cannot redeclare max_checkclient_browser() in /home/NFS-HA/vhosts/pubted.com/public_html/plugins/deliveryLimitations/Client/Browser.delivery.php on line 28
 
Fixed and now all banners are showing!!
 
Anyway, I think I will follow your suggestion Matteo

If you see strict standards error messages there's something wrong with your setup, as they should be hidden.
 
Also, judging by the output above an extension (xdebug?) is messing up with error messages.
 
Finally, RevMax is a 3rd party product and you shouldn't be searching for support about it here

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

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

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

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.

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

I'm afraid the developer documentation is gone during the project move to Revive Adserver. So there's no relevant URLs to link to just yet.