joesc230

Sorry for the super late reply. I ended up deleting the files and database related to the upgrade attempt. I was running into issues because I was upgrading but doing so with a Revive install that I placed in a folder in a subdomain. The upgrade instructions didn't touch on that too much, and I had to realize that the config file wasn't being named in a way that the upgrade software would recognize that I was doing an upgrade vs. a new install. Once I realized that, I was able to perform the upgrade. Thanks for your time!

Hello, I have version 4.1.4 of Revive running on a site. I'm seeing an issue when there is a question mark at the end of the URL of a page (for example: www.example.com? instead of www.example.com) - in such a case, the ad doesn't display for the user. I took a look and there are a couple of browser console errors: First console error: Access to XMLHttpRequest at 'https://subdomain.example.com/adserver/www/delivery/asyncspc.php?zones=1&prefix=revive-0-&loc=https%3A%2F%2Fwww.example.com%2Ffolder%2Ffolder%2Findex.html%3F' from origin 'https://www.example.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Second console error: https://subdomain.example.com/adserver/www/delivery/asyncspc.php?zones=1&prefix=revive-0-&loc=https%3A%2F%2Fsubdomain2.example.com%2Ffolder%2Ffolder%2Fresults.aspx%3F&referer=https%3A%2F%2Fwww.example.com%2Ffolder%2Ffolder%2Findex.html%3Ftest 403 (Forbidden) As you can see above, the second error references the file at https://subdomain.example.com/adserver/www/delivery/asyncjs.php I have Revive running on a subdomain on the site, in a folder...so I used the sample URLs above to demonstrate that (being installed in this example in a folder named adserver in a subdomain named subdomain) Does anyone know if these errors are a result of a Revive bug or something on my end?

I was following the upgrade instructions here and completed an upgrade from 3.2.1 to 4.1.1 and forgot to change the database value from the old database to the new one. My original copy of revive seems to be running okay, despite my error, but when I go into the admin's Product Updates page it says: "You are currently using Revive Adserver v3.2.1 (warning: database is stamped as v4.1.1) running on Apache, PHP 5.6.16 and MySQL 5.6.38" Is there a way to salvage my mistake? For example, can I fix the issue by overwriting the contents of the "old" (currently what I'm using) copy of Revive with the new files in the zip file? Thanks!