Asynchronous JS Tag not working on v4.0.0

[zmeglic]

Hi.

I just upgraded from 2.3 to 4.0.0 and now the async code is not working. Javascript delivery code works fine.

Chrome reports error 500 (internal server error) on  //(domain)/boxes/www/delivery/asyncjs.php

Thank you for any suggestion.

[Erik Geurts]

If there is a 500 error, then the cause can be found in your web server's error log. I suggest you try that first.

Just curious: did the async tags work before you upgraded to v4.0? You write about 2.3, but I assume you mean 3.2?

[zmeglic]

Yes, sorry. It probably was 3.2. :)

Yes, it was working fine before the upgrade.

I found the reason: I replaced these two lines from asyncjs.php

WORKING:

require __DIR__.'/async.js';
require __DIR__.'/fl.js';

NOT WORKING:

require __DIR__.'/'.$GLOBALS['_MAX']['CONF']['file']['asyncjsjs'];
require __DIR__.'/'.$GLOBALS['_MAX']['CONF']['file']['flash'];

 

[Erik Geurts]

Looks like either something went rather wrong during the upgrade process, or your server isn't entirely compatible.

[zmeglic]

Thank you for suggestions. For now, I am fine with the workaround.

[Erik Geurts]

Hacking the code to work around an issue might sound like a nice fix, but it is at best fixing the symptoms, not the actual cause. I wouldn't be surprised if other functionality is now broken as well. I would recommend looking for the actual cause and fixing that.

[zmeglic]

I agree. 

That is why I posted this question, here. Hoping someone would have an idea where to look. I really don't know anything about how revive works.

[Erik Geurts]

As I said, the first and best place to look for information is the Apache error log (or the equivalent if you're using some other sort of web server software).

[zmeglic]

Checked.

Nothing in error log.

only this lines in normal log

31.15.138.76 - - [17/Dec/2016:17:32:12 +0100] "GET /<PATH>/www/delivery/asyncjs.php HTTP/1.1" 500 344 "http://<DOMAIN>/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36"

[Erik Geurts]

Is your error_log completely empty? Or just not logging anything about this particular situation?

[zmeglic]

It is  completely empty. But that is all I can get. The server is not under my control.

I did find some wrong paths under settings, but I can not see a direct connection. 

Is there a way to "RESTART" revive? So it re-reads configuration file.

[andrewatfornax]

Hi @zmeglic,

There's no need to restart Revive Adserver - each banner delivery is a new request, so changes to configuration files are instant. There are some pages / deliveries that are cached for performance, but if the server is not under your control, you can't do much about that anyway.