I encountered the following error when installing a new plug-in (edited for details):<\/p>\n
Warning: include_once() [function.include]: Failed opening ‘##path-to-wordpress##<\/span><\/em>\/wp-content\/plugins\/twitter-for-wordpress\/’ for inclusion (include_path=’.:\/usr\/share\/php:\/usr\/share\/pear’) in ‘##path-to-wordpress##<\/em><\/span>\/wp-settings.php on line 473<\/p><\/blockquote>\n
I’d installed the plug-in “manually” (that is, downloaded it\u00c2\u00a0 and unzipped it into the plug-ins directory).\u00c2\u00a0 Some quick web searching didn’t exactly point to the error.\u00c2\u00a0 Nor did looking at the wp-settings.php file line 473 (just a straightforward directory include … of a directory that’s already been confirmed to exist!).<\/p>\n
Everything pointed to a permissions problem.\u00c2\u00a0 OK.\u00c2\u00a0 Checked the permissions … and they were, indeed, bad.\u00c2\u00a0 So I fixed up all the permissions (so that Apache and its friends could read the directory) … still the same error.\u00c2\u00a0 Even recycled Apache … still a problem.\u00c2\u00a0 Googling didn’t really help … one page was on point (but without a fix), and the rest of the hits were all on pages that were throwing this same error <g>.<\/p>\n
Turns out that once you’ve started a plug-in install, if your permissions are bad, you’re hosed.\u00c2\u00a0 You need to remove, then re-install the plug-in.\u00c2\u00a0 I did this, which fixed the problem:<\/p>\n
\n
- Moved the new plug-in directory out of the plugins folder.<\/li>\n
- Reloaded the admin plugins page … OK, error disappears.<\/li>\n
- Moved the new plug-in directory back in.<\/li>\n
- … voila, able to install and configure the plug-in.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
I encountered the following error when installing a new plug-in (edited for details): Warning: include_once() [function.include]: Failed opening ‘##path-to-wordpress##\/wp-content\/plugins\/twitter-for-wordpress\/’ for inclusion (include_path=’.:\/usr\/share\/php:\/usr\/share\/pear’) in ‘##path-to-wordpress##\/wp-settings.php on line 473 I’d installed the plug-in “manually” (that is, downloaded it\u00c2\u00a0 and unzipped it into the plug-ins directory).\u00c2\u00a0 Some quick web searching didn’t exactly point to the error.\u00c2\u00a0 Nor did … Continue reading “WordPress Plug-In Install Problem”<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[3,12],"_links":{"self":[{"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=\/wp\/v2\/posts\/4"}],"collection":[{"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4"}],"version-history":[{"count":3,"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=\/wp\/v2\/posts\/4\/revisions"}],"predecessor-version":[{"id":6,"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=\/wp\/v2\/posts\/4\/revisions\/6"}],"wp:attachment":[{"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/eggblog.invertedegg.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}