I must apologise for how slow I am this morning. It feels like I need a holiday to recover from the weekend :) So I am sorry if my question makes no sense.

On opening the CMS, and entering into the Content> Meta Data tab, there is a a label of URL and underneath a textfield, of which only part is editable. The uneditable part contains www.yoursite.com/. The editable part is empty.

When I extract the Silverstripe folder on the server, it extracts to a folder called silverstripe-v2.2.1. Now, that is in direct conflict with the URL schema directly input through the CMS (as mentioned above). Does Silverstripe automatically deal with this?

Also, if I create a new folder, eg. CMS, in the public_html root, and place the tarball into the CMS folder, it then extracts out so that access to the CMS itself is akin to this: www.yoursite.com/CMS/silverstripe-v2.2.1/contact/.

I wouldn't want visitors to see such an ugly URI, I would much rather it appeared as suggested in the CMS itself, www.yoursite.com/contact/ .

Does Silverstripe handle this all by itself, or do I need to help it along with a mod_rewrite command?

Thanks!

Let me rephrase my question:

Through the CMS, it appears that the URL will be www.yourdomain.com/pagename, however, when you install the CMS under a sub-directory and check out the published page, it instead appears as

www.domain.com/subdirectory/silverstripe/pagename.

How do I make the URL appear as through the CMS? Do I need to mess about with mod_rewrite?

Well, you don't need the 'silverstripe-v2.2.1' directory, you can have the contents of that directory in whatever directory you like. Or is that not what you meant?

How do I extract and/or install Silverstripe without the default Silverstripe directory?

Well, for instance, you just extract the silverstripe-v2.2.0.tar.gz on your desktop and (s)ftp the contents of the then created silverstripe directory into whatever directory you want on the server... does this help you or are we talking about different things perhaps?

So, if you just copy the contents of the ss folder into www.yourserver.com/testdir/ then the CMS would work from within testdir...

(edited for spelling)