Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. After going to the Plugins tab, you need to click on the "Details" link for the Invocation Tags Plugin, before you can see the "Settings" link, but otherwise, the above is spot on.
  2. The Revive Adserver configuration file will be in your installation's "var" directory. It will have a name based on the domain name the site is running on (or installed with) with a .conf.php extension on the end. So, for example, it may be called "www.example.com.conf.php".
  3. Please let us know how you get on! The option for changing the operation interval was introduced for a specific need way back in the day, but unfortunately, unless you have amazingly high traffic volumes, reducing the OI from the default of 60 minutes tends to cause issues, because the (relatively) small number of impressions per OI means the maintenance script struggles to do a good job. Note that changing the OI will mean it takes a while for Revive Adserver to "learn" what the new impressions/OI values are, so don't expect instant and immediate results. One other tip might be to add some delivery capping to the banners, so that you only show each banner a few times a day (e.g.) to any given user. That can really help prevent over-delivery by thinning out the number of impressions that are possible. HTH!
  4. Ah, now, there used to be a feature to allow eCPM-based prioritisation, but I have to admit that I'm 100% sure that this is still definitely around and working. This is something that I suspect I will be looking into while working on documentation updates - but feel free to have a poke about and it might be in the config options somewhere and you can let us know if it is?
  5. I've created some documentation for this now! http://documentation.revive-adserver.com/display/DOCS/Running+Maintenance HTH.
  6. Revive Adserver uses PHP's mail() function to send email - so, exactly how that happens depends on your PHP configuration. See http://www.php.net/manual/en/mail.configuration.php for details.
  7. HTTPS connections will be enabled & handled by your web server - please see your webserver documentation!
  8. Check your web server logs. Blank screens are usually the result of an internal server error, which you'll need to look in the logs to understand what's happening and fix.
  9. Or it could be that the hardware is not the same, or PHP opscode caching is present on one but not the other - unfortunately, there are a very large number of variables when it comes to asking "why is the performance different between two different installations". Fundamentally, there is very little different between late OpenX Source releases and current 3.0.x Revive Adserver releases - it's all been rebranding and fixing a lot of bugs; certainly nothing has changed to fundamentally change the performance of the application, so I would look hard at your systems setup -- which is unfortunately well beyond the scope of support we're able to help out with here.
  10. We're also happy to accept pull requests in GitHub for translation improvements or new languages, if that's something you're interested in taking part in!
  11. Well, that's what you think you did, but the Revive log is saying something different - or perhaps you repeated the upgrade by accident - or someone else accessing the site did too, and if you look further back in the log file, you will see a different set of messages?
  12. I can answer 1 & 2 - which is Yes, and Yes. 2a isn't really a question, but Revive can support any size banner at all, really, so this is not an issue. 2b isn't something I really know much about - I know there is a Wordpress plugin, but we have not really looked at bringing this over from OpenX to Revive at this stage. But that doesn't matter - you can do all of the above even without a Wordpress plugin.
  13. Targeting channels are just a way of setting up a pre-defined set of target(s) that you can use over and over when doing delivery targeting for banners. However, it certainly sounds like this is a good idea for you - you want to set up a channel for each of the "topics" that you want to target. However, exactly how you define a "topic" depends on how you think you can define where the content is. If each topic lives in a section of your site that is well defined by the URL, then "Site - Page URL" might be a good choice. If you can modify your site's generated content, so that you dynamically insert a variable into the page depending on what the topic is, then the "Site - Variable" option could be what you need. Does that help?
  14. It goes through a process of looking for various options - so as you can see, it says that PAN (phpAdsNew) was not detected, then that MMM was not detected, etc. until it eventually says that it could find "OpenX" 3.0.2, which it "upgraded". However you did it, you must have upgraded the database to the new version at some point, and have then repeated the upgrade!
  15. I'm pretty sure that it will keep all stats, forever.
  16. There's a chance, but it's probably low down the list at the moment for me and the team. You're welcome to put the idea into GitHub, though - or submit a PR for the feature, which would be even better ;-)
  17. Fair enough - I agree that I don't think Revive supports this. Want to log a feature request in GitHub?
  18. Maybe try re-generating the invocation code for a zone, and try testing that to see if clicks get registered?
  19. If it's a brand new Revive Adserver installation, it may take some time before it "learns" how many impressions your zones get, and can accurately set how many impressions to try to allocate to banners. I seem to remember back in the day, we used to recommend that new zones run for a couple of weeks with just remnant inventory before scheduling other types. Give it a try and see if that helps?
  20. If you're missing any of the default plugins for any reason, you can install them by, as an administrator using, going to the "Plugins" tab. Then, click on the "Browse" button in the "Install new plugin" section. Browse through to your Revive Adserver installation root directory, and then look in the "etc/plugins" directory. You can find the .zip files of all the default plugins shipped with Revive Adserver there. Pick the one you want to install, and click the "Install" button.
  21. Great! Could you please also do me a favour, and create a bug in GitHub to note that there's no option for that delivery file? Then we can make sure it gets added to the UI at some point.
  22. I think others have reported that to get the upgrade to proceed, simply create an empty file in the location(s) that the upgrade wizard is requesting. I would think that, at best, this file then gets replaced when the plugin is upgraded to a later version (I am pretty sure all plugins have now been updated to some degree in Revive Adserver), or, at worst, the empty file you create gets copied into the new Revive Adserver installation, but as an empty file, it can't introduce any new exploit and won't add any missing features that you're not already missing as a result of the file being absent. Please note, however, that as you've mentioned old exploits from OpenX, upgrading to Revive can't deal with your server if you've been compromised - you still need to manually clean up all compromised data in your database, remove any users that are not ones that should be there and ideally change all your passwords manually.
  23. As an administrator, go to "Configuration > Global Settings > Geotargeting Settings". Here you can configure various options for letting Revive Adserver do geotargeting, which is what you're talking about for option #1!
  • Create New...