Moodle for mobile

Hey Dani,

Thanks for your reply. I surmised from the code and another thread i found that the content handler must be registered with the course delegate module. I have been looking into this and as far as I can tell, the structure of my plugin is correct, but something is missing in wiring up the components. Maybe something here will look familiar or another forum member will know the anwer.

In my main.js file, I register the content handler like so (I am basically just copying what the url module is doing to get a simple working example):

.config(function($mmCourseDelegateProvider, $mmContentLinksDelegateProvider) {
  $mmCourseDelegateProvider.registerContentHandler('mmaModZoom', 'zoom', '$mmaModZoomHandlers.courseContent');

  // Register content links handler.
  $mmContentLinksDelegateProvider.registerLinkHandler('mmaModZoom', '$mmaModZoomHandlers.linksHandler');

});

So that should make the plugin system look for a '$mmaModZoomHandlers' content handler factory, right? Using that, it should then call `getController` to find the controller file in controllers/index.js, which I've named 'mmaModZoomIndexCtrl' following the naming convention (where is this name actually determined?). The controller then gets the main module '$mmaModZoom' injected as an argument, which we can then call into and return data from the web service endpoint. Makes sense to me so far.

However, when `getContentHandlerControllerFor` gets called, I noticed that the module is *not* in the registered set of `enabledHandlers`. The app still thinks that the module is disabled. When the "modcontent.html" template gets rendered to show the user a message about a non-supported plugin, the following permissions flags are set:

isDisabledOnSite = false
isSupportedByTheApp = true
isContributedPlugin = false

My main module '$mmaModZoom' has the following methods stubbed out to true just to force it to be enabled:

self.isGetUrlWSAvailable = function() {
  return true;
    // return $mmSite.wsAvailable(ZOOM_GET_STATE);
};

self.isPluginEnabled = function(siteId) {
  return true;
  // return $mmSitesManager.getSite(siteId).then(function(site) {
  //   // All WS were introduced at the same time so checking one is enough.
  //   return site.wsAvailable(ZOOM_GET_STATE);
  // });
};

Still no dice. The plugin is considered disabled for some reason, and my content handler gets removed from the list of "enabledHandlers" by the time the view is rendered.

Does any of this ring a bell? I really just want to stub out all this permissions code for now so I can get a very simple empty module to appear on the screen.

Thanks