Moodle for mobile

Hi Tim,

that's weird. Can you send me the main.js and the handlers.js files in your plugin? You can send them to mobile@moodle.com. I'll check if I see why is it failing.

Cheers,

Dani

Picking this up again, I've had a major conference to run and other more pressing matters over the past month...

All I need is the data from the database tables associated with the module instance in order to construct the page I want locally, there shouldn't be any files returned to cache. From what I can tell the method in my external.php is called (but only when the cached version expires, how do I turn that cache off?) and it returns what looks like the correct data. I've also wiresharked the API call and the JSON that's sent looks correct to me when I compare it to the definition I wrote into export.php, but for whatever reason MoodleMobile seems to be incapable of reading this data and passing it back to my code.

So I'm still stuck at the point where the MoodleMobile code inexplicably fails with an undefined error. This is what the fetchContent method looks like:

function fetchContent(refresh) {
var downloadFailed = false;
// Download content. This function also loads module contents if needed.
return $mmaModMyModulePrefetchHandler.download(module, courseId).catch(function() {
// Mark download as failed but go on since the main files could have been downloaded.
downloadFailed = true;
if (!module.contents.length) {
// Try to load module contents for offline usage.
return $mmCourse.loadModuleContents(module, courseId);
}
}).then(function() {
var promises = [];
var getPagePromise;
// Get the module to get the latest title and description. Data should've been updated in download.
if ($scope.canGetPage) {
getPagePromise = $mmaModMyModule.getPageData(courseId, module.id);
} else {
getPagePromise = $mmCourse.getModule(module.id, courseId);
}
promises.push(getPagePromise.then(function(mod){
$scope.title = mod.name;
$scope.description = mod.intro || mod.description;
}).catch(function(error){
console.log("!!!! error: "+error);
// Ignore errors.
}));
// Get the page HTML.
console.log(module.contents+" "+module.id);
promises.push($mmaModMyModule.getPageHtml(module.contents, module.id).then(function(content) {
// All data obtained, now fill the context menu.
$mmCourseHelper.fillContextMenu($scope, module, courseId, refresh, mmaModMyModuleComponent);
$scope.content = content;
if (downloadFailed && $mmApp.isOnline()) {
// We could load the main file but the download failed. Show error message.
$mmUtil.showErrorModal('mm.core.errordownloadingsomefiles', true);
}
}));
return $q.all(promises);
}).catch(function(error) {
console.log("**** error: "+error);
$mmUtil.showErrorModalDefault(error, 'mma.mod_mymodule.errorwhileloadingthepage', true);
return $q.reject();
}).finally(function() {
$scope.loaded = true;
$scope.refreshIcon = 'ion-refresh';
});
}

When the code is run, the two console.log statements in the exception catches simply give a message reporting that an undefined error has been thrown. Without a meaningful error message or in-depth knowledge of the largely undocumented MoodleMobile code, tracing the source of the problem is virtually impossible.