by Tim Williams.
Actually, this is worse than I thought, errors during execution of the external.php code are also suppressed, I've just had another one where all I get is a notice with the text of the error message, no line numbers and the underlying stack trace doesn't lead back to my code. All you see is:
PHP Notice: Undefined property: Error::$errorcode in /home/httpd/mdl33.dev1.autotrain.org/html/webservice/rest/locallib.php on line 153, referer: http://192.168.1.2:8100/
Fortunately in this case the text of the error message gave a strong indication as to the actual source of the error, since it referred to a mis-spelt method call which I can search for. Is there some kind of "webservices debugging" option I'm missing here that would give a proper stack trace? Suppressing error messages like this is just one element making MoodleMobile development more difficult than it needs to be.
PHP Notice: Undefined property: Error::$errorcode in /home/httpd/mdl33.dev1.autotrain.org/html/webservice/rest/locallib.php on line 153, referer: http://192.168.1.2:8100/
Fortunately in this case the text of the error message gave a strong indication as to the actual source of the error, since it referred to a mis-spelt method call which I can search for. Is there some kind of "webservices debugging" option I'm missing here that would give a proper stack trace? Suppressing error messages like this is just one element making MoodleMobile development more difficult than it needs to be.