MDL-61837 core_question: replace tag fields on tag modal
[moodle.git] / question / type / upgrade.txt
1This files describes API changes for question type plugins.
94cb5a66 3=== 3.5 ===
4 + Added new classes backup_qtype_extrafields_plugin and restore_qtype_extrafields_plugin
5 in order to use extra fields method in backup/restore question type. Require and inherit new classes for using it. See
6 backup_qtype_shortanswer_plugin and restore_qtype_shortanswer_plugin for an example of using this.
7 + The declaration of is_gradable_response has been moved from question_automatically_gradable to
8 question_manually_gradable.
9 + The default implementation of is_gradable_response has been moved from question_graded_automatically to
10 question_with_responses.
5a8d683f 11
12=== 3.1.5, 3.2.2, 3.3 ===
14* If you are using check_combined_feedback_file_access in your check_file_access method,
15 then you must now pass $args as the 4th argument, so the correct permission checks
16 can be performed. If you don't, you will get a developer debug notice.
18=== 3.1 ===
20* The following functions, previously used (exclusively) by upgrade steps are not available
21 anymore because of the upgrade cleanup performed for this version. See MDL-51580 for more info:
22 - qtype_essay_convert_to_html()
24=== 2.7 ===
25 + We have added a new method to the question_type base class 'break_down_stats_and_response_analysis_by_variant'. By default it
26 returns true. If your question type does not have variants of question instances then you can ignore this method as it only
27 applies to question types that have variants. If a question type does have variants the default action is to break down
28 response analysis and question stats by variant. But for some question types there might be an almost infinite quantity of
29 variants for the question, in this case you can suppress break down by variant by returning false from this method. See for
30 example the non-core question type varnumeric or the slightly more complex stack question type.
31 + We have added a pair of methods to the question_definition class 'prepare_simulated_post_data' and
32 'get_student_response_values_for_simulation'. You may want to override these methods in question.php in your question type plug
33 -in. These methods are used to convert data from a csv file of simulated step data into the simulated post data that is fed
34 to the question engine. These csv files can be used for unit testing or manual testing the use of your question type within the
35 quiz module. You can use the simulate quiz report for manual testing and also to easily generate csv test files. You can
36 run a number of students through a test and then download a csv file representing their interaction with the quiz. For most
37 question types the default of just passing csv data as post data, directly from the csv file will probably work fine. But for
38 certain question types where the meaning of the post data is deliberately obfuscated it might be necessary to convert from a
39 human friendly format in the csv file to response data expected by the question type using 'prepare_simulated_post_data' and
40 to convert back from a question type response array to values for download in a csv file using
41 'get_student_response_values_for_simulation'.
42=== 2.6 ===
43 + The changes in MDL-32750 were reverted in favour of the new pdw toggle toolbars
44 plugin for TinyMCE. The get_non_collapsible_editor_options method has been deprecated.
46=== 2.5 ===
dc38c5b4 48* There have been some tweaks to the helper class that is used to write
49 walkthrough tests. You should not have to change your code, but you might
50 like to take a look at some of the new helper methods available. In particular,
51 if you had any code that did
52 $this->process_submission(array('-finish' => 1));
53 you should change that to
54 $this->finish();
56* There have been lots of usability improvements to the question editing forms.
57 MDL-37417 links to all the changes. There are only a few API changes that
58 *require* you to upgrade your question type, but you are strongly recommended
59 to make similar usability improvements in your own question types.
61 + Some of the ids used in the form HTML have had ‘id_’ added at the front.
62 Take care if you refer to these in your JavasSript or CSS.
64 + MDL-32750 The HTML editing tools are now collapsed. This is applied by default
65 to all HTML editors except question text and general feedback. If you want to
66 add more exceptions, see the get_non_collabsible_editor_options method.
68 + Form fields have been grouped onto one line where appropriate, to reduce
69 the height of the form. qtype_numerical is a good example of this.
71 + Where elements are in groups, we have changed the normal accesshide CSS, so
72 that their labels are visible. If you were using grouped elements in the past
73 with static elements to lable the fields, then you will need to remove the statics.
75 + All the choices / answers have been merged into a single section of the form.
76 This works better with the new 'shortforms' MDL-30637. Also the
77 "Add blanks for more ..." buttons are now inside that section. This probably
78 requries that you remove any headings from your per-answer fields, and change
79 some of the labels.
81 + Having merged all the elements into one form section, we then used CSS to
82 visually group the fields for one choice, answer, etc.
84 + When editing an existing question, we only show as many repeats are are
85 actually needed until the user clicks the "Add blanks for more ..." button.
86 Where you have your own repeat elements, you may need to change the
87 number of repeats calculation.
89 + As with all forms, setType() is now required for all text form elements.
91 + A good example of a question type being upgraded to take account of all these
92 changes is
eca230b5 95
96=== 2.3.5 / 2.4.2 / 2.5 ===
98* The special value question_attempt::PARAM_CLEANHTML_FILES that could be used
99 in the get_expected_data method was renamed to question_attempt::PARAM_RAW_FILES
100 in order to fix a bug. We failed to think this throught, and so did not realised
101 that this might break some question types. If this affected your question type,
102 please accept our apologies. Details in MDL-37847.
a031b0f3 105=== 2.3 ===
c2f5e2ab 106
107* Support for backwards-compatible string names dropped. MDL-30120. (See under 2.2 below.)
108* If you are overriding export_to_xml and import_from_xml to provide Moodle XML format
109 import and export, then you will probably get PHP strict syntax notices in developer
110 debug mode until you change the method signature to include qformat_xml $format.
111 That is, you need to specify the argument type.
112* qtype_xxx_pluginfile() is now given the 7th parameter (hopefully the last
113 one) that contains additional options for the file serving. The array should
114 be re-passed to question_pluginfile() as is.
117=== 2.2 ===
119* The XML import/export base class has had some minor API changes. The
120 - write_combined_feedback method now requires that you pass the questionid and
121 contextid. (MDL-29058)
122 - calls to the import_hints and import_answer methods now should pass the question
123 text format as the last argument, to be used as a default if necessary. (MDL-29739)
124 If you do not upgrade your code, it will not break, but there will be PHP
125 warnings, and it the export will not work 100% correctly.
127* The old
128 public function requires_qtypes()
129method is no more. Instead use the ->dependencies facility in version.php. E.g.
130$plugin->dependencies = array(
131 'qtype_numerical' => 2011102700,
134* The plugin name and related strings used to be defined in language strings
135called the same thing as the format, for example:
137$string['addingdescription'] = 'Adding a Description';
138$string['description'] = 'Description';
139$string['description_help'] = 'A description is not really a question type. It simply enables text to be displayed without requiring any answers, similar to a label on the course page.
140$string['description_link'] = 'A description is not really a question type. It simply enables text to be displayed without requiring any answers, similar to a label on the course page.
141$string['descriptionsummary'] = 'This is not actually a question. Instead it is a way to add some instructions, rubric or other content to the activity. This is similar to the way that labels can be used to add content to the course page.';
142$string['editingdescription'] = 'Editing a Description';
144All these need to be changed to use the standard string name pluginname, as for
145other plugin types, and similar for the other strings.
147$string['pluginname'] = 'Description';
148$string['pluginname_help'] = 'A description is not really a question type. It simply enables text to be displayed without requiring any answers, similar to a label on the course page.
149$string['pluginname_link'] = 'A description is not really a question type. It simply enables text to be displayed without requiring any answers, similar to a label on the course page.
150$string['pluginnameadding'] = 'Adding a Description';
151$string['pluginnameediting'] = 'Editing a Description';
152$string['pluginnamesummary'] = 'This is not actually a question. Instead it is a way to add some instructions, rubric or other content to the activity. This is similar to the way that labels can be used to add content to the course page.';
154The old strings will continue to work, but only until Moodle 2.3 is released.
156* If you are using the facilities provided by overriding the extra_answer_fields
157 or questionid_column_name methods, then you must change these to be public
158 methods. (This is required so that backup and restore can be made to work
159 automatically. MDL-24408, MDL-25617, MDL-30562)
0b94d6bf 160
0b94d6bf 161
162=== 2.1 ===
164* Lots of API changes due to the new question engine. See
168=== 2.0 ===
170* Lots of changes due to all the API changes in Moodle 2.0.
172* This plugin type now supports cron in the standard way. If required, Create a
173 lib.php file containing
174function qtype_mypluginname_cron() {};