Jump to content

Erik Geurts

Administrators
  • Posts

    752
  • Joined

Everything posted by Erik Geurts

  1. Is it possible to post the third-party tag here? Perhaps remove the domain and replace it with example.com. Be sure to include the protocol (http or https).
  2. If I understand correctly, the banner using third party code appears OK on your website, but it doesn't show up as a preview inside your Revive Adserver ad management screen?
  3. Have you checked if all the plugins were correctly migrated during the upgrade?
  4. Please do not go down the path of showing popup ads.
  5. I would strongly recommend to never manually delete any rows in that table (or any other).
  6. We currently recommend upgrading to Revive Adserver v4.0.0 (or higher if you read this in the future). For Revive Adserver v4.0.0, the technical requirements state (among other things): "PHP 5.5.9+, 5.6.x, 7.0.x" Revive Adserver v3.2.5 exists solely to help people who want to fix just the most recent set of security issues while they prepare for the upgrade to Revive Adserver v4.0.0.
  7. PHP 5.4 is very outdated and no longer supported. I would recommend using a supported version of PHP, regardless of the version of Revive Adserver. And while we're at it, why not upgrade to Revive Adserver v4 as well...
  8. @malmazan Perhaps have a look at the technical requirements at https://www.revive-adserver.com/support/requirements/ "PHP 5.5.9+, 5.6.x, 7.0.x"
  9. This can be achieved by creating a contract campaign. You can give it a target of X impressions per day (or a total number of Y impressions over the entire lifetime of the campaign. See http://documentation.revive-adserver.com/display/DOCS/Creating+a+Campaign#CreatingaCampaign-Contractcampaigns for more information about contract campaigns or perhaps start at http://documentation.revive-adserver.com/display/DOCS/User+Guide for all available end-user documentation.
  10. By webserver software I mean Apache, Nginx, IIS or something like that. That's a question that is hard to answer from out here. You are going to have to consult your hosting provider or sysadmin.
  11. I mentioned configurations files in plural, only for completeness. For people who use Revive Adserver with a different URL for the ad management UI and the ad delivery component, they will have more than one file. This is not covered in the upgrade instructions since there will be very many variations, and we wanted to keep the instructions as concise as possible for novice users or people with less technical skills and/or experience. Permission for the config file should be set according to what it was in the "old" folder. In addition to the permissions, make sure that the file can be accessed by the webserver software.
  12. That htaccess file should not be necessary, the ad server will respond with https (if the webserver is properly configured).
  13. Ad delivery is not affected by the 'requireSSL=1' setting, that's the ad management user interface only. For ad delivery, if the ad request comes in over https the ad server will attempt to respond over https as well. I've never come across a case where logging out from a https UI address attempts to forward you to a non-https address. That might be a misconfiguration of your webserver software, actually.
  14. Require SSL is just for the ad management UI, it does not affect ad delivery.
  15. Yes, if the upgrade wizard detects the configuration files from the previous version, it will start by saying "Upgrading to Revive Aderver v4.0.0" (or whatever version you're going towards). My best guess is that when you copied the configuration file(s), in their new location the permissions and/or owner prevent the webserver from seeing them. I recommend checking that.
  16. The upgrade instructions assume you use the exact same (sub) domain while upgrading as the live system. If not, you must adjust the file name and the content of the copied configuration file accordingly.
  17. Statistics are updated once per hour at the top of the hour.
  18. Instead of renaming the files, I would like to mention the option to use symlinks.
  19. It seems you missed a vital step in the upgrade instructions, which is to copy the configuration files from the old to the new version before starting the upgrade wizard.
  20. See your own screenshot, it says it's doing an new installation. Believe me, I've done dozens of upgrades in the last couple of weeks. Just follow the steps in the upgrade instructions exactly (see https://www.revive-adserver.com/support/requirements/)
  21. It can be used with any type of value.
×
×
  • Create New...