\r
print_header();\r
\r
- echo "<font size=2 face=\"san-serif\">";\r
foreach ($string as $file => $filename) {\r
- echo "<li><a target=\"main\" href=\"$CFG->wwwroot/doc/?file=$file\">$filename</a></li>";\r
+ if (substr($file,0,1) == "-") {\r
+ echo '<p style="font-size:small;margin-bottom:0px;font-family:Trebuchet MS, Verdana, Arial, Helvetica, sans-serif;">'.\r
+ $filename.'</p>';\r
+ } else {\r
+ echo "<li style=\"font-size:small\"><a target=\"main\" href=\"$CFG->wwwroot/doc/?file=$file\">$filename</a></li>";\r
+ }\r
}\r
- echo "</font>";\r
\r
?>\r
-<!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
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
-</head>\r
-<body bgcolor="#ffffff">\r
- \r
-<h2>Background</h2>\r
- \r
-<p>Moodle is an active and evolving work in progress. Development was started \r
- by <a href="http://moodle.org/user/view.php?id=1&course=1" target="_top">Martin \r
- Dougiamas</a> who continues to lead the project:</p>\r
-<blockquote>\r
- <p><em>I've been working on it, in some way or other, for several years. It \r
- started in the 90's when I was webmaster at <a target=_top href="http://www.curtin.edu.au/">Curtin \r
- University of Technology</a> and a system administrator of their WebCT installation. \r
- I encountered many frustrations with the WebCT beast and developed an itch \r
- that needed scratching - there had to be a better way (no, not Blackboard \r
- :-)</em></p>\r
- <p><em>I also know a lot of people in schools and smaller institutions (and \r
- some big ones!) who want to make better use of the Internet but don't know \r
- where to start in the maze of technologies and pedagogies that are out there. \r
- I've always hoped there would be a Free alternative that such people could \r
- use to help them move their teaching skills into the online environment. </em></p>\r
- <p><em>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. In particular, I am particularly influenced \r
- by the epistemology of social constructionism - which not only treats learning \r
- as a social activity, but focusses attention on the learning that occurs while \r
- actively constructing artifacts (such as texts) for others to see or use. \r
- </em></p>\r
- <p><em>It is crucial to me that this software be easy to use - in fact it should \r
- be as intuitive as possible. </em></p>\r
- <p><em>I'm committed to continuing my work on Moodle and on keeping it Open \r
- and Free. I have a deeply-held belief in the importance of unrestricted education \r
- and empowered teaching, and Moodle is the main way I can contribute to the \r
- realisation of these ideals.</em></p>\r
-</blockquote>\r
-<p>A number of early prototypes were produced and discarded before he released \r
- version 1.0 upon a largely unsuspecting world on August 20, 2002. This version \r
- was targeted towards smaller, more intimate classes at University level, and \r
- was the subject of research case studies that closely analysed the nature of \r
- collaboration and reflection that occurred among these small groups of adult \r
- participants.\r
-<p>Since then there has been steady series of new releases adding new features, \r
- better scalability and improved performance. \r
-<p>As Moodle has spread and the community has grown, more input is being drawn \r
- from a wider variety of people in different teaching situations. For example, \r
- Moodle is now used not only in Universities, but in high schools, primary schools, \r
- non-profit organisations, private companies, by independent teachers and even \r
- homeschooling parents. A growing number of people from around the world are \r
- contributing to Moodle in different ways - for more details see the <a href="?file=credits.html">Credits</a> \r
- page. \r
-<p>An important feature of the Moodle project is the <a href="http://moodle.org" target="_top">moodle.org</a> \r
- web site, which provides a central point for information, discussion and collaboration \r
- among Moodle users, who include system administrators, teachers, researchers, \r
- instructional designers and of course, developers. Like Moodle, this site is \r
- always evolving to suit the needs of the community, and like Moodle it will \r
- always be Free.\r
-<p>In 2003, the company <a href="http://moodle.com/" target="_top">moodle.com</a> \r
- was launched to provide additional commercial support for those need it, as \r
- well as managed hosting, consulting and other services.\r
-<p>For more about our future plans for Moodle, see the <a href="?file=future.html">Future</a> \r
- roadmap.</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
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+ <title>Moodle Docs: Background</title>
+ <link rel="stylesheet" href="./docstyles.css" type="TEXT/CSS">
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body bgcolor="#ffffff">
+
+<h1>Background</h1>
+
+<blockquote>
+ <p>Moodle is an active and evolving work in progress. Development was started
+ by <a href="http://moodle.org/user/view.php?id=1&course=1" target="_top">Martin
+ Dougiamas</a> who continues to lead the project:</p>
+ <blockquote>
+ <p><em>I've been working on it, in some way or other, for several years. It
+ started in the 90's when I was webmaster at <a target=_top href="http://www.curtin.edu.au/">Curtin
+ University of Technology</a> and a system administrator of their WebCT installation.
+ I encountered many frustrations with the WebCT beast and developed an itch
+ that needed scratching - there had to be a better way (no, not Blackboard
+ :-)</em></p>
+ <p><em>I also know a lot of people in schools and smaller institutions (and
+ some big ones!) who want to make better use of the Internet but don't know
+ where to start in the maze of technologies and pedagogies that are out there.
+ I've always hoped there would be a Free alternative that such people could
+ use to help them move their teaching skills into the online environment. </em></p>
+ <p><em>My strong beliefs in the unrealised possibilities of Internet-based education
+ led me to complete a Masters and then a PhD in Education, combining my former
+ career in Computer Science with newly constructed knowledge about the nature
+ of learning and collaboration. In particular, I am particularly influenced
+ by the epistemology of social constructionism - which not only treats learning
+ as a social activity, but focusses attention on the learning that occurs while
+ actively constructing artifacts (such as texts) for others to see or use.
+ </em></p>
+ <p><em>It is crucial to me that this software be easy to use - in fact it should
+ be as intuitive as possible. </em></p>
+ <p><em>I'm committed to continuing my work on Moodle and on keeping it Open
+ and Free. I have a deeply-held belief in the importance of unrestricted education
+ and empowered teaching, and Moodle is the main way I can contribute to the
+ realisation of these ideals.</em></p>
+ </blockquote>
+ <p>A number of early prototypes were produced and discarded before he released
+ version 1.0 upon a largely unsuspecting world on August 20, 2002. This version
+ was targeted towards smaller, more intimate classes at University level, and
+ was the subject of research case studies that closely analysed the nature of
+ collaboration and reflection that occurred among these small groups of adult
+ participants.
+</p>
+ <p>Since then there has been steady series of new releases adding new features,
+ better scalability and improved performance.
+</p>
+ <p>As Moodle has spread and the community has grown, more input is being drawn
+ from a wider variety of people in different teaching situations. For example,
+ Moodle is now used not only in Universities, but in high schools, primary schools,
+ non-profit organisations, private companies, by independent teachers and even
+ homeschooling parents. A growing number of people from around the world are
+ contributing to Moodle in different ways - for more details see the <a href="?file=credits.html">Credits</a>
+ page.
+</p>
+ <p>An important feature of the Moodle project is the <a href="http://moodle.org" target="_top">moodle.org</a>
+ web site, which provides a central point for information, discussion and collaboration
+ among Moodle users, who include system administrators, teachers, researchers,
+ instructional designers and of course, developers. Like Moodle, this site is
+ always evolving to suit the needs of the community, and like Moodle it will
+ always be Free.
+</p>
+ <p>In 2003, the company <a href="http://moodle.com/" target="_top">moodle.com</a>
+ was launched to provide additional commercial support for those need it, as
+ well as managed hosting, consulting and other services.
+</p>
+ <p>For more about our future plans for Moodle, see the <a href="?file=future.html">Future</a>
+ roadmap.</p>
+</blockquote>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+
+</body>
+</html>
-<html>\r
-<head>\r
-<title>Moodle Docs: Coding Guidelines</title>\r
-<link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
-<style type="text/css">\r
-\r
-<!--\r
-li {\r
- padding-top: 10px;\r
-}\r
-\r
-.question {\r
-\r
- font-size: medium;\r
-\r
- font-weight: bold;\r
-\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
-\r
- border: 1px dotted;\r
-\r
- padding: 10px;\r
-\r
- background-color: #EEEEEE;\r
-\r
-}\r
-\r
-.answer {\r
-\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
-\r
- font-size: medium;\r
-\r
- border: none;\r
-\r
- padding-left: 40px;\r
-\r
-}\r
-\r
--->\r
-\r
-</style>\r
-<style type="text/css">\r
-\r
-<!--\r
-\r
-.normaltext {\r
-\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
-\r
- font-size: medium;\r
-\r
- border: none;\r
-\r
- padding-left: 10px;\r
-\r
-}\r
-\r
-.answercode {\r
-\r
- font-family: "Courier New", Courier, mono;\r
-\r
- font-size: small;\r
-\r
- border: none;\r
-\r
- padding-left: 60px;\r
-\r
-}\r
-\r
-.questionlink {\r
-\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
-\r
- font-size: medium;\r
-\r
- border: none;\r
-\r
- padding-left: 40px;\r
-\r
-}\r
-\r
--->\r
-\r
-</style>\r
-<style type="text/css">\r
-<!--\r
-.examplecode {\r
- font-family: "Courier New", Courier, mono;\r
- font-size: small;\r
- border: thin dashed #999999;\r
- background-color: #FBFBFB;\r
- margin: auto;\r
- padding: 30px;\r
- height: auto;\r
- width: auto;\r
-}\r
--->\r
-</style>\r
-</head>\r
-<body bgcolor="#FFFFFF">\r
-<h2>Moodle Coding Guidelines</h2>\r
-<p class="normaltext">Any collaborative project needs consistency and stability \r
- to stay strong.</p>\r
-<p class="normaltext">These guidelines are to provide a goal for all Moodle code \r
- to strive to. It's true that some of the older existing code falls short in \r
- a few areas, but it will all be fixed eventually. All new code definitely must \r
- adhere to these standards as closely as possible.</p>\r
-<h2 class="normaltext">General Rules</h2>\r
-<ol class="normaltext">\r
- <li>All code files should use the .php extension.</li>\r
- <li>All template files should use the .html extension.</li>\r
- <li>All text files should use Unix-style text format (most text editors have \r
- this as an option).</li>\r
- <li>All php tags should be 'full' tags like <font color="#339900"><?php</font> \r
- - short tags are not allowed. </li>\r
- <li>All existing copyright notices must be retained. You can add your own if \r
- necessary.</li>\r
- <li>Each file should include the main config.php file.</li>\r
- <li>Each file should check that the user is authenticated correctly, using require_login() \r
- and isadmin(), isteacher(), iscreator() or isstudent().</li>\r
- <li>All access to databases should use the functions in lib/datalib.php whenever \r
- possible - this allows compatibility across a wide range of databases. You \r
- should find that almost anything is possible using these functions. Any other \r
- SQL statements should be: cross-platform; restricted to specific functions \r
- within your code (usally a lib.php file); and clearly marked.</li>\r
- <li>Don't create or use global variables except for the standard $CFG, $SESSION, \r
- $THEME and $USER.</li>\r
- <li>All variables should be initialised or at least tested for existence using \r
- isset() or empty() before they are used.</li>\r
- <li>All strings should be translatable - create new texts in the "lang/en" \r
- files and call them using get_string() or print_string().</li>\r
- <li>All help files should be translatable - create new texts in the "en/help" \r
- directory and call them using helpbutton().</li>\r
-</ol>\r
-<p> </p>\r
-<h2 class="normaltext">Coding Style</h2>\r
-<p class="normaltext">I know it can be a little annoying to change your style \r
- if you're used to something else, but balance that annoyance against the annoyance \r
- of all the people trying later on to make sense of Moodle code with mixed styles. \r
- There are obviously many good points for and against any style that people use, \r
- but the current style just <strong>is</strong>, so please stick to it. </p>\r
-<ol class="normaltext">\r
- <li><strong>Indenting</strong> should be consistently 4 spaces. Don't use tabs \r
- AT ALL. </li>\r
- <li><strong>Variable names</strong> should always be easy-to-read, meaningful \r
- lowercase English words. If you really need more than one word then run them \r
- together, but keep them short as possible. \r
- <p class="examplecode"><font color="#006600">GOOD: $quiz<br>\r
- GOOD: $errorstring<br>\r
- GOOD: $i (but only in little loops)<br>\r
- <br />\r
- BAD: $Quiz <br>\r
- BAD: $aReallyLongVariableNameWithoutAGoodReason<br>\r
- BAD: $error_string</font></p>\r
- </li>\r
- <li><strong>Constants</strong> should always be in upper case, and always start \r
- with the name of the module. They should have words separated by underscores. \r
- <p class="examplecode"><font color="#006600">define("FORUM_MODE_FLATOLDEST", \r
- 1);</font></p>\r
- </li>\r
- <li><strong>Function names</strong> should be simple English words, and start \r
- with the name of the module to avoid conflicts between modules. Words should \r
- be separated by underscores. Parameters should always have sensible defaults \r
- if possible. Note there is no space between the function name and the following \r
- (brackets). <br>\r
- <p class="examplecode"> <font color="#007700">function </font><font color="#0000BB">forum_set_display_mode</font><font color="#007700">(</font><font color="#0000BB">$mode</font><font color="#007700">=</font><font color="#0000BB">0</font><font color="#007700">) \r
- {<br />\r
- global </font><font color="#0000BB">$USER</font><font color="#007700">, \r
- </font><font color="#0000BB">$CFG</font><font color="#007700">;<br />\r
- <br />\r
- if (</font><font color="#0000BB">$mode</font><font color="#007700">) \r
- {<br />\r
- </font><font color="#0000BB">$USER</font><font color="#007700">-></font><font color="#0000BB">mode \r
- </font><font color="#007700">= </font><font color="#0000BB">$mode</font><font color="#007700">;<br />\r
- } else if (empty(</font><font color="#0000BB">$USER</font><font color="#007700">-></font><font color="#0000BB">mode</font><font color="#007700">)) \r
- {<br />\r
- </font><font color="#0000BB">$USER</font><font color="#007700">-></font><font color="#0000BB">mode \r
- </font><font color="#007700">= </font><font color="#0000BB">$CFG</font><font color="#007700">-></font><font color="#0000BB">forum_displaymode</font><font color="#007700">;<br />\r
- }<br />\r
- }</font></p>\r
- </li>\r
- <li><strong>Blocks</strong> must always be enclosed in curly braces (even if \r
- there is only one line). Moodle uses this style: \r
- <p class="examplecode"> <font color="#006600">if (</font><font color="#0000CC">$quiz</font><font color="#006600">-></font><font color="#0000CC">attempts</font><font color="#006600">) \r
- {<br />\r
- if (</font><font color="#0000CC">$numattempts </font><font color="#006600">> \r
- </font><font color="#0000CC">$quiz</font><font color="#006600">-></font><font color="#0000CC">attempts</font><font color="#006600">) \r
- {<br />\r
- </font><font color="#0000CC">error</font><font color="#006600">(</font><font color="#0000BB">$strtoomanyattempts</font><font color="#006600">, \r
- </font><font color="#CC0000">"view.php?id=$cm</font><font color="#006600">-></font><font color="#CC0000">id"</font><font color="#006600">);<br />\r
- }<br />\r
- }</font></p>\r
- </li>\r
- <li><strong>Strings</strong> should be defined using single quotes where possible, \r
- for increased speed.<br>\r
- <p class="examplecode"> <font color="#006600">$var = 'some text without any \r
- variables';<br>\r
- $var = "with special characters like a new line \n";<br>\r
- $var = 'a very, very long string with a '.$single.' variable in it';<br>\r
- $var = "some $text with $many variables $within it"; </font></p>\r
- </li>\r
- <li><strong>Comments</strong> should use two or three slashes and line up nicely \r
- with the code. \r
- <p class="examplecode"><font color="#006600">function </font><font color="#0000BB">forum_get_ratings_mean</font><font color="#007700">(</font><font color="#0000BB">$postid</font><font color="#007700">, \r
- </font><font color="#0000BB">$scale</font><font color="#007700">, </font><font color="#0000BB">$ratings</font><font color="#007700">=</font><font color="#0000BB">NULL</font><font color="#007700">) \r
- {<br />\r
- </font><font color="#FF8000">/// Return the mean rating of a post given \r
- to the current user by others.<br />\r
- /// Scale is an array of possible ratings in the scale<br />\r
- /// Ratings is an optional simple array of actual ratings (just integers)<br />\r
- <br />\r
- </font><font color="#007700">if (!</font><font color="#0000BB">$ratings</font><font color="#007700">) \r
- {<br />\r
- </font><font color="#0000BB">$ratings \r
- </font><font color="#007700">= array(); </font><font color="#FF8000">// \r
- Initialize the empty array</font><font color="#007700"><br />\r
- if (</font><font color="#0000BB">$rates \r
- </font><font color="#007700">= </font><font color="#0000BB">get_records</font><font color="#007700">(</font><font color="#DD0000">"forum_ratings"</font><font color="#007700">, \r
- </font><font color="#DD0000">"post"</font><font color="#007700">, </font><font color="#0000BB">$postid</font><font color="#007700">)) \r
- {<br>\r
- </font><font color="#FF8000">// \r
- Process each rating in turn</font><font color="#007700"><br />\r
- foreach \r
- (</font><font color="#0000BB">$rates </font><font color="#007700">as </font><font color="#0000BB">$rate</font><font color="#007700">) \r
- {</font> <br>\r
- ....etc </p>\r
- </li>\r
- <li><strong>Space</strong> should be used liberally - don't be afraid to spread \r
- things out a little to gain some clarity. Generally, there should be one space \r
- between brackets and normal statements, but no space between brackets and \r
- variables or functions:<br>\r
- <p class="examplecode"> <font color="#007700">foreach (</font><font color="#0000BB">$objects \r
- </font><font color="#007700">as </font><font color="#0000BB">$key </font><font color="#007700">=></font><font color="#0000BB"> \r
- $thing</font><font color="#007700">)</font><font color="#006600"> {<br>\r
- </font><font color="#007700"> </font><font color="#0000BB">process($thing);</font><font color="#006600"> \r
- <br>\r
- } <br>\r
- <br>\r
- </font><font color="#007700">if (</font><font color="#0000BB">$x </font><font color="#007700">== \r
- </font><font color="#0000BB">$y</font><font color="#007700">)</font><font color="#006600"> \r
- {<br>\r
- </font><font color="#007700"> </font><font color="#0000BB">$a \r
- </font><font color="#007700">= </font><font color="#0000BB">$b</font><font color="#007700">;</font><font color="#006600"><br>\r
- } else if (</font><font color="#0000BB">$x </font><font color="#007700">== \r
- </font><font color="#0000BB">$z</font><font color="#006600">) {<br>\r
- </font><font color="#007700"> </font><font color="#0000BB">$a \r
- </font><font color="#007700">= </font><font color="#0000BB">$c</font><font color="#007700">;</font><font color="#006600"><br>\r
- } else {<br>\r
- </font><font color="#007700"> </font><font color="#0000BB">$a \r
- </font><font color="#007700">= </font><font color="#0000BB">$d</font><font color="#007700">;</font><font color="#006600"><br>\r
- } </font></p>\r
- </li>\r
-</ol>\r
-<p align="center" class="normaltext"> </p>\r
-<hr>\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: faq.html,v 1.6 2003/03/30 13:54:28 \r
- moodler Exp $</font></p>\r
-</body>\r
-</html>\r
+<html>
+<head>
+<title>Moodle Docs: Coding Guidelines</title>
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body bgcolor="#FFFFFF">
+<h1>Moodle Coding Guidelines</h1>
+<p class="normaltext">Any collaborative project needs consistency and stability
+ to stay strong.</p>
+<p class="normaltext">These guidelines are to provide a goal for all Moodle code
+ to strive to. It's true that some of the older existing code falls short in
+ a few areas, but it will all be fixed eventually. All new code definitely must
+ adhere to these standards as closely as possible.</p>
+<h2>General Rules</h2>
+<ol class="normaltext">
+ <li class="spaced">All code files should use the .php extension.</li>
+ <li class="spaced">All template files should use the .html extension.</li>
+ <li class="spaced">All text files should use Unix-style text format (most text
+ editors have this as an option).</li>
+ <li class="spaced">All php tags must be 'full' tags like <font color="#339900"><?php
+ ?></font> ... not 'short' tags like <font color="#339900"><? ?></font>.
+ </li>
+ <li class="spaced">All existing copyright notices must be retained. You can
+ add your own if necessary.</li>
+ <li class="spaced">Each file should include the main config.php file.</li>
+ <li class="spaced">Each file should check that the user is authenticated correctly,
+ using require_login() and isadmin(), isteacher(), iscreator() or isstudent().</li>
+ <li class="spaced">All access to databases should use the functions in lib/datalib.php
+ whenever possible - this allows compatibility across a wide range of databases.
+ You should find that almost anything is possible using these functions. Any
+ other SQL statements should be: cross-platform; restricted to specific functions
+ within your code (usally a lib.php file); and clearly marked.</li>
+ <li class="spaced">Don't create or use global variables except for the standard
+ $CFG, $SESSION, $THEME and $USER.</li>
+ <li class="spaced">All variables should be initialised or at least tested for
+ existence using isset() or empty() before they are used.</li>
+ <li class="spaced">All strings should be translatable - create new texts in
+ the "lang/en" files and call them using get_string() or print_string().</li>
+ <li class="spaced">All help files should be translatable - create new texts
+ in the "en/help" directory and call them using helpbutton().</li>
+</ol>
+<p> </p>
+<h2>Coding Style</h2>
+<p class="normaltext">I know it can be a little annoying to change your style
+ if you're used to something else, but balance that annoyance against the annoyance
+ of all the people trying later on to make sense of Moodle code with mixed styles.
+ There are obviously many good points for and against any style that people use,
+ but the current style just <strong>is</strong>, so please stick to it. </p>
+<ol class="normaltext">
+ <li class="spaced"><strong>Indenting</strong> should be consistently 4 spaces.
+ Don't use tabs AT ALL. </li>
+ <li class="spaced"><strong>Variable names</strong> should always be easy-to-read,
+ meaningful lowercase English words. If you really need more than one word
+ then run them together, but keep them short as possible.
+ <p class="examplecode"><font color="#006600">GOOD: $quiz<br>
+ GOOD: $errorstring<br>
+ GOOD: $i (but only in little loops)<br>
+ <br />
+ BAD: $Quiz <br>
+ BAD: $aReallyLongVariableNameWithoutAGoodReason<br>
+ BAD: $error_string</font></p>
+ </li>
+ <li class="spaced"><strong>Constants</strong> should always be in upper case,
+ and always start with the name of the module. They should have words separated
+ by underscores.
+ <p class="examplecode"><font color="#006600">define("FORUM_MODE_FLATOLDEST",
+ 1);</font></p>
+ </li>
+ <li class="spaced"><strong>Function names</strong> should be simple English
+ words, and start with the name of the module to avoid conflicts between modules.
+ Words should be separated by underscores. Parameters should always have sensible
+ defaults if possible. Note there is no space between the function name and
+ the following (brackets). <br>
+ <p class="examplecode"> <font color="#007700">function </font><font color="#0000BB">forum_set_display_mode</font><font color="#007700">(</font><font color="#0000BB">$mode</font><font color="#007700">=</font><font color="#0000BB">0</font><font color="#007700">)
+ {<br />
+ global </font><font color="#0000BB">$USER</font><font color="#007700">,
+ </font><font color="#0000BB">$CFG</font><font color="#007700">;<br />
+ <br />
+ if (</font><font color="#0000BB">$mode</font><font color="#007700">)
+ {<br />
+ </font><font color="#0000BB">$USER</font><font color="#007700">-></font><font color="#0000BB">mode
+ </font><font color="#007700">= </font><font color="#0000BB">$mode</font><font color="#007700">;<br />
+ } else if (empty(</font><font color="#0000BB">$USER</font><font color="#007700">-></font><font color="#0000BB">mode</font><font color="#007700">))
+ {<br />
+ </font><font color="#0000BB">$USER</font><font color="#007700">-></font><font color="#0000BB">mode
+ </font><font color="#007700">= </font><font color="#0000BB">$CFG</font><font color="#007700">-></font><font color="#0000BB">forum_displaymode</font><font color="#007700">;<br />
+ }<br />
+ }</font></p>
+ </li>
+ <li class="spaced"><strong>Blocks</strong> must always be enclosed in curly
+ braces (even if there is only one line). Moodle uses this style:
+ <p class="examplecode"> <font color="#006600">if (</font><font color="#0000CC">$quiz</font><font color="#006600">-></font><font color="#0000CC">attempts</font><font color="#006600">)
+ {<br />
+ if (</font><font color="#0000CC">$numattempts </font><font color="#006600">>
+ </font><font color="#0000CC">$quiz</font><font color="#006600">-></font><font color="#0000CC">attempts</font><font color="#006600">)
+ {<br />
+ </font><font color="#0000CC">error</font><font color="#006600">(</font><font color="#0000BB">$strtoomanyattempts</font><font color="#006600">,
+ </font><font color="#CC0000">"view.php?id=$cm</font><font color="#006600">-></font><font color="#CC0000">id"</font><font color="#006600">);<br />
+ }<br />
+ }</font></p>
+ </li>
+ <li class="spaced"><strong>Strings</strong> should be defined using single quotes
+ where possible, for increased speed.<br>
+ <p class="examplecode"> <font color="#006600">$var = 'some text without any
+ variables';<br>
+ $var = "with special characters like a new line \n";<br>
+ $var = 'a very, very long string with a '.$single.' variable in it';<br>
+ $var = "some $text with $many variables $within it"; </font></p>
+ </li>
+ <li class="spaced"><strong>Comments</strong> should use two or three slashes
+ and line up nicely with the code.
+ <p class="examplecode"><font color="#006600">function </font><font color="#0000BB">forum_get_ratings_mean</font><font color="#007700">(</font><font color="#0000BB">$postid</font><font color="#007700">,
+ </font><font color="#0000BB">$scale</font><font color="#007700">, </font><font color="#0000BB">$ratings</font><font color="#007700">=</font><font color="#0000BB">NULL</font><font color="#007700">)
+ {<br />
+ </font><font color="#FF8000">/// Return the mean rating of a post given
+ to the current user by others.<br />
+ /// Scale is an array of possible ratings in the scale<br />
+ /// Ratings is an optional simple array of actual ratings (just integers)<br />
+ <br />
+ </font><font color="#007700">if (!</font><font color="#0000BB">$ratings</font><font color="#007700">)
+ {<br />
+ </font><font color="#0000BB">$ratings
+ </font><font color="#007700">= array(); </font><font color="#FF8000">//
+ Initialize the empty array</font><font color="#007700"><br />
+ if (</font><font color="#0000BB">$rates
+ </font><font color="#007700">= </font><font color="#0000BB">get_records</font><font color="#007700">(</font><font color="#DD0000">"forum_ratings"</font><font color="#007700">,
+ </font><font color="#DD0000">"post"</font><font color="#007700">, </font><font color="#0000BB">$postid</font><font color="#007700">))
+ {<br>
+ </font><font color="#FF8000">//
+ Process each rating in turn</font><font color="#007700"><br />
+ foreach
+ (</font><font color="#0000BB">$rates </font><font color="#007700">as </font><font color="#0000BB">$rate</font><font color="#007700">)
+ {</font> <br>
+ ....etc </p>
+ </li>
+ <li class="spaced"><strong>Space</strong> should be used liberally - don't be
+ afraid to spread things out a little to gain some clarity. Generally, there
+ should be one space between brackets and normal statements, but no space between
+ brackets and variables or functions:<br>
+ <p class="examplecode"> <font color="#007700">foreach (</font><font color="#0000BB">$objects
+ </font><font color="#007700">as </font><font color="#0000BB">$key </font><font color="#007700">=></font><font color="#0000BB">
+ $thing</font><font color="#007700">)</font><font color="#006600"> {<br>
+ </font><font color="#007700"> </font><font color="#0000BB">process($thing);</font><font color="#006600">
+ <br>
+ } <br>
+ <br>
+ </font><font color="#007700">if (</font><font color="#0000BB">$x </font><font color="#007700">==
+ </font><font color="#0000BB">$y</font><font color="#007700">)</font><font color="#006600">
+ {<br>
+ </font><font color="#007700"> </font><font color="#0000BB">$a
+ </font><font color="#007700">= </font><font color="#0000BB">$b</font><font color="#007700">;</font><font color="#006600"><br>
+ } else if (</font><font color="#0000BB">$x </font><font color="#007700">==
+ </font><font color="#0000BB">$z</font><font color="#006600">) {<br>
+ </font><font color="#007700"> </font><font color="#0000BB">$a
+ </font><font color="#007700">= </font><font color="#0000BB">$c</font><font color="#007700">;</font><font color="#006600"><br>
+ } else {<br>
+ </font><font color="#007700"> </font><font color="#0000BB">$a
+ </font><font color="#007700">= </font><font color="#0000BB">$d</font><font color="#007700">;</font><font color="#006600"><br>
+ } </font></p>
+ </li>
+</ol>
+<p align="center" class="normaltext"> </p>
+<hr>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
-<!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
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
-</head>\r
-<body bgcolor="#ffffff">\r
- \r
-<h2>Credits</h2>\r
- \r
-<p><b>Moodle </b>the package is Copyright © 2001-2003, <a target=_top href="http://dougiamas.com/"> \r
- Martin Dougiamas</a>. It is distributed under the <a href="?file=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\r
-</ul>\r
-\r
-\r
-\r
-<h3><br>Translations</h3>\r
-<blockquote> \r
- <p>Many thanks to every person who has contributed to translating Moodle into \r
- different languages. Each translation takes many hours of work, as there are \r
- over 1000 phrases to translate (plus all the help files!). Many of the languages \r
- have more than one contributor, sometimes working together and sometimes they've \r
- taken over the work from a previous person. \r
- <p>Maintaining a list of everyone here is too difficult. For the most up-to-date \r
- information see the <a target=_top href="http://moodle.org/download/lang/">Language \r
- download page</a>. </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 target=_top href="http://mitstek.com">http://mitstek.com</a>\r
- <li><b>brightretro</b>, by Thomas Murdock, <a target=_top href="http://sand-paper.org/">http://sand-paper.org</a>\r
- <li><b>garden</b>, by Spiggy, <a target=_top 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.org/donations">Donations page</a>,\r
- <li>contributed to the <a target=_top href="http://moodle.org/bugs">bug tracker</a>, and\r
- <li>participated in the <a target=_top href="http://moodle.org/community">Moodle Community</a>\r
-</ul>\r
-<p></p>\r
-\r
-<p>Special thanks to those who have contributed substantial amounts of time to helping with Moodle code, including:\r
- <ul>\r
- Petri Asikainen, \r
- Ray Kingdon,\r
- Eloy Lafuente,\r
- Henrik Kaipe,\r
- Williams Castillo,\r
- Russell Jungwirth.\r
- </ul>\r
-<p></p>\r
-\r
- <p>Also, thanks to those of you who have at some time contributed with constructive \r
- discussions, support, testing and bits of code. This list is long and always \r
- changing, but some names include (in the order I added them): \r
- <ul>\r
- Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin \r
- Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro \r
- Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Przemyslaw Stencel, Roberto Pinna (Bobo), \r
- John "Captain" Eyre, Paula Edmiston, Scott Elliott, Howard Miller, Claudio Tavares, \r
- Zbigniew Fiedorowicz, P. Timothy Ervin, Bob Calder, Ursula Raab, Thomas Robb, \r
- David Delgado, Mad Alex, Gustav Delius.\r
- </ul>\r
- <p>I apologise if I've forgotten to include your name here - it's very difficult \r
- to maintain! Mail me (Martin) and gently remind me! :-) </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 redistributed \r
- as part of Moodle under their respective open source licenses that thankfully \r
- allow us to do so. My thanks go out to the authors of all these excellent \r
- products - without them Moodle would be missing important functionality. Copyright \r
- 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: 3.60<br>\r
- Copyright © 2000-2003 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
-\r
- <p><b>PclZip</b> - lib/pclzip</p>\r
- \r
- <blockquote>Class to create, manage and unpack zip files.<br>\r
- <br>\r
- Version: 2.0 RC2<br>\r
- Copyright © 2003 Vincent Blavet <vincent@phpconcept.net><br>\r
- License: GNU GPL<br>\r
- URL: <a href="http://www.phpconcept.net" target="newpage">http://www.phpconcept.net</a><br>\r
- </blockquote>\r
-\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.71,<br>\r
- Copyright © 2003 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>Spreadsheet::WriteExcel</b> - lib/excel</p>\r
-\r
- <blockquote>A library for generating Excel Spreadsheets.<br>\r
- <br>\r
- Version: 2002-11-28<br>\r
- Copyright © 2002 Xavier Noguer <xnoguer@rezebra.com><br>\r
- License: GNU LGPL<br>\r
- URL: <a href="http://jeffn.users.phpclasses.org/browse.html/package/767.html" target="newpage">http://jeffn.users.phpclasses.org/browse.html/package/767.html</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
- </blockquote>\r
-</body>\r
-</html>\r
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<title>Moodle Docs: Credits</title>
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body bgcolor="#ffffff">
+<h1>Credits</h1>
+<blockquote>
+ <p><b>Moodle </b>the package is Copyright © 2001-2003, <a target=_top href="http://dougiamas.com/">
+ Martin Dougiamas</a>. It is distributed under the <a href="?file=licence.html">
+ GNU Public License</a>.</p>
+ <h2>Special thanks</h2>
+ <blockquote>
+ <p><b><a target=_top href="http://pctaylor.com">Dr Peter C. Taylor</a></b>, at
+ Curtin University of Technology in Perth, Australia, for working with the earliest
+ prototypes and making many useful suggestions along the way
+</p>
+ </blockquote>
+ <h2>Translations</h2>
+ <blockquote>
+ <p>Many thanks to every person who has contributed to translating Moodle into
+ different languages. Each translation takes many hours of work, as there are
+ over 1000 phrases to translate (plus all the help files!). Many of the languages
+ have more than one contributor, sometimes working together and sometimes they've
+ taken over the work from a previous person.
+ </p>
+ <p>Maintaining a list of everyone here is too difficult. For the most up-to-date
+ information see the <a target=_top href="http://moodle.org/download/lang/">Language
+ download page</a>. </p>
+ </blockquote>
+ <h2>Themes</h2>
+ <blockquote>
+ <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:
+ </p>
+ <ul>
+ <li><b>standard* and cordoroyblue</b>, by Martin Dougiamas
+ </li>
+ <li><b>oceanblue</b>, by Mitsuhiro Yoshida, <a target=_top href="http://mitstek.com">http://mitstek.com</a>
+ </li>
+ <li><b>brightretro</b>, by Thomas Murdock, <a target=_top href="http://sand-paper.org/">http://sand-paper.org</a>
+ </li>
+ <li><b>garden</b>, by Spiggy, <a target=_top href="http://phpgirl.com">http://phpgirl.com</a>
+ </li>
+ </ul>
+ </blockquote>
+ <h2>Other contributors</h2>
+ <blockquote>
+ <p>Thanks to all of you who have
+ </p>
+ <ul>
+ <li>donated via the <a target=_top href="http://moodle.org/donations">Donations
+ page</a>,
+ </li>
+ <li>contributed to the <a target=_top href="http://moodle.org/bugs">bug tracker</a>,
+ and
+ </li>
+ <li>participated in the <a target=_top href="http://moodle.org/community">Moodle
+ Community</a>
+ </li>
+ </ul>
+ <p> </p>
+ <p>Special thanks to those who have contributed substantial amounts of time
+ to helping with Moodle code, including:
+ </p>
+ <blockquote>
+ <p>
+ Petri Asikainen, Ray Kingdon, Eloy Lafuente, Henrik Kaipe, Williams Castillo,
+ Russell Jungwirth.
+ </p>
+ </blockquote>
+ <p> </p>
+ <p>Also, thanks to those of you who have at some time contributed with constructive
+ discussions, support, testing and bits of code. This list is long and always
+ changing, but some names include (in the order I added them):
+ </p>
+ <blockquote>
+ <p>
+ Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin
+ Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro
+ Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Przemyslaw Stencel, Roberto
+ Pinna (Bobo), John "Captain" Eyre, Paula Edmiston, Scott Elliott, Howard Miller,
+ Claudio Tavares, Zbigniew Fiedorowicz, P. Timothy Ervin, Bob Calder, Ursula
+ Raab, Thomas Robb, David Delgado, Mad Alex, Gustav Delius.
+ </p>
+ </blockquote>
+ <p>I apologise if I've forgotten to include your name here - it's very difficult
+ to maintain! Mail me (Martin) and gently remind me! :-) </p>
+ </blockquote>
+ <h2>Moodle libraries</h2>
+ <blockquote>
+ <p>Some of Moodle's libraries were written by other people, and are being redistributed
+ as part of Moodle under their respective open source licenses that thankfully
+ allow us to do so. My thanks go out to the authors of all these excellent
+ products - without them Moodle would be missing important functionality. Copyright
+ information for each package is included below:</p>
+ <p><b>ADOdb </b>- lib/adodb</p>
+ <blockquote>
+ <p>Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase,
+ Foxpro, Access, ADO, Sybase, DB2 and ODBC.</p>
+ <p>Version: 3.60<br>
+ Copyright © 2000-2003 John Lim (jlim@natsoft.com.my)<br>
+ License: Dual LGPL and BSD-style<br>
+ URL: <a href="http://php.weblogs.com/adodb" target="newpage">http://php.weblogs.com/adodb</a><br>
+ </p>
+ </blockquote>
+ <p><b>Graph Class</b> - lib/graphlib.php </p>
+ <blockquote>
+ <p>Class to draw line, point, bar, and area graphs, including numeric x-axis
+ and double y-axis.</p>
+ <p> Version: 1.6.3 (with modifications)<br>
+ Copyright © 2000 Herman Veluwenkamp, hermanV@mindless.com<br>
+ License: LGPL<br>
+ </p>
+ </blockquote>
+ <p><b>IP-Atlas</b> - lib/ipatlas</p>
+ <blockquote>
+ <p>PHP scripts to show the location of an IP address on a map.<br>
+ <br>
+ Version: 1.0 (with modifications)<br>
+ Copyright © 2002 Ivan Kozik<br>
+ License: GNU GPL<br>
+ URL: <a href="http://www.xpenguin.com/ip-atlas.php" target="newpage">http://www.xpenguin.com/ip-atlas.php</a><br>
+ </p>
+ </blockquote>
+ <p><b>PclZip</b> - lib/pclzip</p>
+ <blockquote>
+ <p>Class to create, manage and unpack zip files.<br>
+ <br>
+ Version: 2.0 RC2<br>
+ Copyright © 2003 Vincent Blavet <vincent@phpconcept.net><br>
+ License: GNU GPL<br>
+ URL: <a href="http://www.phpconcept.net" target="newpage">http://www.phpconcept.net</a><br>
+ </p>
+ </blockquote>
+ <p><b>PHP mailer</b> - lib/class.phpmailer.php</p>
+ <blockquote>
+ <p>Class for sending email using either sendmail, PHP mail(), or SMTP.
+ Methods are based upon the standard AspEmail(tm) classes.<br>
+ <br>
+ Version 1.71,<br>
+ Copyright © 2003 Brent R. Matzelle <bmatzelle@yahoo.com><br>
+ License: LGPL<br>
+ URL: <a href="http://phpmailer.sourceforge.net" target="newpage">http://phpmailer.sourceforge.net</a><br>
+ </p>
+ </blockquote>
+ <p><b>Spreadsheet::WriteExcel</b> - lib/excel</p>
+ <blockquote>
+ <p>A library for generating Excel Spreadsheets.<br>
+ <br>
+ Version: 2002-11-28<br>
+ Copyright © 2002 Xavier Noguer <xnoguer@rezebra.com><br>
+ License: GNU LGPL<br>
+ URL: <a href="http://jeffn.users.phpclasses.org/browse.html/package/767.html" target="newpage">http://jeffn.users.phpclasses.org/browse.html/package/767.html</a><br>
+ </p>
+ </blockquote>
+ <p><b>Richtext Editor</b> - lib/rte</p>
+ <blockquote>
+ <p>HTML text editor for embedding in web pages.<br>
+ <br>
+ Version: 0.30 beta 1 (plus modifications)<br>
+ Copyright © 2001 Ramesys (Contracting Services) Limited <Austin.France@Ramesys.com>
+ License: GNU LGPL<br>
+ URL: <a href="http://richtext.sourceforge.net" target="newpage">http://richtext.sourceforge.net</a><br>
+ </p>
+ </blockquote>
+ <p><b>SMTP class </b>- lib/class.smtp.php</p>
+ <blockquote>
+ <p>Class that can be used to connect and communicate with any SMTP
+ server. <br>
+ It implements all the SMTP functions defined in RFC821 except TURN.<br>
+ <br>
+ Version: 03/26/2001 <br>
+ Copyright © 2001 Chris Ryan <chris@greatbridge.com></p>
+ <p><br>
+ </p>
+ </blockquote>
+ </blockquote>
+
+ <p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+ <p align="CENTER"><font size="1">Version: $Id$</font></p>
+</blockquote>
+</body>
+</html>
-<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
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
- <!--\r
- .sectionheading {\r
- font-size: medium;\r
- font-weight: bold;\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- border: 1px dotted;\r
- padding: 10px;\r
- background-color: #EEEEEE;\r
- }\r
- -->\r
- </style>\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 the case of Moodle, at <a target="_top" href="http://www.sf.net/">Sourceforge</a>). \r
- </p>\r
- <p>If you just want to access the current CVS version of Moodle with read-only access then \r
- you don't need this page - just follow the simpler CVS instructions on the <a target="_top" href="http://moodle.org/download">Moodle download page</a>.</p>\r
-\r
- <p>To use <a target="_top" href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/">Moodle's \r
- CVS archive</a> (as a <a target="_top" 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>. Take special note of the \r
- sourceforge instructions to <a target="_top" href="http://sourceforge.net/docman/display_doc.php?docid=768&group_id=1#develhomedir">create your CVS home directory</a> - something you have to\r
- do with every new account to "enable" it for CVS. Basically you just have to use ssh to interactively connect to cvs.sourceforge.net.</p>\r
- \r
- <p>Once you have \r
- a working Sourceforge account, contact <a \r
- target="_top" href="http://moodle.org/user/view.php?id=1&course=1">Martin Dougiamas</a> so he can give you write access \r
- to particular Moodle directories.</p>\r
-\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 target="_top" 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 class="sectionheading">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 target="_top" 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 class="sectionheading">2. Using CVS on Windows</h3>\r
- <blockquote> \r
- <p>First, you need to download a completely fresh copy of Moodle using your \r
- developer account.</p>\r
- <blockquote> \r
- <p> 1. Get TortoiseCVS from <a target="_top" href="http://www.tortoisecvs.org/">tortoisecvs.org</a> \r
- and install it, then reboot.<br>\r
- <br>\r
- 2. Find or create a new folder somewhere where you want Moodle to be downloaded \r
- to.<br>\r
- <br>\r
- 3. Right-mouse-click that folder and choose "<strong>CVS Checkout</strong>" \r
- from the menu. You should see a dialog box.<br>\r
- <br>\r
- 4. Copy this text into the CVSROOT field (using your own username!):</p>\r
- <blockquote> \r
- <pre> :ext:<font color="#990000">myusername</font>@cvs.moodle.sourceforge.net:/cvsroot/moodle</pre>\r
- </blockquote>\r
- <p><br>\r
- 5. Press the button: "<strong>Fetch list...</strong>".<br>\r
- <br>\r
- 6. To the right of the button you should see a list of modules: choose \r
- "<strong>moodle</strong>" from that list.<br>\r
- <br>\r
- 7. Press the button: "<strong>OK</strong>" and everything should \r
- be downloaded.<br>\r
- </p>\r
- </blockquote>\r
- <p>A dialog box should show all the files being downloaded, and after a while \r
- you should have a complete copy of Moodle. After this first checkout, you \r
- can fetch the latest updated files from the CVS server:</p>\r
- <blockquote> \r
- <p> 1. Right-mouse-click on your Moodle folder (or any file) and select \r
- "<strong>CVS Update</strong>". <br>\r
- </p>\r
- </blockquote>\r
- <p>After modifying files (you will note they change from green top red!), \r
- you can commit them back to the CVS server like this:</p>\r
- <blockquote> \r
- <p> 1. Right-mouse-click on your Moodle folder (or any file) and select \r
- "<strong>CVS Commit...</strong>".<br>\r
- <br>\r
- 2. In the dialog box, type a clear description of the changes you are \r
- committing. <br>\r
- <br>\r
- 3. Click "OK". Your changes will be sent to the server.<br>\r
- </p>\r
- </blockquote>\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$</font></p>\r
-</body>\r
-</html>\r
+<html>
+<head>
+<title>Moodle Docs: How to use CVS</title>
+ <link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body bgcolor="#ffffff">
+<h1>Using CVS to access and update Moodle source code</h1>
+<blockquote>
+ <p>CVS is the Concurrent Versioning System. It's a commonly used way of storing
+ source code because it keeps versions of all files so that nothing is ever
+ lost, and usage by different people is tracked. It also provides ways to merge
+ code if two or more people are working on the same file. All code and all
+ versions are stored on a central server (in the case of Moodle, at <a target="_top" href="http://www.sf.net/">Sourceforge</a>).
+ </p>
+ <p>If you just want to access the current CVS version of Moodle with read-only access then
+ you don't need this page - just follow the simpler CVS instructions on the <a target="_top" href="http://moodle.org/download">Moodle download page</a>.</p>
+
+ <p>To use <a target="_top" href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/moodle/moodle/">Moodle's
+ CVS archive</a> (as a <a target="_top" href="http://sourceforge.net/project/memberlist.php?group_id=30935">developer
+ with write access</a>), you first need to have an <a href="http://sourceforge.net/account/register.php">account
+ on Sourceforge</a>. For the examples on this page, let's assume your username
+ is <strong><font color="#990000">myusername</font></strong> and your password
+ is <strong><font color="#990000">mypassword</font></strong>. Take special note of the
+ sourceforge instructions to <a target="_top" href="http://sourceforge.net/docman/display_doc.php?docid=768&group_id=1#develhomedir">create your CVS home directory</a> - something you have to
+ do with every new account to "enable" it for CVS. Basically you just have to use ssh to interactively connect to cvs.sourceforge.net.</p>
+
+ <p>Once you have
+ a working Sourceforge account, contact <a
+ target="_top" href="http://moodle.org/user/view.php?id=1&course=1">Martin Dougiamas</a> so he can give you write access
+ to particular Moodle directories.</p>
+
+ <p>To avoid being prompted for <strong><font color="#990000">mypassword</font></strong>
+ every time you run a CVS command, follow the <a target="_top" href="http://sourceforge.net/account/editsshkeys.php">Sourceforge
+ directions for using authorized keys</a>. This step is optional, but it can
+ make your CVS experience a lot nicer.</p>
+ <p>With that done, you should have all the permissions you need, so you just
+ need to set up your machine and download the current sources so you can start
+ working on them. Below are instructions for Unix and Windows systems.</p>
+ <h2>1. Using CVS on Unix</h2>
+ <blockquote>
+ <p>Sourceforge CVS uses ssh as a transport layer for security, so you will
+ have to set this CVS_RSH environment variable in your Unix shell:</p>
+ <blockquote>
+ <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>
+ <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>
+ </blockquote>
+ <p>It's best to put this in your .bashrc or .cshrc so you don't have to type
+ it all the time. Then, check out Moodle using this (all one line): </p>
+ <blockquote>
+ <pre><strong>cvs -z3 -d:ext:myusername@cvs.moodle.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>
+ </blockquote>
+ <p>Don't try to do run this first CVS command into an existing moodle directory
+ - start fresh with a new directory.</p>
+ <p>Note that you will be prompted for <strong><font color="#990000">mypassword</font></strong>
+ for each command unless you set up <a target="_top" href="http://sourceforge.net/account/editsshkeys.php">authorized
+ keys</a></p>
+ <p>Now, you should have a new 'moodle' directory. You can rename it and move
+ it around if you like. Go into it: </p>
+ <blockquote>
+ <pre><strong>cd moodle </strong></pre>
+ </blockquote>
+ <p>All the latest Moodle files should be in there. You can now change files
+ in your copy. To compare your files against the main CVS copy on the server
+ use cvs diff, eg: </p>
+ <blockquote>
+ <pre><strong>cvs diff -c config-dist.php
+cvs diff -c lang</strong></pre>
+ </blockquote>
+ <p>To fetch the latest updates from the server use: </p>
+ <blockquote>
+ <pre><strong>cvs update -dP</strong> </pre>
+ </blockquote>
+ <p>To copy your new files back to the server you would do something like:
+ </p>
+ <blockquote>
+ <pre><strong>cd lang/ca
+cvs commit</strong> </pre>
+ </blockquote>
+ <p>You will be prompted to add some comments (depends on your default text
+ editor) ... add a meangingful comment and close the editor ... the files
+ will be sent to Sourceforge and stored. Done! </p>
+ <p>To save more time you can put default arguments into a file called .cvsrc
+ in your home directory. For example, mine contains: </p>
+ <blockquote>
+ <pre><strong>diff -c
+update -dP</strong> </pre>
+ </blockquote>
+ <p>Try 'cvs help' for more details ... </p>
+ <p> </p>
+ </blockquote>
+ <h2>2. Using CVS on Windows</h2>
+ <blockquote>
+ <p>First, you need to download a completely fresh copy of Moodle using your
+ developer account.</p>
+ <blockquote>
+ <p> 1. Get TortoiseCVS from <a target="_top" href="http://www.tortoisecvs.org/">tortoisecvs.org</a>
+ and install it, then reboot.<br>
+ <br>
+ 2. Find or create a new folder somewhere where you want Moodle to be downloaded
+ to.<br>
+ <br>
+ 3. Right-mouse-click that folder and choose "<strong>CVS Checkout</strong>"
+ from the menu. You should see a dialog box.<br>
+ <br>
+ 4. Copy this text into the CVSROOT field (using your own username!):</p>
+ <blockquote>
+ <pre> :ext:<font color="#990000">myusername</font>@cvs.moodle.sourceforge.net:/cvsroot/moodle</pre>
+ </blockquote>
+ <p><br>
+ 5. Press the button: "<strong>Fetch list...</strong>".<br>
+ <br>
+ 6. To the right of the button you should see a list of modules: choose
+ "<strong>moodle</strong>" from that list.<br>
+ <br>
+ 7. Press the button: "<strong>OK</strong>" and everything should
+ be downloaded.<br>
+ </p>
+ </blockquote>
+ <p>A dialog box should show all the files being downloaded, and after a while
+ you should have a complete copy of Moodle. After this first checkout, you
+ can fetch the latest updated files from the CVS server:</p>
+ <blockquote>
+ <p> 1. Right-mouse-click on your Moodle folder (or any file) and select
+ "<strong>CVS Update</strong>". <br>
+ </p>
+ </blockquote>
+ <p>After modifying files (you will note they change from green top red!),
+ you can commit them back to the CVS server like this:</p>
+ <blockquote>
+ <p> 1. Right-mouse-click on your Moodle folder (or any file) and select
+ "<strong>CVS Commit...</strong>".<br>
+ <br>
+ 2. In the dialog box, type a clear description of the changes you are
+ committing. <br>
+ <br>
+ 3. Click "OK". Your changes will be sent to the server.<br>
+ </p>
+ </blockquote>
+ </blockquote>
+ <p> </p>
+ <p align="center">Good luck!</p>
+ <p> </p>
+</blockquote>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
-<head>\r
- <title>Moodle Docs: Developers Manual</title>\r
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
- <!--\r
- .sectionheading {\r
- font-size: medium;\r
- font-weight: bold;\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- border: 1px dotted;\r
- padding: 10px;\r
- background-color: #EEEEEE;\r
- }\r
- -->\r
- </style>\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>It's a bit thin at the moment - better documentation will come eventually!</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 class="sectionheading"><a name="architecture"></a>1. Moodle architecture</h3>\r
-<blockquote>\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 \r
- with MySQL, and this is the environment that Moodle has been developed in \r
- (on Linux, Windows, and Mac OS X). Moodle also uses the ADOdb library for \r
- database abstraction, 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 \r
- not yet <em><strong>set up tables</strong></em> in all these databases - \r
- more on this later). <br>\r
- <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 \r
- by libraries of clearly-named functions and consistent layout of script \r
- files. PHP is also easy to install (binaries are available for every platform) \r
- and is widely available to the point that most web hosting services provide \r
- it as standard.<br>\r
- <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 \r
- modules) and a mechanism has been built-in so that Moodle can properly upgrade \r
- itself to new versions (for example it can rename database tables or add \r
- new fields). If using CVS in Unix for example, one can just do a "cvs \r
- update -d" and then visit the site home page to complete an upgrade.<br>\r
- <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>\r
- <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, \r
- normal directory on the server. This would allow a system administrator \r
- to provide seamless forms of file-level access for each teacher, such as \r
- Appletalk, SMB, NFS, FTP, WebDAV and so on. The authentication modules allow \r
- Moodle to use LDAP, IMAP, POP3, NNTP and other databases as sources for \r
- user information. Otherwise, there is work yet to do. Features planned for \r
- Moodle in future versions include: import and export of Moodle data using \r
- XML-based formats (including IMS and SCORM); and increased use of style \r
- sheets for interface formatting (so that it can be integrated visually into \r
- other web sites).</li>\r
- </ol>\r
-</blockquote>\r
-<p> </p>\r
-<h3 class="sectionheading"><a name="contribute" id="contribute"></a>2. How you can contribute</h3>\r
-<blockquote>\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. \r
- If 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 \r
- user's 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 \r
- starting with widget_ and any constants you define should start with \r
- WIDGET_ </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.org/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.org/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 \r
- are provided in the main distribution, but you may want to create your own \r
- theme with your own colours, logo, styles and graphics. </p>\r
- <p>Each theme is in a subdirectory of the "theme" directory, and \r
- contains 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 \r
- is 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. </li>\r
- <li>Edit config.php and insert your own colours. </li>\r
- <li>Edit styles.php and change your CSS styles. </li>\r
- <li>Edit header.html and footer.html to add new logos, or change the layout. \r
- </li>\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 \r
- the 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 \r
- based on XSL transformations of XML output from Moodle. It is likely that \r
- the themes for this will be a completely different format, but the advantage \r
- will be a much higher possible degree of customisation (including moving \r
- elements around the page).</p>\r
- <p>More discussion about this in the <a target=_top href="http://moodle.org/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
- <p> </p>\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'. \r
- The 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 \r
- module 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 \r
- create new languages but to refine existing ones. If you are starting a \r
- new language, please contact me, <a target=_top href="http://dougiamas.com/">Martin \r
- Dougiamas</a>. </p>\r
- <p>You might also like to post in the <a target=_top href="http://moodle.org/mod/forum/view.php?id=43">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 \r
- SQL used in Moodle should work fine with a wide variety of database brands.</p>\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 \r
- each database, schemas can be created that list the required SQL to create \r
- Moodle 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
- <p>Currently, only MySQL and PostgreSQL are fully supported in this way (no-one \r
- wrote the schemas for other brands).</p>\r
- <p>Moodle 1.2 will use a new method of database-independent XML schemas that \r
- will make all this unnecessary.</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 \r
- and social. </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 \r
- to 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.org/">http://moodle.org/</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://moodle.org/bugs/">http://moodle.org/bugs</a> \r
- so you can file any bugs that you find and perhaps participate in discussing \r
- and fixing them. </p>\r
- <p>"Bugs" not only includes software bugs with current versions \r
- of 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. \r
- In this project, your input is very welcome!</p>\r
- </blockquote>\r
-</blockquote>\r
-<p> </p>\r
-<blockquote> \r
- <blockquote> \r
- <blockquote> \r
- <p align="center">Thanks for using Moodle!<br>\r
- <br>\r
- <a target=_top href="http://dougiamas.com/">Martin Dougiamas</a>, Lead \r
- Developer </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
-</html>
\ No newline at end of file
+<head>
+<title>Moodle Docs: Developers Manual</title>
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body bgcolor="#FFFFFF">
+<h1>Developers Manual</h1>
+<blockquote>
+ <p>This document describes some of Moodle's design and how you can contribute.</p>
+ <p>It's a bit thin at the moment - better documentation will come eventually!</p>
+ <p>Sections in this document:</p>
+ <ol>
+ <li><a href="#architecture">Moodle architecture</a></li>
+ <li><a href="#contribute">How you can contribute</a>
+ <ul>
+ <li><a href="#activities">Learning activities</a></li>
+ <li><a href="#themes">Themes</a></li>
+ <li><a href="#languages">Languages</a></li>
+ <li><a href="#database">Database Schemas</a></li>
+ <li><a href="#courseformats">Course formats</a></li>
+ <li><a href="#doc">Documentation and articles</a></li>
+ <li><a href="#bugs">Participating in the bug tracker</a></li>
+ </ul>
+ </li>
+ </ol>
+</blockquote>
+<p> </p>
+<h2><a name="architecture"></a>1. Moodle architecture</h2>
+<blockquote>
+ <p>From a system administrator's perspective, Moodle has been designed according
+ to the following criteria:</p>
+ <ol>
+ <li><strong>Moodle should run on the widest variety of platforms</strong><br>
+ <br>
+ The web application platform that runs on most platforms is PHP combined
+ with MySQL, and this is the environment that Moodle has been developed in
+ (on Linux, Windows, and Mac OS X). Moodle also uses the ADOdb library for
+ database abstraction, which means Moodle can use <a href="http://php.weblogs.com/ADOdb_manual#drivers">more
+ than ten different brands of database</a> (unfortunately, though, it can
+ not yet <em><strong>set up tables</strong></em> in all these databases -
+ more on this later). <br>
+ <br>
+ </li>
+ <li><strong>Moodle should be easy to install, learn and modify</strong><br>
+ <br>
+ Early prototypes of Moodle (1999) were built using <a target=_top href="http://www.zope.org/">Zope</a>
+ - an advanced object-oriented web application server. Unfortunately I found
+ that although the technology was pretty cool, it had a very steep learning
+ curve and was not very flexible in terms of system administration. The PHP
+ scripting language, on the other hand, is very easy to get into (especially
+ if you've done any programming using any other scripting language). Early
+ on I made the decision to avoid using a class-oriented design - again, to
+ keep it simple to understand for novices. Code reuse is instead achieved
+ by libraries of clearly-named functions and consistent layout of script
+ files. PHP is also easy to install (binaries are available for every platform)
+ and is widely available to the point that most web hosting services provide
+ it as standard.<br>
+ <br>
+ </li>
+ <li><strong>It should be easy to upgrade from one version to the next</strong><br>
+ <br>
+ Moodle knows what version it is (as well as the versions of all plug-in
+ modules) and a mechanism has been built-in so that Moodle can properly upgrade
+ itself to new versions (for example it can rename database tables or add
+ new fields). If using CVS in Unix for example, one can just do a "cvs
+ update -d" and then visit the site home page to complete an upgrade.<br>
+ <br>
+ </li>
+ <li><strong>It should be modular to allow for growth</strong><br>
+ <br>
+ Moodle has a number of features that are modular, including themes, activities,
+ interface languages, database schemas and course formats. This allows anyone
+ to add features to the main codebase or to even distribute them separately.
+ More on this below in the next section.<br>
+ <br>
+ </li>
+ <li><strong>It should be able to be used in conjunction with other systems</strong><br>
+ <br>
+ One thing Moodle does is keep all files for one course within a single,
+ normal directory on the server. This would allow a system administrator
+ to provide seamless forms of file-level access for each teacher, such as
+ Appletalk, SMB, NFS, FTP, WebDAV and so on. The authentication modules allow
+ Moodle to use LDAP, IMAP, POP3, NNTP and other databases as sources for
+ user information. Otherwise, there is work yet to do. Features planned for
+ Moodle in future versions include: import and export of Moodle data using
+ XML-based formats (including IMS and SCORM); and increased use of style
+ sheets for interface formatting (so that it can be integrated visually into
+ other web sites).</li>
+ </ol>
+</blockquote>
+<p> </p>
+<h2><a name="contribute" id="contribute"></a>2. How you can contribute</h2>
+<blockquote>
+ <p>As mentioned above, Moodle has a number of features that are modular. Even
+ if you are not a programmer there are things you can change or help with.</p>
+ <h3><a name="activities" id="activities"></a>Learning Activities</h3>
+ <blockquote>
+ <p>These are by far the most important modules, and reside in the 'mod' directory.
+ There are seven default modules: assignment, choice, forum, journal, quiz,
+ resource, and survey. Each module is in a separate subdirectory and consists
+ of the following mandatory elements (plus extra scripts unique to each module):</p>
+ <ul>
+ <li>mod.html: a form to set up or update an instance of this module</li>
+ <li>version.php: defines some meta-info and provides upgrading code</li>
+ <li>icon.gif: a 16x16 icon for the module</li>
+ <li>db/: SQL dumps of all the required db tables and data (for each database
+ type) </li>
+ <li>index.php: a page to list all instances in a course</li>
+ <li>view.php: a page to view a particular instance</li>
+ <li>lib.php: any/all functions defined by the module should be in here.
+ If the modulename if called widget, then the required functions include:
+ <ul>
+ <li>widget_add_instance() - code to add a new instance of widget</li>
+ <li>widget_update_instance() - code to update an existing instance</li>
+ <li>widget_delete_instance() - code to delete an instance</li>
+ <li>widget_user_outline() - given an instance, return a summary of a
+ user's contribution</li>
+ <li>widget_user_complete() - given an instance, print details of a user's
+ contribution<br>
+ </li>
+ <li>To avoid possible conflict, any module functions should be named
+ starting with widget_ and any constants you define should start with
+ WIDGET_ </li>
+ </ul>
+ </li>
+ <li>Lastly, each module will have some language files that contain strings
+ for that module. See below.</li>
+ </ul>
+ <p>The easiest way to start a new learning activity module is to use the template
+ in <strong><a href="http://moodle.org/mod/newmodule_template.zip">mod/newmodule_template.zip</a>.</strong>
+ Unzip it and follow the README inside. </p>
+ <p>You might also like to post first in the <a href="http://moodle.org/mod/forum/view.php?id=44" target="_top">Activities
+ modules forum on Using Moodle</a>.</p>
+ <p> </p>
+ </blockquote>
+ <h3><a name="themes" id="themes"></a>Themes</h3>
+ <blockquote>
+ <p>Themes (or skins) define the look of a site. A number of simple themes
+ are provided in the main distribution, but you may want to create your own
+ theme with your own colours, logo, styles and graphics. </p>
+ <p>Each theme is in a subdirectory of the "theme" directory, and
+ contains at least the following files:</p>
+ <ul>
+ <li><strong>config.php</strong>: defines the theme colours used throughout
+ the site</li>
+ <li><strong>styles.php</strong>: the style sheet, containing CSS definitions
+ for standard HTML elements as well as many Moodle elements.</li>
+ <li><strong>header.html</strong>: Included at the top of each page. This
+ is what you need to edit to add a logo at the top of pages, for example.</li>
+ <li><strong>footer.html</strong>: Included at the bottom of each page.</li>
+ </ul>
+ <p>To create your own themes for current versions of Moodle:</p>
+ <ol>
+ <li>Copy one of the existing theme folders to one with a new name. I recommend
+ starting with one of the standard themes. </li>
+ <li>Edit config.php and insert your own colours. </li>
+ <li>Edit styles.php and change your CSS styles. </li>
+ <li>Edit header.html and footer.html to add new logos, or change the layout.
+ </li>
+ </ol>
+ <p>Note that all these steps are optional - you can make a radically different
+ look to your site simply by editing the colours in config.php</p>
+ <p>Note also that Moodle upgrades <em>may</em> break themes slightly, so check
+ the release notes carefully if you are using a custom theme.</p>
+ <p>In particular, Moodle 2.0 will have a completely new display system, probably
+ based on XSL transformations of XML output from Moodle. It is likely that
+ the themes for this will be a completely different format, but the advantage
+ will be a much higher possible degree of customisation (including moving
+ elements around the page).</p>
+ <p>More discussion about this in the <a target=_top href="http://moodle.org/mod/forum/view.php?id=46">Themes
+ forum on Using Moodle</a>. If you create a nice theme that you think others
+ might want to use, please post your zip file on the themes forum!<br>
+ </p>
+ </blockquote>
+ <h3><a name="languages" id="languages"></a>Languages</h3>
+ <blockquote>
+ <p>Moodle has been designed for internationalisation. Each 'string' or 'page'
+ of text that is displayed as part of the interface is drawn from a set of
+ language files. Each language is a subdirectory of the directory 'lang'.
+ The structure of the lang directory is as follows:</p>
+ <p><strong>lang/en</strong> - directory containing all files for one language
+ (eg English)</p>
+ <ul>
+ <li>moodle.php - strings for main interface</li>
+ <li>assignment.php - strings for assignment module</li>
+ <li>choice.php - strings for choice module</li>
+ <li>forum.php - strings for forum module</li>
+ <li>journal.php - strings for journal module </li>
+ <li>quiz.php - strings for quiz module</li>
+ <li>resource.php - strings for resource module</li>
+ <li>survey.php - strings for survey module</li>
+ <li>.... plus other modules if any.<br>
+ <br>
+ A string is called from these files using the <strong><em>get_string()</em></strong><em>
+ </em>or<em> <strong>print_string()</strong> </em>functions. Each string
+ supports variable substitution, to support variable ordering in different
+ languages.<em><br>
+ <br>
+ </em>eg $strdueby = get_string("assignmentdueby", "assignment",
+ userdate($date)); <br>
+ <br>
+ If a string doesn't exist in a particular language, then the equivalent
+ in English will automatically be used instead.</li>
+ </ul>
+ <p><strong>lang/en/help</strong> - contains whole help pages (for popup context-sensitive
+ help)</p>
+ <blockquote>
+ <p>Main help pages are situated here, while help pages specific to each
+ module are located in subdirectories with the module's name.</p>
+ <p>You can insert a helpbutton in a page with the helpbutton function.</p>
+ <p>eg helpbutton("text", "Click here for help about text");</p>
+ <p>and for modules:</p>
+ <p>helpbutton("forumtypes", "Forum types", "forum");</p>
+ </blockquote>
+ <p>Note that you can edit languages online, using the administration web tools
+ under "Check this language". This makes it easy to not to only
+ create new languages but to refine existing ones. If you are starting a
+ new language, please contact me, <a target=_top href="http://dougiamas.com/">Martin
+ Dougiamas</a>. </p>
+ <p>You might also like to post in the <a target=_top href="http://moodle.org/mod/forum/view.php?id=43">Languages
+ forum on Using Moodle</a>. </p>
+ <p>If you are maintaining a language an ongoing basis, I can give you <a href="?file=cvs.html">CVS
+ write access to the Moodle source code</a> so that you can directly maintain
+ the files.</p>
+ </blockquote>
+ <h3><a name="database" id="database"></a>Database Schemas</h3>
+ <blockquote>
+ <p>Given a working database with defined tables, the intentionally simple
+ SQL used in Moodle should work fine with a wide variety of database brands.</p>
+ <p>A problem exists with <strong>automatically creating</strong> new tables
+ in a database, which is what Moodle tries to do upon initial installation.
+ Because every database is very different, there doesn't yet exist any way
+ to do this in a platform-independent way. To support this automation in
+ each database, schemas can be created that list the required SQL to create
+ Moodle tables in a particular database. These are files in <strong>lib/db</strong>
+ and inside the <strong>db</strong> subdirectory of each module.</p>
+ <p>Currently, only MySQL and PostgreSQL are fully supported in this way (no-one
+ wrote the schemas for other brands).</p>
+ <p>Moodle 1.2 will use a new method of database-independent XML schemas that
+ will make all this unnecessary.</p>
+ </blockquote>
+ <p> </p>
+ <h3><a name="courseformats" id="courseformats"></a>Course Formats</h3>
+ <blockquote>
+ <p>Moodle currently supports three different course formats: weekly, topics
+ and social. </p>
+ <p>These are a little more connected to the rest of the code (and hence, less
+ "pluggable") but it is still quite easy to add new ones.</p>
+ <p>If you have any ideas for different formats that you need or would like
+ to see, get in touch with me and I'll do my absolute best to have them available
+ in future releases.</p>
+ </blockquote>
+ <p> </p>
+ <h3><a name="doc" id="doc"></a>Documentation and articles</h3>
+ <blockquote>
+ <p>If you feel like writing a tutorial, an article, an academic paper or anything
+ else about Moodle, please do! </p>
+ <p>Put it on the web and make sure you include links to <a target=_top href="http://moodle.org/">http://moodle.org/</a></p>
+ </blockquote>
+ <p> </p>
+ <h3><a name="bugs" id="bugs"></a>Participating in the bug tracker</h3>
+ <blockquote>
+ <p>Finally, I would like to invite you to register on the "bug tracker"
+ at <a target=_top href="http://moodle.org/bugs/">http://moodle.org/bugs</a>
+ so you can file any bugs that you find and perhaps participate in discussing
+ and fixing them. </p>
+ <p>"Bugs" not only includes software bugs with current versions
+ of Moodle, but also new ideas, feature requests and even constructive criticism
+ of existing features. The beauty of open source is that anyone can participate
+ in some way and help to create a better product for all of us to enjoy.
+ In this project, your input is very welcome!</p>
+ </blockquote>
+</blockquote>
+<p> </p>
+<blockquote>
+ <blockquote>
+ <blockquote>
+ <p align="center">Thanks for using Moodle!<br>
+ <br>
+ <a target=_top href="http://dougiamas.com/">Martin Dougiamas</a>, Lead
+ Developer </p>
+ </blockquote>
+ </blockquote>
+</blockquote>
+<p> </p>
+<blockquote>
+ <p> </p>
+</blockquote>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
<html>
-
-
-
<head>
-
-
-
<title>Moodle Docs: Frequently Asked Questions (FAQ)</title>
-
-
-
-<link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">
-
-
-
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-
-
-
-<style type="text/css">
-
-
-
-<!--
-
-
-
-.question {
-
-
-
- font-size: medium;
-
-
-
- font-weight: bold;
-
-
-
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;
-
-
-
- border: 1px dotted;
-
-
-
- padding: 10px;
-
-
-
- background-color: #EEEEEE;
-
-
-
-}
-
-
-
-.answer {
-
-
-
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;
-
-
-
- font-size: medium;
-
-
-
- border: none;
-
-
-
- padding-left: 40px;
-
-
-
-}
-
-
-
--->
-
-
-
-</style>
-
-
-
-<style type="text/css">
-
-
-
-<!--
-
-
-
-.normaltext {
-
-
-
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;
-
-
-
- font-size: medium;
-
-
-
- border: none;
-
-
-
- padding-left: 10px;
-
-
-
-}
-
-
-
-.answercode {
-
-
-
- font-family: "Courier New", Courier, mono;
-
-
-
- font-size: small;
-
-
-
- border: none;
-
-
-
- padding-left: 60px;
-
-
-
-}
-
-
-
-.questionlink {
-
-
-
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;
-
-
-
- font-size: medium;
-
-
-
- border: none;
-
-
-
- padding-left: 40px;
-
-
-
-}
-
-
-
--->
-
-
-
-</style>
-
-
-
</head>
-
-
-
-
-
-
<body bgcolor="#FFFFFF">
-
-
-
-<h2>Frequently Asked Questions (FAQ)</h2>
-
-
-
+<h1>Frequently Asked Questions (FAQ)</h1>
<p class="normaltext">This page contains answers to some of the most
-
-
-
frequently asked questions by people installing Moodle. If you have
-
-
-
followed the <a href="./?file=install.html">installation instructions</a> but
-
-
-
you still have a problem, then this page is probably the best place to be. </p>
-
-
<p class="normaltext">If you don't find your answer here try the <a href="http://moodle.org/mod/forum/index.php?id=5" target="_top">Using
-
-
-
Moodle</a> course on moodle.org. Start by searching the forums using a few keywords,
-
in case your problem has already been discussed. If you don't find
-
anything, then try posting your question into the appropriate forum - somebody will
-
usually be able to help you.</p>
-
<p class="normaltext">If you have tried a number of solutions without resolving an issue,
-
and you are running behind a firewall, it may be advisable to try re-configuring your
-
firewall to ensure that it is not blocking a required function or necessary communication.
-
Firewalls very rarely cause problems with Moodle but are occasionally responsible for
-
reduced functionality due to a mis-configuration in the firewall settings.
<p class="normaltext">Use this list to jump to the appropriate answer below:</p>
-
-
-
-
-
-
<p class="questionlink"><a href="#filenotfound">Whenever I try to access or view a file that I uploaded, I get an error "File not Found"</a></p>
-<h3
class="question"><a name="filenotfound"></a>Whenever I try to access or view
+<h3><a name="filenotfound"></a>Whenever I try to access or view
- <h
4 class="question"><a name="php"></a>PHP - is it installed and what version
+ <h
3><a name="php"></a>PHP - is it installed and what version
- do I have?</h4>
+ do I have?</h3>
-<h4 class="question"><a name="blankpages"></a>Why are all my pages blank? </h4>
+<h3><a name="blankpages"></a>Why are all my pages blank? </h3>
-<h
4 class="question"><a name="errorgetstring"></a>My pages show fatal errors such
+<h
3><a name="errorgetstring"></a>My pages show fatal errors such
- as : call to undefined function: get_string()</h4>
+ as : call to undefined function: get_string()</h3>
-<h
4 class="question"><a name="headerssent"></a>Why do I keep getting error messages
+<h
3><a name="headerssent"></a>Why do I keep getting error messages
- about "headers already sent"?</h4>
+ about "headers already sent"?</h3>
-<h
4 class="question"><a name="failedopen"></a>I keep getting this error: Failed
+<h
3><a name="failedopen"></a>I keep getting this error: Failed
- opening required '/web/moodle/lib/setup.php'</h4>
+ opening required '/web/moodle/lib/setup.php'</h3>
-<h
4 class="question"><a name="quotes" id="quotes"></a>Any text I add with an apostrophe
+<h
3><a name="quotes" id="quotes"></a>Any text I add with an apostrophe
- (') or a quote (") causes errors or comes up with a slash added</h4>
+ (') or a quote (") causes errors or comes up with a slash added</h3>
-<h4 class="question"><a name="sessiontmp"></a>I keep getting error messages about session_start</h4>
+<h3><a name="sessiontmp"></a>I keep getting error messages about session_start</h3>
-<h4 class="question"><a name="fixdirroot"></a>When I go to the admin page, I get told to make dirroot blank!</h4>
+<h3><a name="fixdirroot"></a>When I go to the admin page, I get told to make dirroot blank!</h3>
-<h4 class="question"><a name="loginsetting"></a>I login but don't appear to be. I am logged in and can navigate freely.</h4>
+<h3><a name="loginsetting"></a>I login but don't appear to be. I am logged in and can navigate freely.</h3>
-<h4 class="question"><a name="resource1"></a>When trying to add a resource I receive error messages.</h4>
+<h3><a name="resource1"></a>When trying to add a resource I receive error messages.</h3>
-<h4 class="question"><a name="noadmin"></a>During the initial setting-up process, I never get asked to create an admin account!</h4>
+<h3><a name="noadmin"></a>During the initial setting-up process, I never get asked to create an admin account!</h3>
-<h4 class="question"><a name="nologin"></a>I can't log in - I just stay stuck on the login screen.</h4>
+<h3><a name="nologin"></a>I can't log in - I just stay stuck on the login screen.</h3>
-<h4 class="question"><a name="backup"></a>How do I backup my whole Moodle site?</h4>
+<h3><a name="backup"></a>How do I backup my whole Moodle site?</h3>
-<h4 class="question"><a name="locale"></a>Why doesn't my Moodle site display the time & date correctly?</h4>
+<h3><a name="locale"></a>Why doesn't my Moodle site display the time & date correctly?</h3>
<p class="answer"> </p>
-<h
4 class="question"><a name="cron"></a>Email copies are not being sent
+<h
3><a name="cron"></a>Email copies are not being sent
- from my forums </h4>
+ from my forums </h3>
<p class="answer">You <strong>must</strong> set up cron properly if you want Moodle
<p class="answer">Tip: Try the default setting in Moodle variables page. Leave the smtphost blank.
This will be acceptable for the majority of users.
-
-<h2> </h2>
-
-<h2> </h2>
-
-
-
-
-
+<p class="answer">
+<p class="answer">
<hr>
-<!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
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
- <!--\r
- .sectionheading {\r
- font-size: medium;\r
- font-weight: bold;\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- border: 1px dotted;\r
- padding: 10px;\r
- background-color: #EEEEEE;\r
- }\r
- -->\r
- </style>\r
-</head>\r
-<body bgcolor="#ffffff">\r
- \r
-<h2>Features</h2>\r
-<p>Moodle is an active and evolving product. This page lists just some of the \r
- many features it contains:</p>\r
-<h3 class="sectionheading">Overall design</h3>\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 (and can share it).</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>Courses can be categorised and searched - one Moodle site can support thousands \r
- of courses</li>\r
- <li>Emphasis on strong security throughout. Forms are all checked, data validated, \r
- cookies encrypted etc</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
-</ul>\r
-<h3 class="sectionheading">Site management</h3>\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 \r
- packs for over <a href="http://moodle.org/download/lang/" target="_top">34 \r
- 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
-<h3 class="sectionheading">User management</h3>\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>A course creator account is only allowed to create courses and teach in \r
- them</li>\r
- <li>Teachers may have editing privileges removed so that they can't modify the \r
- course (eg for part-time tutors)</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 enrol students manually if desired</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
-<h3 class="sectionheading">Course management</h3>\r
-<ul>\r
- <li>A full teacher has full control over all settings for a course, including \r
- restricting other teachers</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, Chats, Workshops</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
- <li>Custom scales - teachers can define their own scales to be used for grading \r
- forums, assignments and journals</li>\r
- <li>Courses can be packaged as a single zip file using the Backup function. \r
- These can be restored on any Moodle server.</li>\r
-</ul>\r
-<h3 class="sectionheading">Assignment Module</h3>\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
-<h3 class="sectionheading">Chat Module</h3>\r
-<ul>\r
- <li>Allows smooth, synchronous text interaction</li>\r
- <li>Includes profile pictures in the chat window</li>\r
- <li>Supports URLs, smilies, embedded HTML, images etc</li>\r
- <li>All sessions are logged for later viewing, and these can also be made available \r
- to students</li>\r
-</ul>\r
-<h3 class="sectionheading">Choice Module</h3>\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
- <li>Students can optionally be allowed to see an up-to-date graph of results</li>\r
-</ul>\r
-<h3 class="sectionheading">Forum Module</h3>\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
- <li>Discussion threads can be easily moved between forums by the teacher</li>\r
- <li>Attached images are shown inline</li>\r
- <li>If forum ratings are being used, these can be restricted to a range of dates</li>\r
-</ul>\r
-<h3 class="sectionheading">Journal Module</h3>\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
-<h3 class="sectionheading">Quiz Module</h3>\r
-<ul>\r
- <li>Teachers can define a database of questions for re-use in different quizzes</li>\r
- <li>Questions can be stored in categories for easy access, and these categories \r
- can be "published" to make them accessible from any course on the \r
- site. </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>Quiz questions and quiz answers can be shuffled (randomised) to reduce cheating</li>\r
- <li>Questions allow HTML and images</li>\r
- <li>Questions can be imported from external text files</li>\r
- <li>Quizzes can be attempted multiple times, if desired</li>\r
- <li>Attempts can be cumulative, if desired, and finished over several sessions</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
- <li>Matching questions</li>\r
- <li>Random questions</li>\r
- <li>Numerical questions (with allowable ranges)</li>\r
- <li>Embedded-answer questions (cloze style) with answers within passages of \r
- text </li>\r
- <li>Embedded descriptive text and graphics</li>\r
-</ul>\r
-<h3 class="sectionheading">Resource Module</h3>\r
-<ul>\r
- <li>Supports display of any electronic content, Word, Powerpoint, Flash, Video, \r
- Sounds etc</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
- <li>External web applications can be linked in with data passed to them</li>\r
-</ul>\r
-<h3 class="sectionheading">Survey Module</h3>\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
-<h3 class="sectionheading">Workshop Module</h3>\r
-<ul>\r
- <li>Allows peer assessement of documents, and the teacher can manage and grade \r
- the assessment.</li>\r
- <li>Supports a wide range of possible grading scales</li>\r
- <li>Teacher can provide sample documents for students to practice grading</li>\r
- <li>Very flexible with many options.</li>\r
-</ul>\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
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+<title>Moodle Docs: Background</title>
+
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body bgcolor="#ffffff">
+
+<h1>Features</h1>
+<blockquote>
+ <p>Moodle is an active and evolving product. This page lists just some of the
+ many features it contains:</p>
+ <h3>Overall design</h3>
+ <ul>
+ <li>Promotes a social constructionist pedagogy (collaboration, activities, critical
+ reflection, etc)</li>
+ <li>Suitable for 100% online classes as well as supplementing face-to-face learning
+ </li>
+ <li>Simple, lightweight, efficient, compatible, low-tech browser interface</li>
+ <li>Easy to install on almost any platform that supports PHP. Requires only
+ one database (and can share it).</li>
+ <li>Full database abstraction supports all major brands of database (except
+ for initial table definition)</li>
+ <li>Course listing shows descriptions for every course on the server, including
+ accessibility to guests.</li>
+ <li>Courses can be categorised and searched - one Moodle site can support thousands
+ of courses</li>
+ <li>Emphasis on strong security throughout. Forms are all checked, data validated,
+ cookies encrypted etc</li>
+ <li>Most text entry areas (resources, forum postings, journal entries etc) can
+ be edited using an embedded WYSIWYG HTML editor</li>
+ </ul>
+ <h3 >Site management</h3>
+ <ul>
+ <li>Site is managed by an admin user, defined during setup</li>
+ <li>Plug-in "themes" allow the admin to customise the site colours, fonts, layout
+ etc to suit local needs</li>
+ <li>Plug-in activity modules can be added to existing Moodle installations</li>
+ <li>Plug-in language packs allow full localisation to any language. These can
+ be edited using a built-in web-based editor. Currently there are language
+ packs for over <a href="http://moodle.org/download/lang/" target="_top">34
+ languages</a>.</li>
+ <li>The code is clearly-written PHP under a GPL license - easy to modify to
+ suit your needs</li>
+ </ul>
+ <h3 >User management</h3>
+ <ul>
+ <li>Goals are to reduce admin involvement to a minimum, while retaining high
+ security</li>
+ <li>Supports a range of authentication mechanisms through plug-in authentication
+ modules, allowing easy integration with existing systems.</li>
+ <li>Standard email method: students can create their own login accounts. Email
+ addresses are verified by confirmation.</li>
+ <li>LDAP method: account logins can be checked against an LDAP server. Admin
+ can specify which fields to use.</li>
+ <li>IMAP, POP3, NNTP: account logins are checked against a mail or news server.
+ SSL, certificates and TLS are supported.</li>
+ <li>External database: any database containing at least two fields can be used
+ as an external authentication source.</li>
+ <li>Each person requires only one account for the whole server - each account
+ can have different access</li>
+ <li>An admin account controls the creation of courses and creates teachers by
+ assigning users to courses</li>
+ <li>A course creator account is only allowed to create courses and teach in
+ them</li>
+ <li>Teachers may have editing privileges removed so that they can't modify the
+ course (eg for part-time tutors)</li>
+ <li>Security - teachers can add an "enrolment key" to their courses to keep
+ out non-students. They can give out this key face-to-face or via personal
+ email etc</li>
+ <li>Teachers can enrol students manually if desired</li>
+ <li>Teachers can unenrol students manually if desired, otherwise they are automatically
+ unenrolled after a certain period of inactivity (set by the admin)</li>
+ <li>Students are encouraged to build an online profile including photos, description.
+ Email addresses can be protected from display if required.</li>
+ <li>Every user can specify their own timezone, and every date in Moodle is translated
+ to that timezone (eg posting dates, assignment due dates etc)</li>
+ <li>Every user can choose the language used for the Moodle interface (English,
+ French, German, Spanish, Portuguese etc)</li>
+ </ul>
+ <h3 >Course management</h3>
+ <ul>
+ <li>A full teacher has full control over all settings for a course, including
+ restricting other teachers</li>
+ <li>Choice of course formats such as by week, by topic or a discussion-focussed
+ social format</li>
+ <li>Flexible array of course activities - Forums, Journals, Quizzes, Resources,
+ Choices, Surveys, Assignments, Chats, Workshops</li>
+ <li>Recent changes to the course since the last login can be displayed on the
+ course home page - helps give sense of community</li>
+ <li>Most text entry areas (resources, forum postings, journal entries etc) can
+ be edited using an embedded WYSIWYG HTML editor</li>
+ <li>All grades for Forums, Journals, Quizzes and Assignments can be viewed on
+ one page (and downloaded as a spreadsheet file)</li>
+ <li>Full user logging and tracking - activity reports for each student are available
+ with graphs and details about each module (last access, number of times read)
+ as well as a detailed "story" of each students involvement including postings,
+ journal entries etc on one page.</li>
+ <li>Mail integration - copies of forum posts, teacher feedback etc can be mailed
+ in HTML or plain text.</li>
+ <li>Custom scales - teachers can define their own scales to be used for grading
+ forums, assignments and journals</li>
+ <li>Courses can be packaged as a single zip file using the Backup function.
+ These can be restored on any Moodle server.</li>
+ </ul>
+ <h3 >Assignment Module</h3>
+ <ul>
+ <li>Assignments can be specified with a due date and a maximum grade.</li>
+ <li>Students can upload their assignments (any file format) to the server -
+ they are date-stamped.</li>
+ <li>Late assignments are allowed, but the amount of lateness is shown clearly
+ to the teacher</li>
+ <li>For each particular assignment, the whole class can be assessed (grade and
+ comment) on one page in one form.</li>
+ <li>Teacher feedback is appended to the assignment page for each student, and
+ notification is mailed out.</li>
+ <li>The teacher can choose to allow resubmission of assignments after grading
+ (for regrading)</li>
+ </ul>
+ <h3 >Chat Module</h3>
+ <ul>
+ <li>Allows smooth, synchronous text interaction</li>
+ <li>Includes profile pictures in the chat window</li>
+ <li>Supports URLs, smilies, embedded HTML, images etc</li>
+ <li>All sessions are logged for later viewing, and these can also be made available
+ to students</li>
+ </ul>
+ <h3 >Choice Module</h3>
+ <ul>
+ <li>Like a poll. Can either be used to vote on something, or to get feedback
+ from every student (eg research consent)</li>
+ <li>Teacher sees intuitive table view of who chose what</li>
+ <li>Students can optionally be allowed to see an up-to-date graph of results</li>
+ </ul>
+ <h3 >Forum Module</h3>
+ <ul>
+ <li>Different types of forums are available, such as teacher-only, course news,
+ open-to-all, and one-thread-per-user.</li>
+ <li>All postings have the authors photo attached.</li>
+ <li>Discussions can be viewed nested, flat or threaded, oldest or newest first.</li>
+ <li>Individual forums can be subscribed to by each person so that copies are
+ forwarded via email, or the teacher can force subscription for all</li>
+ <li>The teacher can choose not to allow replies (eg for an announcements-only
+ forum)</li>
+ <li>Discussion threads can be easily moved between forums by the teacher</li>
+ <li>Attached images are shown inline</li>
+ <li>If forum ratings are being used, these can be restricted to a range of dates</li>
+ </ul>
+ <h3 >Journal Module</h3>
+ <ul>
+ <li>Journals are private between student and teacher.</li>
+ <li>Each journal entry can be directed by an open question.</li>
+ <li>For each particular journal entry, the whole class can be assessed on one
+ page in one form</li>
+ <li>Teacher feedback is appended to the journal entry page, and notification
+ is mailed out.</li>
+ </ul>
+ <h3 >Quiz Module</h3>
+ <ul>
+ <li>Teachers can define a database of questions for re-use in different quizzes</li>
+ <li>Questions can be stored in categories for easy access, and these categories
+ can be "published" to make them accessible from any course on the
+ site. </li>
+ <li>Quizzes are automatically graded, and can be re-graded if questions are
+ modified </li>
+ <li>Quizzes can have a limited time window outside of which they are not available</li>
+ <li>At the teacher's option, quizzes can be attempted multiple times, and can
+ show feedback and/or correct answers</li>
+ <li>Quiz questions and quiz answers can be shuffled (randomised) to reduce cheating</li>
+ <li>Questions allow HTML and images</li>
+ <li>Questions can be imported from external text files</li>
+ <li>Quizzes can be attempted multiple times, if desired</li>
+ <li>Attempts can be cumulative, if desired, and finished over several sessions</li>
+ <li>Multiple-choice questions supporting single or multiple answers</li>
+ <li>Short Answer questions (words or phrases)</li>
+ <li>True-False questions </li>
+ <li>Matching questions</li>
+ <li>Random questions</li>
+ <li>Numerical questions (with allowable ranges)</li>
+ <li>Embedded-answer questions (cloze style) with answers within passages of
+ text </li>
+ <li>Embedded descriptive text and graphics</li>
+ </ul>
+ <h3 >Resource Module</h3>
+ <ul>
+ <li>Supports display of any electronic content, Word, Powerpoint, Flash, Video,
+ Sounds etc</li>
+ <li>Files can be uploaded and managed on the server, or created on the fly using
+ web forms (text or HTML)</li>
+ <li>External content on the web can be linked to or seamlessly included within
+ the course interface.</li>
+ <li>External web applications can be linked in with data passed to them</li>
+ </ul>
+ <h3 >Survey Module</h3>
+ <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
+</li>
+ </ul>
+ <h3 >Workshop Module</h3>
+ <ul>
+ <li>Allows peer assessement of documents, and the teacher can manage and grade
+ the assessment.</li>
+ <li>Supports a wide range of possible grading scales</li>
+ <li>Teacher can provide sample documents for students to practice grading</li>
+ <li>Very flexible with many options.</li>
+ </ul>
+ <p> </p>
+</blockquote>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
-<?PHP // $Id$
+<?php // $Id$
// Names of the documentation files
+ // Files with a definition "-" are treated as spacers
+$string['-about'] = "About Moodle";
$string['intro.html'] = "Introduction";
$string['background.html'] = "Background";
+$string['philosophy.html'] = "Philosophy";
+$string['licence.html'] = "License";
$string['features.html'] = "Features";
$string['release.html'] = "Release Notes";
+$string['future.html'] = "Future";
+$string['credits.html'] = "Credits";
+
+$string['-installation'] = "Administration";
$string['install.html'] = "Installation";
$string['faq.html'] = "Installation FAQ";
$string['installamp.html'] = "Apache, MySQL, PHP";
$string['upgrade.html'] = "Upgrading";
+
+$string['-usage'] = "Using Moodle";
$string['teacher.html'] = "Teacher Manual";
+$string['other.html'] = "Other Docs";
+
+$string['-development'] = "Development";
$string['developer.html'] = "Developer Manual";
+$string['coding.html'] = "Coding Guide";
$string['cvs.html'] = "Using CVS";
-$string['future.html'] = "Future";
-$string['credits.html'] = "Credits";
-$string['licence.html'] = "License";
-$string['other.html'] = "Other Docs";
?>
-<head>\r
- <title>Moodle Docs: Future</title>\r
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
- DT {font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif; font-weight: bold;}\r
- DD {margin-bottom:1em;} \r
- </style>\r
-</head>\r
-\r
-<body bgcolor="#FFFFFF">\r
-\r
-<h2>Future</h2>\r
-\r
-<p>As Moodle gains in maturity, its directions are increasingly influenced by \r
- the community of developers and users. A dynamic database of proposed features \r
- and their status can be found at <a target=_top href="http://moodle.org/bugs/">moodle.org/bugs</a>. \r
- Your <a href="?file=credits.html">contributions</a> in the form of ideas, code, \r
- feedback and promotion are all very welcome - see the <a href="?file=developer.html">Developers \r
- manual</a> for more details.</p>\r
-\r
-<p>Here is a rough map of the future (subject to change): \r
-<dl>\r
-\r
- <dt>Version 1.2 - Late 2003</dt>\r
- <dd>The major targets for this version include:\r
- <ul>\r
- <li>Support for groups/cohorts within courses</li>\r
- <li>New architecture for Enrolments with plugins (similar to the \r
- existing Authentication architecture) so that\r
- external systems (eg Student Records, Paypal, LDAP etc) \r
- can control student access within courses</li>\r
- <li>Miscellaneous contributed code and bug fixes</li>\r
- </ul>\r
- </dd>\r
-\r
-<dt>Version 2.0 - Early 2004</dt>\r
-<dd>This major release will include some major changes in internal structure\r
- designed to add flexibility and scalability in many areas. Among the major \r
- targets are:\r
- <ul>\r
- <li> Rewritten display layer using XHTML-compatible code and complete implementation \r
- of templates for increased standards-compliance, flexibility and accessibility </li>\r
- <li> Wider use of PHP classes in key areas of the Moodle code, to make some \r
- things easier for programmers writing new modules or integrating with \r
- external systems</li>\r
- <li> Stronger pedagogical support for both teachers and students </li>\r
- <li> New access-control system allowing finely-defined roles and rights</li>\r
- <li> Basic support for IMS and SCORM </li>\r
- <li> Better integration of Moodle with moodle.org</li>\r
- <li> Whatever else comes along :-) </li>\r
- </ul>\r
-</dd>\r
-</dl>\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
+<head>
+
+<title>Moodle Docs: Future</title>
+
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body bgcolor="#FFFFFF">
+
+<h1>Future</h1>
+<blockquote>
+ <p>As Moodle gains in maturity, its directions are increasingly influenced by
+ the community of developers and users. A dynamic database of proposed features
+ and their status can be found at <a target=_top href="http://moodle.org/bugs/">moodle.org/bugs</a>.
+ Your <a href="?file=credits.html">contributions</a> in the form of ideas, code,
+ feedback and promotion are all very welcome - see the <a href="?file=developer.html">Developers
+ manual</a> for more details.</p>
+ <p>Here is our current vision of the future, though this always changes depending on what developers want to work on.
+</p>
+ <h3>Version 1.2 - Late 2003
+</h3>
+ <blockquote>
+ <p>The main targets for this version include:
+ </p>
+ <ul>
+ <li>Support for groups/cohorts within courses</li>
+ <li>New module: Glossary</li>
+ <li>New module: Attendance</li>
+ <li>New module: Webquest</li>
+ <li>Text filters, where all text can be parsed by plugins</li>
+ </ul>
+ </blockquote>
+ <p> </p>
+ <h3>Version 2.0 - Early 2004</h3>
+ <blockquote>
+ <p>This major release will include some major changes in internal structure
+ designed to add flexibility and scalability in many areas. Among the major
+ targets are:</p>
+ <ul>
+ <li> Completely rewritten display layer using XHTML-compatible code and complete implementation
+ of templates for increased standards-compliance, flexibility and accessibility </li>
+ <li> Wider use of PHP classes in key areas of the Moodle code, to make some
+ things easier for programmers writing new modules or integrating with
+ external systems</li>
+ <li>New architecture for Enrolments with plugins (similar to the
+ existing Authentication architecture) so that
+ external systems (eg Student Records, Paypal, LDAP etc)
+ can control student and teacher access within courses</li>
+ </ul>
+ </blockquote>
+ <h3>Version 2.1 - Early 2004</h3>
+ <blockquote>
+ <p>This release will start to take advantage of the new structuring and add new features such as:</p>
+ <ul>
+ <li>New access-control system allowing finely-defined roles and rights
+</li>
+ <li> Stronger pedagogical support for both teachers and students </li>
+ <li>Basic support for standard learning objects (SCORM content packages)</li>
+ <li>Better integration of Moodle with moodle.org (for teachers to share and collaborate)</li>
+ </ul>
+ </blockquote>
+ <p align="CENTER"> </p>
+</blockquote>
+<p align="CENTER"> </p>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
+++ /dev/null
-<html>
-
-<head><title>Moodle Docs: Glossary</title>
-
-<link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">
-
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-
-<style type="text/css">
-
-<!--
-
-.question {
-
- font-size: medium;
-
- font-weight: bold;
-
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;
-
- border: 1px dotted;
-
- padding: 10px;
-
- background-color: #EEEEEE;
-
-}
-
-.answer {
-
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;
-
- font-size: medium;
-
- border: none;
-
- padding-left: 40px;
-
-}
-
--->
-
-</style>
-
-<style type="text/css">
-
-<!--
-
-.normaltext {
-
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;
-
- font-size: medium;
-
- border: none;
-
- padding-left: 10px;
-
-}
-
-.answercode {
-
- font-family: "Courier New", Courier, mono;
-
- font-size: small;
-
- border: none;
-
- padding-left: 60px;
-
-}
-
-.questionlink {
-
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;
-
- font-size: medium;
-
- border: none;
-
- padding-left: 40px;
-
-}
-
--->
-
-</style>
-
-</head>
-
-
-
-<body bgcolor="#ffffff">
-
-<h2><a name="pagetop">Glossary</a></h2>
-
-<p class="normaltext">This page contains a number of definitions for many of the words and
-
-expressions you may encounter while working with Moodle.</p>
-
-<p class="normaltext">If you don't find the answer here try the <a href="http://moodle.org/mod/forum/index.php?id=5">Using
-
- Moodle</a> course on moodle.org, and search the forums for keywords. You may
-
- have to try a few different search phrases before you find a resolution.</p>
-
-<p class="normaltext">If you still can't find any answers then we can recommend <a href="http://google.com/">Google</a>, or try posting your question
-
- on the appropriate forum in <a href="http://moodle.org/mod/forum/index.php?id=5">Using
-
- Moodle</a> - someone should be able to help you.</p>
-
-
-
-
-
-<h3 class="question"><a name="active-x"></a>Active-X</h3>
-
-<p class="answer">A method of scripting (controlling) certain functions in a web page, used only by Microsoft Internet Explorer.</p>
-
-
-
-<h3 class="question"><a name="applet"></a>applet</h3>
-
-<p class="answer">Most recent browsers can run these small programs if the <a href="#java">Java</a> feature in the browser has been enabled.</p>
-
-
-
-<h3 class="question"><a name="ascii"></a>ASCII</h3>
-
-<p class="answer">American Standard Code for Information Interchange</p>
-
-<p class="answer">Certain file types require that you upload in ASCII mode when using your <a href="#ftp">FTP</a> program.
-
-It's usually best to choose " AUTO " in your FTP settings. </p>
-
-
-
-<h3 class="question"><a name="binary"></a>binary</h3>
-
-<p class="answer">Certain file types require that you upload in binary mode when
-
-using your <a href="#ftp">FTP</a> program. It's usually best to choose " AUTO " in your FTP settings.</p>
-
-
-
-<h3 class="question"><a name="css"></a>Cascading Style Sheets</h3>
-
-<p class="answer">Please see <a href="#css">CSS</a> below.</p>
-
-
-
-<h3 class="question"><a name="css"></a>CSS</h3>
-
-<p class="answer">Abbreviation for "Cascading Style Sheets".
-
-CSS is used as a template to make it easier to update the look (style) of many
-
-web pages at the same time and CSS also makes it possible to have several pages
-
-that all follow a similar theme. </p>
-
-
-
-<h3 class="question"><a name="cvs"></a>CVS</h3>
-
-<p class="answer">Concurrent Versioning System is simply a method of storing files
-
-on a <a href="#server">server</a> that helps coordinate many people working on those files. To "check out" files from a CVS server means to copy the very latest versions to your own computer.</p>
-
-
-
-<h3 class="question"><a name="database"></a>database</h3>
-
-<p class="answer"> An electronic collection of information, stored in tables of data. For example, Moodle contains a table of all users in a site. MySQL is a brand of database software.</p>
-
-
-
-<h3 class="question"><a name="dataroot"></a>dataroot</h3>
-
-<p class="answer">The place where Moodle can save uploaded files. This
-
-directory should be readable and writeable by the web server user
-
-but it should not be accessible directly via the web.</p>
-
-
-
-<h3 class="question"><a name="domainname"></a>domain name</h3>
-
-<p class="answer">A name given to a computer or a group of computers. eg moodle.org You can buy new domain names on the Internet.</p>
-
-
-
-<h3 class="question"><a name="download"></a>download</h3>
-
-<p class="answer">To move your files from a
-
-<a href="#server">server</a> "down" to your personal computer. Also see <a href="#ftp">FTP</a> and <a href="#upload">upload</a>.</p>
-
-
-
-<h3 class="question"><a name="directory"></a>directory</h3>
-
-<p class="answer">Please see <a href="#dirroot">dirroot</a></p>
-
-
-
-<h3 class="question"><a name="dirroot"></a>dirroot</h3>
-
-<p class="answer">A root directory has content and a name. This root directory may contain
-
-several sub-directories and the name is the location on your <a href="#server">server</a>
-
-where your Moodle files will reside after you <a href="#upload">upload</a> them.</p>
-
-
-
-<h3 class="question"><a name="ftp"></a>FTP</h3>
-
-<p class="answer">File Transfer Protocol - a method of copying files from one
-
-computer to another. For example, you might FTP your Moodle files from your
-
-home computer to your web <a href="#server">server</a></p>
-
-
-
-<h3 class="question"><a name="hostingprovider"></a>hosting provider</h3>
-
-<p class="answer">A business that will host your web site for a monthly fee.
-
-You provide a <a href="#domainname">domain name</a> that you own, and after they've set
-
-it up for you, then you can copy your files to their server and set up your site.</p>
-
-
-
-<h3 class="question"><a name="html"></a>html</h3>
-
-<p class="answer">HyperText Markup Language - a language used to create web pages.</p>
-
-
-
-<h3 class="question"><a name="index"></a>index</h3>
-
-<p class="answer">When a web address specifies a directory (eg http://yoursite.com/moodle/) instead of a file (eg http://yoursite.com/moodle/index.php), then the web server needs to assume the name of the file. The files it looks for to use in this case are called the index files.</p>
-
-
-
-<h3 class="question"><a name="java"></a>Java</h3>
-
-<p class="answer">A programming language that can be used to write applets that may run within web pages. Moodle doesn't use any of it.</p>
-
-
-
-<h3 class="question"><a name="javascript"></a>javascript</h3>
-
-<p class="answer">A scripting language that can be used to write small programs in web pages, such as popup menus. Moodle uses a little Javascript.</p>
-
-
-
-<h3 class="question"><a name="moodle"></a>Moodle</h3>
-
-<p class="answer">The word <a href="http://www.moodle.org/">Moodle</a> is an acronym for
-
-Modular Object-Oriented Dynamic Learning Environment</p>
-
-
-
-<h3 class="question"><a name="mysql"></a>MySQL</h3>
-
-<p class="answer"> MySQL is the world's most popular open source database,
-
- recognized for its speed and reliability.</p>
-
-
-
-<h3 class="question"><a name="nightly"></a>nightly</h3>
-
-<p class="answer">A Moodle Nightly is built automatically every day from the most recent code, and is available from the Moodle web site. It can be useful if you don't have CVS, but you want to try the latest features. It can also contain bugs, since they haven't been well-tested.</p>
-
-
-
-<h3 class="question"><a name="php"></a>PHP</h3>
-
-<p class="answer">PHP is a server-side scripting language which executes commands on
-
-the server side then delivers dynamic HTML pages to the web browser. Your server
-
-must be PHP enabled in order to run Moodle.</p>
-
-
-
-<h3 class="question"><a name="server"></a>server</h3>
-
-<p class="answer">This is where your web site or <a href="#database">database</a>,
-
-or both, resides. You may choose to run your own server or have a
-
-<a href="#hostingprovider">hosting provider</a> look after this for you. </p>
-
-
-
-<h3 class="question"><a name="stylesheet"></a>style sheet</h3>
-
-<p class="answer">Please see <a href="#css">CSS</a> above.</p>
-
-
-
-<h3 class="question"><a name="upload"></a>upload</h3>
-
-<p class="answer">To upload is simply to move your files from your computer
-
-to a <a href="#server">server</a>. Also see <a href="#ftp">FTP</a>.</p>
-
-
-
-<h3 class="question"><a name="url"></a>URL</h3>
-
-<p class="answer">A Uniform Resource Locator is the address that is used to
-
-reach a website.</p>
-
-
-
-<h3 class="question"><a name="xhtml"></a>XHTML - Extensible Hypertext Markup Language</h3>
-
-<p class="answer">XHTML will, eventually, replace HTML as the language used
-
-to program web pages for display in your web browser. XHTML will, hopefully,
-
-make writing code for browsers easier as XHTML code will cause the page to display
-
-exactly the same in any web browser.</p>
-
-
-
-<h3 class="question"><a name="xml"></a>XML</h3>
-
-<p class="answer">Extensible Mark-up Language is just what the name implies, extensible.
-
-The programmer has a very wide latitude when writing XML as the programmer may
-
-choose to add instructions as she/he writes. This is in direct opposition to
-
-HTML which has a clearly defined and documented set of instructions available and
-
-no freedom exists to " extend " this set of rules. Due to its' extreme
-
-versatility XML may be the end of the evolutionary path for HTML. also see
-
-<a href="#xhtml">XHTML</a>
-
-
-
-
-
-
-
-<p align="center" class="normaltext"><a href="#pagetop">Page Top</a></p>
-
-
-
-<hr>
-
-<p align="right"><strong><em>Maintained by John Eyre. Please send suggestions to captain@eyrespace.com.</em></strong></p>
-
-<hr>
-
-
-
-<p align="center"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
-
-<p align="center"><font size="1">Version: $Id$</font></p>
-
-
-
-</body></html>
-
-<head>\r
- <title>Moodle Docs: Installation</title>\r
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
-<!--\r
-.sectionheading {\r
- font-size: medium;\r
- font-weight: bold;\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- border: 1px dotted;\r
- padding: 10px;\r
- background-color: #EEEEEE;\r
-}\r
--->\r
-</style>\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 class="sectionheading"><a name="requirements"></a>1. Requirements</h3>\r
-<blockquote> \r
- <p>Moodle is primarily developed in Linux using Apache, MySQL and PHP (also \r
- sometimes known as the LAMP platform), but is also regularly tested with PostgreSQL \r
- and on Windows XP, Mac OS X and Netware 6 operating systems</p>\r
- <p>The requirements for Moodle are as follows:</p>\r
- <ol>\r
- <li>Web server software. Most people use <a href="http://www.apache.org/" target="_blank">Apache</a>, \r
- but Moodle should work fine under any web server that supports PHP, such \r
- as IIS on Windows platforms.</li>\r
- <li><a href="http://www.php.net/" target="_blank">PHP</a> scripting language (version 4.1.0 \r
- or later), with the following settings: \r
- <ul>\r
- <li><a href="http://www.boutell.com/gd/" target="_blank">GD library</a> \r
- turned ON, with support for JPG and PNG formats</li>\r
- <li>zlib library turned ON (if you want to use backup/restore on Windows)</li>\r
- <li>Sessions support turned ON</li>\r
- <li>File uploading turned ON</li>\r
- <li>Safe Mode must be turned OFF (see the forums on moodle.org for problems \r
- caused by Safe Mode)</li>\r
- </ul>\r
- </li>\r
- <li>a working database server: <a href="http://www.mysql.com/" target="_blank">MySQL</a> \r
- or <a href="http://www.postgresql.org/" target="_blank">PostgreSQL</a> are \r
- completely supported and recommended for use with Moodle 1.1. All other \r
- databases will be supported fully in the next release.</li>\r
- </ol>\r
- <p>Most web hosts support all of this by default. If you are signed up with \r
- one of the few webhosts that does not support these features ask them why, \r
- and consider taking your business elsewhere.</p>\r
- <p>If you want to run Moodle on your own computer and all this looks a bit daunting, \r
- then please see our guide: <a href="http://moodle.org/doc/?file=installamp.html">Installing \r
- Apache, MySQL and PHP</a>. It provides some step-by-step instructions to install \r
- all this on most popular platforms.</p>\r
-<p> </p></blockquote>\r
-<h3 class="sectionheading"><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: <a href="http://moodle.org/download/" target="_blank">http://moodle.org/download/</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 class="sectionheading"><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 class="sectionheading"><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 class="sectionheading"><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 - you can do all this via a web interface).</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 class="sectionheading"><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, <b>if you are using Apache 2</b>, then you should turn on the <i>AcceptPathInfo</i>\r
- variable, which allows scripts to be passed arguments like http://server/file.php/arg1/arg2.\r
- This is essential to allow relative links between your resources, and also \r
- provides a performance boost for people using your Moodle web site. You can \r
- turn this on by adding these lines to your httpd.conf file.</p>\r
- <blockquote>\r
- <pre><strong>AcceptPathInfo</strong> on </pre>\r
- </blockquote>\r
-\r
- <p>Thirdly, 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
-\r
-<pre>magic_quotes_gpc = 1 (preferred but not necessary)\r
-magic_quotes_runtime = 0 (necessary)\r
-file_uploads = 1\r
-session.auto_start = 0\r
-session.bug_compat_warn = 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 settings, \r
- then don't worry, you can still OVERRIDE all of the default settings. \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
-\r
-<IfDefine APACHE2>\r
- <b>AcceptPathInfo</b> on\r
-</IfDefine>\r
-\r
-php_flag magic_quotes_gpc 1\r
-php_flag magic_quotes_runtime 0\r
-php_flag file_uploads 1\r
-php_flag session.auto_start 0\r
-php_flag session.bug_compat_warn 0</pre></blockquote>\r
- <p>You can also do things like define the maximum size for uploaded files:\r
- <blockquote><pre>\r
-LimitRequestBody 0\r
-php_value upload_max_filesize 2M\r
-php_value post_max_size 2M\r
- </pre></blockquote>\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 class="sectionheading"><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 <strong>config-dist.php</strong> and name it \r
- config.php. We do this so that your config.php won't be overwritten in case \r
- you upgrade Moodle later on. </p>\r
- <p>Edit <strong>config.php</strong> to specify the database details that you \r
- just defined (including a table prefix - notice that this is REQUIRED for \r
- PostgreSQL), as well as the site address, file system directory and data directory. \r
- The config file itself has detailed directions and examples.</p>\r
- <p>Once you have done this the rest of the installation is via a web interface. \r
- 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 class="sectionheading"><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 "shrinkwrap" agreement with which you must agree before you \r
- can continue with the setup.</p>\r
- <p>(Moodle will also try to set some cookies in your browser. If you have your \r
- browser set up to let you choose to accept cookies, then you <b>must</b> accept \r
- the Moodle cookies, or Moodle won't work properly.) \r
- <p>Now Moodle will start setting up your database and creating tables to store \r
- data. Firstly, the main database tables are created. You should see a number \r
- of SQL statements followed by status messages (in green or red) that look \r
- 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="#006600">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 sometimes have safe mode \r
- turned 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 \r
- try 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 <font color="#006600">green</font>.</p>\r
- <p>Scroll down the very bottom of the page and press the "Continue" \r
- link.</p>\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 to \r
- the bottom and click "Save changes".</p>\r
- <p>If (and only if) you find yourself getting stuck on this page, unable to \r
- continue, then your server probably has what I call the "buggy referrer" problem. \r
- This is easy to fix: just turn off the "secureforms" setting, then \r
- try to continue again.</p>\r
- <p>The next page is a form where you can define parameters for your Moodle site \r
- and the front page, such as the name, format, description and so on. Fill \r
- this out (you can always come back and change these later) and then press \r
- "Save changes".</p>\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>(If for any reason your install is interrupted, or there is a system error \r
- of some kind that prevents you from logging in using the admin account, you \r
- can usually log in using the default username of "<strong>admin</strong>", \r
- with password "<strong>admin</strong>".)</p>\r
- <p>Once successful, you will be returned to home page of your site. Note the \r
- administration links that appear down the left hand side of the page (these \r
- items also appear on a separate Admin page) - these items are only visible \r
- to you because 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 class="sectionheading"><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 or ten 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 \r
- hosting service that does not have cron, then you can might choose to run \r
- cron on another server or on your home computer. All that matters is that \r
- the cron.php file is called regularly. </p>\r
- <p>The load of this script is not very high, so 5 minutes is usually reasonable, \r
- but if you're worried about it you can reduce the time period to something \r
- like 15 minutes or even 30 minutes. It's best not to make the time period \r
- too long, as delaying mail-outs can slow down activity within the course.</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><b>On Unix systems</b>: 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>Usually, the "crontab" command will put you into the 'vi' editor. You enter \r
- "insert mode" by pressing "i", then type in the line as above, then exit insert mode by \r
- pressing ESC. You save and exit by typing ":wq", or quit with saving using ":q!" (without the quotes).</p>\r
-\r
- <p><b>On Windows systems</b>: The simplest way is to use this little package <a href="http://moodle.org/download/moodle-cron-for-windows.zip" title="Click to download this package (150k)" target="_blank">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>On web hosts: Your web-based control panel may have a web page that allows \r
- you to set up this cron process. Ask your administrator for details on how \r
- it works.</p>\r
- <p></p>\r
-</blockquote>\r
-<h3 class="sectionheading"><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
+<head>
+
+<title>Moodle Docs: Installation</title>
+
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body bgcolor="#FFFFFF">
+<h1>Installing Moodle</h1>
+<blockquote>
+ <p>This guide explains how to install Moodle for the first time. It goes into some detail
+ about some of the steps, in order to cover the wide variety of small differences between
+ web server setups, so this document may look long and complicated. Don't be put off by this
+ - I usually set Moodle up in a few minutes!</p>
+ <p>Take your time and work through this document carefully - it will save you time later on.</p>
+ <p>Sections in this document:</p>
+ <ol>
+ <li><a href="#requirements">Requirements</a></li>
+ <li><a href="#downloading">Download</a></li>
+ <li><a href="#site">Site structure</a></li>
+ <li><a href="#data">Create a data directory</a></li>
+ <li><a href="#database">Create a database</a></li>
+ <li><a href="#webserver">Check web server settings</a></li>
+ <li><a href="#config">Edit config.php</a></li>
+ <li><a href="#admin">Go to the admin page</a></li>
+ <li><a href="#cron">Set up cron</a></li>
+ <li><a href="#course">Create a new course</a></li>
+ </ol>
+ <p> </p>
+</blockquote>
+<h3 class="sectionheading"><a name="requirements"></a>1. Requirements</h3>
+<blockquote>
+ <p>Moodle is primarily developed in Linux using Apache, MySQL and PHP (also
+ sometimes known as the LAMP platform), but is also regularly tested with PostgreSQL
+ and on Windows XP, Mac OS X and Netware 6 operating systems</p>
+ <p>The requirements for Moodle are as follows:</p>
+ <ol>
+ <li>Web server software. Most people use <a href="http://www.apache.org/" target="_blank">Apache</a>,
+ but Moodle should work fine under any web server that supports PHP, such
+ as IIS on Windows platforms.</li>
+ <li><a href="http://www.php.net/" target="_blank">PHP</a> scripting language (version 4.1.0
+ or later), with the following settings:
+ <ul>
+ <li><a href="http://www.boutell.com/gd/" target="_blank">GD library</a>
+ turned ON, with support for JPG and PNG formats</li>
+ <li>zlib library turned ON (if you want to use backup/restore on Windows)</li>
+ <li>Sessions support turned ON</li>
+ <li>File uploading turned ON</li>
+ <li>Safe Mode must be turned OFF (see the forums on moodle.org for problems
+ caused by Safe Mode)</li>
+ </ul>
+ </li>
+ <li>a working database server: <a href="http://www.mysql.com/" target="_blank">MySQL</a>
+ or <a href="http://www.postgresql.org/" target="_blank">PostgreSQL</a> are
+ completely supported and recommended for use with Moodle 1.1. All other
+ databases will be supported fully in the next release.</li>
+ </ol>
+ <p>Most web hosts support all of this by default. If you are signed up with
+ one of the few webhosts that does not support these features ask them why,
+ and consider taking your business elsewhere.</p>
+ <p>If you want to run Moodle on your own computer and all this looks a bit daunting,
+ then please see our guide: <a href="http://moodle.org/doc/?file=installamp.html">Installing
+ Apache, MySQL and PHP</a>. It provides some step-by-step instructions to install
+ all this on most popular platforms.</p>
+ <p> </p>
+</blockquote>
+<h3 class="sectionheading"><a name="downloading"></a>2. Download</h3>
+<blockquote>
+ <p>There are two ways to get Moodle, as a compressed package and via CVS. These
+ are explained in detail on the download page: <a href="http://moodle.org/download/" target="_blank">http://moodle.org/download/</a></p>
+ <p>After downloading and unpacking the archive, or checking out the files via
+ CVS, you will be left with a directory called "moodle", containing
+ a number of files and folders. </p>
+ <p>You can either place the whole folder in your web server documents directory,
+ in which case the site will be located at <b>http://yourwebserver.com/moodle</b>,
+ or you can copy all the contents straight into the main web server documents
+ directory, in which case the site will be simply <b>http://yourwebserver.com</b>.</p>
+</blockquote>
+<p> </p>
+<h3 class="sectionheading"><a name="site"></a>3. Site structure</h3>
+<blockquote>
+ <p>Here is a quick summary of the contents of the Moodle folder, to help get
+ you oriented:</p>
+ <blockquote>
+ <p>config.php - the ONLY file you need to edit to get started<br>
+ version.php - defines the current version of Moodle code<br>
+ index.php - the front page of the site</p>
+ <ul>
+ <li>admin/ - code to administrate the whole server </li>
+ <li>auth/ - plugin modules to authenticate users </li>
+ <li>course/ - code to display and manage courses </li>
+ <li>doc/ - help documentation for Moodle (eg this page)</li>
+ <li>files/ - code to display and manage uploaded files</li>
+ <li>lang/ - texts in different languages, one directory per language </li>
+ <li>lib/ - libraries of core Moodle code </li>
+ <li>login/ - code to handle login and account creation </li>
+ <li>mod/ - all Moodle course modules</li>
+ <li>pix/ - generic site graphics</li>
+ <li>theme/ - theme packs/skins to change the look of the site.</li>
+ <li>user/ - code to display and manage users</li>
+ </ul>
+ <p> </p>
+ </blockquote>
+</blockquote>
+<h3 class="sectionheading"><a name="data"></a>4. Create a data directory</h3>
+<blockquote>
+ <p>Moodle will also need some space on your hard disk to store uploaded files,
+ such as course documents and user pictures.</p>
+ <p>Create a directory for this purpose somewhere. For security, it's best that
+ this directory is NOT accessible directly via the web. The easiest way to do this
+ is to simply locate it OUTSIDE the web directory, otherwise protect it
+ by creating a file in the data directory called .htaccess, containing this line:
+ <blockquote>
+
+ <pre>deny from all</pre>
+ </blockquote>
+ <p>To make sure that Moodle can save uploaded files in this directory, check that
+ the web server software (eg Apache) has permission to write
+ to this directory. On Unix machines, this means setting the owner of the directory
+ to be something like "nobody" or "apache".</p>
+ <p>On many shared hosting servers, you will probably need to restrict all file access
+ to your "group" (to prevent other webhost customers from looking at or changing your files),
+ but provide full read/write access to everyone else (which will allow the web server
+ to access your files). Speak to your server administrator if you are having
+ trouble setting this up securely.</p>
+</blockquote>
+<p> </p>
+<h3 class="sectionheading"><a name="database"></a>5. Create a database</h3>
+<blockquote>
+ <p>You need to create an empty database (eg "moodle") in your database system
+ along with a special user (eg "moodleuser") that has access to that database
+ (and that database only). You could use the "root" user if you wanted to, but
+ this is not recommended for a production system: if hackers manage to discover
+ the password then your whole database system would be at risk, rather than
+ just one database.
+</p>
+ <p>Example command lines for MySQL: </p>
+ <pre>
+ # mysql -u root -p
+ > CREATE DATABASE moodle;
+ > GRANT SELECT,INSERT,UPDATE,DELETE,CREATE,DROP,INDEX,ALTER ON moodle.*
+ TO moodleuser@localhost IDENTIFIED BY 'yourpassword';
+ > quit
+ # mysqladmin -p reload
+</pre>
+ <p>Example command lines for PostgreSQL: </p>
+ <pre>
+ # su - postgres
+ > psql -c "create user moodleuser createdb;" template1
+ > psql -c "create database moodle;" -U moodleuser template1
+ > psql -c "alter user moodleuser nocreatedb;" template1
+</pre>
+ <p>(For MySQL I highly recommend the use of <a href="http://phpmyadmin.sourceforge.net/">phpMyAdmin</a>
+ to manage your databases - you can do all this via a web interface).</p>
+ <p>As of version 1.0.8, Moodle now supports table prefixes, and so can safely share
+ a database with tables from other applications.</p>
+</blockquote>
+<p> </p>
+<h3 class="sectionheading"><a name="webserver" id="webserver"></a>6. Check your web server settings</h3>
+<blockquote>
+ <p>Firstly, make sure that your web server is set up to use index.php as a default
+ page (perhaps in addition to index.html, default.htm and so on).</p>
+ <p>In Apache, this is done using a DirectoryIndex parameter in your httpd.conf
+ file. Mine usually looks like this:</p>
+ <blockquote>
+ <pre><strong>DirectoryIndex</strong> index.php index.html index.htm </pre>
+ </blockquote>
+ <p>Just make sure index.php is in the list (and preferably towards the start
+ of the list, for efficiency).</p>
+ <p>Secondly, <b>if you are using Apache 2</b>, then you should turn on the <i>AcceptPathInfo</i>
+ variable, which allows scripts to be passed arguments like http://server/file.php/arg1/arg2.
+ This is essential to allow relative links between your resources, and also
+ provides a performance boost for people using your Moodle web site. You can
+ turn this on by adding these lines to your httpd.conf file.</p>
+ <blockquote>
+ <pre><strong>AcceptPathInfo</strong> on </pre>
+ </blockquote>
+ <p>Thirdly, Moodle requires a number of PHP settings to be active for it to
+ work. <b>On most servers these will already be the default settings.</b>
+ However, some PHP servers (and some of the more recent PHP versions) may
+ have things set differently. These are defined in PHP's configuration
+ file (usually called php.ini):</p>
+ <blockquote>
+
+ <pre>magic_quotes_gpc = 1 (preferred but not necessary)
+magic_quotes_runtime = 0 (necessary)
+file_uploads = 1
+session.auto_start = 0
+session.bug_compat_warn = 0
+</pre>
+ </blockquote>
+ <p>If you don't have access to httpd.conf or php.ini on your server, or you
+ have Moodle on a server with other applications that require different settings,
+ then don't worry, you can still OVERRIDE all of the default settings.
+ <p>To do this, you need to create a file called <b>.htaccess</b> in Moodle's
+ main directory that contains definitions for these settings.
+ This only works on Apache servers and only when Overrides have been allowed.
+
+ <blockquote>
+ <pre>
+DirectoryIndex index.php index.html index.htm
+
+<IfDefine APACHE2>
+ <b>AcceptPathInfo</b> on
+</IfDefine>
+
+php_flag magic_quotes_gpc 1
+php_flag magic_quotes_runtime 0
+php_flag file_uploads 1
+php_flag session.auto_start 0
+php_flag session.bug_compat_warn 0</pre>
+ </blockquote>
+ <p>You can also do things like define the maximum size for uploaded files:
+
+ <blockquote>
+ <pre>
+LimitRequestBody 0
+php_value upload_max_filesize 2M
+php_value post_max_size 2M
+ </pre>
+ </blockquote>
+ <p>The easiest thing to do is just copy the sample file from lib/htaccess
+ and edit it to suit your needs. It contains further instructions. For
+ example, in a Unix shell:
+ <blockquote>
+ <pre>cp lib/htaccess .htaccess</pre>
+ </blockquote>
+</blockquote>
+<p> </p>
+<h3 class="sectionheading"><a name="config"></a>7. Edit config.php</h3>
+<blockquote>
+ <p>Now you can edit the configuration file, <strong>config.php</strong>, using a
+ text editor. This file is used by all other files in Moodle.</p>
+ <p>To start with, make a copy of <strong>config-dist.php</strong> and name it
+ config.php. We do this so that your config.php won't be overwritten in case
+ you upgrade Moodle later on. </p>
+ <p>Edit <strong>config.php</strong> to specify the database details that you
+ just defined (including a table prefix - notice that this is REQUIRED for
+ PostgreSQL), as well as the site address, file system directory and data directory.
+ The config file itself has detailed directions and examples.</p>
+ <p>Once you have done this the rest of the installation is via a web interface.
+ For the rest of this installation document we will assume your site is at:
+ <u>http://example.com/moodle</u></p>
+</blockquote>
+<p> </p>
+<h3 class="sectionheading"><a name="admin"></a>8. Go to the admin page</h3>
+<blockquote>
+ <p>The admin page should now be working at: <u>http://example.com/moodle/admin</u>.
+ If you try and access the front page of your site you'll be taken there automatically
+ anyway. The first time you access this admin page, you will be presented with
+ a GPL "shrinkwrap" agreement with which you must agree before you
+ can continue with the setup.</p>
+ <p>(Moodle will also try to set some cookies in your browser. If you have your
+ browser set up to let you choose to accept cookies, then you <b>must</b> accept
+ the Moodle cookies, or Moodle won't work properly.)
+ <p>Now Moodle will start setting up your database and creating tables to store
+ data. Firstly, the main database tables are created. You should see a number
+ of SQL statements followed by status messages (in green or red) that look
+ like this:</p>
+ <blockquote>
+ <p>CREATE TABLE course ( id int(10) unsigned NOT NULL auto_increment, category
+ int(10) unsigned NOT NULL default '0', password varchar(50) NOT NULL default
+ '', fullname varchar(254) NOT NULL default '', shortname varchar(15) NOT
+ NULL default '', summary text NOT NULL, format tinyint(4) NOT NULL default
+ '1', teacher varchar(100) NOT NULL default 'Teacher', startdate int(10)
+ unsigned NOT NULL default '0', enddate int(10) unsigned NOT NULL default
+ '0', timemodified int(10) unsigned NOT NULL default '0', PRIMARY KEY (id))
+ TYPE=MyISAM</p>
+ <p><font color="#006600">SUCCESS</font></p>
+ <p>...and so on, followed by: <font color="#006600">Main databases set up
+ successfully.</font> </p>
+ </blockquote>
+ <p>If you don't see these, then there must have been some problem with the database
+ or the configuration settings you defined in config.php. Check that PHP isn't
+ in a restricted "Safe Mode" (commercial web hosts sometimes have safe mode
+ turned on). You can check PHP variables by creating a little file containing
+ <? phpinfo() ?> and looking at it through a browser. Check all these and
+ try this page again.</p>
+ <p>Scroll down the very bottom of the page and press the "Continue"
+ link.</p>
+ <p>Next you will see a similar page that sets up all the tables required by
+ each Moodle module. As before, they should all be <font color="#006600">green</font>.</p>
+ <p>Scroll down the very bottom of the page and press the "Continue"
+ link.</p>
+ <p>You should now see a form where you can define more configuration variables
+ for your installation, such as the default language, SMTP hosts and so on.
+ Don't worry too much about getting everything right just now - you can always
+ come back and edit these later on using the admin interface. Scroll down to
+ the bottom and click "Save changes".</p>
+ <p>If (and only if) you find yourself getting stuck on this page, unable to
+ continue, then your server probably has what I call the "buggy referrer" problem.
+ This is easy to fix: just turn off the "secureforms" setting, then
+ try to continue again.</p>
+ <p>The next page is a form where you can define parameters for your Moodle site
+ and the front page, such as the name, format, description and so on. Fill
+ this out (you can always come back and change these later) and then press
+ "Save changes".</p>
+ <p>Finally, you will then be asked to create a top-level administration user
+ for future access to the admin pages. Fill out the details with your own name,
+ email etc and then click "Save changes". Not all the fields are
+ required, but if you miss any important fields you'll be re-prompted for them.
+ </p>
+ <blockquote>
+ <blockquote>
+ <blockquote>
+ <blockquote>
+ <blockquote>
+ <p><strong>Make sure you remember the username and password you chose
+ for the administration user account, as they will be necessary to
+ access the administration page in future.</strong></p>
+ </blockquote>
+ </blockquote>
+ </blockquote>
+ </blockquote>
+ </blockquote>
+ <p>(If for any reason your install is interrupted, or there is a system error
+ of some kind that prevents you from logging in using the admin account, you
+ can usually log in using the default username of "<strong>admin</strong>",
+ with password "<strong>admin</strong>".)</p>
+ <p>Once successful, you will be returned to home page of your site. Note the
+ administration links that appear down the left hand side of the page (these
+ items also appear on a separate Admin page) - these items are only visible
+ to you because you are logged in as the admin user. All your further administration
+ of Moodle can now be done using this menu, such as:</p>
+ <ul>
+ <li>creating and deleting courses</li>
+ <li>creating and editing user accounts</li>
+ <li>administering teacher accounts</li>
+ <li>changing site-wide settings like themes etc</li>
+ </ul>
+</blockquote>
+<p> </p>
+<h3 class="sectionheading"><a name="cron"></a>9. Set up cron</h3>
+<blockquote>
+ <p>Some of Moodle's modules require continual checks to perform tasks. For example,
+ Moodle needs to check the discussion forums so it can mail out copies of posts
+ to people who have subscribed.</p>
+ <p>The script that does all this is located in the admin directory, and is called
+ cron.php. However, it can not run itself, so you need to set up a mechanism
+ where this script is run regularly (eg every five or ten minutes). This provides
+ a "heartbeat" so that the script can perform functions at periods
+ defined by each module.</p>
+ <p>Note that the machine performing the cron <b>does not need to be the same
+ machine that is running Moodle</b>. For example, if you have a limited web
+ hosting service that does not have cron, then you can might choose to run
+ cron on another server or on your home computer. All that matters is that
+ the cron.php file is called regularly. </p>
+ <p>The load of this script is not very high, so 5 minutes is usually reasonable,
+ but if you're worried about it you can reduce the time period to something
+ like 15 minutes or even 30 minutes. It's best not to make the time period
+ too long, as delaying mail-outs can slow down activity within the course.</p>
+ <p>First, test that the script works by running it directly from your browser:</p>
+ <blockquote>
+ <pre>http://example.com/moodle/admin/cron.php</pre>
+ </blockquote>
+ <p>Now, you need to set up some of way of running the script automatically and
+ regularly. </p>
+ <h4> Running the script from a command line</h4>
+ <p>You can call the page from the command line just as you did in the example
+ above. For example, you can use a Unix utility like 'wget':</p>
+ <blockquote>
+ <pre>wget -q -O /dev/null http://example.com/moodle/admin/cron.php</pre>
+ </blockquote>
+ <p>Note in this example that the output is thrown away (to /dev/null).</p>
+ <p>The same thing using lynx:</p>
+ <blockquote>
+ <pre>lynx -dump http://example.com/moodle/admin/cron.php > /dev/null</pre>
+ </blockquote>
+ <p>Alternatively you could use a standalone version of PHP, compiled to be run
+ on the command line. The advantage with doing this is that your web server
+ logs aren't filled with constant requests to cron.php. The disadvantage is
+ that you need to have access to a command-line version of php.</p>
+ <blockquote>
+ <pre>/opt/bin/php /web/moodle/admin/cron.php
+
+
+(Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php
+
+</pre>
+ </blockquote>
+ <h4>Automatically running the script every 5 minutes</h4>
+ <p><b>On Unix systems</b>: Use <b>cron</b>. Edit your cron settings from the commandline
+ using "crontab -e" and add a line like:</p>
+ <blockquote>
+ <pre>*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php</pre>
+ </blockquote>
+ <p>Usually, the "crontab" command will put you into the 'vi' editor. You enter
+ "insert mode" by pressing "i", then type in the line as above, then exit insert mode by
+ pressing ESC. You save and exit by typing ":wq", or quit with saving using ":q!" (without the quotes).</p>
+ <p><b>On Windows systems</b>: The simplest way is to use this little package <a href="http://moodle.org/download/moodle-cron-for-windows.zip" title="Click to download this package (150k)" target="_blank">moodle-cron-for-windows.zip</a>
+ which makes this whole thing very easy. You can also explore using the built-in
+ Windows feature for "Scheduled Tasks".</p>
+ <p>On web hosts: Your web-based control panel may have a web page that allows
+ you to set up this cron process. Ask your administrator for details on how
+ it works.</p>
+ <p></p>
+</blockquote>
+<h3 class="sectionheading"><a name="course"></a>10. Create a new course</h3>
+<blockquote>
+ <p>Now that Moodle is running properly, you can create a course. </p>
+ <p>Select "Create a new course" from the Admin page (or the admin
+ links on the home page).</p>
+ <p>Fill out the form, paying special attention to the course format. You don't
+ have to worry about the details too much at this stage, as everything can
+ be changed later by the teacher.</p>
+ <p>Press "Save changes", and you will be taken to a new form where
+ you can assign teachers to the course. You can only add existing user accounts
+ from this form - if you want to create a new teacher account then either ask
+ the teacher to create one for themselves (see the login page), or create one
+ for them using the "Add a new user" on the Admin page.</p>
+ <p>Once done, the course is ready to customise, and is accessible via the "Courses"
+ link on the home page.</p>
+ <p>See the "<a href="./?file=teacher.html">Teacher Manual</a>" for more details
+ on course-building.</p>
+</blockquote>
+<p> </p>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
-<head>\r
- <title>Moodle Docs: Installing PHP and MySQL</title>\r
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
- <!--\r
- .sectionheading {\r
- font-size: medium;\r
- font-weight: bold;\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- border: 1px dotted;\r
- padding: 10px;\r
- background-color: #EEEEEE;\r
- }\r
- -->\r
- </style>\r
-</head>\r
-\r
-<body bgcolor="#FFFFFF">\r
-<h2>Installing Apache, MySQL and PHP</h2>\r
-<p>Moodle is written in a scripting language called PHP, and stores most of its \r
- data in a database. The database we recommend is MySQL. Before installing Moodle \r
- you must have a working PHP installation and a working database to turn your \r
- computer into a functional web server platform. These packages can be tricky \r
- to set up for average computer users, so this page has been written to try to \r
- make this process as simple as possible for different platforms:</p>\r
-<ul>\r
- <li><a href="#host" class="questionlink">Hosting Service</a></li>\r
- <li><a href="#mac" class="questionlink">Mac OS X</a></li>\r
- <li><a href="#redhat" class="questionlink">Redhat Linux</a></li>\r
- <li><a href="#windows" class="questionlink">Windows</a></li>\r
-</ul>\r
-<p class="questionlink"> </p>\r
-<h3 class="sectionheading"><a name="host" id="host"></a>Hosting Service</h3>\r
-<blockquote> \r
- <p>Unfortunately hosting services vary quite a lot in the way they work. Some \r
- will even install Moodle for you.</p>\r
- <p>Most will offer a web-based control panel to control your site, create databases \r
- and set up cron. Some may also offer terminal access via ssh, so that you \r
- can use the command shell to do things.</p>\r
- <p>You should work your way through the <a href="./?file=install.html">Installation \r
- guide</a> and take each step at a time. Ask your hosting provider if you get \r
- stuck. </p>\r
- <p> </p>\r
-</blockquote>\r
-<h3 class="sectionheading"><a name="mac" id="mac"></a>Mac OS X</h3>\r
-<blockquote> \r
- <p>The easiest way to do this is use the Apache server that Apple provides, \r
- and add PHP and MySQL using Marc Liyanage's packages. Both of the pages below \r
- come with good instructions that we won't duplicate here:</p>\r
- <blockquote> \r
- <p><strong>PHP</strong>: Download from here: <a href="http://www.entropy.ch/software/macosx/php/" target="_top">http://www.entropy.ch/software/macosx/php/</a></p>\r
- <p><strong>MySQL</strong>: Download here: <a href="http://www.entropy.ch/software/macosx/mysql/" target="_top">http://www.entropy.ch/software/macosx/mysql/</a></p>\r
- </blockquote>\r
- <p>Once these are installed the standard <a href="./?file=install.html">Installation \r
- guide</a> should be fairly straightforward.</p>\r
- <p>A more detailed walkthrough is here: <a href="http://moodle.org/wiki/index.php/InstallingMoodle">http://moodle.org/wiki/index.php/InstallingMoodle</a></p>\r
- <p> </p>\r
-</blockquote>\r
-<h3 class="sectionheading"><a name="redhat"></a>Redhat Linux</h3>\r
-<blockquote> \r
- <p>You should install all available RPM packages for Apache, PHP and MySQL. \r
- One package that people frequently forget is the php-mysql package which is \r
- necessary for PHP to talk to MySQL.</p>\r
- <p>Once these are installed the standard <a href="./?file=install.html">Installation \r
- guide</a> should be fairly straightforward.</p>\r
- <p>A more detailed walkthrough is here: <a href="http://moodle.org/wiki/index.php/InstallingMoodle">http://moodle.org/wiki/index.php/InstallingMoodle</a></p>\r
-</blockquote>\r
-<p> </p>\r
-<h3 class="sectionheading"><a name="windows" id="windows"></a>Windows</h3>\r
-<blockquote> \r
- <p>The easiest way to do this is use <a href="http://www.easyphp.org/" target="_blank">EasyPHP</a>, \r
- a package that bundles all the software you need into a single Windows application. \r
- Here are the steps from start to finish:</p>\r
- <ol>\r
- <li> Firstly, if you have ever installed MySQL before (even as part of another \r
- package), uninstall it all, delete all the MySQL files and make sure you \r
- delete <strong>c:\my.cnf</strong> and <strong>c:\windows\my.ini</strong>.You \r
- might want to do a search and delete ANY file called <strong>my.cnf</strong> \r
- or <strong>my.ini</strong>.</li>\r
- <li> If you've ever installed PHP before delete any files called <strong>php4ts.dll</strong> \r
- from around your Windows directory, as well as any files called <strong>php.ini</strong>.</li>\r
- <li> Download EasyPHP from here: <a href="http://www.easyphp.org/telechargements/dn.php?F=easyphp1-6.php3" target="_blank">http://www.easyphp.org/telechargements/dn.php?F=easyphp1-6.php3</a> \r
- (approx 10 Mb)</li>\r
- <li> Run the downloaded file: <strong>easyphp1-6_setup.exe</strong>. The installation \r
- process is in French but is otherwise much like installing any other Windows \r
- program - I advise accepting the defaults and letting it all install. Note \r
- that "Suivant" means Next.and "Oui" means Yes.</li>\r
- <li>At the end of the install leave the checkbox selected to "Lancer \r
- EasyPHP" (Start EasyPHP) and hit the 'Terminer" button.You might \r
- be taken to a information web page which you can safely ignore. </li>\r
- <li>If all went well - congratulations! Apache, PHP and MySQL are all installed \r
- and running! You should see a black E in your toolbar tray. You can right \r
- click on it to get a menu which will let you control the running programs, \r
- but you won't be needing that for now.</li>\r
- <li> The next thing you need to do is to set up a database for Moodle to use. \r
- Using a browser, go to <a href="http://localhost/mysql/" target="_blank">http://localhost/mysql/</a> \r
- (note the final slash).</li>\r
- <li>If asked for a username, use "root" with a blank password. You \r
- should see a phpMyAdmin web interface that allows you to create a new databases \r
- and user accounts. </li>\r
- <li>Create a new database by typing "moodle" into the field and \r
- hitting the "Create" button. That was easy!</li>\r
- <li>You can also create a new user to access your database if you want. This \r
- can be a bit tricky for a first-time user, so you might just want to use \r
- the existing user "root" with no password in your Moodle config \r
- for now, and fix this later.</li>\r
- <li> You're ready to install Moodle! Download the latest release of Moodle \r
- from <a href="http://moodle.org/download" target="_blank">http://moodle.org/download</a>, \r
- then unzip the archive.</li>\r
- <li>Copy your moodle files into <strong>C:\Program Files\EasyPHP\www. </strong>You \r
- can either copy the entire moodle directory (ie C:\Program Files\EasyPHP\www\moodle) \r
- or copy all the <em>contents</em> of the moodle directory. If you choose \r
- this second option then you will be able to access your Moodle home page \r
- using http://localhost/ instead of http://localhost/moodle/.</li>\r
- <li> Make a new empty folder somewhere else for Moodle to store uploaded files \r
- in, eg: <strong>C:\moodledata</strong></li>\r
- <li> Go into your Moodle folder. Make a copy of config-dist.php, and call \r
- it config.php</li>\r
- <li> Edit config.php using a text editor (Notepad will do, just be careful \r
- that it doesn't add unwanted spaces at the end). </li>\r
- <li>Put in all your new database info:<br>\r
- $CFG->dbtype = 'mysql';<br>\r
- $CFG->dbhost = 'localhost';<br>\r
- $CFG->dbname = 'moodle';<br>\r
- $CFG->dbuser = 'root'; <br>\r
- $CFG->dbpass = '';<br>\r
- $CFG->dbpersist = true;<br>\r
- $CFG->prefix = 'mdl_';<br>\r
- </li>\r
- <li>And put in all your file paths:<br>\r
- $CFG->wwwroot = 'http://localhost/moodle'; // Use an external address \r
- if you know it. <br>\r
- $CFG->dirroot = 'C:\Program Files\EasyPHP\www\moodle'; <br>\r
- $CFG->dataroot = 'C:\moodledata';<br>\r
- </li>\r
- <li>Save config.php - you can ignore the other settings if there are any.</li>\r
- <li>You're nearly there now! The rest of the setup is all web-based. Visit \r
- <a href="http://localhost/moodle/admin/" target="_blank">http://localhost/moodle/admin/</a> \r
- with your browser to continue the setup via your browser.</li>\r
- <li>To use zip files with Moodle (for example the backups use zip) you might \r
- need to enable "zlib". You can do this by going to your EasyPHP \r
- directory (<strong>C:\Program Files\EasyPHP</strong>), and running the program \r
- phpini.exe in there. Put a mark in the checkbox next to "zlib.dll". \r
- Close that window, then go to the black E in your toolbar and right-click \r
- it to get a menu - select "Restart" from this menu.</li>\r
- <li>Lastly, you need to set up some sort of cron. See the <a href="./?file=install.html">Installation \r
- guide</a> for more details on this.</li>\r
- </ol>\r
- <p>If you don't or can't use EasyPHP, here are some a few tips to make sure \r
- your PHP is set up correctly and avoid common problems:</p>\r
- <ul>\r
- <li>Make sure you enable the GD module so Moodle can process images - you \r
- may have to edit php.ini and remove the comment (;) from this line: 'extension=php_gd2.dll'. \r
- </li>\r
- <li>Make sure you enable the Zlib module so that you can create and unpack \r
- zip files from within Moodle.</li>\r
- <li>Make sure sessions is turned on - you may have to edit php.ini and fix \r
- the directory for <strong>session.save_path</strong> - instead of the default \r
- "/tmp" use a Windows directory like "c:/temp".</li>\r
- </ul>\r
-</blockquote>\r
-<h3> </h3>\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
+<head>
+ <title>Moodle Docs: Installing PHP and MySQL</title>
+ <link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body bgcolor="#FFFFFF">
+<h1>Installing Apache, MySQL and PHP</h1>
+<blockquote>
+ <p>Moodle is written in a scripting language called PHP, and stores most of its
+ data in a database. The database we recommend is MySQL. Before installing Moodle
+ you must have a working PHP installation and a working database to turn your
+ computer into a functional web server platform. These packages can be tricky
+ to set up for average computer users, so this page has been written to try to
+ make this process as simple as possible for different platforms:</p>
+ <ul>
+ <li><a href="#host" class="questionlink">Hosting Service</a></li>
+ <li><a href="#mac" class="questionlink">Mac OS X</a></li>
+ <li><a href="#redhat" class="questionlink">Redhat Linux</a></li>
+ <li><a href="#windows" class="questionlink">Windows</a></li>
+ </ul>
+ <p class="questionlink"> </p>
+ <h3 class="sectionheading"><a name="host" id="host"></a>Hosting Service</h3>
+ <blockquote>
+ <p>Unfortunately hosting services vary quite a lot in the way they work. Some
+ will even install Moodle for you.</p>
+ <p>Most will offer a web-based control panel to control your site, create databases
+ and set up cron. Some may also offer terminal access via ssh, so that you
+ can use the command shell to do things.</p>
+ <p>You should work your way through the <a href="./?file=install.html">Installation
+ guide</a> and take each step at a time. Ask your hosting provider if you get
+ stuck. </p>
+ <p> </p>
+ </blockquote>
+ <h3 class="sectionheading"><a name="mac" id="mac"></a>Mac OS X</h3>
+ <blockquote>
+ <p>The easiest way to do this is use the Apache server that Apple provides,
+ and add PHP and MySQL using Marc Liyanage's packages. Both of the pages below
+ come with good instructions that we won't duplicate here:</p>
+ <blockquote>
+ <p><strong>PHP</strong>: Download from here: <a href="http://www.entropy.ch/software/macosx/php/" target="_top">http://www.entropy.ch/software/macosx/php/</a></p>
+ <p><strong>MySQL</strong>: Download here: <a href="http://www.entropy.ch/software/macosx/mysql/" target="_top">http://www.entropy.ch/software/macosx/mysql/</a></p>
+ </blockquote>
+ <p>Once these are installed the standard <a href="./?file=install.html">Installation
+ guide</a> should be fairly straightforward.</p>
+ <p>A more detailed walkthrough is here: <a href="http://moodle.org/wiki/index.php/InstallingMoodle">http://moodle.org/wiki/index.php/InstallingMoodle</a></p>
+ <p> </p>
+ </blockquote>
+ <h3 class="sectionheading"><a name="redhat"></a>Redhat Linux</h3>
+ <blockquote>
+ <p>You should install all available RPM packages for Apache, PHP and MySQL.
+ One package that people frequently forget is the php-mysql package which is
+ necessary for PHP to talk to MySQL.</p>
+ <p>Once these are installed the standard <a href="./?file=install.html">Installation
+ guide</a> should be fairly straightforward.</p>
+ <p>A more detailed walkthrough is here: <a href="http://moodle.org/wiki/index.php/InstallingMoodle">http://moodle.org/wiki/index.php/InstallingMoodle</a></p>
+ </blockquote>
+ <p> </p>
+ <h3 class="sectionheading"><a name="windows" id="windows"></a>Windows</h3>
+ <blockquote>
+ <p>The easiest way to do this is use <a href="http://www.easyphp.org/" target="_blank">EasyPHP</a>,
+ a package that bundles all the software you need into a single Windows application.
+ Here are the steps from start to finish:</p>
+ <ol>
+ <li> Firstly, if you have ever installed MySQL before (even as part of another
+ package), uninstall it all, delete all the MySQL files and make sure you
+ delete <strong>c:\my.cnf</strong> and <strong>c:\windows\my.ini</strong>.You
+ might want to do a search and delete ANY file called <strong>my.cnf</strong>
+ or <strong>my.ini</strong>.</li>
+ <li> If you've ever installed PHP before delete any files called <strong>php4ts.dll</strong>
+ from around your Windows directory, as well as any files called <strong>php.ini</strong>.</li>
+ <li> Download EasyPHP from here: <a href="http://www.easyphp.org/telechargements/dn.php?F=easyphp1-6.php3" target="_blank">http://www.easyphp.org/telechargements/dn.php?F=easyphp1-6.php3</a>
+ (approx 10 Mb)</li>
+ <li> Run the downloaded file: <strong>easyphp1-6_setup.exe</strong>. The installation
+ process is in French but is otherwise much like installing any other Windows
+ program - I advise accepting the defaults and letting it all install. Note
+ that "Suivant" means Next.and "Oui" means Yes.</li>
+ <li>At the end of the install leave the checkbox selected to "Lancer
+ EasyPHP" (Start EasyPHP) and hit the 'Terminer" button.You might
+ be taken to a information web page which you can safely ignore. </li>
+ <li>If all went well - congratulations! Apache, PHP and MySQL are all installed
+ and running! You should see a black E in your toolbar tray. You can right
+ click on it to get a menu which will let you control the running programs,
+ but you won't be needing that for now.</li>
+ <li> The next thing you need to do is to set up a database for Moodle to use.
+ Using a browser, go to <a href="http://localhost/mysql/" target="_blank">http://localhost/mysql/</a>
+ (note the final slash).</li>
+ <li>If asked for a username, use "root" with a blank password. You
+ should see a phpMyAdmin web interface that allows you to create a new databases
+ and user accounts. </li>
+ <li>Create a new database by typing "moodle" into the field and
+ hitting the "Create" button. That was easy!</li>
+ <li>You can also create a new user to access your database if you want. This
+ can be a bit tricky for a first-time user, so you might just want to use
+ the existing user "root" with no password in your Moodle config
+ for now, and fix this later.</li>
+ <li> You're ready to install Moodle! Download the latest release of Moodle
+ from <a href="http://moodle.org/download" target="_blank">http://moodle.org/download</a>,
+ then unzip the archive.</li>
+ <li>Copy your moodle files into <strong>C:\Program Files\EasyPHP\www. </strong>You
+ can either copy the entire moodle directory (ie C:\Program Files\EasyPHP\www\moodle)
+ or copy all the <em>contents</em> of the moodle directory. If you choose
+ this second option then you will be able to access your Moodle home page
+ using http://localhost/ instead of http://localhost/moodle/.</li>
+ <li> Make a new empty folder somewhere else for Moodle to store uploaded files
+ in, eg: <strong>C:\moodledata</strong></li>
+ <li> Go into your Moodle folder. Make a copy of config-dist.php, and call
+ it config.php</li>
+ <li> Edit config.php using a text editor (Notepad will do, just be careful
+ that it doesn't add unwanted spaces at the end). </li>
+ <li>Put in all your new database info:<br>
+ $CFG->dbtype = 'mysql';<br>
+ $CFG->dbhost = 'localhost';<br>
+ $CFG->dbname = 'moodle';<br>
+ $CFG->dbuser = 'root'; <br>
+ $CFG->dbpass = '';<br>
+ $CFG->dbpersist = true;<br>
+ $CFG->prefix = 'mdl_';</li>
+ <li>And put in all your file paths:<br>
+ $CFG->wwwroot = 'http://localhost/moodle'; // Use an external address
+ if you know it. <br>
+ $CFG->dirroot = 'C:\Program Files\EasyPHP\www\moodle'; <br>
+ $CFG->dataroot = 'C:\moodledata';</li>
+ <li>Save config.php - you can ignore the other settings if there are any.</li>
+ <li>You're nearly there now! The rest of the setup is all web-based. Visit
+ <a href="http://localhost/moodle/admin/" target="_blank">http://localhost/moodle/admin/</a>
+ with your browser to continue the setup via your browser.</li>
+ <li>To use zip files with Moodle (for example the backups use zip) you might
+ need to enable "zlib". You can do this by going to your EasyPHP
+ directory (<strong>C:\Program Files\EasyPHP</strong>), and running the program
+ phpini.exe in there. Put a mark in the checkbox next to "zlib.dll".
+ Close that window, then go to the black E in your toolbar and right-click
+ it to get a menu - select "Restart" from this menu.</li>
+ <li>Lastly, you need to set up some sort of cron. See the <a href="./?file=install.html">Installation
+ guide</a> for more details on this.</li>
+ </ol>
+ <p>If you don't or can't use EasyPHP, here are some a few tips to make sure
+ your PHP is set up correctly and avoid common problems:</p>
+ <ul>
+ <li>Make sure you enable the GD module so Moodle can process images - you
+ may have to edit php.ini and remove the comment (;) from this line: 'extension=php_gd2.dll'.
+ </li>
+ <li>Make sure you enable the Zlib module so that you can create and unpack
+ zip files from within Moodle.</li>
+ <li>Make sure sessions is turned on - you may have to edit php.ini and fix
+ the directory for <strong>session.save_path</strong> - instead of the default
+ "/tmp" use a Windows directory like "c:/temp".</li>
+ </ul>
+ <p> </p>
+ </blockquote>
+</blockquote>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+
+</body>
</html>
\ No newline at end of file
-<!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
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\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/edmedia2003/" target="_top">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" target="_top"> \r
- Open Source</a> software (under the <a href="http://www.gnu.org/copyleft/gpl.html" target="_top"> \r
- GNU Public License</a>). Basically this means Moodle is copyrighted, but that \r
- you have additional freedoms. You are allowed to copy, use and modify Moodle \r
- provided that you agree to: <strong>provide the source to others</strong>; <strong>not \r
- modify or remove the original license and copyrights</strong>, and <strong>apply \r
- this same license to any derivative work</strong>. Read the license for full \r
- details and please contact the <a href="http://moodle.org/user/view.php?id=1&course=1">copyright \r
- holder</a> directly if you have any questions. \r
-<p>Moodle will run on any computer that can run <a href="http://www.php.net/" target="_top"> \r
- PHP</a>, and can support many types of database (particularly <a href="http://www.mysql.com/" target="_top">MySQL</a>).</p>\r
-\r
-<p>The word Moodle was originally an acronym for Modular Object-Oriented Dynamic \r
- Learning Environment, which is mostly useful to programmers and education theorists. \r
- It's also a verb that describes the process of lazily meandering through something, \r
- doing things as it occurs to you to do them, an enjoyable tinkering that often \r
- leads to insight and creativity. As such it applies both to the way Moodle was \r
- developed, and to the way a student or teacher might approach studying or teaching \r
- an online course. Anyone who uses Moodle is a Moodler.</p>\r
-<p>Come and <a href="http://moodle.org/community/" target="_top">moodle with us</a>!</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
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+<title>Moodle Docs: Introduction</title>
+
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body bgcolor="#ffffff">
+
+<h1>Introduction</h1>
+<blockquote>
+ <p>Moodle is a software package for producing internet-based courses and web sites.
+ It's an ongoing development project designed to support a <a href="?file=philosophy.html">social constructionist</a> framework of education. </p>
+ <p>Moodle is provided freely as <a href="http://www.opensource.org/docs/definition_plain.html" target="_top">
+ Open Source</a> software (under the <a href="http://www.gnu.org/copyleft/gpl.html" target="_top">
+ GNU Public License</a>). Basically this means Moodle is copyrighted, but that
+ you have additional freedoms. You are allowed to copy, use and modify Moodle
+ provided that you agree to: <strong>provide the source to others</strong>; <strong>not
+ modify or remove the original license and copyrights</strong>, and <strong>apply
+ this same license to any derivative work</strong>. Read the license for full
+ details and please contact the <a href="http://moodle.org/user/view.php?id=1&course=1">copyright
+ holder</a> directly if you have any questions.
+</p>
+ <p>Moodle will run on any computer that can run <a href="http://www.php.net/" target="_top">
+ PHP</a>, and can support many types of database (particularly <a href="http://www.mysql.com/" target="_top">MySQL</a>).</p>
+ <p>The word Moodle was originally an acronym for Modular Object-Oriented Dynamic
+ Learning Environment, which is mostly useful to programmers and education theorists.
+ It's also a verb that describes the process of lazily meandering through something,
+ doing things as it occurs to you to do them, an enjoyable tinkering that often
+ leads to insight and creativity. As such it applies both to the way Moodle was
+ developed, and to the way a student or teacher might approach studying or teaching
+ an online course. Anyone who uses Moodle is a Moodler.</p>
+ <p>Come and <a href="http://moodle.org/community/" target="_top">moodle with us</a>!</p>
+</blockquote>
+<p><br>
+</p>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
-<!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
- <meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">\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
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+<title>Moodle Docs: Copyright License</title>
+
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body bgcolor="#ffffff">
+
+<h1>Copyright License for Moodle</h1>
+<blockquote>
+ <p>Moodle is Copyright © 2001-2003, <a href="http://dougiamas.com/">Martin
+ Dougiamas</a>.</p>
+ <p>This program is free software; you can redistribute it and/or modify<br>
+ it under the terms of the GNU General Public License as published by<br>
+ the Free Software Foundation; either version 2 of the License, or<br>
+ (at your option) any later version.</p>
+ <p>This program is distributed in the hope that it will be useful,<br>
+ but WITHOUT ANY WARRANTY; without even the implied warranty of<br>
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br>
+ GNU General Public License for more details (attached below).<br>
+ </p>
+ <hr width="100%" size="2">
+ <br>
+
+ <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>
+</blockquote>
+
+
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
-<html>\r
-<head>\r
-<title>Moodle Docs: Frequently Asked Questions (FAQ)</title>\r
-<link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
-<style type="text/css">\r
-<!--\r
-.question {\r
- font-size: medium;\r
- font-weight: bold;\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- border: 1px dotted;\r
- padding: 10px;\r
- background-color: #EEEEEE;\r
-}\r
-.answer {\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- font-size: medium;\r
- border: none;\r
- padding-left: 40px;\r
-}\r
--->\r
-</style>\r
-<style type="text/css">\r
-<!--\r
-.normaltext {\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- font-size: medium;\r
- border: none;\r
- padding-left: 10px;\r
-}\r
-.answercode {\r
- font-family: "Courier New", Courier, mono;\r
- font-size: small;\r
- border: none;\r
- padding-left: 60px;\r
-}\r
-.questionlink {\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- font-size: medium;\r
- border: none;\r
- padding-left: 40px;\r
-}\r
--->\r
-</style>\r
-</head>\r
-\r
-<body bgcolor="#FFFFFF">\r
-<h2>Other documentation</h2>\r
-<p class="normaltext">Here are some links to other sources of Moodle documentation:</p>\r
-<p class="normaltext"><a href="../help.php?file=index.html">Index of all Moodle \r
- help pages</a> - a list of all the context-sensitive help files within Moodle</p>\r
-<p class="normaltext"><a href="http://moodle.org/docs/">User-contributed documentation</a> \r
- - this page lists documentation contributed by Moodle users</p>\r
-<p align="center" class="normaltext"> </p>\r
-<hr>\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
+<html>
+<head>
+<title>Moodle Docs: Frequently Asked Questions (FAQ)</title>
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body bgcolor="#FFFFFF">
+<h1>Other documentation</h1>
+<p class="normaltext">Here are some links to other sources of Moodle documentation:</p>
+<p class="normaltext"><a href="../help.php?file=index.html">Index of all Moodle
+ help pages</a> - a list of all the context-sensitive help files within Moodle</p>
+<p class="normaltext"><a href="http://moodle.org/docs/">User-contributed documentation</a>
+ - this page lists documentation contributed by Moodle users</p>
+<p align="center" class="normaltext"> </p>
+<hr>
+
+<p align="center"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="center"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+<title>Moodle Docs: Philosophy</title>
+
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body bgcolor="#ffffff">
+
+<h1>Philosophy</h1>
+
+<blockquote>
+ <p>The design and development of Moodle is guided by a particular philosophy of learning, a way of thinking that you may see referred to in shorthand as a "<em>social constructionist pedagogy</em>". (Some of you Physics teachers may already be thinking "soft education mumbo jumbo" and reaching for the mouse, but please read on - this is useful for every subject area!)</p>
+ <p>This page tries to explain in simple terms what that phrase means by unpacking <strong>four main concepts</strong> behind it. Note that each of these is summarising one view of an immense amount of diverse research so these definitions will seem thin if you have read about these before.</p>
+ <p>If these concepts are completely new to you then it is likely that these ideas will be hard to understand at first - all I can recommend is that you read it carefully, while thinking about your own experiences of trying to learn something.<br>
+ </p>
+ <h3>1. Constructivism</h3>
+ <blockquote>
+ <p>This point of view maintains that people actively <strong>construct</strong> new knowledge as they interact with their environment. </p>
+ <p>Everything you read, see, hear, feel, and touch is tested against your prior knowledge and if it is viable within your mental world, may form new knowledge you carry with you. Knowledge is strengthened if you can use it successfully in your wider environment. You are not just a memory bank passively absorbing information, nor can knowledge be "transmitted" to you just by reading something or listening to someone.</p>
+ <p>This is not to say you can't learn anything from reading a web page or watching a lecture, obviously you can, it's just pointing out that there is more interpretation going on than a transfer of information from one brain to another.<br>
+ </p>
+ </blockquote>
+ <h3>2. Constructionism</h3>
+ <blockquote>
+ <p>Constructionism asserts that learning is particularly effective when constructing something for others to experience. This can be anything from a spoken sentence or an internet posting, to more complex artifacts like a painting, a house or a software package.</p>
+ <p>For example, you might read this page several times and still forget it by tomorrow - but if you were to try and explain these ideas to someone else in your own words, or produce a slideshow that explained these concepts, then I can guarantee you'd have a better understanding that is more integrated into your own ideas. This is why people take notes during lectures, even if they never read the notes again.<br>
+ </p>
+ </blockquote>
+ <h3>3. Social Constructivism</h3>
+ <blockquote>
+ <p>This extends the above ideas into a social group constructing things for one another, collaboratively creating a small culture of shared artifacts with shared meanings. When one is immersed within a culture like this, one is learning all the time about how to be a part of that culture, on many levels.</p>
+ <p>A very simple example is an object like a cup. The object can be used for many things, but its shape does suggest some "knowledge" about carrying liquids. A more complex example is an online course - not only do the "shape" of the software tools indicate certain things about the way online courses should work, but the activities and texts produced within the group as a whole will help shape how each person behaves within that group.<br>
+ </p>
+ </blockquote>
+ <h3>4. Connected and Separate</h3>
+ <blockquote>
+ <p>This idea looks deeper into the motivations of individuals within a discussion. <strong>Separate</strong> behaviour is when someone tries to remain 'objective' and 'factual', and tends to defend their own ideas using logic to find holes in their opponent's ideas. <strong>Connected</strong> behaviour is a more empathic approach that accepts subjectivity, trying to listen and ask questions in an effort to understand the other point of view. <strong>Constructed</strong> behaviour is when a person is sensitive to both of these approaches and is able to choose either of them as appropriate to the current situation.</p>
+ <p>In general, a healthy amount of connected behaviour within a learning community is a very powerful stimulant for learning, not only bringing people closer together but promoting deeper reflection and re-examination of their existing beliefs.</p>
+ </blockquote>
+ <hr>
+ <p>Once you are thinking about all these issues, it helps you to focus on the experiences that would be best for learning from the learner's point of view, rather than just publishing and assessing the information you think they need to know. It can also help you realise how each participant in a course can be a teacher as well as a learner. Your job as a 'teacher' can change from being 'the source of knowledge' to being an influencer and role model of class culture, connecting with students in a personal way that addresses their own learning needs, and moderating discussions and activities in a way that collectively leads students towards the learning goals of the class.</p>
+ <p>Obviously Moodle doesn't force this style of behaviour, but this is what it is best at supporting. In future, as the technical infrastructure of Moodle stabilises, further improvements in pedagogical support will be a major direction for Moodle development.</p>
+</blockquote>
+<hr>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+</body>
+</html>
-<head>\r
- <title>Moodle Docs: Release notes</title>\r
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
- dt {font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif; font-weight: bold;}\r
- dd {margin-bottom:1em;} \r
- </style>\r
-</head>\r
-\r
-<body bgcolor="#FFFFFF">\r
-<h2>Release notes</h2>\r
-\r
-<h3> New in Moodle 1.1.1 (10 September, 2003):</h3>\r
-\r
-<ul>\r
- <dl>\r
- <dt> </dt>\r
- <dt>General Fixes</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li>Translation improvements in many languages</li>\r
- <li>Frame fix when switching languages in documentation</li>\r
- <li>All short PHP tags removed ... short_tags is no longer a requirement</li>\r
- <li>Forum search results link using anchor tag for better context</li>\r
- <li>Removed target from "delete" link on user editing page</li>\r
- <li>'Search' on social format moved closer to the top to prevent browser \r
- self-scrolling </li>\r
- <li>Page redirection is faster and no longer causes intermediate page \r
- to be stored in IE history</li>\r
- <li>Course listings improved when courses are displayed, including more \r
- information</li>\r
- <li>Category listings show courses in full when there are under ten courses</li>\r
- <li>Invisible courses are always shown last in My Courses</li>\r
- <li>Course creators can now see all hidden categories and courses</li>\r
- <li>Styles added for category and course names</li>\r
- <li>Removed tags from question text on quiz 'simplestat' report</li>\r
- <li>Added percentages to downloaded data from 'simplestat' report</li>\r
- <li>Allow external deep linking using guest account ?username=guest</li>\r
- <li>Any admin can now add/remove course creators</li>\r
- <li>Primary admin can now update own username/password even with external authentication</li>\r
- <li>Quizzes can now be specified as having "no grade" and no grades will be shown</li>\r
- <li>When editing a language, missing strings files are created if possible</li>\r
- <li>Fixed bug in weekly journal date calculations</li>\r
- <li>Fixed bug in config.php that made error_reporting not work</li>\r
- <li>Fixed bug when editing user name with quotes in it</li>\r
- <li>Fixed bug in email obfuscation for email addresses with numbers in \r
- them </li>\r
- <li>Fixed missing PostgreSQL schema for chat module</li>\r
- <li>Fixed several typos in PostgreSQL upgrading code</li>\r
- <li>Fixed some uninitialised variables</li>\r
- <li>Several bugs fixed in Workshop module</li>\r
- </ul>\r
- </dd>\r
- </dl>\r
-</ul>\r
-\r
-<hr>\r
-\r
-\r
-\r
-<h3> New in Moodle 1.1 (28 August, 2003):</h3>\r
-<ul>\r
- <dl>\r
- <dt> </dt>\r
- <dt>Major Changes</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li>A completely new <strong>backup</strong> system for backup and restore \r
- of courses (Thanks, Eloy!)</li>\r
- <li>A new <strong>workshop</strong> module for peer grading (Thanks, Ray!)</li>\r
- <li>A new <strong>chat</strong> module for synchronous discussions</li>\r
- <li>All-new <strong>course manager</strong> to handle very large numbers \r
- of courses (tested with 3700)</li>\r
- <li>Custom-defined <strong>grading scales</strong> that can be used throughout \r
- a course</li>\r
- <li>Performance improvements in many areas</li>\r
- </ul>\r
- </dd>\r
- </dl>\r
- <dl>\r
- <dt>General</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li>Clean up of the whole admin menu organisation to make it clearer</li>\r
- <li>Categories can be nested and sorted alphabetically or manually</li>\r
- <li>Courses and whole categories can be hidden from students</li>\r
- <li>Course descriptions and names can be searched for keywords</li>\r
- <li>Large categories are now completely paged</li>\r
- <li>Improved web caching for stylesheets and images</li>\r
- <li>"My courses" display on the home page when logged in.</li>\r
- <li>Inclusion of non-linked page to display ALL user pictures at once \r
- (see /userpix)</li>\r
- <li>The "secureforms" feature now defaults to OFF.</li>\r
- <li>Moodle now doesn't care if "magic quotes" is on or off.</li>\r
- <li>Images in /pix were rearranged and tidied up</li>\r
- <li>HTML email is better formatted for wider compatibility</li>\r
- <li>Mail bounces are now sent to the admin user</li>\r
- <li>Better cron tasks (less CPU used) and duplicate enrolments are now \r
- cleaned</li>\r
- <li>Improved display of logs with infinite paging and increased flexibility</li>\r
- <li>User log graphs now work at site-level (showing ALL logs on the site)</li>\r
- <li>People with manual accounts can now recover their password</li>\r
- <li>Improved system for defining/printing help files for major activity \r
- modules</li>\r
- <li>Activity modules can now have settings</li>\r
- <li>Email addresses are all completely obfuscated (to fool web spiders)</li>\r
- <li>There is now an index to the help files</li>\r
- <li>Library (Mark Kimes' add-on) is now supported if it is installed (see Moodle contrib for Library source)</li>\r
- </ul>\r
- </dd>\r
- </dl>\r
- <dl>\r
- <dt></dt>\r
- <dt>Courses</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li>Teachers can now have their course editing privileges removed</li>\r
- <li>Teachers can now manually enrol students if they want to</li>\r
- <li>Teacher management is now all combined in one interface</li>\r
- <li>Activities can be moved any distance with two clicks</li>\r
- <li>Topics/weeks can now be moved up and down</li>\r
- <li>Pop-up menu to quickly switch between topics/weeks when collapsed</li>\r
- <li>When self-enrolling, students are notified and given a chance to cancel</li>\r
- <li>Teachers and students see list of "My Courses" on course \r
- home pages.</li>\r
- <li>Grades can be hidden from students if not needed</li>\r
- </ul>\r
- </dd>\r
- </dl>\r
- <dl>\r
- <dt></dt>\r
- <dt>Languages</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li><strong>Hungarian</strong> and <strong>Greek</strong> have been added, \r
- and there are lots of other updates. As usual, the language packs within \r
- this release may not be fully completed yet. You can always download \r
- the newest language packs from <a href="http://moodle.org/download/lang/">http://moodle.org/download/lang/</a>.</li>\r
- <li>Updates and fixes to most languages</li>\r
- <li>Languages now have a parent language (for displaying missing strings)</li>\r
- <li>Some fixes for locales and time display in several languages</li>\r
- <li>es_mx is being phased out in favour of "es" (International \r
- Spanish) </li>\r
- </ul>\r
- </dd>\r
- </dl>\r
- <dl>\r
- <dt></dt>\r
- <dt>Forum</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li>Much improved searching, with multiple keywords, paging etc</li>\r
- <li>Forum grading can be either off, used by everyone, or used only by teachers</li>\r
- <li>Forum grading can use custom scales or numbers</li>\r
- <li>A date range can be set to restrict the posts that can be graded.</li>\r
- <li>Admin now has access to some settings via Admin -> Modules -> Forums </li>\r
- <li>After editing a post, user is returned to post in context</li>\r
- <li>Attached images are displayed inline</li>\r
- <li>Email copies in plain text format now print URLs nicely</li>\r
- </ul>\r
- </dd>\r
- </dl>\r
- <dl>\r
- <dt>Quiz</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li>New question type: Embedded Answers (Cloze) - allows text passages \r
- with embedded answers</li>\r
- <li>New question type: Numerical - allows a range of numerical answers \r
- to be entered</li>\r
- <li>New question type: Description - not a real question, it allows text/graphics \r
- to be inserted anywhere</li>\r
- <li>Expanded quiz reporting with modular report plugins</li>\r
- <li>New feature for repeat attempts, where each attempt builds on the \r
- last </li>\r
- <li>If the quiz is closing within the next 24 hours, a small countdown \r
- clock is shown in the title bar and alerts warn at ten minutes and zero \r
- minutes.</li>\r
- <li>Some refactoring to the quiz code to make it easier to extend with \r
- new question types</li>\r
- </ul>\r
- </dd>\r
- </dl>\r
- <dl>\r
- <dt></dt>\r
- <dt>Resources</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li>Web links can now be in very customisable pop-up windows.</li>\r
- <li>Admin now has access to some settings via Admin -> Modules -> \r
- Resources</li>\r
- </ul>\r
- </dd>\r
- </dl>\r
- <dl>\r
- <dt>Some of the more annoying bugs recently fixed</dt>\r
- </dl>\r
- <dl>\r
- <dd> \r
- <ul>\r
- <li>Moving posts now also moves attachments</li>\r
- <li>No more warnings when looking for uploaded files in an empty course</li>\r
- <li>Students no longer always get plain-format mail on force-subscribed \r
- forums</li>\r
- <li>Cookies can no longer interfere with the admin setup during installation</li>\r
- <li>Effectively no limit to the number of activities per section</li>\r
- <li>Several fixes when dealing with zip files, especially on Windows</li>\r
- <li>Admins can now edit accounts created from external databases</li>\r
- <li>Session no longer conflicts with other software</li>\r
- <li>Excel files now work on non-Intel machines</li>\r
- </ul>\r
- </dd>\r
- </dl>\r
- <dl>\r
- <dt> </dt>\r
- </dl>\r
- <dd> </dd>\r
-</ul>\r
-\r
-<hr>\r
-\r
-<h3> New in Moodle 1.0.9 (29th May, 2003) :</h3>\r
-<ul><dl>\r
-<dt> General</dt>\r
-<dd> \r
- <li>Various optimisations and significant performance enhancements</li>\r
- <li>Several obscure security fixes</li>\r
- <li>Moodle is now well-behaved when enclosed within a frame</li>\r
- <li>Richtext editor can now be used in more text-editing fields</li>\r
- <li>New format "Plain text format", useful when posting code or HTML.</li>\r
- <li>New format "Wiki format", allows Wiki-style tagging in most places</li>\r
- <li>New popup allows emoticons/smilies to be inserted by clicking on images</li>\r
- <li>Ability to specify permissions of new folders and files created on the server</li>\r
- <li>Some fixes for servers running in Safe Mode (some file problems remain)</li>\r
- <li>Various fixes for cleaning some external text of quotes, etc</li>\r
- <li>Various fixes for PostgreSQL 7.3 compatibility</li>\r
- <li>Started migration of HTML code towards XHTML Transitional</li>\r
- <li>Countless other little fixes all over the place</li>\r
-</dd>\r
-\r
-<dt> Languages</dt>\r
-<dd> \r
- <li><b>10</b> new language packs! Argentinian Spanish, Czech, Portuguese, Slovakian, Romanian, Danish, Russian, Polish, Chinese Traditional and French Canadian.</li>\r
- <li>Fixes and upgrades to almost all language packs</li>\r
- <li>Language can be specified for the current session (see menu on home page and login page) and can be changed on any page by something to the url, eg: http://moodle.org/?lang=ru </li>\r
- <li>Language menu can be restricted to a subset of languages and even removed.\r
- <li>Truetype fonts are now part of the language packs</li>\r
- <li>ALL dates/times can now be reformatted as part of the language pack</li>\r
- <li>A small but annoying bug was fixed with the web-based language editor on Windows servers that caused language files to grow</li>\r
-</dd>\r
-\r
-<dt> Developers</dt>\r
-<dd> \r
- <li>Global debug variable gives more feedback about uninitialised variables and the like</li>\r
- <li>Various fixes to tidy up and further standardise some of the PHP code</li>\r
- <li>Various fixes for robustness (ensuring variables are always initialised)</li>\r
-</dd>\r
-\r
-<dt> Admin</dt>\r
-<dd> \r
- <li><font color=red>Some changed options and code in config-dist.php (if upgrading, compare with your current config.php or rebuild your config.php from scratch)</font></li>\r
- <li><font color=red>Many changes to themes - authors of custom themes should read <a href="http://moodle.org/theme/UPGRADE.txt">theme/UPGRADE.txt</a> </font></li>\r
- <li>New moodle.org registration function for security notifications etc</li>\r
- <li>Admin directory can be moved from /admin to something else (see config-dist.php)</li>\r
- <li>User listing is now paged, and can now be searched for strings</li>\r
- <li>Module management: activity modules can now be individually disabled or deleted completely</li>\r
- <li>Improvements to the language editing page</li>\r
- <li>Better checking of PHP environment during installation, with warnings</li>\r
- <li>Cleaner installation procedure.</li>\r
-</dd>\r
-\r
-<dt> User management</dt>\r
-<dd> \r
- <li>New role: Course creator - just like teacher but can also create new courses</li>\r
- <li>New authentication plug-in named "manual", prevents users from creating their own accounts</li>\r
- <li>"Forgot Password" routine now uses an email confirmation before resetting password</li>\r
-</dd>\r
-\r
-\r
-<dt> Courses</dt>\r
-<dd> \r
- <li>Activities on the course page now have a little button to hide/show that activity to students</li>\r
- <li>Whole topics/weeks can also now be hidden or shown</li>\r
- <li>The list of participants now has some paging, to cope with very large classes</li>\r
- <li>Zip/Unzip is now supported by an internal zip library, removing \r
- the dependence on external programs to do this. This also means that \r
- zip/unzip now works on Windows.</li>\r
-</dd>\r
-\r
-<dt> Assignments</dt>\r
-<dd> \r
- <li>Assignment submissions can be sorted</li>\r
- <li>Assignment notification mail isn't sent to unenrolled students</li>\r
-</dd>\r
-\r
-<dt> Forums</dt>\r
-<dd> \r
- <li>Display of forum discussions list is greatly improved</li>\r
- <li>Whole discussions can be moved to any other forum with a single click</li>\r
- <li>Date/time of posts is now "last modified", not "created"</li>\r
- <li>Blank subject-lines or messages are now prevented</li>\r
- <li>More intelligent parsing and display of text in posts</li>\r
- <li>Force Subscribe now works on the "Site News" forum (mails all active students/teachers)</li>\r
- <li>Better handling of mailouts to prevent the possibility of double copies\r
- that sometimes happened with very large classes</li>\r
-</dd>\r
-\r
-<dt> Workshop Assignment module (not included: available soon as a separate download)</dt>\r
-<dd> \r
- <li>A very interesting new module contributed by Ray Kingdon,</li>\r
- <li>A flexible tool that implements a variety of peer-grading and \r
- example-setting schemes that involve a whole group in examining \r
- and grading pieces of work.</li>\r
-</dd>\r
-\r
-<dt> Quizzes</dt>\r
-<dd> \r
- <li>New question type, Random Question (selects from all questions in the same category)</li>\r
- <li>New question type, Matching Question (student must match answers to questions)</li>\r
- <li>New question type, Random Matching Short-Answers (randomly creates Matching Questions \r
- from the available Short Answer questions in the same category)</li>\r
- <li>Quiz question import from text files (modular design allows expansion to new formats - a beta Blackboard module is included)</li>\r
- <li>'Create multiple questions' wizard to quickly create a random quiz</li>\r
- <li>Quiz questions may be randomly shuffled</li>\r
- <li>Quiz answers (multiple choice, etc) may be randomly shuffled</li>\r
- <li>Fixed off-by-one error when "Save Grades" button wasn't used.</li>\r
- <li>Regrading works properly if the quiz has been changed</li>\r
- <li>Editing a question after it's already been used in a quiz no longer affects quiz results</li>\r
- <li>Multiple choice answers are labelled a,b,c not 1,2,3</li>\r
-</dd>\r
-\r
-<dt> Resources</dt>\r
-<dd> \r
- <li>Better performance when editing large text or HTML resources</li>\r
- <li>Plain images are now display centered within a proper web page (not raw).</li>\r
- <li>Wiki format added as a new option for Resource pages</li>\r
-</dd>\r
-\r
-<dt> Custom Themes</dt>\r
-<dd> \r
- <li>A number of new styles have been added to all built-in themes. Some of these are ESSENTIAL\r
- to viewing some of the new features. PLEASE SEE \r
- <a href="http://moodle.org/theme/UPGRADE.txt">theme/UPGRADE.txt</a> \r
- TO SEE THE CHANGES YOU WILL HAVE TO MAKE TO OLDER THEMES.</li>\r
-\r
- <li>Custom themes now have the capability to re-define all the little button graphics. \r
- There is a new entry in theme/x/config.php ($THEME->custompix) and a new \r
- optional subdirectory "pix". See the theme cordoroyblue for an example.</li>\r
-</dd>\r
-\r
-</dl></ul>\r
-\r
-<hr>\r
-\r
-\r
-<p>Older releases can be seen in the <a href="http://moodle.org/mod/forum/view.php?f=1">Moodle.org announcement forum</a>.\r
-\r
-\r
-<p> </p>\r
-<p align="CENTER"><font size="1"><a href="../doc/" target="_top">Moodle Documentation</a></font></p>\r
-<p align="CENTER"><font size="1">Version: $Id$</font></p>\r
+<head>
+
+<title>Moodle Docs: Release notes</title>
+
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+
+<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">
+<h1>Release notes</h1>
+<h3> New in Moodle 1.1.1 (10 September, 2003):</h3>
+<ul>
+ <dl>
+ <dt> </dt>
+ <dt>General Fixes</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li>Translation improvements in many languages</li>
+ <li>Frame fix when switching languages in documentation</li>
+ <li>All short PHP tags removed ... short_tags is no longer a requirement</li>
+ <li>Forum search results link using anchor tag for better context</li>
+ <li>Removed target from "delete" link on user editing page</li>
+ <li>'Search' on social format moved closer to the top to prevent browser
+ self-scrolling </li>
+ <li>Page redirection is faster and no longer causes intermediate page
+ to be stored in IE history</li>
+ <li>Course listings improved when courses are displayed, including more
+ information</li>
+ <li>Category listings show courses in full when there are under ten courses</li>
+ <li>Invisible courses are always shown last in My Courses</li>
+ <li>Course creators can now see all hidden categories and courses</li>
+ <li>Styles added for category and course names</li>
+ <li>Removed tags from question text on quiz 'simplestat' report</li>
+ <li>Added percentages to downloaded data from 'simplestat' report</li>
+ <li>Allow external deep linking using guest account ?username=guest</li>
+ <li>Any admin can now add/remove course creators</li>
+ <li>Primary admin can now update own username/password even with external authentication</li>
+ <li>Quizzes can now be specified as having "no grade" and no grades will be shown</li>
+ <li>When editing a language, missing strings files are created if possible</li>
+ <li>Fixed bug in weekly journal date calculations</li>
+ <li>Fixed bug in config.php that made error_reporting not work</li>
+ <li>Fixed bug when editing user name with quotes in it</li>
+ <li>Fixed bug in email obfuscation for email addresses with numbers in
+ them </li>
+ <li>Fixed missing PostgreSQL schema for chat module</li>
+ <li>Fixed several typos in PostgreSQL upgrading code</li>
+ <li>Fixed some uninitialised variables</li>
+ <li>Several bugs fixed in Workshop module</li>
+ </ul>
+ </dd>
+ </dl>
+</ul>
+<hr>
+
+
+
+<h3> New in Moodle 1.1 (28 August, 2003):</h3>
+<ul>
+ <dl>
+ <dt> </dt>
+ <dt>Major Changes</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li>A completely new <strong>backup</strong> system for backup and restore
+ of courses (Thanks, Eloy!)</li>
+ <li>A new <strong>workshop</strong> module for peer grading (Thanks, Ray!)</li>
+ <li>A new <strong>chat</strong> module for synchronous discussions</li>
+ <li>All-new <strong>course manager</strong> to handle very large numbers
+ of courses (tested with 3700)</li>
+ <li>Custom-defined <strong>grading scales</strong> that can be used throughout
+ a course</li>
+ <li>Performance improvements in many areas</li>
+ </ul>
+ </dd>
+ </dl>
+ <dl>
+ <dt>General</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li>Clean up of the whole admin menu organisation to make it clearer</li>
+ <li>Categories can be nested and sorted alphabetically or manually</li>
+ <li>Courses and whole categories can be hidden from students</li>
+ <li>Course descriptions and names can be searched for keywords</li>
+ <li>Large categories are now completely paged</li>
+ <li>Improved web caching for stylesheets and images</li>
+ <li>"My courses" display on the home page when logged in.</li>
+ <li>Inclusion of non-linked page to display ALL user pictures at once
+ (see /userpix)</li>
+ <li>The "secureforms" feature now defaults to OFF.</li>
+ <li>Moodle now doesn't care if "magic quotes" is on or off.</li>
+ <li>Images in /pix were rearranged and tidied up</li>
+ <li>HTML email is better formatted for wider compatibility</li>
+ <li>Mail bounces are now sent to the admin user</li>
+ <li>Better cron tasks (less CPU used) and duplicate enrolments are now
+ cleaned</li>
+ <li>Improved display of logs with infinite paging and increased flexibility</li>
+ <li>User log graphs now work at site-level (showing ALL logs on the site)</li>
+ <li>People with manual accounts can now recover their password</li>
+ <li>Improved system for defining/printing help files for major activity
+ modules</li>
+ <li>Activity modules can now have settings</li>
+ <li>Email addresses are all completely obfuscated (to fool web spiders)</li>
+ <li>There is now an index to the help files</li>
+ <li>Library (Mark Kimes' add-on) is now supported if it is installed (see Moodle contrib for Library source)</li>
+ </ul>
+ </dd>
+ </dl>
+ <dl>
+ <dt></dt>
+ <dt>Courses</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li>Teachers can now have their course editing privileges removed</li>
+ <li>Teachers can now manually enrol students if they want to</li>
+ <li>Teacher management is now all combined in one interface</li>
+ <li>Activities can be moved any distance with two clicks</li>
+ <li>Topics/weeks can now be moved up and down</li>
+ <li>Pop-up menu to quickly switch between topics/weeks when collapsed</li>
+ <li>When self-enrolling, students are notified and given a chance to cancel</li>
+ <li>Teachers and students see list of "My Courses" on course
+ home pages.</li>
+ <li>Grades can be hidden from students if not needed</li>
+ </ul>
+ </dd>
+ </dl>
+ <dl>
+ <dt></dt>
+ <dt>Languages</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li><strong>Hungarian</strong> and <strong>Greek</strong> have been added,
+ and there are lots of other updates. As usual, the language packs within
+ this release may not be fully completed yet. You can always download
+ the newest language packs from <a href="http://moodle.org/download/lang/">http://moodle.org/download/lang/</a>.</li>
+ <li>Updates and fixes to most languages</li>
+ <li>Languages now have a parent language (for displaying missing strings)</li>
+ <li>Some fixes for locales and time display in several languages</li>
+ <li>es_mx is being phased out in favour of "es" (International
+ Spanish) </li>
+ </ul>
+ </dd>
+ </dl>
+ <dl>
+ <dt></dt>
+ <dt>Forum</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li>Much improved searching, with multiple keywords, paging etc</li>
+ <li>Forum grading can be either off, used by everyone, or used only by teachers</li>
+ <li>Forum grading can use custom scales or numbers</li>
+ <li>A date range can be set to restrict the posts that can be graded.</li>
+ <li>Admin now has access to some settings via Admin -> Modules -> Forums </li>
+ <li>After editing a post, user is returned to post in context</li>
+ <li>Attached images are displayed inline</li>
+ <li>Email copies in plain text format now print URLs nicely</li>
+ </ul>
+ </dd>
+ </dl>
+ <dl>
+ <dt>Quiz</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li>New question type: Embedded Answers (Cloze) - allows text passages
+ with embedded answers</li>
+ <li>New question type: Numerical - allows a range of numerical answers
+ to be entered</li>
+ <li>New question type: Description - not a real question, it allows text/graphics
+ to be inserted anywhere</li>
+ <li>Expanded quiz reporting with modular report plugins</li>
+ <li>New feature for repeat attempts, where each attempt builds on the
+ last </li>
+ <li>If the quiz is closing within the next 24 hours, a small countdown
+ clock is shown in the title bar and alerts warn at ten minutes and zero
+ minutes.</li>
+ <li>Some refactoring to the quiz code to make it easier to extend with
+ new question types</li>
+ </ul>
+ </dd>
+ </dl>
+ <dl>
+ <dt></dt>
+ <dt>Resources</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li>Web links can now be in very customisable pop-up windows.</li>
+ <li>Admin now has access to some settings via Admin -> Modules ->
+ Resources</li>
+ </ul>
+ </dd>
+ </dl>
+ <dl>
+ <dt>Some of the more annoying bugs recently fixed</dt>
+ </dl>
+ <dl>
+ <dd>
+ <ul>
+ <li>Moving posts now also moves attachments</li>
+ <li>No more warnings when looking for uploaded files in an empty course</li>
+ <li>Students no longer always get plain-format mail on force-subscribed
+ forums</li>
+ <li>Cookies can no longer interfere with the admin setup during installation</li>
+ <li>Effectively no limit to the number of activities per section</li>
+ <li>Several fixes when dealing with zip files, especially on Windows</li>
+ <li>Admins can now edit accounts created from external databases</li>
+ <li>Session no longer conflicts with other software</li>
+ <li>Excel files now work on non-Intel machines</li>
+ </ul>
+ </dd>
+ </dl>
+ <dl>
+ <dt> </dt>
+ </dl>
+ <dd> </dd>
+</ul>
+<hr>
+
+<h3> New in Moodle 1.0.9 (29th May, 2003) :</h3>
+<ul>
+ <dl>
+ <dt> General</dt>
+ <dd>
+ <li>Various optimisations and significant performance enhancements</li>
+ <li>Several obscure security fixes</li>
+ <li>Moodle is now well-behaved when enclosed within a frame</li>
+ <li>Richtext editor can now be used in more text-editing fields</li>
+ <li>New format "Plain text format", useful when posting code or HTML.</li>
+ <li>New format "Wiki format", allows Wiki-style tagging in most places</li>
+ <li>New popup allows emoticons/smilies to be inserted by clicking on images</li>
+ <li>Ability to specify permissions of new folders and files created on the server</li>
+ <li>Some fixes for servers running in Safe Mode (some file problems remain)</li>
+ <li>Various fixes for cleaning some external text of quotes, etc</li>
+ <li>Various fixes for PostgreSQL 7.3 compatibility</li>
+ <li>Started migration of HTML code towards XHTML Transitional</li>
+ <li>Countless other little fixes all over the place</li>
+ </dd>
+ <dt> Languages</dt>
+ <dd>
+ <li><b>10</b> new language packs! Argentinian Spanish, Czech, Portuguese, Slovakian, Romanian, Danish, Russian, Polish, Chinese Traditional and French Canadian.</li>
+ <li>Fixes and upgrades to almost all language packs</li>
+ <li>Language can be specified for the current session (see menu on home page and login page) and can be changed on any page by something to the url, eg: http://moodle.org/?lang=ru </li>
+ <li>Language menu can be restricted to a subset of languages and even removed.
+ <li>Truetype fonts are now part of the language packs</li>
+ <li>ALL dates/times can now be reformatted as part of the language pack</li>
+ <li>A small but annoying bug was fixed with the web-based language editor on Windows servers that caused language files to grow</li>
+ </dd>
+ <dt> Developers</dt>
+ <dd>
+ <li>Global debug variable gives more feedback about uninitialised variables and the like</li>
+ <li>Various fixes to tidy up and further standardise some of the PHP code</li>
+ <li>Various fixes for robustness (ensuring variables are always initialised)</li>
+ </dd>
+ <dt> Admin</dt>
+ <dd>
+ <li><font color=red>Some changed options and code in config-dist.php (if upgrading, compare with your current config.php or rebuild your config.php from scratch)</font></li>
+ <li><font color=red>Many changes to themes - authors of custom themes should read <a href="http://moodle.org/theme/UPGRADE.txt">theme/UPGRADE.txt</a> </font></li>
+ <li>New moodle.org registration function for security notifications etc</li>
+ <li>Admin directory can be moved from /admin to something else (see config-dist.php)</li>
+ <li>User listing is now paged, and can now be searched for strings</li>
+ <li>Module management: activity modules can now be individually disabled or deleted completely</li>
+ <li>Improvements to the language editing page</li>
+ <li>Better checking of PHP environment during installation, with warnings</li>
+ <li>Cleaner installation procedure.</li>
+ </dd>
+ <dt> User management</dt>
+ <dd>
+ <li>New role: Course creator - just like teacher but can also create new courses</li>
+ <li>New authentication plug-in named "manual", prevents users from creating their own accounts</li>
+ <li>"Forgot Password" routine now uses an email confirmation before resetting password</li>
+ </dd>
+ <dt> Courses</dt>
+ <dd>
+ <li>Activities on the course page now have a little button to hide/show that activity to students</li>
+ <li>Whole topics/weeks can also now be hidden or shown</li>
+ <li>The list of participants now has some paging, to cope with very large classes</li>
+ <li>Zip/Unzip is now supported by an internal zip library, removing
+ the dependence on external programs to do this. This also means that
+ zip/unzip now works on Windows.</li>
+ </dd>
+ <dt> Assignments</dt>
+ <dd>
+ <li>Assignment submissions can be sorted</li>
+ <li>Assignment notification mail isn't sent to unenrolled students</li>
+ </dd>
+ <dt> Forums</dt>
+ <dd>
+ <li>Display of forum discussions list is greatly improved</li>
+ <li>Whole discussions can be moved to any other forum with a single click</li>
+ <li>Date/time of posts is now "last modified", not "created"</li>
+ <li>Blank subject-lines or messages are now prevented</li>
+ <li>More intelligent parsing and display of text in posts</li>
+ <li>Force Subscribe now works on the "Site News" forum (mails all active students/teachers)</li>
+ <li>Better handling of mailouts to prevent the possibility of double copies
+ that sometimes happened with very large classes</li>
+ </dd>
+ <dt> Workshop Assignment module (not included: available soon as a separate download)</dt>
+ <dd>
+ <li>A very interesting new module contributed by Ray Kingdon,</li>
+ <li>A flexible tool that implements a variety of peer-grading and
+ example-setting schemes that involve a whole group in examining
+ and grading pieces of work.</li>
+ </dd>
+ <dt> Quizzes</dt>
+ <dd>
+ <li>New question type, Random Question (selects from all questions in the same category)</li>
+ <li>New question type, Matching Question (student must match answers to questions)</li>
+ <li>New question type, Random Matching Short-Answers (randomly creates Matching Questions
+ from the available Short Answer questions in the same category)</li>
+ <li>Quiz question import from text files (modular design allows expansion to new formats - a beta Blackboard module is included)</li>
+ <li>'Create multiple questions' wizard to quickly create a random quiz</li>
+ <li>Quiz questions may be randomly shuffled</li>
+ <li>Quiz answers (multiple choice, etc) may be randomly shuffled</li>
+ <li>Fixed off-by-one error when "Save Grades" button wasn't used.</li>
+ <li>Regrading works properly if the quiz has been changed</li>
+ <li>Editing a question after it's already been used in a quiz no longer affects quiz results</li>
+ <li>Multiple choice answers are labelled a,b,c not 1,2,3</li>
+ </dd>
+ <dt> Resources</dt>
+ <dd>
+ <li>Better performance when editing large text or HTML resources</li>
+ <li>Plain images are now display centered within a proper web page (not raw).</li>
+ <li>Wiki format added as a new option for Resource pages</li>
+ </dd>
+ <dt> Custom Themes</dt>
+ <dd>
+ <li>A number of new styles have been added to all built-in themes. Some of these are ESSENTIAL
+ to viewing some of the new features. PLEASE SEE
+ <a href="http://moodle.org/theme/UPGRADE.txt">theme/UPGRADE.txt</a>
+ TO SEE THE CHANGES YOU WILL HAVE TO MAKE TO OLDER THEMES.</li>
+ <li>Custom themes now have the capability to re-define all the little button graphics.
+ There is a new entry in theme/x/config.php ($THEME->custompix) and a new
+ optional subdirectory "pix". See the theme cordoroyblue for an example.</li>
+ </dd>
+ </dl>
+</ul>
+<hr>
+
+
+<p>Older releases can be seen in the <a href="http://moodle.org/mod/forum/view.php?f=1">Moodle.org 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>
-<head>\r
- <title>Moodle Docs: Teachers Manual</title>\r
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
- <!--\r
- .sectionheading {\r
- font-size: medium;\r
- font-weight: bold;\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- border: 1px dotted;\r
- padding: 10px;\r
- }\r
- -->\r
- </style>\r
-</head>\r
-\r
-<body bgcolor="#FFFFFF">\r
-\r
-<h2>Teacher Manual</h2>\r
-<p>This page is a very quick guide to creating online courses with Moodle. It \r
- outlines the main functions that are available, as well as some of the main \r
- decisions 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 class="sectionheading"><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
- <p> <img src="../pix/i/hide.gif" width="16" height="16"> - the <strong>open-eye \r
- icon</strong> will let you hide something from students</p>\r
- <p> <img src="../pix/i/show.gif" width="16" height="16"> - the <strong>closed-eye \r
- icon</strong> will make a hidden item available</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
- \r
-<p> </p></blockquote>\r
-<h3 class="sectionheading"><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.org">martin@moodle.org</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
- \r
-<p> </p></blockquote>\r
-<h3 class="sectionheading"><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
- \r
-<p> </p></blockquote>\r
-<h3 class="sectionheading"><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>\r
- <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 have a report screen \r
- where you can see the results. I use it to gather research consent from \r
- my students, but you could use it for quick polls or class 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). A general rule of thumb is to create one journal per week. \r
- Encourage students to write reflectively and critically in these journals, \r
- as they are only available to them and you. Afterwards, you will be able \r
- to grade and comment all the entries for that week or topic, and students \r
- will receive an automatic email informing them of your feedback. Journals \r
- are not designed to be continually added to - if you need to do that then \r
- add more journal activities.</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 \r
- text-based pages by typing them 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 multiple \r
- choice, true-false, and short answer questions. These questions are kept \r
- in a categorised database, and can be re-used within courses and even between \r
- courses. Quizzes can allow multiple attempts. Each attempt is automatically \r
- marked, and the teacher can choose whether to give feedback or to show correct \r
- answers. This module includes grading facilities. </dd>\r
- <br>\r
- <br>\r
- <dt><strong>Survey</strong></dt>\r
- <dd>The survey module provides a number of predefined survey instruments that \r
- are useful in evaluating and understanding your class. Currently they include \r
- the COLLES and the ATTLS instruments. They can be given to students early \r
- in the course as a diagnostic tool and at the end of the course as an evaluation \r
- 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
- \r
-<p> </p></blockquote>\r
-<h3 class="sectionheading"><a name="course"></a>Running the course</h3>\r
-<blockquote> \r
- <p>There are some big plans to extend this document into a more comprehensive \r
- tutorial. Until then here are a few ideas:</p>\r
- <ol>\r
- <li>Subscribe yourself to all the forums so you keep in touch with your class \r
- activity. </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 \r
- and help you to respond in ways that are tailored to their own needs.</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
- \r
-<p> </p></blockquote>\r
-<h3 class="sectionheading"><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.org/" target="_top">moodle.org</a> \r
- and join us in the course called "<a href="http://moodle.org/course/view.php?id=5" target=_top >Using \r
- Moodle</a>". 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://moodle.org/user/view.php?id=1&course=1" target="_top">Martin \r
- Dougiamas</a> or browse the "bug tracker" site for Moodle, at <a href="http://moodle.org/bugs/" target="_top">moodle.org/bugs</a></p>\r
- <p align="center">Thanks for using Moodle - and good luck with your teaching!</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
+<head>
+<title>Moodle Docs: Teachers Manual</title>
+<link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body bgcolor="#FFFFFF">
+<h1>Teacher Manual</h1>
+<p>This page is a very quick guide to creating online courses with Moodle. It
+ outlines the main functions that are available, as well as some of the main
+ decisions you'll need to make.</p>
+<p>Sections in this document:</p>
+<ol>
+ <li><a href="#started">Getting started</a></li>
+ <li><a href="#settings">Course settings</a></li>
+ <li><a href="#upload">Uploading files</a></li>
+ <li><a href="#activities">Setting up activities</a></li>
+ <li><a href="#course">Running the course</a></li>
+ <li><a href="#further">Further information</a></li>
+</ol>
+<h3 class="sectionheading"><a name="started"></a>Getting started</h3>
+<blockquote>
+ <p>This document assumes your site administrator has set up Moodle and given
+ you new, blank course to start with. It also assumes you have logged in to
+ your course using your teacher account.</p>
+ <p>Here are three general tips that will help you get started.</p>
+ <ol>
+ <li><strong>Don't be afraid to experiment:</strong>
+ <blockquote>feel free to poke around and change things. It's hard to break anything
+ in a Moodle course, and even if you do it's usually easy to fix it.
+ </blockquote>
+ <li><strong>Notice and use these little icons</strong>:
+ <blockquote>
+ <p> <img src="../pix/i/edit.gif"> - the <strong>edit icon</strong>
+ lets you edit whatever it is next to.</p>
+ <p><img src="../pix/help.gif" width="22" height="17"> - the <strong>help
+ icon</strong> will provide you with a popup help window </p>
+ <p> <img src="../pix/i/hide.gif" width="16" height="16"> - the <strong>open-eye
+ icon</strong> will let you hide something from students</p>
+ <p> <img src="../pix/i/show.gif" width="16" height="16"> - the <strong>closed-eye
+ icon</strong> will make a hidden item available</p>
+ </blockquote>
+ </li>
+ <li><strong>Use the navigation bar at the top of each page</strong>
+ <blockquote>this
+ should help remind you where you are and prevent getting lost.
+ </blockquote>
+ </li>
+ </ol>
+ <p> </p>
+</blockquote>
+<h3 class="sectionheading"><a name="settings"></a>Course settings</h3>
+<blockquote>
+ <p>The first thing you should do is look under the "Administration"
+ on your course home page and click on "<strong>Settings...</strong>"
+ (Note that this link, and in fact the whole Administration section is only
+ available to you (and the site administrator). Students will not even see
+ these links).</p>
+ <p>On the Settings page you can change a number of settings about your course,
+ ranging from its name to what day it starts. I won't talk here about all these,
+ as they all have a help icon next to them which explains them all in detail.
+ However, I will talk about the most important of these - the <strong>course
+ format</strong>.</p>
+ <p>The course format that you choose will decide the basic layout of your course,
+ like a template. Moodle version 1.0 has three formats - in future there will
+ probably be many more (please send new ideas to <a href="mailto:martin@moodle.org">martin@moodle.org</a>!)</p>
+ <p>Here are some screenshots of three sample courses in each of these three
+ formats (ignore the different colours, which are set for a whole site by the
+ site administrator):</p>
+ <p align="center"><strong>Weekly format:</strong></p>
+ <p align="center"><img src="pix/weekly.jpg" width="570" height="527"></p>
+ <p align="center"> </p>
+ <p align="center"><strong>Topics format:</strong></p>
+ <p align="center"><img src="pix/topics.jpg" width="570" height="463"></p>
+ <p align="center"> </p>
+ <p align="center"><strong>Social format:</strong></p>
+ <p align="center"><img src="pix/social.jpg" width="570" height="429"></p>
+ <p> </p>
+ <p>Note that the weekly and topics formats are very similar in structure. The
+ main difference is that each box in the weekly format covers exactly one week,
+ whereas in the topic format each box can cover whatever you like. The social
+ format doesn't use much content at all and is based around just one forum
+ - this is displayed on the main page.</p>
+ <p>See the help buttons on the Course Settings page for more details.</p>
+ <p> </p>
+</blockquote>
+<h3 class="sectionheading"><a name="upload"></a>Uploading files</h3>
+<blockquote>
+ <p>You may have existing content that you want to add to your course, such as
+ web pages, audio files, video files, word documents, or flash animations.
+ Any type of file that exists can be uploaded into your course and stored on
+ the server. While your files are on the server you can move, rename, edit
+ or delete them.</p>
+ <p>All of this is achieved through the <strong>Files</strong> link in your Administration
+ menu. The Files section looks like this:</p>
+ <p align="center"><img src="pix/files.jpg" width="400" height="347"></p>
+ <p> </p>
+ <p>This interface is only available to teachers - it is not accessible by students.
+ Individual files are made available to students later on (as "Resources"
+ - see the next section).</p>
+ <p>As you can see in the screenshot, files are listed alongside subdirectories.
+ You can create any number of subdirectories to organise your files and move
+ your files from one to the other.</p>
+ <p>Uploading files via the web is currently restricted to one file at a time.
+ If you want to upload a lot of files at once (for example a whole web site),
+ it can be a lot easier to use a <strong>zip program</strong> to compress them
+ into a single file, upload the zip file and then unzip them again on the server
+ (you will see an "unzip" link next to zip archives).</p>
+ <p>To preview any file you have uploaded just click on its name. Your web browser
+ will take care of either displaying it or downloading it to your computer.</p>
+ <p>HTML and text files can be edited in-place online. Other files will need
+ to be edited on your local computer and uploaded again. if you upload a file
+ with the same name as an existing file it will automatically be overwritten.</p>
+ <p>A final note: if your content resides out on the web then you don't need
+ to upload the files at all - you can link directly to them from inside the
+ course (see the Resources module and the next section).</p>
+ <p> </p>
+</blockquote>
+<h3 class="sectionheading"><a name="activities"></a>Setting up activities</h3>
+<blockquote>
+ <p>Building a course involves adding course activity modules to the main page
+ in the order that students will be using them. You can shuffle the order any
+ time you like.</p>
+ <p>To turn on editing, click "Turn on editing" under Administration.
+ This toggle switch shows or hides the extra controls that allow you to manipulate
+ your main course page. Note in the first screenshot above (of the Weekly format
+ course) that the editing controls are turned on.</p>
+ <p>To add a new activity, simply go to the week or topic or section of the screen
+ where you want to add it, and select the type of activity from the popup menu.
+ Here is a summary of all the standard activities in Moodle 1.0:</p>
+ <dl>
+ <dt><strong>Assignment</strong></dt>
+ <dd>An assignment is where you set a task with a due date and a maximum grade.
+ Students will be able to upload one file to satisify the requirements. The
+ date they upload their file is recorded. Afterwards, you will have a single
+ page on which ou can view each file (and how late or early it is), and then
+ record a grade and a comment. Half an hour after you grade any particular
+ student, Moodle will automatically email that student a notification. </dd>
+ <br>
+ <br>
+ <dt><strong>Choice</strong></dt>
+ <dd>A choice activity is very simple - you ask a question and specify a choice
+ of responses. Students can make their choice, and you have a report screen
+ where you can see the results. I use it to gather research consent from
+ my students, but you could use it for quick polls or class votes.</dd>
+ <br>
+ <br>
+ <dt><strong>Forum</strong></dt>
+ <dd>This module is by far the most important - it is here that discussion
+ takes place. When you add a new forum, yu will presented with a choice of
+ different types - a simple single-topic discussion, a free-for-all general
+ forum, or a one-discussion-thread-per-user.</dd>
+ <br>
+ <br>
+ <dt><strong>Journal</strong></dt>
+ <dd>Each journal activity is an entry in the whole course journal. For each
+ one you can specify an open-ended question that guides what students write,
+ as well as a window of time in which the journal is open (weekly course
+ format only). A general rule of thumb is to create one journal per week.
+ Encourage students to write reflectively and critically in these journals,
+ as they are only available to them and you. Afterwards, you will be able
+ to grade and comment all the entries for that week or topic, and students
+ will receive an automatic email informing them of your feedback. Journals
+ are not designed to be continually added to - if you need to do that then
+ add more journal activities.</dd>
+ <br>
+ <br>
+ <dt><strong>Resource</strong></dt>
+ <dd>Resources are the content of your course. Each resource can be any file
+ you have uploaded or can point to using a URL. You can also maintain simple
+ text-based pages by typing them directly into a form.</dd>
+ <br>
+ <br>
+ <dt><strong>Quiz</strong></dt>
+ <dd>This module allows you to design and set quiz tests, consisting of multiple
+ choice, true-false, and short answer questions. These questions are kept
+ in a categorised database, and can be re-used within courses and even between
+ courses. Quizzes can allow multiple attempts. Each attempt is automatically
+ marked, and the teacher can choose whether to give feedback or to show correct
+ answers. This module includes grading facilities. </dd>
+ <br>
+ <br>
+ <dt><strong>Survey</strong></dt>
+ <dd>The survey module provides a number of predefined survey instruments that
+ are useful in evaluating and understanding your class. Currently they include
+ the COLLES and the ATTLS instruments. They can be given to students early
+ in the course as a diagnostic tool and at the end of the course as an evaluation
+ tool (I use one every week in my courses).</dd>
+ </dl>
+ <br>
+ <p>After adding your activities you can move them up and down in your course
+ layout by clicking on the little arrow icons (<img src="../pix/t/up.gif" width="9" height="10">
+ <img src="../pix/t/down.gif" width="9" height="10">) next to each one. You
+ can also delete them using the cross icon <img src="../pix/t/delete.gif" width="10" height="10">,
+ and re-edit them using the edit icon <img src="../pix/t/edit.gif" width="10" height="11">.</p>
+ <p> </p>
+</blockquote>
+<h3 class="sectionheading"><a name="course"></a>Running the course</h3>
+<blockquote>
+ <p>There are some big plans to extend this document into a more comprehensive
+ tutorial. Until then here are a few ideas:</p>
+ <ol>
+ <li>Subscribe yourself to all the forums so you keep in touch with your class
+ activity. </li>
+ <li>Encourage all the students fill out their user profile (including photos)
+ and read them all - this will help provide some context to their later writings
+ and help you to respond in ways that are tailored to their own needs.</li>
+ <li>Keep notes to yourself in the private "<strong>Teacher's Forum</strong>"
+ (under Administration). This is especially useful when team teaching.</li>
+ <li>Use the "<strong>Logs</strong>" link (under Administration)
+ to get access to complete, raw logs. In there you'll see a link to a popup
+ window that updates every sixty seconds and shows the last hour of activity.
+ This is useful to keep open on your desktop all day so you can feel in touch
+ with what's going on in the course.</li>
+ <li>Use the "<strong>Activity Reports</strong>" (next to each name
+ in the list of all people, or from any user profile page). These provide
+ a great way to see what any particular person has been up to in the course.</li>
+ <li>Respond quickly to students. Don't leave it for later - do it right away.
+ Not only is it easy to become overwhelmed with the volume that can be generated,
+ but it's a crucial part of building and maintaining a community feel in
+ your course.</li>
+ </ol>
+ <p> </p>
+</blockquote>
+<h3 class="sectionheading"><a name="further"></a>Further information</h3>
+<blockquote>
+ <p>If you have any particular problems with your site, you should contact your
+ local site administrator.</p>
+ <p>If you have some great ideas for improvements to Moodle, or even some good
+ stories, come over to <a href="http://moodle.org/" target="_top">moodle.org</a>
+ and join us in the course called "<a href="http://moodle.org/course/view.php?id=5" target=_top >Using
+ Moodle</a>". We'd love to hear from you, and you can help Moodle improve.</p>
+ <p>If you want to contribute to coding new modules, or writing documentation,
+ or papers, contact me: <a href="http://moodle.org/user/view.php?id=1&course=1" target="_top">Martin
+ Dougiamas</a> or browse the "bug tracker" site for Moodle, at <a href="http://moodle.org/bugs/" target="_top">moodle.org/bugs</a></p>
+ <p align="center">Thanks for using Moodle - and good luck with your teaching!</p>
+ <hr>
+ <p> </p>
+</blockquote>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01
+ martin Exp $</font></p>
+</body>
-<head>\r
- <title>Moodle Docs: Upgrading</title>\r
- <link rel="stylesheet" href="../theme/standard/styles.php" type="TEXT/CSS">\r
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">\r
- <style type="text/css">\r
- <!--\r
- .sectionheading {\r
- font-size: medium;\r
- font-weight: bold;\r
- font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif;\r
- border: 1px dotted;\r
- padding: 10px;\r
- background-color: #EEEEEE;\r
- }\r
- -->\r
- </style>\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
-<h3 class="sectionheading">1. Backup important data</h3>\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 optional \r
- "Database" web interface to do the same thing on all platforms.</p>\r
- <p> </p>\r
- </blockquote>\r
- </blockquote>\r
-</blockquote>\r
-\r
-<h3 class="sectionheading">2. Install the new Moodle software</h3>\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.1.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
-<h3 class="sectionheading">3. Finishing the upgrade</h3>\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.org/">moodle.org</a> \r
- and post on the <a target=_top href="http://moodle.org/mod/forum/view.php?id=28">Installation \r
- Support Forum</a> in the Using Moodle course.</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
+<head>
+ <title>Moodle Docs: Upgrading</title>
+ <link rel="stylesheet" href="docstyles.css" type="TEXT/CSS">
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+
+<body bgcolor="#FFFFFF">
+<h1>Upgrading Moodle</h1>
+
+<blockquote>
+ <p>Moodle is designed to upgrade cleanly from any earlier version to any later
+ version. </p>
+ <p>When upgrading a Moodle installation you should follow these steps:</p>
+ <h3 class="sectionheading">1. Backup important data</h3>
+ <blockquote>
+ <p>Although it is not strictly necessary, it is always a good idea to make a
+ backup of any production system before a major upgrade, just in case you need
+ to revert back to the older version for some reason. In fact, it's a good
+ idea to automate your server to backup your Moodle installation daily, so
+ that you can skip this step.</p>
+ <p>There are three areas that need backing up:</p>
+ <blockquote>
+ <p><strong>1. The Moodle software directory itself</strong></p>
+ <blockquote>
+ <p>Make a separate copy of these files before the upgrade, so that you can
+ retrieve your config.php and any modules you have added like themes, languages
+ etc<strong><br>
+ </strong></p>
+ </blockquote>
+ <p><strong>2. Your data directory.</strong></p>
+ <blockquote>
+ <p>This is where uploaded content resides (such as course resources and
+ student assignments) so it is very important to have a backup of these
+ files anyway. Sometimes upgrades may move or rename directories within
+ your data directory.<strong><br>
+ </strong></p>
+ </blockquote>
+ <p><strong>3. Your database</strong></p>
+ <blockquote>
+ <p>Most Moodle upgrades will alter the database tables, adding or changing
+ fields. Each database has different ways to backup. One way of backing
+ up a MySQL database is to 'dump' it to a single SQL file. The following
+ example shows Unix commands to dump the database called "moodle":</p>
+ <blockquote>
+ <p><font face="Courier New, Courier, mono">mysqldump moodle > moodle-backup-2002-10-26.sql</font></p>
+ </blockquote>
+ <p>You can also use the "Export" feature in Moodle's optional
+ "Database" web interface to do the same thing on all platforms.</p>
+ <p> </p>
+ </blockquote>
+ </blockquote>
+ </blockquote>
+ <h3 class="sectionheading">2. Install the new Moodle software</h3>
+ <blockquote>
+ <p><strong>Using a downloaded archive</strong></p>
+ <blockquote>
+ <p>Do not overwrite an old installation unless you know what you are doing
+ ... sometimes old files can cause problems in new installations. The best
+ way it to rename the current Moodle directory to something else, then unpack
+ the new Moodle archive into the old location.</p>
+ <blockquote>
+ <p><font face="Courier New, Courier, mono">mv moodle moodle.backup<br>
+ tar xvzf moodle-1.1.tgz</font></p>
+ </blockquote>
+ <p>Next, copy across your config.php and any other plugins such as custom
+ themes:</p>
+ <blockquote>
+ <p><font face="Courier New, Courier, mono">cp moodle.backup/config.php moodle<br>
+ cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme</font></p>
+ </blockquote>
+ </blockquote>
+ <p><strong>Using CVS</strong></p>
+ <blockquote>
+ <p>If you are using CVS, just go into the Moodle root directory and update
+ to the new files:</p>
+ <blockquote>
+ <p><font face="Courier New, Courier, mono">cvs update -dP</font></p>
+ </blockquote>
+ <p>Make sure you use the "d" parameter to create new directories
+ if necessary, and the "P" parameter to prune empty directories.</p>
+ <p>If you have been editing Moodle files, watch the messages very closely
+ for possible conflicts. All your customised themes and non-standard plugins
+ will be untouched.</p>
+ </blockquote>
+ <p> </p>
+ </blockquote>
+ <h3 class="sectionheading">3. Finishing the upgrade</h3>
+ <blockquote>
+ <p>The last step is to trigger the upgrade processes within Moodle.</p>
+ <p>To do this just visit <a target=_top href="../admin/index.php">the admin page of your
+ installation</a>.</p>
+ <blockquote>
+ <p><font face="Courier New, Courier, mono">http://example.com/moodle/admin</font></p>
+ </blockquote>
+ <p>It doesn't matter if you are logged in as admin or not.</p>
+ <p> Moodle will automatically detect the new version and perform all the database
+ or filesystem upgrades that are necessary. If there is anything it can't do
+ itself (very rare) then you will see messages telling you what you need to
+ do. </p>
+ </blockquote>
+ <p> </p>
+ <p> Assuming all goes well (no error messages) then you can start using your new
+ version of Moodle and enjoy the new features!</p>
+ <p>If you have trouble with the upgrade, visit <a target=_top href="http://moodle.org/">moodle.org</a>
+ and post on the <a target=_top href="http://moodle.org/mod/forum/view.php?id=28">Installation
+ Support Forum</a> in the Using Moodle course.</p>
+</blockquote>
+<p> </p>
+<p> </p>
+<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
+<p align="CENTER"><font size="1">Version: $Id$</font></p>
+
+</body>
</html>
\ No newline at end of file
projects / moodle.git / commitdiff