Jump to content

andrewatfornax

Administrators
  • Content Count

    1,882
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. I would check the location & permissions for your image storage folder, as you're uploading to the webserver.
  2. Quite possibly! First thing I would check is - do the Adsense banners appear in the Revive UI when you preview the banners? If that is okay, take a look at the zone probability page - do the banners have a non-zero probability? Is the sum of all probabilities for the zone 100%, or is it less (i.e. are you just happening to see blank impressions because you're only using a small part of your inventory by not including a remnant campaign?) HTH.
  3. Back in the day, when Revive Adserver was OpenX Source (around about version 2.6 I think), conversion tracking was done server side. The problem is that the storage requirements for all the data just got too large when you had more than a trivially sized installation. So, everything was moved to be cookie based. I honestly can't see us changing things to work in a non-cookie way. But I suspect you probably could make calls to Revive as you have suggested - or, if all else fails, just write the appropriate data to the database!
  4. Hi, As above, sorry, but we need more information. Post some screenshots of the campaign and banner details for those banners that are not delivering? Also, take a look at the probability % values for those banners in the relevant zone(s) and tell us what you see. Thanks.
  5. Maybe post some screenshots of the campaign and banner details for those banners that are not delivering? Also, take a look at the probability % values for those banners in the relevant zone(s).
  6. See also the documentation: http://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Documentation
  7. Check your PHP settings - Revive Adserver tries to suppress these warnings, but it can't do so if your PHP config won't allow it.
  8. Sounds like a bug to me - can you report in GitHub, if not already reported, and reference the details & this thread, please?
  9. Can you please provide a lot more information? Like for example - what tag type you are using? Where we can see the generated invocation tag in raw form? Where we can see the tag working on a non-SSL site, and not working on an SSL enabled site? Thanks.
  10. See some of the many other posts on the same topic! However, in short - this was resolved in 3.0.4 (and only affected users running automatic maintenance).
  11. Can you provide a link to more information, please?
  12. I haven't done it yet - but when I do, these will all be explained somewhere around this page in the documentation: http://documentation.revive-adserver.com/display/DOCS/Invocation+code
  13. Revive Adserver support pop-unders. Create a zone of type "popup" and you are away! http://documentation.revive-adserver.com/display/DOCS/Creating+a+zone
  14. Hi! When you say "sidebar widget", it makes me think that you're pasting the invocation code into the UI of some kind of CMS (e.g. Wordpress), inside a widget for displaying things. Sometimes, those kind of CMS tools try to be nice and prevent you from putting HTML code in them, and escape all the code, so that it doesn't display correctly when you view the page. Have you checked the source of the page you're viewing to make sure the Revive Adserver invocation tag is appearing as it should?
  15. Check your spam filter, perhaps, or your mail server logs? Revive really does use mail() to send mail. Of course, perhaps it's not sending mail at all to the mail server, but then, your mail server logs should be able to confirm that.
  16. @bmanke I never heard back - please let me know if it works for you, so we can resolve this topic if it helps?
  17. No; the Google Adsense (or other network) targeting will not be affected. Google (and just about every other network) uses JavaScript-based tags. While Revive Adserver can deliver these (and add/modify as required to ensure that it can track impressions & clicks), in the end, the JavaScript will be executed by the user's web browser, on their computer; the fact that you are using Revive to deliver the JS code in the first place has no effect at all on what the tag does; as a result, any geo or other form or targeting or logic that the ad network implements in their system is unaffected.
  18. Most likely this was due to the recursive nature of the above commands, rather than the absolute vs. relative path. Permissions actually need to be set appropriately for all files/sub directories; for a clean install, it's not an issue, as the folders are empty. But on migration, that may not be the case, depending on how the files were move and what else may be changing.
  19. Banner weights operate in exactly the same way as campaign weights, which are described in the documentation: http://documentation.revive-adserver.com/display/DOCS/Creating+a+campaign Having just re-created your example above (having three banners with weight 1, and one with weight 2), I get exactly what I would expect - the weight 1 banners have probability of 1/5 (i.e. 20%) and the weight 2 banners has probability of 2/5 (i.e. 40%). I wonder if the above updated when the maintenance script ran? Or did it stay like this?
  20. Good news! The Revive Adserver documentation explains: http://documentation.revive-adserver.com/display/DOCS/Email
  21. Normally, they should be. What version of Revive Adserver was this? Was it an upgrade from OpenX? Direct, or were there versions of Revive Adserver in between?
  22. Hi Paul, What version of Revive Adserver are you running? What version of OpenX did you upgrade from? Did you go directly between those two versions, or have there been versions of Revive Adserver in between? Thanks.
  23. See above re: my comments about the development team "not caring". Of course we care - we would not do what we do (for free) if we didn't care. (Either that, or we're all mad!). However, we do get a lot of new bug reports on GitHub, and sometimes, they just sound like requests for support. We could do support through GitHub, but if that's the case, then we're paying a lot of money (at our own expense, for free, for no reward other than personal satisfaction) for this forum! So, we'd rather close a few cases and ask people to come here first if it's not a clear cut, definitely a bug type of report. If you're able to make sure bug reports are clear cut, and include all the detail required to prove it's a bug (and even better, send a pull request with it), then this will hugely improve the Revive Adserver community for everyone, as well as making the development team more able to correctly and swiftly respond to bugs. In the mean time, when we get it wrong, and close something that actually is a bug because we think it's a support case - please accept our apologies. We're not perfect - just a few guys who love Revive Adserver, and want to do the best we can in our spare time to make it better. Cheers, Andrew
×
×
  • Create New...