-
Bug
-
Resolution: Fixed
-
Minor
-
4.4.5, 4.5.1
As reported in community forums, after uninstalling tool_moodlenet the Activity chooser footer (activitychooseractivefooter) configuration still points to the same plugin, which breaks the Add an activity or resource dialogue when editing courses. The following error is instead shown in the browser console:
15:13:44.776 Uncaught (in promise)
|
Object { message: "Coding error detected, it must be fixed by a programmer: Invalid component used in plugin/component_callback():tool_moodlenet", errorcode: "codingerror", backtrace: "* line 7474 of /lib/moodlelib.php: core\\exception\\coding_exception thrown\n* line 7417 of /lib/moodlelib.php: call to component_callback_exists()\n* line 4658 of /course/externallib.php: call to component_callback()\n* line ? of unknownfile: call to core_course_external::get_activity_chooser_footer()\n* line 253 of /lib/external/classes/external_api.php: call to call_user_func_array()\n* line 83 of /lib/ajax/service.php: call to core_external\\external_api::call_external_function()\n", link: "http://localhost:8000/course/view.php?id=2", moreinfourl: "https://docs.moodle.org/500/en/error/debug/codingerror", debuginfo: "\nError code: codingerror" }
|
|
backtrace: "* line 7474 of /lib/moodlelib.php: core\\exception\\coding_exception thrown\n* line 7417 of /lib/moodlelib.php: call to component_callback_exists()\n* line 4658 of /course/externallib.php: call to component_callback()\n* line ? of unknownfile: call to core_course_external::get_activity_chooser_footer()\n* line 253 of /lib/external/classes/external_api.php: call to call_user_func_array()\n* line 83 of /lib/ajax/service.php: call to core_external\\external_api::call_external_function()\n"
|
|
debuginfo: "\nError code: codingerror"
|
|
errorcode: "codingerror"
|
|
link: "http://localhost:8000/course/view.php?id=2"
|
|
message: "Coding error detected, it must be fixed by a programmer: Invalid component used in plugin/component_callback():tool_moodlenet"
|
|
moreinfourl: "https://docs.moodle.org/500/en/error/debug/codingerror"
|
|
<prototype>: Object { … }
|
first.js:1673:2173
|
The external method should be more resilient against stale/invalid site configuration and handle this more gracefully