Ir a la última revisión | Autoría | Comparar con el anterior | Ultima modificación | Ver Log |
This files describes API changes in /availability/*.The information here is intended only for developers.=== 4.4.1 ===* The base class `info::get_groups` method has a `$userid` parameter to specify for which user you want to retrieve course groups (defaultsto current user)=== 4.3 ===* The `availability_info templatable` no longer exports 'showmore' information, and any component rendering avaialable_infoshould handle showmore/showless behaviour by itself.That means that 'showmorelink', 'hidden' and 'abbreviate' won't be exported for template in the root element neither its child items,and `core_availability/availability_more` module has beed deprecated=== 4.2 ===* The form for editing availability conditions now supports "private" conditions, that should not be shownto users. If a "private" condition is selected (as determined by the condition plugin), the whole rulesetwill be forcibly set to "Hidden entirely if student doesn't meet the conditions".* The group condition plugin will now treat any rule containing a group with a visibility setting other than`visibility:ALL` as private.=== 4.0 ===* Method render_core_availability_multiple_messages() is deprecated. Please use core_availability\\output\\multiple_messagesThe new rendereable will produce output with a 'more' link when there is lots of availability information.* There were existing restrictions on what condition plugins can do in the get_descriptionmethod (for example they mustn't call format_string), which were not well documented.New functions description_cm_name(), description_format_string(), description_callback()can be used so that condition plugins to behave correctly in all situations.=== 3.2 ===* Condition plugins must replace the CSS selector "#fitem_id_availabilityconditionsjson" with ".availability-field".This selector is often used in your plugin's yui/src/form/js/form.js file.=== 2.9 ===* Condition plugins can now implement a new include_after_restore function toindicate that they should be removed during the restore process. (This isimplemented so that group and grouping conditions are removed if groups arenot restored.)=== 2.8 ===* There is a new API function in the info_module/info_section objects (andrelated functions in internal API): get_user_list_sql. This returns SQL codethat does roughly the same as filter_user_list to return a list of users whoshould be shown as having access to the module or section.* Any third-party availability plugins which return true tois_applied_to_user_lists (and therefore previously implementedfilter_user_list) should now also implement get_user_list_sql. If notimplemented, a debugging warning will occur when anybody callsget_user_list_sql if the affected plugin is in use, and that user list willnot be filtered by the plugin.