Jump to content

andrewatfornax

Administrators
  • Content Count

    1,898
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. We took over the project a year ago. The plugin framework that exists is exactly how we inherited it - we have not worked on it at all in the last year, as there are simply too many other things that we have been trying to do. As soon as we can, we will absolutely document how to write plugins -- but be aware that even then, there will be lots of things people will want to do with plugins that the framework will not support, so it's not like documentation will automatically make everything be possible to be done as a plugin. For now, our focus is on fixing the bugs we can, adding new features where there seems to be the broadest demand (so that we can help out as many users as we possibly can) and writing user documentation first, then admin documentation, and finally developer documentation. For us, that seems to be the best way we can help out the Revive Adserver community.
  2. 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
  3. I wonder if the image tag might be a better option for you? See some of the details of different tag types at: http://documentation.revive-adserver.com/display/DOCS/Invocation+code
  4. Geotargeting plugins are included by default in Revive Adserver - there's no need to "get" one for this.
  5. It's not because you've defined the targeting channels as a different manager account, or at the website level that isn't relevant to what you're currently looking at?
  6. 644 is suggested because it does what you can see - it locks the configuration file from changes. Which is a more secure way to leave things that always allowing the UI to make changes any time - and you can always update the file permissions when you need to make changes.
  7. Anyone who wants this want to create a feature request in GitHub, please, describing what it should do / why it's required? Thinking we might aim to do this for 3.1.0 if we can. Thanks.
  8. Now a new feature request in GitHub: https://github.com/revive-adserver/revive-adserver/issues/370
  9. See our troubleshooting guide for when you can't see any statistics!
  10. 1. Revive Adserver 3.0.what? 3.0.5, or something older? 2. Are there any differences in PHP version and configuration between the old and new servers? 3. When you transferred the files, did you ensure that ownership & permissions were transferred as well and/or corrected for new user details on the new server?
  11. Good to know it's fixed! For anyone else with a "missing stats" problem, please see the troubleshooting guide on missing stats.
  12. There is no need to do this - it's already supported out of the box. Please see the reply to duplicate post here.
  13. More specifically, if you want to target certain ISPs, the way to do this is with the already included plugin for MaxMind, and to use the MaxMind ISP database. MaxMind offer a free version of most of their databases, but for up to date info, you would probably want to consider their commercial ISP database, as it's not that expensive. As of the Revive Adserver 3.0.x series, make sure you get the GeoIP Legacy version - MaxMind's GeoIP2 is not yet supported.
  14. See also: http://documentation.revive-adserver.com/display/DOCS/No+Statistics
  15. I'd suggest starting at http://documentation.revive-adserver.com/display/DOCS/Advertisers and working your way down until you've to the end of the zones section. That should cover all you need to know about setting things up so you can display some banners on a site.
  16. Easy - set up your Google Adsense tags as HTML banners in a remnant campaign with the lowest priority, and link the campaign/banners to the zone(s). Revive Adserver will deliver your other campaign(s) as required, and only show the Google Adsense banners when not required and/or when your other campaigns have ended.
  17. Hi Marc, 1. If you want to show each banner equally, I would recommend running each banner - probably each in an advertiser specific campaign to allow each advertiser access to stats as you want - with equal weights for all the banners and campaigns. This way, Revive Adserver will set things up so that every banner has an identical probability of being selected in each linked zone. For more information, see: http://documentation.revive-adserver.com/display/DOCS/Creating+a+campaign HOWEVER 2. Things start to get complicated because although you are talking about wanting to show all of the banners an equal number of times, you're then talking about billing customers on a CPC basis, and wanting them to have a minimum spend. If you start running things using the Contract campaign type, and setting that each campaign has a target of 3,334 clicks/month (i.e. $10,000 month / $3 CPC), then Revive Adserver will no longer attempt to display each banner an equal number of times. Instead, it will try to display banners as often as required to, in it's opinion based on past performance of the click-through rate, obtain the required number of clicks. So, if you had one banner that gets a 50% click through rate, Revive Adserver will only try to deliver that banner 6,668 times in a month, while a banner with a 1% click through rate will need to be delivered 333,400 times to obtain the same number of target clicks. 3. Revive Adserver always does the best it can to deliver the impressions at a rate that will ensure that the clicks are spread out evenly over the campaign duration. However, unfortunately, Revive Adserver can't make people click when it wants them to, so there will of course be some variation from perfect delivery. Revive Adserver will adapt its plan of delivery as it goes along to account for peaks/troughs in success. 4. You can set up users & accounts for your customers to log in with, and you can customise the logo. HTH.
  18. Are you absolutely certain that the "php" you are using when you run that command line call is the same PHP that you are calling when you hit Revive Adserver via the web server? It's pretty easy to have more than one installation of PHP on a server. Easiest way to check would be to create a web page with the phpinfo(); call in it, and check that the MySQL client extension is installed and enabled via the web server...
  19. What was the issue? It's always helpful for other users in the community if you can let people know what the issue was, and how you fixed it, so anyone with the same problem can find this page in the future and know what to do... and/or I can add things to the documentation!
  20. Sorry, but no, Revive Adserver doesn't support a "self service" model where users can sign up and either sell or purchase inventory.
  21. Yes! http://documentation.revive-adserver.com/display/DOCS/Banner+Logging+Settings
  22. I totally agree. The main issue we have with the UI is that there's no separation of content and presentation, as the origins stretch all the way back to PHP3 (if you can remember back that far), apart from the one (or two, or maybe three) areas where various developers/companies over time have had a stab of introducing something more MVC-like, all in different ways. I was talking with the other core developers a few weeks ago, and we all would love to take on this job - but honestly, I think it would need me to be able to put a year, full time, into this to really be able to take it on....
  23. It would be possible to create a plugin for Revive Adserver to use MongoDB as a data store for logging. However, this would not by any means be a trivial task.
  24. I can honestly say that we've changed absolutely nothing in the Revive Adserver 3.0.x series of releases from the most recent 2.8.x of OpenX Source. So, there is absolutely no difference in how Revive Adserver predicts zone inventory, prioritises campaigns, and delivers. That said, we know things are not perfect - there are some circumstances where we know under-delivery can happen, and we also have some ideas for how we might be able to make things better. Stay tuned!
×
×
  • Create New...