Sperber Posted August 3, 2015 Report Share Posted August 3, 2015 Hi folks, I was becoming wet hands as I found out, 3.2.1 can provide asynchronous tags. Nice work But: I upgraded today without any issue, logged in, created the asynch tags for all of my zones and inserted them in our website. So far so good. When I visit our website I can see how the browser tries to fetch the advertiser-url-sources in the status bar, but in the end not a single Ad appears. This isn´t restricted to one of our advertisers - it´s for all of them. AdSense, Affili, Premium Partners, etc... Somehow I get the feelin that may be I forget to activate something, even when I´m sure the upgrade instructions are pretty idiotproof. Anyone who could help me out with a clever hint? Much appreciated. Regards, Chris. tobiasmadsen 1 Quote Link to comment Share on other sites More sharing options...
Adservermods Posted August 4, 2015 Report Share Posted August 4, 2015 Kindly delete the Revive Adserver cache files in var/cache path. This might resolve this issue. Richard Foley 1 Quote Link to comment Share on other sites More sharing options...
Sperber Posted August 4, 2015 Author Report Share Posted August 4, 2015 Thanks for your hint, but I´ve already deleted the cache files this this morning without any effect. The code is delivered and inserted into the sites source code, but the ads still won´t appear. Mhm..anyone experienced this before? Weird.. tobiasmadsen 1 Quote Link to comment Share on other sites More sharing options...
Sperber Posted August 5, 2015 Author Report Share Posted August 5, 2015 So, it´s even getting more weird. Yesterday night - somehow - I managed to get the asynch AdTags working. I guess, so funny it may sound, this was related to disabling tracking for standard html code. Unfortunal, a few hours later Revive refused to deliver the ads, even when the adtags were properly inserted into the website. So this problem persists and I had to switch back to js-tag. Meanwhile I did a little testing, cause our site uses 4 asynch calls for each page. I was thinking wether this could be to much for Revives asynch.php. At least this seems to be one part of the problem. With one asynch active and the rest as js-tags, it worked. Not every time (every third or forth time), but finally the Ads came through. That brings me to the point, wether our machine is deprecated or outdated (8 cores 3.2Ghz, 16 GB...don´t think so with only ~80 active users on website/minute), something went wrong while upgrading or the whole thing could be a part of a possible bug. Guess Erik should have a look into this (if you need site access, please drop me line to my registration mail-adress.) Anyone out there who could confirm this for his Revive instance? tobiasmadsen 1 Quote Link to comment Share on other sites More sharing options...
tobiasmadsen Posted May 9, 2017 Report Share Posted May 9, 2017 Hi, Did you ever find a solution to this issue, or have someone else found a solution? We are experiencing the same issues as Sperber describes, and it looks like our implementation is correct. Kind regards, Tobias. Quote Link to comment Share on other sites More sharing options...
Sperber Posted May 10, 2017 Author Report Share Posted May 10, 2017 (edited) Hello Tobias, unfortunal we were´nt able to bring the asynch-tags to work, nor could we narrow down the problem any further to at least give a feedback if this is more a server side problem regarding php limits & exec time (no errors logged in Revive or the server logs), a browser issue or a native bug in Revive. The asynch function just don´t work for us and I´ve seen no Revive instance - beside the one that delivers the ads in this forums here - that does by now. It´s a pity. If you manage to get them working, please let us others know about it. Regards, Chris. Edited May 10, 2017 by Sperber tobiasmadsen 1 Quote Link to comment Share on other sites More sharing options...
tobiasmadsen Posted May 10, 2017 Report Share Posted May 10, 2017 Hi Chris, That is unfortunate news, but thank you for updating me :) I think we need to implement it without async for now, if we find a solution I will post it here! Kind regards, Tobias. Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted May 25, 2017 Report Share Posted May 25, 2017 A thought on this topic - was there a Varnish cache in use at all? Quote Link to comment Share on other sites More sharing options...
Sperber Posted May 25, 2017 Author Report Share Posted May 25, 2017 (edited) 4 hours ago, andrewatfornax said: A thought on this topic - was there a Varnish cache in use at all? Hello Andre, we use Zend and don´t have varnish installed on our server. If it may help you investigate further on, here is our phpinfo for troubleshooting purposes: https://www.dropbox.com/s/syd5zzp74gtekoh/phpinfo.png Regards, Chris. Edited May 25, 2017 by Sperber Link edited Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted May 25, 2017 Report Share Posted May 25, 2017 Hi @Sperber, Could you just PM me one of your async tags that doesn't work? Thanks. Quote Link to comment Share on other sites More sharing options...
Sperber Posted May 25, 2017 Author Report Share Posted May 25, 2017 11 minutes ago, andrewatfornax said: Hi @Sperber, Could you just PM me one of your async tags that doesn't work? Thanks. Sure @andrewatfornax, check your inbox. Quote Link to comment Share on other sites More sharing options...
Sperber Posted May 25, 2017 Author Report Share Posted May 25, 2017 (edited) @tobiasmadsen, finally and through Andre´s help the asynch-tags are working for us now. I guess he´ll release an official note to this issue, when this is gone through the dev-chain. At least I can tell, in our case it was related to a server setting, redirecting http to https on server level, which leads to a 301 Revive can´t handle by now. Expect this issue to be resolved in one of the upcoming releases. For now and if this is the same scenario for you: just disable the 301 redirecting and you´ll be good. All props belong to Andre! Thanks ;) Edited May 25, 2017 by Sperber Quote Link to comment Share on other sites More sharing options...
tobiasmadsen Posted May 25, 2017 Report Share Posted May 25, 2017 @Sperber That is great news! We will be looking forward to get an official statement :) Sperber 1 Quote Link to comment Share on other sites More sharing options...
andrewatfornax Posted May 26, 2017 Report Share Posted May 26, 2017 Officially, we've updated our documentation explaining what the issue was, and how to get it to work: https://documentation.revive-adserver.com/display/DOCS/Banners+Not+Delivering+over+SSL Hope that helps! Sperber 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.