what's the "Subdirectory for site"?

Permalink
I just unzipped c5 into my public_html folder. so there's an index.php and a folder "concrete" in the root directory.

is the latter the "subdirectory" for the site even though that concrete basically is installed in the root (public_html) directory?

thanks

chris
 
andrew replied on at Permalink Reply
andrew
Usually the base url and subdirectory for site will be populated - I've never seen a server that wasn't able to automatically figure it out. So when in doubt you probably won't have to modify those values.

Subdirectory for site only applies if you're installing C5 into a subdirectory that's not at the top of a domain.

So, if you're installing C5 into

http://www.somedomain.com/mynewsite/...

and so the directory itself that you've unzipped C5 into is:

public_html/mynewsite/

Then the base url would be

http://www.somedomain.com

And the subdirectory for site would be

/mynewsite

Does that help?
chris replied on at Permalink Reply
chris
but according to that the helptext below the textfield for subdirectory is wrong:
"e.g.http://www.mysite.com/concrete/"...

it then should be
"e.g. /concrete/"

right?

thanks
dancobb replied on at Permalink Reply
dancobb
I think there might just be some confusion here. If the index.php file is in the root directory then the subdomain value will be blank because it thinks you want to install to the root.

The "concrete" folder that comes with the install is where all the standard non-custom files are stored to reference and build out the site.

If you dropped all the concrete zip contents into "public_html/test/" then the subdirectory would be auto populated as "/test/"
chris replied on at Permalink Reply
chris
this confirms my theory that the "hint"-text below the field is wrong.

it should read
"e.g. /subdir/" then - without http:// and domain.
andrew replied on at Permalink Reply
andrew
At one point those explanatory URLs weren't bolded, but the portions of the URLs themselves that corresponded to the thing being asked for (BASE_URL, etc...) were... but we lost that somewhere along the way.

We'll try and make it more clear (along with the fact that 99% of the time you won't need to change these values.