Reports: Course size
report_coursesize
Maintained by 
Dan Marsden, 
Peter Bulmer, 
Catalyst IT
This plugin provides approximate disk usage by Moodle courses.
4234 sites
1k downloads
68 fans
Current versions available: 6
This plugin provides approximate disk usage by Moodle courses.
There are 2 known shortcomings with this plugin
- If the same file is used multiple times within a course, the report will report an inflated disk usage figure as the files will be counted each time even though Moodle only stores one copy of the file on disk.
- If the same file is used within multiple courses it will be counted in each course and there is no indicator within the report to inform the user if they delete the course or files within the course they will not free that amount from disk.
It should be possible to improve the report to address these issues - we'd greatly appreciate any patches to improve the plugin!
To improve the performance of the total disk usage check, you should configure the pathtodu in your installation:
https://docs.moodle.org/en/System_paths#Path_to_du
Useful links
Screenshots
Contributors
Dan Marsden (Lead maintainer)
Peter Bulmer: Developer
Catalyst IT
Please login to view contributors details and/or to contact them
Awards
Comments 
Comments
Please login to post comments
Many thanks for sharing this plugin with the Moodle community. I believe that the report will be very useful to site admins. This question of how big a course is comes up frequently. I noticed that the particular version provided does not specify for which version(s) of Moodle it is intended. I believe you can edit the details of the version and select the versions under Supported software.
Please review the validation results and fix all of the issues mentioned. These changes are typically pretty easy to make but if you have any questions just let us know. In your case it is just a matter of adding the release to the version.php:
Release name ($plugin->release) not found in version.php
I noticed that you did not specify an issue tracker for your plugin. Providing a place for users of your plugin to report issues encourages participation and provides a way for users to report bugs, make feature requests, or suggest other types of improvements. There are a couple of options. You are welcome to request that a component be created in the Moodle Tracker. This will allow for you to become more familiar with how issues are managed in Moodle core but may take a little more time to setup. Alternatively, for folks who are using Github.com, you can use the issues feature of Github to handle such requests. Kindly let me know which of these two options seems best for you.
Please provide a documentation URL. You are welcome to create your documentaiton in Moodle Docs, See http://docs.moodle.org/dev/Plugin_documentation for more information.
I did not attempt to install and test the plugin because of not being sure for which versions it was intended; however, once that is done then we can take another look at it. For now, I am going to mark this plugin as needing more work until we get these issues resolved. Thanks for your patience with the review and approval process.
Peace -Anthony
It is encouraged to follow Moodle’s coding style as outlined in: http://docs.moodle.org/dev/Coding_style and http://docs.moodle.org/dev/Coding The code checker plugin can be quite helpful in fine tuning your code and can be found at: https://moodle.org/plugins/view.php?plugin=local_codechecker You may wish to consider using that tool to further improve your plugin. I only noticed some minor space issues but here are the results:
Files found: 6
report/coursesize/lang/en/report_coursesize.php
report/coursesize/index.php - 0 error(s) and 1 warning(s)
report/coursesize/db/access.php
report/coursesize/version.php
report/coursesize/settings.php
report/coursesize/README.txt - 1 error(s) and 0 warning(s)
Looks good so I am going to go ahead and approve. Peace - Anthony