* The fields for the ID number-related indexes that were created for
the question and question_categories tables in MDL-62708 should not
be in comma-separated strings.
* The fields for the ID number-related indexes that were created for
the messages and message_user_actions tables in MDL-36941 should not
be in comma-separated strings.
Refactored quiz_statistics_table class to remove some duplications by defining and using
format_range(), format_percentage() and format_percentage_range() methods.
Part of MDL-62610
Variants should also be treated like random questions in the sense that
a summary row
should be displayed for them as well.
This commit deals with handling variants.
Also the name of the calculated_random_question_summary class has
changed to
calculated_question_summary to be more generic as the summary row is not
specific to random questions only.
Also removed the protected function too_many_subq_and_or_variant_rows
and the const SUBQ_AND_VARIANT_ROW_LIMIT as they were not being used
anymore.
Part of MDL-62610
Fixed calculated_random_question_summary:get_min_max_of and calculated_random_question_summary:get_min_max_of_sd
functions and added unit tests
Part of MDL-62610
The statistics table have been modified so that the summary row shows the minimum and maximum
values of each column for the set of questions that are being summarised.
Part of MDL-62610
Moved 'percents' lang string from workshopform_numerrors to core_moodle.
AMOS BEGIN
MOV [percents,workshopform_numerrors],[percents,core_moodle]
AMOS END
Part of MDL-62610
Modified calculated_random_question_summary class so that it can return minimum and maximum
of each attribute of the sub questions it is summarising.
Part of MDL-62610
* Use standard Bootstrap4 table classes for the categories and purposes
tables.
* Set w-25 for the name and description columns of the purposes table.
* Set w-50 for the description column of the categories table.
* Set a minimum width for the actions column of these tables.
The message_contact_blocked and message_contact_unblocked
events were deprecated. The reason being that you will be
able to block and unblock any user, regardless if they are
a contact or not. This information is also now stored in a
separate DB table.
Remove any duplicate rows - from now on adding contacts just requires 1 row.
The person who made the contact request (userid) and the person who approved
it (contactid). Upgrade the table so that the first person to add the contact
was the one who made the request.
Allow NULL values for timecreated in both message_contacts
and message_users_blocked because there is existing data
that has no timecreated value associated with it.
