This is a dirty fix, but the tracker logging is too messy right now to make it correctly work with the logger. At least now it works.

Keep BC w/ old Formatter class since it is likely used by 3rd party plugins. Move Numeric formatter to CoreVisualizations and do not mark w/ @api.

I also replaced the check that does a request against Piwik to check
whether it is installed with `SettingsPiwik::isInstalled()` as discussed
recently

Fixes #7247, move default Formatter class to new Numeric metrics formatter and use in Graph visualization since jqplot requires numeric values in JSON data.

Hide error when reading the Plugins array, when this function is called before we have a config.ini.php file
fixes https://github.com/PiwikPRO/plugin-EnterpriseAdmin/issues/31

Sometimes, eg when module=API, we do not start a session. If any code
part during such a request uses SessionNamespace although we did not start
a session, Zend_Session_Namespace will start a Zend_Session which does not
respect our configuration. It would use default Zend Session options
and therefore probably file based sessions. Therefore, we force the
creation of a "Piwik session". If we have created the session before it
won't be started again.

Making algorithm processing unique visitors across websites actually work, refs https://github.com/PiwikPRO/plugin-MetaSites/issues/3

Fixes #7195 Make code more efficient by only updating the numeric archive tables (blob tables don't have `done` flags)

Since getLocalConfigInfoForHostname() is declared private, calling it with static will lead to errors in possible sub-classes. You can either use self, or increase the visibility of commandExists() to at least protected.

Since commandExists() is declared private, calling it with static will lead to errors in possible sub-classes. You can either use self, or increase the visibility of commandExists() to at least protected.

refs #4633 we should convert a segment value to a segment filter before queued filters are applied which allows us to use the prependSegment filter in combination with AddSegmentValue

refs #4633 actually it is not a good idea to generate a segment for subtables since they can belong to different repots and need different segments

refs #4633 a couple of code improvements eg we do not need to run a filter within a filter and run them recursive. not sure if recursive is a good idea though

refs #7104 make sure to close session for sparklines only when requested from dashboard or allwebsites

refs #7104 directly close session again to prevent any blocking when ajax requests are made within widget or when sparklines are requested