Jump to content

andrewatfornax

Approved members
  • Posts

    2007
  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. Although this is not exactly the same issue, it may be related to this: http://documentation.revive-adserver.com/pages/viewpage.action?pageId=5931093 Is the performance of your new Revive Adserver host up to the job, or is it too slow, and although it's still recording things, it's taking just that little bit longer, and so users are not waiting for the Google Adsense content to load?
  2. Hi @Sukh, It's the same thing, but you just give the invocation tags to your clients, to put on their websites.
  3. There's actually a .gitignore file in GitHub... https://github.com/revive-adserver/revive-adserver/blob/master/.gitignore
  4. Hi @Bernard, Can you do what you want with a Contract Campaign - that lets you say what the pricing model is, and then limit to a given number of impressions, clicks and/or conversions as appropriate...
  5. Simple - if we're looking into it, you'll see updates on the ticket! This is an open source project, with no funding - so everything we do is completely on a volunteer basis. Unfortunately, that means that not everyone is happy that we don't fix all their issues right away - but we do what we can.
  6. That depends on what the permissions are! If the permissions are okay, and the web server user can write to the files that Revive Adserver needs to be able to write to, then it won't ask you to update the permissions. Of course, that may mean your write permissions are more permissive than you really would like - so it's worth checking that you don't have *everything* writable. But glad to hear it's working now.
  7. Anything in the log files in Revive Adserver's var/ directory that indicate an issue with the DB?
  8. http://documentation.revive-adserver.com/pages/viewpage.action?pageId=5931093
  9. All the details of upgrades performed are in the upgrade_action table in the database. I suppose it would be safe to delete the artefacts, and then delete the relevant row(s) from the DB. I doubt there's really much need to do this, though - it's used in trying to perform rollbacks if upgrades fail, and I doubt it takes up much space?
  10. The only zone tag that's native to Revive Adserver that can refresh the banner without the page reloading is an iFrame tag: http://documentation.revive-adserver.com/display/DOCS/Tag+settings As you say, there may be plugins around for Revive Adserver that will add this capability, but I can't comment on the utility of them - caveat emptor!
  11. Right, so, you want your banner to be responsive - to scale the size of the content down (or up, possibly) depending on the user's screen dimensions - or perhaps to select from a range of different zone sizes, depending on screen dimensions. Revive Adserver doesn't have anything built in for this at the moment. Your choices are: * Set up a zone for each size banner you want to display, and write your own code to decide which zone tag to include, depending on display size; or * Set up a *x* sized zone, and use an HTML banner that's responsive of its own right.
  12. I suspect you've missed a step in the upgrade process - if you follow it carefully, it does work!
  13. I suspect this was an issue with database vs. version, possibly fixed later in 3.1.0? https://github.com/revive-adserver/revive-adserver/issues/68 Is this still an issue for you?
  14. Well, if the database has been changed manually, then there's probably no easy way to do this. Any database export you make is going to include the changes, unless you revert those changes to the DB first. Unless the changes are only to indexes, in which case if you dump the data out with out indexes, you may be in luck?
  15. http://documentation.revive-adserver.com/display/DOCS/Invocation+code%3A+Zone+level
  16. Sounds to me like the geotargeting isn't working at all. I do need to work through getting some documentation up on Geotargeting... Have you had any luck since this post?
  17. 1. Yes. 2. Yes. 3. Yes - it's not ideal, but there is a local mode tag, which is PHP, and provided your site is PHP based, will do just that.
  18. That's a webserver permission error, which is preventing Revive Adserver from executing. Something that I'm afraid you will need to sort out using your webserver documentation, and not something we can really help you with.
  19. Ah. No. What you want to do is put any additional MaxMind files somewhere on disk that Revive Adserver will have access to, and then, as an administrative user, go to the Plugins tab, then find the MaxMind GeoIP Plugin. Click on its Details link, then the Settings link. Here, you can define where all the different files are located that are supported for different targeting types.
  20. Sounds good @horseguards! This might be something we'll consider in the near future - if the community really is interested in getting Revive Adserver to move forward faster, then hopefully, you're right, and people would be willing to chip in!
  21. Hi @horseguards, Alas, I don't think you can. There's no "recurring" campaign type in Revive, so it is something that you'd have to set up manually, once for each month.
  22. Hi @Roberto Pasini, No need to be perplexed! As Erik mentions above, Revive Adserver will work with PHP7, just using the mysql extension via PECL. It would be great to be able to move to pdo or mysqli, as mentioned by others above - but we're currently without any kind of sponsorship or revenue - the core team supports Revive Adserver as best we can in our spare time, around our day jobs. So, it's not surprising at all (to me) that this hasn't been done yet - along with all of the many other things we haven't done (yet). We do our best!
  23. No - you can configure that yourself with a cronjob, if you want to, but that's all manual scripting. I think we only ship the free country database, and we do try to update that to the latest version with each release - but for things like regional level targeting, you'll need to go and get (and install, and update) the MaxMind (version 1) regional database yourself.
  24. I suspect this is due to your webserver not allowing the JS code from Revive Adserver to be executed? Have a look at your web server's CORS setup, and see if it needs to allow access to your Revive Adserver domain, which I presume is different to your website?
  25. I think what I'd be trying to do is see if this is in any way repeatable (even if only occasionally), and then try to repeat it with Firefox's Firebug turned on, so you can see what resources are loaded over the network. That may provide a hint as to what's being called, and perhaps something will be more obvious about a call that's being re-directed by your webserver? I would have a feeling that there's a call to Revive Adserver somewhere that your web server is intercepting, and not allowing, and re-directing to your home page, perhaps?
×
×
  • Create New...