Try our conversational search powered by Generative AI!

Catalogue view fails with custom dijit after upgrade to 7.19.1/8.7.1


We've upgraded our solution to EPiServer 7.19.1 and Commerce 8.7.1 and now we can't load the catalogue view, the cause behind the error that is thrown is our custom dijit, which was working before the upgrade. The error is only occuring randomly. If we outcomment the custom dijit it is working.

Following errors is thrown in firebug:

Error: Could not resolve dependency "epi.globalcommandregistry" (epi.dependency)

.cache["epi-cms/CMSModule"]/<.initialize@http: spsm.local hittalaromedel spsm manage cms clientresources epi-cms widgets.js:2:9929>
.cache["epi/ModuleManager"]/<._runmoduleinitializer><@http: spsm.local hittalaromedel spsm manage shell clientresources epi epi.js:2:8779>
.cache["dojo/_base/lang"]/<@http: spsm.local hittalaromedel spsm manage shell clientresources dojo dojo.js:15:30898>
_7c/<@http: spsm.local hittalaromedel spsm manage shell clientresources dojo dojo.js:15:13239>

Sometimes only the first error is thrown and then the catalogue view loads correctly, and then the second error is occuring and the catalogue view fails.

The custom dijit looks like this:


], function (
) {
    var handle,
        registry = dependency.resolve('epi.globalcommandregistry'),
        callback = function (identifier, provider) {
            if (identifier !== 'epi.cms.globalToolbar') {
            provider.addCommand(new EmailUpdateCommand(), { showLabel: true, id: "EmailUpdateCommand", disabled: false });


    handle = aspect.after(registry, 'registerProvider', callback, true);

EmailUpdateCommand is another js file, and the value from the log above is 3(!), and in Chrome I'm getting:

TypeError: number is not a function

Any ideas why code above fails after the upgrade?


Feb 10, 2015 16:28
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.