See notes on:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Charset
Warning: Do not use this header. Browsers omit this header and servers
should ignore it.
The Accept-Charset request HTTP header was a header that advertised a
client's supported character encodings. It is no longer widely used.
UTF-8 is well-supported and the overwhelmingly preferred choice for
character encoding. To guarantee better privacy through less
configuration-based entropy, all browsers omit the Accept-Charset
header.
Prior to this change, when importing grades from .csv (or another
method) and you choose to map the grades to a 'New grade item', you get
the following error message:
```
"Mapping collision detected - two fields maps to the same grade item
new."
```
A workaround existed that required users to import one column at a time,
which was cumbersome.
This change fixes importing multiple new grade items and adds a behat
test.
Co-authored-by: hehe009 <max_kan@hotmail.com>
Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
The default option "ASSIGN_ATTEMPT_REOPEN_METHOD_NONE" for the
"attemptreopenmethod" setting, which disallows multiple attempts at the
assignment, has been removed. This option was unnecessary because
limiting attempts to 1 through the "maxattempts" setting achieves the
same behavior.
Apart from removing this setting option (including removal of usage in
code and updating existing data in the DB), these changes include:
- Introducing a more effective progressive disclosure by allowing the
"maxattempts" setting to control the visibility of the
"attemptreopenmethod" setting in the form.
- String improvements to the labels and help text for the "maxattempts"
and "attemptreopenmethod" settings
- Changing the default value of the "maxattempts" setting from
"unlimited" to "1"
Usage:
node .grunt/upgradenotes.mjs
OR
npm run upgradenote
Arguments can be provided to specify the issue number, component,
message, and type of change.
node .grunt/upgradenotes.mjs -- \
-c [component] \
-i [issue number] \
-t [type] \
-m [message]
OR
npm run upgradenote -- \
-c [component] \
-i [issue number] \
-t [type] \
-m [message]
Summary Markdown files can be created using:
node .grunt/upgradenotes.mjs summary
Weekly release files can be created using:
node .grunt/upgradenotes.mjs release
Final release files can be created using:
using:
node .grunt/upgradenotes.mjs release [version]
Generally speaking the integration team will be responsible for updating
the UPGRADING.md notes as part of the weekly integration processes.
When the question custom fields were deleted, if there were any
hidden columns in qbank Column sort order referring those fields they
were throwing 'Custom field does not exist' exception. Changes done to
ignore such fields and display valid hiddencols, as these references
were breaking the qbank Column sort order and Question bank pages.
Finding the page layout fallback was trying to get a default layout from
the ancient theme called "base". This default theme do not exists
anymore and defining a wrong layout in a theme is a code mistake that
should not be bypassed.
