Covered Content Editor

Popout Page Editor Content Editor

Posted 07/10/2013 by sconnall

If you are somebody who is more interested in the answer than how to find it, then you’re in luck:

The skinny:
            Indicates whether WebEdit uses the popup content editor.
            Default value: false   -->
      <setting name="WebEdit.UsePopupContentEditor" value="true"/>

However, if you would like to see how I was able to find the solution and other ways to go about fixing it please continue.

Tools necessary to follow along: Program capable of decompiling DLL’s.


  • Reflector (Paid) from Red Gate
  • JustDecompile (Free) from Telrik
  • dotPeek (Free) from Jetbrains

Whether due to your own style of coding CSS or having to use another company’s layout, there comes a time when the Content Editor, called from the “Edit Related Item” Edit Frame Button, may not work very well because of z-indexing or absolution positioning.

Due to the way the HTML, CSS, and JS was written the content editor is being hidden behind much of the layout.


First thing to do is determine if there is an alternate way to show the content editor. The best way to do this is to find the code that is called on button click and give it a quick scan to see if there is already a way.

To find the button command, check in the Core database under:
/sitecore/content/Applications/WebEdit/Edit Frame Buttons/Default/Edit related item for the “Click” field.
“chrome:common:edititem” is unimportant for what we’re looking for, but it is basically calling the bit inside the curly brackets. So we want to look for the command attached to “webedit:open”.

Built in commands exist in the command.config under the app_config folder. Checking the entry in this file will show to check this class: Sitecore.Shell.Applications.WebEdit.Commands.Open,Sitecore.Client

Checking that button’s command through your decompile software you can see that it has the ability to show the Content Editor in a pop up instead of taking up half the browser window. Digging deeper into the code shows that it uses the two forms of checks to determine whether to show it as a pop-up.

  1. If the browser running is IE and the major version is greater than 8.
  2. OR the registry for key “Current_User/UserOptions.WebEdit.UsePopupContentEditor” is set to true

The last part to look at is the getter of the property, as it is using Settings.WebEdit.UsePopupContentEditor as a default to determine whether to show it or not. Looking at that property will net you:
return Settings.GetBoolSetting("WebEdit.UsePopupContentEditor", false);

Jumping into the Web.Config and scrolling into the properties you’ll find the previously mentioned setting. Update this through an include config file and everything should run as expected.