Approved members
  • Content count

  • Joined

  • Last visited

About firstimpression

  • Rank

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

651 profile views
  1. According to this webserver config, any request like would be fetched from /opt/revive-adserver-4.0.1/www/images/image.jpeg. You have to configure your webserver accordingly if you want to serve over HTTP anything that is outside of www folder. You can use Alias or RewriteRule directives.
  2. @BrianB, did you ever solve it?
  3. Yes, look in /etc/php.ini and apache configs (usually in /etc/httpd/) for anything that refers to "/hermes/phpsessions". I think there is some strange ASCII symbol that someone mistyped in a config before path. Eg. session.save_path=`/hermes/phpsessions If you fix the setting don't forget to reload the webserver to apply the change.
  4. @Accuraty, from my experience, after you run out of disk space, and after you solve the issue by freeing up some space, you have to restart MySQL. Otherwise it just continues to behave as if there is still no space available.
  5. @duplexcleaning, this soudns like an issue with PHP session storage. Try to enable PHP error logging in php.ini (the setting called log_errors), and see if there are any error messages in webserver error log. My bet is that your session storage folder is not writable.
  6. Are you absolutely positive that error logging is enabled, and still there are no error messages in logs? Keep in mind that you can enable: Revive's native logging Webserver logging PHP error logging Those are different logs that work on different levels of systems, enable them all and check them all. Does the error appear instantly, or after some long time?
  7. What is the document root of your webserver?
  8. Got it, had to run "composer update" in install directory to download dependencies Sinergi and Symfony.
  9. I performed a normal upgrade from 3.2.2, and everything worked except upgrade of DeliveryLimitations plugin (request returned Error 500). Now when I try to manually enable the plugin, getting error 500. The PHP error log would pop the error below. PHP Fatal error: Class 'Sinergi\\BrowserDetector\\Browser' not found in /var/ox/lib/OX/Plugin/Component.php on line 64, referer: http://localhost/admin/plugin-index.php PHP Stack trace:, referer: http://localhost/admin/plugin-index.php PHP 1. {main}() /admin/plugin-index.php:0, referer: http://localhost/admin/plugin-index.php PHP 2. OX_PluginManager->enablePackage($name = 'openXDeliveryLimitations', $reparse = *uninitialized*) /var/ox/www/admin/plugin-index.php:192, referer: PHP 3. OX_Plugin_ComponentGroupManager->enableComponentGroup($name = 'Client', $extends = 'deliveryLimitations') /var/ox/lib/OX/Plugin/PluginManager.php:504, referer: http://localhost/admin/plugin-index.php 4. OX_Component->getComponents($extension = 'deliveryLimitations', $group = 'Client', $recursive = TRUE, $enabledOnly = FALSE) /var/ox/lib/OX/Plugin/ComponentGroupManager.php:641, referer: http://localhost/admin/plugin-index.php 5. OX_Component::factory($extension = 'deliveryLimitations', $group = 'Client', $component = 'BrowserVersion') /var/ox/lib/OX/Plugin/Component.php:189, referer: http://localhost/admin/plugin-index.php How to fix this? Do I have to separately install Sinergi browser detector...? Thank you
  10. Can you give me any hint how to check if database was upgraded? Some specific field value, or type? But except the `rv_application_variable`.`oa_version`
  11. No. That's where I got surprised, that no further action was required. I refreshed the page, and probabluy because /var/INSTALLED file is present it just acts as usual, just like a normal upgraded installation.
  12. Does upgrade from 3.2.2 to 4.0.1 include any database changes? When I ran a test upgrade on a dev server, after copying files I entered admin GUI, and it gave me message, unfortunately, it is gone now, but it was something like "your version is 4.0.1 no upgrade is needed". Is that normal??
  13. Done:
  14. Distribution. Sometimes we want to switch admin servers and not to loose all currently logged in users' sessions.
  15. The problem of malvertising is becoming bigger issue all the time. I'd suggest adding an option to sandbox iframe tags, so that the stuff that runs in iframe would not be able to: perform top-window redirects run javascript (serve static HTML only) open any new windows (not clickable) prevent content from using plugins (eg. if you want to block video when you sell placement for HTML ads only)