Tridion 2011 Publish Queue Shortcut

July 30th, 2012 | Posted by Robert Curlette in GUI Extension | Tridion 2011

Tridion 2011 provides shortcuts for several actions to navigate the tree view in the GUI and open items.  However, many other operations do not have a hotkey available, such as the Publish Queue.  During a normal day I open the Publish Queue many times, often from a Component or Page view.  I also have minimized the ribbon toolbar and finding the Publish Queue button is still an effort.  I wanted a shortcut key to assign to the Publish Queue to bring it up.  In this post I’ll explain how I added the hotkey to the Tridion GUI using a GUI Extension and provide a way for you to further customize it with your own hotkeys.

Code published at

Update:  Big thanks to @puf for the comments.  Code is updated to reflect them.

Step 1:  Create the Folder for the GUI Extension.  I created the folder for the GUI Extension:  C:\Program Files\Tridion\web\WebUI\Editors\Shortcuts

Step 2:  Add the js files

For this extension I am using an external js library called Mousetrap,  It is an excellent library, stand-alone, no dependencies, and only 1.6kb when minified.  This is important to know because the js library will load on every GUI view.

Create a js folder in the Shortcuts folder and put the mousetrap.min.js file there.

Step 3:  Adding our shortcut

Create another js file and call it mousekeys.js.  This is the place we’ll define our shortcuts and map them to GUI Javascript calls.

The below code was borrowed and adapted  from Albert Romkes excellent post about adding js files without showing a GUI element.


//If you only want your code to affect certain screens/views, you should listen to Anguilla events like this:
$evt.addEventHandler($display, "start", onDisplayStarted);

// This callback is called when any view has finished loading
function onDisplayStarted() {

	// Open Publish Queue dialog
	Mousetrap.bind('q', function() {
	                // UPDATE:  Below is the easy way to do it.  Make sure to update your Shortcuts.config to include the CME dependencies.  Big thanks to Frank van Puffelen (@puf) for the suggestion!

			//var popup = $popup.create($cme.Popups.PUBLISH_QUEUE.URL, $cme.Popups.PUBLISH_QUEUE.FEATURES);

    $evt.removeEventHandler($display, "start", onDisplayStarted);


   //if ($display.getView().getId() == "ComponentView") {
		//alert('comp view');

Step 4:  Finding the js call for the Tridion functionality

Using Firebug I inspected the Publish Queue button and then searched through the GUI js using Firebug Script window and found the code to open the Publish Dialog.  I feel lucky to have found it and that it worked.  🙂  This is not always so easy and you might want to do some research before planning on mapping a shortcut to a favorite functionality, like checking-in or checking-out TBBs.  (if you do figure out how to do this pls leave a comment!)  🙂  What other hotkey mappings would you like to see?

Step 5:  Create the config file for the extension

For me this was the first time using the domain model element within the config node.  It is a distinct difference between the normal method of having the cfg:file set node under the cfg:group node.


<?xml version="1.0" ?>
    Tridion Hotkeys Extension

    Copyright (C) 2012 Robert Curlette
<Configuration xmlns="" xmlns:cfg="" xmlns:ext="" xmlns:cmenu="">
  <resources cache="true">
      <cfg:group name="Curlette.Shortcuts" merger="Tridion.Web.UI.Core.Configuration.Resources.CommandGroupProcessor" merge="always">
          <cfg:domainmodel name="MousetrapDomain">
              <cfg:file type="script" id="mousetrapLib">/js/mousetrap.min.js</cfg:file>
              <cfg:file type="script" id="mouseKeys">/js/mousekeys.js</cfg:file>
            <cfg:services />
      <ext:editorextension target="CME">
        <ext:contextmenus />

Step 6:  Add the GUI Extension to the GUI
C:\Program Files\Tridion\web\WebUI\WebRoot\Configuration\System.config

<editor name="TridionShortcuts" xmlns="">
<installpath xmlns="">C:\Program Files\Tridion\web\WebUI\Editors\Shortcuts</installpath>
      <configuration xmlns="">Shortcuts.config</configuration>
      <vdir xmlns="">Shortcuts</vdir>

Step 7:  Flush browser cache and try it.

Press the ‘q’ key in any window.  The moustrap js library does not work if you are in a text box or an input element, even if you use the ctrl-q key instead of ‘q’ as a hokey.

Code published at


The GUI Extension framework allows us to easily enhance and enrich the User Experience using existing js libraries.  However, we should use care when adding libraries since they will be loaded with each GUI View and any errors in the js code will break the GUI.  To find out if your extension is breaking the gUI you can quicly comment it out in the System.config file and be back to normal very quickly.  I hope you enjoy using this and it makes it easier and quicker to view the Publish Queue.

You can follow any responses to this entry through the RSS 2.0 You can leave a response, or trackback.

3 Responses

  • Frank van Puffelen says:

    If you want to fire an existing command, I suggest doing exactly that: firing the existing command (instead of reproducing what happens when it fires).

    In this case it is really as easy as:


  • Frank van Puffelen says:

    Great extension, as usual Robert.

    In your step 7, you tell the user to clear the browser cache. This means that every user of the GUI will have to take action to get access to this great new shortcut.

    As a better alternative, please consider increasing the @Update number in the System.config. This number is used in the URL of every GUI request, so increasing the number means every browser will automatically get the latest version. This technique (known as URL fingerprinting) is quite common nowadays as it means your end users won’t have to take action to get the latest version of the resources: hit F5 and you’re up to date.

  • Angel Puntero says:

    Love it! Fantastic extension. This technique also makes me think of a lot of useful scenarios.

Leave a Reply

Your email address will not be published. Required fields are marked *