Refs #572

 * Implementing Custom Date range in Core, eg "period=range&date=2010-01-05,2010-02-03"
 * Only the requested plugin's report will be processed, ensuring fast responses
 * when a large period is requested, the code will try and select an optimal number of sub periods (see Range.test.php) - a mix of weeks, months and days inside the requested range
 * adding integration testing + unit test for optimal subperiods algorithm

TODO
 * we should also use Yearly archives whenever possible (when date range is very large)
 * if custom date range start date == website creation date or before, can use more optimal subperiods (using starting month / year / week)
 * Test/implement "last N days" 
 * Test with timezones when the custom date range ends today
 * UI to allow selecting custom range (show 2 calendars)
 * Update API reference doc + add example in API page listing
 * Add "last 7 days", "last 30 days" in the user settings for "Default date to load"
 
NB: 3 tests fail in Main.test.php on my box, but I'm really not sure why... let's see if Jenkins fails as well

git-svn-id: http://dev.piwik.org/svn/trunk@4159 59fd770c-687e-43c8-a1e3-f5a4ff64c105

1 files changed, 1 insertions, 1 deletions

diff --git a/core/Period.php b/core/Period.php
index ca97fd902c..2c9b5c0473 100644
--- a/core/Period.php
+++ b/core/Period.php
@@ -30,7 +30,7 @@ abstract class Piwik_Period
 	protected $subperiodsProcessed = false;
 	protected $label = null;
 	protected $date = null;
-	static protected $errorAvailablePeriods = 'day, week, month, year';
+	static protected $errorAvailablePeriods = 'day, week, month, year, range';
 	
 	public function __construct( $date )
 	{