andrewatfornax

Hi @gniver, Possibly the final part of http://documentation.revive-adserver.com/display/DOCS/No+Statistics re: UI preferences?

Hi @fbela15907, First step in debugging - does the tag work in a plain HTML page, outside of a mail client, with Adblocking plugins disabled?

Well, it looks like you've changed that page now, to not be the async tag we were looking at before; I'm afraid that if you're going to keep changing things about, I can't really help any more.

Hi @tomek, Perhaps: http://documentation.revive-adserver.com/display/DOCS/Invocation+code%3A+Website+level ?

Hi @mibert, Haven't Chrome disabled support for things like SWF now? https://support.google.com/chrome/answer/6213033?hl=en-GB

Hi @Fisherman, They should, eventually. Revive Adserver has a default deliver cache of 20 minutes, so, you will have to wait a little while before changes will appear, depending on if there's a zone (or other) cache in place already.

Hi @ekortright, It should be safe to delete the user from the DB. You said you delete the user from the UI - do they show up there at all? An alternative to deleting from the DB would be to just change the password in the DB. Then they won't be able to log in any more.

Hi @brijeshguru99, As you can see from the above code, this is straight HTML - a standard <a href> tag, wrapping an <img> tag. So, I can only think of two reasons why it won't work: 1. The email client blocks this standard HTML feature. If so, there's nothing anyone can do about that. 2. The ck.php script isn't working for some reason. Without seeing the actual link, I can't advise why the second might be the case. Try clicking on the real link to the ck.php script in your tag, and looking for any errors in the UI, or web server/PHP logs for clues.

Hi @scott001, I have doubts that it's a fork bomb - I don't think there's any code in Revive Adserver that creates any additional threads - everything is single threaded (although you can of course have as many single-threaded pathways executing as you set up your web server to allow). It's more likely a mis-identified report by Suhosin as a result of a high number of calls to the logging scripts - either simply legitimately (as a result of a normal traffic spike or a legitimate scripted bulk access), or, possibly a DoS attack.

Hi @re35vive, In that case, please seek help from the developer(s) of the Wordpress plugin. We can't really advise or support something we didn't write. Thanks, Andrew

Hi @Yuttakarn, I've had a look at your page at 192.185.62.148/error.html again, and for whatever reason, I can see something there now. Interestingly, in that page's HTML source, I can see that you have an <ins> tag of: <ins data-revive-zoneid="1" data-revive-id="109667daaa24962d89f6d4716de3a572"></ins>However, when I look at the async.js file that is asynchronously loaded after this tag, the ID appears to be: f58dc13e7cadc4cc6fd01a33bb837915I would have expected those to match - quickly doing up a test async tag in my local 3.2.4 installation, and I do see the tags the same. Have you modified the async tag at all - or perhaps created the tag initially, and then re-installed Revive Adserver, and not re-generated your tags?

Thanks for the information, @deannag65 - you have inspired me to add a new general "Revive Adserver is broken" trouble shooting guide to help capture general issues like this one for others to refer to in the future. http://documentation.revive-adserver.com/pages/viewpage.action?pageId=8028358

Hi @Yuttakarn, The link you posted where the error can be seen does not work, so, there's little we can do to help. I would also recommend that you read up on forum etiquette - it is generally considered to be impolite to repeatedly ask for help. Erik has kindly pointed to a page of suggested, common problems, but you haven't come back to the community with any additional information that would help anyone figure out the issue.

Hi @Joe Blow, Sorry, still no idea really as to why this would be happening - it's not something I have ever seen before. As above, my question remains - any chance of pointing to a link where the issue is happening?

Hi @CyberspaceNet, Unfortunately, while you may not have changed anything, it's almost certain that something has changed! An installation of Revive Adserver won't just stop working for no reason. Your best bet will be to try to find out what has changed - a package update? Someone gaining access and changing or deleting files? A hardware issue? There are lots of things that could have happened - if finding this out is beyond your capabilities, I'd suggesting talking to your hosting provider. HTH, Andrew

All thanks to my wonderful colleagues in the team, but you are welcome, @Docent!

Programmatically, you mean? Via an API?

Can you just leave the divs empty, and then write the invocation tags into them if you want them to be there?

There is an event model, but naturally, it's wildly undocumented - best way to learn how things work would be to step through the code with an IDE debugger. Alternatively, take a look at the older OpenX Source 2.6 code if you can find it, and see how it used to do the logging! Somewhat unhelpful replies, I know, but I am trying to focus on the basic documentation for now, rather than developer documentation.

Alternatively, for future reference, there's are a couple of troubleshooting guide for this: http://documentation.revive-adserver.com/display/DOCS/Plugins+Missing+or+Disabled or http://documentation.revive-adserver.com/display/DOCS/Plugins+Incorrectly+Upgraded

Correct, that is a limitation of the plugin - but also, if I remember correctly, that's due to the underlying geo database, which doesn't have a mechanism for obtaining the list of cities that are supported, nor having a hierarchy of the states they are in (where, of course, the city is even in a state, because not all countries have states... which is probably why the geo database doesn't have such a hierarchy!) Also, yes, technically correct. Well, because, unfortunately, geo targeting is not an exact science. There are a few possibilities: 1. You're not using the paid database, so, the database is deliberately not as up to date and accurate as the commercial database (to give you an incentive to pay); 2. You are using the paid database, but the IP address has been re-assigned or moved, and it's not yet up to date; 3. The database is just wrong; 4. The database would normally be right, but there's some kind of temporary re-routing going on; 5. There's a proxy that's doing something funny with the IP address, and for some reason, Revive Adserver hasn't been able to detect this and deal with it.

Hi @polaris, Getting the 3rd party tag to display should be just a case of putting it into an HTML banner, and then linking that banner to the appropriate zone(s), and putting the zone(s) on to your site. Presumably, though, as you're talking about magic macros, there's something else you are trying to do with that 3rd party tag - but it's not clear to me what that is! Perhaps you could explain the issue a little more, please?

Hi @Matt Glover, As an employee of OpenX at the time the move to the new aggregated stats tables happened in OpenX Source 2.8, I suppose we could more technically say that non-aggregate data collection doesn't scale well using a MySQL-based relational database - and that was the key concern for the business at the time! While other relational databases may offer scaling through sharding, OpenX at the time wasn't about to consider a move away from MySQL for it's systems, and alternatives like Cassandra, Mongo or Redis weren't considered to be mature enough - so the decision was made to go to aggregated logging. I agree that now, it would very much be possible to use another engine other than MySQL to allow scalable, high performance logging that includes the ability to report on things like the referer, or geotargeting information, etc. However, one of the long-standing advantages of Revive Adserver has been that you need very little technical knowledge or access to be able to install it. If MySQL or PostgreSQL is installed, and you have FTP access to a server with PHP, then that's about it. The more we add to Revive Adserver - especially in terms of adding another logging engine - the more we have to maintain. If we were going to make a change like this, I would want to make the new logging engine the default, and drop support for logging to MySQL/PostgreSQL, otherwise maintenance of logging will become a real burden. But, how many existing Revive Adserver users would this then mean can no longer afford to run the server, because they are on really cheap hosts and can't afford a "proper" host that has root access, and wouldn't be able to manage the server anyway if they did have access? I'm not saying "no way" - updating the logging engine would be a really fun project! But is it the right direction for the product? Do we keep things simple, and accept that it won't suit everyone - or do we make Revive Adserver more fully featured, and accept that some lower end users will end up being left behind? Something to think about, and perhaps we'll get a survey out to the community in the near future about what direction the project needs to head in...

Hi @kingcharles, What version of Revive Adserver are you seeing this in, please? Documentation is an ongoing project, and I will get to writing up how to do conversion tracking ASAP.

Hi @Docent, Apologies, I've been sick and away with work travelling. There's a release candidate that's being tested now - hopefully, this will be out at some point next week!