Erik Geurts
-
Posts
752 -
Joined
Posts posted by Erik Geurts
-
-
It looks to me like the database that was found by the upgrade wizard is tagged as 2.4.6 but the content of that database doesn't match. This is an issue that is probably too hard to solve by means of a forum.
-
This issue you have is listed there:
comparing database netcoupe4 with schema /home/users3/n/netcoupe/www/openads_new-adserver 3.0.2/etc/changes/schema_tables_core_613.xml
index missing from table: acls.bannerid
index missing from table: acls_channel.channelid -
The install.log and/or debug.log files (in the 'var' folder) will contain more information on what the upgrade wizard has found in terms of a discrepancy between the database it found and the database is was expecting to find.
-
If your web server software is displaying 500 errors, the Apache error log is the place to get details. If this doesn't tell you enough, then your hosting provider should be able to provide more information.
-
It is true that statistics update once per hour, but this is not (just) because of distributed statistics.
It is not possible to implement 'real time' statistics, however. Any attempt to do so will result in scalability issues that are virtually impossible to solve.
-
Hello,
Please review your Apache error log, the cause of the 500 error will be listed there.
-
This SDK was (is, actually) for OpenX Enterprise only.
Revive Adserver is the successor for OpenX Source, and there is no SDK for mobile app development.
-
Just continue using the software, just continue visiting these forums. There are many ways to contribute, for example by posting ideas or questions here, or by helping to answer questions that other people might have.
-
You will be notified when you log in as an administrator, the software checks for a new version very night at midnight.
You can also follow our blog at http://www.revive-adserver.com/categories/releases/ where we will post a message every time a new version is released.
-
In my opinion, it is a very bad idea to enable advertisers to add or change banners. It will almost certainly result in unapproved or unwanted advertising on your site(s) if you do not moderate what they add.
-
I agree, the only file that should have this is fl.js, the rest should do their best not to be cached.
We should remember that tools.pingdom.com (even though it's a great tool, and I'm a loyal paying Pingdom customer even), is not always right.
-
It would be great if someone could post a higher resolution or a vector Revive Adserver logo.
Hi Ilya,
Nice to meet you again!
What would you want to use that logo for?
Regards, Erik
-
A complete and correctly executed upgrade to Revive Adserver v3 would have removed these two plugins automatically. Have you seen these instructions?
-
Hi Shay,
Yes, this is actually rather easy to do. You might find this diagram useful: http://www.reviveservers.com/revive-adserver-hosting/revive-adserver-hosting-platform-and-technology/
(Full disclaimer: ReviveServers.com is an independent hosting provider, and a tradename of the company I own)
Regards, Erik
-
The most important reason why asynchronous loading is complicated, is that many browsers fail to correctly process and display ads that are in turn third party ad tags. Because of this, I believe nobody has been able yet to build anything that works flawlesly.
-
Please have a look at the upgrade instructions at http://www.revive-adserver.com/support/upgrading/ and this blog post at http://www.revive-adserver.com/blog/enabling-revive-adserver-plugins-after-upgrading-to-version-3-0-0/
Problem Upgrading From 2.8.11 To 3.0.2.
in Managing Revive Adserver
Posted
I've seen this before.
In recent years, there have been several people that had their system hacked, and found that hackers had replaced this specific file with one that was malicious. In many cases, since this particular file isn't used all that often, the quick fix was to just delete the file. However, now the upgrade wizard can't find it.
You should be able to find the original fine in the plugins zip files in the etc folder.