@@ -37,6 +37,39 @@ The updater is currently performing the following steps. If one of those steps f
373716 . Deauthenticate updater session
383817 . Redirect to the phpList dashboard
3939
40+ ### Permissions
41+
42+ The whole phpList directory and the files within it must be writable by the HTTP user under which your web server is running as.
43+ If there is no match between the owner of your phpList files and the user under which your web server is running, you won’t be able to update.
44+ The ownership can be changed in a Linux terminal using this command:
45+
46+ <pre > chown -R user:group /path/to/phpList-directory </pre >
47+
48+ For instance:
49+
50+ <pre > chown -R www-data:www-data /var/www/lists </pre >
51+
52+ Change directory and file permissions:
53+
54+ <pre > find . -type d -exec chmod 755 {} \; </pre >
55+ <pre > find . -type f -exec chmod 644 {} \; </pre >
56+
57+ Permissions vary from host to host. To find the HTTP user check the Apache Server configuration files.
58+ You can view a file's ownership, permissions, and other important information with the ls command, using the -la option:
59+
60+ <pre > ls -la file.php </pre >
61+
62+ The default Apache user and group for some Linux distributions are:
63+
64+ - Debian/Ubuntu: www-data
65+ - Arch Linux: http
66+ - Fedora/CentOS: apache
67+ - openSUSE: user is wwwrun and the group is www.
68+
69+ After you change the permissions, you can try again the update.
70+ After a successful update, please consider to re-apply any hardened directory permissions.
71+
72+
4073### What the updater doesn't do (yet):
4174
4275The updater is at the moment solely focused on replacing the files of the core installation. It does neither:
0 commit comments