Jump to content

andrewatfornax

Approved members
  • Posts

    2007
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. Update, with a partially happy outcome. Invision basically brushed us off, and said, well, you should have noticed the problem right away, and used a backup to restore. Unfortunately, we didn't notice, and the backups had already been rotated by the time we did, so that's not an option. However, @Matteo Beccati very kindly figured out how to fix all the posts where the links were full URLs, and this has been done - which is the happy part. The unhappy part is that for any post with a link that isn't a full URL, we can't fix it, and it will stay broken unless anyone can figure out where it should have linked to, and then update the post.
  2. Hi @GAEL, What error is showing up in your web server logs when this happens?
  3. Hi @Pat, Sorry to hear that you're having issues. Revive Adserver is an open source project, and there is a lot of code that is old. However, that doesn't mean that it doesn't work - it just means that your PHP installation needs to be appropriately configured and set up to allow Revive Adserver to let PHP know that it has code like this, and to not display these errors. Then things work just fine, and lots of people are successfully running Revive Adserver commercially. HTH.
  4. Hi @Andrew S, 1. Well, disk I/O is often just as important as the number of cores and the amount of RAM. The only way to really know if you have enough is to have monitoring in place on your utilisation of CPUs & RAM, and then look at things like SWAP and disk I/O, and see if there are any bottlenecks. Are you using a PHP opcode cache? 2. No, I don't really think that there will be much difference in the required "power" between these tag types. 3. It's definitely worth using a CDN for the banner creatives, if you have access to do this. It probably won't affect the power required to deliver things, as it's not really something that takes up much "power", but it will result in better performance for the users (unless you've moved to HTTP/2....)
  5. Hi @ChaoFan, Check that you haven't blocked cookies, and that you're not running anything in the browser that may interfer with loading of the site (e.g. ad blockers). You can find details on how to reset passwords in our documentation: http://documentation.revive-adserver.com/display/DOCS/Resetting+User+Passwords
  6. Hi @Velislav, Have you see our FAQ on this topic? http://www.revive-adserver.com/faq/troubleshooting-banner-delivery/
  7. Hi Blinky, Thank you for wanting to help out with translations! Before you get carried away in GitHub, though, please see our page (which is in our FAQ) on how to help out with translations: http://www.revive-adserver.com/blog/translations-for-revive-adserver/ We have a separate system for submitting improvements to translations - we won't accept updates via GitHub! Thanks, Andrew
  8. I would try setting Campaign 1 to have weight 1, and Campaign 2 to have weight 10. This way, 1/11 of all banners will be from Campaign 1 (hence, 1/11 of all banners is the one banner there), and 10/11 of all banners will be from Campaign 2 (and, assuming all banners in Campaign 2 are all weight 1, then each banner in Campaign 2 will also end up displaying 1/11 of the time). However - this is a laborious process, and impossible to manage when you start to get a large number of banners across multiple campaigns and zones. So, I would really ask myself - if I *need* this kind of totally equal distribution of between these 11 banners, are these 11 banners *really* from two different campaigns, with different delivery targets - or are these 11 banners actually part of the *one* campaign?
  9. Thanks for the info! I've raised a ticket: https://github.com/revive-adserver/revive-adserver/issues/639
  10. Thank you for the info! I've raised a ticket: https://github.com/revive-adserver/revive-adserver/issues/639
  11. Thanks Ian - and apologies all for the SPAM. Things were really good, but then Invision released a new version of their forum, we upgraded, and things have never been quite as good ever since.
  12. Hmmm, this is a third, but more complex need that I wasn't originally thinking of! The issue here is that Revive Adserver only has the concept of one set of URLs to use, so, to make something like this work, you'd have to have one install set up, with two completely different sets of URLs for the UI and delivery, and then make sure that you log into the correct UI to generate invocation tags. But, in theory, I think this would work: http://documentation.revive-adserver.com/display/DOCS/Managing+Configuration+Files Please let me know if not, I may have mis-remembered the ordering of the config file entries...
  13. The iFrame invocation tag type has an option to refresh the contents after a given number of seconds. See: http://documentation.revive-adserver.com/display/DOCS/Tag+settings
  14. Hi Andrew, I know you say that Revive Adserver is installed on a clean, fast VPS, but please don't underestimate how much power you really do need to do fast banner delivery. When I see you say that you've tried a remnant campaign (presumably with no limitations on delivery at all), then if you're still seeing (far) fewer banner impressions than page impressions, then really, the most likely reasons are the performance of the Revive Adserver being low, and users not waiting for the banner to load before they navigate away. I know this is not exactly the issue you are talking about (I do plan to write a troubleshooting guide about what you're talking about at some stage), but have you see in the documentation, which is similar? http://documentation.revive-adserver.com/display/DOCS/Requests+Higher+than+Impressions
  15. Hi Richard, I'm still actively chasing Invision for a solution. Apologies for the delay - but they are not being especially helpful, which is disappointing for something we pay to have... Cheers, Andrew
  16. From memory, the issue was that before the upgrade, the database wasn't in a good state - there had been some manual changes made to data etc. So, after the upgrade, things were not in a state that would allow a newer Revive Adserver to work. I think I had to trawl through the data, and figure out what the bad records were - perhaps relating to user accounts? - and fix these.
  17. Is Revive Adserver tracking impressions on the banner? I am just wondering if it the banner type is interfering with Revive Adserver, and it's failing to record the fact the impression has happened, which is why it's not capping delivery. Could you set up a plan HTML page with just a single zone on it, and that zone just containing the capped banner? That would let us see the banner being delivered, and inspect what cookies are being set etc.
  18. Rather than having a full page of stuff, would you mind creating a simple, plain HTML page, and put both the normal JS tag, and the async tag on it, side by side? Then we can compare what's going on! Thanks.
  19. The issue is, I think, that Revive Adserver assumes you won't do that, by (at the very least), having a default house banner to display, if there's nothing else available. However, this might work if you set up your zone as a *x* size, rather than a fixed size - although, that would be at the expense of not having the zone's dimensions reserved at the time the invocation tag is processed and rendered.
  20. What tag type are you using to display the banners? Have you enabled the option to allow display on first view, but then have cookies disabled on the browser? Finally, I think you only want one of the total vs. per session values set. It doesn't make sense to say only ever display once AND also display once per session.
  21. Yes, of course - Revive Adserver has a range of tag types, most of which do not require code to be added to the head section of the page.
  22. What happens if you drop back to just the "iPhone" one, so that there's not an OR statement in the limitations? And I assume there are absolutely no other limitations or caps being applied? And other banners without any limitations display okay?
  23. Have you tried creating a *x* zone (i.e. one that has no fixed size), and then ensuring that your HTML5 creative changes its size, depending on the screen size? Otherwise, if you have two specific sizes - one for mobile and one for desktop - why not just have two different zones, and only put the appropriate zone on the site, depending on if you're delivering the mobile or desktop version?
  24. Set up a new zone, and link your targeted banner to that zone. The banner is now the only thing that can display there. Put your zone tag on a non-public page of your website, and go take a look! If the banner shows up for you, then you've targeted it correctly. If not... Either you're not where you think you are (i.e. the IP to location database isn't accurate), or the IP is not coming through to Revive correctly (i.e. you're going via a proxy that makes it look like you're elsewhere), or you've targeted it incorrectly (or something else is broken!).
  25. Agreed, that is a good idea. Would you like to create an issue for this on GitHub, please?
×
×
  • Create New...