* Rebase and resolve conflicts from initial patch.
* Reorganise contentitem and contentitem_return pages.
* Add capability checks for contentitem and contentitem_return pages.
* Move the building of Content-Item selection request to a local
lib function.
* Move contentitem_return processing logic to a local lib function.
* Fix type settings update. Content-item checkbox does not get
checked/unchecked on load.
* Fix tool settings update. Disabled content-item checkbox gets unchecked when
tool settings form is submitted.
* Add "Select content" button on load which launches the content item
selection dialogue.
* Move hardcoded HTML and JS to mustache templates and AMD modules.
* Use standard YUI dialog for displaying the Content-Item selection page.
* Added processing for the following Content-Item properties:
- text
- icon
* On ContentItem selection, fill out form with the configuration data retrieved,
instead of automatically saving the tool and redirecting to the course page.
* Removed section- and sectionreturn-related code since we're not automatically
adding the tool on ContentItem selection.
* On mod_lti_mod_form, enable configuration fields if they support ContentItem
selection.
* New form-field module for setting fields using JS
* Change types_config table's 'value' column from char(255) to text
* Fixed XML loading when there is an error
* Fixed exception thrown by lti_load_cartridge
* By default, don't allow LTI mod generator to
use a toolurl as that results in a cURL call.
1. getMock()
2. setExpectedException()
3. checkForUnintentionallyCoveredCode renamed to beStrictAboutCoversAnnotation
4. beStrictAboutTestSize renamed to enforceTimeLimit
5. UnitTestCase class is now fully removed.
* Use clean_param() for name and description when displaying the tool type.
Basically in the following functions:
- serialise_tool_type()
- lti_get_configured_types()
* Changed name and description's type from PARAM_TEXT to PARAM_RAW
in tool update parameters.
* Changed name and description's type from PARAM_TEXT to PARAM_RAW
in mod_lti_external::tool_type_return_structure()
dirname() is a slow function compared with __DIR__ and using
'/../'. Moodle has a large number of legacy files that are included
each time a page loads and is not able to use an autoloader as it is
functional code. This allows those required includes to perform as
best as possible in this situation.
If creating a proxy fails, we will show an error using the
notification API. So we can remove the notification.exception call.
But modify the docs for ToolProxy.create so that future developers
will know they need to handle failures themselves.
Only show one, more helpful error instead of two non-helpful errors.
Don't show the 'no configured tools' message if there is a proxy there.
Return to the Tool configure page when editing a proxy if you came
from it.
