Serendipity Forums

This is why I said this was confusing and couldn't get located, since not all RC testers had this problem...

btw, in my 1.6.1 installs configuration - path, there are 2 fields for uploads/ dir. The first says Upload-Pfad (Relativ zum vollen Pfad - üblicherweise 'uploads/') and has the value "uploads/", the second says Relativer Upload-Pfad (relativ zum HTTP-Pfad) and also has the value "uploads/".

Should the second (for my path example) not contain "/blogs/serendipity/uploads/" ?
This is the same in the already upgraded to 1.7 system...

Can anyone check this please if having an installation in /serendipity or others?

Edit onli: Moved from http://board.s9y.org/viewtopic.php?f=3&t=19295

Is that in any way related to the issue at hand? I don't think so. Same values on my system btw, and I don't know your current HTTP-Path (uploads/ seems fine to me). If I didn't miss the connection, please cut that out here and make an own thread out of it.

ju wrote:I started reading this thread only after the update 1.6 to 1.7 and I can confirm that the "URL to Blog" field in http://www.example.com/serendipity_admi ... erendipity[adminModule]=configuration is empty. But up to now I haven't seen any negative consequences.

Please don't leave it empty. It has consequences now, as we have heard by those users having trouble with this issue. It is not intended to be left empty, even if it may have worked before! Values can be a relative (/) or as default the (http://path/).


------------------------------------------------------------------------------------------------

Timbalu wrote:btw, in my 1.6.1 installs configuration - path, there are 2 fields for uploads/ dir. The first says Upload-Pfad (Relativ zum vollen Pfad - üblicherweise 'uploads/') and has the value "uploads/", the second says Relativer Upload-Pfad (relativ zum HTTP-Pfad) and also has the value "uploads/".

Should the second (for my path example) not contain "/blogs/serendipity/uploads/" ?

[Closed]
Please reset this drop-in post! In both cases it is "uploads/" only, even in cases of directory blogs. The second value is to build and link the Serendipity ML Thumb-Images eg. uploads/name.serendipityThumb.jpg and needs to stick like this (at least for me on my local testings).

The question remains why we have two values of the same. Is there a case where this is different?

I think that one is the Path in the URL, the HTTP-Path, the other one is the path in the file-system.

onli wrote:I think that one is the Path in the URL, the HTTP-Path, the other one is the path in the file-system.

This.

It used for scenarios like supersized, where the upload folder is in a different filesystem location and uses apache/nginx handlers to map a URL to a different directory than it really is.

So by default, both urls would be identical and that's fine.

Regards,
Garvin