Non-BC Changes


On This Page:

Non-Backwards Compatible Changes

A consolidated list of all non-backwards compatible changes made in every Revive Adserver release, to help make life easier for administrators skipping multiple versions when upgrading.


Revive Adserver Release VersionRelease DateNon-Backwards Compatible Changes


September 13, 2023We removed support for creating new inline video ads using FLV type and/or streaming format.  Backwards compatibility for delivery is retained, meaning that banners that were created with older version and that still exist in the database will continue to work.


April 14, 2022
  • XML-RPC API v1 is deprecated and might be removed in a future version. Please make sure v2 is used instead.
  • Legacy SPC invocation code has been deprecated: delivery will still function as usual, but the tags cannot be generated anymore.
  • Default banner image URL configuration has been deprecated, since it interferes with blank impressions. It is still working if already set, but is not displayed anymore in the settings UI and will be removed in a future release.
  • It is no longer possible to set the password when creating new users via the admin interface: a welcome email will be sent instead for them to set their new password. Users created via the API will receive the welcome email when no password is set.
  • Removed unmaintained Java XML-RPC API client and its supporting libraries.


September 14, 2021
  • A PHP version greater or equal to 7.2.5 is now required to run Revive Adserver.

  • The mysql4_compatiblity setting has been removed: Revive Adserver will now always make sure that the appropriate (empty) sql_mode is set when running on a MySQL database.

  • Support for the legacy pecl MySQL extension has been removed: mysqli will always be used instead.

5.2.0March 16, 2021None


January 19, 2021
  • Delivery rules including South African subdivions Gauteng and Kwazulu-Natal will require manual adjusting.
  • Click tracking via ck.php is deprecated and the behaviour of some ad render internal functions (_adRenderBuildClickUrl, _adRenderBuildParams) has changed accordingly. The "{clickurlparams}" magic macro has been removed.
  • Removed 3rd Party click tracking plugin, as the system is not compatible with the new signed click tracking functionality.
  • Deprecated PHP execution inside banners by removing the setting from the admin UI. The (risky) functionality itself will be still working if enabled in the configuration file, but will be removed in a future release.
  • Removed support for Flash banners and the fl.js delivery file that is now unnecessary.
  • Removed Flash-based graphs and supporting libraries in the video ads plugin reports.
  • The new manager permission is disabled by default, which means that non-admin managers won't be able to delete items, unless an admin grants them the permission.
  • The VAST output was still using the obsolete video/x-mp4 as content type, which has now been updated to video/mp4.


September 30, 2019
  • The date and time that new user accounts are created / email address is updated has changed to UTC format in the database with this release. As timezone information was not stored with the previous values, these cannot be safely converted to UTC format. As a result, all user account creation / email address update values stored before upgrading to this release may not be accurate - but only by up to 13 hours.
  • There are several changes between the legacy GeoIP and GeoIP2 databases and the upgrade process will try to migrate the rules in the best possible way:
    • "Regions" have been split into two levels of subdivisions and the ISO-3166 database has been updated. Depending on the country, the old delivery rule will be transformed in the appropriate subdivision level and geopolitical changes applied to the best of our knowledge.
    • "Area code" is no longer returned. Any such delivery rule will be deleted.
  • The way the Geotargeting plugins work has been revamped. As such, third party geotargeting plugins or plugins depending on geotargeting information might require to be updated accordingly.


April 23, 2019
  • Revive Adserver now requires PHP 7.0.8+.
  • Revive Adserver now requires the PHP "zip" extension. (See the complete list of required PHP extensions.) This extension was needed in previous releases for HTML5 banner support, but was not previously enforced.
  • XML-RPC invocation is deprecated and requires manually renaming www/delivery/axmlrpc.txt to www/delivery/axmlrpc.php in order to restore XML-RPC invocation functionality. However, this is not recommended, and users are strongly advised to move to another form of delivery and remove the axmlrpc file again as soon as practicable.


October 18, 2017
  • Revive Adserver now requires PHP 5.6.0+.
  • The removal of a file related to the deprecation of Google Adsense click tracking in 4.0.0 may result in a 404 error during delivery for users who have upgraded, if they at some point were running a version prior to 4.0.0.


September 28, 2016
  • Revive Adserver now requires PHP 5.5.9+.
  • Client Delivery Rules:
    • Support for delivery rules against older operating systems has been dropped in Revive Adserver 4.0.0. As a result, existing Client - Operating system delivery rules 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 rules are advised that they should check delivery rules before and after upgrading to Revive Adserver 4.0.0, to ensure that the rules set remain valid for the desired delivery behaviour.
  • 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 rules plugin code for a usage example.


March 2, 2016
  • 3rd party logging plugins that also deal with conversions and conversion variables might require some additional testing.


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.


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.


September 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 for more details on why, and what combinations of servers & tags may be affected.