zmeglic
-
Posts
6 -
Joined
-
Last visited
Posts posted by 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"
-
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.
-
Thank you for suggestions. For now, I am fine with the workaround.
-
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']; -
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.
Asynchronous JS Tag not working on v4.0.0
in Managing Revive Adserver
Posted
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.