weekly release 3.8dev
[moodle.git] / search / upgrade.txt
1This files describes API changes in /search/*,
2information provided here is intended especially for developers.
4=== 3.7 ===
6* Search areas now have categories and can optionally implement get_category_names method to
7 display search results of the area in the required tab on the search results screen (if this
8 feature is enabled).
9* Added a new call back search_area_categories. Plugins can implement this method in lib.php and
10 return a list of custom search area categories (\core_search\area_category) and associated with
11 them search areas. This will bring additional custom tabs to the search results screen.
12* Added \core_search\manager::clean_up_non_existing_area method to clean up removed or renamed
13 search areas. To support that a new adhoc task core\task\clean_up_deleted_search_area_task
14 added.
25564a78 16=== 3.5 ===
18* Search areas may now optionally implement the get_contexts_to_reindex function (for modules and
19 blocks, see also get_contexts_to_reindex_extra_sql). This allows a search area to customise the
20 order in which it is reindexed when doing a gradual reindex, so as to reindex the most important
65da6840 21 contexts first. If not implemented, the default behaviour for modules and blocks is to reindex
22 the newest items first; for other types of search area it will just index the whole system
23 context, oldest data first.
fc440796 24* Search engines may now implement get_supported_orders function to provide multiple ordering
25 options (other than 'relevance' which is default). If there is more than one order then a choice
26 will be shown to users. (This is an optional feature, existing search engine plugins do not need
27 to be modified in order to continue working.)
4359ef18 28* Module search areas that wish to support group filtering should set the new optional search
29 document field groupid (note: to remain compatible with earlier versions, do this inside an if
30 statement so that it only happens on 3.4+) and return true to the supports_group_restriction
31 function. See documentation in \core_search\base_mod class and example in \mod_forum\search\post.
4359ef18 32* When a search engine supports group filtering, the \core_search\manager::search function now
33 accepts the optional 'groupids' parameter in its $data input. This parameter is an array of one
34 or more group IDs. If supplied, only results from those groups will be returned.
4359ef18 35* Search engine plugins will need to be be modified if they wish to support group filtering.
36 (Search engines should continue to work unmodified, but will not then support group filtering.)
37 The modification steps are:
38 - Implement the new update_schema function to make the schema change (add groupid field).
39 - Ensure that the groupid field is stored correctly when provided in a document while indexing.
40 - Return true to new supports_group_filtering() function.
41 - execute_query should support the new $data->groupids parameter (to allow users to restrict
42 search results to specific groups) and the modified meaning of the second parameter,
43 $accessinfo (to automatically restrict search results users cannot access due to groups).
44 See implementation in Solr search engine.
73fd5666 45* Search engine plugins can optionally use a new $this->should_skip_schema_check() function to
46 decide when to skip slow schema checking inside the is_server_ready function, improving user
47 performance on the search page. The Solr plugin implements this.
48* API function \core_search\manager::instance() now includes a $fast parameter to skip schema
49 checks (as above).
4359ef18 50
222a97ce 51* Search engines should now implement the 'userids' option to restrict search results to those from
52 specific users, and return true to the new supports_users() function. The supplied Solr search
53 engine includes this feature. If this is not implemented, the search engine will continue to work
54 but the 'Users' search option will not appear.
67d64795 56=== 3.4 ===
58* Search indexing now supports time limits to make the scheduled task run more neatly. In order for
59 this to work, search engine plugins will need to implement the 'stopat' parameter if they
60 override the add_documents() function, and return an extra parameter from this function (see base
61 class in engine.php). Unmodified plugins will still work, but without supporting time limits.
427b7563 62* Search areas should now implement the get_document_recordset function instead of the old
63 get_recordset_by_timestamp API (implement both if the area should work in older Moodle versions
64 as well). The new function is the same as the old one, but has an additional context parameter.
65 There is a helper function get_context_restriction_sql to make this easy to implement; see code
66 in base_activity.php for an example of how to implement this in your search area. (The
67 change was required to make search work after restoring sites. It also allows more flexible
68 reindexing in other cases.)
67d64795 69
70=== 3.2 ===
72* Base search area classes have been renamed, please update your search areas to use the classes below:
73 - \core_search\area\base has been renamed to \core_search\base
74 - \core_search\area\base_mod has been renamed to \core_search\base_mod
75 - \core_search\area\base_activity has been renamed to \core_search\base_activity