Sperber

Hi Eric,
this is your answer to this really important question? The official answer? Then, this is the end of Revive in the EU! I fully agree with Mr. Sperber.
Really disappointing after so many years ...
tobean

Due to the fact, that on may 25th the GDPR comes into effect, is there anything in the pipe to make Revive complying with the EU-regulation? Actual, Revive processes a whole of bunch of personal data and and the use of it will be penalized in the end through fines. I am wondering that there is not one official statement about the whole GDPR-thing, as this needs to be clearified by Eric ASAP. Else we all have to shut down our Revive-Installations or we have to face drastic fines for using it beyond may 25th.
20 days to go, plus the rest of today.

Hi @NuMedia Direct Marketing,
Okay, thanks for letting me know that * isn't supported in banners - I wasn't entirely sure, but thought it might have been.
Sounds like a dynamic banner type is something we could really do with having supported...

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
That is great news! 
We will be looking forward to get an official statement :)

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.

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..

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?

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.
 

@Sperber Please upgrade to the latest version. The issue has been fixed in 4.0.1.