| 1 |
efrain |
1 |
This files describes API changes in /availability/*.
|
|
|
2 |
|
|
|
3 |
The information here is intended only for developers.
|
|
|
4 |
|
|
|
5 |
=== 4.4.1 ===
|
|
|
6 |
* The base class `info::get_groups` method has a `$userid` parameter to specify for which user you want to retrieve course groups (defaults
|
|
|
7 |
to current user)
|
|
|
8 |
|
|
|
9 |
=== 4.3 ===
|
|
|
10 |
* The `availability_info templatable` no longer exports 'showmore' information, and any component rendering avaialable_info
|
|
|
11 |
should handle showmore/showless behaviour by itself.
|
|
|
12 |
That means that 'showmorelink', 'hidden' and 'abbreviate' won't be exported for template in the root element neither its child items,
|
|
|
13 |
and `core_availability/availability_more` module has beed deprecated
|
|
|
14 |
|
|
|
15 |
=== 4.2 ===
|
|
|
16 |
|
|
|
17 |
* The form for editing availability conditions now supports "private" conditions, that should not be shown
|
|
|
18 |
to users. If a "private" condition is selected (as determined by the condition plugin), the whole ruleset
|
|
|
19 |
will be forcibly set to "Hidden entirely if student doesn't meet the conditions".
|
|
|
20 |
* The group condition plugin will now treat any rule containing a group with a visibility setting other than
|
|
|
21 |
`visibility:ALL` as private.
|
|
|
22 |
|
|
|
23 |
=== 4.0 ===
|
|
|
24 |
|
|
|
25 |
* Method render_core_availability_multiple_messages() is deprecated. Please use core_availability\\output\\multiple_messages
|
|
|
26 |
The new rendereable will produce output with a 'more' link when there is lots of availability information.
|
|
|
27 |
* There were existing restrictions on what condition plugins can do in the get_description
|
|
|
28 |
method (for example they mustn't call format_string), which were not well documented.
|
|
|
29 |
New functions description_cm_name(), description_format_string(), description_callback()
|
|
|
30 |
can be used so that condition plugins to behave correctly in all situations.
|
|
|
31 |
|
|
|
32 |
=== 3.2 ===
|
|
|
33 |
|
|
|
34 |
* Condition plugins must replace the CSS selector "#fitem_id_availabilityconditionsjson" with ".availability-field".
|
|
|
35 |
This selector is often used in your plugin's yui/src/form/js/form.js file.
|
|
|
36 |
|
|
|
37 |
=== 2.9 ===
|
|
|
38 |
|
|
|
39 |
* Condition plugins can now implement a new include_after_restore function to
|
|
|
40 |
indicate that they should be removed during the restore process. (This is
|
|
|
41 |
implemented so that group and grouping conditions are removed if groups are
|
|
|
42 |
not restored.)
|
|
|
43 |
|
|
|
44 |
=== 2.8 ===
|
|
|
45 |
|
|
|
46 |
* There is a new API function in the info_module/info_section objects (and
|
|
|
47 |
related functions in internal API): get_user_list_sql. This returns SQL code
|
|
|
48 |
that does roughly the same as filter_user_list to return a list of users who
|
|
|
49 |
should be shown as having access to the module or section.
|
|
|
50 |
|
|
|
51 |
* Any third-party availability plugins which return true to
|
|
|
52 |
is_applied_to_user_lists (and therefore previously implemented
|
|
|
53 |
filter_user_list) should now also implement get_user_list_sql. If not
|
|
|
54 |
implemented, a debugging warning will occur when anybody calls
|
|
|
55 |
get_user_list_sql if the affected plugin is in use, and that user list will
|
|
|
56 |
not be filtered by the plugin.
|