people who enrol in the course.
$course->defaultrole defines the value for each course for what role
should be used in the same case. Naturally it defaults to the site config
(when it is zero).
This role is retained even when the person editing the course settings
doesn't actually have that role in their list of assignable rights (however
they are prevented from actually switching to any such role themselves).
Note that enrol plugins are free to ignore these values and use whatever
roles they like. Generally, though, they should respect these settings.
Reports now don't need mod.php but they should include the admin headers/footers.
There are undoubtedly bugs in this but this framework should be more sane
* proposed by Martin Dougiamas
* implemented by skodak
Usage:
1/ change enabletrusttext to yes in site settings (it is off by default) or set it in config.php
2/ assign moodle/site:trustcontent capability to users whose text submitted in glossary entries, comments, forum posts etc. should not be cleaned == they can use javascript or any other forbidden tags in glossary and forums...
done:
* core
* glossary (without proper upgrade)
to do:
* data cleaning in upgrades
* forum, blocks and some other places (MD decides)
