Details
-
Bug
-
Resolution: Fixed
-
Minor
-
3.5.9, 3.6.7, 3.7.3, 3.8, 3.9.12, 3.11.5, 4.0
-
MOODLE_311_STABLE, MOODLE_35_STABLE, MOODLE_36_STABLE, MOODLE_37_STABLE, MOODLE_38_STABLE, MOODLE_39_STABLE, MOODLE_400_STABLE
-
MOODLE_311_STABLE
-
MDL-67428-filter-context -
Description
We have several customers who have quite expansive categories lists of courses, and naturally if you're on a course, the navigation will build the tree down to the point you're at, and typically will apply filters as well.
The problem we're seeing is that the navigation will apply the filtering by context and need to fetch many separate contexts to work out the filtering - in some cases this has amounted to hundreds of lookups to fetch filters.
I'm wondering if the solution to this problem is to have the navigation system only ever treat the filters as coming from the system context (or, instead, have this as an option) since if you're using multilang on titles, you probably need it at all contexts anyway (therefore having it in the system context doesn't make things significantly worse)
The worst cases for us are when users take a quiz and the quiz ends up producing hundreds of queries form each user for each page load, just to fetch the filters.