-
Bug
-
Resolution: Fixed
-
Minor
-
3.11.8
-
MOODLE_311_STABLE
-
MOODLE_311_STABLE, MOODLE_400_STABLE
-
Same problem as that described in MDL-74100, for all forms using an autocomplete enhanced via 'core_user/form_user_selector' AJAX call, a user entering anything that Moodle considers "invalid" will trigger an exception
Example from webservices (same effect observed in Report builder forms):
invalidparameter
|
Invalid parameter value detected
|
File: /lib/externallib.php
|
Line: 366
|
Stack trace:
|
|
|
query => Invalid parameter value detected (Invalid external api parameter: the value is "<", the server was expecting "text" type): Invalid external api parameter: the value is "<", the server was expecting "text" type
|
Error code: invalidparameter
|
* line 366 of /lib/externallib.php: invalid_parameter_exception thrown
|
* line 240 of /lib/externallib.php: call to external_api::validate_parameters()
|
* line 81 of /lib/ajax/service.php: call to external_api::call_external_function()
|
query => Invalid parameter value detected (Invalid external api parameter: the value is "<", the server was expecting "text" type): Invalid external api parameter: the value is "<", the server was expecting "text" type
|
Error code: invalidparameter
|
* line 366 of /lib/externallib.php: invalid_parameter_exception thrown
|
* line 240 of /lib/externallib.php: call to external_api::validate_parameters()
|
* line 81 of /lib/ajax/service.php: call to external_api::call_external_function()
|
We can make this friendlier to the end user by avoiding showing confusing/unhelpful exceptions in the UI (defer parameter cleaning until later)
- has a non-specific relationship to
-
-
- Closed
-
