@ProCycleDev opened this Issue on May 18th 2018

Server: Ubuntu 16.04 running Nginx 10.3.3
Matomo version: 3.5.0
MySQL version: 10.2.14-MariaDB-10.2.14+maria~xenial-log
PHP version: 7.0.30-0ubuntu0.16.04.1

This error was encountered on a brand new install. The error only appeared after attempting to install a plugin. It was not present before that.

2018-05-18 12_34_47-procycle us - friday may 18 2018 - web analytics reports - matomo

Originally I had perms set so the plugins directory was read only by the webserver

chown -R manager:www-data web/
chmod -R u=rwX,g=rX,o= web/
chmod -R ug=rwX,o= web/tmp
chmod -R ug=rwX,o= web/config
chmod -R ug=rwX,o= web/piwik.js

After trying to install a plugin I got this error, so I fixed the permissions.

chown -R www-data:www-data web/
chmod ug=rwX,o= web/
chmod -R ug=rwX,o= web/plugins

The error message still popped up.

I set 777 for the entire web directory to test and still the error message shows.

2018-05-18 12_40_43-matomoadmin procycleus-matomo_ _srv_www_usage procycle us_web

So I installed the plugin I was trying to install before and it installs perfectly fine. The error message still shows.

I cannot get rid of the error message and I don't know why.

@robertgarrigos commented on September 7th 2018

I just found myself with this problem. The error disappears once you log out and log in again. But indeed it shouldn't persist for the session.

@NathanQ commented on August 23rd 2019

Where are the permissions documented? Thanks.

@tsteur commented on August 26th 2019 Member

cheers @robertgarrigos I had a look in the code and noticed it is setting the persistent notification here: https://github.com/matomo-org/matomo/blob/3.12.0-b2/plugins/Marketplace/Controller.php#L435

It is doing this because there's a redirect afterwards. I reckon it should indeed cancel all notifications once it was shown if we are not in an AJAX request 👍

We simply need to add another method cancelAll() and call removeNotification for all notifications. We would need to see though how to detect ajax requests vs regular request. I reckon there's a header set.

Powered by GitHub Issue Mirror