Jump to content

martin.krcho

Approved members
  • Content Count

    13
  • Joined

  • Last visited

  1. Thanks for the advice, @Joost Gysemans. I had the same issue and changing the "webDir" setting solved it.
  2. I would, but the snippet posted above just keeps repeating every time I try to run the upgrade again.
  3. The permissions on the file are 100% correct. It still doesn't work as it should.
  4. No, I definitely didn't overwrite the config file. It has the correct file name. I am very detail oriented person which is kind of a necessity when performing upgrades such as this one. I thought it might be file permission or something else at the system level, but I can't figure it out. I even started debugging the PHP code that is determining if the action that needs to be done is an upgrade or an install. No luck there either. Has anyone got any other ideas? Somebody from the Revive team?
  5. I am not able to upgrade from 3.2.0 to 3.2.1 and I have no idea what is wrong. I tried for the third time in the span of couple of weeks with the same result. I followed the official instructions step by step: http://www.revive-adserver.com/support/upgrading/ The problem comes when I run the upgrade wizard in the browser. It is asking me for database details instead of picking them up from the config file. When I enter the details it is not happy. I have successfully upgraded Revive couple of times before, even when it was still OpenX. I am out of ideas here. Can somebody please help me? This is in the install.log: ========================================================================= Attempting to detect an existing Openads (aka. phpAdsNew) installation... PAN not detected Attempting to detect an existing Openads (aka. Max Media Manager 0.1) installation... MMM v0.1 not detected Attempting to detect an existing Openads (aka. Max Media Manager 0.3) installation... MMM v0.3 not detected Attempting to detect an existing Revive Adserver installation... No previous version of Revive Adserver detected
  6. I am trying to upgrade from Revive 3.2.0 to 3.2.1 by following this guide: http://www.revive-adserver.com/support/upgrading/ When I get to the "Run the upgrade wizard" step, it is not finding my existing installation and it is asking for database details as if it was going to install a fresh instance for the application. Anyone else is having this problem? Any ideas what could be wrong? I checked the file permissions, database credentials... The install.log shows this: ========================================================================= Attempting to detect an existing Openads (aka. phpAdsNew) installation... PAN not detected Attempting to detect an existing Openads (aka. Max Media Manager 0.1) installation... MMM v0.1 not detected Attempting to detect an existing Openads (aka. Max Media Manager 0.3) installation... MMM v0.3 not detected Attempting to detect an existing Revive Adserver installation... No previous version of Revive Adserver detected I looked at the code in lib/OA/Upgrade/Upgrade.php, function detectOpenads. After some debugging I found out it is never getting past the first if statement. Is it supposed to? I can't see where else would it set the existing_installation_status to OA_STATUS_CAN_UPGRADE.
  7. I believe zero in those fields DOES mean unlimited. At least it always used to be the case and these are also the default values. I tried to change the values to "-" (similar to "Impressions"), but they revert to zero when saving. I tried to set both values to 1000, but it is still not showing the banner.
  8. I tried clearing the cache couple of times but that did not help either. Are there any debugging features I could use to identify the cause and perhaps help fixing it in case it turns out to be a bug?
  9. I don't think so. All the other ones are working fine and I haven't changed anything. Cache timeout is set to 1 second at the moment to eliminate any caching weirdness.
  10. Sure. The zone ID is 48 and it is loading asynchronously from https://kampane.virtualstudio.sk/www/delivery/asyncspc.php?zones=48%7C3%7C6%7C1%7C14&prefix=revive-0-&loc=https%3A%2F%2Fwww.mojandroid.sk%2Fgarmin-nove-akcne-kamery-vibr-x%2F&referer=https%3A%2F%2Fwww.mojandroid.sk%2F%3Fs%3Dgarmin.
  11. It doesn't work for me when I include the async script multiple times on the same page. Only one of them loads and doesn't pick up all the zones (at least not the 1st time the page loads). I ended up writing a WordPress plugin that does the placement for me.
  12. I have a zone in single banner in it with 100% probability. Despite this the banner doesn't show. I have seen this behavior in previous version as well, but it was pretty random. I already tried all the obvious - clear cache, recalculate all the probabilities, checked campaign and banner setting... Has anyone seen this issue on their Revive instance? Do you have any more tips for debugging/trying to find out why the banner is NOT being served when it SHOULD be? PS: I already raised an issue on the GitHub, but this needs to be confirmed as a bug: https://github.com/revive-adserver/revive-adserver/issues/569
  13. My Revive installation does something very odd and it seems to be random. It decides to stop showing certain banners even though they should be showing. This is second time this happened to be and it is really frustrating as I spent all day trying to get to the bottom of it. Could anyone please help? I am happy to explain details over an email. Before you start suggesting things like upgrade, checking the Revive troubleshooting and all the other usual things, let me tell you, I've done everything there is to do or check. Anyone?
×
×
  • Create New...