Jump to content

andrewatfornax

Administrators
  • Content Count

    1,968
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. But eventually, as I progress through updating the documentation, I'd expect plugin development documentation to end up somewhere under: http://documentation.revive-adserver.com/display/DOCS/Developer+Guide
  2. Unfortunately not. We can't tell from the above post if the 404 is from your adserver (in which case, something has gone wrong with your server - you will need to investigate yourself or speak to your admin team), or if it's from the banner's target server (in which case, something has gone wrong with the site the banner is linking to - you will need to speak to the administrator of that server). HTH,
  3. Hi omenicus, Alas, that link is not for anything associated directly with the Revive Adserver team (and isn't loading for me anyway), so I'm afraid we really can't comment on what it is. Best bet would be to contact the appropriate people for that link. Cheers, Andrew
  4. Please note also, improved documentation on delivery via SSL vs. not via SSL here: http://documentation.revive-adserver.com/display/DOCS/Tag+settings
  5. Sure, PM details, and I will take a look. NB. I'm travelling with the day job next week, so may be a couple of weeks before I can take a proper look into it, sorry.
  6. I don't believe that as yet, Revive Adserver has changed any re: reporting statistics for banners from what was available in OpenX.
  7. Most likely explanation: Your OpenX installation is on faster hardware than your Revive Adserver installation. As a result, your OpenX served banners appear quickly, and the impressions are therefore more likely to be logged; your Revive Adserver banners are served more slowly, and users are more likely to navigate away from the page before they have loaded, and so there are fewer impressions logged.
  8. You probably can't - if the browser (or a browser plugin) blocks it, well, then it's blocked. I suspect there's really not much we can do about that.
  9. Thanks for the feedback! I don't think there is any specific need for Revive Adserver to have any given number of CPU cores - rather, it's more likely that this is simply the level of CPU power your specific installation requires to cope with the load you have. Did you change to asynchronous tags at all? One thought might be that if you did, then Revive Adserver is now trying to do more work in parallel than before (rather than doing all ad serving serially), and so this may have affected the level of performance you need for your specific installation... Hope that helps.
  10. I've never used a cPanel based host before, so your mileage may vary on the results here, but: https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=change%20mysql%20password%20with%20cpanel
  11. The following post may also be of help: http://www.openxconsultant.com/blog/2011/10/what-to-do-when-you-suspect-your-openx-system-has-been-hacked/
  12. Yeah, it's been a while since I've looked at this - and have not had a chance to review yet as I work through updating the user documentation - but my expectation is that you're right - when you create a user account, Revive Adserver should email the new user with a link for them to create their own password.
  13. Thanks for the feedback - and good to know that it's down to the network speed, rather than something wrong with the asynchronous tag. A thought - would you be able to mix the two types? Use the normal SPC tag on pages where users are likely to navigate quickly, but asynchronous on pages that are more content focused and users may stick around longer?
  14. This is a complex (and incompletely described, as I don't know what banner/campaign to zone links exist) scenario. Can you please try a more simple scenario? Campaign A - One banner; Campaign limited to 5 views. Campaign B - One banner, no capping. One zone. Both campaigns linked to the zone. I've tested this with both Asynchronous and JS tags, and in both cases, I see a mix of the campaign A and campaign B banners in the zone until I've seen the campaign A banner 5 times, and then I only see the campaign B banner. Can you get it to show the campaign A banner more than 5 times with this setup using the Asynch tag?
  15. 1. Yes, you can use gif banners. 2. Yes, you can use wget for scheduled maintenance on Windows. 3. You will need to establish trust over time with your advertisers that they are getting what they paid for, based on transparency and communication. You will need to see your server's web logs, to understand why access was denied - unfortunately, that's not something we can help with based on the information you've provided here.
  16. Banner selection is random. So - all 10 banners in the same zone, and just the one zone on the page, 10 time? That should display banners randomly.
  17. I would expect that with iFrame, you're not going to be able to do a responsive banner. I'd probably be thinking you need to create the banner as an HTML banner with all the required code for the banner to be responsive, and deliver it using something other than an iFrame tag.
  18. Sorry to hear the plugin Erik mentions is out of your price range. It would be great if we could extend core Revive Adserver functionality to more cases, but as an open source project, there's only so much we can do without community support. We're working really hard on documentation right now, and as part of that, I'd like to get more developer documentation up - perhaps one day that will help the community to bring features like (or others) this into core. Cheers, Andrew
  19. There are a number of reasons - and what I really need to do is create a troubleshooting guide for people to help them walk through understanding what the cause is. I've added this to the documentation todo list...
  20. Hi David & Richard, Sorry the documentation is not yet in place around this area - I'm working hard to improve the documentation little by little, and will put this on my list to look at ASAP. Cheers, Andrew
  21. Well, could just be a flat out bug that no one noticed in beta testing :-) However, I've just tested delivery capping at the campaign and the banner level, and they seem to work just fine for both JS tags and Async tags. Maybe you could give some more details or reproduce steps, please?
  22. I'd start by taking a look at the underlying system - perhaps a database corruption issue, disk full, recently applied server updates, or something like that? Sounds very strange for even a completely clean install in a brand new database to have that kind of an issue. Certainly not something I have seen, which makes me suspect an environmental change on the host. HTH
  23. Sorry, no - OpenX Source, while something we took and moved forward into Revive Adserver, is not something we support; Revive Adserver has nearly 2 years of work done to take it forward from the old OpenX Source days now. I'd suggest either going back to trying a test upgrade on a test bed system and see if you can get that to work, or, perhaps start with a smaller site and do a fresh install or Revive and just manually move some of the traffic over to see if that solves the issue at least, before you commit time and effort to trying to move everything... HTH.
  24. Thanks so much for the feedback gabrielt! It's great to see your graph above showing that you've probably taken 30-60% off of your page load time by moving to the asynchronous tag type, which is obviously a super result, and very encouraging to see that in principle, it does what its supposed to do! However, the drop off in banner impressions is of course, worrying. What does pop into my head though, as an immediate thought is that after the move, the page load time has come down to around 5 seconds. However, that is, I assume, the load time for the page without ads, as the ads will then start to load up after the page is done. Assuming nothing else has changed performance-wise, I would guess this means that the ads are then taking something like another 5 to 10 seconds to complete loading up? If that's the case, there's now a 5 to 10 second window for your site users to move on to another page, and interrupt the loading (and therefore impression logging) of the ads. How does your average time on page look? Might this kind of behaviour explain the drop off in impressions? I think this is worth looking into - although of course, we're totally open to the fact that perhaps it's something in the tag that isn't working as we expect re: logging impressions...
×
×
  • Create New...