Proyectos de Subversion Moodle

Rev

Rev 1 | | Comparar con el anterior | Ultima modificación | Ver Log |

Rev Autor Línea Nro. Línea
1441 ariadna 1
=== 4.5 Onwards ===
2
 
3
This file has been replaced by UPGRADING.md. See MDL-81125 for further information.
4
 
5
===
1 efrain 6
This files describes API changes in /blocks/* - activity modules,
7
information provided here is intended especially for developers.
8
 
9
=== 4.2 ===
10
 
11
* Block configuration form is now displayed in a modal. Class 'block_edit_form' now extends
12
  '\core_form\dynamic_form' and properties $block and $page are read-only. Normally
13
  no changes should be necessary to keep the old behavior of configuration form.
14
* Block plugins can specify that they want to display configuration form when block is
15
  added to the page by overriding static method block_edit_form::display_form_when_adding().
16
* Web service 'core_block_fetch_addable_blocks' accepts new parameter 'pagehash'
17
* JS module 'core/addblockmodal' is deprecated, instead there is new module
18
  'core_block/add_modal' with similar functionality but different arguments.
19
* Functions in the JS modules 'moodle-core-blockdraganddrop' have changed their parameters.
20
  File lib/ajax/blocks.php takes different arguments.
21
  No backward-compatibility is provided since these files are not part of the blocks API
22
  and not intended to be used by plugins.
23
 
24
=== 4.0 ===
25
 
26
* Block block_quiz_results has been completely removed from core.
27
The Quiz results block is hidden by default since Moodle 2.9. It is recommended to use the Activity results block instead, which works with any type of activity (not just quizzes).
28
* External function core_block::get_dashboard_blocks has a new parameter to indicate if you want to receive the block on the my/courses page.
29
* The `core_block_fetch_addable_blocks` external method accepts an optional `subpage` parameter, in order to correctly
30
  calculate available blocks for pages that use this property (e.g. the user dashboard)
31
* A new method, can_block_be_added(), has been added to let blocks override it when they want to include some extra checks
32
to decide whether the block can be added to a page or not.
33
 
34
=== 3.8 ===
35
* Block block_community is no longer a part of core.
36
* Block block_participants is no longer a part of core.
37
* Block plugins should overwrite get_config_for_external function to return the blocks settings viewable by the current user.
38
  If the block plugin does not have any setting that could be considerated private (like a private/access key/token),
39
  is ok to return all the settings via the get_config_for_external function.
40
 
41
=== 3.7 ===
42
* The block:addinstance capability is no longer required if the block can only be added to a dashboard.
43
 
44
=== 3.6 ===
45
 
46
* The timeline view from block_myoverview has been split out into block_timeline.
47
* External function core_blocks::get_course_blocks now returns the block visible status and weight for ordering.
48
* New method added block_base::get_content_for_external(). It will return all the block contents rendered for external functions.
49
  If your block is returning formatted content or provide files for download, you should override this method to use the
50
  external_format_text, external_format_string functions for formatting or external_util::get_area_files for files.
51
  See block_html as example.
52
* External functions core_block::get_course_blocks and core_block::get_dashboard_blocks have a new parameter to indicate if
53
  you want to receive the block contents.
54
 
55
=== 3.4 ===
56
 
57
* The block_instances table now contains fields timecreated and timemodified. If third-party code
58
  creates or updates these rows (without using the standard API), it should be modified to set
59
  these fields as appropriate.
60
* Blocks can now be included in Moodle global search, with some limitations (at present, the search
61
  works only for blocks located directly on course pages or site home page). See the HTML block for
62
  an example.
63
* Block block_messages is no longer a part of core.
64
 
65
=== 3.3 ===
66
 
67
* block_manager::get_required_by_theme_block_types() is no longer static.
68
* The plugin block_course_overview has been removed from core and is being replaced by block_myoverview.
69
  During the upgrade process the block_course_overview block will be uninstalled and all its settings will be deleted.
70
  If you wish to keep the block_course_overview block and its settings, download it from moodle.org and put it back in
71
  the blocks/ directory BEFORE UPGRADING.
72
 
73
=== 3.1 ===
74
 
75
* The collapsed class was removed from the navigation block to make it compatible with aria.
76
* New aria attributes were added on the navigation block [aria-expanded="false"].
77
* The tree JS handling were moved from YUI to AMD module (Jquery).
78
 
79
=== 2.9 ===
80
 
81
* The obsolete method preferred_width() was removed (it was not doing anything)
82
* Deprecated block_base::config_save as is not called anywhere and should not be used.
83
* Added instance_copy() function to the block_base class. This function allows for block
84
  specific data to be copied when a block is copied.
85
 
86
=== 2.8 ===
87
 
88
* The instance_config_print() function was removed. It was deprecated in
89
  Moodle 2.0, but without debugging notices. Since it was no longer a part
90
  of the code path, debugging notices would not have been displayed.
91
* Deprecated functions were removed from the block_base class:
92
** _print_block()
93
** _print_shadow()
94
** _title_html()
95
** _add_edit_controls()
96
** config_print()
97
 
98
=== 2.6 ===
99
 
100
* Deprecated /admin/block.php was removed, make sure blocks are using settings.php instead.
101
 
102
=== 2.4 ===
103
 
104
Created new capability 'blocks/xxx:myaddinstance' that determines whether a user can add
105
a specific block to their My Home page. This capability was only defined for blocks where
106
the applicable_formats function does not include "'my' => false" in the returned array,
107
allowing it be added to the My Home page.
108
 
109
=== 2.3 ===
110
 
111
required changes in code:
112
* block_xxx_pluginfile() is now given the 7th parameter (hopefully the last one) that
113
  contains additional options for the file serving. The array should be re-passed
114
  to send_stored_file().
115
 
116
=== 2.0 ===
117
 
118
required changes in code:
119
* use new DML syntax everywhere
120
* use new DDL syntax in db/upgrade.php
121
* replace defaults.php by settings.php and db/install.php
122
* replace STATEMENTS section in db/install.xml by db/install.php
123
* move post instalation code from install() method into db/install.php
124
* completely rewrite file handling
125
* rewrite backup/restore
126
* theme changes: move plugin styles into blocks/xxx/styles.css and use new css markers for images,
127
                 move all images into new blocks/xxx/pix/ directory and use new outputlib api
128
                 old global $THEME is fully replaced by $OUTPUT
129
* remove '_utf8' from language pack names, use new {$a} syntax in language packs
130
* use 'pluginname' lang pack identifier instead of 'blockname'
131
* move cron and version number into standard version.php
132
* removed support for old config_global.html, use settings.php