Resource module file API migration: Difference between revisions
From MoodleDocs
Line 14: | Line 14: | ||
* Packages and uploaded html files | * Packages and uploaded html files | ||
* Other 3rd party plugis | * Other 3rd party plugis | ||
=Upgrade problems= | |||
* Migration of files used by resources to resource file areas (linked files mainly) | |||
* Should we split resource into multiple modules and delegate more work to Repositories? | |||
* Current repository/file api does not have suitable UI for selection of main/index file in case of packages and uploaded html files. | |||
=See also= | =See also= |
Revision as of 22:08, 11 May 2009
Moodle 2.0
Current problems
- text and html resource types separate
- embedded images and files in general are stored in course files without appropriate access control
- local files and Internet links mixed
- is IMS plug-in maintained?
- repository plug-in obsoleted
Types of resources
- Resource page - using new editor element
- External resource link - some file stored elsewhere
- Single uploaded images and files
- Packages and uploaded html files
- Other 3rd party plugis
Upgrade problems
- Migration of files used by resources to resource file areas (linked files mainly)
- Should we split resource into multiple modules and delegate more work to Repositories?
- Current repository/file api does not have suitable UI for selection of main/index file in case of packages and uploaded html files.
See also
- Using the file API
- Repository API
- Portfolio API
- File API
- MDL-14589 - File API Meta issue
- MDL-16089 - Resource module conversion