Jump to content

Revive Adserver Forum

Administrators
  • Content count

    18
  • Joined

  • Last visited

1 Follower

About Revive Adserver Forum

  • Rank
    Administrator

Contact Methods

  • Website URL
    http://www.revive-adserver.com/

Recent Profile Visitors

3,221 profile views
  1. Revive Adserver v4.1.4 is available now. This new version of the Revive Adserver software includes two new settings that can be enabled, one to prevent the creation of a unique but random ID value in the OAID cookie, and the other to anonymise IP addresses coming into Revive Adserver before they are processes. These new settings will help with GDPR compliance. To take advantage of the new settings, log in as an Administrator and go to the Configuration tab. The Banner Delivery Settings page is automatically displayed. The new settings are in a section called “Privacy Settings”: Put a checkbox in the setting(s) you want to enable and don’t forget to click the “Save changes” button at the end of the page. If the “Disable unique Viewer id cookies” setting is On, any existing OAID cookies for visiting browsers will be replaced with the same value for every visitor: 01000111010001000101000001010010. This is the binary representation of the acronym GDPR. New visitors will also receive a new OAID cookie with value 01000111010001000101000001010010. If the “Anonymise viewer IP address” setting is On, then the Revive Adserver software will turn the 4th octet of any IP address it deals with into a zero, thus making it meaningless when it comes to identifying individual visitors. For example: 192.168.1.123 will become 192.168.1.0. The anonymized IP address will subsequently be used for geotargeting (if enabled) or for recording conversion statistics. In this release v4.1.4, these two settings will be Off by default in the interest of backward compatibility. In a future release, most likely v4.2.0, the defaults will become On. Below is a list of all changes in Revive Adserver v4.1.4: New feature: Added new privacy settings under ‘banner delivery settings’ to optionally stop tagging viewers via a cookie with a unique identifier (OAID) and to anonymise IP addresses, in order to better comply with GDPR regulations. Fixed an issue with evaluating very large delivery rules that caused an internal error with the PCRE library. Reverted a change introduced in v4.1.2 that was preventing preferences from being properly saved. Full release notes for v4.1.4 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1.4 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1.4 released appeared first on Revive Adserver. View the full article
  2. If you work in the digital advertising industry, you must have heard about GDPR by now. So a very brief introduction should be sufficient. GDPR is an acronym for “General Data Protection Regulations”, which is a law that was adopted by the European Parliament in the autumn of 2015 and which came into force on May 25, 2016. There was a 24 month implementation period, and as a result the enforcement of GDPR commences on May 25, 2018. We want to help the community understand how GDPR and other privacy regulations apply to using the Revive Adserver open source software. That’s why we’ve published a number of articles. The first article has an introduction about GDPR and how it relates to the Revive Adserver software. The second article describes how the Revive Adserver software treats personal data. Privacy and data protection are important topics, but they are also complicated. Regulations are updated all the time and their interpretation evolves constantly, for example from jurisprudence. We will update the aforementioned articles from time to time when new insights become available. The post Revive Adserver in the age of GDPR appeared first on Revive Adserver. View the full article
  3. Help us test the upgrade of Geotargeting rules to GeoIP2 The Revive Adserver project team is looking for help from community members to test the upgrade path of geotargeting to GeoIP2. In a recent blog post, we announced our plans to modernize the Geotargeting feature in Revive Adserver. The upcoming version 4.2 of Revive Adserver will have support for the new GeoIP2 and GeoLite2 data files published by MaxMind. In the blog post, we mentioned that we intend to include a migration process for existing geotargeting rules. This would ensure that banners with existing getoargeting will be converted from the current format to the new format, as best as possible. However, we recognize that there are very many ways to use geotargeting, and even more combinations of all of those. As a result, it would be virtually impossible to define a set of test cases that cover every possible use case. The second best alternative is to enlist the help of the Revive Adserver community. If you use Revive Adserver with a few dozen, or preferably a few hundred banners, that have geotargeting rules specified, and if you’re willing and able to send us an export of the banners and targeting tables from your database, then please consider submitting the form below. Once we are ready to start testing, we will contact you (or a subset of the applicants if there is much interest) and provide instructions on how to send us the necessary table exports. Yes, I would like to contribute to the Revive Adserver project by participating in the Geotargeting upgrade path test process. My name* First name Last name My Email address* A note about your privacy: any personal data collected through this form will only be used to contact you for this particular test. The Revive Adserver project team will not share your data with anyone, and we will not contact you for anything other than this test. If you’re unable to assist us with this specific item, then please consider helping us by becoming a sponsor of the Revive Adserver project on Patreon. For as little as $10 a month or more, your financial contribution helps us to continue developing Revive Adserver so that it continues to be the world’s most popular, free, open source ad server system. The post Help us test the upgrade of Geotargeting rules to GeoIP2 appeared first on Revive Adserver. View the full article
  4. Revive Adserver has had support for geotargeting for ages, but the world has moved on (no pun intended). MaxMind, the company that creates and maintains the data files needed for the feature, is about to stop supporting the old “GeoIP” data files in favor of their newer GeoIP2 file format, and the free GeoLite2 files. We’re working on a new release, v4.2.0, of the Revive Adserver software, with support for these new GeoIP2 and GeoLite2 data files created by MaxMind. Here is what we have in mind: Starting with version 4.2, the Revive Adserver software will no longer ship with the original ‘MaxMind GeoIP’ plugin. Instead, there will be a new plugin that supports the new GeoIP2 and GeoLite2 data file formats distributed by MaxMind. It is our intention to develop a ‘migration’ so that any existing banner using a geotargeting delivery rule will automatically be converted to the new format. While upgrading from any older version of Revive Adserver to version 4.2.0, the old MaxMind GeoIP plugin will be removed automatically, to make room for the new one. The reason for this is that the new “Geo” delivery rules will not be compatible with the old rules. MaxMind no longer allow us to distribute the free GeoLite2 Country data file with our software releases. That will mean that our distributions will become a lot smaller in the future, since it no longer contains a large .dat file from MaxMind. It is our intention to add functionality to the new geotargeting plugin to enable it to download the required data files from the MaxMind website and store them on the server where the Revive Adserver software is installed. It will also be able to download subsequently updated files released by MaxMind on the first Tuesday of each new month. Please keep an eye on our blog, Twitter feed or forums to stay informed about the upcoming v4.2.0 release. The post Modernizing geotargeting in Revive Adserver appeared first on Revive Adserver. View the full article
  5. Revive Adserver v4.1.3 is available now. This is a maintenance release taking care of a single non-critical bug that was discovered in Revive Adserver v4.1.2 shortly after it was released on February 6th, 2018. Version 4.1.2 had some changes to how time zones are handled during the change to and from daylight savings time (DST). This turned out to trigger an old bit of code that caused the display of statistics with a breakdown by hour to be disfigured. See issue 949 with the fix as recorded on our Github account for more details. If you haven’t upgraded to v4.1.2 yet, we recommend that you skip that version and upgrade straight to v4.1.3, since it contains all the changes and fixes of v4.1.2 plus the fix for the new bug. If you have already upgraded to v4.1.2, and can live with this small bug, you can consider skipping this upgrade, since the fix will also be included in future releases. If you have already upgraded to v4.1.2, and would prefer to just implement the fix, see the Github issue and the code change. Below is a list of changes in Revive Adserver v4.1.3: Fixed an issue that prevented properly displaying hourly breakdown statistic screens. Full release notes for v4.1.3 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1.3 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1.3 released – bug fix appeared first on Revive Adserver. View the full article
  6. Revive Adserver v4.1.2 is available now. This new release fixes a number of bugs that were discovered since the release of Revive Adserver v4.1.1 on October 24, 2017, and it has a small improvement for the HTML5 banner functionality introduced with v4.1 in October 2017. Below is a list of changes in Revive Adserver v4.1.2: Improved HTML5 banner compatibility by whitelisting a few more common file extensions, e.g. “.svg”, “.txt”, “.json”, “.xml”. Fixed an issue that was sometimes preventing file/folder permission errors from being written to the debug log. Fixed an issue with the Campaign Banners page not working when the banner preview was enabled and the campaign contained a mix of HTML5 and regular HTML banners. Fixed an issue with saving account preferences on MySQL 5.7+. Fixed an issue with failing to warn users about silent delivery rule data truncation when using MySQL. Fixed an issue with the core delivery rule code failing to take into account changes to data made by delivery rule plugins, causing the UI to report an issue with delivery rules, when in fact, the rules were working. Fixed an issue with incorrect timezone conversion during DST switches, potentially affecting campaign activation/deactivation times. Fixed a broken help link for video banner invocation in the UI. Various language updates and corrections. Full release notes for v4.1.2 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1.2 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1.2 released – bug fixes appeared first on Revive Adserver. View the full article
  7. In January 2017, we announced that Revive Adserver had launched on Patreon, a crowdfunding site that allows Revive Adserver users to make a small financial contribution each month, to help the Revive Adserver project. Then, in May 2017, we reported that we had already met our first goal of $250/month, and how that was helping us to do more, as well as that we were approaching the next goal of $500/month. Today, we are delighted to be able to announce that we have now reached our $500/month goal, and are only $173/month away from our $1000/month goal as well. However, our next goal of $1000/month is a massive one for Revive Adserver – this is when we plan to block out guaranteed weekly development time. The income from our Patreon site is already helping us to spend more time on the project, but being able to block out guaranteed development time would be huge. To help give you an idea of what this could mean, we could: Continue with our already improved level of support via the Community Forums; Continue with our work to update the documentation to cover all areas of functionality; and Release more new features and bug fixes – in 2017, we put out a release of Revive Adserver roughly every quarter, resolving 33 bugs (4 of which fixed security issues), as well as introducing a host of important new features: HTML5 banner support; new WYSIWYG HTML editor option for HTML banners; improved security by expiring a user’s sessions when their password is changed/recovered; disable impression and click logging for expired banners, to reduce overcounting in statistics; new hostname/domain name whitelist/blacklist delivery rules; support for ordering advertisers, campaigns, banners, websites and zones by the date each was last updated; zone chaining to undefined sized zones. Imagine what we could do with guaranteed weekly development time! Please help us to do even more in 2018 by getting us to our next Patreon goal – consider supporting us at a level that you are comfortable with. Although we suggest $10/month as a starting point, you are free to sponsor us at any level, so, if a cup of coffee per month is all you can afford, then please, don’t hesitate to sign up and support us with a couple of dollars. There are over 8,000 instances of Revive Adserver in use, so if everyone contributed just a small amount each month, we could easily meet not just our next goal of $1000/month, but many of the goals after that! Thank you, The Revive Adserver Team The post Help us reach our next Patreon goal appeared first on Revive Adserver. View the full article
  8. Revive Adserver v4.1.1 is available now. This new release fixes a number of bugs that were discovered since the release of Revive Adserver v4.1.0 on October 18, 2017. Users trying to upgrade their installations reported problems when they initially installed the software before v2.8.x. These problems have now been fixed. Systems that were initially installed with v3.0 or higher, were not affected. We also fixed a small but annoying issue on the Campaign Properties screen when editing an existing campaign. Below is a list of changes in Revive Adserver v4.1.1: Removed newly added database integrity check for default values and not null constraints, that was preventing successful upgrades when the database itself was created before 2.8.x. Fixed various issues preventing a direct upgrade from phpAdsNew 2.0.11-pr1 and possibly earlier 2.4/2.6 versions. Fixed an issue that was causing the campaign radio button on the campaign edit screen to be empty and the bottom half of the form to disappear when editing an existing campaign. Full release notes for v4.1.1 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1.1 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1.1 released – bug fixes appeared first on Revive Adserver. View the full article
  9. We’re very proud to announce the immediate release of our newest software product: Revive Adserver v4.1 is available now. This version of the world’s most popular, free, open source ad serving system contains several enhancements and improvements (described in detail below) and some bug fixes. The most important enhancements are: support for HTML5 ads (beta), new delivery rules for whitelisting and blacklisting domains, and a WYSIWYG editor for HTML banners. Below is a list of enhancements and improvements included in Revive Adserver v4.1: We added a new (optional) setting to prevent a user from being redirected to the landing page associated with a banner, when the banner has been deactivated or when the campaign it belongs to is no longer active. In such cases, impressions and clicks on those banners will no longer be counted either. When generating invocation codes (tags), there is a much shorter comment than in earlier releases (long comments can be switched on while generating tags if so desired). In the user interface, a number of terms have been renamed, to bring the language used into line with modern terminology used in the advertising industry: * ACLs are now Delivery Options; * Delivery Limitations are now Delivery Rules; * Targeting Channels are now Delivery Rule Sets. We added some new Site Delivery Rules, to enable white-listing or black-listing based on hostnames and/or registerable domain names. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous. We added a new security feature to invalidate all the active sessions of the current user when changing or recovering their password. We added the option to use TinyMCE as a WYSIWYG HTML editor (just like in WordPress) when creating and editing HTML banners. The editor is switched off by default, for increased backwards compatibility, but it can be enabled by default via the user interface account preferences. This preference is ignored when editing HTML ads containing scripts or iframes in order to avoid inadvertently altering 3rd party tags. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous. We added a new {img_url_prefix} magic macro that will print the configured http/https images URL during delivery, depending on the calling protocol. We added (beta) support for HTML5 banners, allowing the upload of banners in IAB compliant ZIP file formats. The development of this feature has been sponsored in part by Aqua Platform, a company specializing in Revive Adserver hosting at enterprise scale. We added support for ordering advertisers, campaigns, banners, websites and zones by the date each was last updated, on the main index page for each, to make finding recently updated entities easier in large installations. We added automatic switching to the mysqli driver when mysql is selected as the database type in the configuration file, but the mysql extension is not available (and vice versa). We added custom events for Javascript Async delivery, allowing the website to better interact with Revive Adserver, e.g. to refresh some ad placements or modifying the data that is sent to and received from the ad server. There have also been many other smaller enhancements and improvements, described in detail in the release notes. We have fixed numerous bugs, and there are also some non-backward compatible changes, so please make sure you carefully study the release notes. Important: this v4.1 release has a Non-Backwards Compatible Change. Support for PHP 5.5 has been dropped and Revive Adserver now requires at least PHP 5.6.0. Full release notes for v4.1.0 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.1 released appeared first on Revive Adserver. View the full article
  10. The Revive Adserver team announces Release Candidate 2 of Revive Adserver v4.1. After recently publishing the first Release Candidate for v4.1, our testers found several bugs related to performing an upgrade from an earlier version, when the database server being used is PostgreSQL. These bugs have now been fixed. This matter does not affect users of the MySQL database server software (which is in use by the majority of people). We took advantage of the extra time this gave us to add one new feature: Custom events for Javascript Async delivery, allowing the website to better interact with Revive Adserver, e.g. to refresh some ad placements or modifying the data that is sent to and received from the ad server. For an overview of all the other changes, improvements and fixes in this release candidate 2, please review our blog post about Release Candidate 1. Important: these release candidates, and the actual v4.1 release later, will have a Non-Backwards Compatible Change. Support for PHP 5.5 has been dropped and Revive Adserver now requires at least PHP 5.6.0. Full release notes for v4.1.0-rc2 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1 Release Candidate 2 is available for download now. Please keep in mind that this is a release candidate, and as such it can result in issues. If you don’t feel confident about testing beta-level software, we recommend that you wait until the final v4.1 is available. This will be announced here on the blog. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions Several new developments in version 4.1 have been sponsored by community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. The post Release Candidate 2 for Revive Adserver v4.1 appeared first on Revive Adserver. View the full article
  11. The Revive Adserver team is immensely proud to announce the immediate availability of the Release Candidate of Revive Adserver v4.1. Today marks the fourth anniversary of the unveiling of the Revive Adserver project, with the release of version 3.0. We feel that this is the perfect day to announce the next major release of the Revive Adserver software, which has been given version number v4.1. Since this new version includes a large number of changes and enhancements, including some breaking changes, we think it is appropriate to first make available a Release Candidate. This will enable users, administrators, plugin developers, hosting providers and consultants to put the new version to the test in all sorts of scenarios and environments. If everything goes according to plan, we expect to release the final v4.1 in 2 weeks from today. Below is a partial list of enhancements and improvements included in this Release Candidate for Revive Adserver v4.1: We added a new (optional) setting to prevent a user from being redirected to the landing page associated with a banner, when the banner has been deactivated or when the campaign it belongs to is no longer active. In such cases, impressions and clicks on those banners will no longer be counted either. When generating invocation codes (tags), there is a much shorter comment than in earlier releases (long comments can be switched on while generating tags if so desired). In the user interface, a number of terms have been renamed, to bring the language used into line with modern terminology used in the advertising industry: * ACLs are now Delivery Options; * Delivery Limitations are now Delivery Rules; * Targeting Channels are now Delivery Rule Sets. We added some new Site Delivery Rules, to enable white-listing or black-listing based on hostnames and/or registerable domain names. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous. We added a new security feature to invalidate all the active sessions of the current user when changing or recovering their password. We added the option to use TinyMCE as a WYSIWYG HTML editor (just like in WordPress) when creating and editing HTML banners. The editor is switched off by default, for increased backwards compatibility, but it can be enabled by default via the user interface account preferences. This preference is ignored when editing HTML ads containing scripts or iframes in order to avoid inadvertently altering 3rd party tags. The development of this feature has been sponsored by a generous donor who has asked to remain anonymous. We added a new {img_url_prefix} magic macro that will print the configured http/https images URL during delivery, depending on the calling protocol. We added (beta) support for HTML5 banners, allowing the upload of banners in IAB compliant ZIP file formats. The development of this feature has been sponsored in part by Aqua Platform, a company specializing in Revive Adserver hosting at enterprise scale. We added support for ordering advertisers, campaigns, banners, websites and zones by the date each was last updated, on the main index page for each, to make finding recently updated entities easier in large installations. We added automatic switching to the mysqli driver when mysql is selected as the database type in the configuration file, but the mysql extension is not available (and vice versa). There have also been many other smaller enhancements and improvements, described in detail in the release notes. We have fixed numerous bugs, and there are also some non-backward compatible changes, so please make sure you carefully study the release notes. Important: this release candidate and the actual v4.1 release later, will have a Non-Backwards Compatible Change. Support for PHP 5.5 has been dropped and Revive Adserver now requires at least PHP 5.6.0. Full release notes for v4.1.0-rc1 can be found on our Github page. Download, install and upgrade Revive Adserver v4.1 Release Candidate is available for download now. Please keep in mind that this is a release candidate, and as such it can result in issues. If you don’t feel confident about testing beta-level software, we recommend that you wait until the final v4.1 is available. This will be announced here on the blog. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server(s) being used meet(s) the minimum technical requirements. Community contributions Several new developments in version 4.1 have been sponsored by community members, either financially or in the form of code contributions. We’re very grateful for the support we’ve received. If you would like to contribute to our project, please consider becoming a patron on Patreon.com. The post Release Candidate for Revive Adserver v4.1 appeared first on Revive Adserver. View the full article
  12. In January, we announced that Revive Adserver had launched on Patreon, a crowdfunding site that allows Revive Adserver users to make a small financial contribution each month, to help the Revive Adserver project. So far, we are delighted that members of the Revive Adserver community have started to make contributions and that, within a week of launching, we reached our first goal of $250/month – in particular, thanks to our Revive Adserver sponsors. As a result of meeting this first goal, we’ve been able to make some great progress towards doing even more with Revive Adserver: The level of support that we’re able to provide on the forums has improved greatly – not only are we now able to respond to most posts daily, but we have been able to put in a great deal of effort to go through the history of unanswered posts and respond to most of them. (If you have a post that’s waiting for a response, please comment on it and we’ll respond!). We’ve been able to spend time working on user documentation – many of the items on our documentation “todo” list have been crossed off. The core team has been able to spend more time coding and reviewing community proposed changes – this week’s Revive Adserver v4.0.2 release is a direct result of the time that our Patreon sponsors have made available through their support. Of course, there are benefits to supporting Revive Adserver on Patreon as well! Depending on your level of support, there are options to: Get a weekly update on what the Revive Adserver team have been working on; Get advance notice of upcoming software releases, to let you plan for upgrades; Participate in occasional “Ask Me Anything” sessions with the core team; Vote on (and propose) what features should be included in future releases of Revive Adserver; Get your (or your company’s) name on our list of Revive Adserver sponsors; and Help the Revive Adserver project move forward faster – especially with regards to completing documentation and developing new features! Some of the above benefits will only become available once we meet certain goals on Patreon – at the moment, we are only $152/month away from our next goal. Please help us meet our next goal – consider supporting us at a level that you are comfortable with. There are over 8,000 instances of Revive Adserver in use, so if everyone contributed just a small amount each month, we could easily meet not just our next goal of $500/month, but many of the goals after that! The post Patreon and Revive Adserver appeared first on Revive Adserver. View the full article
  13. Revive Adserver v4.0.2 is available now. This new release includes one new feature and a number of bug fixes. Below is a list of changes in Revive Adserver v4.0.2: New: Revive Adserver now supports zone chaining to zones where the dimension(s) of the zone are undefined (i.e. “*”) as well as an exact match. Improved the handling of Email/Newsletter zone linking, to ensure that disallowed HTML banners are simply not shown in the first place when linking from the zone, and to fix a bug that allowed HTML banners to be linked to Email/Newsletter zones from the banner. Fixed a JavaScript error that occurred on the Campaign Properties page when the global Enable Conversion Tracking option is disabled. Fixed an issue with the Client/Language delivery limitation not properly working when targeting specific territories (e.g. en_US) or targeting the broader locale when the browser is only sending locale + territory. Improved the warning messages used when generating Local Mode and XML-RPC invocation tags to clarify why these tags are not compliant with IAB guidelines for ad impression measurement (i.e. the ad request comes from the server, not the client). Fixed numerous instances of incomplete breadcrumb trails in statistics pages. Broken examples of Inline Video banners have been removed from the UI. Fixed an incompatibility with recent MySQL versions (5.7.5+) when acquiring advisory locks, due to their name being now limited to 64 characters. Changed misleading “Connection Window” wording to “Conversion Window” in the settings screen, to match the current usage. Full release notes for v4.0.2 can be found on our Github page. Download, install and upgrade Revive Adserver v4.0.2 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. The post Revive Adserver v4.0.2 released appeared first on Revive Adserver. View the full article
  14. Revive Adserver v4.0.1 is available now. This new release fixes a number of bugs and security issues that were discovered since the release of Revive Adserver v4.0.0 on September 28, 2016. Below is a list of changes in Revive Adserver v4.0.1: Fixed an issue in the newly introduced mysqli driver, which was preventing the delivery engine from working when using unix sockets to connect to the database. Fixed an issue with the banner properties page accepting weights of zero, negative or numbers with decimal points. Fixed an issue preventing Revive Adserver from being installed or upgraded on setups using both a custom session.save_path and open_basedir, or using a custom session handler. Fixed an issue preventing Revive Adserver from serving video ads on recent Flash Player versions when loading HTTPS resources from an HTTP website. Fixed an issue preventing the Revive Adserver XML-RPC API from working on PHP 7+. Fixed an issue preventing forms generated with HTML_QuickForm from working with PHP 7.1. Fixed an issue with the “View by day/week/month” dropdown not properly working on PHP 7+. Fixed an issue with magic macros not properly working when nested in curly brackets, e.g. within JSON or JavaScript code. Fixed an issue with parent entities names being sometimes escaped twice in the inventory header, thus displaying HTML entities on screen. Fixed a missing translation string that prevented an error message from displaying in the installer, and various community-supplied translation string updates. This version 4.0.1 also contains fixes for four vulnerabilities that were recently discovered and reported to us through our HackerOne security program. Full release notes for v4.0.1 can be found on our Github page. Download, install and upgrade Revive Adserver v4.0.1 is available for download now. Once downloaded, please refer to the instructions for Installations of Revive Adserver or for Upgrading Revive Adserver. Make sure that the server being used meets the minimum technical requirements. View the full article
  15. Did you know that the idea of Revive Adserver is nearly 4 years old? It was early 2013 when the opportunity came along to purchase the OpenX Source code base from OpenX, and Erik, Matteo and myself decided to work together to create Revive Adserver, and breathe some new life into a project that had pretty much stalled for 5 years. In the years that have followed, we’ve made terrific progress – something that we are immensely proud of. However, it’s been clear for a while now that the community and the core Revive Adserver team want more. More features, more fixes, more documentation. And, what’s more, we want to do it faster. This was something that was confirmed by the results of our community survey last year. Today, to try to make this happen, Revive Adserver has launched on Patreon. If you’re not familiar with Patreon, it’s a crowd-funding website, but (unlike, say, Kickstarter), it’s not about raising funds for a specific, one-off development or product. Instead, it’s about delivering regular, monthly funding to the project, to allow the core team to spend more time on developing the things that the community wants. If you use Revive Adserver to help generate revenue from advertising, and you’re part of the community that wants to see more development and documentation done for Revive Adserver, then we need your help. We’re not asking for a fortune – just a small amount each month. Even just $10 a month per sponsor will help us a lot. Larger contributions are of course also very welcome. Please, visit our Patreon site, see what we have to say about what we want to achieve with your help, and sign up as a patron. Together, we will take Revive Adserver forward to another level, and see where the next 4 years takes us! View the full article
×