[wp-hackers] Proposal: standardize plugin-data path

[Stephen Rider]

It's NOT relative to the web root, that's the problem.  It's relative  
to ABSPATH.

If my WordPress files are at example.com/wp. then I MUST put the  
uploads folder somewhere within the wp/ directory.  I can't do  
example.com/uploads, for example.

Stephen

On Oct 1, 2008, at 8:18 AM, Otto wrote:

> I don't see any problem with leaving the uploads folder relative to
> root, since it is an explicit setting that the user can specify. In
> the settings page, it states that the default is wp-content/uploads,
> which is a ABSPATH relative path.
>
> I mean, what if you want the upload folder to be at
> example.com/wp/uploads/ instead? That's not relative to the wp-content
> folder.
>
> If you want it to be in wp-content and you move wp-content, then you
> need to move the upload folder location as well. It's already custom,
> we don't need to make it confusingly custom.
>
>
>
> On Wed, Oct 1, 2008 at 7:23 AM, Stephen Rider <wp-hackers at striderweb.com 
> > wrote:
>> It appears that the upload folder setting is parsed relative to  
>> ABSPATH,
>> rather than web root.  So, if I move wp-content out of the wp  
>> folder, it's
>> then impossible to set the uploads folder to be in wp-content...?
>>
>> Site is at example.com, but WP files are at example.com/wp.
>>
>> Contents folder is example.com/wp-content.
>>
>> Setting uploads folder to wp-content/uploads, that ends up pointing  
>> to
>> example.com/wp/wp-content/uploads/.  I want it to point to
>> example.com/wp-content/uploads/ instead....
>>
>> We've abstracted everything else so that people can move everything  
>> custom
>> (wp-content, wp-config.php) out of the folder with the actual WP  
>> files
>> (which makes updates soooooo much better thanks).  It appears we  
>> need to do
>> the same for the uploads folder.