Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9230799
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T05:54:31+00:00 2026-06-18T05:54:31+00:00

I am working on moving the custom configuration settings for a Sitecore (6.2) project

  • 0

I am working on moving the custom configuration settings for a Sitecore (6.2) project into a separate App_Config\Include file. I am testing my changes using the sitecore page /sitecore/admin/ShowConfig.aspx. My question is what is the expected behaviour when using the <patch:delete /> element?

In my include file I have the following:

<setting name="Preview.DefaultSite">
  <patch:delete/>
</setting>

When I look at ShowConfig.aspx I see the following:

<setting name="Preview.DefaultSite" value="website">
  <delete/>
</setting>

Is this correct and expected behaviour, or should the <setting name="Preview.DefaultSite"> element completely disappear?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T05:54:32+00:00Added an answer on June 18, 2026 at 5:54 am

    The element should completely disappear and this works as expected for me in Sitecore 6.5 (update-5) and I know it worked in 6.4 as well.

    Which version of Sitecore are you using?

    All the patch attributes are mentioned here: All About web.config Include Files with the Sitecore ASP.NET CMS but the comments suggest some people had issues with this. This article from 2010 on web.config includes also mentions you cannot delete but like I said, it works in the newer versions.

    You could always patch the attribute to remove the value:

    <setting name="Preview.DefaultSite">
      <patch:attribute name="value"></patch:attribute>
    </setting>
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm working on moving an API project from raw http handlers where I'm using
I am working on some migration project, involves moving around quite a few stuff
I'm working on moving some files to a different directory in my project and
I'm working on moving as much logic out of a custom control as possible
I am working on a project which involves moving products around a virtual living
I am currently working on moving a large project over to use Common.Logging and
After moving a file into another directory I cannot display the differences between two
Am working on moving nodes in a tree, and as they are moved, their
At the place I am working we are moving to a more agile approach
We are moving to a process where multiple developers will be working on solutions

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.