With the release of WordPress 2.7 on 11th December, I was facing a problem: Manual plugin updates don’t seem to be provided for anymore. To date, I had always downloaded my plugins using the download link in the backend and then moved them to my server via FTP, because the automatic update had never worked for me – instead I always got the well-known error message “open basedir restriction in effect”. I always thought that was down to the configuration of my server and therefore outside my sphere of influence, and so I just put up with it.<\/p>\r\n\r\n
Now however, WordPress notifies you in the backend when new plugin updates are available, but there is no longer a direct download link to the .zip file. That would have meant that I had to search for every plugin on wordpress.org myself or visit the author’s website every time to download the current version as .zip file there. Extremely annoying! This gave me cause to go searching for a solution once more, and lo and behold, I found one on LastManStanding.de<\/a>.<\/p>\r\n\r\n\r\n\r\n Open your add the following:<\/p>\r\n\r\n It doesn’t matter what you name the subfolder of Now everything works as intended: Plugins as well as WordPress itself can now be updated with one simple mouse click! Incredibly comfortable!<\/p><\/del>","protected":false},"excerpt":{"rendered":"With the release of WordPress 2.7 on 11th December, I was facing a problem: Manual plugin updates don’t seem to be provided for anymore. To date, I had always downloaded my plugins using the download link in the backend and then moved them to my server via FTP, because the automatic update had never worked for me […]","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[77],"tags":[147,146,144,145,149,606,148],"_links":{"self":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/697"}],"collection":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/comments?post=697"}],"version-history":[{"count":5,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/697\/revisions"}],"predecessor-version":[{"id":814,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/697\/revisions\/814"}],"wp:attachment":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/media?parent=697"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/categories?post=697"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/tags?post=697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}wp-config.php<\/code>, and below (!)<\/em> the line<\/p>\r\n\r\n\r\ndefine('ABSPATH', dirname(__FILE__).'\/');\r\n<\/pre>\r\n\r\n\r\nputenv(\"TMPDIR=\" . ABSPATH . \"wp-content\/upgrade\");\r\ndefine('WP_TEMP_DIR', ABSPATH . \"wp-content\/upgrade\");\r\n<\/pre>\r\n\r\nwp-content<\/code>. I preferred the name “upgrade”, because in my case, WordPress itself had already created it with that name a while ago. But you could also name it “tmp”, as suggested on LastManStanding.de, or yet different. Note: The directory must of course exist, i. e. you have to create it if necessary, and WordPress must have writing permissions in that folder!<\/p>\r\n\r\n