Remove rootpath in Internal Link Field

Question

In Internal Link field, Sitecore adds rootpath like "/sitecore/content" as prefix if I use the "Insert Link" button.

I would like to remove this. Is there a way to resolve this by updating .config file? or Do I have to include another config file to call process after Sitecore.Data.Fields.InternalLinkField.UpdateLink(), if it is right?

When I click the "Insert Link" button, "Insert Item" dialog pops up.

Answer 1

Internal Link is a System field type. Unless you're creating new Sitecore features, I'd recommend you switch to one of the following:

*Generallink Use this if your users can select both Sitecore Items and external URLs.

*Droplink Use this if you want to force the user to select a Sitecore Item.

These field types can be found under the "Linking" group when you define the Field on the Data Template.

Answer 2

Before you start remember that value you see in this field is the actual value of the field (this is true raw value of the field).

You will have to modify then two things:

• value of the field while saving
• logic for resolving the field value (getting item)

How to:

You need to create your own custom InternalLink

InternalLink.cs

using Sitecore.Data.Items;

namespace Sitecore.Custom.CustomFields.FieldTypes
{
    public class InternalLink : Shell.Applications.ContentEditor.InternalLink
    {
    }
}

Configuration

<?xml version="1.0" encoding="utf-8" ?>
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
    <sitecore>
        <controlSources>
            <source patch:before="*[@namespace='Sitecore.Shell.Applications.ContentEditor']" mode="on" namespace="Sitecore.Custom.CustomFields.FieldTypes" assembly="Sitecore.Custom" prefix="content"/>
        </controlSources>
    </sitecore>
</configuration>

You will need new implementation of:

protected void OpenLink(ClientPipelineArgs args)

method to handle your custom link format.

Answer 3

I don't really suggest to implement a custom field to change this because it is too painful. I think you should change the logic where this field is used and resolve there correctly.