-
Bug
-
Resolution: Fixed
-
Major
-
3.2, 3.4
-
MOODLE_32_STABLE, MOODLE_34_STABLE
-
MOODLE_34_STABLE
-
MDL-55356-master -
I thought we already had an issue about this, I haven't found it so I assume that I didn't create it.
Global search is indexing contents by timestamp through get_recordset_by_timestamp(), but restored contents are using the original records timestamps so these contents are not indexed.
This is a known limitation of Moodle 3.1 search API, the API should be extended to allow components to get records data from a list of ids (search area's itemid which is the unique identifier at search area level) so during restore we can flag activities and moodle subsystems elements that will later need to be indexed. A cron task can go through this list of items to index, execute this new search areas function (e.g. get_records_by_ids) and pass the records through get_docuement like we do with get_recordset_by_timestamp() when indexing by timestamp.
- caused a regression
-
MDL-61913 Restoring (or importing) blocks with Global Search enabled can lead to fatal error
- Closed
-
MDL-61824 Restored contexts waiting to be indexed may be already deleted
- Closed
- has a non-specific relationship to
-
MDL-58957 Global search: Make it possible to search blocks
- Closed