andrewatfornax

Maybe post some screenshots of the campaign and banner details for those banners that are not delivering? Also, take a look at the probability % values for those banners in the relevant zone(s).

What was the version, and what was the issue, please?

See also the documentation: http://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Documentation

Check your PHP settings - Revive Adserver tries to suppress these warnings, but it can't do so if your PHP config won't allow it.

Sounds like a bug to me - can you report in GitHub, if not already reported, and reference the details & this thread, please?

Can you please provide a lot more information? Like for example - what tag type you are using? Where we can see the generated invocation tag in raw form? Where we can see the tag working on a non-SSL site, and not working on an SSL enabled site? Thanks.

See some of the many other posts on the same topic! However, in short - this was resolved in 3.0.4 (and only affected users running automatic maintenance).

Can you provide a link to more information, please?

I haven't done it yet - but when I do, these will all be explained somewhere around this page in the documentation: http://documentation.revive-adserver.com/display/DOCS/Invocation+code

Revive Adserver support pop-unders. Create a zone of type "popup" and you are away! http://documentation.revive-adserver.com/display/DOCS/Creating+a+zone

Hi! When you say "sidebar widget", it makes me think that you're pasting the invocation code into the UI of some kind of CMS (e.g. Wordpress), inside a widget for displaying things. Sometimes, those kind of CMS tools try to be nice and prevent you from putting HTML code in them, and escape all the code, so that it doesn't display correctly when you view the page. Have you checked the source of the page you're viewing to make sure the Revive Adserver invocation tag is appearing as it should?

Check your spam filter, perhaps, or your mail server logs? Revive really does use mail() to send mail. Of course, perhaps it's not sending mail at all to the mail server, but then, your mail server logs should be able to confirm that.

@bmanke I never heard back - please let me know if it works for you, so we can resolve this topic if it helps?

No; the Google Adsense (or other network) targeting will not be affected. Google (and just about every other network) uses JavaScript-based tags. While Revive Adserver can deliver these (and add/modify as required to ensure that it can track impressions & clicks), in the end, the JavaScript will be executed by the user's web browser, on their computer; the fact that you are using Revive to deliver the JS code in the first place has no effect at all on what the tag does; as a result, any geo or other form or targeting or logic that the ad network implements in their system is unaffected.

Most likely this was due to the recursive nature of the above commands, rather than the absolute vs. relative path. Permissions actually need to be set appropriately for all files/sub directories; for a clean install, it's not an issue, as the folders are empty. But on migration, that may not be the case, depending on how the files were move and what else may be changing.

Banner weights operate in exactly the same way as campaign weights, which are described in the documentation: http://documentation.revive-adserver.com/display/DOCS/Creating+a+campaign Having just re-created your example above (having three banners with weight 1, and one with weight 2), I get exactly what I would expect - the weight 1 banners have probability of 1/5 (i.e. 20%) and the weight 2 banners has probability of 2/5 (i.e. 40%). I wonder if the above updated when the maintenance script ran? Or did it stay like this?

Good news! The Revive Adserver documentation explains: http://documentation.revive-adserver.com/display/DOCS/Email

What do you mean by "slot", please?

Normally, they should be. What version of Revive Adserver was this? Was it an upgrade from OpenX? Direct, or were there versions of Revive Adserver in between?

Hi Paul, What version of Revive Adserver are you running? What version of OpenX did you upgrade from? Did you go directly between those two versions, or have there been versions of Revive Adserver in between? Thanks.

See above re: my comments about the development team "not caring". Of course we care - we would not do what we do (for free) if we didn't care. (Either that, or we're all mad!). However, we do get a lot of new bug reports on GitHub, and sometimes, they just sound like requests for support. We could do support through GitHub, but if that's the case, then we're paying a lot of money (at our own expense, for free, for no reward other than personal satisfaction) for this forum! So, we'd rather close a few cases and ask people to come here first if it's not a clear cut, definitely a bug type of report. If you're able to make sure bug reports are clear cut, and include all the detail required to prove it's a bug (and even better, send a pull request with it), then this will hugely improve the Revive Adserver community for everyone, as well as making the development team more able to correctly and swiftly respond to bugs. In the mean time, when we get it wrong, and close something that actually is a bug because we think it's a support case - please accept our apologies. We're not perfect - just a few guys who love Revive Adserver, and want to do the best we can in our spare time to make it better. Cheers, Andrew

Hello! If you disable maintenance, Revive Adserver won't work. Maintenance needs to be run to ensure that statistics are summed up, and banner delivery priorities are re-calculated. Please see: http://documentation.revive-adserver.com/display/DOCS/Running+Maintenance As for us helping out in the forum - we provide the forum (for free) for the software we develop (for free), and we help out when we can (for free). I also have a day job that takes up 45+ hours a week. So, I do my best to make Revive Adserver as good as it can be, and to help out and answer what questions I can, when I have time. I also hope that the project grows, and more people help out and provide good answers. However, as this topic started out as an issue about missing stats in Revive Adserver 3.0.0, which was resolved by the user, but has now morphed into a discussion about the issue in 3.0.3, it's not always easy to see what's going on or be immediately responsive. Until someone offers to pay me to do this full time, I'm afraid support from the development team will have to be on a good will basis! It has been, and is fixed in Revive Adserver 3.0.4. Thanks to all who helped locate the cause and gave us the information needed to fix the issue.

Yep - use the JavaScript tags!

I think they can, it's just not recommended - without anything else present, if Revive Adserver decides that an impression isn't needed, a blank will end up being served, which means the impression won't be counted, and Revive's view of the available inventory will be wrong. Where are you seeing this warning, by the way? I have just tested linking a contract campaign to a zone, with no other campaigns linked, and I can't see where a warning appears... Can you provide a screenshot, please? If Revive does this, I may have a documentation update I need to do!

Do you mean, can Revive Adserver display a certain banner (or set of banners, or externally provided invocation tag) in the event that it would otherwise have no banner to display? If that's what you're asking, then yes! You can definitely configure Revive Adserver to ensure that, no matter what, there is a fallback banner (or tag) that will be displayed to the user, so you don't have an "empty" impression.