andrewatfornax

Check that all the files in the directories & sub-directories are also writable?

The calls you have in the code above to the lg.php script are the ones that perform impression logging. Are they being triggered?

https://documentation.revive-adserver.com/display/DOCS/Directory+Permissions

Hi @Korona, The terms Advertiser and Publisher as used in Revive Adserver are defined on the docs page at https://documentation.revive-adserver.com/display/DOCS/Key+Concepts. Revive Adserver is not a "self-service" application by itself - you cannot use it to go an find advertisers for your website. Instead, Revive Adserver will help you manage the advertisers that you do find - be that directly, or via one or more ad networks.

Please work through https://documentation.revive-adserver.com/display/DOCS/No+Statistics and let us know what you find.

I agree with Ian I can see from your screenshot that this is an HTML banner, that is loading a <script> tag. That tag is clearly being loaded correctly by Revive Adserver into the user's browser, because the script is on a totally different URL from the one that is then failing. That tells me that the ad is being loaded, the script is being run... and then it's doing whatever it's doing, and ending up with a problem. Now, I don't know why that script works when you put it directly into HTML, but doesn't work when it's loaded via Revive Adserver, but that's something you can really only track down via a process of looking at the calls made, and talking about them with the relevant 3rd parties.

As I understand it, asynchronous tags load banner content after the main document has been written, so, you cannot use document.write to put content into the main document, because it's already been written. See: https://stackoverflow.com/questions/24297829/execute-write-on-doc-it-isnt-possible-to-write-into-a-document-from-an-asynchr I think the work arounds are: 1. Don't use asynchronous tags; 2. Use a different mechanism for writing the banners other than document.write; or 3. We look at using something like https://github.com/krux/postscribe I'll raise the idea of #3 with the core team.

Yes, you do need to enable cookies before you can use the admin UI of Revive Adserver. I'm not sure what you mean by your second sentence, though. Are you saying that something is not working? https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken

No, I would not attempt to modify a 3rd party banner - if their banner is designed to work in an iframe, then that's how it should be used. Altering it could have any number of unexpected consequences.

Hi @King of Ads, As a general rule, I would say yes, most of the code is required. If you go changing things, then who know what will work or won't work. I hate giving this advice, because it always seems a little lame and unhelpful, but honestly, if your hosting provider cannot give you a host where you can upload files and they files you put in place actually stay there, then you're wasting your money. There are plenty of other hosting companies out there who actually deliver the service that you pay for.

Yes, that looks like an iframe as external content to me.

I'd maybe double check all the plugins really are installed and enabled?

Alas, a 500 internal server error means exactly that - something went wrong internally with the server. That could be a web server problem, or it could be that there was a fatal PHP error. Either way, the logs on the server (both webserver and PHP logs) are where you need to look. If there's nothing there, you may need to increase the logging level. https://documentation.revive-adserver.com/display/DOCS/Revive+Adserver+Broken#ReviveAdserverBroken-HTTP500ErrorCode

https://documentation.revive-adserver.com/display/DOCS/No+Statistics

It should, but we use a 3rd party library for this, so it might not. If you have reproduce steps, could you please create a bug in GitHub for us?

I'd go for a distribution list in that case...

Definitely correctly sized & typed banners/zones are in place?

https://documentation.revive-adserver.com/display/DOCS/Delivery+Rule+Evaluation+Order Easier way is to use Delivery Rule Sets!

Revive Adserver always stores data in the database in UTC time. Changing the timezone in the UI will not affect that. However, data will be converted and displayed in the selected timezone in the UI.

Yes, you can absolutely set daily limits for a remnant campaign. Just make sure you always have at least one unlimited remnant campaign in every zone, if you want to ensure that you have no blank impressions. (Or use zone chaining to fall back to another zone in the event of a blank, if that approach works better for you.) I think we might prefer to say that Revive Adserver makes an intelligent estimate of expected inventory for zones, when calculating the priority to use for contract campaigns, rather than "guess", but in essence... Yes. :-)

https://documentation.revive-adserver.com/display/DOCS/Setting+Up+a+Development+Environment

Hi Ken, Ah, okay. If the banner is installed already, and is generally working, then I would not uninstall the plugin and re-install (at least, not in the production environment without having a backup in place, and having tested the process out in your staging environment). What about the database? Has that been checked for consistency issues etc?

Well, having a remnant banner in place will ensure that a banner is always displayed, but that might not be what you mean, as it sounds like your real issue is not that you sometimes get blank impressions (although you do want to ideally fix that with a remnant banner), but that your contract banners are not meeting your desired contract targets. Take a look at https://documentation.revive-adserver.com/display/DOCS/Banner+Selection+Mechanism to see if that helps track down why your contract campaigns are not delivering when you are expecting them to.

Sounds like the plugin might be missing or faulty, or there's a DB issue. See our troubleshooting FAQ on RA being broken.

Yes, absolutely - Revive Adserver is open source, so you are free to change your code base however you like. Unfortunately, we don't yet have great developer documentation, so I would definitely recommend using xdebug and a good IDE to allow you to step through the code as it executes.