Love this plugin and use it on MANY Moodle sites. However it hasn't officially been compatible with Moodle 3.2+ and PHP 7.x.
The Moodle community is wondering if you are planning on releasing an update compatible with more recent releases of Moodle or if we should consider this plugin abandoned and focus on Ad-Hoc Database Queries which recently release a version compatible with Moodle 3.4. I understand that life can get in the way but we would really appreciate a quick note from you to learn you intentions... please.
Like you, and lot of other people, i wait for a new version, officialy compatible with Moodle 3.2 to 3.4 (and soon 3.5), and PHP 7.x.
Juan said some months ago that it wasn't abandoned, but he had lot of work.
And i imagine that, working for the mobile version, with the new plugin support for mobile and Moodle 3.5 coming soon, Juan won't have time to work on this before june...
But it would be really helpful to have new versions before this summer, to allow everybody to update easily. So i really hope that, when Moodle 3.5 is out, and mobile version also, Juan will take time to update this plugin soon.
We want to support the further development of your plugin for Moodle 3.3 to 3.5.
What is needed?
What can we do?
(But no money. We can bring in man power for programming, testing, documentation.)
If you or someone of your organisation has time and competencies for that, i think you can do the job to improve the plugin and make it compatible with changes by Moodle 3.3 and by Moodle 3.4 (perhaps check other upgrade.txt files, for other Moodle versions).
You'll also have to check it installs and upgrade well on several Moodle versions, and everything works OK.
Different changes should be made in different commit, all accessible somewhere with git.
Hope this helps,
Thank you for your feedback in regards to this Séverin Terrier. It would be fantastic if this plugin could be supported as a CORE plugin. How could we as a community move to do that so this plugin has additional support and the development does not fall on one developer? Thanks for any suggestions! -Ben
You could create a tracker item to ask for this inclusion in core, and ask people to vote for it, but not sure (at all) it will be sufficent.
You could also create an MUA (Moodle User Association) project for it.
Amazing! Looking forward to this!
Wow. Thanks for your support with this Elizabeth. I know the community will be excited to explore the potential with CR as a core feature.
Thanks for your answer.
We will check with our programmers what we can do.
just some news about the plugin.
After several months of discussions and trying to find someone to help with the plugin, I'm very happy to say that Sara Arjona (a colleague from Moodle HQ) it is going to spend some time working on the plugin to fix several issues and have a working version for Moodle 3.6
Thank you to Moodle HQ (and especially Sander) for allowing Sara to work on this.
Great, thank you verý much! Will search and try that!
Thank you for sharing this good news Juan about Configurable Reports Juan! Does HQ have a timeline or roadmap of when updates to the plugin will be released?
for now, it was only decided to make all the required fixes to make the plugin work properly in 3.6 (and future 3.7)
Hi Juan et al,
Just a quick question,
Could you please help directing me where configurable reports stores its downloadable CSV files?
This is excellent news, thanks Juan and Sara.
We have been working on CR for a couple of clients. We would be happy to assist by sharing what we have done. Just have Sara reach out and I will connect her with David Saylor, our lead developer.
We have some added some new features, such as scheduled reports and some new filter / menu options such as allowing more than one text search and labels for text searches.
Thanks for your support! It's really exciting to be able to contribute to update and improve this useful and amazing plugin developed by Juan.
For now, as Juan said, my priority number one is to make it work with the most recent Moodle versions (i.e. replace deprecated functions or implement the privacy API).
I've started reviewing the Pull Requests sent to the GitHub project, to take into account the patches prepared by some of you. Then I was planning to continue fixing the main issues raised in the tracker or in GitHub to make CR compatible with the most recent versions and finally, if I have enough time, I'll also try to include some improvement.
Please, feel free to contact me or send your improvements to the GitHub project (as you prefer).