andrewatfornax
-
Posts
2007 -
Joined
-
Last visited
Posts posted by andrewatfornax
-
-
What? No, you don't need to put information into banners delivered with Revive Adserver to say that they include GeoIP2.
That's the kind of thing that needs to go into Revive Adserver's documentation, when we support GeoIP2 (which we currently don't, but are working on). Just because someone delivers ads through Revive Adserver does not mean you have to call out an attribution for GeoIP.
-
Okay - glad you managed to fix it, even if you are not sure how!
-
You could feed the cookie data you want into Revive Adserver using one of the various targeting options.
-
The ID is just a unique identifier for each item (i.e. the Advertiser ID, the Campaign ID, the Banner ID...) Everything in Revive Adserver gets a unique ID.
Most statistics pages should have an option to download the stats in CSV or Excel format, from memory.
-
Sorry, this isn't an issue we can help with - it will be something to do with your networking, proxy or web server configuration.
-
Is this a question?
-
Hi @franciscomesa,
No movement yet - please help us out!
https://documentation.revive-adserver.com/display/DOCS/Missing+Features
-
Hi @Avindale,
No, unfortunately, there isn't - it's so hard to recommend a specific level of hardware, because the possibilities for configuration are huge (O/S, webserver, database, opcode cache, all manner of Revive Adserver configuration options), and what people want to do with Revive vary as well (something to manage ads for their hobby site all the way up to commercial operations serving billions of impressions a month... maybe even a week or per day).
My recommendation would be that if you're starting out, and you're not sure of hardware scale - don't buy any hardware! Get a VM from provider that will let you scale up (or down) as per your requirements - you can always migrate to dedicated physical hardware later on, if that's your desire, once you have an idea from using a cloud-VM first.
-
Hi Ryan,
I haven't actually run your query, so, just to clarify - is the issue that your query isn't returning the data you want (and you need help getting the right info), or is the issue that it takes a while to return (and you need help making it faster)?
Thanks!
-
-
Yes, for example, as I suggested above. ?
-
Okay - did allowing the path fix the issue?
If not, then I suspect you haven't really allowed what's needed.
Try turning off all restrictions first - if that works, then you've got a starting point to figure it out from!
-
On 6/12/2018 at 3:25 AM, svsanchez said:
Hello, I'm having the same problem here. How do you upgrade to the latest version when there's the Internal Server Error appearing?
Fix the cause of the Internal Server Error first.
Once you have done that, upgrading is possible.
-
There's no documentation that we have to help with this, sorry - this is essentially a systems management issue.
1. Trace down what the internal server error is when you change the memory limit. That's something to do with PHP or the web server - not Revive Adserver. See the appropriate documentation for those products.
2. The database error is pretty clear - Revive Adserver can't connect to your database. Check to make sure that it's possible to connect to the database from where Revive Adserver is hosted, and confirm the username and password. Then make sure all of those (hostname, ports, username, password, database name) are set correctly in Revive Adserver's configuration file.
-
Hi,
Did this fix in the end?
Even if you changed the cache value down from 1200 to 60, information that was cached when it was set to 1200 will still take that long to expire... So it might have started working after that time?
-
It's not clear why you're trying to replace a file in Revive Adserver. Please don't do that.
The post immediately above says that the issue was an ad blocker - so maybe start with that for a solution?
-
No, sorry, there's no easy solution.
You'd have to write a script to parse your logs, and update the database accordingly.
-
Hi @MarkoOpserver,
Hacks are terrible, sorry to hear about it.
The best thing you can do is restore a backup (both database and filesystem - ideally, whole O/S) from when you know the system was clean.
However, if you can't do that...
What makes you say that you are having false clicks? How do you know? What do you see?
-
It does, yes! We're hoping that everyone can spare a couple of $ a month, and together, that will get us to where we can really dedicate some serious time each month to the project... ?
-
Not yet, on my imminent todo list for the coming weeks...
-
Restart? Double check the documentation on allowing things that it says are not allowed?
-
Check the troubleshooting guide, which has a better way to deal with missing plugin functionality...
-
Before you convert, the most important thing to do would be to:
- Backup the database.
- Test the backup can be used to restore the database.
- Test the conversion process on the restored database.
- Test Revive Adserver on the converted test database.
- Document everything so you can do it quickly when you need to.
- Plan for how to revert if it all goes wrong.
But you know all that already!
-
Hi,
No idea, I don't know anything about MOAT yet. Can you please provide more info - e.g. a link?
Output Stats -> Hours
in Feature Requests
Posted
Understood, but if you have a lot of data, then yes, 6 months will take a long time to process and export.
You may be better off querying the database separately if you have specific reporting requirements - or, write up a ticket in GitHub clearly explaining the use case and details of how it should work, and it might be something to consider for future releases.