-
Bug
-
Resolution: Fixed
-
Major
-
4.0.6, 4.1
-
MOODLE_400_STABLE, MOODLE_401_STABLE
-
MOODLE_400_STABLE, MOODLE_401_STABLE
-
MDL-76873-401 -
-
WP Sprint 2023-I1.2 (David), WP Sprint 2023-I1.1 (David)
This was originally reported by a Workplace partner (see WP-4030, thanks dag), but should be fixed in LMS as the bug originates there
codingerror
|
Coding error detected, it must be fixed by a programmer: Invalid column name
|
File: ...ses/local/entities/base.php
|
Line: 252
|
Stack trace:
|
|
profilefield_visibleuta
|
Error code: codingerror
|
* line 252 of /reportbuilder/classes/local/entities/base.php: coding_exception thrown
|
* line 122 of /reportbuilder/classes/local/entities/user.php: call to core_reportbuilder\local\entities\base->get_column()
|
* line 89 of /reportbuilder/classes/local/systemreports/report_access_list.php: call to core_reportbuilder\local\entities\user->get_identity_column()
|
* line 61 of /reportbuilder/classes/local/systemreports/report_access_list.php: call to core_reportbuilder\local\systemreports\report_access_list->add_columns()
|
* line 102 of /reportbuilder/classes/local/report/base.php: call to core_reportbuilder\local\systemreports\report_access_list->initialise()
|
* line 70 of /reportbuilder/classes/system_report.php: call to core_reportbuilder\local\report\base->__construct()
|
* line 64 of /reportbuilder/classes/manager.php: call to core_reportbuilder\system_report->__construct()
|
* line 56 of /reportbuilder/classes/system_report_factory.php: call to core_reportbuilder\manager::get_report_from_persistent()
|
* line 46 of /reportbuilder/classes/output/dynamictabs/access.php: call to core_reportbuilder\system_report_factory::create()
|
* line 92 of /lib/classes/external/dynamic_tabs_get_content.php: call to core_reportbuilder\output\dynamictabs\access->export_for_template()
|
* line 261 of /lib/externallib.php: call to core\external\dynamic_tabs_get_content::execute()
|
* line 81 of /lib/ajax/service.php: call to external_api::call_external_function()
|
The problem occurs because Report builder inconsistently determines the visibility of a user profile field, and differs from the actual implementation within the profile field API
Note that the \core_user\fields class also ought to avoid re-implementing the same/similar logic (which Report builder calls) but that is currently a bit tricky because it's not at all easy or convenient to do so (we'll fix that too)
- caused a regression
-
MDL-77928 Changes to profile field signature causes fatal errors/documentation
-
- Open
-
-
MDL-77723 Exception when trying to load non-existing custom profile field
-
- Closed
-
- has been marked as being related by
-
MDL-83256 When a teacher exports participants list, it doesn't include custom profile fields
-
- Waiting for integration review
-