adTumbler

Erik and team We started using OpenX in 2005, and moved to Revive in 2012. Thank you, again and again for bringing this project back to life. We are hosting our ad server on a cloud provider called Cloudways. They are growing quickly, with provisioning for AWS, Google, Digital Cloud and many others. Gives us flexibility on capacity, availability and scale. Mention this as they are adding "standard builds" at a fair clip: Drupal, Wordpress, Magento; Joomla, SugarCRM etc etc. Have a base PHP configuration we use for Revive. Let me know how I can help have Revive added to their list of supported builds? Version: latest version Revive: 4.0.1 Problem: We are unable to get any Client; Site or Time delivery limitations to work. I have checked the obvious install, config and banner set up. Latest versions of plug-ins are installed and enabled. e.g. Client Delivery Limitation Plugin 2.0.0: Creation Date 2016-09-13: Compatible with 3.2.0-beta-rc3 Extends deliveryLimitations (Note: I would have expected this to say" Compatible with 4.0.1 ? ) Testing: We installed a fresh 4.0.1 on a local VM. Set up duplicate delivery limitations, and as expected, they are all working correctly. Testing: We have done a file compare between our production site and the test VM. There are no differences. Problem: I am almost certain that the problem is with how Cloudways are handling something? Please can you suggest where we can look; debug code etc; we are developers an can dig in if this will help.

I am getting the following warning in our PHP logs. PHP Warning: date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. i) This is a new install of 3.2.2 - I have checked that the system time zone is set - refer earlier issue in forums ii) I have found the suggestion that I recompile Apache - but I can not do this as the site is hosted on a virtual server - which is provided by a service called Cloudways Here is the full stack trace From: [email protected] (Cron Daemon) To: [email protected] Subject: Cron <master_mysite@mysite> php /mysite/scripts/maintenance/maintenance.php ads.adtumbler.com Content-Type: text/plain; charset=UTF-8 X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/home/master> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=master_mysite> Date: Thu, 24 Dec 2015 01:01:02 +0000 (UTC) Status: R PHP Warning: date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /mysite/lib/OX/Admin/Timezones.php on line 136 PHP Stack trace: PHP 1. {main}() /mysite/scripts/maintenance/maintenance.php:0 PHP 2. OX_Admin_Timezones::getTimezone() /mysite/scripts/maintenance/maintenance.php:30 PHP 3. date_default_timezone_get() /mysite/lib/OX/Admin/Timezones.php:136 PHP Warning: date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /mysite/variables.php on line 67 PHP Stack trace: PHP 1. {main}() /mysite/scripts/maintenance/maintenance.php:0 PHP 2. require_once() /mysite/scripts/maintenance/maintenance.php:33 PHP 3. init() /mysite/init.php:139 PHP 4. setupConfigVariables() /mysite/init.php:61 PHP 5. date_default_timezone_get() /mysite/variables.php:67