rebased branch, changed parameter meaning and usage

config/global.ini.php

@@ -266,6 +266,11 @@ enable_browser_archiving_triggering = 1
 ; so you can disable these special queries here:
 enable_sql_optimize_queries = 1
 
+; By default Piwik is purging complete date range archives to free spaces after deleting some data.
+; If you are pre-processing custom ranges using CLI task to make them easily available in UI,
+; you can prevent this action from happening by setting this parameter to value bigger than 1
+purge_date_range_archives_after_X_days = 1
+
 ; MySQL minimum required version
 ; note: timezone support added in 4.1.3
 minimum_mysql_version = 4.1

core/DataAccess/ArchivePurger.php

@@ -10,6 +10,7 @@ namespace Piwik\DataAccess;
 
 use Exception;
 use Piwik\ArchiveProcessor\Rules;
+use Piwik\Config;
 use Piwik\Date;
 use Piwik\Db;
 use Piwik\Log;
@@ -104,12 +105,13 @@ class ArchivePurger
     {
         $numericTable = ArchiveTableCreator::getNumericTable($date);
         $blobTable    = ArchiveTableCreator::getBlobTable($date);
-        $yesterday    = Date::factory('yesterday')->getDateTime();
+        $daysRangesValid = Config::getInstance()->General['purge_date_range_archives_after_X_days'];
+        $pastDate    = Date::factory('today')->subDay($daysRangesValid)->getDateTime();
 
-        self::getModel()->deleteArchivesWithPeriod($numericTable, $blobTable, Piwik::$idPeriods['range'], $yesterday);
+        self::getModel()->deleteArchivesWithPeriod($numericTable, $blobTable, Piwik::$idPeriods['range'], $pastDate);
 
         Log::debug("Purging Custom Range archives: done [ purged archives older than %s from %s / blob ]",
-            $yesterday, $numericTable);
+            $pastDate, $numericTable);
     }
 
     /**