matomo-org/matomo

Plugins Directory Permissions Notification Persists after Fixing

Open

#12,934 opened on 2018年5月18日

GitHub で見る
 (3 comments) (0 reactions) (0 assignees)PHP (21,513 stars) (2,847 forks)batch import
BugHelp wanted

説明

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.

コントリビューターガイド

技術スタック
phpmysql
領域
backenddatabase
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
basic file permissions knowledgeMatomo basics
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
Investigate how Matomo checks plugin directory permissions and displays the notification. Look for caching mechanisms that might retain the error state after permissions are fixed. Check the relevant PHP files in the Matomo codebase, such as those in the 'plugins' or 'core' directories, and consider whether clearing cache or restarting services would resolve the issue.