Jump to content

Erik Geurts

Administrators
  • Posts

    752
  • Joined

Everything posted by Erik Geurts

  1. See https://www.revive-adserver.com/blog/translations-for-revive-adserver/
  2. I didn't say that. Those might actually be the active tables of your ad server. If you started years ago with OpenX Source (prefix ox_) and over time upgraded to Revive Adserver, the table names will still have ox_ as their prefix. What you can delete are the ox_z_ tables and the rv_z_ tables (if any of those exist).
  3. Have a look in your webserver's error log, the cause should be listed there.
  4. Anything with those random name with _z_ in them are backup tables. What I don't understand is how you can have both rv_ and ox_ tables in your database. The most likely explanation is that you used OpenX Source and at some point did a fresh install of Revive Adserver in the same database.
  5. Those are backup tables from earlier upgrades. You can safely delete them.
  6. There is no reason why that widget wouldn't work for you as an administrator. However, in my personal opinion, that entire dashboard isn't all that useful anyway, and I always disable it right after installation. To disable it, log in and switch to Working as Administrator. Then go to "Configuration" and next "Global Settings - User interface setting". Scroll to the bottom of that page and uncheck the "Enable Dashboard" checkbox: Afterwards, don't forget to save the changes.
  7. Looks like instead of doing a proper upgrade, you just uploaded the new software files on top of the existing 3.2.0 files. The correct upgrade procedure can be found here: https://www.revive-adserver.com/support/upgrading/
  8. We do not use the e-mail address you mentioned. There should not be a username 'maintenance' either, so it seems your installations was hacked.
  9. OK, so the issue is not that the stats are not showing (topic title) but that there is a problem during the upgrade process. Let's focus on that. If you see that the plugins aren't getting migrated during the upgrade, there is no point in continuing, that issue needs to be resolved first. Unfortunately, it's impossible to say anything about the cause without access to the specific server. Note: do not post your server details in public.
  10. You started the topic by saying it didn't work after an upgrade, and now you say it's a clean install. Forgive me, but that's all very confusing. If you do an upgrade according to the upgrade instructions, all plugins will be migrated along and there shouldn't be any issue with statistics. Instructions can be found here: https://www.revive-adserver.com/support/upgrading/ That process works, I have personally done it over 2,500 times by now.
  11. Sounds like an overly complicated setup to me. Just pass it into AdX once and ensure that their fill rate (they call it coverage) is 100% or as close as possible to it. Then you do not need a passback scheme.
  12. Well, there you have a problem. AdX will only take a URL of an HTML page as a backup ad. You could create such a web page, and send the URL to whoever managers that AdX for you. I really don't understand though, how the second AdX account could possibly fill an impression that the first one could not...
  13. Once you pass off an impression to AdX (or any other third party system, for that matter), it's gone. The only exception is when you use AdX's feature to define a backup ad. But in short, what you're trying to achieve is not possible without a whole lot more work.
  14. Very strange, but not something we can fix remotely.
  15. So it's just a local issue with your own PC, nothing with the server. I suggest checking your browser. Does it accept cookies? Can you try with another browser?
  16. No, I doubt an upgrade will fix anything, if only, it'll make things worse. Have you contacted your hosting provider, asking them to check the database?
  17. How would a power outage on your computer affect the server? Are your ads still delivering? If there was a power outage on the server, then yes, this can have affected the database. I would recommend contacting your hosting provider and asking them to check things for you.
  18. What sort of problem did you have earlier with your computer/browser? Can you post a screenshot where it says it is not accepting your login? Can you log in from another computer?
  19. Both are symptoms caused by the same root cause. I wouldn't recommend any code tweaking, just fix the permissions issues. Unfortunately, we can't see what's going on as outsiders (and I do not recommend posting your server credentials in public).
  20. I think the permissions error you're seeing is that it's unable to create/update that very file. Permissions on the var folder and every file and folder in it might be better at 777.
  21. If you enter the macros manually in an HTML banner, you should set the "Alter HTML to enable click tracking" to "Do not alter" otherwise you run the risk that Revive Adserver will insert the macros twice (once manual, once automatic). You will not need to generate zone invocation code with third party click tracking, that's only for when your zone will go into someone else's ad server. Just use the default async invocation code.
  22. That's an ordinary Apache (or some other webserver) log file, nothing to do with Revive Adserver itself. I suggest you contact your hosting provider. I just checked the link to https://www.aquaplatform.com/revive-adserver-hosting/ and it works just fine. What happens when you click it (in my signature)?
  23. I don't recall ever seeing dserver-access.log being part of Revive Adserver, so it's probably not the right place to ask this question here.
  24. There are 2 ways to approach this: Before the start of the installation wizard, make sure you have already created a database, and a database user with password and with "all privilege" to that database. During the installation wizard, enter the database name and user credentials, and the installation will just just that database. During the installation wizard, enter the name of a database that should be created as new, and the username and password of a MySQL user with sufficient privileges to create a new database. Personally I prefer the first method, because it makes it easier to spot problems.
  25. Yes, there is an API, and there is also a REST API (see my signature). Disclaimer: that Revive Adserver REST API is a third party paid product being marketed by my company.
×
×
  • Create New...