Apex Code Development You need to sign in to do that
Don't have an account?
steven_noble Retaining directory structure with URL masking
With Force.com Site's URL masking, will the pages at companyname.force.com/dir_a and companyname.force.com/dir_b appear to be at companyname.com/dir_a and companyname.com/dir_b? Or will they appear to be at the top level of companyname.com, regardless of where they are in the site?
so for your example
mycompany.force.com/products
mycompany.force.com/press
would be different sites. So you would be able to leverage the path field to mimic your menu/folder structure. But you can only have up to 25 sites in the same org.
However, you won't be able to mask both sites with the same custom domain name. Each would need to have a unique custom domain name (if you want to use custom domains).
The main reason to have multiple sites is to target different audience, to have a different look and feel, different access settings, different authentication setup.
What you really need is the support for multiple level folder hierarchy within the same site which we do not support.
I hope this clarifies the topic.
All Answers
If you have a site like http://dellideas.force.com/ then
http://dellideas.force.com/resource/1231359401000/image_banner
and
http://www.ideastorm.com/resource/1231359401000/image_banner
will both preserve the path. Are you needing something more?
My idea obviously then is redundant.
I wonder why the product manager in the forums told me the directory structure wasn't retained?
I'll see if there's an easy way to archive this thread.
I must have misunderstood your question. I thought you are talking about site url which has the following format:
http://abc.force.com domain name/path
and you can use your own custom domain name like www.abc.com to mask this URL
I didn't realize your question was about the final url for the static resources used in site context
Imagine I use Force.com sites to publish a web site at mycompany.force.com.
I use Force.com sites to ensure users find this web site at mycompany.com.
My question is this: When users browse the site at mycompany.com, do they see the same menu structure in the URLs as they would if they browsed the site at mycompany.force.com?
For example, do they see mycompany.com/products/chairs/chair1.htm
From Ryan's contribution, I'd say the answer is yes, which is great news.
If you use force.com domain name you get to chose a path like abc.force.com/developer/page_name
if you use your custom domain name then the same example would be abc.force.com/page_name
# mycompany.force.com/tables = mycompany.com/tables
and
# mycompany.force.com/chairs = mycompany.com/chairs
but there can be no:
# mycompany.com/products/tables
because there can be no:
# mycompany.force.com/products/tables
correct?
so for your example
mycompany.force.com/products
mycompany.force.com/press
would be different sites. So you would be able to leverage the path field to mimic your menu/folder structure. But you can only have up to 25 sites in the same org.
However, you won't be able to mask both sites with the same custom domain name. Each would need to have a unique custom domain name (if you want to use custom domains).
The main reason to have multiple sites is to target different audience, to have a different look and feel, different access settings, different authentication setup.
What you really need is the support for multiple level folder hierarchy within the same site which we do not support.
I hope this clarifies the topic.
http://www.ideastorm.com/ideaView?id=087700000000F6sAAE#comments
If this is correct, then we're good to go. Thanks for sticking with me.
Sorry my previous explaination wasn't very clear.