![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 17 years ago
Closed 17 years ago
#9535 closed defect (bug) (fixed)
FTP plugin updates result in empty dirs
| Reported by: | demetris | Owned by: | ryan |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.8 |
| Component: | Plugins | Version: | 2.8 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
I noticed the problem in r10927.
It starts with r10919.
r10918 is OK.
I’m getting directories like these:
wp-content/plugins/wp-super-cache.0.9.3.1 (empty) wp-content/plugins/stray-quotes.1.9.4 (empty) wp-content/plugins/tangofy wp-content/plugins/tangofy/tangofy (empty)
The difference between the third plugin and the other two is that it declares “trunk” as its STABLE TAG.
PHP plugin update seems to be OK (tested on a different server setup). Only FTP update seems to have this problem.
Please let me know if you need any more information.
Change History (3)
Note:
See TracTickets
for help on using tickets.
Does reverting just the changes to ftpext and ftpsockets from r10919 help?