Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. Just to check - please post a screengrab of your plugins admin page? That will help us see exactly was is, and isn't, installed. Thanks.
  2. Hi stix_121, The formatting above makes it a little hard to tell what Revive Adserver is saying - would you please be able to post a screengrab of what Revive looks like when it's saying that the unknown version has been detected? Also, can you please have a look in the log files for Revive Adserver - sometimes there is extra information in there that may help explain what's going on. Thanks.
  3. Not sure! Can you please provide some more information about the problem? Your webserver log files are usually a good place to start re: web redirect loops - they can tell you (and us) exactly what web page(s) your browser is getting, and where it's being re-directed to.
  4. Just checking - do you run your Revive Adserver installation over more than one server?
  5. Try this: SELECT * FROM phpads_account_preference_assoc WHERE account_id = 1 AND preference_id = 0; It appears that there is already something in the database using those account ID and preference ID values. If you take note of the value (so that you can restore it again, should you need to do so), and then delete that row, perhaps you will then be able to correctly set the timezone via the UI.
  6. Have a look in the "data_bkt_m" table (with appropriate table name prefix, if present). This is where Revive Adserver stores the counts of impressions as they are recorded during delivery, before the maintenance engine summarises everything up.
  7. For completeness, I think the separate topic suggested is http://forum.revive-adserver.com/topic/92-avast-detecting-trojan-in-the-openx-delivery/
  8. No, memcached is not required. The reason you are getting this warning is because your PHP installation is configured in such a way that it is looking for a memcache.so file in the listed location, but the file is not there. That's something to take up separately in terms of fixing your PHP configuration - but had nothing to do with your issue re: disabled plugins. I'm just noting it for completeness of this thread :-)
  9. There's an option to configure the names of the delivery files in the global administrator settings, under Banner Delivery Settings. Change the filename, and update the settings, and with any luck, that will work.
  10. Works for me in my local setup. Are you definitely using www.myserver.com to access your installation, and not another URL?
  11. Thanks, and I note that the request is in at https://github.com/revive-adserver/revive-adserver/issues/156 too; certainly something we can think about (or would gladly accept a PR for) as an addition to supporting filesystem and memcached.
  12. Well, it would have actually deleted them; but there was a bug at some point where (if you use a different URL for the upgrade to that which is configured) the upgrade of plugins didn't work correctly. That has been fixed now, however, so hopefully others will not have this issue again.
  13. You may need to check a different error log, or increase the level of logging provided by your web server. Or it may be in the PHP error log!
  14. Yep, sounds to me like maintenance is not running, if the stats are in the database, but not in the UI.
  15. Yes. From the error messages, it's clear that your PHP installation is set up to not allow non-static methods to be called statically. Although the code in Revive Adserver tries to tone down your PHP error levels & strictness checking, something in your configuration of PHP won't let it. For now, I don't have time to completely gut and refactor the internals of the application to newer PEAR libraries (which, as you can see from the error, is the cause in the MDB2 library), so you need to update your PHP configuration so that it can work.
  16. You're most welcome - glad to hear the upgrade worked!
  17. Well, we used more than just the Singleton design pattern! However, there really is not any good documentation for developers, nor is there a description of the architecture other than "it evolved, and is evolving". Unless you are willing to commit time to running through the code in a debugger, you're not going to get very far, unfortunately - and it's very. very difficult to customise. But please do give it a shot! We welcome PRs in GitHub.
  18. Yeah, if the page is blank, I would expect to see some kind of error in your webserver log that will help diagnose what's wrong.
  19. We might be able to do something re: donations for hosting costs eg. for the sync server - something for me to look into, anyway. For now though, save up your spare cash ;-)
  20. Erm - don't all the delivery files (not the creatives!) deliberately go to some effort to avoid being cached by browsers, to ensure that on each page load, the script is loaded fully from the server, to ensure correct delivery of the right ad, and correct logging?
  21. At present, beyond the planning that you can see in GitHub, I don't think we have anything concrete. But we are working on some ideas for where we want the ad server to go -- but we also want your input, which is what this part of the forum is all about! Tell us your ideas, and we'll see what we might be able to accommodate...
  22. Correct! Now that it's Revive Adserver, and not OpenX Source, and given that OpenX (the company) have shut down the OpenX Market, there is no point in having a plugin for OpenX Market any more - there's no point. The workflow plugin was related, and has also been removed. You will note that this is mentioned in the release notes: https://github.com/revive-adserver/revive-adserver/blob/v3.0.0/RELEASE_NOTES.txt#L24
  • Create New...