Aportación realizada por Martin Dougiamas

Imagen de Core developers Imagen de Documentation writers Imagen de Moodle HQ Imagen de Plugin developers Imagen de Testers
Sure, I was going to put it in core anyway.  Basically it's the patch below, plus this in config.php:  $CFG->hideloginpanel = true;


Index: index_form.html
===================================================================
RCS file: /cvsroot/moodle/moodle/login/index_form.html,v
retrieving revision 1.50.2.1
diff -r1.50.2.1 index_form.html
2c2
< if ($show_instructions) {
---
> if ($show_instructions and empty($CFG->hideloginpanel)) {
8a9
> <?php if (empty($CFG->hideloginpanel)) { ?>
74a76
> <?php } ?>
Imagen de Core developers Imagen de Documentation writers Imagen de Moodle HQ Imagen de Plugin developers Imagen de Testers
That's very odd, the data looks good and it should work.

Try leaving out the login command - it's already stored in the CVS/Root file so not needed.

Try forcing the version again too:

cvs -q update -dP -r MOODLE_19_STABLE

And yes, CVS *will* merge in your local changes and flag you about conflicts.
Imagen de Core developers Imagen de Documentation writers Imagen de Moodle HQ Imagen de Plugin developers Imagen de Testers
Sure, the new messaging 2.0 framework in Moodle 2.0 supports this ... someone just needs to write you an sms plugin to route user messages via some sms gateway (there is already support for Jabber and Email).

Note that each SMS costs money so you might want to be careful with this sort of thing (students could really rack up your costs).