Support for delivery limitations against older browser types has been dropped in Revive Adserver 4.0.0. As a result, existing Client - Browser delivery limitations for all browser types other than Chrome, Firefox, Internet Explorer, Safari and Opera will be removed as part of the upgrade process.
Support for delivery limitations against older operating systems has been dropped in Revive Adserver 4.0.0. As a result, existing Client - Operating system delivery limitations for all operating system types other than Windows 7, Windows XP, Windows 2000, Linux, FreeBSD, Solaris and Mac OSX will be removed as part of the upgrade process.
Users with either existing Client - Browser or Client - Operating system delivery limitations are advised that they should check delivery limitations before and after upgrading to Revive Adserver 4.0.0, to ensure that the limitations set remain valid for the desired delivery behavior.
Support for 3rd party click tracking of Rich Media - Google AdSense and Rich Media - Yahoo! Publisher Network banners has been removed, as these were not working. Banners configured to use these 3rd party click tracking options will be switched to the "Generic HTML banner" tracking option during the upgrade.
Browser and Operating System detection speed has been optimized, and as a result, the browser and operating system are only detected if necessary. Plugins that need access to this information during delivery will need to be updated to use the provided wrapper to perform browser/operating system detection. Please see the core Browser/Operating System delivery limitations plugin code for a usage example.
March 14, 2016
March 2, 2016
Logging plugins that also deal with conversions and conversion variables might require some additional testing.
October 7, 2015
June 2, 2015
April 28, 2015
The signatures of bannerTypeHtml/bannerTypeText's preprocessForm() and processForm() methods have been updated to what was actually used when invoking them. Albeit unlikely, this might clash with the definition used in some custom plugins.
December 17, 2014
Revive Adserver now requires PHP 5.3+.
HTML banners no longer present URL and Target fields in the user interface unless editing an existing HTML banner where one of these fields is present; the URL(s) and target(s) should be set as part of the HTML banner.
A number of database table columns are removed as part of the upgrade process for Revive Adserver 3.1.0, as they were deprecated with the removal of the OpenX Market in version 3.0.0. Please ensure that you back up your Revive Adserver database before upgrading to 3.1.0.
Existing accounts with the name "Default manager" will be updated to "Default Account" to ensure the account name is consistent with updated language files. Similarly, existing accounts with the name "Administrator account" will be updated to "System Administrator".
Activation/deactivation emails and scheduled reports are now disabled by default when creating new advertisers via the API, in order to match the UI behaviour. This does not affect any existing advertiser account settings for this feature; but please be aware that the default for all new advertiser accounts has been changed.
The adRender hook function signature was missing the $richMedia argument before $loc and $referer. Please make sure you double check your custom plugins in case they use such hook.
December 17, 2014
May 14, 2014
April 8, 2014
March 13, 2014
Email based campaign activation/deactivation reports are now disabled by default when creating new advertisers. This does not affect any existing advertiser account settings for this feature; but please be aware that the default for all new advertiser accounts has been changed.
3rd party plugins developers should be aware:
The unused Zend XML-RPC library has been removed; please make sure your 3rd party plugins bundle their own copy if they need it.
The OA_Sync class has been moved to the RV_Sync class; please make sure your 3rd party plugins are updated accordingly.
December 20, 2013
December 13, 2013
Bug fixes made to 3rd party click-tracking mean that it is possible that existing, working 3rd party click-tracking configurations may break. Please see http://tinyurl.com/ojr989o for more details on why, and what combinations of servers & tags may be affected.