Hi Alex, you might want to see: http://moodle.org/course/view.php?id=32
Martin Dougiamas
Posts made by Martin Dougiamas
Shrug, lines of code doesn't mean that much, but this is a different graph of the same thing:
http://www.ohloh.net/p/compare?project_0=Moodle+(contrib)&project_1=moodle+(lang)&project_2=dokeos&submit=Go
http://www.ohloh.net/p/compare?project_0=Moodle+(contrib)&project_1=moodle+(lang)&project_2=dokeos&submit=Go
I don't think it's PHP5 ... moodle.org uses PHP5, for example.
Perhaps the services you are trying have some sort of spam control?
Try turning on all the debugging under Admin > Server > Debugging (especially debugsmtp) and then run cron.php from the command line ... you might see some useful feedback from Moodle about the error.
Perhaps the services you are trying have some sort of spam control?
Try turning on all the debugging under Admin > Server > Debugging (especially debugsmtp) and then run cron.php from the command line ... you might see some useful feedback from Moodle about the error.
I spent days nutting out times in Moodle originally and even then PJ rewrote a lot of it - they are a real headache to think about!
Most of the timestamps in Moodle are generated using time() which yes, is GMT. (ie the number of seconds since 1/1/1970 0:00 in England).
You'd use mktime() if you were generating a GMT timestamp from some arbitrary date/time (eg in the future) expressed in your local time zone.
Most of the timestamps in Moodle are generated using time() which yes, is GMT. (ie the number of seconds since 1/1/1970 0:00 in England).
You'd use mktime() if you were generating a GMT timestamp from some arbitrary date/time (eg in the future) expressed in your local time zone.
This is already implemented in Moodle 2.0 MDL-16910