Jump to content


Approved members
  • Content Count

  • Joined

  • Last visited

About Josh

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just tested clean install of 5.0.1 and get the same issues. Since I thought it may be related to geoip I tested that maxmind reader can successfully read from the mmdb file, which it does. <?php require 'lib/vendor/autoload.php'; use MaxMind\Db\Reader; $ipAddress = ''; $databaseFile = 'var/plugins/rvMaxMindGeoIP2/GeoLite2-City.mmdb'; $reader = new Reader($databaseFile); print_r($reader->get($ipAddress)); print_r($reader->getWithPrefixLen($ipAddress)); $reader->close();
  2. After upgrading 4.1.4 to 5.0.1 I get this message on every banner. WARNING: The cached delivery rules DO NOT AGREE with the delivery rules shown below Please hit save changes to update the cached delivery rules. This occurs even for freshly created banners with no delivery rules. Re-saving banner delivery rules has no affect. Zone probabilities show banners will display, but they do not. I have tried the upgrade process to 5.0.1 from both 4.1.4 and 4.2.1 multiple times. PHP 7.3.11 MySQL 5.7.27
  3. The upgrade process is fairly easy but make sure to create a backup. 5.x comes with a new MaxMind GeoIP2 plugin. Several including myself are seeing problems with delivery rules after upgrade.
  4. The htmlcache column will be rebuilt. You need to find the source of the problem.
  5. If you haven't already, move the current revive webroot somewhere else for later review. Do a clean install of revive. Move only your image files to new install and copy your config over after manually reviewing it. Review the append and prepend fields in _banners and _zones tables. Look especially for <script> and <iframe> tags that should not be there. This may help you find the file that was compromised. grep -rIP '(eval|exec|system|passthru)\(' /path/to/revive-install | grep -P '\$_(REQ|GET|POS)' Reset passwords and review rest of server. Through the fi
  6. It's useful to look at the zone probability report to see what Revive is calculating for current probability. As you do this and make changes remember that caching can have some impact, switch to admin user and recalc probability in maintenance.
  7. check permission of all the *.conf.php files in var/ maybe the webserver (apache?) is the file owner and thus writable.
  8. Configure CDN Origin to be your revive /www/images In Revive admin Configuration > Banner Delivery Settings > update Image Store URLs to your CDN URL
  9. Search for HTML5 + clicktag. This site provides instructions for several creation tools. http://www.html5clicktag.com/clicktag-for-google-web-designer
  10. What invocation tags do you use? Look in Dev Tools > Network. Do you see double impressions being requested? Look in web server logs, isolate some requests and investigate them. Are they bots?
  11. Usage example for refreshing javascript async invocation tags. Got it working like so HTML <div class="ad-300x250" id="ad-300x250-1"> <ins data-revive-zoneid="153" data-revive-id="b7c2bd3ff3b3bed3a9daa932a43cc2a8"></ins> <script async src="https://ra.example.com/www/delivery/asyncjs.php"></script> </div> <div class="ad-300x250" id="ad-300x250-2"> <ins data-revive-zoneid="154" data-revive-id="b7c2bd3ff3b3bed3a9daa932a43cc2a8"></ins> <script async src="https://ra.exa
  12. Assuming you can control your invocation code output for new visitors, you could use Delivery Options to target source=new-visitor. And like Andrew said, use override campaign to make sure they are highest priority.
  13. This is due to bots. Bots most often won't execute js tags but will follow <img> (logging beacon) and <a> (click tracker). You can confirm this by looking at your web server logs.
  14. For "Alter HTML to enable click tracking" choose "Eyeblaster" instead of "Generic HTML" If that doesnt work, add the "ncu" param, like so <script src="https://bs.serving-sys.com/BurstingPipe/adServer.bs?cn=rsb&c=28&pli=22958752&PluID=0&w=728&h=90&ord={random}&ncu={clickurl}"></script>
  15. Sure. Disable the auto refresh and let it serve once per page load. Or put a frequency cap on the Campaign Properties or Banner > Delivery Options. Then add a remnant campaign to consume the excess.
  • Create New...