WordPress.org

Make WordPress Core

Opened 13 years ago

Closed 13 years ago

#7861 closed defect (bug) (fixed)

"Unable to locate WordPress directory." on core update & PHPDoc for WP_Filesystem_Base

Reported by: DD32 Owned by:
Milestone: 2.7 Priority: normal
Severity: normal Version: 2.7
Component: General Keywords: has-patch
Focuses: Cc:

Description

Attached patch does 2 things:

  • Moves sanitization for windows paths around a bit
  • Fixes trailing slash problems which caused "Unable to locate WordPress directory." on core upgrade attempts with FTP
  • Added PHPDoc for most of the class functions. (Hopefully the docs are inline with the rest of WP..)

Attachments (3)

7861.diff (6.9 KB) - added by DD32 13 years ago.
7861.2.diff (7.1 KB) - added by DD32 13 years ago.
7861.3.diff (1.1 KB) - added by ShaneF 13 years ago.

Download all attachments as: .zip

Change History (10)

@DD32
13 years ago

#1 @DD32
13 years ago

  • PHPDoc also adds correct sources for the helper functions

@DD32
13 years ago

#2 @DD32
13 years ago

attachment 7861.2.diff added.

  • Adds a check for situations where the FTP account is rooted to the base of the WordPress install (Which some security concious people do, and some webhosts do(when WordPress is installed into the base of the public_html folder))

#3 @azaozz
13 years ago

  • Resolution set to fixed
  • Status changed from new to closed

(In [9117]) Fix for "Unable to locate WordPress directory" on core update and PHPDoc for class-wp-filesystem-base.php, props DD32, fixes #7861

#4 @azaozz
13 years ago

(In [9118]) Check if the FTP account is rooted to the base of the WordPress install, props DD32, see #7861

#5 @ShaneF
13 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

@ShaneF
13 years ago

#6 @DD32
13 years ago

attachment 7861.3.diff added.

That fixes the issue outlined by Viper007Bond in #7872:

Downloading update from http://wordpress.org/nightly-builds/wordpress-latest.zip 
Unpacking the core update
Verifying the unpacked files
The update could not be unpacked
Installation Failed

#7 @azaozz
13 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

(In [9128]) Core update: fix for "The update could not be unpacked" error, props ShaneF, fixes #7861

Note: See TracTickets for help on using tickets.