Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by andrewatfornax

  1. ... and what do the log files say about what maintenance is doing, please? Anything interesting in there? If you look in your data_bkt_m table in your database, is there anything in there? (That's where the raw impressions get logged before the maintenance script counts everything up).
  2. If you'd like to contribute to the translations present, please jump over to GitHub, fork the project, and submit your pull requests with any changes or additions. We'd love to have them!
  3. Just for completeness of this thread, there really should be no need to download the default Revive Adserver plugins from anywhere. They are included as part of the install/upgrade package, and should be installed/upgraded when you install/upgrade Revive. If that's not working, please ensure that you take note of any errors that are displayed when installing/upgrading (it should tell you about all plugins that fail to install/upgrade) and look in the Revive Adserver log files, which will also note this and provide more information, which will help us figure out what's going on. Thanks.
  4. It also looks to me like at some point in the past, you have managed to install OpenX twice into the one database? So, if you look in your database, for example, do you see both a table called "acls" and one called "ox_acls"? (It looks like all the OpenX tables are duplicated, from the above error - each being there with and without an ox_ prefix.) This is likely to cause all kinds of issues and confusion for the upgrade system! If you're able to make sure you have a good clean backup of your database, and then figure out which tables are valid, and remove the invalid ones, that would possibly help with some of the errors above.
  5. If you have already got to a certain point of previously installing (rather than upgrading) Revive Adserver, it may be that the Revive Adserver installation is no longer configured in the default state to allow an upgrade to happen. I would remove your Revive Adserver installation (assuming you have not changed over to using it yet), and start again with a fresh un-zip of the install package, and make sure you copy over your OpenX config files (*.conf.php) from the old OpenX var directory to the new Revive Adserver var directory, before you start. It should then do an upgrade, instead of an install. Don't be confused by the config files in any etc directories! They are for new installations only, so leave them well alone.
  6. Which version of Revive are you running, please?
  7. Any reason why we wouldn't support this Matteo? If not, Denis, you could log the feature request in GitHub for us, please? Thanks!
  8. I have to admit that I'm going from memory here - but does it work if you simply use a comma separated list of emails in the field for the email to send the report(s) to?
  9. Yeah, to the best of my knowledge, this isn't something we support natively in Revive Adserver. But it's an interesting idea - want to log it as a new feature request in GitHub?
  10. Exactly so - companion positioning is the feature you're after here.
  11. 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.
  12. 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.
  13. 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.
  14. Just checking - do you run your Revive Adserver installation over more than one server?
  15. 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.
  16. 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.
  17. For completeness, I think the separate topic suggested is http://forum.revive-adserver.com/topic/92-avast-detecting-trojan-in-the-openx-delivery/
  18. 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 :-)
  19. 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.
  20. Works for me in my local setup. Are you definitely using www.myserver.com to access your installation, and not another URL?
  21. 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.
  22. 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.
  23. 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!
  • Create New...