In reference to my previous question (javascript is not hitting from configuration file in GUI Extension), I have applied Config changes and js changes as I got in my old question answer still I am getting this error in Browser Console.

What does it mean and how can I resolve it? What is the cause of this?

Warning :Command is not registered

My latest Config


    ?xml version="1.0"?>
    <Configuration xmlns="http://www.sdltridion.com/2009/GUI/Configuration/Merge" xmlns:cfg="http://www.sdltridion.com/2009/GUI/Configuration" xmlns:ext="http://www.sdltridion.com/2009/GUI/extensions" xmlns:cmenu="http://www.sdltridion.com/2009/GUI/extensions/ContextMenu">
      <resources cache="false">
          <cfg:group name="Counter.Commands" merger="Tridion.Web.UI.Core.Configuration.Resources.CommandGroupProcessor"  merge="always">
              <cfg:file type="script">/Counter/Counter.js</cfg:file>
              <cfg:file type="reference">Counter.CommandSet</cfg:file>
          <ext:editorextension target="CME">
            <ext:editurls />
            <ext:commands />
                <ext:extension name="Counter" assignid="ext_Counter" insertbefore="cm_refresh">
                  <ext:menudeclaration externaldefinition="">
                    <cmenu:ContextMenuItem id="ext_Counter" name="Count:" command="CounterCommand"/>
                    <ext:view name="DashboardView"/>
        <cfg:commandset id="Counter.CommandSet">
        <cfg:command name="CounterCommand" implementation="Extensions.Counter"/>
  • Why does resource group Counter.Commands have a reference to Counter.CommandSet? I just see that Counter.CommandSet has a dependency on Counter.Commands and I do not know how Tridion handles this circular dependency. Commented Aug 21, 2014 at 8:03

1 Answer 1


That error means that some code is calling executeCommand with the name of a command that either hasn't been registered or doesn't implement the "Tridion.Core.Command" interface.

Commands are automatically registered when defined in the configuration, and the code in your other question seems to implement the correct interface, so I would say that the problem is likely that it is still not configured correctly.

New commands will need to be registered in the <commands> section of your Editor configuration file. If you need assistance with that, you'll need to post your updated configuration XML so that we can point out the problem.

Try double-checking that you've followed the steps outlined in the documentation for creating a new command.

  • hi peter please check latest config
    – Pankaj786
    Commented Aug 21, 2014 at 4:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.