-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send report csv as attachment #55
Comments
Is this feature still being considered? |
Can the Moodle message API handle attachments? If so, this would be a nice feature. Up-to-date pull requests welcome. |
Hi Tim, this plugin is great and implementing this feature could be very useful (in our university I would say necessary). We have read the discussion made in the pull request #86 and, since the Message API still does not support temp files, I would say that the only solution is to use a Stored File. Starting from that, we implemented the feature, paying attention to have all your automated tests working. Giorgio |
Thank you for considering contributing to this plugin. I note that pull request #86 has been sitting around for over 2 years. If, 2 years ago, someone had made a change to Moodle core so that the file API could send temp files, then there would not be an issue any more. On the other hand, just having the files sitting around in moodledate, but not in filedir, causes problems with some ways of setting up cloud hosting, so I am no longer so opposed to saving the reports with the file API, if that is implemented nicely. I think that the key part of working out how to implement this is deciding exactly how things will be stored. Do you have a plan for how you will do it? It would be good to agree on that before you start writing code. Thanks. Tim. |
We want to be able to send data to users in a format that allows them to do their own filtering. Requiring them to log in to download the csv adds extra overhead to the task, so we want to attach the csv to the notification that they get sent.
The text was updated successfully, but these errors were encountered: