-
Improvement
-
Resolution: Done
-
Minor
-
None
-
5.0
-
MOODLE_500_STABLE
-
-
-
5
-
Team Alpha - Sprint 3 I1-2025, Team Alpha - Sprint 4 I1-2025, Team Alpha - Planning I2-2025
MDL-79109 now includes lti_resource_link (and a persistent). Now, instead of link data being included inside the lti record, we've pulled it out and store it in core_ltix. Links should be created by providing (among other things) {'component', ''itemtype', 'itemid', 'contextid'}, which uniquely identify the link for a given component, meaning the component can fetch the links later.
This issue is scoped with:
- Creating/updating the resource link in core_ltix at the point where we're saving the mod_lti instance. See lti_add_instance() and lti_update_instance().
- Deleting the links on mod instance deletion, see lti_delete_instance().
In terms of the unique identifiers to use, we should use:
'itemtype': use 'mod_lti:activityplacement' string (the same string in mod/lti/db/lti.php - the placement type)
'itemid': use the cmid of the instance (available as $lti->coursemodule in the above add/update methods, I believe).
This ensures we can find the link later, when we want to launch it.
Links can be created with or without deep linking, so we need to make sure that's tested. Also, we should test the "create multiple links via a single deep linking" scenario, if possible, just to make sure that's covered.
- blocks
-
MDL-84653 Support resource links in the core_ltix privacy provider
-
- Open
-