Jump to content

andrewatfornax

Administrators
  • Content Count

    1,884
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. If you want to set up scheduled maintenance, you need to pass in the correct domain name as a parameter to the script. Please see the documentation: http://documentation.revive-adserver.com/display/DOCS/Running+Maintenance
  2. In general, adding ads is the same no matter what device the user is viewing it on. The documentation at http://documentation.revive-adserver.com/display/DOCS/User+Guide is still under development, but there should be enough there now if you read it through to understand how to add banners and get them displaying.
  3. When you generate the zone invocation tag, those tag types that support it have an option called "Don't show a banner from the same campaign again on the same page". That does exactly what it says it does, and does exactly what you're asking for -- it stops another banner from the same campaign showing up again on the same page.
  4. When you access a page on your webserver from the iPhone you are testing with, have you inspected the useragent details in your webserver log file (you may need to increase the logging level) to see what useragent is actually being passed through to Revive Adserver?
  5. Yes! Revive Adserver can do a number of things with multiple domains: 1. You can have multiple, but completely independent installations running out of one code base (but with different databases); or more commonly (and usefully) 2. You can have one installation running, but deliver the UI and/or banners on different domains.
  6. Nothing official yet. I'm working on documentation when I can, and adding pages as often as I can. There's usually something new every week or so.
  7. Yes, but don't. There are a number of serious consequences from doing that, and generally, you probably don't want them. (I will write that up one day in the documentation!) http://documentation.revive-adserver.com/display/DOCS/Running+Maintenance
  8. Correct - also, remnant campaigns are there so that every possible impression has something delivered and logged, because Revive Adserver doesn't log "blank" impressions. EDIT: Revive Adserver now DOES count blank impressions, so this will have improved things as well! Sometimes, Revive Adserver can take a while (e.g. a couple of weeks) to learn how much inventory you have; but if you have wildly changing inventory, it may not do a great job (i.e. predicting the future is hard). So, it does its best, but it won't ever be perfect.
  9. If "www.example.com" if your "primary" domain, your config file "www.example.com.conf.php" should be the one with all the details in it. However, there should also be one called "default.comf.php" that has contents something like: ;<?php exit; ?> ;*** DO NOT REMOVE THE LINE ABOVE *** realConfig="www.example.com" Do you have one of these?
  10. There's a reason why Revive Adserver has an email/newsletter zone type - and why that zone type has a very specific, no-javascript, no cookies type of zone tag; Javascript generally won't be run by email clients; that's why your banner code isn't working. Set up an email/newsletter zone, and use the invocation code from that in your emails.
  11. What do your webserver logs tell you? Hopefully, they will indicate why permission is denied.
  12. Can you describe the problem more completely, please? I routinely develop Revive Adserver using a root-based installation on a sub-domain, and never have any issues performing an upgrade, so I find the setup you've described to be an unlikely cause of any issues.
  13. Looks like a file is missing. Is it there? Or has it got lost when you unpacked or uploaded the files?
  14. Kinda looks like you're doing interesting things with your server setup - multi domains, perhaps - or maybe rather restrictive web server setup / PHP security mods?
  15. http://documentation.revive-adserver.com/display/DOCS/Email
  16. Turn off your ad blocking plugin in your browser.
  17. You copied over all of the *.conf.php files, right - not just the default one?
  18. Okay, now we're down to checking your web server log, unfortunately. Use something like Firebug to track the execution of banner invocation and see that there are calls being made to Revive Adserver to log the banner delivery. Try calling the URL manually, and watch your web server logs to see if it tells you anything. You may need to increase the logging level in your webserver and/or PHP.
  19. I think ultimately, it would be great if Revive Adserver can have support for letting website owners & advertisers to effectively self-service (including important features like moderation of new campaigns, banners & built in payment processing) -- but that is a massive job, and is at best a long term aspiration for Revive Adserver right at the current time. It's certainly something I will keep in mind, though.
  20. Can you please create a Git issue for this? Seems like something we would be able to do.
  21. Either you've made a mistake, and haven't copied the correct configuration file(s) over to the correct location, or your web server cannot read the configuration file(s) in the new location. Check that they really are there, and the permissions are correct.
  22. I don't think so. (I assume you mean display something like how often a user sees any given banner?)
  23. Revoke? Or "invoke"? Do you mean you're trying to have one banner display on one URL, and one display on the other URL?
  24. You can read about the three different types of campaigns in Revive Adserver here: http://documentation.revive-adserver.com/display/DOCS/Creating+a+campaign
×
×
  • Create New...