@tsteur opened this Pull Request on September 7th 2019 Member

fix https://github.com/matomo-org/matomo/issues/13037

As user described in the issue the user path behaviour didn't quite make sense. For example in an update we copied over config/global.php and config/global.ini.php to the user path. This may fail though due to write permission and is generally not needed cause the only files it should load from there is config/config.php and config/config.ini.php and config/common.config.ini.php.

This makes things a lot simpler and now there is an easy way to put the config file outside Matomo webroot.

Should probably also create an FAQ for this afterwards.

@mattab commented on October 25th 2019 Member

Should probably also create an FAQ for this afterwards.

@tsteur if you have a FAQ draft let me know, happy to publish it :+1:

@tsteur commented on October 25th 2019 Member

It was already there kind of

@florianjacob commented on November 3rd 2019 Contributor

This made it impossible to use PIWIK_USER_PATH as an instance-specific writable location, separated from a shared, read-only PIWIK_DOCUMENT_ROOT: https://github.com/matomo-org/matomo/issues/15087

This Pull Request was closed on September 17th 2019
Powered by GitHub Issue Mirror