ansaurus

Question

Getting rid of Sitecore link prefix (sitecore/content/..)

Answer 1

A:

Is your

<setting name="Rendering.SiteResolving" value="true" />

set?

Mark Cassidy 2010-09-10 16:13:32

Yes - it is set to true (default value)

kastru 2010-09-10 20:27:41

Answer 2

A:

It's possible your config requires this... otherwise the links could be ambiguous. Are you linking to items across sites?

Bryan 2010-09-14 08:15:32

Answer 3

A:

Are your site definitions setup to use different values for the rootPath attribute?

<site name="mysite1" rootPath="/sitecore/content/mysite1" startItem="/home" hostName="mysite1.com" ... />
<site name="mysite2" rootPath="/sitecore/content/mysite2" startItem="/home" hostName="mysite2.com" ... />

Krisc 2010-09-14 13:41:24

Here's an example of a site.config:

kastru 2010-09-15 15:54:08

kastru 2010-09-15 15:55:54

See Bryan's question. Are you linking across sites? Do you see the same results if you write some code that uses LinkManager?

Krisc 2010-09-15 16:00:08

I am linking across 'internal' sites, but the problem occurs in all links (navigation, where xsl is used, links inserted in RTE etc.

kastru 2010-09-15 17:51:31

Had any usefull comments to this question yet? I'm having the same issue for some of our websites that use multiple site config with internal linking from one to another website.

Younes 2010-10-22 06:40:02

Have you tried using a piece of code to generate a URL with the SiteResolving option on? Sitecore may not be attempting to resolve the site's url and thus is including the full content path. In general, I use a method or two to generate all the internal URLs for the Sitecore sites. It essentially boils down to `options.SiteResolving = true; return LinkManager.GetItemUrl(item, options);`

Krisc 2010-10-22 10:45:29

ansaurus

tags:

views:

answers:

Getting rid of Sitecore link prefix (sitecore/content/..)

related questions