--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">\r
+<HTML>\r
+<HEAD>\r
+ <TITLE>Moodle Docs: Background</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+<BODY BGCOLOR="#ffffff">\r
+ \r
+<H2>Background</H2>\r
+ \r
+<P>Moodle is an active and evolving work in progress.</P>\r
+<P>I've been working on it, in some way or other, for several years. It started \r
+ in the 90's when I was webmaster at <a target=_top href="http://www.curtin.edu.au/">Curtin University \r
+ of Technology</a> and a system administrator of their WebCT installation. I \r
+ encountered many frustrations with the WebCT beast and developed an itch that \r
+ needed scratching - there had to be a better way (no, not Blackboard :-)</P>\r
+<P>I also know a lot of people in schools and smaller institutions (and some big \r
+ ones!) who want to make better use of the Internet but don't know where to start \r
+ in the maze of technologies and pedagogies that are out there. I've always hoped \r
+ there would be a Free alternative that such people could use to help them move \r
+ their teaching skills into the online environment.</P>\r
+<P>My strong beliefs in the unrealised possibilities of Internet-based education \r
+ led me to complete a Masters and then a PhD in Education, combining my former \r
+ career in Computer Science with newly constructed knowledge about the nature \r
+ of learning and collaboration.</P>\r
+<P>Since then Moodle has progressed through several very different prototypes \r
+ until the release of version 1.0 upon a largely unsuspecting world on \r
+ August 20, 2002 and a steady series of improved releases since then.\r
+<P>I've been using it in several courses and find it an \r
+ extremely usable and reliable tool for building high-quality online courses \r
+ - others are reporting the same. Given the context in which it's been designed, \r
+ it works particularly well for smaller institutions, or for smaller, more intimate \r
+ classes.</P>\r
+<P>When compared to the big commercial tools such as WebCT or Blackboard I think \r
+ it still falls short in some areas (such as scalability and standards support), \r
+ but it comes out ahead in many others (see <a href="index.php?file=features.html">Features</a>). \r
+</P>\r
+<P> </P>\r
+\r
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>\r
+\r
+</BODY>\r
+</HTML>\r
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">\r
+<HTML>\r
+<HEAD>\r
+ <TITLE>Moodle Docs: Credits</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+ <BODY BGCOLOR="#ffffff">\r
+ \r
+<H2>Credits</H2>\r
+ \r
+<P><B>Moodle </B>itself is Copyright © 2001-2002, <A TARGET=_top HREF="http://dougiamas.com/"> \r
+ Martin Dougiamas</A>. It is distributed under the <A HREF="licence.html"> \r
+ GNU Public License</A>.</P>\r
+\r
+\r
+ \r
+<H3><BR>Special thanks</H3>\r
+<UL>\r
+ <B><A TARGET=_top HREF="http://pctaylor.com">Dr Peter C. Taylor</A></B>, \r
+ at Curtin University of Technology in Perth, Australia, for working \r
+ with the earliest prototypes and making many useful suggestions along the way</LI>\r
+</UL>\r
+\r
+\r
+\r
+<H3><BR>Translations</H3>\r
+<BLOCKQUOTE> \r
+<P>Many thanks to these people - each translation takes many hours of work, as there are nearly \r
+ 900 phrases to translate (plus all the help files!). \r
+ These are listed in the order they joined the project:\r
+<UL>\r
+ <LI><B>en - English</B>, by Martin Dougiamas\r
+ <LI><B>fr - French</B>, by Sébastien Namèche, seb@gaia.anet.fr, <A HREF="http://gaia.anet.fr/">http://gaia.anet.fr/</A>\r
+ <LI><B>fi - Finnish</B>, by Petri Asikainen (paca@sci.fi), Jaana Tolvanen (jaanat@cedunet.com)\r
+ <LI><B>it - Italian</B>, by Davide Suraci, icarused@tiscalinet.it\r
+ <LI><B>pt_br - Portuguese (Brazil)</B>, by Fabricio Valadares, webdesigner@unincor.br\r
+ <LI><B>de - German</B>, by Holger Schadeck, Holger.Schadeck@webdesign-forum.de\r
+ <LI><B>es_mx - Spanish (Mexico)</B>, by Claudio Tavares, <A HREF="http://enlaceacademico.com">enlaceacademico.com</A>\r
+ <LI><B>es_es - Spanish </B>, by Antonio J. Navarro Vergara, anavarro@sextaisla.com, <A HREF="http://www.sextaisla.com">www.sextaisla.com</A>\r
+ <LI><B>ca - Catalan</B>, by Carles Bellver with the help of Mercè Renau, \r
+ Clara Andrés and Jordi Adell, cent@uji.es, <A HREF="http://cent.uji.es">Centre d'Educació i Noves Tecnologies</A>\r
+ <LI><B>no - Norwegian</B>, by Jøran Sørbø, joran.sorbo@teleweb.no\r
+ <LI><B>id - Indonesian</B>, by Arfan Hidayat, ivanh@telkom.net, <A HREF="http://www.kursusmaya.com">http://www.kursusmaya.com</A>\r
+ <LI><B>ja - Japanese</B>, by Mitsuhiro Yoshida, mits@mitstek.com, <A HREF="http://mitstek.com">http://mitstek.com</A>\r
+ <LI><B>tr - Turkish</B>, by M. Cüneyt Birkök, cuneyt@birkok.net, <A HREF="http://birkok.net">http://birkok.net</A>\r
+ <LI><B>zh_cn - Chinese</B>, by Zhang Dexuan, cncoolbit@hotmail.com\r
+ <LI><B>ar - Arabic</B>, by Ahmed Nabil, ana@harf.com\r
+ <LI><B>sv - Swedish</B>, by Set Lonnert, set@setlonnert.com, <A HREF="http://setlonnert.com">http://setlonnert.com</A>\r
+ <LI><B>th - Thai</B>, by Wim Singhanart, minkowski@ntlworld.com, <A HREF="http://www.suthira.net">www.suthira.net</A>\r
+ <LI><B>nl - Dutch</B>, by Hans Zwart (hans@hansdezwart.info) and Jacob Romeyn (jromeyn@thekingsschool.net)\r
+ <LI><B>es_ar - Spanish (Argentina)</B>, by Rodrigo Vigil (rmvigil@frre.utn.edu.ar)\r
+\r
+</UL>\r
+</BLOCKQUOTE> \r
+\r
+<H3><BR>Themes</H3>\r
+<BLOCKQUOTE> \r
+<P>Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle distribution, along with their authors:\r
+<UL>\r
+ <LI><B>standard* and cordoroyblue</B>, by Martin Dougiamas\r
+ <LI><B>oceanblue</B>, by Mitsuhiro Yoshida, <A HREF="http://mitstek.com">http://mitstek.com</A>\r
+ <LI><B>brightretro</B>, by Thomas Murdock, <A HREF="http://sand-paper.org/">http://sand-paper.org</A>\r
+ <LI><B>garden</B>, by Spiggy, <A HREF="http://phpgirl.com">http://phpgirl.com</A>\r
+</UL>\r
+</BLOCKQUOTE> \r
+\r
+\r
+<H3><BR>Other contributors</H3>\r
+<BLOCKQUOTE> \r
+<P>Thanks to all of you who have\r
+<UL>\r
+ <LI>donated via the <A TARGET=_top HREF="http://moodle.com/donations">Donations page</A>,\r
+ <LI>contributed to the <A TARGET=_top HREF="http://bugs.moodle.com">bug tracker</A>, and\r
+ <LI>participated in the "<A TARGET=_top HREF="http://moodle.com/course/">Using Moodle</A>" course at moodle.com</A>\r
+</UL>\r
+</P>\r
+\r
+<P>Especially, thanks to those of you who have at some time contributed \r
+ with long constructive discussions and especially code. This list is long \r
+ and always changing, but some names include (in the order I added them):\r
+ <UL> \r
+ Art Lader, \r
+ Matt Hope, \r
+ Tom Murdock, \r
+ Sébastien Namèche,\r
+ Petri Asikainen, \r
+ James Miller, \r
+ Dustin Rue, \r
+ Holger Schadeck, \r
+ Giovanni Tummarello, \r
+ John Windmueller, \r
+ Sean Keogh,\r
+ Mitsuhiro Yoshida,\r
+ Mark Kimes, \r
+ Greg Barnett, \r
+ Mary Hunter\r
+ </UL>\r
+</P>\r
+\r
+<P>I apologise if for some reason your name is not on this list - it's very\r
+ difficult to maintain! Mail me and demand to be on it. :-)\r
+</P>\r
+\r
+</BLOCKQUOTE> \r
+\r
+ \r
+<H3><BR>Moodle libraries</H3>\r
+ \r
+<BLOCKQUOTE> \r
+ <P>Some of Moodle's libraries were written by other people, and are being \r
+redistributed as part of Moodle under the LGPL. My thanks go out to the \r
+authors of all these excellent products - without them Moodle would be missing \r
+important functionality. Copyright information for each package is included below:</P>\r
+ \r
+ <P><B>ADOdb </B>- lib/adodb<BR>\r
+ </P>\r
+ \r
+ <BLOCKQUOTE> \r
+ <P>Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle,\r
+Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.</P>\r
+ \r
+ <P>Version: 2.00 14 May 2002 <BR>\r
+ Copyright © 2000, 2001 John Lim (jlim@natsoft.com.my)<BR>\r
+ License: Dual LGPL and BSD-style<BR>\r
+ URL: <A HREF="http://php.weblogs.com/adodb" TARGET="newpage">http://php.weblogs.com/adodb</A><BR>\r
+ </P>\r
+ </BLOCKQUOTE>\r
+ \r
+ <P><B>Graph Class</B> - lib/graphlib.php </P>\r
+ \r
+ <BLOCKQUOTE> \r
+ <P>Class to draw line, point, bar, and area graphs, including numeric\r
+ x-axis and double y-axis.</P>\r
+ \r
+ <P> Version: 1.6.3 (with modifications)<BR>\r
+ Copyright © 2000 Herman Veluwenkamp, hermanV@mindless.com<BR>\r
+ License: LGPL<BR>\r
+ </P>\r
+ </BLOCKQUOTE>\r
+\r
+\r
+ <P><B>IP-Atlas</B> - lib/ipatlas</P>\r
+ \r
+ <BLOCKQUOTE>PHP scripts to show the location of an IP address on a map.<BR>\r
+ <BR>\r
+ Version: 1.0 (with modifications)<BR>\r
+ Copyright © 2002 Ivan Kozik<BR>\r
+ License: GNU GPL<BR>\r
+ URL: <A HREF="http://www.xpenguin.com/ip-atlas.php" TARGET="newpage">http://www.xpenguin.com/ip-atlas.php</A><BR>\r
+ </BLOCKQUOTE>\r
+ \r
+ \r
+ <P><B>PHP mailer</B> - lib/class.phpmailer.php<BR>\r
+ </P>\r
+ \r
+ <BLOCKQUOTE>Class for sending email using either sendmail, PHP mail(), \r
+or SMTP. Methods are based upon the standard AspEmail(tm) classes.<BR>\r
+ <BR>\r
+ Version 1.60, Created 03/30/2002<BR>\r
+ Copyright © 2001 Brent R. Matzelle <bmatzelle@yahoo.com><BR>\r
+ License: LGPL<BR>\r
+ URL: <A HREF="http://phpmailer.sourceforge.net" TARGET="newpage">http://phpmailer.sourceforge.net</A><BR>\r
+ <BR>\r
+ </BLOCKQUOTE>\r
+\r
+\r
+\r
+ <P><B>PHP Simple Excel File Generator</B> - lib/psxlsgen.php</P>\r
+ \r
+ <BLOCKQUOTE>Class to generate very simple MS Excel files (xls)\r
+via PHP.<BR>\r
+ <BR>\r
+ Version: 0.3b<BR>\r
+ Copyright © 2001 Erol Ozcan <eozcan@superonline.com><BR>\r
+ License: GNU LGPL<BR>\r
+ URL: <A HREF="http://psxlsgen.sourceforge.net" TARGET="newpage">http://psxlsgen.sourceforge.net</A><BR>\r
+ </BLOCKQUOTE>\r
+\r
+\r
+\r
+\r
+\r
+ <P><B>Richtext Editor</B> - lib/rte</P>\r
+ \r
+ <BLOCKQUOTE>HTML text editor for embedding in web pages.<BR>\r
+ <BR>\r
+ Version: 0.30 beta 1 (plus modifications)<BR>\r
+ Copyright © 2001 Ramesys (Contracting Services) Limited <Austin.France@Ramesys.com>\r
+ License: GNU LGPL<BR>\r
+ URL: <A HREF="http://richtext.sourceforge.net" TARGET="newpage">http://richtext.sourceforge.net</A><BR>\r
+ </BLOCKQUOTE>\r
+ \r
+ \r
+ <P><B>SMTP class </B>- lib/class.smtp.php<BR>\r
+ </P>\r
+ \r
+ <BLOCKQUOTE>Class that can be used to connect and communicate with\r
+ any SMTP server. <BR>\r
+ It implements all the SMTP functions defined in RFC821 except TURN.<BR>\r
+ <BR>\r
+ Version: 03/26/2001 <BR>\r
+ Copyright © 2001 Chris Ryan <chris@greatbridge.com><BR>\r
+ <BR>\r
+ </BLOCKQUOTE>\r
+ \r
+ \r
+ <BLOCKQUOTE><BR>\r
+ </BLOCKQUOTE>\r
+ \r
+ <P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+ <P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>\r
+\r
+ \r
+ </BODY>\r
+ </HTML>\r
--- /dev/null
+<html>\r
+<head>\r
+<title>Moodle Docs: How to use CVS</title>\r
+<link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
+</head>\r
+<body bgcolor="#ffffff">\r
+<h2>Using CVS to access and update Moodle source code</h2>\r
+<blockquote> \r
+ <p>CVS is the Concurrent Versioning System. It's a commonly used way of storing \r
+ source code because it keeps versions of all files so that nothing is ever \r
+ lost, and usage by different people is tracked. It also provides ways to merge \r
+ code if two or more people are working on the same file. All code and all \r
+ versions are stored on a central server (in this case, at <a href="http://www.sf.net/">Sourceforge</a>). \r
+ </p>\r
+ <p>To use <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/">Moodle's \r
+ CVS archive</a> (as a <a href="http://sourceforge.net/project/memberlist.php?group_id=30935">developer \r
+ with write access</a>), you first need to have an <a href="http://sourceforge.net/account/register.php">account \r
+ on Sourceforge</a>. For the examples on this page, let's assume your username \r
+ is <strong><font color="#990000">myusername</font></strong> and your password \r
+ is <strong><font color="#990000">mypassword</font></strong>. Once you have \r
+ a Sourceforge account, contact me (<a \r
+ href="http://dougiamas.com/">Martin Dougiamas</a>) so I can give you write access \r
+ to particular directories.</p>\r
+ <p>To avoid being prompted for <strong><font color="#990000">mypassword</font></strong> \r
+ every time you run a CVS command, follow the <a href="http://sourceforge.net/account/editsshkeys.php">Sourceforge \r
+ directions for using authorized keys</a>. This step is optional, but it can \r
+ make your CVS experience a lot nicer.</p>\r
+ <p>With that done, you should have all the permissions you need, so you just \r
+ need to set up your machine and download the current sources so you can start \r
+ working on them. Below are instructions for Unix and Windows systems.</p>\r
+ <h3>1. Using CVS on Unix</h3>\r
+ <blockquote> \r
+ <p>Sourceforge CVS uses ssh as a transport layer for security, so you will \r
+ have to set this CVS_RSH environment variable in your Unix shell:</p>\r
+ <blockquote> \r
+ <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>\r
+ <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>\r
+ </blockquote>\r
+ <p>It's best to put this in your .bashrc or .cshrc so you don't have to type \r
+ it all the time. Then, check out Moodle using this (all one line): </p>\r
+ <blockquote> \r
+ <pre><strong>cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>\r
+ </blockquote>\r
+ <p>Don't try to do run this first CVS command into an existing moodle directory \r
+ - start fresh with a new directory.</p>\r
+ <p>Note that you will be prompted for <strong><font color="#990000">mypassword</font></strong> \r
+ for each command unless you set up <a href="http://sourceforge.net/account/editsshkeys.php">authorized \r
+ keys</a></p>\r
+ <p>Now, you should have a new 'moodle' directory. You can rename it and move \r
+ it around if you like. Go into it: </p>\r
+ <blockquote> \r
+ <pre><strong>cd moodle </strong></pre>\r
+ </blockquote>\r
+ <p>All the latest Moodle files should be in there. You can now change files \r
+ in your copy. To compare your files against the main CVS copy on the server \r
+ use cvs diff, eg: </p>\r
+ <blockquote> \r
+ <pre><strong>cvs diff -c config-dist.php\r
+cvs diff -c lang</strong></pre>\r
+ </blockquote>\r
+ <p>To fetch the latest updates from the server use: </p>\r
+ <blockquote> \r
+ <pre><strong>cvs update -dP</strong> </pre>\r
+ </blockquote>\r
+ <p>To copy your new files back to the server you would do something like: \r
+ </p>\r
+ <blockquote> \r
+ <pre><strong>cd lang/ca \r
+cvs commit</strong> </pre>\r
+ </blockquote>\r
+ <p>You will be prompted to add some comments (depends on your default text \r
+ editor) ... add a meangingful comment and close the editor ... the files \r
+ will be sent to Sourceforge and stored. Done! </p>\r
+ <p>To save more time you can put default arguments into a file called .cvsrc \r
+ in your home directory. For example, mine contains: </p>\r
+ <blockquote> \r
+ <pre><strong>diff -c \r
+update -dP</strong> </pre>\r
+ </blockquote>\r
+ <p>Try 'cvs help' for more details ... </p>\r
+ <p> </p>\r
+ </blockquote>\r
+ <h3>2. Using CVS on Windows</h3>\r
+ <blockquote> \r
+ <p>These instructions are based on notes provided by Mitsuhiro Yoshida <mits@mitstek.com>.</p>\r
+ <p>Firstly, download and install WinCVS.</p>\r
+ <blockquote> \r
+ <p><a href="https://sourceforge.net/project/showfiles.php?group_id=10072">https://sourceforge.net/project/showfiles.php?group_id=10072</a></p>\r
+ </blockquote>\r
+ <p>Secondly, download sfsetup for SourceForge ssh access, install it and reboot \r
+ Windows.</p>\r
+ <blockquote> \r
+ <p><a href="http://sourceforge.net/projects/sfsetup/">http://sourceforge.net/projects/sfsetup/</a></p>\r
+ </blockquote>\r
+ <p>Next, configure WinCVS. Launch it, and select Admin -> Preferences. \r
+ Then change them as follows:</p>\r
+ <blockquote> \r
+ <p> [General]<br>\r
+ <strong>CVSROOT data</strong>:<br>\r
+ <strong>Authentication</strong>: ssh<br>\r
+ <strong>Path</strong>: /cvsroot/moodle<br>\r
+ <strong>Host address</strong>: cvs.moodle.sourceforge.net<br>\r
+ <strong>User name</strong>: <font color="#990000">myusername</font><br>\r
+ <strong>CVSROOT</strong>: <font color="#990000">myusername</font>@cvs.moodle.sourceforge.net:/cvsroot/moodle</p>\r
+ <p>[Globals]<br>\r
+ <strong>Checkout read-only</strong>: uncheck<br>\r
+ <strong>Supply control when adding files</strong>: check<br>\r
+ <strong>Quiet mode</strong>: uncheck<br>\r
+ <strong>TCP/IP compression</strong>: check and select 9<br>\r
+ <strong>Dirty files support</strong>: check<br>\r
+ <strong>Prune(remove) empty directories</strong>: check<br>\r
+ <strong>Disable splash screen</strong>: uncheck</p>\r
+ </blockquote>\r
+ <p>Congratulations, WinCVS is set up. Now, you should check out a complete \r
+ working copy of the Moodle course code:</p>\r
+ <ol>\r
+ <li>Select 'Create -> checkout'</li>\r
+ <li>For the setting 'Module name and path on the server", type "moodle", \r
+ then click OK.</li>\r
+ <li>Type in <strong><font color="#990000">mypassword</font></strong> and \r
+ press Enter in the DOS window.</li>\r
+ </ol>\r
+ <p>After this first checkout, you can fetch updated files from the CVS server \r
+ like this:</p>\r
+ <ol>\r
+ <li> Select folders or files you want to update</li>\r
+ <li>Press right mouse button and select '<strong>Update selection</strong>'</li>\r
+ <li>Press OK button</li>\r
+ <li>Type in <strong><font color="#990000">mypassword</font></strong> and \r
+ press Enter in the DOS window.</li>\r
+ </ol>\r
+ <p>After modifying files, you can commit them back to the CVS server like \r
+ this:</p>\r
+ <ol>\r
+ <li>Select folders or files you want to commit</li>\r
+ <li>Press right button and select '<strong>Commit selection</strong>'</li>\r
+ <li>Press OK button</li>\r
+ <li>Type in a meaningful comment and press OK button.</li>\r
+ <li>Type in <strong><font color="#990000">mypassword</font></strong> and \r
+ press Enter in the DOS window.</li>\r
+ </ol>\r
+ </blockquote>\r
+ <p> </p>\r
+ <p align="center">Good luck!</p>\r
+ <p> </p>\r
+</blockquote>\r
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>\r
+<p align="CENTER"><font size="1">Version: $Id: features.html,v 1.2 2001/12/09 \r
+ 10:34:19 martin Exp $</font></p>\r
+</body>\r
+</html>\r
--- /dev/null
+<head>\r
+ <title>Moodle Docs: Developers Manual</title>\r
+ <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
+</head>\r
+\r
+<body bgcolor="#FFFFFF">\r
+<h2>Developers Manual</h2>\r
+<p>This document describes some of Moodle's design and how you can contribute.</p>\r
+<p>Sections in this document:</p>\r
+<ol>\r
+ <li><a href="#architecture">Moodle architecture</a></li>\r
+ <li><a href="#contribute">How you can contribute</a> \r
+ <ul>\r
+ <li><a href="#activities">Learning activities</a></li>\r
+ <li><a href="#themes">Themes</a></li>\r
+ <li><a href="#languages">Languages</a></li>\r
+ <li><a href="#database">Database Schemas</a></li>\r
+ <li><a href="#courseformats">Course formats</a></li>\r
+ <li><a href="#doc">Documentation and articles</a></li>\r
+ <li><a href="#bugs">Participating in the bug tracker</a></li>\r
+ </ul>\r
+ </li>\r
+</ol>\r
+<p> </p>\r
+<h3><a name="architecture"></a>1. Moodle architecture</h3>\r
+<p>From a system administrator's perspective, Moodle has been designed according \r
+ to the following criteria:</p>\r
+<ol>\r
+ <li><strong>Moodle should run on the widest variety of platforms</strong><br>\r
+ <br>\r
+ The web application platform that runs on most platforms is PHP combined with \r
+ MySQL, and this is the environment that Moodle has been developed in (on Linux, \r
+ Windows, and Mac OS X). Moodle also uses the ADOdb library for database abstraction, \r
+ which means Moodle can use <a href="http://php.weblogs.com/ADOdb_manual#drivers">more \r
+ than ten different brands of database</a> (unfortunately, though, it can not \r
+ yet <em><strong>set up tables</strong></em> in all these databases - more \r
+ on this later). <br><br>\r
+ </li>\r
+ <li><strong>Moodle should be easy to install, learn and modify</strong><br>\r
+ <br>\r
+ Early prototypes of Moodle (1999) were built using <a target=_top href="http://www.zope.org/">Zope</a> \r
+ - an advanced object-oriented web application server. Unfortunately I found \r
+ that although the technology was pretty cool, it had a very steep learning \r
+ curve and was not very flexible in terms of system administration. The PHP \r
+ scripting language, on the other hand, is very easy to get into (especially \r
+ if you've done any programming using any other scripting language). Early \r
+ on I made the decision to avoid using a class-oriented design - again, to \r
+ keep it simple to understand for novices. Code reuse is instead achieved by \r
+ libraries of clearly-named functions and consistent layout of script files. \r
+ PHP is also easy to install (binaries are available for every platform) and \r
+ is widely available to the point that most web hosting services provide it \r
+ as standard.<br><br>\r
+ </li>\r
+ <li><strong>It should be easy to upgrade from one version to the next</strong><br>\r
+ <br>\r
+ Moodle knows what version it is (as well as the versions of all plug-in modules) \r
+ and a mechanism has been built-in so that Moodle can properly upgrade itself \r
+ to new versions (for example it can rename database tables or add new fields). \r
+ If using CVS in Unix for example, one can just do a "cvs update -d" \r
+ and then visit the site home page to complete an upgrade.<br><br>\r
+ </li>\r
+ <li><strong>It should be modular to allow for growth</strong><br>\r
+ <br>\r
+ Moodle has a number of features that are modular, including themes, activities, \r
+ interface languages, database schemas and course formats. This allows anyone \r
+ to add features to the main codebase or to even distribute them separately. \r
+ More on this below in the next section.<br><br>\r
+ </li>\r
+ <li><strong>It should be able to be used in conjunction with other systems</strong><br>\r
+ <br>\r
+ One thing Moodle does is keep all files for one course within a single, normal \r
+ directory on the server. This would allow a system administrator to provide \r
+ seamless forms of file-level access for each teacher, such as Appletalk, SMB, \r
+ NFS, FTP, WebDAV and so on. The authentication modules allow Moodle to use \r
+ LDAP, IMAP, POP3, NNTP and other databases as sources for user information.\r
+ Otherwise, there is work yet to do. Features planned \r
+ for Moodle in future versions include: import and export of Moodle data using XML-based \r
+ formats (including IMS and SCORM); and increased use of style sheets for \r
+ interface formatting (so that it can be integrated visually into other web sites).</li>\r
+</ol>\r
+<p> </p>\r
+<h3><a name="contribute" id="contribute"></a>2. How you can contribute</h3>\r
+<p>As mentioned above, Moodle has a number of features that are modular. Even \r
+ if you are not a programmer there are things you can change or help with.</p>\r
+<p><strong><a name="activities" id="activities"></a>Learning Activities</strong></p>\r
+<blockquote> \r
+ <p>These are by far the most important modules, and reside in the 'mod' directory. \r
+ There are seven default modules: assignment, choice, forum, journal, quiz, \r
+ resource, and survey. Each module is in a separate subdirectory and consists \r
+ of the following mandatory elements (plus extra scripts unique to each module):</p>\r
+ <ul>\r
+ <li>mod.html: a form to set up or update an instance of this module</li>\r
+ <li>version.php: defines some meta-info and provides upgrading code</li>\r
+ <li>icon.gif: a 16x16 icon for the module</li>\r
+ <li>db/: SQL dumps of all the required db tables and data (for each database \r
+ type) </li>\r
+ <li>index.php: a page to list all instances in a course</li>\r
+ <li>view.php: a page to view a particular instance</li>\r
+ <li>lib.php: any/all functions defined by the module should be in here. If \r
+ the modulename if called widget, then the required functions include: \r
+ <ul>\r
+ <li>widget_add_instance() - code to add a new instance of widget</li>\r
+ <li>widget_update_instance() - code to update an existing instance</li>\r
+ <li>widget_delete_instance() - code to delete an instance</li>\r
+ <li>widget_user_outline() - given an instance, return a summary of a user's \r
+ contribution</li>\r
+ <li>widget_user_complete() - given an instance, print details of a user's \r
+ contribution<br>\r
+ </li>\r
+ <li>To avoid possible conflict, any module functions should be named starting \r
+ with widget_ and any constants you define should start with WIDGET_ \r
+ </li>\r
+ </ul>\r
+ </li>\r
+ <li>Lastly, each module will have some language files that contain strings \r
+ for that module. See below.</li>\r
+ </ul>\r
+ <p>The easiest way to start a new learning activity module is to use the template \r
+ in <strong><a href="http://moodle.com/mod/newmodule_template.zip">mod/newmodule_template.zip</a>.</strong> \r
+ Unzip it and follow the README inside. </p>\r
+ <p>You might also like to post first in the <a href="http://moodle.com/mod/forum/view.php?id=44" target="_top">Activities \r
+ modules forum on Using Moodle</a>.</p>\r
+ <p> </p>\r
+</blockquote>\r
+<p> <strong><a name="themes" id="themes"></a>Themes</strong></p>\r
+<blockquote> \r
+ <p>Themes (or skins) define the look of a site. A number of simple themes are \r
+ provided in the main distribution, but you may want to create your own theme\r
+ with your own colours, logo, styles and graphics.\r
+\r
+ <p>Each theme is in a subdirectory of the "theme" directory, and contains \r
+ at least the following files:</p>\r
+ <ul>\r
+ <li><strong>config.php</strong>: defines the theme colours used throughout \r
+ the site</li>\r
+ <li><strong>styles.php</strong>: the style sheet, containing CSS definitions \r
+ for standard HTML elements as well as many Moodle elements.</li>\r
+ <li><strong>header.html</strong>: Included at the top of each page. This is \r
+ what you need to edit to add a logo at the top of pages, for example.</li>\r
+ <li><strong>footer.html</strong>: Included at the bottom of each page.</li>\r
+ </ul>\r
+ <p>To create your own themes for current versions of Moodle:</p>\r
+ <ol>\r
+ <li>Copy one of the existing theme folders to one with a new name. I recommend\r
+ starting with one of the standard themes.\r
+ <li>Edit config.php and insert your own colours.\r
+ <li>Edit styles.php and change your CSS styles.\r
+ <li>Edit header.html and footer.html to add new logos, or change the layout.\r
+ </ol>\r
+ <p>Note that all these steps are optional - you can make a radically different\r
+ look to your site simply by editing the colours in config.php</p>\r
+ <p>Note also that Moodle upgrades <em>may</em> break themes slightly, so check the \r
+ release notes carefully if you are using a custom theme.</p>\r
+ <p>In particular, Moodle 2.0 will have a completely new display system, probably based on\r
+ XSL transformations of XML output from Moodle. It is likely that the \r
+ themes for this will be a completely different format, but the advantage will \r
+ be a much higher possible degree of customisation (including moving elements \r
+ around the page).</p>\r
+ <p>More discussion about this in the <a target=_top href="http://moodle.com/mod/forum/view.php?id=46">Themes \r
+ forum on Using Moodle</a>. If you create a nice theme that you think others\r
+ might want to use, please post your zip file on the themes forum!<br>\r
+ </p>\r
+</blockquote>\r
+\r
+ <p> </p>\r
+\r
+<p><strong><a name="languages" id="languages"></a>Languages</strong></p>\r
+<blockquote> \r
+ <p>Moodle has been designed for internationalisation. Each 'string' or 'page' \r
+ of text that is displayed as part of the interface is drawn from a set of \r
+ language files. Each language is a subdirectory of the directory 'lang'. The \r
+ structure of the lang directory is as follows:</p>\r
+ <p><strong>lang/en</strong> - directory containing all files for one language \r
+ (eg English)</p>\r
+ <ul>\r
+ <li>moodle.php - strings for main interface</li>\r
+ <li>assignment.php - strings for assignment module</li>\r
+ <li>choice.php - strings for choice module</li>\r
+ <li>forum.php - strings for forum module</li>\r
+ <li>journal.php - strings for journal module </li>\r
+ <li>quiz.php - strings for quiz module</li>\r
+ <li>resource.php - strings for resource module</li>\r
+ <li>survey.php - strings for survey module</li>\r
+ <li>.... plus other modules if any.<br>\r
+ <br>\r
+ A string is called from these files using the <strong><em>get_string()</em></strong><em> \r
+ </em>or<em> <strong>print_string()</strong> </em>functions. Each string \r
+ supports variable substitution, to support variable ordering in different \r
+ languages.<em><br>\r
+ <br>\r
+ </em>eg $strdueby = get_string("assignmentdueby", "assignment", \r
+ userdate($date)); <br>\r
+ <br>\r
+ If a string doesn't exist in a particular language, then the equivalent \r
+ in English will automatically be used instead.</li>\r
+ </ul>\r
+ <p><strong>lang/en/help</strong> - contains whole help pages (for popup context-sensitive \r
+ help)</p>\r
+ <blockquote> \r
+ <p>Main help pages are situated here, while help pages specific to each module \r
+ are located in subdirectories with the module's name.</p>\r
+ <p>You can insert a helpbutton in a page with the helpbutton function.</p>\r
+ <p>eg helpbutton("text", "Click here for help about text");</p>\r
+ <p>and for modules:</p>\r
+ <p>helpbutton("forumtypes", "Forum types", "forum");</p>\r
+ </blockquote>\r
+ <p>Note that you can edit languages online, using the administration web tools \r
+ under "Check this language". This makes it easy to not to only create \r
+ new languages but to refine existing ones. If you are starting a new language, \r
+ please contact me, <a target=_top href="http://dougiamas.com/">Martin Dougiamas</a>. </p>\r
+ <p>You might also like to post in the <a target=_top href="http://moodle.com/mod/forum/view.php?id=43" target="_top">Languages \r
+ forum on Using Moodle</a>. </p>\r
+ <p>If you are maintaining a language an ongoing basis, I can give you <a href="?file=cvs.html">CVS \r
+ write access to the Moodle source code</a> so that you can directly maintain \r
+ the files.</p>\r
+</blockquote>\r
+<p><br>\r
+ <strong><a name="database" id="database"></a>Database Schemas</strong></p>\r
+<blockquote> \r
+ <p>Given a working database with defined tables, the intentionally simple SQL \r
+ used in Moodle should work fine with a wide variety of database brands.</p>\r
+\r
+ <p>A problem exists with <strong>automatically creating</strong> new tables \r
+ in a database, which is what Moodle tries to do upon initial installation. \r
+ Because every database is very different, there doesn't yet exist any way \r
+ to do this in a platform-independent way. To support this automation in each \r
+ database, schemas can be created that list the required SQL to create Moodle \r
+ tables in a particular database. These are files in <strong>lib/db</strong> \r
+ and inside the <strong>db</strong> subdirectory of each module.</p>\r
+\r
+ <p>Currently, only MySQL and PostgreSQL are fully supported in this way. If you are \r
+ familiar with another database (especially open source databases) and are \r
+ willing to help port the existing schema, please get in contact with me (<a target=_top href="http://dougiamas.com/">Martin \r
+ Dougiamas</a>).</p>\r
+</blockquote>\r
+<p> </p>\r
+<p><strong><a name="courseformats" id="courseformats"></a>Course Formats</strong></p>\r
+<blockquote> \r
+ <p>Moodle currently supports three different course formats: weekly, topics and social. \r
+ </p>\r
+ <p>These are a little more connected to the rest of the code (and hence, less \r
+ "pluggable") but it is still quite easy to add new ones.</p>\r
+ <p>If you have any ideas for different formats that you need or would like to \r
+ see, get in touch with me and I'll do my absolute best to have them available \r
+ in future releases.</p>\r
+</blockquote>\r
+<p> </p>\r
+<p><strong><a name="doc" id="doc"></a>Documentation and articles</strong></p>\r
+<blockquote> \r
+ <p>If you feel like writing a tutorial, an article, an academic paper or anything \r
+ else about Moodle, please do! </p>\r
+ <p>Put it on the web and make sure you include links to <a target=_top href="http://moodle.com/">http://moodle.com/</a></p>\r
+ </blockquote>\r
+<p> </p>\r
+<p><strong><a name="bugs" id="bugs"></a>Participating in the bug tracker</strong></p>\r
+<blockquote> \r
+ <p>Finally, I would like to invite you to register on the "bug tracker" \r
+ at <a target=_top href="http://bugs.moodle.org">bugs.moodle.org</a> so you can file any \r
+ bugs that you find and perhaps participate in discussing and fixing them. \r
+ </p>\r
+ <p>"Bugs" not only includes software bugs with current versions of \r
+ Moodle, but also new ideas, feature requests and even constructive criticism \r
+ of existing features. The beauty of open source is that anyone can participate \r
+ in some way and help to create a better product for all of us to enjoy. In \r
+ this project, your input is very welcome!</p>\r
+</blockquote>\r
+<p> </p>\r
+<blockquote> \r
+ <blockquote> \r
+ <blockquote> \r
+ <p align="center">Thanks for using Moodle!</p>\r
+ <p align="center">Cheers,<br>\r
+ <a target=_top href="http://dougiamas.com/" target="_top">Martin Dougiamas</a></p>\r
+ </blockquote>\r
+ </blockquote>\r
+</blockquote>\r
+<p> </p>\r
+<p> </p>\r
+<blockquote> \r
+ <p> </p>\r
+</blockquote>\r
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>\r
+<p align="CENTER"><font size="1">Version: $Id: developer.html,v 1.2 2001/12/09 \r
+ 10:34:19 martin Exp $</font></p>\r
+\r
+</body>\r
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">\r
+<HTML>\r
+<HEAD>\r
+ <TITLE>Moodle Docs: Background</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+<BODY BGCOLOR="#ffffff">\r
+ \r
+<H2>Features</H2>\r
+<p>Moodle is an active and evolving product. This page lists some of the many \r
+ features it contains:</p>\r
+<p><strong>Overall design</strong></p>\r
+<UL>\r
+ <LI>Promotes a social constructionist pedagogy (collaboration, activities, critical \r
+ reflection, etc)</LI>\r
+ <LI>Suitable for 100% online classes as well as supplementing face-to-face learning \r
+ <LI>Simple, lightweight, efficient, compatible, low-tech browser interface</LI>\r
+ <LI>Easy to install on almost any platform that supports PHP. Requires only \r
+ one database.</LI>\r
+ <LI>Full database abstraction supports all major brands of database (except \r
+ for initial table definition)</LI>\r
+ <LI>Course listing shows descriptions for every course on the server, including \r
+ accessibility to guests.</LI>\r
+ <LI>Emphasis on strong security throughout. Forms are all checked, data validated, \r
+ cookies encrypted etc</LI>\r
+</UL>\r
+<p><strong>Site management</strong></p>\r
+<UL>\r
+ <LI>Site is managed by an admin user, defined during setup</LI>\r
+ <LI>Plug-in "themes" allow the admin to customise the site colours, fonts, layout \r
+ etc to suit local needs</LI>\r
+ <LI>Plug-in activity modules can be added to existing Moodle installations</LI>\r
+ <LI>Plug-in language packs allow full localisation to any language. These can \r
+ be edited using a built-in web-based editor. Currently there are language packs\r
+ for more than <A HREF="http://moodle.com/download/lang/" TARGET="_top">19 languages</A>.</LI>\r
+ <LI>The code is clearly-written PHP under a GPL license - easy to modify to \r
+ suit your needs</LI>\r
+</UL>\r
+<p><strong>User management</strong></p>\r
+<UL>\r
+ <LI>Goals are to reduce admin involvement to a minimum, while retaining high \r
+ security</LI>\r
+ <LI>Supports a range of authentication mechanisms through plug-in authentication \r
+ modules, allowing easy integration with existing systems.</LI>\r
+ <LI>Standard email method: students can create their own login accounts. Email \r
+ addresses are verified by confirmation.</LI>\r
+ <LI>LDAP method: account logins can be checked against an LDAP server. Admin \r
+ can specify which fields to use.</LI>\r
+ <LI>IMAP, POP3, NNTP: account logins are checked against a mail or news server. \r
+ SSL, certificates and TLS are supported.</LI>\r
+ <LI>External database: any database containing at least two fields can be used \r
+ as an external authentication source.</LI>\r
+ <LI>Each person requires only one account for the whole server - each account \r
+ can have different access</LI>\r
+ <LI>An admin account controls the creation of courses and creates teachers by \r
+ assigning users to courses</LI>\r
+ <LI>Security - teachers can add an "enrolment key" to their courses to keep \r
+ out non-students. They can give out this key face-to-face or via personal \r
+ email etc</LI>\r
+ <LI>Teachers can unenrol students manually if desired, otherwise they are automatically \r
+ unenrolled after a certain period of inactivity (set by the admin)</LI>\r
+ <LI>Students are encouraged to build an online profile including photos, description. \r
+ Email addresses can be protected from display if required.</LI>\r
+ <LI>Every user can specify their own timezone, and every date in Moodle is translated \r
+ to that timezone (eg posting dates, assignment due dates etc)</LI>\r
+ <LI>Every user can choose the language used for the Moodle interface (English, \r
+ French, German, Spanish, Portuguese etc)</LI>\r
+</UL>\r
+<p><strong>Course management</strong></p>\r
+<UL>\r
+ <LI>Teacher has full control over all settings for a course</LI>\r
+ <LI>Choice of course formats such as by week, by topic or a discussion-focussed \r
+ social format</LI>\r
+ <LI>Flexible array of course activities - Forums, Journals, Quizzes, Resources, \r
+ Choices, Surveys, Assignments.</LI>\r
+ <LI>Recent changes to the course since the last login can be displayed on the \r
+ course home page - helps give sense of community</LI>\r
+ <LI>Most text entry areas (resources, forum postings, journal entries etc) can \r
+ be edited using an embedded WYSIWYG HTML editor</LI>\r
+ <LI>All grades for Forums, Journals, Quizzes and Assignments can be viewed on \r
+ one page (and downloaded as a spreadsheet file)</LI>\r
+ <LI>Full user logging and tracking - activity reports for each student are available \r
+ with graphs and details about each module (last access, number of times read) \r
+ as well as a detailed "story" of each students involvement including postings, \r
+ journal entries etc on one page.</LI>\r
+ <LI>Mail integration - copies of forum posts, teacher feedback etc can be mailed \r
+ in HTML or plain text.</LI>\r
+</UL>\r
+<B>Assignment Module</B> \r
+<UL>\r
+ <LI>Assignments can be specified with a due date and a maximum grade.</LI>\r
+ <LI>Students can upload their assignments (any file format) to the server - \r
+ they are date-stamped.</LI>\r
+ <LI>Late assignments are allowed, but the amount of lateness is shown clearly \r
+ to the teacher</LI>\r
+ <LI>For each particular assignment, the whole class can be assessed (grade and \r
+ comment) on one page in one form.</LI>\r
+ <LI>Teacher feedback is appended to the assignment page for each student, and \r
+ notification is mailed out.</LI>\r
+ <LI>The teacher can choose to allow resubmission of assignments after grading \r
+ (for regrading)</LI>\r
+</UL>\r
+<P><B>Choice Module</B> </P>\r
+<UL>\r
+ <LI>Like a poll. Can either be used to vote on something, or to get feedback \r
+ from every student (eg research consent)</LI>\r
+ <LI>Teacher sees intuitive table view of who chose what</LI>\r
+</UL>\r
+<P><B>Forum Module</B> </P>\r
+<UL>\r
+ <LI>Different types of forums are available, such as teacher-only, course news, \r
+ open-to-all, and one-thread-per-user.</LI>\r
+ <LI>All postings have the authors photo attached.</LI>\r
+ <LI>Discussions can be viewed nested, flat or threaded, oldest or newest first.</LI>\r
+ <LI>Individual forums can be subscribed to by each person so that copies are \r
+ forwarded via email, or the teacher can force subscription for all</LI>\r
+ <LI>The teacher can choose not to allow replies (eg for an announcements-only \r
+ forum)</LI>\r
+</UL>\r
+<B>Journal Module</B> \r
+<UL>\r
+ <LI>Journals are private between student and teacher.</LI>\r
+ <LI>Each journal entry can be directed by an open question.</LI>\r
+ <LI>For each particular journal entry, the whole class can be assessed on one \r
+ page in one form</LI>\r
+ <LI>Teacher feedback is appended to the journal entry page, and notification \r
+ is mailed out.</LI>\r
+</UL>\r
+<P><B>Quiz Module</B> </P>\r
+<UL>\r
+ <LI>Teachers can define a database of questions for re-use in different quizzes</LI>\r
+ <LI>Quizzes are automatically graded, and can be re-graded if questions are \r
+ modified </LI>\r
+ <LI>Quizzes can have a limited time window outside of which they are not available</LI>\r
+ <LI>At the teacher's option, quizzes can be attempted multiple times, and can \r
+ show feedback and/or correct answers</LI>\r
+ <LI>Questions allow HTML and images</LI>\r
+ <LI>Multiple-choice questions supporting single or multiple answers</LI>\r
+ <LI>Short Answer questions (words or phrases)</LI>\r
+ <LI>True-False questions </LI>\r
+</UL>\r
+<P><B>Resource Module</B> </P>\r
+<UL>\r
+ <LI>Supports display of any electronic content</LI>\r
+ <LI>Files can be uploaded and managed on the server, or created on the fly using \r
+ web forms (text or HTML)</LI>\r
+ <LI>External content on the web can be linked to or seamlessly included within \r
+ the course interface.</LI>\r
+</UL>\r
+<B>Survey Module</B> \r
+<UL><LI>Built-in surveys (COLLES, ATTLS) have been proven as instruments for analysing online classes</LI><LI>Online survey reports always available, including many graphs. Data is downloadable as an Excel spreadsheet or CSV text file.</LI><LI>Survey interface prevents partly-finished surveys.</LI><LI>Feedback is provided to the student of their results compared to the class averages</UL>\r
+\r
+<P> </P>\r
+\r
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id: features.html,v 1.2 2001/12/09 \r
+ 10:34:19 martin Exp $</FONT></P>\r
+\r
+</BODY>\r
+</HTML>\r
--- /dev/null
+<HEAD>\r
+ <TITLE>Moodle Docs: Future</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+\r
+<BODY BGCOLOR="#FFFFFF">\r
+\r
+<H2>Future</H2>\r
+<P>I'm committed to continuing my work on Moodle and on keeping it Open and Free. \r
+ I have a deeply-held belief in the importance of unrestricted education and \r
+ empowered teaching, and Moodle is the main way I can contribute to the realisation \r
+ of these ideals. \r
+\r
+<P>As Moodle gains in maturity, I hope its directions are influenced by the community \r
+ of developers and users. A dynamic database of proposed features and their status \r
+ can be found at <A TARGET=_top HREF="http://bugs.moodle.org/">bugs.moodle.org</A>. \r
+ Your <A href="developer.html">contributions</a> in the form of ideas, code, \r
+ feedback and promotion are all very welcome. \r
+\r
+<P>Until about April 2003, my own involvement will slow down while I finish my PhD thesis.\r
+ During this time there will still be releases, but they will only contain minor \r
+ new features and bug fixes. I will also be including modules and other code contributed \r
+ by others.\r
+\r
+<P>After this time, by around June/July 2003, I am expecting a major release called Moodle 2.0\r
+ that will include major new features such as:\r
+ <UL>\r
+ <LI>Stronger pedagogical support for both teachers and students\r
+ <LI>Support for groups and group work\r
+ <LI>Rewritten display incorporating XML, XSL and CSS for full flexibility \r
+ and compatibility with all modern web standards.\r
+ <LI>Basic support for IMS and SCORM\r
+ <LI>A variety of new modules (chat, tracker etc)\r
+ <LI>Whatever else seems most important at the time :-)\r
+ </UL>\r
+\r
+<P>About this time I will also be experimenting with ways of making \r
+ Moodle development more sustainable for the long term. This may \r
+ include offering services for payment - although the software itself \r
+ will always remain Free.\r
+ \r
+<P ALIGN="CENTER"> </P>\r
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>\r
+</BODY>\r
--- /dev/null
+<HEAD>\r
+ <TITLE>Moodle Docs: Installation</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+\r
+<BODY BGCOLOR="#FFFFFF">\r
+<H2>Installing Moodle</H2>\r
+<P>This guide explains how to install Moodle for the first time. It goes into some detail\r
+ about some of the steps, in order to cover the wide variety of small differences between\r
+ web server setups, so this document may look long and complicated. Don't be put off by this \r
+ - I usually set Moodle up in a few minutes!</P>\r
+<P>Take your time and work through this document carefully - it will save you time later on.</P>\r
+<P>Sections in this document:</P>\r
+<OL>\r
+ <LI><A HREF="#requirements">Requirements</A></LI>\r
+ <LI><A HREF="#downloading">Download</A></LI>\r
+ <LI><A HREF="#site">Site structure</A></LI>\r
+ <LI><A HREF="#data">Create a data directory</A></LI>\r
+ <LI><A HREF="#database">Create a database</A></LI>\r
+ <LI><A HREF="#webserver">Check web server settings</A></LI>\r
+ <LI><A HREF="#config">Edit config.php</A></LI>\r
+ <LI><A HREF="#admin">Go to the admin page</A></LI>\r
+ <LI><A HREF="#cron">Set up cron</A></LI>\r
+ <LI><A HREF="#course">Create a new course</A></LI>\r
+</OL>\r
+<H3><A NAME="requirements"></A>1. Requirements</H3>\r
+<blockquote>\r
+ <p>Moodle is primarily developed in Linux using PHP, Apache and MySQL, and regularly \r
+ tested with PostgreSQL and in Windows XP and Mac OS X environments.</p>\r
+ <p>All you should need are:</p>\r
+ <ol>\r
+ <li>a working installation of <A HREF="http://www.php.net/">PHP</A> (version \r
+ 4.1.0 or later), with the following features enabled (most PHP installations \r
+ these days will have all of these):\r
+ <ul>\r
+ <LI><A HREF="http://www.boutell.com/gd/">GD library</A> with support for JPG and PNG formats</li>\r
+ <LI>Sessions support</LI>\r
+ <LI>File uploading allowed</LI>\r
+ </UL>\r
+</LI>\r
+ <li>a working database server: <A HREF="http://www.mysql.com/">MySQL</A> or <A HREF="http://www.postgresql.org/">PostgreSQL</A> are recommended. (MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 or ODBC are also theoretically supported but will require you to manually set up the database tables).</li>\r
+ </ol>\r
+ <p>On a Windows platform, the quickest way to satisfy these requirements is \r
+ to download <A HREF="http://www.foxserv.net/">FoxServ</A>, \r
+ or <A HREF="http://www.easyphp.org/">EasyPHP</A> which will install Apache, \r
+ PHP, and MySQL for you. Make sure you enable the GD module so Moodle can process \r
+ images - you may have to edit php.ini and remove the comment (;) from this \r
+ line: 'extension=php_gd.dll'. You may also have to fix the directory for \r
+ session.save_path - instead of the default "/tmp" use a Windows directory \r
+ like "c:/temp".</p>\r
+\r
+ <p>On Mac OS X I highly recommend the <a href="http://fink.sourceforge.net/">fink</a> \r
+ project as a way to download easily-maintainable packages for all of this. If you are less\r
+ confident with command-line stuff then <A HREF="http://www.entropy.ch/software/macosx/php/">Marc Liyanage's PHP Apache Module</A> is the easiest way to get PHP up and running on a new Mac OS X server.</p>\r
+\r
+ <p>If you're on Linux or another Unix then I'll assume you can figure all this out for yourself! ;-) </p>\r
+\r
+</blockquote>\r
+<P> </P>\r
+<H3><A NAME="downloading"></A>2. Download</H3>\r
+<blockquote>\r
+ <p>There are two ways to get Moodle, as a compressed package and via CVS. These \r
+ are explained in detail on the download page on <A HREF="http://moodle.com/">http://moodle.com/</A></p>\r
+ <p>After downloading and unpacking the archive, or checking out the files via \r
+ CVS, you will be left with a directory called "moodle", containing \r
+ a number of files and folders. </p>\r
+ <p>You can either place the whole folder in your web server documents directory, \r
+ in which case the site will be located at <B>http://yourwebserver.com/moodle</B>, \r
+ or you can copy all the contents straight into the main web server documents \r
+ directory, in which case the site will be simply <B>http://yourwebserver.com</B>.</p>\r
+</blockquote>\r
+<P> </P>\r
+<H3><A NAME="site"></A>3. Site structure</H3>\r
+<BLOCKQUOTE>\r
+ <p>Here is a quick summary of the contents of the Moodle folder, to help get \r
+ you oriented:</p>\r
+ <blockquote>\r
+ <p>config.php - the only file you need to edit to get started<br>\r
+ version.php - defines the current version of Moodle code<BR>\r
+ index.php - the front page of the site</p>\r
+ <ul>\r
+ <li>admin/ - code to administrate the whole server </li>\r
+ <li>auth/ - plugin modules to authenticate users </li>\r
+ <li>course/ - code to display and manage courses </li>\r
+ <li>doc/ - help documentation for Moodle (eg this page)</li>\r
+ <li>files/ - code to display and manage uploaded files</li>\r
+ <li>lang/ - texts in different languages, one directory per language </li>\r
+ <li>lib/ - libraries of core Moodle code </li>\r
+ <li>login/ - code to handle login and account creation </li>\r
+ <li>mod/ - all Moodle course modules</li>\r
+ <li>pix/ - generic site graphics</li>\r
+ <li>theme/ - theme packs/skins to change the look of the site.</li>\r
+ <li>user/ - code to display and manage users</li>\r
+ </ul>\r
+ <p> </p>\r
+ </blockquote>\r
+</BLOCKQUOTE>\r
+<H3><A NAME="data"></A>4. Create a data directory</H3>\r
+<blockquote>\r
+ <p>Moodle will also need some space on your hard disk to store uploaded files, \r
+ such as course documents and user pictures.</p>\r
+\r
+ <p>Create a directory for this purpose somewhere. For security, it's best that \r
+ this directory is NOT accessible directly via the web. The easiest way to do this\r
+ is to simply locate it OUTSIDE the web directory, otherwise protect it \r
+ by creating a file in the data directory called .htaccess, containing this line:\r
+ <blockquote>\r
+ <PRE>deny from all</PRE>\r
+ </blockquote>\r
+ \r
+ <p>To make sure that Moodle can save uploaded files in this directory, check that \r
+ the web server software (eg Apache) has permission to write \r
+ to this directory. On Unix machines, this means setting the owner of the directory \r
+ to be something like "nobody" or "apache".</p>\r
+\r
+ <p>On many shared hosting servers, you will probably need to restrict all file access \r
+ to your "group" (to prevent other webhost customers from looking at or changing your files), \r
+ but provide full read/write access to everyone else (which will allow the web server\r
+ to access your files). Speak to your server administrator if you are having \r
+ trouble setting this up securely.</p>\r
+\r
+</blockquote>\r
+<P> </P>\r
+<H3><A NAME="database"></A>5. Create a database</H3>\r
+<blockquote>\r
+<p>You need to create an empty database (eg "moodle") in your database system \r
+ along with a special user (eg "moodleuser") that has access to that database \r
+ (and that database only). You could use the "root" user if you wanted to, but \r
+ this is not recommended for a production system: if hackers manage to discover\r
+ the password then your whole database system would be at risk, rather than \r
+ just one database.\r
+</p>\r
+ <p>Example command lines for MySQL: </p>\r
+ <PRE>\r
+ # mysql -u root -p\r
+ > CREATE DATABASE moodle; \r
+ > GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.* \r
+ TO moodleuser@localhost IDENTIFIED BY 'yourpassword'; \r
+ > quit \r
+ # mysqladmin -p reload\r
+</PRE>\r
+ <p>Example command lines for PostgreSQL: </p>\r
+ <PRE>\r
+ # su - postgres\r
+ > psql -c "create user moodleuser createdb;" template1\r
+ > psql -c "create database moodle;" -U moodleuser template1\r
+ > psql -c "alter user moodleuser nocreatedb;" template1\r
+</PRE>\r
+ <p>(For MySQL I highly recommend the use of <a href="http://phpmyadmin.sourceforge.net/">phpMyAdmin</a> \r
+ to manage your databases).</p>\r
+<p>As of version 1.0.8, Moodle now supports table prefixes, and so can safely share \r
+ a database with tables from other applications.</p>\r
+</blockquote>\r
+<P> </P>\r
+<H3><A NAME="webserver" id="webserver"></A>6. Check your web server settings</H3>\r
+<blockquote>\r
+ <p>Firstly, make sure that your web server is set up to use index.php as a default \r
+ page (perhaps in addition to index.html, default.htm and so on).</p>\r
+ <p>In Apache, this is done using a DirectoryIndex parameter in your httpd.conf \r
+ file. Mine usually looks like this:</p>\r
+ <blockquote>\r
+ <pre><strong>DirectoryIndex</strong> index.php index.html index.htm </pre>\r
+ </blockquote>\r
+ <p>Just make sure index.php is in the list (and preferably towards the start \r
+ of the list, for efficiency).</p>\r
+ <p>Secondly, Moodle requires a number of PHP settings to be active for it to \r
+ work. <B>On most servers these will already be the default settings.</B>\r
+ However, some PHP servers (and some of the more recent PHP versions) may \r
+ have things set differently. These are defined in PHP's configuration\r
+ file (usually called php.ini):</p>\r
+ <blockquote>\r
+<pre>file_uploads = 1\r
+magic_quotes_gpc = 1\r
+short_open_tag = 1\r
+session.auto_start = 0\r
+</pre>\r
+ </blockquote>\r
+ <p>If you don't have access to httpd.conf or php.ini on your server, or you \r
+ have Moodle on a server with other applications that require different \r
+ settings, then you can OVERRIDE all of the default settings.\r
+ \r
+ <p>To do this, you need to create a file called <B>.htaccess</B> in Moodle's\r
+ main directory that contains definitions for these settings.\r
+ This only works on Apache servers and only when Overrides have been allowed.\r
+ <BLOCKQUOTE><PRE>\r
+DirectoryIndex index.php index.html index.htm\r
+php_value magic_quotes_gpc 1\r
+php_value file_uploads 1\r
+php_value short_open_tag 1\r
+php_value session.auto_start 0</BLOCKQUOTE></PRE>\r
+ <P>You can also do things like define the maximum size for uploaded files:\r
+ <BLOCKQUOTE><PRE>\r
+php_value upload_max_filesize 2M\r
+php_value post_max_size 2M\r
+ </BLOCKQUOTE></PRE>\r
+\r
+ <p>The easiest thing to do is just copy the sample file from lib/htaccess \r
+ and edit it to suit your needs. It contains further instructions. For \r
+ example, in a Unix shell:\r
+ <blockquote>\r
+ <pre>cp lib/htaccess .htaccess</pre>\r
+ </blockquote>\r
+\r
+</blockquote>\r
+<p> </p>\r
+<H3><A NAME="config"></A>7. Edit config.php</H3>\r
+<blockquote>\r
+ <p>Now you can edit the configuration file, <strong>config.php</strong>, using a \r
+ text editor. This file is used by all other files in Moodle.</p>\r
+ <p>To start with, make a copy of config-dist.php and call it config.php. We \r
+ do this so that your config.php won't be overwritten in case you upgrade Moodle \r
+ later on. </p>\r
+ <p>Edit config.php to specify the database details that you just defined (including \r
+ a table prefix - notice this is REQUIRED for PostgreSQL), as \r
+ well as the site address, file system directory and data directory. \r
+ The config file has detailed directions.</p>\r
+ <p>For the rest of this installation document we will assume your site is at: \r
+ <u>http://example.com/moodle</u></p>\r
+</blockquote>\r
+<P> </P>\r
+<H3><A NAME="admin"></A>8. Go to the admin page</H3>\r
+<blockquote> \r
+ <p>The admin page should now be working at: <u>http://example.com/moodle/admin</u>. \r
+ If you try and access the front page of your site you'll be taken there automatically \r
+ anyway. The first time you access this admin page, you will be presented with \r
+ a GPL agreement with which you need to agree before you can continue with the setup.</p>\r
+ <P>(Moodle will also try to set some cookies in your browser. If you have \r
+ your browser set up to let you choose to accept cookies, then you <B>must</B>\r
+ accept the Moodle cookies, or Moodle won't work properly.)\r
+ <p>Now Moodle will start setting up your database and creating tables to store data. \r
+ Firstly, the main database tables are created. You should see a number of SQL statements followed by \r
+ status messages (in green or red) that look like this:</p>\r
+ <blockquote> \r
+ <p>CREATE TABLE course ( id int(10) unsigned NOT NULL auto_increment, category \r
+ int(10) unsigned NOT NULL default '0', password varchar(50) NOT NULL default \r
+ '', fullname varchar(254) NOT NULL default '', shortname varchar(15) NOT \r
+ NULL default '', summary text NOT NULL, format tinyint(4) NOT NULL default \r
+ '1', teacher varchar(100) NOT NULL default 'Teacher', startdate int(10) \r
+ unsigned NOT NULL default '0', enddate int(10) unsigned NOT NULL default \r
+ '0', timemodified int(10) unsigned NOT NULL default '0', PRIMARY KEY (id)) \r
+ TYPE=MyISAM</p>\r
+ <p><FONT COLOR="#006600">SUCCESS</FONT></p>\r
+ <p>...and so on, followed by: <FONT COLOR="#FF0000">Main databases set up \r
+ successfully</FONT>. </p>\r
+ </blockquote>\r
+ <p>If you don't see these, then there must have been some problem with the database \r
+ or the configuration settings you defined in config.php. Check that PHP isn't \r
+ in a restricted "safe mode" (commercial web hosts often have safe mode turned \r
+ on). You can check PHP variables by creating a little file containing <? \r
+ phpinfo() ?> and looking at it through a browser. Check all these and try \r
+ this page again.</p>\r
+ <p>Scroll down the very bottom of the page and press the "Continue" \r
+ link.</p>\r
+ <p>Next you will see a similar page that sets up all the tables required by \r
+ each Moodle module. As before, they should all be green.</p>\r
+\r
+ <p>Scroll down the very bottom of the page and press the "Continue" \r
+ link.</p>\r
+\r
+ <p>You should now see a form where you can define more configuration variables\r
+ for your installation, such as the default language, SMTP hosts and so on.\r
+ Don't worry too much about getting everything right just now - you can always \r
+ come back and edit these later on using the admin interface. Scroll down \r
+ to the bottom and click "Save changes".</p>\r
+\r
+ <p>If (and only if) you find yourself getting stuck on this page or the next \r
+ page, unable to continue, then your server probably has what I call the \r
+ "buggy referrer" problem. This is easy to fix: just edit\r
+ your config.php and set the variable buggy_referrer to <i>true</i>, then \r
+ try the page again.</p>\r
+\r
+ <p>The next page is a form where you can define parameters for your Moodle site and the \r
+ front page, such as the name, format, description and so on. \r
+\r
+ Fill this out (you can always go back and change these later) and then press \r
+ "Save changes".</p>\r
+\r
+ <p>Finally, you will then be asked to create a top-level administration user \r
+ for future access to the admin pages. Fill out the details with your own name, \r
+ email etc and then click "Save changes". Not all the fields are \r
+ required, but if you miss any important fields you'll be re-prompted for them. \r
+ </p>\r
+ <blockquote> \r
+ <blockquote> \r
+ <blockquote> \r
+ <blockquote> \r
+ <blockquote>\r
+ <p><strong>Make sure you remember the username and password you chose \r
+ for the administration user account, as they will be necessary to \r
+ access the administration page in future.</strong></p>\r
+ </blockquote>\r
+ </blockquote>\r
+ </blockquote>\r
+ </blockquote>\r
+ </blockquote>\r
+ <p>Once successful, you will be returned to the main admin page, which contain \r
+ a number of links arranged in a menu (these items also appear on the home \r
+ page when you are logged in as the admin user). All your further administration \r
+ of Moodle can now be done using this menu, such as:</p>\r
+ <ul>\r
+ <li>creating and deleting courses</li>\r
+ <li>creating and editing user accounts</li>\r
+ <li>administering teacher accounts</li>\r
+ <li>changing site-wide settings like themes etc</li>\r
+ </ul>\r
+</blockquote>\r
+<P> </P>\r
+<H3><A NAME="cron"></A>9. Set up cron</H3>\r
+<blockquote> \r
+ <p>Some of Moodle's modules require continual checks to perform tasks. For example, \r
+ Moodle needs to check the discussion forums so it can mail out copies of posts \r
+ to people who have subscribed.</p>\r
+ <p>The script that does all this is located in the admin directory, and is called \r
+ cron.php. However, it can not run itself, so you need to set up a mechanism \r
+ where this script is run regularly (eg every five minutes). This provides \r
+ a "heartbeat" so that the script can perform functions at periods \r
+ defined by each module.</p>\r
+ <P>Note that the machine performing the cron <B>does not need to be the same \r
+ machine that is running Moodle</B>. For example, if you have a limited web hosting \r
+ service that does not have cron, then you can might choose to run cron on another \r
+ server or on your home computer. All that matters is that the cron.php file is \r
+ called every five minutes or so.</p>\r
+ <p>First, test that the script works by running it directly from your browser:</p>\r
+ <blockquote> \r
+ <PRE>http://example.com/moodle/admin/cron.php</PRE>\r
+ </blockquote>\r
+ <p>Now, you need to set up some of way of running the script automatically and \r
+ regularly. </p>\r
+ <H4> Running the script from a command line</H4>\r
+ <p>You can call the page from the command line just as you did in the example \r
+ above. For example, you can use a Unix utility like 'wget':</p>\r
+ <blockquote>\r
+ <PRE>wget -q -O /dev/null http://example.com/moodle/admin/cron.php</PRE>\r
+ </blockquote>\r
+ <p>Note in this example that the output is thrown away (to /dev/null).</p>\r
+ <p>The same thing using lynx:</p>\r
+ <blockquote>\r
+ <pre>lynx -dump http://example.com/moodle/admin/cron.php > /dev/null</pre>\r
+ </blockquote>\r
+ <p>Alternatively you could use a standalone version of PHP, compiled to be run \r
+ on the command line. The advantage with doing this is that your web server \r
+ logs aren't filled with constant requests to cron.php. The disadvantage is \r
+ that you need to have access to a command-line version of php.</p>\r
+ <blockquote>\r
+ <PRE>/opt/bin/php /web/moodle/admin/cron.php\r
+\r
+\r
+(Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php\r
+\r
+</PRE>\r
+ </blockquote>\r
+ <h4>Automatically running the script every 5 minutes</h4>\r
+ <p>On Unix systems: Use <B>cron</B>. Edit your cron settings from the commandline \r
+ using "crontab -e" and add a line like:</p>\r
+ <blockquote>\r
+ <PRE>*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php</PRE>\r
+ </blockquote>\r
+ <p>On Windows systems: The simplest way is to use my package <A TITLE="Click to download this package (150k)" HREF="http://moodle.com/download/moodle-cron-for-windows.zip">moodle-cron-for-windows.zip</A> \r
+ which makes this whole thing very easy. You can also explore using the built-in \r
+ Windows feature for "Scheduled Tasks".</p>\r
+ </p>\r
+</blockquote>\r
+<H3><A NAME="course"></A>10. Create a new course</H3>\r
+<blockquote>\r
+ <p>Now that Moodle is running properly, you can create a course. </p>\r
+ <p>Select "Create a new course" from the Admin page (or the admin \r
+ links on the home page).</p>\r
+ <p>Fill out the form, paying special attention to the course format. You don't \r
+ have to worry about the details too much at this stage, as everything can \r
+ be changed later by the teacher.</p>\r
+ <p>Press "Save changes", and you will be taken to a new form where \r
+ you can assign teachers to the course. You can only add existing user accounts \r
+ from this form - if you want to create a new teacher account then either ask \r
+ the teacher to create one for themselves (see the login page), or create one \r
+ for them using the "Add a new user" on the Admin page.</p>\r
+ <p>Once done, the course is ready to customise, and is accessible via the "Courses" \r
+ link on the home page.</p>\r
+ <p>See the "<A HREF="./?file=teacher.html">Teacher Manual</A>" for more details \r
+ on course-building.</p>\r
+</blockquote>\r
+<P> </P>\r
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>\r
+\r
+</BODY>\r
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">\r
+<HTML>\r
+<HEAD>\r
+ <TITLE>Moodle Docs: Introduction</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+<BODY BGCOLOR="#ffffff">\r
+ \r
+<H2>Introduction</H2>\r
+ \r
+<P>Moodle is a software package for producing internet-based courses and web sites. \r
+ It's an ongoing development project designed to support a <A HREF="http://dougiamas.com/writing/herdsa2002/">social constructionist</A> framework of education. </P>\r
+\r
+<P>Moodle is provided freely as <A HREF="http://www.opensource.org/docs/definition_plain.html"> \r
+ Open Source</A> software (under the <A HREF="http://www.gnu.org/copyleft/gpl.html"> \r
+ GNU Public License</A>). Basically this means Moodle is copyrighted, but that you have additional \r
+ freedoms. You are allowed to copy, use and modify Moodle <B>provided</B> that you agree: to provide \r
+ the source to others; to not modify or remove the original license, and apply this same \r
+ license to any derivative work.\r
+\r
+<P>Moodle will run on any computer that can run <A HREF="http://www.php.net/"> \r
+ PHP</A>, and can support many types of database (particularly <a href="http://www.mysql.com/">MySQL</a>).</P>\r
+\r
+<P>The word Moodle is an acronym for Modular Object-Oriented Dynamic Learning \r
+ Environment, which is mostly useful to programmers and education theorists. \r
+ It's also a verb that describes the process of lazily meandering through \r
+ something, doing things as it occurs to you to do them, an enjoyable tinkering \r
+ that often leads to insight and creativity. As such it applies both to the way \r
+ Moodle was developed, and to the way a student or teacher might approach studying \r
+ or teaching an online course.</P>\r
+<P><BR>\r
+</P>\r
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>\r
+\r
+</BODY>\r
+</HTML>\r
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">\r
+<HTML>\r
+<HEAD>\r
+ <TITLE>Moodle Docs: Copyright License</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+<BODY BGCOLOR="#ffffff">\r
+ \r
+<H2>Copyright License for Moodle</H2>\r
+ \r
+<P>Moodle is Copyright © 2001-2003, <A HREF="http://dougiamas.com/">Martin \r
+ Dougiamas</A>.</P>\r
+<P>This program is free software; you can redistribute it and/or modify<BR>\r
+ it under the terms of the GNU General Public License as published by<BR>\r
+ the Free Software Foundation; either version 2 of the License, or<BR>\r
+ (at your option) any later version.</P>\r
+<P>This program is distributed in the hope that it will be useful,<BR>\r
+ but WITHOUT ANY WARRANTY; without even the implied warranty of<BR>\r
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<BR>\r
+ GNU General Public License for more details (attached below).<BR>\r
+</P>\r
+\r
+<HR WIDTH="100%" SIZE="2"><BR>\r
+ \r
+<PRE> GNU GENERAL PUBLIC LICENSE<BR> Version 2, June 1991<BR><BR> Copyright (C) 1989, 1991 Free Software Foundation, Inc.<BR> 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<BR> Everyone is permitted to copy and distribute verbatim copies<BR> of this license document, but changing it is not allowed.<BR><BR> Preamble<BR><BR> The licenses for most software are designed to take away your<BR>freedom to share and change it. By contrast, the GNU General Public<BR>License is intended to guarantee your freedom to share and change free<BR>software--to make sure the software is free for all its users. This<BR>General Public License applies to most of the Free Software<BR>Foundation's software and to any other program whose authors commit to<BR>using it. (Some other Free Software Foundation software is covered by<BR>the GNU Library General Public License instead.) You can apply it to<BR>your programs, too.<BR><BR> When we speak of free software, we are referring to freedom, not<BR>price. Our General Public Licenses are designed to make sure that you<BR>have the freedom to distribute copies of free software (and charge for<BR>this service if you wish), that you receive source code or can get it<BR>if you want it, that you can change the software or use pieces of it<BR>in new free programs; and that you know you can do these things.<BR><BR> To protect your rights, we need to make restrictions that forbid<BR>anyone to deny you these rights or to ask you to surrender the rights.<BR>These restrictions translate to certain responsibilities for you if you<BR>distribute copies of the software, or if you modify it.<BR><BR> For example, if you distribute copies of such a program, whether<BR>gratis or for a fee, you must give the recipients all the rights that<BR>you have. You must make sure that they, too, receive or can get the<BR>source code. And you must show them these terms so they know their<BR>rights.<BR><BR> We protect your rights with two steps: (1) copyright the software, and<BR>(2) offer you this license which gives you legal permission to copy,<BR>distribute and/or modify the software.<BR><BR> Also, for each author's protection and ours, we want to make certain<BR>that everyone understands that there is no warranty for this free<BR>software. If the software is modified by someone else and passed on, we<BR>want its recipients to know that what they have is not the original, so<BR>that any problems introduced by others will not reflect on the original<BR>authors' reputations.<BR><BR> Finally, any free program is threatened constantly by software<BR>patents. We wish to avoid the danger that redistributors of a free<BR>program will individually obtain patent licenses, in effect making the<BR>program proprietary. To prevent this, we have made it clear that any<BR>patent must be licensed for everyone's free use or not licensed at all.<BR><BR> The precise terms and conditions for copying, distribution and<BR>modification follow.<BR>\f<BR> GNU GENERAL PUBLIC LICENSE<BR> TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION<BR><BR> 0. This License applies to any program or other work which contains<BR>a notice placed by the copyright holder saying it may be distributed<BR>under the terms of this General Public License. The "Program", below,<BR>refers to any such program or work, and a "work based on the Program"<BR>means either the Program or any derivative work under copyright law:<BR>that is to say, a work containing the Program or a portion of it,<BR>either verbatim or with modifications and/or translated into another<BR>language. (Hereinafter, translation is included without limitation in<BR>the term "modification".) Each licensee is addressed as "you".<BR><BR>Activities other than copying, distribution and modification are not<BR>covered by this License; they are outside its scope. The act of<BR>running the Program is not restricted, and the output from the Program<BR>is covered only if its contents constitute a work based on the<BR>Program (independent of having been made by running the Program).<BR>Whether that is true depends on what the Program does.<BR><BR> 1. You may copy and distribute verbatim copies of the Program's<BR>source code as you receive it, in any medium, provided that you<BR>conspicuously and appropriately publish on each copy an appropriate<BR>copyright notice and disclaimer of warranty; keep intact all the<BR>notices that refer to this License and to the absence of any warranty;<BR>and give any other recipients of the Program a copy of this License<BR>along with the Program.<BR><BR>You may charge a fee for the physical act of transferring a copy, and<BR>you may at your option offer warranty protection in exchange for a fee.<BR><BR> 2. You may modify your copy or copies of the Program or any portion<BR>of it, thus forming a work based on the Program, and copy and<BR>distribute such modifications or work under the terms of Section 1<BR>above, provided that you also meet all of these conditions:<BR><BR> a) You must cause the modified files to carry prominent notices<BR> stating that you changed the files and the date of any change.<BR><BR> b) You must cause any work that you distribute or publish, that in<BR> whole or in part contains or is derived from the Program or any<BR> part thereof, to be licensed as a whole at no charge to all third<BR> parties under the terms of this License.<BR><BR> c) If the modified program normally reads commands interactively<BR> when run, you must cause it, when started running for such<BR> interactive use in the most ordinary way, to print or display an<BR> announcement including an appropriate copyright notice and a<BR> notice that there is no warranty (or else, saying that you provide<BR> a warranty) and that users may redistribute the program under<BR> these conditions, and telling the user how to view a copy of this<BR> License. (Exception: if the Program itself is interactive but<BR> does not normally print such an announcement, your work based on<BR> the Program is not required to print an announcement.)<BR>\f<BR>These requirements apply to the modified work as a whole. If<BR>identifiable sections of that work are not derived from the Program,<BR>and can be reasonably considered independent and separate works in<BR>themselves, then this License, and its terms, do not apply to those<BR>sections when you distribute them as separate works. But when you<BR>distribute the same sections as part of a whole which is a work based<BR>on the Program, the distribution of the whole must be on the terms of<BR>this License, whose permissions for other licensees extend to the<BR>entire whole, and thus to each and every part regardless of who wrote it.<BR><BR>Thus, it is not the intent of this section to claim rights or contest<BR>your rights to work written entirely by you; rather, the intent is to<BR>exercise the right to control the distribution of derivative or<BR>collective works based on the Program.<BR><BR>In addition, mere aggregation of another work not based on the Program<BR>with the Program (or with a work based on the Program) on a volume of<BR>a storage or distribution medium does not bring the other work under<BR>the scope of this License.<BR><BR> 3. You may copy and distribute the Program (or a work based on it,<BR>under Section 2) in object code or executable form under the terms of<BR>Sections 1 and 2 above provided that you also do one of the following:<BR><BR> a) Accompany it with the complete corresponding machine-readable<BR> source code, which must be distributed under the terms of Sections<BR> 1 and 2 above on a medium customarily used for software interchange; or,<BR><BR> b) Accompany it with a written offer, valid for at least three<BR> years, to give any third party, for a charge no more than your<BR> cost of physically performing source distribution, a complete<BR> machine-readable copy of the corresponding source code, to be<BR> distributed under the terms of Sections 1 and 2 above on a medium<BR> customarily used for software interchange; or,<BR><BR> c) Accompany it with the information you received as to the offer<BR> to distribute corresponding source code. (This alternative is<BR> allowed only for noncommercial distribution and only if you<BR> received the program in object code or executable form with such<BR> an offer, in accord with Subsection b above.)<BR><BR>The source code for a work means the preferred form of the work for<BR>making modifications to it. For an executable work, complete source<BR>code means all the source code for all modules it contains, plus any<BR>associated interface definition files, plus the scripts used to<BR>control compilation and installation of the executable. However, as a<BR>special exception, the source code distributed need not include<BR>anything that is normally distributed (in either source or binary<BR>form) with the major components (compiler, kernel, and so on) of the<BR>operating system on which the executable runs, unless that component<BR>itself accompanies the executable.<BR><BR>If distribution of executable or object code is made by offering<BR>access to copy from a designated place, then offering equivalent<BR>access to copy the source code from the same place counts as<BR>distribution of the source code, even though third parties are not<BR>compelled to copy the source along with the object code.<BR>\f<BR> 4. You may not copy, modify, sublicense, or distribute the Program<BR>except as expressly provided under this License. Any attempt<BR>otherwise to copy, modify, sublicense or distribute the Program is<BR>void, and will automatically terminate your rights under this License.<BR>However, parties who have received copies, or rights, from you under<BR>this License will not have their licenses terminated so long as such<BR>parties remain in full compliance.<BR><BR> 5. You are not required to accept this License, since you have not<BR>signed it. However, nothing else grants you permission to modify or<BR>distribute the Program or its derivative works. These actions are<BR>prohibited by law if you do not accept this License. Therefore, by<BR>modifying or distributing the Program (or any work based on the<BR>Program), you indicate your acceptance of this License to do so, and<BR>all its terms and conditions for copying, distributing or modifying<BR>the Program or works based on it.<BR><BR> 6. Each time you redistribute the Program (or any work based on the<BR>Program), the recipient automatically receives a license from the<BR>original licensor to copy, distribute or modify the Program subject to<BR>these terms and conditions. You may not impose any further<BR>restrictions on the recipients' exercise of the rights granted herein.<BR>You are not responsible for enforcing compliance by third parties to<BR>this License.<BR><BR> 7. If, as a consequence of a court judgment or allegation of patent<BR>infringement or for any other reason (not limited to patent issues),<BR>conditions are imposed on you (whether by court order, agreement or<BR>otherwise) that contradict the conditions of this License, they do not<BR>excuse you from the conditions of this License. If you cannot<BR>distribute so as to satisfy simultaneously your obligations under this<BR>License and any other pertinent obligations, then as a consequence you<BR>may not distribute the Program at all. For example, if a patent<BR>license would not permit royalty-free redistribution of the Program by<BR>all those who receive copies directly or indirectly through you, then<BR>the only way you could satisfy both it and this License would be to<BR>refrain entirely from distribution of the Program.<BR><BR>If any portion of this section is held invalid or unenforceable under<BR>any particular circumstance, the balance of the section is intended to<BR>apply and the section as a whole is intended to apply in other<BR>circumstances.<BR><BR>It is not the purpose of this section to induce you to infringe any<BR>patents or other property right claims or to contest validity of any<BR>such claims; this section has the sole purpose of protecting the<BR>integrity of the free software distribution system, which is<BR>implemented by public license practices. Many people have made<BR>generous contributions to the wide range of software distributed<BR>through that system in reliance on consistent application of that<BR>system; it is up to the author/donor to decide if he or she is willing<BR>to distribute software through any other system and a licensee cannot<BR>impose that choice.<BR><BR>This section is intended to make thoroughly clear what is believed to<BR>be a consequence of the rest of this License.<BR>\f<BR> 8. If the distribution and/or use of the Program is restricted in<BR>certain countries either by patents or by copyrighted interfaces, the<BR>original copyright holder who places the Program under this License<BR>may add an explicit geographical distribution limitation excluding<BR>those countries, so that distribution is permitted only in or among<BR>countries not thus excluded. In such case, this License incorporates<BR>the limitation as if written in the body of this License.<BR><BR> 9. The Free Software Foundation may publish revised and/or new versions<BR>of the General Public License from time to time. Such new versions will<BR>be similar in spirit to the present version, but may differ in detail to<BR>address new problems or concerns.<BR><BR>Each version is given a distinguishing version number. If the Program<BR>specifies a version number of this License which applies to it and "any<BR>later version", you have the option of following the terms and conditions<BR>either of that version or of any later version published by the Free<BR>Software Foundation. If the Program does not specify a version number of<BR>this License, you may choose any version ever published by the Free Software<BR>Foundation.<BR><BR> 10. If you wish to incorporate parts of the Program into other free<BR>programs whose distribution conditions are different, write to the author<BR>to ask for permission. For software which is copyrighted by the Free<BR>Software Foundation, write to the Free Software Foundation; we sometimes<BR>make exceptions for this. Our decision will be guided by the two goals<BR>of preserving the free status of all derivatives of our free software and<BR>of promoting the sharing and reuse of software generally.<BR><BR> NO WARRANTY<BR><BR> 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY<BR>FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN<BR>OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES<BR>PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED<BR>OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF<BR>MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS<BR>TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE<BR>PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,<BR>REPAIR OR CORRECTION.<BR><BR> 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING<BR>WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR<BR>REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,<BR>INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING<BR>OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED<BR>TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY<BR>YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER<BR>PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE<BR>POSSIBILITY OF SUCH DAMAGES.<BR><BR> END OF TERMS AND CONDITIONS<BR></PRE>\r
+ \r
+\r
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>\r
+\r
+</BODY>\r
+</HTML>\r
--- /dev/null
+<HEAD>
+ <TITLE>Moodle Docs: Release notes</TITLE>
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">
+ <style type="text/css">
+ DT {font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif; font-weight: bold;}
+ DD {margin-bottom:1em;}
+ </style>
+</HEAD>
+
+<BODY BGCOLOR="#FFFFFF">
+<H2>Release notes</H2>
+
+<H3> New in Moodle 1.0.8.1 (12th January, 2003) :</H3>
+<UL><DL>
+<DT> No new features, just bug fixes:</DT>
+<DD>
+ <LI> Fixed one-in-a-million bug with email confirmations
+ <LI> Quiz feedback text can be styled
+ <LI> Deals better with a new module that is not readable
+ <LI> Fixed bug when setting times for assignments, quizzes when the teacher is in a different timezone to the server
+ <LI> Fixed listing of calendar months on some servers
+ <LI> Richtext editor now works properly in choice module
+ <LI> More robust when looking for some environment variables
+ <LI> Installer checks that sessions directory is writeable
+ <LI> Added a small test program to test sessions support
+</DD>
+</DL></UL>
+
+<HR>
+
+
+<H3> New in Moodle 1.0.8 (6th January, 2003) :</H3>
+<UL><DL>
+<DT> Databases</DT>
+<DD> Moodle now has complete native support support for <B>PostgreSQL 7</B> databases (thanks
+ to Mary Hunter for the SQL files and other ideas!).
+ Moodle also now supports table prefixes, which means you can install
+ Moodle into any database, even if it already contains tables from
+ other web applications.
+ A number of other changes have also been made to the code structure that will
+ make it fairly easy now to add full support for other database types.</DD>
+
+<DT> Languages </DT>
+<DD> <B><U>Six</U> new languages have been added!</B> Chinese (from Zhang Dexuan),
+ Arabic (from Ahmed Nabil), Turkish (from M. Cüneyt Birkök), Swedish (from Set Lonnert),
+ Thai (from Wim Singhanart) and Dutch (from Hans Zwart and Jacob Romeyn). Many thanks
+ to all these hard-working people! Most other languages have also had updates and fixes since 1.0.7.
+ The language editor has been improved slightly, making it easier to see
+ new strings and empty strings that need translating. The main documentation manual is
+ also now able to be localised and will appear in the current language if
+ translated versions exist.</DD>
+
+<DT> Layout</DT>
+<DD> A number of small improvements have been made in the layout of many pages (such
+ as the forum posting screen) to make them clearer, neater and smaller. Almost all text entry screens
+ now have specific help items alongside them (depending on the pedagogical
+ focus). The forums now have a quick search form available on every page.</DD>
+
+<DT> Themes </DT>
+<DD> Theme support of CSS has been extended to give theme makers more control
+ over more of the Moodle web site. A variety of new themes has been added
+ to the distribution.</DD>
+
+<DT> Resources</DT>
+<DD> A new type of resource has been added, called "Program", which allows
+ Moodle to cooperate with external web applications by passing information
+ about the current user and session to them.
+ Uploaded HTML files can now be edited using the WYSIWYG HTML editor. </DD>
+
+<DT> Choices</DT>
+<DD> Results can now be "published" (either with names or anonymously) so that
+ everyone can see the statistics. Choice text can be edited using HTML editor.</DD>
+
+<DT> Grades</DT>
+<DD> Students can now see all their own grades for a course on one page, accessible
+ from the course home page.</DD>
+
+<DT> Quizzes</DT>
+<DD> Students can now review all their past quiz attempts, but only if the quiz has been closed,
+ and if the teacher allows it.</DD>
+
+<DT> Authorisation </DT>
+<DD> The database module now supports databases that contain md5-encrypted passwords,
+ which means it should now be compatible with systems like PostNuke. When using
+ external authorisation students are now forced to fully fill-out their information
+ before they can enter any course. An ADOdb bug was also causing some mischief
+ when the external database type was the same as the Moodle database.
+ Overall it's now quite usable.</DD>
+
+<DT> Administration </DT>
+<DD> The admin can now assign other people to also be admins. The interface to the
+ Database Manager has been cleaned up, and it now always uses the same
+ language as the current Moodle language (see separate download for <A HREF="http://moodle.com/mod/resource/view.php?id=8">moodle-1.0.8-mysql-admin.zip</A>).</DD>
+
+<DT> Debugging mode </DT>
+<DD> Admins/developers can use a "debugging mode" which prints more information
+ and warning messages about unset variables and so on - making it easier to
+ find bugs. To make this work a LOT of cleaning up has been done on existing
+ Moodle code to make it more robust.</DD>
+
+<DT> Other things</DT>
+<DD>
+ <LI> Unpacked template module is ignored by Moodle.
+ <LI> A default country can be set by the admin
+ <LI> View source button in Richtext editor was missing with some languages
+ <LI> A bug affecting grades page on some installations was fixed.
+ <LI> File upload problems on 4.3.0 have been fixed.
+ <LI> Some minor problems with the display of logs has been fixed.
+ <LI> Improved GD detection that works with PHP 4.3.0
+ <LI> If GD is not present then Moodle is now more usable (just less capable)
+ <LI> A bug causing the wrong display of the date has been fixed.
+ <LI> Usernames can now contain "." and "-" characters.
+ <LI> Cookies now use table prefixes for unique naming, so that many
+ different moodle sites can be run on the same web site and database.
+ <LI> Site news forum heading can now be changed (edit the forum).
+ <LI> Improved code for gathering form input
+ <LI> The buggy_referrer variable is fixed and now works as expected
+ <LI> Some small performance improvements here and there
+ <LI> Other improvements I probably forgot to add here
+ <LI> Many little code clean-ups.
+</DD>
+
+</DL></UL>
+
+
+<HR>
+<H3> New in Moodle 1.0.7 (10th December, 2002): </H3>
+<UL><DL>
+<DT> Simpler version numbers!</DT>
+<DD> The four-digit version numbers were getting a bit ridiculous (too complex),
+ so I've switched back to simpler 3-digit numbers. The first digit is the
+ major structural version, the second digit is for decent-sized upgrades
+ and the third digit is for minor upgrades.</DD>
+
+<DT> Languages</DT>
+<DD> Two completely new languages have been added: Indonesian (from Arfan Hidayat)
+ and Japanese (from Mitsuhiro Yoshida). A US English version was added too.
+ Most other languages contain some updates. All languages now contain locale
+ information, which means that when a user changes the language all the dates
+ will display properly too.</DD>
+
+<DT> Database access</DT>
+<DD> ADOdb was upgraded to 2.50 which should fix some problems with very
+ new versions of PHP (4.3.0).</DD>
+
+<DT> Layout improvements</DT>
+<DD> Cleaned up the display of "side boxes" and added CSS style control over
+ more elements on the site and course pages. You may need to upgrade
+ your custom themes to get the full effect. Changes are in styles.php,
+ config.php and one line in header.html.
+
+ <P>The interface when
+ courses are on front page and there is more than one category has
+ been improved (no longer just shows short course names).</P>
+
+ </DD>
+
+<DT> Class interface</DT>
+<DD> A wrapper file provides a class interface to main Moodle library
+ (for external programs interfacing to Moodle) - moodle/lib/makeclass.php</DD>
+
+<DT> Small improvements and bug fixes</DT>
+<DD>
+ <LI> Quizzes now have a confirmation dialog when submitting an attempt
+ <LI> Courses now default to having "show recent activity" on (again).
+ <LI> Abolished leading zeroes in dates (introduced in last release)
+ <LI> Some formatting fixes for Japanese and old Netscape browsers
+ <LI> Teacher can allow larger assignments to be uploaded
+ <LI> Change password button on user page now always functions like the one on login page
+ <LI> Forum search now searches subjects as well as messages
+ <LI> Various HTML fixes
+ <LI> Fixes to grades display when there are no grades, also no forum ratings
+ <LI> Slashes in requested filenames are now stripped
+ <LI> Updates to the documentation
+</DD>
+
+
+</DL></UL>
+
+
+
+<HR>
+<H3> New in Moodle 1.0.6.4 (24th November, 2002) : </H3>
+<UL><DL>
+
+<DT> Authentication</DT>
+<DD> Moodle now features seven different authentication mechanisms,
+ making it possible to hook Moodle up to nearly any external list
+ of users!</P>
+ <P>New methods just added include IMAP, POP3 and NNTP servers (including
+ those using SSL or certificate-based authentication), and also
+ authentication against user-specified fields in ANY
+ external database table.</P>
+ <P>The login page can now be partially customised
+ by the admin with personalised instructions, and the guest login can be
+ hidden if desired. </P>
+ <P>"Mappings" can be defined so that other fields (such as email, firstname,
+ lastname, department, language etc) can also be copied from LDAP or an
+ external database when accounts are first used.</P>
+
+ <P>Finally, Moodle now sports a cool
+ new admin GUI for configuring all of this, so it should be pretty
+ easy now to set up external authentication.
+ Many thanks to contributor Petri Asikainen for helping with the admin GUI.</P></DD>
+
+<DT> Languages</DT>
+<DD> Complete new Norwegian translation (from Jøran Sørbø), and updates for several others.</DD>
+
+<DT> Assignments</DT>
+<DD> Students can now resubmit assignments after grading if the teacher allows it</DD>
+
+<DT> Contributed code</DT>
+<DD> Standalone user-contributed code is now distributed under the /contrib directory. This directory
+ could get quite large, and the quality/security of it has usually not been checked by me,
+ and so this code is not included in the standard releases and nightlies. However, people
+ who are interested in it can access it via CVS (or see <A HREF="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/contrib/">CVS web view</A>). As these new features become polished or if demand grows for them,
+ then I'll integrate them into the main Moodle distribution.
+ <BR><BR>
+ The first contributor is Holger Schadeck (compuproggy), who has written some <A HREF="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/contrib/compuproggy/">interesting code</A> to help with translating all the Moodle help files. Check it out!</DD>
+
+<DT> Bug fixes</DT>
+<DD>
+ <LI> Day value in dates (eg forum posts, weekly listing) are
+ now displayed correctly on Windows servers.
+ <LI> config-dist.php and README.txt is now in DOS format to make it easier for Windows users to get started (Unix users shouldn't be affected).
+ <LI> Added a workaround (and new config switch in config-dist.php) for
+ some systems which have buggy referer variables. This should help
+ those people getting "stuck" on a form during setup.
+ <LI> Logout now sends you to the home page and clears the session completely.
+ <LI> Timezones now range between -13 to 13 hours (for daylight saving).
+ <LI> Character set in email now matches current language.
+ <LI> User pictures are now uploaded even if other fields have errors.
+ <LI> Full-size user pictures on user profile page no longer clickable.
+ <LI> Long user listing now has a small notice at the bottom about automatic unenrolment
+ <LI> Unenrol and change password buttons are hidden for guest student
+ <LI> Fixed occasional case where submitted assignments were sometimes having their owner changed.
+ <LI> User log graphs are now faster, cleaner and translatable.
+ <LI> Fixed HTML display errors with courses in category boxes on front page.
+ <LI> Admin and guest accounts now always work, even with external authentication activated.
+ <LI> Slightly more security when writing/reading files (now checks for embedded scripting).
+ <LI> The same user can now be deleted more than once (create, delete, recreate, delete caused error).
+ <LI> Language editor now works with multibyte languages (Thanks, Mits)
+</DD>
+
+</DL></UL>
+
+
+<HR>
+<H3> New in Moodle 1.0.6.3 (14th November, 2002) : </H3>
+<UL><DL>
+
+<DT> Bug fix for no-name forums.</DT>
+<DD> New sites created with 1.0.6.2 had some forums appearing with no names
+ (for example the News forum on the home page).
+ A workaround is to add a new activity to that section (all the names
+ will be refreshed), but this release will fix it too. </DD>
+
+<DT> New languages!</DT>
+<DD> Catalan and Spanish (Spain) translations have arrived!</DD>
+
+<DT> Some display improvements for old Netscape browsers (headers and quizzes)</DT>
+
+<DT> Guest language now ALWAYS the same as the current site language</DT>
+
+<DT> "Recent Activity" can now be disabled completely if desired </DT>
+
+<DT> For very large classes (larger than 500) participant list is not displayed</DT>
+
+</DL></UL>
+
+<HR>
+
+<H3> New in Moodle 1.0.6.2 (11th November, 2002) : </H3>
+<UL><DL>
+<DT> Course formatting improvements </DT>
+<DD> The weekly and topic formats now have an extra "general" area up
+ the top where "general" activities are listed - these are things
+ that apply throughout the course, not just to one particular topic
+ or week. This general area is not shown if it is completely empty.</DD>
+
+<DT> Popup "jump" menu. </DT>
+<DD> You can now jump from one activity directly to any other using a
+ popup menu in the upper-right corner of the page</DD>
+
+<DT> Speed improvements </DT>
+<DD> Course activity details are now cached for each course, which
+ greatly reduces the amount of database access required to display
+ the course page. On heavily accessed systems this should improve speed.</DD>
+
+<DT> Languages </DT>
+<DD> Surveys are now completely translatable.</DD>
+
+<DT> Admin improvements </DT>
+<DD> Paging was added to the user admin page, so that the admin can now
+ browse large numbers of users. </DD>
+
+<DT> Fixes and tweaks </DT>
+<DD> Various other small improvements to formatting</DD>
+</DL></UL>
+
+
+<HR>
+
+<H3> New in Moodle 1.0.6.1 (6th November, 2002) : </H3>
+<UL><DL>
+<DT> New assignment type: offline assignments </DT>
+<DD> In addition to "upload a file" assignments, you can now have "offline"
+ assignments. These don't require the student to do anything online.
+ They are useful for grading activities that are not on in Moodle, and a
+ also useful for adding "manual" columns to the grade page.</DD>
+
+<DT> Languages </DT>
+<DD> Spanish (Mexican) has been added to the distribution. Other languages have various improvements.</DD>
+
+<DT> SMTP authentication </DT>
+<DD> SMTP mail now supports SMTP username and password if needed</DD>
+
+<DT> Documentation </DT>
+<DD> Some parts rewritten, and documentation cleaned up (upgrade info now part of main docs)</DD>
+
+<DT> Other fixes </DT>
+<UL><LI>Better checking on teachers using "loginas" to stop them roaming other courses as a student
+ <LI>While using "loginas", teachers can return to their own identity using a link in the footer
+ <LI>Some strings fixed in assignments, journals, and forums.
+ <LI>Guest language is now the same as the site
+ <LI>etc
+ </UL></DD>
+
+</DL></UL>
+
+
+<HR>
+<H3> New in Moodle 1.0.6 (26th October, 2002) : </H3>
+
+<UL><DL>
+<DT> New feature - WYSIWYG Text editing! </DT>
+<DD> A WYSIWYG text editor has been added to many of the forms in Moodle. These are currently
+ only visible when using Microsoft Internet Explorer 5.5 or later - other browsers see the
+ normal forms exactly as before.</DD>
+
+<DT> New feature - Quiz module! </DT>
+<DD> Finally, the most requested new module is here! Multiple choice, short answer, and true-false
+ questions with automatic marking, multiple attempts, teacher regrading and many other features.
+ Questions are stored in a categorised database, and may be "published" to other courses.</DD>
+
+<DT> New feature - Grade manager! </DT>
+<DD> A new tool has been added for teachers to see all grades for a course on one page.
+ You can also download/export grades as a tab-separated text file or an Excel
+ Spreadsheet. In future more features will be added to this page like sorting, manual
+ columns and calculations, but it's still pretty useful right now.</DD>
+
+<DT> New feature - LDAP authentication! </DT>
+<DD> Moodle can now authenticate against external directories that use the
+ LDAP protocol (including Novell etc). Many thanks to Petri Asikainen for
+ developing this authentication plug-in!</DD>
+
+<DT> New feature - New smilies </DT>
+<DD> Many new smilies have been added, and are now also accessible using a GUI in the text editor.</DD>
+
+<DT> Improved text editing </DT>
+<DD> You can now include all major HTML tags in all texts. This is now safe because
+ of newly added functionality that strips all Javascript and faulty tags from texts
+ before they can cause security or display problems.</DD>
+
+<DT> Languages </DT>
+<DD> German and Italian have been added! Many thanks to the translators (see the credits).</DD>
+
+<DT> Reading module => Resource module </DT>
+<DD> After much thought and a vote of support (21 "yes" to 6 "no") on the "Using Moodle"
+ web site I changed the name of the "reading" module to "resource" (at the code level
+ and also the language packs). It was better to do this earlier than later.
+ This more generic name will be more meaningful to more people and opens the way to
+ some real development on a resource library.
+ But I don't want to ever change a module name again! :-)
+ If you have any hard-coded URLs pointing to readings that you don't want to break,
+ you can add a line like this to your Apache httpd.conf to redirect them:
+ <P><CODE>Redirect /mod/reading http://yourserver.com/mod/resource</CODE></P>
+ <FONT COLOR=RED>Note: if upgrading to 1.0.6 you may have some "reading" errors in "Recent activity" ... logging
+ out and then logging in again will fix this</FONT></DD>
+
+<DT> Other additions </DT>
+<DD> An admin script to totally delete the Moodle data directory has been included (admin/delete.php)
+ for people who need to tear down a Moodle installation but don't have root access on their
+ server.</DD>
+
+<DT> Miscellaneous </DT>
+<DD> Many small improvements have been made to the interface, and many small bugs have been fixed.
+ Some examples:
+ <UL>
+ <LI> Big "Edit this page" buttons at the top of pages (replacing the tiny icon)
+ <LI> LDAP authentication module (thanks to Petri)
+ <LI> Authentication from external sources can now import any fields
+ <LI> Student assignment list now shows submission status properly
+ <LI> Default language for users is now the site language
+ <LI> Users have a 'Change Password' button on their profile page
+ <LI> Journals that need teacher feedback are highlighted
+ <LI> More documentation and more context help buttons
+ <LI> Database-specific upgrade code
+ <LI> Uses character-set codes to make the browser do the right thing
+ <LI> User's name in footer is now a link
+ <LI> News and social forums are now editable
+ <LI> Forums that don't allow posting don't have uneccessary "discuss" links
+ <LI> Improved algorithm for shortening posts in forum listings
+ <LI> Choice module now allows up to six choices
+ </UL>
+</DD>
+</DL></UL>
+
+<P>Older releases can be seen in the <A HREF="http://moodle.com/mod/forum/view.php?f=1">Moodle.com announcement forum</A>.
+
+
+<P> </P>
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="../doc/" TARGET="_top">Moodle Documentation</A></FONT></P>
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>
--- /dev/null
+<HEAD>\r
+ <TITLE>Moodle Docs: Teachers Manual</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+\r
+<BODY BGCOLOR="#FFFFFF">\r
+\r
+<H2>Teacher Manual</H2>\r
+<P>This page is a quick guide to creating online courses with Moodle. It outlines \r
+ the main functions that are available, as well as some of the main decisions \r
+ you'll need to make.</P>\r
+\r
+<P>Sections in this document:</P>\r
+<OL>\r
+ <LI><A HREF="#started">Getting started</A></LI>\r
+ <LI><A HREF="#settings">Course settings</A></LI>\r
+ <LI><A HREF="#upload">Uploading files</A></LI>\r
+ <LI><A HREF="#activities">Setting up activities</A></LI>\r
+ <LI><A HREF="#course">Running the course</A></LI>\r
+ <LI><A HREF="#further">Further information</A></LI>\r
+</OL>\r
+<H3><A NAME="started"></A>Getting started</H3>\r
+<blockquote> \r
+ <p>This document assumes your site administrator has set up Moodle and given \r
+ you new, blank course to start with. It also assumes you have logged in to \r
+ your course using your teacher account.</p>\r
+ <p>Here are three general tips that will help you get started.</p>\r
+ <ol>\r
+ <li><strong>Don't be afraid to experiment:</strong>\r
+ <blockquote>feel free to poke around and change things. It's hard to break anything \r
+ in a Moodle course, and even if you do it's usually easy to fix it.\r
+ </blockquote>\r
+ <li><strong>Notice and use these little icons</strong>: \r
+ <blockquote> \r
+ <p> <img src="../pix/i/edit.gif"> - the <strong>edit icon</strong> \r
+ lets you edit whatever it is next to.</p>\r
+ <p><img src="../pix/help.gif" width="22" height="17"> - the <strong>help \r
+ icon</strong> will provide you with a popup help window </p>\r
+ </blockquote>\r
+ </li>\r
+ <li><strong>Use the navigation bar at the top of each page</strong>\r
+ <blockquote>this \r
+ should help remind you where you are and prevent getting lost.\r
+ </blockquote></li>\r
+ </ol>\r
+ <hr>\r
+</blockquote>\r
+<h3><A NAME="settings"></A>Course settings</h3>\r
+<blockquote> \r
+ <p>The first thing you should do is look under the "Administration" \r
+ on your course home page and click on "<strong>Settings...</strong>" \r
+ (Note that this link, and in fact the whole Administration section is only \r
+ available to you (and the site administrator). Students will not even see \r
+ these links).</p>\r
+ <p>On the Settings page you can change a number of settings about your course, \r
+ ranging from its name to what day it starts. I won't talk here about all these, \r
+ as they all have a help icon next to them which explains them all in detail. \r
+ However, I will talk about the most important of these - the <strong>course \r
+ format</strong>.</p>\r
+ <p>The course format that you choose will decide the basic layout of your course, \r
+ like a template. Moodle version 1.0 has three formats - in future there will \r
+ probably be many more (please send new ideas to <a href="mailto:martin@moodle.com">martin@moodle.com</a>!)</p>\r
+ <p>Here are some screenshots of three sample courses in each of these three \r
+ formats (ignore the different colours, which are set for a whole site by the \r
+ site administrator):</p>\r
+ <p align="center"><strong>Weekly format:</strong></p>\r
+ <p align="center"><img src="pix/weekly.jpg" width="570" height="527"></p>\r
+ <p align="center"> </p>\r
+ <p align="center"><strong>Topics format:</strong></p>\r
+ <p align="center"><img src="pix/topics.jpg" width="570" height="463"></p>\r
+ <p align="center"> </p>\r
+ <p align="center"><strong>Social format:</strong></p>\r
+ <p align="center"><img src="pix/social.jpg" width="570" height="429"></p>\r
+ <p> </p>\r
+ <p>Note that the weekly and topics formats are very similar in structure. The \r
+ main difference is that each box in the weekly format covers exactly one week, \r
+ whereas in the topic format each box can cover whatever you like. The social \r
+ format doesn't use much content at all and is based around just one forum \r
+ - this is displayed on the main page.</p>\r
+ <p>See the help buttons on the Course Settings page for more details.</p>\r
+ <HR>\r
+</blockquote>\r
+<H3><A NAME="upload"></A>Uploading files</H3>\r
+<blockquote> \r
+ <p>You may have existing content that you want to add to your course, such as \r
+ web pages, audio files, video files, word documents, or flash animations. \r
+ Any type of file that exists can be uploaded into your course and stored on \r
+ the server. While your files are on the server you can move, rename, edit \r
+ or delete them.</p>\r
+ <p>All of this is achieved through the <strong>Files</strong> link in your Administration \r
+ menu. The Files section looks like this:</p>\r
+ <p align="center"><img src="pix/files.jpg" width="400" height="347"></p>\r
+ <p> </p>\r
+ <p>This interface is only available to teachers - it is not accessible by students. \r
+ Individual files are made available to students later on (as "Resources" \r
+ - see the next section).</p>\r
+ <p>As you can see in the screenshot, files are listed alongside subdirectories. \r
+ You can create any number of subdirectories to organise your files and move \r
+ your files from one to the other.</p>\r
+ <p>Uploading files via the web is currently restricted to one file at a time. \r
+ If you want to upload a lot of files at once (for example a whole web site), \r
+ it can be a lot easier to use a <strong>zip program</strong> to compress them \r
+ into a single file, upload the zip file and then unzip them again on the server \r
+ (you will see an "unzip" link next to zip archives).</p>\r
+ <p>To preview any file you have uploaded just click on its name. Your web browser \r
+ will take care of either displaying it or downloading it to your computer.</p>\r
+ <p>HTML and text files can be edited in-place online. Other files will need \r
+ to be edited on your local computer and uploaded again. if you upload a file \r
+ with the same name as an existing file it will automatically be overwritten.</p>\r
+ <p>A final note: if your content resides out on the web then you don't need \r
+ to upload the files at all - you can link directly to them from inside the \r
+ course (see the Resources module and the next section).</p>\r
+ <HR>\r
+</blockquote>\r
+<H3><A NAME="activities"></A>Setting up activities</H3>\r
+<blockquote> \r
+ <p>Building a course involves adding course activity modules to the main page \r
+ in the order that students will be using them. You can shuffle the order any \r
+ time you like.</p>\r
+ <p>To turn on editing, click "Turn on editing" under Administration. \r
+ This toggle switch shows or hides the extra controls that allow you to manipulate \r
+ your main course page. Note in the first screenshot above (of the Weekly format \r
+ course) that the editing controls are turned on.</p>\r
+ <p>To add a new activity, simply go to the week or topic or section of the screen \r
+ where you want to add it, and select the type of activity from the popup menu. \r
+ Here is a summary of all the standard activities in Moodle 1.0:</p>\r
+ <dl>\r
+ <dt><strong>Assignment</strong></dt>\r
+ <dd>An assignment is where you set a task with a due date and a maximum grade. \r
+ Students will be able to upload one file to satisify the requirements. The \r
+ date they upload their file is recorded. Afterwards, you will have a single \r
+ page on which ou can view each file (and how late or early it is), and then \r
+ record a grade and a comment. Half an hour after you grade any particular \r
+ student, Moodle will automatically email that student a notification. </dd><BR>\r
+ <BR>\r
+ <dt><strong>Choice</strong></dt>\r
+ <dd>A choice activity is very simple - you ask a question and specify a choice \r
+ of responses. Students can make their choice, and you \r
+ have a report screen where you can see the results. I use it to gather research \r
+ consent from my students, but you could use it for quick polls or class \r
+ votes.</dd>\r
+ <BR>\r
+ <BR>\r
+ <dt><strong>Forum</strong></dt>\r
+ <dd>This module is by far the most important - it is here that discussion \r
+ takes place. When you add a new forum, yu will presented with a choice of \r
+ different types - a simple single-topic discussion, a free-for-all general \r
+ forum, or a one-discussion-thread-per-user.</dd>\r
+ <BR>\r
+ <BR>\r
+ <dt><strong>Journal</strong></dt>\r
+ <dd>Each journal activity is an entry in the whole course journal. For each \r
+ one you can specify an open-ended question that guides what students write, \r
+ as well as a window of time in which the journal is open (weekly course \r
+ format only). Encourage students to write reflectively and critically in \r
+ these journals, as they are only available to them and you. Afterwards, \r
+ you will be able to grade and comment all the entries for that week or topic, \r
+ and students will receive an automatic email informing them of your feedback.</dd>\r
+ <BR>\r
+ <BR>\r
+ <dt><strong>Resource</strong></dt>\r
+ <dd>Resources are the content of your course. Each resource can be any file \r
+ you have uploaded or can point to using a URL. You can also maintain simple text-based pages by typing them\r
+ directly into a form.</dd>\r
+ <BR>\r
+ <BR>\r
+ <dt><strong>Quiz</strong></dt>\r
+ <dd>This module allows you to design and set quiz tests, consisting of\r
+ multiple choice, true-false, and short answer questions. These\r
+ questions are kept in a categorised database, and can be re-used\r
+ within courses and even between courses. Quizzes can allow\r
+ multiple attempts. Each attempt is automatically marked, and the\r
+ teacher can choose whether to give feedback or to show correct answers.\r
+ This module includes grading facilities.\r
+ </dd>\r
+ <BR>\r
+ <BR>\r
+ <dt><strong>Survey</strong></dt>\r
+ <dd>The survey module provides a number of predefined survey instruments that are useful in \r
+ evaluating and understanding your class. Currently they include the COLLES and the ATTLS instruments.\r
+ They can be given to students early in the course as a diagnostic tool and at the end of the \r
+ course as an evaluation tool (I use one every week in my courses).</dd>\r
+ </dl>\r
+ <BR>\r
+ <p>After adding your activities you can move them up and down in your course \r
+ layout by clicking on the little arrow icons (<img src="../pix/t/up.gif" width="9" height="10"> \r
+ <img src="../pix/t/down.gif" width="9" height="10">) next to each one. You \r
+ can also delete them using the cross icon <img src="../pix/t/delete.gif" width="10" height="10">, \r
+ and re-edit them using the edit icon <img src="../pix/t/edit.gif" width="10" height="11">.</p>\r
+ <HR>\r
+</blockquote>\r
+<H3><A NAME="course"></A>Running the course</H3>\r
+<blockquote> \r
+ <p>I could write a thesis about this. Actually I <strong>am</strong> writing \r
+ a thesis about this. <img src="../pix/s/biggrin.gif" width="15" height="15"></p>\r
+ <p>Until then here are just a few quick pointers:</p>\r
+ <ol>\r
+ <li>Subscribe yourself to all the forums.</li>\r
+ <li>Encourage all the students fill out their user profile (including photos) \r
+ and read them all - this will help provide some context to their later writings.</li>\r
+ <li>Keep notes to yourself in the private "<strong>Teacher's Forum</strong>" \r
+ (under Administration). This is especially useful when team teaching.</li>\r
+ <li>Use the "<strong>Logs</strong>" link (under Administration) \r
+ to get access to complete, raw logs. In there you'll see a link to a popup \r
+ window that updates every sixty seconds and shows the last hour of activity. \r
+ This is useful to keep open on your desktop all day so you can feel in touch \r
+ with what's going on in the course.</li>\r
+ <li>Use the "<strong>Activity Reports</strong>" (next to each name \r
+ in the list of all people, or from any user profile page). These provide \r
+ a great way to see what any particular person has been up to in the course.</li>\r
+ <li>Respond quickly to students. Don't leave it for later - do it right away. \r
+ Not only is it easy to become overwhelmed with the volume that can be generated, \r
+ but it's a crucial part of building and maintaining a community feel in \r
+ your course.</li>\r
+ </ol>\r
+ <HR>\r
+</blockquote>\r
+<H3><A NAME="further"></A>Further information</H3>\r
+<blockquote> \r
+ <p>If you have any particular problems with your site, you should contact your \r
+ local site administrator.</p>\r
+ <p>If you have some great ideas for improvements to Moodle, or even some good \r
+ stories, come over to <a href="http://moodle.com/" target="_top">moodle.com</a> and join \r
+ in the course called "<A HREF="http://moodle.com/course/view.php?id=5" target=_top >Using Moodle</A>". \r
+ We'd love to hear from you, and you can help Moodle improve.</p>\r
+ <p>If you want to contribute to coding new modules, or writing documentation, \r
+ or papers, contact me: <a href="http://dougiamas.com/" target="_top">Martin \r
+ Dougiamas</a> or browse the "bug tracker" site for Moodle, at <a href="http://bugs.moodle.com" target="_top">bugs.moodle.com</a></p>\r
+ <p align="center">Thanks for using Moodle - good luck!</p>\r
+ <HR>\r
+ <p> </p>\r
+</blockquote>\r
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01 \r
+ martin Exp $</FONT></P>\r
+\r
+</BODY>\r
--- /dev/null
+<HEAD>\r
+ <TITLE>Moodle Docs: Upgrading</TITLE>\r
+ <LINK REL="stylesheet" HREF="../theme/standard/styles.php" TYPE="TEXT/CSS">\r
+</HEAD>\r
+\r
+<BODY BGCOLOR="#FFFFFF">\r
+<H2>Upgrading Moodle</H2>\r
+\r
+<p>Moodle is designed to upgrade cleanly from any earlier version to any later \r
+ version. </p>\r
+<p>When upgrading a Moodle installation you should follow these steps:</p>\r
+<h2>1. Backup important data</h2>\r
+<blockquote> \r
+ <p>Although it is not strictly necessary, it is always a good idea to make a \r
+ backup of any production system before a major upgrade, just in case you need \r
+ to revert back to the older version for some reason. In fact, it's a good \r
+ idea to automate your server to backup your Moodle installation daily, so \r
+ that you can skip this step.</p>\r
+ <p>There are three areas that need backing up:</p>\r
+ <blockquote> \r
+ <p><strong>1. The Moodle software directory itself</strong></p>\r
+ <blockquote> \r
+ <p>Make a separate copy of these files before the upgrade, so that you can \r
+ retrieve your config.php and any modules you have added like themes, languages \r
+ etc<strong><br>\r
+ </strong></p>\r
+ </blockquote>\r
+ <p><strong>2. Your data directory.</strong></p>\r
+ <blockquote> \r
+ <p>This is where uploaded content resides (such as course resources and \r
+ student assignments) so it is very important to have a backup of these \r
+ files anyway. Sometimes upgrades may move or rename directories within \r
+ your data directory.<strong><br>\r
+ </strong></p>\r
+ </blockquote>\r
+ <p><strong>3. Your database</strong></p>\r
+ <blockquote> \r
+ <p>Most Moodle upgrades will alter the database tables, adding or changing \r
+ fields. Each database has different ways to backup. One way of backing \r
+ up a MySQL database is to 'dump' it to a single SQL file. The following \r
+ example shows Unix commands to dump the database called "moodle":</p>\r
+ <blockquote>\r
+ <p><font face="Courier New, Courier, mono">mysqldump moodle > moodle-backup-2002-10-26.sql</font></p>\r
+ </blockquote>\r
+ <p>You can also use the "Export" feature in Moodle's "Manage \r
+ Database" web interface to do the same thing on all platforms.</p>\r
+ </blockquote>\r
+ </blockquote>\r
+</blockquote>\r
+<h2> </h2>\r
+<h2>2. Install the new Moodle software</h2>\r
+<blockquote> \r
+ <p><strong>Using a downloaded archive</strong></p>\r
+ <blockquote> \r
+ <p>Do not overwrite an old installation unless you know what you are doing \r
+ ... sometimes old files can cause problems in new installations. The best \r
+ way it to rename the current Moodle directory to something else, then unpack \r
+ the new Moodle archive into the old location.</p>\r
+ <blockquote> \r
+ <p><font face="Courier New, Courier, mono">mv moodle moodle.backup<br>\r
+ tar xvzf moodle-1.0.6.tgz</font></p>\r
+ </blockquote>\r
+ <p>Next, copy across your config.php and any other plugins such as custom \r
+ themes:</p>\r
+ <blockquote>\r
+ <p><font face="Courier New, Courier, mono">cp moodle.backup/config.php moodle<br>\r
+ cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme</font></p>\r
+ </blockquote>\r
+ </blockquote>\r
+ <p><strong>Using CVS</strong></p>\r
+ <blockquote> \r
+ <p>If you are using CVS, just go into the Moodle root directory and update \r
+ to the new files:</p>\r
+ <blockquote> \r
+ <p><font face="Courier New, Courier, mono">cvs update -dP</font></p>\r
+ </blockquote>\r
+ <p>Make sure you use the "d" parameter to create new directories \r
+ if necessary, and the "P" parameter to prune empty directories.</p>\r
+ <p>If you have been editing Moodle files, watch the messages very closely \r
+ for possible conflicts. All your customised themes and non-standard plugins \r
+ will be untouched.</p>\r
+ </blockquote>\r
+ <p> </p>\r
+</blockquote>\r
+<h2>3. Finishing the upgrade</h2>\r
+<blockquote> \r
+ <p>The last step is to trigger the upgrade processes within Moodle.</p>\r
+ <p>To do this just visit <a target=_top href="../admin/index.php">the admin page of your \r
+ installation</a>.</p>\r
+ <blockquote> \r
+ <p><font face="Courier New, Courier, mono">http://example.com/moodle/admin</font></p>\r
+ </blockquote>\r
+ <p>It doesn't matter if you are logged in as admin or not.</p>\r
+ <p> Moodle will automatically detect the new version and perform all the database \r
+ or filesystem upgrades that are necessary. If there is anything it can't do \r
+ itself (very rare) then you will see messages telling you what you need to \r
+ do. </p>\r
+</blockquote>\r
+<p> </p>\r
+<p> Assuming all goes well (no error messages) then you can start using your new \r
+ version of Moodle and enjoy the new features!</p>\r
+<p>If you have trouble with the upgrade, visit <a target=_top href="http://moodle.com/">moodle.com</a> \r
+ and post on the <a target=_top href="http://moodle.com/mod/forum/view.php?id=28">Installation \r
+ Support Forum</a>.</p>\r
+<p> </p>\r
+<P> </P>\r
+<P ALIGN="CENTER"><FONT SIZE="1"><A HREF="." TARGET="_top">Moodle Documentation</A></FONT></P>\r
+<P ALIGN="CENTER"><FONT SIZE="1">Version: $Id$</FONT></P>\r
+\r
+</BODY>\r
projects / moodle.git / commitdiff