Jump to content

scott001

Approved members
  • Content Count

    103
  • Joined

  • Last visited

About scott001

  • Rank
    Advanced

Recent Profile Visitors

1,787 profile views
  1. Or you can just ignore this and nearly every other post in your forum...it seems like nothing ever gets a reply here. I'm not sure who's running the show, but it seems like most issues posted here go unanswered. Why bother having a forum at all? Just ignore it, and it will go away, right?
  2. I'm looking for the same information, but since you've gotten no reply to this in 8 months, it doesn't look like they want to help those affected by their security issue.
  3. Any word from Revive on this??? Just ignore it and it the issue will go away, right? Thank you for sharing this. I was just reading about a widespread exploit against Revive, but can't find anything here from them, only from individual users who've had the issue. It seems like Revive should be publishing methods for finding such exploits, since they left the hole in the software that caused this.
  4. I am shocked there is still no answer provided.
  5. After reading this article it made my wonder if my installation in infected with malware, and if so, how can I detect it? Millions of web surfers are being targeted by a single malvertising group ­ Ars Technica https://arstechnica.com/information-technology/2021/04/malvertisers-use-120-hacked-ad-servers-to-target-millions-of-web-surfers/ To me it seems like you should have alerted anyone running your software of this problem, and sent out tips for how to find an infected installation, and repair it, but, it's not me running your business. Please share how to s
  6. Update, I am able to get the link to at least function with the changes below, but notice the destination URL is very different from what is generated by the zone. In the code above generated by the zone, the link does not work: <!-- MySite.com Advertising No Cookie Image Tag - Generated with Revive Adserver v5.2.0 --> <a href='https://www. MySite.com/adserv/www/delivery/cl.php?zoneid=397&campaignid=1131&bannerid=2539' target='external'><img src='https://www. MySite.com/adserv/www/delivery/avw.php?zoneid=397&amp;source= MySite.com&amp;target=_blank&am
  7. After the same upgrade my click tracking and links used in my eNewsletter no longer work. I re-created a tag which looks like this: <!-- MySite.com Advertising No Cookie Image Tag - Generated with Revive Adserver v5.2.0 --> <a href='http://www. MySite.com/adserv/www/delivery/cl.php?zoneid=397' target='_blank'><img src='http://www. MySite.com/adserv/www/delivery/avw.php?zoneid=397&amp;source= MySite.com&amp;target=_blank' border='0' alt='' /></a> However, the link does not function, even though it is correctly set up for the banner selected
  8. I am also having trouble creating links to track clicks in my eNewsletters. Has anyone found a solution to this issue?
  9. How can I receive email notifications of updates to Revive? I just discovered that 5.5.1 is out with a security update, but never received an email about this. I thought I was on the list, but apparently I'm not.
  10. So, the important test I did was that it works fine using Iframe tags, but will not work at all using the async tags. Do you know why that would be? Again, I've tried everything, and to me it seems to be some sort of coding issue with the async tags.
  11. So I can get the iFrame tags working as described above, but not the async tags. Do you know why the async would not work for a subdomain, while the iFrame tag would?
  12. Perhaps I am misunderstanding what Delivery Engine URL means. Is this the web site where the ads are served? It isn't clear, but knowing this might be helpful?
  13. When I change the Delivery Engine URL (SSL) to the subdomain ads.mydomain.com the banners stop displaying. I can only get this setting working when it is www.mydomain.com. Normally this would make me think that the subdomain isn't set up properly, but it is, as I use it to server other content on the site (for example Google Analytics). I also mentioned that I am using the subdomain to server the asyncjs.php script in the site template, and I am using it as the Image Store URL (SSL) setting. So, the subdomain is set up, working, and there is nothing in my .htaccess, site security policy,
  14. I brought this up once before, and I still cannot solve this issue. I would like to change the setting for "Delivery Engine URL (SSL)" to a subdomain, for example ads.mydomain.com. But when I do this the ads do not show. It only works using www.mydomain.com. This is strange because I can change the "Image Store URL (SSL)" setting to ads.mydomain.com, and it works fine. I can also use this path in my site's template, and it works fine: <script async src="https://ads.mydomain.com/adserv/www/delivery/asyncjs.php"></script> There is nothing in my .htaccess or site
  15. So in root .htaccess is being read and executed, and I do have that code in there for force cookies to be https, yet it does not work.
×
×
  • Create New...