diff options
| author | mattab <matthieu.aubry@gmail.com> | 2016-08-23 00:12:23 +0300 |
|---|---|---|
| committer | mattab <matthieu.aubry@gmail.com> | 2016-08-23 00:15:56 +0300 |
| commit | d83b2b2dd42020dd27a6cf06ad70687aeef42b8f (patch) | |
| tree | 03f7edde5139c6defbffb2f03453b092d6141148 /config | |
| parent | 05298a51789e34e14840ae5c8f8f6fc7a68ef5c0 (diff) | |
Minor Improvement to description
Diffstat (limited to 'config')
| -rw-r--r-- | config/global.ini.php | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/config/global.ini.php b/config/global.ini.php index 35655e3b49..5f904efe27 100644 --- a/config/global.ini.php +++ b/config/global.ini.php @@ -281,10 +281,10 @@ time_before_today_archive_considered_outdated = 150 enable_browser_archiving_triggering = 1 ; By default, Piwik will force archiving of range periods from browser requests, even if enable_browser_archiving_triggering -; is set to 0. This can sometimes create too much of a demand on system resources. Setting this option to 0 and setting -; enable_browser_archiving_triggering to 0 will make sure ranges are not archived on browser request. Since the cron -; archiver does not archive ranges, you must either disable ranges or make sure the ranges users' want to see will be -; processed somehow. +; is set to 0. This can sometimes create too much of a demand on system resources. Setting this option to 0 and +; disabling browser trigger archiving will make sure ranges are not archived on browser request. Since the cron +; archiver does not archive any custom date ranges, you must either disable range (using enabled_periods_API and enabled_periods_UI) +; or make sure the date ranges users' want to see will be processed somehow. archiving_range_force_on_browser_request = 1 ; By default Piwik runs OPTIMIZE TABLE SQL queries to free spaces after deleting some data. |