Jump to content

Revive Adserver Forum

Administrators
  • Content Count

    18
  • Joined

  • Last visited


Reputation Activity

  1. Upvote
    Revive Adserver Forum got a reaction from andrewatfornax in Can Revive Adserver Support Vast 2.0?   
    One of the more frequently asked questions that we see about Revive Adserver is about VAST support. People want to know why Revive Adserver doesn’t support VAST 2.0 or VAST 3.0 out of the box.
    Well, here’s why.
    When we took over what was OpenX Source and re-named it Revive Adserver back in 2013, all we hoped for was the chance to allow the project to grow once again – and it has done so, beyond all expectations. We now have over 6,000 users of Revive Adserver, we’ve released 10 updates to the software, and closed 337 issues in GitHub, including numerous security fixes.
    We’ve also been extremely proud to introduce a number of brand new features to the software that users have wanted for years – such as asynchronous JavaScript delivery tags, logging of blank impressions and improvements to the delivery algorithm for better campaign delivery.
    The amazing team of developers who volunteer their time to Revive Adserver are dedicated to making as much happen as possible, as soon as possible – but the truth is that there is always going to be more work than time, so there will always be some users who are disappointed that the feature they want the most isn’t included out of the box.
    You may be aware that VAST 2.0 support is available for Revive Adserver via the (commercial) Advanced Video Ads plugin for Revive Adserver. This plugin was developed by two of the volunteer members of the Revive Adserver team before Revive Adserver was formed. Given their time and effort to create this commercial plugin, it would be unfair to ask them to open source this plugin.
    However, in the event that anyone else chooses to develop or otherwise open source a VAST plugin for Revive Adserver that is suitable, then as a project, we would not hesitate to include such a plugin in the core product.
    So, to everyone who feels that VAST 2.0 or 3.0 support should be in the core of Revive Adserver, we’re sorry that it’s not there already. We’d love it to be there as much as you – but as a project based on the goodwill of its members to create code for free and release it as open source, we can only deliver what the community puts in. If something suitable is donated, then we’ll absolutely include it.
    Until that day, however, I hope that you’ll understand, and appreciate everything that Revive Adserver does, completely freely and openly.
    Sincerely,
    Andrew Hill


    View the full article
  2. Upvote
    Revive Adserver Forum got a reaction from andrewatfornax in Asynchronous Js Tags Reducing Revenue   
    Async tags use a friendly iframe, so RTB systems shouldn't mind. Most likely cause is that your pages are loading faster now, but the async tags mean the visitors never see the ads because your own ad server is slow.
  3. Upvote
    Revive Adserver Forum got a reaction from andrewatfornax in Thanks to our sponsor: Platform IQ   
    In our last blog post, discussing the results of the Revive Adserver 2016 Community Survey, we highlighted the fact that, on the whole, the community would like to see more features added to Revive Adserver, but that there were mixed views on how this should happen – a mixture of improving documentation to allow more developers to contribute, as well as seeking corporate sponsorship or crowdfunding to allow the core developers to spend more time working on the project.
    Following on from that theme, the core Revive Adserver team would like to publicly thank Platform IQ, who have now sponsored the development work for two core features: they paid for both the development work in the Revive Adserver 4.0 release to replace the phpSniff library for browser & operating system detection with the more modern Sinergi library, and for the development of the asynchronous tags feature that was introduced in Revive Adserver v3.2 in the spring of 2015.
    Without Platform IQ’s sponsorship, it is likely that these features would not have been released. If you are in need of professional services for Revive Adserver, then please do consider Platform IQ, given their very generous sponsorship of the Revive Adserver development effort. You may even notice some advertising appearing from Platform IQ, across our site and forum in the near future, as we experiment with ways to generate revenue to enable us to develop new functionality in Revive Adserver.
    In addition, we also want to thank Aqua Platform, who are sponsoring the hosting of our website, forum site, and other sources, and the SSL certificates we use. Aqua Platform specializes in Revive Adserver hosting, and have been a great help when we were doing performance testing for the improved browser and operating system targeting functionality in Revive Adserver v4.0.
    We would also like to take this opportunity to let larger, corporate users of Revive Adserver know that if they have a need for new functionality to be added to Revive Adserver, then we would please ask that they get in touch with the core team. We would love to discuss your needs, particularly if it’s a commonly requested feature. It may be that even a modest contribution towards the development of the feature will help make it happen faster, especially if there are a number of corporate users looking for the same functionality.
    View the full article
  4. Upvote
    Revive Adserver Forum reacted to Erik Geurts in Zone invocation codes are not used for Video Ads.   
    Can you please explain what the problem is you are trying to solve? 
  5. Upvote
    Revive Adserver Forum reacted to Erik Geurts in Zone invocation codes are not used for Video Ads.   
    It is not an error message. It simply tells you that zones being used for pre-roll video do not use the ordinary invocation code.
    Just follow the link in the note to http://documentation.revive-adserver.com/display/DOCS/Invocation+code%3A+Zone+level#InvocationCode:ZoneLevel-Video where you will find more information about what to do.
    Also please have a look at https://www.revive-adserver.com/blog/can-revive-adserver-support-vast-2-0/
  6. Upvote
    Revive Adserver Forum reacted to Erik Geurts in Zone invocation codes are not used for Video Ads.   
    Revive Adserver is what it says, an ad server. You'll have to provide the video player yourself.
  7. Upvote
    Revive Adserver Forum reacted to Erik Geurts in Track Click GWD to Revive adserver with Iframe   
    Adding the click macro to the source URL of the iframe means that a click will be counted for every single impression. You should remove that.
    The real answer to your question is that clicks inside iframes can not be counted.
  8. Upvote
    Revive Adserver Forum reacted to Erik Geurts in Track Click GWD to Revive adserver with Iframe   
    Sorry to disappoint you, but since the ad server is completely unaware of what's going on inside the iframe, it is impossible to count clicks on this type of externally hosted banner.
  9. Upvote
    Revive Adserver Forum reacted to Erik Geurts in AMP and Revive Adserver?   
    Please do not double post the same question.
  10. Upvote
    Revive Adserver Forum reacted to Erik Geurts in Geotargeting and MaxMind .dat files   
    This recommendation is incorrect. It should not be needed to set that "Even if GeoIP data unavailable checkbox" on, in fact, it is advised to never do that unless you know exactly what you're doing.
     
    I recommend double checking that path, and to make sure that the folder and the files in it are actually accessible.
  11. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Revive Adserver v3.2.4 Released   
    Revive Adserver v3.2.4 is available now. It fixes several bugs introduced in v3.2.3 published on March 2nd, 2016, and a few other bugs that have been reported to us in recent weeks.
    [url={url}]View the full article[/url]
  12. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Make sure you receive our update notifications   
    As with any software, it is important to keep your ad server system’s software up to date with the most recent release. Where to find Update information The Revive Adserver software has a useful built-in update notification feature, which helps system administrators stay up to date about the latest release of our software. It can be found by […]
    [url={url}]View the full article[/url]
  13. Downvote
    Revive Adserver Forum reacted to Richard Foley in Spam in forum   
    There's an irregular amount of spam on the site, admins need to spend a little more time cleaning up, or you need more admins :)
  14. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Revive Adserver v3.2.2 Released – Security Fix   
    Revive Adserver v3.2.2 is now available. This release fixes a number of medium security issues, which were recently discovered and reported to the Revive Adserver Project team, some via direct community feedback, but mostly via the Revive Adserver HackerOne project (which is the reason for the relatively large number of security issues resolved in this […]
    [url={url}]View the full article[/url]
  15. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Keep Your Revive Adserver Installation Up To Date   
    Following up on an article about the quick adoption of Revive Adserver v3.2.0, I had a look at the current situation. From the numbers for July 31, 2015, it turns out that almost half of all Revive Adserver installations runs a recent version of the software, v3.0.6 or above.
    Version 3.2.x
    Seeing over 2,000 instance running v3.2.x, and over 1,300 of those on the most recent v3.2.1 is very rewarding. These users take full advantage of the newest functionality, which includes the asynchronous javavcript tags introduced in v3.2.0 (and a small fix for Flash ads via async tags in v3.2.1).
    Version 3.1.0
    A little over 1,700 of you are still running on version 3.1.0. That version is perfectly stable, and if you don’t have a need for asynchronous tags, it is understandable that upgrading is postponed. Since the previous blog post, some 15% of v3.1.0 user have upgraded to v3.2.0 or v3.2.1. These newer versions do have many enhancements and bug fixes, so I would suggest that upgrading is something to be considered.
    Recommendation to upgrade for users of all older versions
    Version 3.0.6 is a small security fix relative to v3.0.5, so it might even be that part of those v3.0.5 installation have that patch applied, even though the application will still report in as v3.0.5.
    Anyone still running Revive Adserver software older than v3.0.5 is exposed to several known security vulnerabilities, all of which have been fixed a long time ago. I would like to urge anyone still using one of those older versions to upgrade to the most recent version available. Just download the newest version and then follow the upgrade instructions. Like with any other software product, running the latest stable version is the safest option.


    View the full article
  16. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Can Revive Adserver Support Vast 2.0?   
    One of the more frequently asked questions that we see about Revive Adserver is about VAST support. People want to know why Revive Adserver doesn’t support VAST 2.0 or VAST 3.0 out of the box.
    Well, here’s why.
    When we took over what was OpenX Source and re-named it Revive Adserver back in 2013, all we hoped for was the chance to allow the project to grow once again – and it has done so, beyond all expectations. We now have over 6,000 users of Revive Adserver, we’ve released 10 updates to the software, and closed 337 issues in GitHub, including numerous security fixes.
    We’ve also been extremely proud to introduce a number of brand new features to the software that users have wanted for years – such as asynchronous JavaScript delivery tags, logging of blank impressions and improvements to the delivery algorithm for better campaign delivery.
    The amazing team of developers who volunteer their time to Revive Adserver are dedicated to making as much happen as possible, as soon as possible – but the truth is that there is always going to be more work than time, so there will always be some users who are disappointed that the feature they want the most isn’t included out of the box.
    You may be aware that VAST 2.0 support is available for Revive Adserver via the (commercial) Advanced Video Ads plugin for Revive Adserver. This plugin was developed by two of the volunteer members of the Revive Adserver team before Revive Adserver was formed. Given their time and effort to create this commercial plugin, it would be unfair to ask them to open source this plugin.
    However, in the event that anyone else chooses to develop or otherwise open source a VAST plugin for Revive Adserver that is suitable, then as a project, we would not hesitate to include such a plugin in the core product.
    So, to everyone who feels that VAST 2.0 or 3.0 support should be in the core of Revive Adserver, we’re sorry that it’s not there already. We’d love it to be there as much as you – but as a project based on the goodwill of its members to create code for free and release it as open source, we can only deliver what the community puts in. If something suitable is donated, then we’ll absolutely include it.
    Until that day, however, I hope that you’ll understand, and appreciate everything that Revive Adserver does, completely freely and openly.
    Sincerely,
    Andrew Hill


    View the full article
  17. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Revive Adserver V3.2.1 Released   
    Revive Adserver v3.2.1 is now available.
    This new version addresses and fixes the following issues:
    Flash banners now work correctly through the asynchronous tags introduced in v3.2.0. The campaign edit screen had javascript errors when switching to some languages other than English, and was therefore unusable. This has been fixed. Some translation strings that were mistakenly removed in the cleanup of the language files, have been restored. This fixes certain issues in the delivery limitations screen. The regular Javascript Tag is once again present in the invocation screen dropdown, in addition to the asynchronous tags introduced in v3.2.0. HTML entities, such as “&”, are now properly parsed when using the “Alter HTML” functionality for a banner. This should fix a problem with truncated destination URLs. The getBannerTargeting API call did not work when the banner didn’t have any delivery limitation. This has been fixed. The full list of changes included in version 3.2.1 can be reviewed on the project’s Github pages.
    Download, install and upgrade
    Revive Adserver v3.2.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(s) being used meet(s) the minimum technical requirements.


    View the full article
  18. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Quick Adoption Of Revive Adserver V3.2.0   
    Revive Adserver version distribution on May 25, 2015
    One month after the release of v3.2.0 of the Revive Adserver software, we’re starting to see a nice adoption rate for the new version by the community. This graph shows the various versions and their relative share of the overall picture.
    There were a total of 6,449 active installations of Revive Adserver being counted on May 25.
    Of those, 693 were already running on the latest version 3.2.0, which is 11%. 31% of the installations are running on version 3.1.0. Almost 40% are still running on version 3.0.5. No less than 16% of installations are still running v3.0.2, that’s over 1,000 installations. The remaining 313 installations, less than 5%, are running some other version. We are very proud to notice that so many of you have started to use version 3.2.0. If you’re still using version 3.1.0, that’s fine too. It might be that you’re waiting for a known issue in v3.2.0 with Flash banners not working correctly via the new asynchronous tags to be fixed. We’re close to releasing a bug fix release that will take care of that.
    Running version 3.0.5 or even version 3.0.2, which is what more than half of the community is doing, is something we are a little bit concerned about. Any versions before v3.1.0 (or the special patch release v3.0.6) has several known security vulnerabilities. We would like to urge anyone still using one of those older versions to upgrade to the most recent version available. Just download the newest version and then follow the upgrade instructions.


    View the full article
  19. Upvote
    Revive Adserver Forum got a reaction from andrewatfornax in Base Plugins   
    see http://documentation.revive-adserver.com/display/DOCS/Standard+Plugins
  20. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Base Plugins   
    see http://documentation.revive-adserver.com/display/DOCS/Standard+Plugins
  21. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Revive Adserver V3.2.0 Released   
    The Revive Adserver project team is proud to announce the immediate availability of Revive Adserver v3.2.0.
    The most important improvements for this new version:
    Revive Adserver now offers support for asynchronous javascript tags. The benefit is that a website that contains these asynchronous tags will continue to work even if the ad server, for whatever reason, is slow or not responding. Many new translations are included, from contributions by community members in our Translations project on Crowdin. Fixes for a dozen bugs. A separate post describing and explaining asynchronous tags will be posted in the coming days.

    What’s New in Revive Adserver version 3.2.0?
    Version 3.2.0 of Revive Adserver does not include any security updates.
    We have included the following new features and improvements in Revive Adserver v3.2.0:
    Added new Javascript based asynchronous tags. Added new help dialogue for companion positioning option. Integrated (most) translations with Crowdin. Added plugin hooks to the VAST events in the VideoAds plugin. Added preliminary support for PHP7. Version 3.2.0 introduces a number of bug fixes:
    Fixed issue with interstitial images (e.g. close.gif) always using http:// even when the request came via https. Fixed issue with interstitial layers showing even when no matching banner was found, since the introduction of blank logging. Fixed issue that prevented the error message screen to be displayed when trying to install or run Revive Adserver with some required functions disabled via php.ini. Fixed issue causing campaign revenue to be improperly parsed when using a number format different than nnnn.nn. Fixed a problem with the destination URL not being available for new overlay video ads, and potentially other HTML-based custom banner types. Fixed the size of the search popup window under Chrome. Fixed missing translation string from statistics screens for conversions. Fixed issue preventing contract campaigns to reach their daily target when TZ had a negative offset. Fixed a problem with “Export Statistics to Excel” not working on some platforms. Fixed a problem with VideoAds VAST events not properly being logged on Postgres, as the required pl/pgsql function wasn’t created during install. Fixed potential timeouts or memory limit issues when displaying the audit log index. Version 3.2.0 introduces one non-backwards compatible change:
    The signatures of bannerTypeHtml/Text’s preprocessForm() and processForm() methods has been updated to what was actually used when invoking them. Albeit unlikely, this might clash with the definition used in some custom plugins. The full list of changes included in version 3.2.0 can be reviewed on the project’s Github pages.
    Download, install and upgrade
    Revive Adserver v3.2.0 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(s) being used meet(s) the minimum technical requirements.



    View the full article
  22. Upvote
    Revive Adserver Forum got a reaction from Richard Foley in Beta Version Of Revive Adserver V3.2.0 Released   
    The Revive Adserver project team is proud to announce the availability of a Beta release of the Revive Adserver software.
    We’re asking members of the community to help us test this beta release of version 3.2.0, with focus on the following topics:
    Asynchronous Javascript tags
    We’re very proud to finally be able to offer support for Asynchronous Javascript tags. In short, these tags work in such a way that any delay in the adserver itself, will no longer cause a delay in the rendering of the webpage on which the tags are placed.
    The new Asynchronous tags can be generated just as easily as before, by going to the Invocation Code tab of any zone. A new type of code will be presented when running the v3.2.0 beta: Creating invocation code for the new Asynchronous JS tags
    We’ve tested the asynchronous tags in a variety of scenarios, but we might have missed a few. We’d like to ask the menbers of the community to test their banners with existing third party ad tags in combination with the new async tags. Do the third party ads work correctly when served via Revive Adserver onto a webpage? Likewise, we’d like to ask you to verify if the asynchronous tags, when trafficked into a third party ad server down the line, work correctly.
    Language and translations
    A lot of work went into a clean-up of the English language files of the product. At the same time, we’ve started a large scale translation project (see the recent blog post Translations for Revive Adserver). It is not unlikely that one or more or the English text lines have unknowingly been removed, but are still ‘in use’.
    You would recognize this from a strange looking ‘placeholder’ text instead of the actual text you used to see in a screen, a field label, an explanation, a mouse-over, or anywhere else in the user interface.At the same time, a translator may have accidentally introduced something in a translation that breaks the user interface (for example, a line break was introduced or a special character that is not properly displayed). Delivery of contract campaigns
    Version 3.1 (released in December 2014) introduced a set of fixes related to the correct and full delivery of contract campaigns. In this version 3.2.0-beta, we’ve fine-tuned this code even more to take better care of situations where the ad server is running in time zones with a positive offset from UTC. We thank community member Victor (Rhapsodyv) for this contribution to the project. We would like to ask members of the community to test delivery of contract campaigns. Of course, we would welcome any feedback on any of the other changes, improvements and fixes as detailed in the release notes below.

    How to test this beta release?
    Version 3.2.0-beta can now be downloaded and tested by the community.
    The purpose of the beta testing phase is to allow users and developers to thoroughly test the new version before it will be released as a stable version. If the beta testing phase proceeds according to plan, we intend to publish the official version 3.2.0 two weeks after the beta release.
    We recommend that users do not upgrade their existing ad server installations if it is mission critical, or if they are uncertain about their abilities to deal with bugs, upgrade issues, or other unexpected problems.
    Please make sure to study the release notes below, including the notes on non-backwards compatible changes.
    What’s New in Revive Adserver version 3.2.0-beta?
    Version 3.2.0-beta of Revive Adserver does not include any security updates.
    We have included the following new features and improvements:
    Added new Javascript based asynchronous tags. Added new help dialogue for companion positioning option. Integrated (most) translations with Crowdin. Added plugin hooks to the VAST events in the VideoAds plugin. Added preliminary support for PHP7. Version 3.2.0-beta introduces a number of non-backwards compatible changes:
    Fixed issue with interstitial images (e.g. close.gif) always using http:// even when the request came via https. Fixed issue with interstitial layers showing even when no matching banner was found, since the introduction of blank logging. Fixed issue that prevented the error message screen to be displayed when trying to install or run Revive Adserver with some required functions disabled via php.ini. Fixed issue causing campaign revenue to be improperly parsed when using a number format different than nnnn.nn. Fixed a problem with the destination URL not being available for new overlay video ads, and potentially other HTML-based custom banner types. Fixed the size of the search popup window under Chrome. Fixed missing translation string from statistics screens for conversions. Fixed issue preventing contract campaigns to reach their daily target when TZ had a negative offset. Fixed a problem with “Export Statistics to Excel” not working on some platforms. Version 3.2.0-beta introduces a number of non-backwards compatible changes:
    The signatures of bannerTypeHtml/Text’s preprocessForm() and processForm() methods has been updated to what was actually used when invoking them. Albeit unlikely, this might clash with the definition used in some custom plugins. The full list of changes included in version 3.2.0-beta can be reviewed on the project’s Github pages.
    Download, install and upgrade
    Revive Adserver v3.2.0 Beta is now available for download.
    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 the minimum technical requirements.


    View the full article
  23. Upvote
    Revive Adserver Forum got a reaction from jmkonin in Creating Accounts   
    See http://documentation.revive-adserver.com
  24. Upvote
    Revive Adserver Forum reacted to andrewatfornax in Is This The Policy In Revive Adserver Hide Developer Documentation To Force To Pay For Support ? !   
    Hello,
     
    No, absolutely not. The Revive Adserver team do not have a policy to hide anything to force people to pay for support.
     
    We appreciate that our documentation is incomplete as at the time of this post - use documentation, admin documentation, and developer documentation. Indeed, there is simply no developer documentation for Revive Adserver at all at this point in time.
     
    As Revive Adserver is an open source project, with no financial backing, the time that the team spends working on the code, the website, the documentation and the forum is entirely voluntary, and unpaid for. While we have a few ideas for helping to raise money to pay for things like hosting, etc., at the present time, the income that the team gets from the Revive Adserver project is effectively zero.
     
    So, we'd love to have lots of developer documentation, and it's certainly on the list. When we get a chance, I am sure we will write some. Until then, we rely on the support of the community to help each other - and us - out, develop code where they can, suggest documentation improvements where they can, keep translation files up to date where they can, and support each other and answer questions on the forums where they can. All of these things will help the team spend the time they can afford to donate to the project focussed on core updates that will benefit everyone.
     
    Sincerely,
     
    Andrew
  25. Downvote
×
×
  • Create New...