I already have plans to add a system check at installation.

In the meantime... your change might be considered a security vulnerability, ie locally exploitable session file hijacking.

Try chmod -R apache /your/piwik/folder

Sorry... I meant chown (not chmod).

Sadly, I can't chown files, I'm on shared hosting. My provider claims the alternatives are even less secure and wouldn't allow it anyway - there are arguments both ways, I know.

Glad to hear there are plans to address this, anyway. I defected to Google analytics for a while because of this, but it's just not the same.

If you were on a dedicated host, you could set apache's umask instead of using the hackish cron job. But on shared hosting, making your files world-writeable is a bad idea.

Your provider evidently hasn't heard of using phpsuexec for php-cgi (php runs under your user ID), or using php-fpm (which allows workers to be started with a different uid/gid or php.ini).

Id like to confirm this issue. I need to make FTP backups of my whole project folder, and my FTP client stops working when it encounters those files that are only readable by the owner.

gerritvanaaken: please use the forum for further followup (instead of commenting on a closed ticket). You can safely ignore files in the tmp folder when ftp-ing.