Moodle plugins directory: VMoodle | Moodle.org
VMoodle
IMPORTANT NOTE FOR PLUGIN ARCHIVE AVAILABILITY
: due to the large amount of plugins supported, it is NOT affordable
for us to update moodle.org packages. Please use the Source Control urls
to our github to get plugins archives.
VMoodle provides an infrastructure to virtualize moodle getting many platforms running on the same codebase. VMoodle can register moodle "templates", as a complete snaphsot of a preset Moodle and create new moodles from this template in a few clicks.
Vmoodle provides :
- Moodle instance creation, monitoring and management
- Moodle Mnet "supernetwork" command system, running meta-adminsitration commands over several or all instances.
The Moodle 2.x versions are the result of the French state level project "ENTLibre 2.0" Of the National Funding program "Investissement d'Avenir"
Important notice: From Moodle 2.8 Upwards, the core implementation of VMoodle has moved to the local VMoodle plugin. This plugin is awaiting approval at this moment. You may find the last code of the plugin in http://github.com/vfremaux/moodle-local_vmoodle repository.
VMoodle is now maintained at Activeprolearn.com.
Screenshots
i've moved this into the 'Other' category as this plugin cannot be installed easily by an automated system.
Perhaps if we can work on MDL-34632 sometime we won't need patching to config.php but can instead use a callback as a hook (if not events).
I think a video showing how this is/was used will be really useful in the long description here for anyone looking at this as it can seem complicated.
In future it would be great if this was transformed into a local plugin using those events/hooks etc.
About the question of making a local plugin : anyway needs VMoodle be monitored and operated from somewhere, thus a block was interesting to give at least an accesspoint to backoffice. Maybe the local plugin could now add adequate Admin links to do it... yeah that seems a good idea indeed, as the position of this bloc in the GUI was not so pretty.... i'll take some time ASAP to consider this architecture shift.
I was looking at your VMoodle block and I noticed that the English language strings are not available for translation at AMOS, which most likely means that there is something not quite right in the plugin code. I think you might want to contact David Mudrak about this.
In the meantime, I downloaded the files and I hope I will have the spanish translation of the English strings in a few days.
I also checked the documentation page at http://docs.moodle.org/23/en/VMoodle_Block, added a link to the spanish translation for the 2.3 page version (which seems to be newer than the 2.4 version), and corrected a couple of minor English typos, all of which you can see in the history tab of the page.
Thanks again for a very promising add-on for large Moodle sites (such as my University).
It seems i have a persistant trouble with this package as package info form gets empty (need sto hand fill field) and AMOS warning is raised... Are there any new rules for packaging i need to know ?
Cheers
Valery.
I installed the plugin on Moodle 2.5+. Seems to be fine. But when making the Snapshot Moodle Master Step 1 I get following message: 'Database dump command /usr/bin/mysqldump does not match any executable' - what ca I do?
Cheers. Tabea
You need to make sure that in the admin settings the MySQLdump path is set properly.
The message you get indicates the Mysqldump executable is not in its default location, you may refere to your system administrator for the exact path .
best regards
Wafa
Home
Coding error detected, it must be fixed by a programmer: required_param() requires $parname and $type to be specified (parameter: vdbtype)
and above error is displayed pressing the "database connection test" button
To fix it, you need to modify this file: /moodle/blocks/vmoodle/views/management.testcnx.php
just add the parameter type for each requiring parameters
$database->vdbtype = required_param('vdbtype', PARAM_RAW);
$database->vdbhost = required_param('vdbhost', PARAM_RAW);
$database->vdblogin = required_param('vdblogin', PARAM_RAW);
$database->vdbpass = required_param('vdbpass', PARAM_RAW);
applying your modification, now it returns "Connection is OK"