-
Posts
752 -
Joined
Everything posted by Erik Geurts
-
HTML5 banner showing up on website but not in Revive
Erik Geurts replied to mgh's topic in Using Revive Adserver
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). -
HTML5 banner showing up on website but not in Revive
Erik Geurts replied to mgh's topic in Using Revive Adserver
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? -
Cannot Add New Banner, Advertiser or Website
Erik Geurts replied to TKList's topic in Managing Revive Adserver
You're welcome, glad it was resolved. -
Cannot Add New Banner, Advertiser or Website
Erik Geurts replied to TKList's topic in Managing Revive Adserver
Have you checked if all the plugins were correctly migrated during the upgrade? -
Need help using revive adserver- New to this
Erik Geurts replied to balatkari's topic in Using Revive Adserver
Please do not go down the path of showing popup ads. -
I would strongly recommend to never manually delete any rows in that table (or any other).
-
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.
-
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...
-
@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"
-
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.
-
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.
-
2 problems with https version of revive adserver
Erik Geurts replied to tobean's topic in Managing Revive Adserver
That htaccess file should not be necessary, the ad server will respond with https (if the webserver is properly configured). -
2 problems with https version of revive adserver
Erik Geurts replied to tobean's topic in Managing Revive Adserver
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. -
2 problems with https version of revive adserver
Erik Geurts replied to tobean's topic in Managing Revive Adserver
Require SSL is just for the ad management UI, it does not affect ad delivery. -
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.
-
See
-
Revive is not Counting Clicks for CPC
Erik Geurts replied to dottedquad's topic in Using Revive Adserver
Statistics are updated once per hour at the top of the hour. -
Instead of renaming the files, I would like to mention the option to use symlinks.
-
Tried upgrading to 4.0.0 but getting error now
Erik Geurts replied to anshul123's topic in Managing Revive Adserver
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. -
It can be used with any type of value.