#13741 closed defect (bug) (fixed)
Plugin Installation not working
| Reported by: | slaith | Owned by: | dd32 |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.0 |
| Component: | Upgrade/Install | Version: | 3.0 |
| Severity: | normal | Keywords: | reporter-feedback |
| Cc: | Focuses: |
Description
Whenever I try to install a plugin from within Wordpress admin interface, it says Plugin install failed. "Could not Create Directory. /". Now I understand how this might be a problem since / directory cannot be created. I looked in wp-config, and many other sources, could not find anything wrong. ABSPATH registers correctly, but this problem is still there
Attachments (1)
Change History (7)
#1
@
16 years ago
- Component Plugins → Upgrade/Install
- Keywords reporter-feedback added
- Milestone Unassigned → Future Release
- Owner changed from to
- Priority high → normal
- Severity major → normal
Did it work previously on this host?
Do you have to enter your FTP Credentials?
Do you have a 2.9.2 installation on the same host in the same style setup you can test?
If FTP, When you connect by FTP, what are the paths you see? Is WordPress installed in "/" when you connect by FTP, or something else such as /public_html/somehost.com/<WordPress files>
What path is ABSPATH set to?
Setting to Future Release pending confirmation of what the problem is.
#2
@
16 years ago
- Cc added
Someone experienced this problem the other day and came to the #wordpress irc channel. The end result was that they did not have a directory called wp-content/upgrade
Creating this directory manually and making it writable to the webserver user resolved the issue.
#3
@
16 years ago
The end result was that they did not have a directory called wp-content/upgrade
Creating this directory manually and making it writable to the webserver user resolved the issue.
Hm, That folder should be auto-created in all cases if it doesnt exist, I'll run a few tests to make sure thats still happening in edge-case environments shortly.
#4
@
16 years ago
Done. There was no folder called upgrade. I made one and everything seems fine. Thanks Sivel. Also just for info, I wasn't asked for FTP credentials, ever, and this is a new install. Perhaps you should ship the folder in the distribution itself, instead of having it auto-created? Just a suggestion
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
ScreenShot OF the Error