You can do that as WordPress asks you for them. If you just want to fix it and not fiddle with plugins or fancy server altering techniques, the easiest way is just to provide your FTP details.
This can cause permission errors in some applications – for example, a PHP upload script.ġ Editor’s note: 404 link removed. Something that may be useful, Media Temple has an article called Run PHP with FastCGI 1 with a potential solution.īecause of the ownership that Plesk assigns to your website files and directories, Apache does not have permission to write to your web directories by default. By default, at least on the (dv) server, the ‘apache’ user doesn’t have write access to your web directories. The core of the issue is that when WordPress does these upgrades for you on your behalf, it is the server that is doing the work, which runs as the ‘apache’ user. As he explains it:įilesystem access is available, the files are owned by me, but the webserver doesn’t run as me, and thus, WordPress doesn’t detect the automatic update correcly.
Under the hoodĪ while back, Joost De Valk had the same problem and created a plugin that helped him and may help you. I don’t have experience with loads and loads of different hosts, but I can tell you that when hosting on Media Temple (gs), upgrades generally “just work”, but if you are using their more powerful (dv) service (which I definitely recommend), you’ll run into the FTP thing. Are you hosting your WordPress sites on one of those hosts where WordPress asks you to provide FTP details before upgrading itself or upgrading plugins? So when you click to do an upgrade, instead of just launching into the update process, you get a screen that looks like this instead:
0 kommentar(er)
