diff options
| author | Bill McGonigle <bill-github.com@bfccomputing.com> | 2022-06-14 14:10:29 +0300 |
|---|---|---|
| committer | backportbot-nextcloud[bot] <backportbot-nextcloud[bot]@users.noreply.github.com> | 2022-06-17 13:46:32 +0300 |
| commit | 8a3c19f894ddbbe59ccd730c74e56d48910618c4 (patch) | |
| tree | 0ee9c167960fccbf4b225b5ddafafe986bcfbc02 /apps | |
| parent | 7ffcca7e1f8293c1bd7e1df2e746b5f6294fd60f (diff) | |
Mention missing files subdirbackport/32874/stable22
Many users are getting confused by the inaccurate error message "Home storage for user $user not writable" because the storage *is* writable. The actual issue is a missing files/ subdirectory. cf. https://help.nextcloud.com/t/home-storage-for-user-not-writable/10831/7
By mentioning the possible cause in the error message, users are going to be able to rapidly solve their problem rather than bang their heads against the screen, Google, and eventually forums to find out that the error message is wrong in their case.
Yes, it would be better to detect and precisely describe the fault, or fix the problem automatically, but until then, be kind to the users for the next however many years.
Diffstat (limited to 'apps')
| -rw-r--r-- | apps/files/lib/Command/Scan.php | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/apps/files/lib/Command/Scan.php b/apps/files/lib/Command/Scan.php index ff96fbf2dab..70b87298612 100644 --- a/apps/files/lib/Command/Scan.php +++ b/apps/files/lib/Command/Scan.php @@ -143,7 +143,7 @@ class Scan extends Base { $scanner->scan($path, $recursive, $homeOnly ? [$this, 'filterHomeMount'] : null); } } catch (ForbiddenException $e) { - $output->writeln("<error>Home storage for user $user not writable</error>"); + $output->writeln("<error>Home storage for user $user not writable or 'files' subdirectory missing</error>"); $output->writeln('Make sure you\'re running the scan command only as the user the web server runs as'); } catch (InterruptedException $e) { # exit the function if ctrl-c has been pressed |