���ѧۧݧ�ӧ�� �ާ֧ߧ֧էا֧� - ���֧էѧܧ�ڧ��ӧѧ�� - /home3/cpr76684/public_html/upgrade.txt.tar
���ѧ٧ѧ�
home3/cpr76684/public_html/Aem/admin/tool/lp/upgrade.txt 0000644 00000001302 15151222500 0016623 0 ustar 00 This files describes changes in /admin/tool/lp/* - plugins, information provided here is intended especially for developers. === 3.3 === * Deprecated classes and their new equivalent: - tool_lp\external\cohort_summary_exporter -> core_cohort\external\cohort_summary_exporter - tool_lp\external\course_summary_exporter -> core_course\external\course_summary_exporter - tool_lp\external\course_module_summary_exporter -> core_course\external\course_module_summary_exporter === 3.2 === * The icon 'competency.png/svg' has been removed, please use i/competencies instead. === 3.1.1 === * The plugin icon 'competency.png/svg' will be removed in the future use i/competencies instead. home3/cpr76684/public_html/Aem/availability/upgrade.txt 0000644 00000003502 15151251372 0016632 0 ustar 00 This files describes API changes in /availability/*. The information here is intended only for developers. === 4.0 === * Method render_core_availability_multiple_messages() is deprecated. Please use core_availability\\output\\multiple_messages The 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_description method (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 to indicate that they should be removed during the restore process. (This is implemented so that group and grouping conditions are removed if groups are not restored.) === 2.8 === * There is a new API function in the info_module/info_section objects (and related functions in internal API): get_user_list_sql. This returns SQL code that does roughly the same as filter_user_list to return a list of users who should be shown as having access to the module or section. * Any third-party availability plugins which return true to is_applied_to_user_lists (and therefore previously implemented filter_user_list) should now also implement get_user_list_sql. If not implemented, a debugging warning will occur when anybody calls get_user_list_sql if the affected plugin is in use, and that user list will not be filtered by the plugin. home3/cpr76684/public_html/Aem/blocks/calendar_upcoming/upgrade.txt 0000644 00000000336 15151251664 0021115 0 ustar 00 === 3.4 === * block_calendar_upcoming::get_upcoming_content has been deprecated. Please update your code to use the new APIs. You can see an example of how these may be used in block_calendar_upcoming::get_content(). home3/cpr76684/public_html/Aem/theme/upgrade.txt 0000644 00000066661 15152001014 0015264 0 ustar 00 This files describes API changes in /theme/* themes, information provided here is intended especially for theme designer. === 4.1 === * The function core_course_renderer::course_modchooser() has been finally deprecated and can not be used anymore. Please use core_course_renderer::course_activitychooser() instead. * $OUTPUT->favicon() now returns the URL of the configurable favicon if present. * The body tag include a class with module name specific for each activity E.g.: cm-type-page === 4.0 === * A new theme config 'removedprimarynavitems' allows a theme to customise primary navigation by specifying the list of items to remove. * A new theme config 'usescourseindex' allows a theme to specify whether it implements and uses course index. * A new theme setting 'unaddableblocks' allows admins to define the blocks that won't be displayed in the "Add a block" list. === 3.11 === * The classname 'viewmode-cobmined' in course/management.php has been changed to 'viewmode-combined' === 3.10 === * The Bootstrap legacy css utilities from Bootstrap 2 and 4alpha have been removed. The syntax for the new Bootstrap 4.5 utility classes is {property}{sides}-{breakpoint}-{size} for sm, md, lg, and xl. The size values are: 1: 0.25rem 2: 0.5rem 3: 1rem 4: 1.5rem 5: 2rem 6: 3rem In Bootstrap 4alpa a spacing utility class '.m-l-1' would mean margin-left 1rem. With the new spacing classes it should now be '.ml-3' These class names have changed: .row-fluid is now .row .text-error is now .text-danger These classes should no longer be used: .label .label-{type}, use .badge .badge-{type} instead .tag .tag-{type}, use .badge .badge-{type} instead .well, just set a border with .border and a background with .bg-light === 3.9 === * Add class .d-print-block to #page, #page-wrapper and #page content to fix Firefox printing problems * A function to core_renderer has been added, secure_layout_login_info. This allows the boost and classic templates to display the users full name in a secure layout. * Secure layout in themes boost and classic have been modified to allow language selection as they now call the output.secure_layout_language_menu function. === 3.8 === * Moodle does not produce chunked CSS anymore, instead an unique css fils is generated and served (MDL-55751). This implies: * css_chunk_by_selector_count() has been removed. * css_store_css(), theme_styles_get_filename() and theme_styles_get_etag() don't accept any chunk-related param anymore. * The PHP Less compilier has now been removed from the core library. Please consider migrating your theme to use SCSS. * It is now possible to use sub-directories when creating mustache templates. The standard rules for Level 2 namespaces also apply to templates. The sub-directory used must be either an valid component, or placed inside a 'local' directory to ensure that it does not conflict with other components. The following are all valid template names and locations in your theme: theme_themename/columns2: theme/[themename]/templates/columns2.mustache theme_themename/local/layouts/columns2: theme/[themename]/templates/local/layouts/columns2.mustache The following are core templates, locations, and override locations in your theme: core/modal: lib/templates/modal.mustache => theme/[themename]/templates/core/modal.mustache mod_forum/forum_post: mod/forum/templates/forum_post.mustache => theme/[themename]/templates/mod_forum/forum_post.mustache mod_forum/local/post/user: mod/forum/templates/local/post/user.mustache => theme/[themename]/templates/mod_forum/local/post/user.mustache The following are _invalid_ template names and locations: theme_themename/layouts/columns2: theme/[themename]/layouts/columns2.mustache === 3.7 === * The core/form_autocompelte_input template now has a `data-tags` attribute. * Boost theme renderer overrides have now been migrated to core. * Renderers that were overridden by Boost are now in Bootstrapbase * Core templates in Boost have now moved into core * Templates that were overridden by boost are now located in Bootstrapbase * Themes bootstrapbase, clean & more have now been removed. === 3.6 === * A new callback has been added to the theme layout files allowing plugins to inject their content into the page. For Boost it was added as a mustache variable "{{{ output.standard_after_main_region_html }}}" in templates/columns1.mustache and templates/columns2.mustache. In bootstrapbase it was added as a function call "$OUTPUT->standard_after_main_region_html()" in layout/columns1.php, layout/columns2.php. and layout/columns3.php. Child themes not inheriting these templates should add the function call after the div containing the main content region. Please refer to the messaging drawer UI for an example of making use of this new feature. * The body tag has various browser-specific classes for those cases where some browser-sniffing is unavoidable. This used not to recognised Microsoft Edge, but now it does (class 'edge'). Also, both Safari and Chrome used to be class 'safari', but now there are separate classes 'safari' and 'chrome'. The body's class should change to match the browser: - Google Chrome (Mac & Window): The body class should change from safari to chrome. - Google Chrome (Android) : The body class should change from safari, android to chrome, android. - Microsoft Edge: The body class should change from safari to edge. - Mobile safari: The class ios should exist, safari class should be removed. * Remove class .safari styling from activity chooser dialog for theme boost and bootstrapbase. * The following functions and classes have been finally deprecated and can not be used anymore: * css_is_colour() * css_is_width() * css_sort_by_count() * core_course_renderer::add_modchoosertoggle() * class css_optimiser === 3.4 === * There was a mustache template login.mustache in /lib/templates/ rendering the login form and a template with the same name in /theme/boost/templates/ rendering the pagelayout "login". To prevent misunderstanding when overriding one of these templates in a Boost child theme, the first one was renamed to loginform.mustache - see MDL-58970. * The Boost flat navigation nodes now have several data-attributes which let plugin developers access properties from the underlying navigation nodes in the browser - see MDL-59425. * Navigation between activities via a previous and next link was added to Boost, Clean and Bootstrapbase. This is made possible by a new function core_renderer->activity_navigation(). * Theme designers may now place the Reset tour on this page link where required by adding an empty container (e.g. <div class="tool_usertours-resettourcontainer"></div>) to their layouts. === 3.3 === * As boost-based themes no longer use the moodle-core-popuphelp help popups, the javascript setup for this module have been moved from core standard_head_html to the bootstrapbase renderer. If your theme needs this javascript you will need to ensure the bootstrap renderer is called, or require the JS yourself === 3.2 === * Removed themes: base, canvas During the upgrade process the themes will be uninstalled and all their settings will be deleted. If you wish to keep your theme and its settings, download it from moodle.org and put it back in the theme/ directory BEFORE UPGRADING. * Bootstrap 4 was added as part of a the new theme 'boost'. * Some backwards and forwards compatibility has been added for different bootstrap versions. This is to allow the same markup to work in "clean" and "boost" themes a lot of the time. It is also to allow user text with bootstrap classes to keep working in the new theme. * Using .dir-rtl for RTL styling is deprecated and should not be used any more. From now the styles are automatically flipped when the language is right-to-left. However, as this is not always perfect, you can define exceptions. Please refer to the documentation of the tool RTLCSS-PHP for more information: https://github.com/moodlehq/rtlcss-php * Themes can now automatically compile SCSS on the fly. This works the same way as it does compiling LESS on the fly, effecitvely adding $THEME->scss to your config. The latter can either be the name a SCSS file (without extension) in your theme's scss/ folder, or a Closure which will return the main SCSS content. * Two new callbacks allow themes to inject SCSS code before and after the content provided by the SCSS file $THEME->scss. See $THEME->prescsscallback and $THEME->extrascsscallback. * A new callback can be defined to post process the CSS using an object representation of the CSS tree ($THEME->csstreepostprocess). This gives a lot more flexibility than a simple find and replace. Refer to 'boost' for an example, and to PHP-CSS-Parser. (https://github.com/sabberworm/PHP-CSS-Parser) for the API. * A new core setting now enables admins to upload the logos of their site. Using the following methods, themers can instantly support branding logos without the need to implement specific theme settings: * $OUTPUT->get_logo_url($maxwidth, $maxheight); * $OUTPUT->get_compact_logo_url($maxwidth, $maxheight); * The class .dir-ltr should not be used any more. To force LTR styles use the directive to remove the rule when the language is RTL. See RTLCSS-PHP for more information. * A new class .text-ltr may be used to force the direction to LTR. This is especially useful for forms fields (numbers, emails, URLs must not be RTL'd), and for displaying code snippets or configuration samples. * A new theme config 'requiredblocks' allows a theme to define which blocks are deletable. * You may no longer override the following core_course_renderer methods. See course/upgrade.txt for more information: - course_modchooser_module_types - course_modchooser_module - course_modchooser_title * The question chooser now uses a renderable and a template, the following methods have been deprecated in favour of core_question_bank_renderer::render_qbank_chooser(). - qbank_chooser - qbank_chooser_types - qbank_chooser_qtype - qbank_chooser_title * The 'css optimiser' has been removed. Developers are encouraged to use tools such as stylelint to help optimise their css. Some functions and classes in lib/csslib.php (which was not for public use) have been deprecated: - css_is_colour - css_is_width - css_sort_by_count - class css_optimiser no longer does anything. * CLI svgtool.php has moved from theme/base/cli to admin/cli and paths should be relative to the new location. * mod_chat will now display the 'course theme' option for all themes (previously it was only displayed on bootstrap2 based themes). * Theme can choose how to display "Add a block" control in $THEME->addblockposition, default value is BLOCK_ADDBLOCK_POSITION_DEFAULT that displays it as a fake block in editing mode. === 3.1 === * A new search box for global search has been added to bootstrap and clean layout files, if your theme is overwriting columns1.php, columns2.php or columns3.php you will need to add a call to core_renderer::search_box to display it. * Notification templates have been renamed to better suit types of alert rather than uses. The following changes have been made: * notification_problem.mustache => notification_error.mustache * notification_message => notification_info * notification_redirect => notification_warning * Method core_course_renderer::course_section_cm_name() is split into two methods, custom themes that override this method must be modified or otherwise editing functionality may become broken. This method is now also used by social activities block and site menu block to display activities names. === 3.0 === * The renderer function core_availability_renderer::multiple_messages was changed to render_core_availability_multiple_messages, requiring a parameter of the new \core_availability\multiple_messages type. * Meta description is now included in standard_head_html for homepage in bootstrapbase. If your theme includes a meta description directly in a layout for the frontpage, you will need to remove it or override the standard_head_html instead. * Themes Clean and More have been updated to use a new navbar_button function, which shows the hamburguer icon (responsive menu) or not depending on custom and language menus settings; themes extending bootstrapbase and overriding its layouts can call replace their "a.btn-navbar" node for a call to this function. * Themes Clean and More page header logo only displays on front page and login page. * A new function navbar_home has been added to theme_clean and theme_more to display the navigation bar link to the site home. Two new settings have been added to control if the link should be a small logo image, text or both. It defaults to the current behaviour, only a text link. === 2.9 === * Themes Bootstrapbase, Clean and More have undergone some changes for RTL layouts see - MDL-48160. * Themes Clean amd More page header background logo, if loaded, no longer links to the home page. * Themes Clean and More have been updated to use the renderer full_header(). This renderer (when in a user context) displays a message button and consequently the link to message users have been removed from various pages. It is recommended that theme developers use this renderer to ensure that they do not suffer from a reduction in access to this feature. * $OUTPUT->context_header() has been introduced to produce headers similar to what full_header() creates. This renderer is used for creating subsequent headers in a page. If provided with user information, this render will also display a message button like full_header(). === 2.8 === * Themes Base and Canvas layout/embedded.php has changed. The div id="content" has been changed to id="page-content" - see MDL-47915. * All mod_assign CSS selectors have been qualified with ".path-mod-assign". This means any custom CSS rules for mod_assign in a theme may need to be updated. * The following render methods were renamed, if you have overridden any of these you will need to update your renderer: - report_log_renderer::render_report_log_renderable => report_log_renderer::render_report_log - report_loglive_renderer::render_report_loglive_renderable => report_loglive_renderer::render_report_log * On calendar view screen the course selector and new event button have been swapped, custom CSS for .path-calendar might be affected. * The functions search_listing() and search_pagination() in the core_course_management_renderer class take the searched string as an extra parameter - see MDL-46902. * Themes with non-fixed headers must have the .navbar class in their navbar in order for floating headers in the grader report to work - see MDL-46658. * To accomodate the new gradebook, use of overflow: hidden or overflow-x: hidden CSS rules on DOM elements containing the #user-grades table, visible at [Course administration -> Grades] is not recommended. Please use overflow: auto or overflow: scroll instead, as this will handle medium to large courses with multiple activities better (more information available at https://docs.moodle.org/dev/Theme_upgrade_notes ). * The new user menu can be added to themes by calling $OUTPUT->user_menu(); we recommend doing so in a backwards-compatible way (see https://docs.moodle.org/dev/Theme_upgrade_notes for more information). === 2.7 === * CSS related functions in theme class and csslib.php were refactored, addons that are using this private API need to be updated * Please update your css to use 'tr:nth-of-type(odd/even)' instead of '.r0/.r1' to apply tr specific css for various tables. These classes are deprecated now and will be removed in Moodle 2.9. This has done to better support styling tables that will be altered by JavaScript. Here is an example to update your css: Old code: table.generaltable .r0 {background-color: #F0F0F0;} table.generaltable .r1 {background-color: #F0F0F0;} New code: table.generaltable > tbody > tr:nth-of-type(even) {background-color: #F0F0F0;} table.generaltable > tbody > tr:nth-of-type(odd) {background-color: #F0F0F0;} Removed themes: * afterburner, anomaly, arialist, binarius, boxxie, brick, formal_white, formfactor, fusion, leatherbound, magazine, nimble, nonzero, overlay, serenity, sky_high, splash, standard and standardold have been removed. During the upgrade process the themes will be uninstalled and all their settings will be deleted. If you wish to keep your theme and its settings, download it from moodle.org and put it back in the theme/ directory BEFORE UPGRADING. Notes: * z-index on #dock has been adjusted from 11000 to 5000 to prevent overlapping issues with fullscreen TinyMCE in Base theme. === 2.6 === Removed themes: * "My Mobile" theme has been removed (see MDL-40874). During the upgrade process "My Mobile" theme will be uninstalled and all its settings will be deleted. "My Mobile" theme and its extending themes will fallback to the mobile friendly "Clean" theme. If you wish to keep "My Mobile" theme and its settings, BEFORE UPGRADING you can copy the files from the unmaintained plugin into theme/mymobile. The unmaintained plugin can be downloaded at https://moodle.org/plugins/pluginversion.php?id=4563 Notes: * There have been several changes made to the classes used on headings throughout Moodle. This was done as per the Moodle HTML guidelines. h1 and h2 elements should have no classes, h3 and lower headings may have descriptive classes only (any classes must properly describe the relation between the header and its content). * The parameters value for the following functions have been modified: core_renderer::heading() and core_renderer::heading_with_help(). This means that headings using the default options will no longer have the class "main" which was the previous default. * The file picker and activity chooser have been converted to use M.core.dialogue. This means the styles for these elements have changed in the base and bootstrapbase themes and you will need to copy the new styles if you are not inheriting from either one of these themes. * For the themes based on bootstrapbase please also read theme/bootstrapbase/upgrade.txt * A new component action_menu is now used to display editing icons for courses and blocks within a drop down. If you have a theme that doesn't extend base, canvas, or clean then you will need to style for this new component within your theme. * The maintenance layout now has a special renderer that extends the core_renderer in order to prevent some methods from interacting with the database. Please be aware that for the maintenance layout some methods now always return an empty string. This has been done because it is important that during maintenance routines we don't show any links, interact with the database, or interact with caches as doing so may lead to errors, Please see the maintenance renderer notes below for details on the functions affected. Renderer changes: * core_course_renderer::course_section_cm_edit_actions has two new optional arguments and now uses and action_menu component. * core_course_renderer::course_section_cm has been altered to call core_course_renderer::course_section_cm_edit_actions with the two new arguments. * core_renderer::block_controls has a new optional argument (the block id) and has been altered to use the new action_menu component. * core_renderer::block_header has been altered to give core_renderer::block_controls the new second argument, the block id. * core_renderer::action_link has a new argument, and optional icon that can be rendererd into the link. Selector changes: * Changes to the classes given to the header produced when rendering a single section within a course. .section-navigation.header.headingblock => .section-navigation.navigationtitle * Changes to the classes used when producing the course information box that lists courses. The name (h3|div} of both courses and categories used to have .name, for courses in the list this was changed to .coursename and for categories in the list this was changed to .categoryname. * Classes ".header and .headingblock" were removed from all front page content headings. * Classes ".headingblock .header .tag-header" were removed from the tag index page Maintenance renderer notes: When the maintenance layout is being used $OUTPUT will be an instance of core_renderer_maintenance. This renderer mimics the core_renderer except that the following functions always return an empty string. * core_renderer_maintenance::block * core_renderer_maintenance::blocks * core_renderer_maintenance::blocks_for_regions * core_renderer_maintenance::course_header * core_renderer_maintenance::course_footer * core_renderer_maintenance::course_content_header * core_renderer_maintenance::course_content_footer * core_renderer_maintenance::custom_menu * core_renderer_maintenance::file_picker * core_renderer_maintenance::htmllize_file_tree * core_renderer_maintenance::lang_menu * core_renderer_maintenance::login_info * core_renderer_maintenance::user_picture If you have overridden methods of the core_renderer in your theme and want those changes to be shown during times of maintenance you will also need to override the core_renderer_maintenance and copy your customisations from the core_renderer to that. === 2.5.1 === Notes: * Block drag and drop functionality has been improved so that it works regardless of what block regions you use or how many block regions you have. In order to benefit from this improvement you must convert your calls from $OUTPUT->blocks_for_region() to $OUTPUT->blocks. Optional changes: * Theme config can nominate block regions to swap if the user is using a rtl languages such as Hebrew. $THEME->blockrtlmanipulations should be an associative array, the key is the original block region, and the value should be where the blocks in that region should be displayed. * New $OUTPUT methods to replace code that was previously using $PAGE. Converting to these methods is optional but highly recommended. Refer to the bootstrapbase layouts for examples. - $OUTPUT->body_attributes() returns a string you can use for the body id and classes. - $OUTPUT->blocks() returns HTML to display a block region and all of its blocks. This adds data attributes that ensure drag and drop of blocks will work no matter what block regions or how many you have. - $OUTPUT->page_heading() returns the page heading. Replaces $PAGE->heading. - $OUTPUT->page_heading_button() returns the button to display with the heading. Replaces $page->button. - $OUTPUT->page_doc_link() returns the link to moodle docs for the page. Replaces page_doc_link(). - $OUTPUT->page_heading_menu() returns the heading menu for the page. Replaces $PAGE->headingmenu. - $OUTPUT->page_title() Returns the title to use for the head section. - $OUTPUT->favicon() returns the URL to the favicon. Renderer changes: * core_renderer::navbar now returns an empty string if there are no navigation items to display. * core_renderer::custom_menu now adds a class "custom_menu" to the div that contains the HTML for the custom menu. === 2.5 === required changes: * Functions core_course_renderer::course_category_tree() and course_category_tree_category() are deprecated * Significant changes in rendering of courses and categories listings, lots of CSS classes changed, several functions such as print_courses(), print_whole_category_list(), print_category_info() are moved to course renderer. See http://docs.moodle.org/dev/Courses_lists_upgrade_to_2.5 DOM changes: * changed the h1 title in the help popup to a h2. * new setting $THEME->yuicssmodules = array('cssreset', 'cssfonts', 'cssgrids', 'cssbase'); which allows themes to use different CSS reset normalisers such as cssnormalize YUI module. * Re-wrote the user profile views to definition lists. * Re-wrote the table for the course completion status block to use html_table - added some CSS classes to the table in the process (see MDL-35608). * Cancel buttons have the class btn-cancel. * Added a z-index for the div#dateselector-calendar-panel so that the calendar pop-up renders above the filemanager when they overlap, ie. the course settings page (see MDL-39047). * Trivial change of CSS selectors used to display plugin status at the plugins overview screen (#plugins-control-panel). Renderer changes: * Mymobile theme changed to support more verbose move-block-here descriptions. === 2.4 === required changes: * output course and course content header/footer that may be returned by course format (see MDL-36048) * span.completionprogress has been changed to a <div> and is not a float by default any more. deprecation: * i/roles: Use t/assignroles instead * t/manual_item: Use i/manual_item instead * t/unlock_gray: Use t/locked instead * t/userblue: Previously used to unblock a user, use t/unblock. * c/course: Use i/courseevent instead * c/group: Use i/groupevent instead * c/site: Use i/siteevent instead * c/user: Use i/userevent instead * t/clear: Use t/check instead * i/cross_red_big: Use i/invalid or i/grade_incorrect * i/tick_green_big: Use i/valid or i/grade_correct * i/tick_amber_big: Use i/caution or i/grade_partiallycorrect * No more small versions of i/cross_red_small, i/tick_green_small and i/tick_amber_small, use their big equivalent. * t/addgreen: Use t/add instead. * i/approve: Use t/approve instead optional changes: * new optional boolean parameter $withlinks for public function login_info() in lib/outputrenderers.php (MDL-31365) * new layout option "nologinlinks" and new page layout "secure" e.g. for safebrowser and securewindow (MDL-31365) * new class 'iconlarge' for 24x24 icons. * new icons i/export and i/import (sized 16x16). Previously export and import actions used i/backup and i/restore. * new icon i/assignroles (sized 16x16), to prevent the use of i/roles which is 12x12. * new icon i/switchrole (sized 16x16), was previously using i/roles. Now is a copy of the new i/assignroles icon. * new icons i/enrolusers and t/enrolusers, previsouly i/users was used. * new icon t/cohorts (sized 12x12), to prevent the use of i/cohorts which is 16x16. * new icons t/sort_asc, t/sort_desc to use for ordering in table headers. * new class 'iconsort' for icons used for ordering in table headers. * new icons t/locked and t/unlocked (12x12) which should be used when there is no action associated to the icon. * new icons i/folder (16x16), monochrome equivalent to f/folder. * new icons t/addcontact, t/removecontact and t/messages, previously t/addgreen, t/delete and t/log were used in messaging. * new icons t/unblock and i/twoway. * new icons i/courseevent, i/groupevent, i/siteevent and i/userevent (16x16) instead of c/* for calendar events. * new icon t/markasread (12x12) to replace t/clear used in forums. * new icon t/check (12x12) to replace t/clear which name does not reflect the icon meaning. * new classes 'icon-pre' and 'icon-post' supposedly to be used when the icon is positioned before or after the text. This is not really used yet, but it's a start towards some standardisation of the icon selectors. * new icons i/valid, i/caution and i/invalid for generic statuses. * new icons i/grade_correct, i/grade_partiallycorrect and i/grade_incorrect for grades. * new icon t/approve (12x12). * new icon t/contextmenu (12x12) for a monochrome version of i/menu. === 2.3 === optional changes: * add new u/f3.png image when theme contains customised f1 and f2 default user images === 2.2 === required changes: * use new page content placeholder "echo $OUTPUT->main_content()" instead of "echo core_renderer::MAIN_CONTENT_TOKEN" see git commit: 3b3f302855d7621405a8b93e49bd399d67a998d7 * upgrade report selectors: search for "-course-report-" and replace with "-report-" home3/cpr76684/public_html/Aem/analytics/upgrade.txt 0000644 00000016331 15152013123 0016142 0 ustar 00 This files describes API changes in analytics sub system, information provided here is intended especially for developers. === 3.11 === * Final deprecation get_enabled_time_splitting_methods. Method has been removed. Use get_time_splitting_methods_for_evaluation instead. * Final deprecation add_builtin_models. Method has been removed. The functionality has been replaced with automatic update of models provided by the core moodle component. There is no need to call this method explicitly any more. Instead, adding new models can be achieved by updating the lib/db/analytics.php file and bumping the core version. * Final deprecation - get_analysables(). Please see get_analysables_interator() instead. get_analysables_iterator() needs to be overridden by the child class. * A new function get_executed_actions() has been added to \core_analytics\prediction class to get all (or filtered by action name) executed actions of a prediction === 3.8 === * "Time-splitting method" have been replaced by "Analysis interval" for the language strings that are displayed in the Moodle UI. The name of several time-splitting methods have been updated according to the new description of the field. * A new target::can_use_timesplitting method must be implemented to discard time-splitting methods that can not be used on a target. * Targets can now implement get_insight_body and get_insight_body_for_prediction to set the body of the insight. * Indicators can add information about calculated values by calling add_shared_calculation_info(). This data is later available for targets in get_insight_body_for_prediction(), it can be accessed appending ':extradata' to the indicator name (e.g. $sampledata['\mod_yeah\analytics\indicator\ou:extradata') * A new \core_analytics\local\time_splitting\past_periodic abstract class has been added. Time-splitting methods extending \core_analytics\local\time_splitting\periodic directly should be extending past_periodic now. 'periodic' can still be directly extended by implementing get_next_range and get_first_start methods. * Targets can now specify a list of bulk actions in bulk_actions(). core_analytics\prediction_action is now extending core_analytics\action and a new core_analytics\bulk_action class has been added. Actions can now specify a type in its constructor: core_analytics\action::TYPE_POSITIVE, TYPE_NEUTRAL or TYPE_NEGATIVE. A list of default bulk actions is available in \core_analytics\default_bulk_actions. * The default suggested actions provided to users changed: * For targets with one single sample per analysable (e.g. upcoming activities due) the default actions are Useful and Not useful. * For targets with multiple samples per analysable (e.g. students at risk) the default actions are Accept, Not applicable and Incorrectly flagged. * The suggested actions for the existing models have been reworded: * Predictions flagged as "Acknowledged" in models whose targets use analysers that provide one sample per analysable (e.g. upcoming activities due) have been updated to "Useful" flag. * Predictions flagged as "Not useful" in models whose targets use analysers that provide multiple samples per analysable (e.g. students at risk or no teaching) have been updated to "Incorrectly flagged". * \core_analytics\predictor::delete_output_dir has a new 2nd parameter, $uniquemodelid. * Analyser's get_analysables_iterator and get_iterator_sql have a new $contexts parameter to limit the returned analysables to the ones that depend on the provided contexts. * Analysers can implement a context_restriction_support() method to restrict models to a subset of the contents in the site. Only CONTEXT_COURSE and CONTEXT_COURSECAT are supported. === 3.7 === * \core_analytics\regressor::evaluate_regression and \core_analytics\classifier::evaluate_classification have been updated to include a new $trainedmodeldir param. This new param will be used to evaluate the existing trained model. * Plugins and core subsystems can now declare default prediction models by describing them in their db/analytics.php file. Models should not be created manually via the db/install.php file any more. * The method \core_analytics\manager::add_builtin_models() has been deprecated. The functionality has been replaced with automatic update of models provided by the core moodle component. There is no need to call this method explicitly any more. Instead, adding new models can be achieved by updating the lib/db/analytics.php file and bumping the core version. * \core_analytics\model::execute_prediction_callbacks now returns an array with both sample's contexts and the prediction records. * \core_analytics\model::export() now expects the renderer instance as an argument. * Time splitting methods: * \core_analytics\local\time_splitting\base::append_rangeindex and \core_analytics\local\time_splitting\base::infer_sample_info are now marked as final and can not be overwritten. * Can now overwrite include_range_info_in_training_data() and get_training_ranges() methods. They can be used to create time splitting methods with a pre-defined number of ranges. * Can now overwrite cache_indicator_calculations(). You should return false if the time frames generated by your time-splitting method are unique and / or can hardly be reused by further models. * Can now overwrite valid_for_evaluation(). You can return false if the time-splitting method can not be used to evaluate prediction models or if it does not make sense to evaluate prediction models with it, as for example upcoming_periodic children classes. * \core_analytics\local\analyser\base::get_most_recent_prediction_range has been moved to \core_analytics\local\time_splitting\base::get_most_recent_prediction_range and it is not overwritable by time splitting methods. * Targets: * The visibility of the following methods must now be public: ignored_predicted_classes() and get_insights_users() * Prediction_actions() has now a 3rd parameter $isinsightuser. This parameter is true when we are listing actions for the user that will receives the insight. * Can now implement a always_update_analysis_time() method so analysable elements' timeanalysed is only updated when analysable elements have been successfully evaluated. It is useful for lightweight targets. * Can not implement two new methods to tune the insights generated by the model: get_insight_subject() and get_insight_context_url(). * Analysers: * The visibility of get_all_samples() method must now be public. * get_analysables() method has been deprecated in favour of a new get_analysables_interator() for performance reasons. * Can overwrite a new one_sample_per_analysable() method if the analysables they use only have one sample. The insights generated by models will then include the suggested actions in the notification. === 3.5 === * There are two new methods for analysers, processes_user_data() and join_sample_user(). You need to overwrite them if your analyser uses user data. As a general statement, you should overwrite these new methods if your samples return 'user' data. These new methods are used for analytics' privacy API implementation. home3/cpr76684/public_html/Aem/mod/quiz/accessrule/upgrade.txt 0000644 00000001130 15152025101 0020041 0 ustar 00 This files describes API changes for quiz access rule plugins. Overview of this plugin type at http://docs.moodle.org/dev/Quiz_access_rules === 2.8, 2.7.1, 2.6.4 and 2.5.7 === * New static method delete_settings for access rules, which is called when a quiz is deleted. === 2.4 and 2.3.4 === * Replaced time_left() with new time_left_display() and end_time() functions. === 2.3 === * This plugin type now supports cron in the standard way. If required, Create a lib.php file containing function quizaccess_mypluginname_cron() {}; === 2.2 === * This plugin type was new in Moodle 2.2! home3/cpr76684/public_html/Aem/mod/quiz/report/upgrade.txt 0000644 00000007726 15152065056 0017261 0 ustar 00 This files describes API changes for quiz report plugins. Overview of this plugin type at http://docs.moodle.org/dev/Quiz_reports === 4.1.1 === There was an ill-advised, never documented, API change in quiz_report_get_significant_questions in Moodle 4.0. The API has now been reverted to how it was before 4.0. Hopefully this will not cause anyone a problem. (The API revert did not require any changes in any automated tests or standard quiz reports.) === 3.9 === * Quiz report plugins defining capabilities used to require an extra string like $string['statistics:componentname'] = 'Quiz statistics report'; in addition to $string['pluginname'] = 'Statistics'; This is no longer required. === 3.8 === * New quiz_attempts_report_table method: \quiz_attempts_report_table::checkbox_col_header() This generates a column header containing a checkbox that toggles the checked state of all the checkboxes corresponding to the entries listed on a given quiz report table. It requires the name of the checkbox column as a parameter in order to disable sorting on the checkbox column. === 3.2 === * A code refactoring based on new sql functions in MDL-31243 and removing get_users_by_capability from the quiz reports in MDL-27072. The class quiz_attempts_report is now initialised to return \core\dml\sql_join (joins, wheres, params) rather than arrays of userids. This allows the use of joins in quiz report queries and is very important when there are larger numbers of enrolled users. The signature of many quiz report methods now includes '$studentsjoins', rather than '$students' and similar for '$groupstudentsjoins', '$allowedjoins' and '$usersjoins'. For clear examples of the use of these changes please see attemptsreport_table.php base_sql() or almost any function in overview/report.php. The protected function quiz_attempts_report::load_relevant_students is deprecated, please use quiz_attempts_report::get_students_joins() instead. === 2.6 === * Improving the display page and heading levels to have a proper nesting. We are reducing the amount of white spaces for the top report by making 'separate group' options and attempts to be displayed inline. In grading report, we are changing 'no questions' from using heading to notification message. (MDL-41615) === 2.3 === * Support for the old way of doing cron in a separate cron.php file has been removed. Instead, you need a lib.php file inside the plugin with a cron function called quiz_myreportname_cron(). The statistics report is an example of how it should be done. * There was a big refactor of the quiz reports, in issues MDL-32300, MDL-32322 and MDL-3030. It is difficult to explain the changes. Probably the best way to understand what happened is to look at git log mod/quiz/report/overview git log mod/quiz/report/responses and so on. Here are some notes on a few of the changes: The class quiz_attempt_report was renamed to quiz_attempts_report (with an extra s). Some globally defined constants with the prefix QUIZ_REPORT_ATTEMPTS_ moved into the quiz_attempts_report class. Specifically quiz_attempts_report::ALL_WITH replaces QUIZ_REPORT_ATTEMPTS_ALL quiz_attempts_report::ENROLLED_ALL replaces QUIZ_REPORT_ATTEMPTS_ALL_STUDENTS quiz_attempts_report::ENROLLED_WITH replaces QUIZ_REPORT_ATTEMPTS_STUDENTS_WITH quiz_attempts_report::ENROLLED_WITHOUT replaces QUIZ_REPORT_ATTEMPTS_STUDENTS_WITH_NO Your if you have a table class, it needs to be renamed like quiz_report_myreportname_table -> quiz_myreportname_table. That is, all the class names in your plugin should start with the frankenstyle plugin name quiz_myreportname. === 2.2 === * Plugins should be converted to implement cron in the standard way. In lib.php, define a function quiz_myreportname_cron() {}; This replaces the old way of having a separate cron.php file. Also, the cron frequency should be defined in version.php, not in the quiz_reports table. === earlier versions === * ... API changes were not documented properly. Sorry. (There weren't many!) home3/cpr76684/public_html/Aem/mod/glossary/upgrade.txt 0000644 00000002377 15152155360 0016614 0 ustar 00 This files describes API changes in /mod/glossary/*, information provided here is intended especially for developers. === 3.10 === * External function get_entries_by_id now returns and additional "permissions" field indicating the user permissions for managing the entry. === 3.8 === * The following functions have been finally deprecated and can not be used anymore: * glossary_scale_used() === 3.7 === * External functions get_entries_by_* and get_entry now return an additional field "tags" containing the entry tags. === 3.4 === * External functions returning entries now return an additional field "ratinginfo" containing the entry rating information. === 3.2 === * External functions that were returning file information now return the following file fields: filename, filepath, mimetype, filesize, timemodified and fileurl. Those fields are now marked as VALUE_OPTIONAL for backwards compatibility. === 2.8 === * The glossary_print_entry_attachment function no longer takes an `align` or `insidetable` property. Instead the attachments are printed within a div whose class is `attachments` and which can be targetted using appropriate CSS rules. * The glossary_print_entry_attachment function now displays the attachments on the left by default. home3/cpr76684/public_html/Aem/auth/db/upgrade.txt 0000644 00000001472 15152170175 0015514 0 ustar 00 This files describes API changes in /auth/db/*, information provided here is intended especially for developers. === 3.3 === * The config.html file was migrated to use the admin settings API. The identifier for configuration data stored in config_plugins table was converted from 'auth/db' to 'auth_db'. === 3.1 === * The auth_plugin_db::clean_data() has been deprecated and will be removed in a future version. Please update to use core_user::clean_data() instead. === 2.9 === Some alterations have been made to the handling of case sensitity handling of passwords and password hashes which previously varied depending on database configuration: * Plain text password matching is now always case sensitive * sha1/md5 hash comparisons are now enforced case insensitive (as underlying they are hexidecimal values) home3/cpr76684/public_html/Aem/comment/upgrade.txt 0000644 00000000711 15152170316 0015620 0 ustar 00 This files describes API changes in /comment/* , information provided here is intended especially for developers. === 3.8 === * External function get_comments now returns the total count of comments and the number of comments per page. It also has a new parameter to indicate the sorting direction (defaulted to DESC). * The external function core_comment_get_comments now indicates if the current user can post comments in the requested area. home3/cpr76684/public_html/Aem/auth/shibboleth/upgrade.txt 0000644 00000001376 15152171623 0017254 0 ustar 00 This files describes API changes in /auth/shibboleth/*, information provided here is intended especially for developers. === 3.11 === * The 'Data modification API' (convert_data) setting can no longer be configured to use files located within the current site data directory ($CFG->dataroot), as it exposes the site to security risks. === 3.5.2 === * Moved the public function unserializesession in auth/shibboleth/logout.php to auth/shibboleth/classes/helper.php and made it private. This function should not have been used outside of this file. === 3.3 === * The config.html file was migrated to use the admin settings API. The identifier for configuration data stored in config_plugins table was converted from 'auth/shibboleth' to 'auth_shibboleth'. home3/cpr76684/public_html/Aem/mod/lesson/upgrade.txt 0000644 00000004625 15152203301 0016237 0 ustar 00 This files describes API changes in the lesson code. === 4.0 === * Deprecated the function lesson_add_header_buttons in favour of tertiary navigation. === 3.6.1 === * A new function update_form_data() has been added to lesson_page class. This can be overridden by the individual page types to alter the form data before being sent to the mform. === 3.4 === * External function mod_lesson_external::get_user_attempt() now returns the full page object inside each answerpages. === 3.3.2 === * lesson_refresh_events() Now takes two additional parameters to refine the update to a specific instance. This function now optionally takes the module instance object or ID, and the course module object or ID. Please try to send the full objects instead of the ids to save DB calls. === 3.3 === * lesson::callback_on_view() has an additional optional parameter $redirect default to true. It can be set to false to avoid redirection and return the page to redirect. === 3.1 === * Removed the unused file reformat.php * removedoublecr() and importmodifiedaikenstyle() have now been removed. === 3.0 === * Removed broken high score code. Use the activity results block instead. === 2.9 === * The grade_item_delete function in mod/lesson/lib.php was removed because it was not doing anything and was never called. * A third optional boolean parameter $endreached was added to lesson::update_timer to indicate that end of lesson was reached. This is used by 'completionendreached' custom completion rule. * lesson_page_type_endofbranch::update in mod/lesson/pagetypes/endofbranch.php and lesson_page_type_endofcluster::update in mod/lesson/pagetypes/endofcluster.php have been removed, this is now handled by the base class: lesson_page::update in locallib.php and the exact same code is executed (it is also executed by the lesson_page_type_cluster class that previously had no update function). * A fourth parameter (format) has been added to the add_answer() function located as part of the lesson_add_page_form_base class. If specified with a value of 'LESSON_ANSWER_HTML' then a rich html editor is generated. Otherwise an editor is created with Moodle Auto Format * removedoublecr() and importmodifiedaikenstyle() are now deprecated. * Added support for groups and groupings. If enabled, this allows the Report and Grade Essay view to be filtered by a group === Earlier changes === * Were not documented in this way. Sorry. home3/cpr76684/public_html/Aem/mod/imscp/upgrade.txt 0000644 00000000473 15152217552 0016061 0 ustar 00 This files describes API changes in the imscp code. === 3.0 === * External function mod_imscp_external::get_imscps_by_courses returned parameter "name" has been changed to PARAM_RAW, this is because the new external_format_string function may return raw data if the global moodlewssettingraw parameter is used. home3/cpr76684/public_html/Aem/mod/h5pactivity/upgrade.txt 0000644 00000001100 15152217552 0017203 0 ustar 00 This files describes API changes in /mod/h5pactivity/*, information provided here is intended especially for developers. === 4.1 === * The following methods now accept an optional `$currentgroup` parameter in order to better support groups: - `\mod_h5pactivity\local\manager::get_active_users_join` - `\mod_h5pactivity\local\manager::get_report` - `\mod_h5pactivity\local\report\participants` constructor === 3.11 === * Added mod_h5pactivity\local\manager::get_active_users_join method to query all active users from a specific activity, even in a freeze context. home3/cpr76684/public_html/Aem/mod/bigbluebuttonbn/upgrade.txt 0000644 00000001103 15152220263 0020113 0 ustar 00 This files describes API changes in the bigbluebuttonbn code. === 4.1.3 === * Add a new parameter for mod_bigbluebuttonbn\recording::sync_pending_recordings_from_server so sync only 'dismissed' recordings (This was fixed in 4.2, 4.1.3 and 4.0.8). === 4.1 === * External function mod_bigbluebuttonbn\external\meeting_info now return the list of the instance features and whether they are enabled or not. * External function mod_bigbluebuttonbn\external\meeting_info may now return guestaccessenabled, guestjoinurl, and guestpassword if the callee can have access to them. home3/cpr76684/public_html/Aem/blocks/section_links/upgrade.txt 0000644 00000000364 15152220702 0020276 0 ustar 00 This file describes API changes in the section_links block code. === 3.11 === * New optional parameter $showsectionname has been added to render_section_links(). Setting this to true will display section name in addition to section number. home3/cpr76684/public_html/Aem/admin/tool/behat/upgrade.txt 0000644 00000001010 15152220711 0017272 0 ustar 00 This files describes API changes in the tool_behat code. === 3.7 === * Behat will now look for behat step definitions in the current theme and any parents the theme may have. === 2.7 === * Constants behat_base::cap_allow, behat_base::cap_prevent and behat_base::cap_prohibit have been removed in favour of the lang/en/role.php language strings 'allow', 'prevent' and 'prohibit'. * @_only_local tag used in .feature files replaced by @_file_upload tag * @_alerts tag used in .feature files replaced by @_alert tag home3/cpr76684/public_html/Aem/auth/cas/upgrade.txt 0000644 00000000467 15152231444 0015675 0 ustar 00 This files describes API changes in /auth/cas/*, information provided here is intended especially for developers. === 3.3 === * The config.html file was migrated to use the admin settings API. The identifier for configuration data stored in config_plugins table was converted from 'auth/cas' to 'auth_cas'. home3/cpr76684/public_html/Aem/question/engine/upgrade.txt 0000644 00000013765 15152251241 0017304 0 ustar 00 This files describes API changes for the core question engine. === 4.1.2 === * A `$questionidentifier` property has been added to `\question_display_options` to enable question type plugins to associate the question number to the question that is being rendered. This can be used to improve the accessibility of rendered questions and can be especially be helpful for screen reader users as adding the question number on the answer field(s) labels will allow them to distinguish between answer fields as they navigate through a quiz. * Question type plugins can use \question_display_options::add_question_identifier_to_label() to add the question number to the label of the answer field(s) of the question that is being rendered. The question number may be redundant when displayed, so the function allows for it to be enclosed within an sr-only container. === 4.0 === 1) A new optional parameter $extraselect has been added as a part of load_questions_usages_where_question_in_state() method in question/engine/datalib.php, anything passed here will be added to the SELECT list, use this to return extra data. === 3.9 === 1) In the past, whenever a question_usage_by_activity was loaded from the database, the apply_attempt_state was immediately called on every question, whether the results of doing that were ever used, or not. Now we have changed the code flow, so that apply_attempt_state is only called when some data or processing is requested (e.g. analysing a response or rendering the question) which requires the question to be fully initialised. This is MDL-67183. This change should be completely invisible with everything handled by the question engine. If you don't change your code, it should continue to work. However, to get the full advantage of this change, you should review your code, and look at every call to get_question or get_behaviour (on a question_attempt or question_usage_by_activity). The problem with these methods is that the question engine cannot know what you are planning to do with the question once you have got it. Therefore, they have to assume that apply_attempt_state must be called - which can be expensive. If you know that you don't need that (because, for example, you are just going to look at ->id or ->questiontext or something simple) then you should pass false to these functions, to get the possible performance benefit. In addition, there is a new method $qa->get_question_id() to handle that case more simply. Note that you don't have worry about this in places like the renderer for your question type, because by the time you are in the renderer, the question will already have been initialised. === 3.7 === 1) When a question is rendered, the outer div of the question has an id="q123" added. Unfortunately, this id was not actually unique, leading to bugs like MDL-52572. Therefore, we have had to change it. The id used now is what is returned by the new method $qa->get_outer_question_div_unique_id(). The old code that you need to search for and replace with a call to this method is "'q' . $qa->get_slot()" Note, the new method has also been added to Moodle 3.5.6 and 3.6.4, but returning the old id. This is to help question types that want to support multiple Moodle versions. === 3.1, 3.0.3, 2.9.5 === 1) The field question_display_options::$extrainfocontent is now displayed in the outcomes (yellow) div by default. It used to be in the info div. If you have overriden the question renderer, you may need to make a corresponding change. === 3.0, 2.9.2, 2.8.8 === 1) The extra internal PARAM constant question_attempt::PARAM_MARK should no longer be used. (It should not have been used outside the core of the question system). See MDL-51090 if you want more explanation. === 2.9 === 1) Some new methods on the question_usage class (and corresponding methods on question_attempt, question_attempt_step, question_usage_observer, ... requried to implement them, but almost certainly you should only be calling the question_usage methods from your code. * question_usage::add_question_in_place_of_other($slot, $question, $maxmark = null) This creates a new questoin_attempt in place of an existing one, moving the existing question_attempt to the end of the usage, in a new slot number. The new slot number is returned. The goal is to replace the old attempt, but not lose the old data. * question_usage::set_question_max_mark($slot, $maxmark) Sets the max mark for one question in this usage. Previously, you could only change this using the bulk operation question_usage::set_max_mark_in_attempts; * question_usage::set_question_attempt_metadata($slot, $name, $value); question_usage::get_question_attempt_metadata($slot, $name); You can now record metadata, that is, values stored by name, against question_attempts. The question engine ignores this data (other than storing and loading it) but you may find it useful in your code. To see examples of where these are used, look at the chagnes from MDL-40992. 2) New fields in question_display_options, ->extrainfocontent and ->extrahistorycontent. These default to blank, but can be used to inject extra content into those parts of the question display. If you have overridden the methods in core_question_renderer that use these fields, you may need to update your renderer. === 2.6 === 1) The method question_behaviour::is_manual_grade_in_range and move and become question_engine::is_manual_grade_in_range. 2) The arguments to core_question_renderer::mark_summary changed from ($qa, $options) to ($qa, $behaviouroutput, $options). If you have overridden that method you will need to update your code. 3) Heading level for number(), add_part_heading() and respond_history() has been lowered by one level. These changes are part of improving the page accessibility and making heading to have proper nesting. (MDL-41615) === Earlier changes === * Were not documented in this way. Sorry. home3/cpr76684/public_html/Aem/question/behaviour/upgrade.txt 0000644 00000010772 15152253526 0020026 0 ustar 00 This files describes API changes for question behaviour plugins. === 4.0 === 1) The major question bank changes should not affect behaviour plugins. The navigation changes may affect Behat tests. If you encounter this, the best way to fix it is to use the new navigation steps in MDL-74130. === 3.10 === 1) The slot parameter of method M.core_question_engine.init_submit_button now removed. The method will get the unique id by using the 'Check' button element. === 3.1 === 1) The standard behaviours that use a 'Check' button have all been changed so that they only show the button when the question is active. Your behaviour may interit this behaviour, because the change was made in the base class, and this is probably good for consistency. However, if your question behaviour uses the Check button, your probably want to test it carefully, and you will probably have to update your unit tests. See MDL-53304 for more details. === 2.9 === 1) There are new methods question_behaviour::can_finish_during_attempt and question_behaviour_type::can_finish_during_attempt. These methods both return false by default. You should override it if, with your behaviour, questions may finish just through the student interacting with them (e.g. by clicking the Check button within the question). The behaviour type method answers the the question for this behaviour in general, without reference to a specific question. The method on the behaviour class answers the question for a specific attempt at a specific question. === 2.7 === 1) question_behaviour_type has a new method allows_multiple_submitted_responses which defaults to false but should return true if this question behaviour accepts multiple submissions of responses within one attempt eg. multiple tries for the interactive or adaptive question behaviours. question_behaviour has a new method step_has_a_submitted_response($step). For question behaviours where it is not only the final response that is submitted by the student, you need to override this method to return true for other steps where a student has submitted a response. See question_behaviour_with_multiple_tries::step_has_a_submitted_response($step) for example. This method only needs to be overriden if you are returning true from allows_multiple_response_submissions. === 2.6 === 1) Legacy required_question_definition_type no longer supported. (See 2.2 point 2) below.) 2) Behaviours now have to define an extra class class qbehaviour_mybehaviour_type extends question_behaviour_type { This class returns information about the type of behaviour, as opposed to the qbehaviour_mybehaviour class which controls a particular question_attempt. That is like the difference between the qtype_mytype and the qtype_mytype_question classes. Practically, what this means is that any of the methods that used to be static methods of qbehaviour_mybehaviour class are now normal instance methods of the qbehaviour_mybehaviour_type class. Specifically. 2.5 / qbehaviour_mybehaviour -> 2.6 / qbehaviour_mybehaviour_type IS_ARCHETYPAL -> is_archetypal() adjust_random_guess_score() -> adjust_random_guess_score() get_unused_display_options() -> get_unused_display_options() 3) The static method is_manual_grade_in_range has moved from the question_behaviour class to the question_engine class. 4) Behaviours can now control how the marks information is displayed in the grey info area to the left of the question. There is a new method mark_summary that you can override, although the default implementation is fine in most cases. it uses the marked_out_of_max and mark_out_of_max methods as appropriate, so you may just wish to override those. === 2.3 === 1) This plugin type now supports cron in the standard way. If required, Create a lib.php file containing function qbehaviour_mypluginname_cron() {}; === 2.2 === 1) The old public static function get_required_behaviours() method is no more. Instead use the ->dependencies facility in version.php. E.g. $plugin->dependencies = array( 'qbehaviour_immediatefeedback' => 2011102700, 'qbehaviour_deferredcbm' => 2011102700 ); 2) The old required_question_definition_type method has been replaced by a new is_compatible_question method. You should change your behaviour to override the new method, not the old one. This change has been implemented in a backwards-compatible way, so behaviours will not break. home3/cpr76684/public_html/Aem/grade/export/upgrade.txt 0000644 00000001642 15152356113 0016566 0 ustar 00 This files describes API changes in /grade/export/* - plugins, information provided here is intended especially for developers. === 2.8 === The UI for the grade export form was simplified down so it's all on one page. The export preview was removed because it was not useful (more useful on import than on export). To update your export plugins you must pass 'simpleui' => true as an option to the grade_export_form, and make your grade_export_form submit directly to your export script. It's easiest to look at a complete example - see "git show 1cc43058" for a complete example of updating the ods exporter. Also the grade export UI form was changed to support multiples display types. The combo box was removed from (Open Document, Plain Text, Excel) and for each selected display type a column is generated. We didn't extended this solution to XML export which remains with a combo and can only select a single display type. home3/cpr76684/public_html/Aem/lib/editor/atto/upgrade.txt 0000644 00000002622 15152365243 0017171 0 ustar 00 This files describes API changes in the editor_atto code. === 4.1 === * Two new helper functions have been added to lib/editor/atto to handle enable/disable the empty placeholder for empty content in the HTML source view: - enablePlaceholderForEmptyContent() - Handle to enable the empty placeholder for empty content - disablePlaceholderForEmptyContent() - Handle to disable the empty placeholder for empty content. * One property have been added to lib/editor/atto to handle the state of the empty placeholder content. - enableAppropriateEmptyContent - Enable/disable the empty placeholder content. === 3.4 === * The following functions, previously used (exclusively) by upgrade steps are not available anymore because of the upgrade cleanup performed for this version. See MDL-57432 for more info: - atto_equation_update_librarygroup4_setting() === 3.0 === * Rangy updated to 1.3.0. Rangy has deprecated the createCssClassApplier function in this version (it is now createClassApplier). === 2.9 === * When adding a shortcut to the button of a plugin, atto will add a layer of validation to ensure that only the required keys are pressed. However, if you are using a custom keyConfig object you must validate the shortcut yourself. This is particularly important for non-English keyboard users. For more information read the documentation of EditorPluginButtons::_addKeyboardListener() and MDL-47133. home3/cpr76684/public_html/Aem/question/upgrade.txt 0000644 00000042134 15152537400 0016033 0 ustar 00 This files describes API changes for code that uses the question API. === 4.1 === 1) get_bulk_action_key() in core_question\local\bank\bulk_action_base class is deprecated and renamed to get_key(). === 4.0.5 === 1) Question bank plugins can now define more than one bulk action. Therefore, plugin_features_base::get_bulk_actions has been changed to return an array, rather than a single bulk action class. Please update the plugin_features class in your plugin if necessary. === 4.0 === Moodle 4.0 included the results of a major project to re-work the question bank. 1) Database changes (as usual, all existing data is updated automatically). * Previously there was a single {question} table. This has now been split into three to handle versionning questions: - question - This now has a row for each version of each question. Therefore, some of the metadata (e.g. category) is moved to the next table. However, data that defines how a question works is unchanged, so question type plugins will mostly keep working. - question_bank_entries - Each question bank entry is a question that appears in the question bank, which can have many versions. - question_versions - This joins all the versions of a question in the {question} table to the {question_bank_entries} row they belong to. * Also, how other parts of the code refer to questions they want to to has changed, to be managed by the core API in two new tables. - question_references -> Records where a specific question is used. - question_set_references -> Records where groups of questions are used (for example random questions in quizzes). As a result of this, data from the two quiz tables {quiz_slot} and {quiz_slot_tags} was moved to these new tables. 2) There is a new plugin type 'qbank' for adding features to the question bank. See question/bank/upgrade.txt. 3) Many previously core features have been moved into new plugins, meaning that many old functionsand classes in lib/questionlib.php and other locations have been deprecated and moved: * Moved to qbank_previewquestion: - question_preview_url() is moved to qbank_previewquestion\helper::question_preview_url() - question_preview_popup_params() is moved to qbank_previewquestion\helper::question_preview_popup_params() the following were really part of the internal implementation of preview, so should not have been used elsewhere, but they were also moved (from previewlib.php). - restart_preview() => qbank_previewquestion\helper::restart_preview(), - question_preview_form_url() => qbank_previewquestion\helper::question_preview_form_url(), - question_preview_action_url() => qbank_previewquestion\helper::question_preview_action_url(), - question_preview_question_pluginfile() => qbank_previewquestion\helper::question_preview_question_pluginfile(), - class preview_options_form => 'qbank_previewquestion\form\preview_options_form', - class question_preview_options => 'qbank_previewquestion\output\question_preview_options', * Moved to qbank_managecategories: - qbank_managecategories\helper::question_remove_stale_questions_from_category() - flatten_category_tree() => qbank_managecategories\helper::flatten_category_tree() - add_indented_names() => qbank_managecategories\helper::add_indented_names() - question_category_select_menu() => qbank_managecategories\helper::question_category_select_menu() - get_categories_for_contexts() => qbank_managecategories\helper::get_categories_for_contexts() - question_category_options() => qbank_managecategories\helper::question_category_options() - question_add_context_in_key() => qbank_managecategories\helper::question_add_context_in_key() - question_fix_top_names() => qbank_managecategories\helper::question_fix_top_names() - class category_form => qbank_managecategories\form\category_form - class question_category_list => qbank_managecategories\question_category_list - class question_category_list_item => 'bank_managecategories\question_category_list_item - class question_category_object => qbank_managecategories\question_category_object - class question_category_edit_form => qbank_managecategories\form\category_form - class question_move_form => qbank_managecategories\form\question_move_form * Moved to qbank_exporttoxml: - question_get_export_single_question_url() -> qbank_exporttoxml\helper::question_get_export_single_question_url(). * Moved to qbank_exportquestions: - class question_export_form => qbank_exportquestions\form\export_form - class export_form => qbank_exportquestions\form\export_form * Moved to qbank_importquestions: - class question_import_form => qbank_importquestions\form\question_import_form * Moved to qbank_tagquestion: - submit_tags_form and associated external services for question tag, - tags_form in question/type, - core_question_output_fragment_tags_form() => /question/bank/qbank_tagquestion/lib.php. 4) The following functions in questionlib.php now using type hinting. So, if you call them with the wrong types, you will now get fatal errors. - is_latest() - get_next_version() - get_question_version() - get_question_bank_entry() - core_question_find_next_unused_idnumber() - question_module_uses_questions() - question_page_type_list() - core_question_question_preview_pluginfile() - question_rewrite_question_preview_urls() - question_rewrite_question_urls() - question_get_all_capabilities() - question_get_question_capabilities() - question_require_capability_on() - question_has_capability_on() - question_default_export_filename() - get_import_export_formats() - question_categorylist_parents() - question_categorylist() - question_make_default_categories() - question_get_top_categories_for_contexts() - sort_categories_by_tree() - print_question_icon() - question_sort_tags() - _tidy_question() - question_preload_questions() - question_move_category_to_context() - move_question_set_references() - question_move_questions_to_category() - idnumber_exist_in_question_category() - question_move_question_tags_to_new_context() - question_delete_activity() - question_delete_course_category() - question_delete_course() - question_delete_context() - question_delete_question() - delete_question_bank_entry() - question_category_in_use() - question_category_delete_safe() - question_context_has_any_questions() - questions_in_use() - question_save_qtype_order() - question_reorder_qtypes() 5) Function question_hash() from questionlib.php is deprecated without replacement. 6) The following classes have been moved, to better follow Moodle's name-space usage rules: 'core_question\bank\action_column_base' => 'core_question\local\bank\action_column_base', 'core_question\bank\checkbox_column' => 'core_question\local\bank\checkbox_column', 'core_question\bank\column_base' => 'core_question\local\bank\column_base', 'core_question\bank\edit_menu_column' => 'core_question\local\bank\edit_menu_column', 'core_question\bank\menu_action_column_base' => 'core_question\local\bank\menu_action_column_base', 'core_question\bank\menuable_action' => 'core_question\local\bank\menuable_action', 'core_question\bank\random_question_loader' => 'core_question\local\bank\random_question_loader', 'core_question\bank\row_base' => 'core_question\local\bank\row_base', 'core_question\bank\view' => 'core_question\local\bank\view', 'core_question\bank\copy_action_column' => 'qbank_editquestion\copy_action_column', 'core_question\bank\edit_action_column' => 'qbank_editquestion\edit_action_column', 'core_question\bank\creator_name_column' => 'qbank_viewcreator\creator_name_column', 'core_question\bank\question_name_column' => 'qbank_viewquestionname\viewquestionname_column_helper', 'core_question\bank\question_name_idnumber_tags_column' => 'qbank_viewquestionname\question_name_idnumber_tags_column', 'core_question\bank\delete_action_column' => 'qbank_deletequestion\delete_action_column', 'core_question\bank\export_xml_action_column' => 'qbank_exporttoxml\export_xml_action_column', 'core_question\bank\preview_action_column' => 'qbank_previewquestion\preview_action_column', 'core_question\bank\question_text_row' => 'qbank_viewquestiontext\question_text_row', 'core_question\bank\question_type_column' => 'qbank_viewquestiontype\question_type_column', 'core_question\bank\tags_action_column' => 'qbank_tagquestion\tags_action_column', 'core_question\form\tags' => '\qbank_tagquestion\form\tags_form', 'core_question\output\qbank_chooser' => 'qbank_editquestion\qbank_chooser', 'core_question\output\qbank_chooser_item' => 'qbank_editquestion\qbank_chooser_item', 7) The Behat class for question-related steps has been renamed to behat_core_question to match the expected naming convention. In the unlikely event that you are directly referring to the behat_question class name (nothing in the standard Moodle code was) then you will have to update your reference. === 3.9 === 1) For years, the ..._questions_in_use callback has been the right way for plugins to tell the core question system if questions are required. Previously this callback only worked in mods. Now it works in all plugins. At the same time, if you are still relying on the legacy ..._question_list_instances callback for this, you will now get a debugging warning telling you to upgrade. 2) Previously, the functions question_delete_activity, question_delete_course and question_delete_course_category would echo output. This was not correct behaviour for a low-level API function. Now, they no longer output. Related to this, the helper function they use, question_delete_context, now always returns an empty array. This probably won't acutally cause you any problems. However, you may previously have had to add expectOutputRegex calls to your unit tests to avoid warnings about risky tests. If you have done that, those tests will now fail until you delete that expectation. === 3.8 === If you have customised the display of the question bank (using $CFG->questionbankcolumns) then be aware that the default configuration has changed, and you may wish to make equivalent changes in your customised version. The old column question_name_column has been replaced by question_name_idnumber_tags_column. The old question_name_column still exists, so it is safe to continue using it. There is a new question bank column edit_menu_column which displays all actions in a drop-down menu, instead of as separate icons. This is now used by default. Specifically, it gathers all other columns which implement the new interface menuable_action. If you have made a custom subclasses of action_column_base, you probably want to implement the new interface. If your column is a simple action, the easiest way to do this will be to subclass menu_action_column_base. If your action is more complex, and does not follow the simple pattern that menu_action_column_base uses, then you will need to implement menuable_action yourself. The commit for MDL-66816 updates all the core action columns. Looking at that change should make it clearly the changes you need to make to your columns. === 3.7 === The code for the is_valid_number function that was duplicated in the qtype_numerical and qtype_multianswer plugins in the qtype_numerical_edit_form and qtype_multianswer_edit_form classes has been moved to a static function in the qtype_numerical class of the qtype_numerical plugin. The exportprocess function of the qformat_default class doesn't output a blank line if the result of the writequestion function is null. This permit to qformat plugins to ignore some questions without the need to overwrite this function. * The question_preview_cron() has been deleted. Please use \core\task\question_cron_task::execute(). * The question_usage_statistics_cron() has been deleted. Please use \core\task\question_cron_task::execute(). * The method question_bank::cron() has been deleted, please use question related scheduled tasks. === 3.5 === 1) The question format exportprocess function now adds a $checkcapabilities boolean to allow questions to be exported in certain circumstances. === 3.2 === 1) The following renderers have been deprecated in favour of the renderable core_question\output\qbank_chooser and associated render_* method. * qbank_chooser * qbank_chooser_types * qbank_chooser_qtype * qbank_chooser_title === 3.1 === 1) The argument $requirecourseid was removed from question_edit_setup() and is no longer respected. The behaviour was found to be buggy and now throws debugging notices if passed. === 2.9 === 1) Some functions in questionlib.php which were deprecated in the past have now been deleted: Deprecated since 2.1 * question_list_instances * get_grade_options * question_category_isused * save_question_options * question_get_real_state Deprecated since 2.6 * question_rewrite_questiontext_preview_urls * question_send_questiontext_file * question_pluginfile no longer falls back to using the old {$previewcomponent}_questiontext_preview_pluginfile callback if the new {$previewcomponent}_question_preview_pluginfile callback is missing. === 2.8 === 1) This is just a warning that some methods of the question_engine_data_mapper class have changed. All these methods are ones that you should not have been calling directly from your code, so this should not cause any problems. The changed methods are: * insert_question_attempt * insert_step_data * update_question_attempt_step === 2.7 === 1) Changes to class question_bank_view: Filters, including $recurse and $showhidden, are now implemented as pluggable \core_question\bank\search\condition classes. Therefore $recurse and $showhidden are no longer passed to the following functions: protected function display_options [deprecated, use display_options_form()] protected function build_query_sql [deprecated, use build_query()] protected function display_category_form() is deprecated. Use \core_question\bank\search\category_condition protected function display_category_form_checkbox deprecated use html_writer::checkbox and separate JavaScript To add filters, local plugins can now implement the function local_[pluginname]_get_question_bank_search_conditions, 2) To make columns available to question_bank_view, plugins can extend core_question\bank\column_base. Users may choose to display additional columns by setting $CFG->questionbankcolumns to a comma-delimited list of columns. 3) The subsort separator has changed from _ to - in order to distinuguish subsorts vs frankenstyle component separators. 4) Because of the move to autoloading, $knowncolumntypes and known_field_types() are no longer used. 5) question_bank_column_base and it's derived classes have been namespaced to core_question\bank\column_base. === 2.6 === 1) Modules using the question bank MUST now declare their use of it with the xxx_supports() flag FEATURE_USES_QUESTIONS. question_module_uses_questions() should be used to determine if a module uses questions. 2) It is sometimes necessary to display bits of question content without having and attempt (question_usage) in progress. Two examples of this are the option in the question bank to display the questiontext, and in the quiz statistics report, where it displays the question text above the report. Previously, this display was done using a special method that only worked for the question text, but which would not work for other parts of the question. That old mechanism has been deprecated, and there is a new method that you should use. To display the question, replace calls to question_rewrite_questiontext_preview_urls with calls to question_rewrite_question_preview_urls. Because the new function is more flexibile, you have to pass more arguments. To perform the necessary permission checks when the file is downloaded, you need to implement the callback [component name]_question_preview_pluginfile. (Previously you implemented [component name]_questiontext_preview_pluginfile.) quiz_statistics_question_preview_pluginfile is an example of what to do. question_send_questiontext_file has been deprecated. It is no longer necessary. To ensure you are no longer using or defining any deprecated functions, search for the regular expression: question_rewrite_questiontext_preview_urls|_questiontext_preview_pluginfile|question_send_questiontext_file 3) The argument list for core_question_renderer::mark_summary has changed. Please update your calls. (The most likely scenario for this is if you have overridden core_question_renderer::info in your own renderer.) You need to make a change like: - $this->mark_summary($qa, $options); + $this->mark_summary($qa, $behaviouroutput, $options); home3/cpr76684/public_html/Aem/mod/book/upgrade.txt 0000644 00000002310 15152625625 0015674 0 ustar 00 This files describes API changes in the book code. === 4.0 === * book_get_nav_types() has been deprecated. Related settings have been removed. The navigation is now set to only "next" and "previous". === 3.11 === * Final deprecation - booktool_print_get_toc(). Please use render_print_book_toc() instead. === 3.8 === * The following functions have been finally deprecated and can not be used anymore: * book_scale_used() === 3.7 === * book_export_contents() callback now returns tags information for every chapter. === 3.1 === * The following functions, previously used (exclusively) by upgrade steps are not available anymore because of the upgrade cleanup performed for this version. See MDL-51580 for more info: - mod_book_migrate_moddata_dir_to_legacy() - mod_book_migrate_all_areas() - mod_book_migrate_area() === 3.0 === * External function mod_book_external::get_books_by_courses returned parameter "name" has been changed to PARAM_RAW, this is because the new external_format_string function may return raw data if the global moodlewssettingraw parameter is used. === 2.7 === * bogus legacy log calls were removed * \mod_book\event\chapter_deleted::set_legacy_logdata() was removed
| ver. 1.4 |
Github
|
.
| PHP 7.4.33 | ���֧ߧ֧�ѧ�ڧ� ����ѧߧڧ��: 0 |
proxy
|
phpinfo
|
���ѧ����ۧܧ�