For consistency, it would be nice if the PrivacyManager plugin + Custom logo ([Branding] section) stored its data in the DB rather than in the config file.
The ultimate goal is to make Piwik not need to write to the config file during normal operations.
- Create global config entries for the following settings:
- delete_logs_max_rows_per_query
- delete_reports_enable
- delete_reports_older_than
- delete_reports_keep_basic_metrics
- delete_reports_keep_day_reports
- delete_reports_keep_week_reports
- delete_reports_keep_month_reports
- delete_reports_keep_year_reports
- delete_reports_keep_range_reports
- delete_reports_keep_segment_reports
- Read the following settings from config instead of option if delete old data admin UI is disabled
- delete_logs_enable
- delete_logs_schedule_lowest_interval
- delete_logs_older_than
- delete_logs_max_rows_per_query
- delete_reports_enable
- delete_reports_older_than
- delete_reports_keep_basic_metrics
- delete_reports_keep_day_reports
- delete_reports_keep_week_reports
- delete_reports_keep_month_reports
- delete_reports_keep_year_reports
- delete_reports_keep_range_reports
- delete_reports_keep_segment_reports
The values from the option table should overwrite the values from the config in case the delete old data admin UI is enabled. It should not be possible to set a value in the option table while the delete old data admin UI is disabled.
- Migrate entries from config to option database table:
- Following config settings to be stored in the DB using Option::set and Option::get
- Upgrade: convert config file values to the new format in db. Then explicitely remove the settings from config file.
- Values are cached in the file tmp/cache/tracker/ file for fast access during tracker mode using the existing hook to add to cache/tracker/x.php in case they are used during the tracker process
Here are the config settings that, should be removed in favor of Option::
- use_anonymized_ip_for_visit_enrichment
- ip_address_mask_length
- [Branding] use_custom_logo
Note:
- The "enabled" setting is already using Option:: mechanism.
For consistency, it would be nice if the PrivacyManager plugin + Custom logo ([Branding] section) stored its data in the DB rather than in the config file.
The ultimate goal is to make Piwik not need to write to the config file during normal operations.
The values from the option table should overwrite the values from the config in case the delete old data admin UI is enabled. It should not be possible to set a value in the option table while the delete old data admin UI is disabled.
Here are the config settings that, should be removed in favor of Option::
Note: