@robocoder opened this Issue on February 10th 2010 Contributor

Piwik should have a UI for superusers to override global.ini.php and/or change config.ini.php settings. Manually editing these files is out of character given Piwik's installation UI and Flash-y dashboard.

A list of such useful settings that could be made available via UI is:

  • default day when loading Piwik (today VS yesterday)
  • default period (day vs week vs ...)
  • always redirect to login screen, even if some websites are available to the anonymous user?
  • enable browser archiving trigger?
@mattab commented on February 11th 2010 Member

That makes sense. Before implementing this, though, we would need to think very carefully of the wording and which settings make sense to be available through the UI.

@mattab commented on March 21st 2010 Member

Actually, I would prefer to see specific tickets to add the UI for each setting that make sense to be "modified" in a UI. In particular, a lot of the settings currently in the config file would make sense to have a setting, but many wouldn't (too technical/rarely used).

Also, for settings that are currently in the config file but would be editable via the UI, it would be better to have them saved in the Option table.

Here are the settings I think should be editable in the UI, and stored in the Piwik_SetOption mechanism

; When loading piwik interface, we redirect the user to 'yesterday' statistics by default
; Possible values: yesterday, today, or any YYYY-MM-DD
default_day = yesterday
; Possible values: day, week, month, year
default_period = day

; When loading piwik interface, Piwik will load by default the CoreHome module
; You can override the setting to force the user to login. 
; This is useful when you have some websites view "anonymous" access but you want to 
; force users to login instead of viewing the first anonymous website available 
default_module_login = 0

; When loading the piwik interface in the browser (as opposed to from the PHP-CLI client)
; should we launch the archiving process if the archives have not yet been processed?
; You want to set it to 0 when triggering the archiving is done through a crontab, 
; so that your users do not trigger archiving in their browser when this is not expected
enable_browser_archiving_triggering = 1

I vote for closing this ticket and adding these settings in the UI, before 1.0. Am I missing some?


@robocoder commented on March 21st 2010 Contributor

Yes, only a subset of the config settings would be available through the UI. Why would we close this ticket just to open another one that says the same thing? Just change the milestone.

@robocoder commented on March 21st 2010 Contributor

We will eventually add timezone (and possibly campaign parameter) to the config UI but these shouldn't be in the option table for tracker performance reasons.

@mattab commented on March 22nd 2010 Member

Re timezone: see #5476; timezone can be stored in option as Tracker will always record dates in UTC. The archive queries will know about the timezone offset and select the right date ranges accordingly.

@mattab commented on March 22nd 2010 Member

Anthon, followed your advice, changed description and moved to 1.0 milestone

@mattab commented on April 1st 2010 Member

(In [2036]) * Added General settings page to: enable browser archiving, define today's archive time to live (fixes #1149)

  • added User settings page, that all logged in users can access to edit: Alias, email, default report to load, default date. Implemented settings in the _option table (rather than adding new fields to the table). Fixes #401 refs #526
  • the super user can edit settings for the anonymous user and force the anonymous to the login screen or a specific website
  • added order feature in admin menu + colored current menu + hiding menu entries that are not visible to the logged in user anyway
  • improved styles of admin forms
@mattab commented on April 2nd 2010 Member

(In [2041]) Refs #1149
enable browser archiving setting wasn't working

This Issue was closed on October 12th 2010
Powered by GitHub Issue Mirror