]>
Commit | Line | Data |
---|---|---|
5b7effe1 | 1 | |
2 | Customizing WordPress plugins and themes | |
3 | in a default installation from PLD package. | |
4 | ||
5 | Pawel Wilk <siefca@gnu.org> | |
6 | ||
7 | Some WordPress plugins need customization by editing PHP | |
8 | files via web interface. Maybe there are also some CSS | |
9 | styles and/or theme files you would like to edit that way. | |
10 | However, in default PLD installation (from RPM package) | |
11 | all these files (plugins and themes and their respective | |
12 | directories) are writable only by their owner, which is root | |
13 | user. Additionaly the group which owns the files is a group, | |
14 | which web server uses by default (http), but the files and | |
15 | directories are only readable (searchable) by this group. | |
16 | ||
17 | If you would like to customize your WordPress site via the | |
18 | Web you should first let the owning group to write the | |
19 | files. You can set it up by invoking: /usr/bin/wp-setup or | |
20 | ./wp-setup.sh in your WordPress directory. | |
21 | ||
22 | When you finish you may want to revoke the ability to change | |
23 | by calling: /usr/bin/wp-secure or ./wp-secure.sh in the | |
24 | WordPress default installation directory. | |
25 | ||
26 | This simple routine is highly recommended when you have | |
27 | multiple dynamic sites running under the same parmissions | |
28 | and avoids bad users to overwrite your content files via | |
29 | nasty server-side scripts. | |
30 |