Sitecore Corner

Sitecore Tips and Tricks


Switch Sitecore 7.2 Speak UI Media Browser to the good old Sheer UI Media Browser

I am posting this article as a follow up to the following SDN Topic – Sitecore 7.2: Delete image in media picker in page editor.

After upgrading to Sitecore 7.2 the content editors might complain about the new Speak UI Media Browser, as they would not find it as intuitive as the old one (or maybe they will have a hard time getting used to it). Fortunately there is a way to disable the new Speak Media Browser and switch to the good old Sheer one.

It can be achieved by disabling Speak overrideXmlControls in the Sitecore.Speak.config.

Create a custom configuration with the following code.

<?xml version="1.0" encoding="utf-8"?>
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
	<sitecore>
		<overrideXmlControls>
			<override xmlControl="Sitecore.Shell.Applications.Media.MediaBrowser" with="/sitecore/client/applications/Dialogs/SelectMediaDialog">
				<patch:delete />
			</override>
		</overrideXmlControls>
	</sitecore>
</configuration>

Keep in mind that the configuration file needs to be bellow the Sitecore.Speak.config in the Include folder otherwise the configuration file won’t work because the original Sitecore.Speak.config overrides won`t be registered (a good name will be z_Sitecore.Speak.Overrides.config).

The effects can be seen on the screenshots bellow.

Before:

Speak UI Media Browser
After:

Sheer UI Media Browser

You can also notice that Sitecore.Speak.config is the configuration file in which the old Sheer UI Dialogs were overridden by the new Speak UI Dialogs (under the overrideDialogs node). If you want to switch to the old Sheer Dialogs this is the place to do it.



4 responses to “Switch Sitecore 7.2 Speak UI Media Browser to the good old Sheer UI Media Browser”

  1. I’ve been to post something about this but nicely written. In terms of naming the patch config file, put it in a folder instead: http://jammykam.wordpress.com/2014/07/18/organising-your-sitecore-patch-include-files/

    Like

    1. Thanks for your feedback !

      I am not used to this approach because sometimes you want to attach before all the other includes passed (00_sitename.config) and sometimes after all the other config files passed (zz_sitename.config) I think this will be better for organizing stuff 🙂 As for the other configs I totally agree on a separate folder.

      Like

      1. Agree about order, you still have to do that even if you put in a separate folder, but at least you don’t have to worry about Sitecore order, just your own, which is often easier to manage 🙂

        Like

Leave a reply to jammykam Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.