From dfa4162d8a6665f5a883e81dfe762fdc14bf36dc Mon Sep 17 00:00:00 2001 From: wildgirl Date: Sat, 28 Jul 2007 20:27:21 +0000 Subject: [PATCH] MDL-4912 docs directory clean-up --- lang/en_utf8/docs/README.txt | 55 +- lang/en_utf8/docs/background.html | 80 -- lang/en_utf8/docs/coding.html | 270 ------ lang/en_utf8/docs/credits.html | 287 ------- lang/en_utf8/docs/cvs.html | 216 ----- lang/en_utf8/docs/developer.html | 289 ------- lang/en_utf8/docs/docstyles.css | 134 --- lang/en_utf8/docs/faq.html | 806 ------------------ lang/en_utf8/docs/features.html | 211 ----- lang/en_utf8/docs/files.php | 32 - lang/en_utf8/docs/future.html | 62 -- lang/en_utf8/docs/install.html | 448 ---------- lang/en_utf8/docs/installamp.html | 158 ---- lang/en_utf8/docs/intro.html | 44 - lang/en_utf8/docs/licence.html | 9 +- lang/en_utf8/docs/other.html | 23 - lang/en_utf8/docs/philosophy.html | 53 -- lang/en_utf8/docs/release.html | 537 ------------ lang/en_utf8/docs/releaseold.html | 1253 ---------------------------- lang/en_utf8/docs/teacher.html | 235 ------ lang/en_utf8/docs/translation.html | 249 ------ lang/en_utf8/docs/upgrade.html | 117 --- 22 files changed, 14 insertions(+), 5554 deletions(-) delete mode 100644 lang/en_utf8/docs/background.html delete mode 100644 lang/en_utf8/docs/coding.html delete mode 100644 lang/en_utf8/docs/credits.html delete mode 100644 lang/en_utf8/docs/cvs.html delete mode 100644 lang/en_utf8/docs/developer.html delete mode 100755 lang/en_utf8/docs/docstyles.css delete mode 100644 lang/en_utf8/docs/faq.html delete mode 100644 lang/en_utf8/docs/features.html delete mode 100644 lang/en_utf8/docs/files.php delete mode 100644 lang/en_utf8/docs/future.html delete mode 100644 lang/en_utf8/docs/install.html delete mode 100644 lang/en_utf8/docs/installamp.html delete mode 100644 lang/en_utf8/docs/intro.html delete mode 100644 lang/en_utf8/docs/other.html delete mode 100644 lang/en_utf8/docs/philosophy.html delete mode 100644 lang/en_utf8/docs/release.html delete mode 100644 lang/en_utf8/docs/releaseold.html delete mode 100644 lang/en_utf8/docs/teacher.html delete mode 100644 lang/en_utf8/docs/translation.html delete mode 100644 lang/en_utf8/docs/upgrade.html diff --git a/lang/en_utf8/docs/README.txt b/lang/en_utf8/docs/README.txt index 27265d05da4..627306c9ad6 100644 --- a/lang/en_utf8/docs/README.txt +++ b/lang/en_utf8/docs/README.txt @@ -1,48 +1,13 @@ -Moodle documentation --------------------- +This directory used to contain lots of documentation in HTML form. -If you want to translate this documentation into another language, -I would suggest that you: - - 1) don't include English versions of the files in this directory - because they will be used automatically anyway if it is missing - from your language pack. - - 2) translate them in this order (starting with the important ones): - - MOST IMPORTANT - |------------------- - | - | - files.php - | - install.html - | - installamp.html - | - upgrade.html - | - faq.html - | - | ----------------- - | - | - teacher.html - | - module_files.txt - | - | ----------------- - | - | - intro.html - | - features.html - | - release.html - | - | ----------------- - | - | - developer.html - | - cvs.html - | - future.html - | - | ----------------- - | - | - license.html - | - |------------------- - LEAST IMPORTANT - - 3) Please don't translate credits.html at all - it changes too much. +All of it has gone now because we now use the Moodle Docs wiki. +To find out the new locations for all the information that was here, see: + + http://docs.moodle.org/en/MoodleDocs_and_lang_packs + + http://tracker.moodle.org/browse/MDL-4912 + +Cheers, +Martin Dougiamas, 10th July 2007 diff --git a/lang/en_utf8/docs/background.html b/lang/en_utf8/docs/background.html deleted file mode 100644 index 2919676aef2..00000000000 --- a/lang/en_utf8/docs/background.html +++ /dev/null @@ -1,80 +0,0 @@ - - - - Moodle Docs: Background - - - - - -

Background

- -
-

Moodle is an active and evolving work in progress. Development was started - by Martin - Dougiamas who continues to lead the project:

-
-

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 Curtin - University of Technology 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 - :-)

-

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.

-

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. -

-

It is crucial to me that this software be easy to use - in fact it should - be as intuitive as possible.

-

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.

-
-

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. -

-

Since then there has been steady series of new releases adding new features, - better scalability and improved performance. -

-

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 Credits - page. -

-

An important feature of the Moodle project is the moodle.org - 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. -

-

In 2003, the company moodle.com - was launched to provide additional commercial support for those who need it, as - well as managed hosting, consulting and other services. -

-

For more about our future plans for Moodle, see the Future - roadmap.

-
-

Moodle Documentation

-

Version: $Id$

- - - diff --git a/lang/en_utf8/docs/coding.html b/lang/en_utf8/docs/coding.html deleted file mode 100644 index 6bea20efe1e..00000000000 --- a/lang/en_utf8/docs/coding.html +++ /dev/null @@ -1,270 +0,0 @@ - - - -Moodle Docs: Coding Guidelines - - - - -

Moodle Coding Guidelines

-

Any collaborative project needs consistency and stability - to stay strong.

-

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.

-

General Rules

-
    -
  1. All code files should use the .php extension.
    2. -
  2. All template files should use the .html extension.
    3. -
  3. All text files should use Unix-style text format (most text - editors have this as an option).
    4. -
  4. All php tags must be 'full' tags like <?php - ?> ... not 'short' tags like <? ?>. -
    5. -
  5. All existing copyright notices must be retained. You can - add your own if necessary.
    6. -
  6. Each file should include the main config.php file.
    7. -
  7. Each file should check that the user is authenticated correctly, - using the correct has_capability() or required_capability() checks.
    8. -
  8. 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. If you must write SQL code then make sure it is: cross-platform; restricted to specific functions - within your code (usually a lib.php file); and clearly marked.
    9. -
  9. Don't create or use global variables except for the standard - $CFG, $SESSION, $THEME and $USER.
    10. -
  10. All variables should be initialised or at least tested for - existence using isset() or empty() before they are used.
    11. -
  11. All strings should be translatable - create new texts in - the "lang/en" files with concise English lowercase names and retrieve them - from your code using get_string() or print_string().
    12. -
  12. All help files should be translatable - create new texts - in the "en/help" directory and call them using helpbutton(). -

    If you need to update a help file:

    -
      -
    • with a minor change, where an old translation of the - file would still make sense, then it's OK to make the change - but you should notify translation@moodle.org
      • -
    • for a major change you should create a new file by adding - an incrementing number (eg filename2.html) so that translators - can easily see it's a new version of the file. Obviously the - new code and the help index files should also be modified to point - to the newest versions.
      • -
    - -
    13. -
  13. Incoming data from the browser (sent via GET or POST) automatically - has magic_quotes applied (regardless of the PHP settings) so that you can safely - insert it straight into the database. All other raw data (from files, or from databases) - must be escaped with addslashes() before inserting it into the database.
    14. -
  14. IMPORTANT: All texts within Moodle, especially those that have - come from users, should be printed using the format_text() function. This ensures that - text is filtered and cleaned correctly.
    15. -
-

 

-

Coding Style

-

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 is, so please stick to it.

-
    -
  1. Indenting should be consistently 4 spaces. - Don't use tabs AT ALL.
    2. -
  2. Variable names 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. Use -plural names for arrays of objects. -

    GOOD: $quiz
    - GOOD: $errorstring
    -GOOD: $assignments (for an array of objects)
    - GOOD: $i (but only in little loops)
    -
    - BAD: $Quiz
    - BAD: $aReallyLongVariableNameWithoutAGoodReason
    - BAD: $error_string

    -
    3. -
  3. Constants should always be in upper case, - and always start with the name of the module. They should have words separated - by underscores. -

    define("FORUM_MODE_FLATOLDEST", - 1);

    -
    4. -
  4. Function names should be simple English - lowercase 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).
    -

    function forum_set_display_mode($mode=0) - {
    -     global     $USER, - $CFG;
    -
    -     if (    $mode) - {
    -             $USER->mode - = $mode;
    -     } else if (empty(    $USER->mode)) - {
    -             $USER->mode - = $CFG->forum_displaymode;
    -     }
    - }

    -
    5. -
  5. Blocks must always be enclosed in curly - braces (even if there is only one line). Moodle uses this style: -

    if ($quiz->attempts) - {
    -     if (    $numattempts > - $quiz->attempts) - {
    -             error($strtoomanyattempts, - "view.php?id=$cm->id");
    -     }
    - }

    -
    6. -
  6. Strings should be defined using single quotes - where possible, for increased speed.
    -

    $var = 'some text without any - variables';
    - $var = "with special characters like a new line \n";
    - $var = 'a very, very long string with a '.$single.' variable in it';
    - $var = "some $text with $many variables $within it";

    -
    7. - - -
  7. Comments should be added as much as is - practical, to explain the code flow and the purpose of functions and variables. -
      -
    • Every function (and class) should use the popular - phpDoc format. - This allows code documentation to be generated automatically.
      • -
    • Inline comments should use the // style, laid out neatly - so that it fits among the code and lines up with it.
      • -
    - -

    -/**
    - * The description should be first, with asterisks laid out exactly
    - * like this example. If you want to refer to a another function,
    - * do it like this: {@link clean_param()}. Then, add descriptions
    - * for each parameter as follows.
    - *
    - * @param int $postid The PHP type is followed by the variable name
    - * @param array $scale The PHP type is followed by the variable name
    - * @param array $ratings The PHP type is followed by the variable name
    - * @return mixed
    - */
    -function forum_get_ratings_mean($postid, - $scale, $ratings=NULL) - {
     -     if (!$ratings) - {
    -             $ratings - = array();     // - Initialize the empty array
    -         if (    $rates - = get_records("forum_ratings", - "post", $postid)) - {
    -                 // - Process each rating in turn
    -             foreach - (    $rates as $rate) - {
    - ....etc

    -
    8. - -
  8. Space 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:
    -

    foreach ($objects - as $key => - $thing) {
    -         process($thing); -
    - }
    -
    -     if ($x == - $y) - {
    -         $a - = $b;
    - } else if (    $x == - $z) {
    -         $a - = $c;
    - } else {
    -         $a - = $d;
    - }

    -
    9. -
-

 

-

Database structures

-
    -
  1. Every table must have an auto-incrementing id field (INT10) as primary index.
    2. -
  2. The main table containing instances of each module must have the same name as the module (eg widget) and contain the following minimum fields: -
      -
    • id - as described above
      • -
    • course - the id of the course that each instance belongs to
      • -
    • name - the full name of each instance of the module
      • -
    -
    3. -
  3. Other tables associated with a module that contain information about 'things' should be named widget_things (note the plural).
    4. -
  4. Column names should be simple and short, following the same rules as for variable names.
    5. -
  5. Where possible, columns that contain a reference to the id field of another table (eg widget) should be called widgetid. (Note that this convention is newish and not followed in some older tables)
    6. -
  6. Boolean fields should be implemented as small integer fields (eg INT4) containing 0 or 1, to allow for later expansion of values if necessary.
    7. -
  7. Most tables should have a timemodified field (INT10) which is updated with a current timestamp obtained with the PHP time() function.
    8. -
-

 

-

Security Issues (and handling form and URL data)

-
    -
  1. Do not rely on 'register_globals'. Every variable must be - properly initialised in every code file. It must be obvious where the variable - came from
    2. -
  2. Initialise all arrays and objects, even if empty. $a = array() - or $obj = new stdClass();.
    3. -
  3. Do not use the optional_variable() function. Use the optional_param() - function instead. Pick the correct PARAM_XXXX value for the data type you expect. To check and set an optional - value for a variable, use the set_default() function.
    4. -
  4. Do not use the require_variable() function. Use the required_param() - function instead. Pick the correct PARAM_XXXX value for the data type you expect.
    5. -
  5. Use data_submitted(), with care. Data must still be cleaned before use.
    6. -
  6. Do not use $_GET, $_POST or $_REQUEST. Use the - appropriate required_param() or optional_param() appropriate to your need.
    7. -
  7. Do not check for an action using something like if (isset($_GET['something'])). - Use, e.g., $something = optional_param( 'something',-1,PARAM_INT ) and then perform - proper test for it being in its expected range of values e.g., if ($something>=0) {....
    8. -
  8. Wherever possible group all your required_param(), optional_param() - and other variables initialisation at the beginning of each file to make them easy to find.
    9. -
  9. Use 'sesskey' mechanism to protect form handling routines from attack. - Basic example of use: when form is generated, - include <input type="hidden" name="sesskey" value="<?php echo sesskey(); ?>" />. - When you process the form check with if (!confirm_sesskey()) {error('Bad Session Key');}.
    10. -
  10. All filenames must be 'cleaned' using the clean_filename() function, if this - has not been done already by appropriate use of required_param() or optional_param() -
    11. -
  11. Any data read from the database must have addslashes() applied to it before it - can be written back. A whole object of data can be hit at once with addslashes_object().
    12. -
  12. Wherever possible, data to be stored in the database must come from POST - data (from a form with method="POST") as opposed to GET data (ie, data from the URL line).
    13. -
  13. Do not use data from $_SERVER if you can avoid it. This has portability - issues.
    14. -
  14. If it hasn't been done somewhere else, make sure all data written to the database has - been through the clean_param() function using the appropriate PARAM_XXXX for the datatype.
    15. -
  15. If you write custom SQL code, make very sure it is correct. In particular watch out for - missing quotes around values. Possible SQL 'injection' exploit.
    16. -
  16. Check all data (particularly that written to the database) in every - file it is used. Do not expect or rely on it being done somewhere else.
    17. -
  17. Blocks of code to be included should contain a definite PHP structure (e.g, - a class declaration, function definition(s) etc.) - straight blocks of code promote uninitialised - variable usage.
    18. -
-
-

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/en_utf8/docs/credits.html b/lang/en_utf8/docs/credits.html deleted file mode 100644 index 05fe0eae45a..00000000000 --- a/lang/en_utf8/docs/credits.html +++ /dev/null @@ -1,287 +0,0 @@ - - - -Moodle Docs: Credits - - - - -

Credits

-
-

Overall guidance

-
-

Martin Dougiamas is the originator, lead developer, project manager, release manager and general teaboy for the whole Moodle project. Do you take sugar?

-

The Moodle software package is Copyright © 1999-2004, Martin Dougiamas under the GNU GPL.

-

 

-
-

Main Developers

-
-

A special thanks from all of us goes to those who have contributed substantial and ongoing amounts of time - to writing Moodle code and helping it grow. These are people who "get" what developing Moodle is all about and without whom Moodle would be a far lesser thing:

-
-

- Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff

-
-

 

-
-

Other Contributors

-
-

Many other people have contributed (and are still contributing) with constructive - discussions, support, testing and various chunks of code and documentation. This list is long and always - changing, but some names include (in the order they were added): -

-
-

- Peter C. Taylor, 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, Russell Jungwirth, Przemyslaw Stencel, - John "Captain" Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, - Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, - Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker, Urs Hunkler.

-
-

Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult - to maintain! Please email Martin and make your suggestions! :-)

-

Thanks also to everyone of you who have -

- -
-

 

-

Translators

-
-

One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are - over 1000 phrases to translate (plus hundreds of help files!). Many of the languages - have more than one contributor, sometimes working together and sometimes working serially. -

-

Maintaining a list of all these wonderful people is too difficult, so please look at the Language - download page for names and details.

-

The Translation Coordinator is Koen Roggemans (translation@moodle.org).

-

 

-
-

Themes

-
-

Themes give Moodle sites some colour and life. Here are all the themes carried - as part of the Moodle distribution, along with their authors: -

- -

 

-
-

Moodle libraries

-
-

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:

- -

ADOdb   -  lib/adodb

-
-

Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, - Foxpro, Access, ADO, Sybase, DB2 and ODBC.

-

Version: 4.71
- Copyright © 2000-2006 John Lim (jlim@natsoft.com.my)
- License: Dual LGPL and BSD-style
- URL:  http://adodb.sourceforge.net -

-
- -

FPDF Class   -  lib/fpdf

-
-

Class to generate PDF files

-

Version: 1.53
- Copyright Olivier PLATHEY - License: Freeware -

-
- -

Graph Class   -  lib/graphlib.php

-
-

Class to draw line, point, bar, and area graphs, including numeric x-axis - and double y-axis.

-

Version: 1.6.3 (with modifications)
- Copyright © 2000  Herman Veluwenkamp, hermanV@mindless.com
- License: LGPL -

-
- -

html2text   -  lib/html2text.php

-
-

PHP script to convert HTML into an approximate text equivalent

-

Version: 1.0 (with modifications)
- Copyright © 2002  Mark Wilton-Jones
- License: HowToCreate script license with written permission
- URL: http://www.howtocreate.co.uk/php/
-

-
- -

htmlArea   -  lib/editor

-
-

Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla

-

Version: 3.0 beta (with modifications)
- Copyright © 2002  interactivetools.com, inc.
- License: htmlArea License (based on BSD license)
-

-
- -

IP-Atlas  -   lib/ipatlas

-
-

PHP scripts to show the location of an IP address on a map.
-
- Version: 1.0 (with modifications)
- Copyright © 2002   Ivan Kozik
- License: GNU GPL
- URL: http://www.xpenguin.com/ip-atlas.php -

-
- -

kses   -  lib/kses.php

-
-

HTML/XHTML filter that only allows some elements and attributes

-

Version: 0.2.2
- Copyright © 2002, 2003, 2005   Ulf Harnhammar
- License: GNU GPL
- URL: http://sourceforge.net/projects/kses -

-
- -

mimeTeX  -   filter/tex

-
-

Compiled C program to convert TeX into GIFs
-
- Version: 1.4
- Copyright © 2002-2004   John Forkosh Associates, Inc
- License: GNU GPL
- URL: http://www.forkosh.com/mimetex.html
- URL: http://moodle.org/download/mimetex -

-
- -

mp3player  -   lib/mp3player

-
-

Flash movie to play streaming MP3s
-
- Copyright © 2005   Andrew Walker
- License: GNU GPL

-
- -

overlibmws  -   lib/overlib.js

-
-

Javascript library to enable DHTML popups, floating windows, events etc
-
- Version: July 2004
- Copyright © 2002-2004   Foteos Macrides
- Copyright © 1998-2004   Erik Bosrup
- License: Artistic Open Source License
- URL: http://www.macridesweb.com/oltest/ -

-
- -

PclZip  -   lib/pclzip

-
-

Class to create, manage and unpack zip files.
-
- Version: 2.4
- Copyright © 2004  Vincent Blavet <vincent@phpconcept.net>
- License: GNU GPL
- URL: http://www.phpconcept.net
-

-
- -

PHP mailer   -  lib/class.phpmailer.php

-
-

Class for sending email using either sendmail, PHP mail(), or SMTP.  - Methods are based upon the standard AspEmail(tm) classes.
-
- Version 1.71,
- Copyright © 2003 Brent R. Matzelle <bmatzelle@yahoo.com>
- License: LGPL
- URL:   http://phpmailer.sourceforge.net
-

-
- -

PHP Markdown   -  lib/markdown.php

-
-

Functions to convert from the Markdown text format into clean XHTML.

-

Version: 1.0b9 (with modifications)
- Copyright © 2003-2004 , John Gruber
- Copyright © 2004 , Michel Fortin
- License: LGPL
- URL: http://www.michelf.com/projects/php-markdown/
-

-
- -

Snoopy  -   lib/snoopy

-
-

A PHP net client
-
- Version: 1.2
- Copyright © 1999-2000 Monte Ohrt <monte@ispi.net>
- License: GNU LGPL
- URL: http://snoopy.sourceforge.net/
-

-
- -

Spreadsheet::WriteExcel  -   lib/excel

-
-

A library for generating Excel Spreadsheets.
-
- Version: 2002-11-28
- Copyright © 2002  Xavier Noguer <xnoguer@rezebra.com>
- License: GNU LGPL
- URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html
-

-
- -

SMTP class   -  lib/class.smtp.php

-
-

Class that can be used to connect and communicate with any SMTP - server.
- It implements all the SMTP functions defined in RFC821 except TURN.
-
- Version: 03/26/2001
- Copyright © 2001  Chris Ryan <chris@greatbridge.com>
-

-
- -

Typo3 Character Set Class  -   lib/typo3

-
-

Class for conversion between charsets and multibyte-savy operations - with strings.
-
- CVS version: 1.54
- Copyright © 2003-2005 Kasper Skaarhoj
- License: GNU GPL
- URL: http://typo3.org/
-

-
- -
-

Moodle Documentation

-

Version: $Id$

-
- - diff --git a/lang/en_utf8/docs/cvs.html b/lang/en_utf8/docs/cvs.html deleted file mode 100644 index 70970b45538..00000000000 --- a/lang/en_utf8/docs/cvs.html +++ /dev/null @@ -1,216 +0,0 @@ - - - -Moodle Docs: How to use CVS - - - - - -

CVS for Moodle Developers

-
-

CVS is the Concurrent Versioning System, a commonly-used way of managing source code for large software projects. CVS keeps all 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 Sourceforge).

-

If you just want to download Moodle using CVS to run a site, then you probably don't need this page - just follow the simpler CVS instructions on the Moodle download page.

-

 

-
    -
  1. Joining the project as a developer
    2. -
  2. CVS Modules
    3. -
  3. Basic CVS Commands
    - 3.1. CVS on Unix
    - 3.2. CVS on Windows
    4. -
  4. Working with Branches
    - 4.1. Trunk development
    - 4.2. Stable branches for each release
    - 4.3. Feature branches for large changes
    5. -
-
-
-

1. Joining the project as a developer

-
-

So, you've been offered CVS write access to help us develop and maintain Moodle! Welcome aboard!

-

To be able to write changes into Moodle's CVS archive, you first need to have an account at Sourceforge (registration is free and easy). For the examples on this page, let's assume your username is myusername and your password is mypassword. Take special note of the sourceforge instructions to create your CVS home directory - 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.

-

Once you have a working Sourceforge account, contact Martin Dougiamas so he can set up your account with write access to particular Moodle directories.

-

To avoid being prompted for mypassword every time you run a CVS command, follow the Sourceforge directions for using authorized keys. This step is optional, but it can make your CVS experience a lot nicer.

-

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.

-

 

-
-

2. CVS Modules

-
-

Within CVS, the word "modules" refers to separate collections of code. In Moodle we have the following modules within our repository:

-
-

moodle - the main Moodle source code

-

contrib - user contributions and other assorted code in development

-

mysql - a customised phpMyAdmin to plug into Moodle for database admin

-

windows-cron - a small package that makes cron possible on Windows systems

-

docs - various extra user-contributed documentation

-
-

Most people are working on the existing features in the moodle module, but many are also contributing new ideas in the contrib modules. Once code reaches a certain level of maturity in the contrib area, it can be migrated over into the main moodle tree.

-

 

-
-

3. Basic CVS Commands

-
-

3.1 CVS on Unix

-
-

Sourceforge CVS uses ssh as a transport layer for security, so you will have to set a CVS_RSH environment variable in your Unix shell. It's best to put these commands in your .bashrc or .cshrc so you don't have to type it all the time:

-
setenv CVS_RSH ssh (for csh, tcsh etc)
- export CVS_RSH=ssh (for sh, bash etc)
-

Next, you can check out the latest development version of Moodle using this (all one line):

-
cvs -z3 -d:ext:myusername@cvs.sourceforge.net:/cvsroot/moodle co moodle
-

The command is similar for other CVS modules:

-
cvs -z3 -d:ext:myusername@cvs.sourceforge.net:/cvsroot/moodle co contrib
-

Don't try to do run this first CVS command over an existing moodle installation: start fresh with a new directory.

-

Note that you will be prompted for mypassword for each command unless you set up authorized keys.

-

Now, you should have a new 'moodle' directory. You can rename it and move it around if you like. Go into it:

-
cd moodle
-

All the latest Moodle files should be in there. You can now change files in your copy. To compare your files and directories against the main CVS copy on the server use cvs diff, e.g.:

-
cvs diff -c config-dist.php
- cvs diff -c lang
-

To fetch the latest updates from the server use:

-
cvs update -dP
-

To copy your new files back to the server you would do something like:

-
cd lang/ca
-cvs commit
-

You will be prompted to add some comments (depends on your default text editor) ... add a meaningful comment and close the editor ... the files will be sent to Sourceforge and stored. Done!

-

To save more time you can put default arguments into a file called .cvsrc in your home directory. For example, mine contains:

-
diff -c
-update -dP
-

Try 'cvs help' for more details ...

-

 

-
-

3.2 CVS on Windows

-
-

First, you need to download a completely fresh copy of Moodle using your developer account.

-
-
    -
  1. Get TortoiseCVS from tortoisecvs.org and install it, then reboot.
    2. -
  2. Find or create a new folder somewhere where you want Moodle to be downloaded to.
    3. -
  3. Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box.
    4. -
  4. Copy this text into the CVSROOT field (using your own username!): - 
     :ext:myusername@cvs.sourceforge.net:/cvsroot/moodle
    -
    5. -
  5. Under the "Module" field, type "moodle" to get the latest development version of Moodle, "contrib" to get the contributions directory, or "mysql" to get the MySQL Admin module.
    6. -
  6. Press the button: "OK" and everything should be downloaded.
    -
    7. -
-
-

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:

-
-
    -
  1. Right-mouse-click on your Moodle folder (or any file) and select "CVS Update".
    2. -
  2. Sit back and watch the logs scroll by. Take note of conflicts that may occur if your local code has changes that conflict with the incoming versions - you will need to edit these files and resolve the conflicts manually.
    -
    3. -
-
-

After modifying files (you will notice their icons change from green to red!), you can commit them back to the CVS server like this:

-
-
    -
  1. Right-mouse-click on your Moodle folder (or any file) and select "CVS Commit...".
    2. -
  2. In the dialog box, type a clear description of the changes you are committing.
    3. -
  3. Click "OK". Your changes will be sent to the server.
    -
    4. -
-
-
-

4. Working with Branches

-
-

This diagram shows how the main moodle module branches into different versions over time.

-

-

To see all the current tags and branches that are available, use this command on any old file (such as index.php in the top moodle directory):

-
cvs status -v index.php
-

Some tagging guidelines:

- -
-
-

4.1 Trunk development

-
-

The Trunk of CVS is the main development version of Moodle. In CVS it is also known as the HEAD, or default branch.

-

Moodle developers try to keep this stable as possible, but as it usually contains new code it probably has bugs and small instabilities.

-

Every now and then we decide the product has enough features to make a release. At this time, the trunk is tagged with a MOODLE_XX_BETA tag (in case we ever want to roll back to that point) and a new branch is formed for the release, called MOODLE_XX_STABLE.

-

A Beta package is also released at this point - it's for testers who don't use CVS but want to test the latest features and report bugs.

-
-

 

-

4.2 Stable branches for each release

-
-

As soon as the stable branch MOODLE_XX_STABLE is created, development efforts will fork into two streams for a while. Some people may continue working on new features in the trunk for the next release, but most developers should be concentrating on using the current STABLE branch and fixing bugs that are found in it.

-

You can switch your local copy of Moodle to the STABLE version using the following command in Unix from the root directory:

-
cvs update -dP -r MOODLE_XX_STABLE
-

After that, all the commands described above will apply to that stable version. To return to the trunk version just issue:

-
cvs update -dPA
-

On Windows clients you should have a menu from which you can choose the branch.

-

Once the new STABLE branch really stabilises, a release can be declared. Packages are created for distribution and the branch will be tagged (by Martin) with a tag named: MOODLE_XXX

-

Periodically, bug fixes in the STABLE branch should be merged into the trunk so that they become available in future versions of Moodle. A floating tag called MOODLE_XX_MERGED will be maintained to keep track of the last merge. The procedure for such a merge is as follows:

-
    -
  1. Get out the very latest trunk version.
    -
    -
    cvs update -dPA
    -
    2. -
  2. Merge everything on the branch since the last merge, into your trunk version

    -
    cvs update -kk -j MOODLE_13_MERGED -j MOODLE_13_STABLE
    -
    3. -
  3. Carefully watch the update logs for conflicts, and fix every file that you see with a conflict
    4. -
  4. Check the merged copy back into CVS trunk version
    -
    -
    cvs commit
    -
    5. -
  5. Go back to the branch version

    -
    cvs update -dPr MOODLE_13_STABLE
    -
    6. -
  6. Update the floating merge tag so that this process can be repeated next time

    -
    cvs tag -RF MOODLE_13_MERGED
    -
    7. -
-


- Finally, the values for $version in all the Moodle version.php files within the stable branch should not be updated at all if possible (except the last digit if necessary). The reason is that someone updating from a very stable version to the next very stable version could miss database upgrades that happened on the trunk.

-
-
-

4.3 Feature branches for large changes

-
-

Occasionally, there may be a very large feature that needs to be checked in so several people can work on it, but it is too unstable to be included in the main development trunk.

-

In these cases a short-term branch can be created to work on the feature, and then merged back into the main trunk as soon as possible. An example called MOODLE_14_WIDGET branch can be seen in the above diagram.

-

If you need to do this for your new WIDGET feature, follow these steps:

-
    -
  1. Discuss with other developers to make sure it's necessary!
    2. -
  2. Make a new tag on the trunk (for all of moodle) called MOODLE_XX_WIDGET_PRE -

    -
    cvs tag -R MOODLE_XX_WIDGET_PRE
    3. -
  3. Create your branch called MOODLE_XX_WIDGET -

    -
    cvs tag -Rb MOODLE_XX_WIDGET
    4. -
  4. Work in that branch until the feature is reasonably stable. Commit as necessary. -

    -
    cvs commit
    5. -
  5. When ready, merge the whole branch into the trunk, fix conflicts, commit it to the trunk and then abandon the branch. -
    -
    -
    - cvs update -dPA
    - cvs update -kk -j MOODLE_XX_WIDGET
    - cvs commit
    -
    6. -
-
-
-
-

Good luck, be careful and have fun!

-
-
-

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/en_utf8/docs/developer.html b/lang/en_utf8/docs/developer.html deleted file mode 100644 index 6834cfd4c9d..00000000000 --- a/lang/en_utf8/docs/developer.html +++ /dev/null @@ -1,289 +0,0 @@ - - - -Moodle Docs: Developers Manual - - - - - -

Developers Manual

-
-

This document describes some of Moodle's design and how you can contribute.

-

It's a bit thin at the moment - better documentation will come eventually!

-

Sections in this document:

-
    -
  1. Moodle architecture
    2. -
  2. How you can contribute - -
    3. -
-
-

 

-

1. Moodle architecture

-
-

From a system administrator's perspective, Moodle has been designed according - to the following criteria:

-
    -
  1. Moodle should run on the widest variety of platforms
    -
    - 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 more - than ten different brands of database (unfortunately, though, it can - not yet set up tables in all these databases - - more on this later).
    -
    -
    2. -
  2. Moodle should be easy to install, learn and modify
    -
    - Early prototypes of Moodle (1999) were built using Zope - - 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.
    -
    -
    3. -
  3. It should be easy to upgrade from one version to the next
    -
    - 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.
    -
    -
    4. -
  4. It should be modular to allow for growth
    -
    - 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.
    -
    -
    5. -
  5. It should be able to be used in conjunction with other systems
    -
    - 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).
    6. -
-
-

 

-

2. How you can contribute

-
-

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.

-

Learning Activities

-
-

These are by far the most important modules, and reside in the 'mod' directory. - There are a number of default modules: assignment, choice, forum, quiz, survey, wiki, etc. Each module is in a separate subdirectory and consists - of the following mandatory elements (plus extra scripts unique to each module):

-
    -
  • mod.html: a form to set up or update an instance of this module
    • -
  • version.php: defines some meta-info and provides upgrading code
    • -
  • icon.gif: a 16x16 icon for the module
    • -
  • db/: SQL dumps of all the required db tables and data (for each database - type)
    • -
  • index.php: a page to list all instances in a course
    • -
  • view.php: a page to view a particular instance
    • -
  • lib.php: any/all functions defined by the module should be in here. - If the modulename if called widget, then the required functions include: -
      -
    • widget_add_instance() - code to add a new instance of widget
      • -
    • widget_update_instance() - code to update an existing instance
      • -
    • widget_delete_instance() - code to delete an instance
      • -
    • widget_user_outline() - given an instance, return a summary of a - user's contribution
      • -
    • widget_user_complete() - given an instance, print details of a user's - contribution
      -
      • -
    • To avoid possible conflict, any module functions should be named - starting with widget_ and any constants you define should start with - WIDGET_
      • -
    -
    • -
  • Lastly, each module will have some language files that contain strings - for that module. See below.
    • -
-

The easiest way to start a new learning activity module is to use the template - in mod/newmodule_template.zip. - Unzip it and follow the README inside.

-

You might also like to post first in the Activities - modules forum on Using Moodle.

-

 

-
-

Themes

-
-

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.

-

Each theme is in a subdirectory of the "theme" directory, and - contains at least the following files:

-
    -
  • config.php: to configure how the CSS files work together. You can build your theme onto the standard or onto any parent theme, can include or exclude several CSS files.
    • -
  • styles.php: Builds the bridge to the CSS files. You don't need to edit anything.
    • -
  • header.html: 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.
    • -
  • footer.html: Included at the bottom of each page.
    • -
  • styles_color.css: CSS styles for all colour properties.
    • -
  • styles_fonts.css: CSS styles for fonts, font-size, line-height etc.
    • -
  • styles_layout.css: CSS styles for the page layout, positioning etc.
    • -
  • styles_moz.css: CSS styles for Mozilla special rounded corners.
    • -
-

To create your own themes for the current versions of Moodle:

-
    -
  1. Copy one of the existing theme folders to one with a new name. I recommend - starting with one of the standard themes.
    2. -
  2. Edit config.php to meet your demands.
    3. -
  3. Edit the CSS files with your styles.
    4. -
  4. Edit header.html and footer.html to add new logos, or change the layout. -
    5. -
-

Note also that Moodle upgrades may break themes slightly, so check - the release notes carefully if you are using a custom theme.

-

Please read the detailed description of Moodle themes in the Themes documentation in Moodle Docs.

-

More discussion about themes in the Themes - forum on Using Moodle. If you create a nice theme that you think others - might want to use, please post your zip file on the themes forum!
-

-
-

Languages

-
-

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:

-

lang/en - directory containing all files for one language - (eg English)

-
    -
  • moodle.php - strings for main interface
    • -
  • assignment.php - strings for assignment module
    • -
  • choice.php - strings for choice module
    • -
  • forum.php - strings for forum module
    • -
  • quiz.php - strings for quiz module
    • -
  • resource.php - strings for resource module
    • -
  • survey.php - strings for survey module
    • -
  • .... plus other modules if any.
    -
    - A string is called from these files using the get_string() or print_string() functions. Each string - supports variable substitution, to support variable ordering in different - languages.
    -
    -     eg $strdueby = get_string("assignmentdueby", "assignment", - userdate($date));
    -
    - If a string doesn't exist in a particular language, then the equivalent - in English will automatically be used instead.
    • -
-

lang/en/help - contains whole help pages (for popup context-sensitive - help)

-
-

Main help pages are situated here, while help pages specific to each - module are located in subdirectories with the module's name.

-

You can insert a helpbutton in a page with the helpbutton function.

-

eg helpbutton("text", "Click here for help about text");

-

and for modules:

-

helpbutton("forumtypes", "Forum types", "forum");

-
-

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, Martin - Dougiamas.

-

You might also like to post in the Languages - forum on Using Moodle.

-

If you are maintaining a language an ongoing basis, I can give you CVS - write access to the Moodle source code so that you can directly maintain - the files.

-
-

Database Schemas

-
-

Given a working database with defined tables, the intentionally simple - SQL used in Moodle should work fine with a wide variety of database brands.

-

A problem exists with automatically creating 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 lib/db - and inside the db subdirectory of each module.

-

Currently, only MySQL and PostgreSQL are fully supported in this way (no-one - wrote the schemas for other brands).

-

Moodle 1.2 will use a new method of database-independent XML schemas that - will make all this unnecessary.

-
-

 

-

Course Formats

-
-

Moodle currently supports three different course formats: weekly, topics - and social.

-

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.

-

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.

-
-

 

-

Documentation and articles

-
-

If you feel like writing a tutorial, an article, an academic paper or anything - else about Moodle, please do!

-

Put it on the web and make sure you include links to http://moodle.org/

-
-

 

-

Participating in the bug tracker

-
-

Finally, I would like to invite you to register on the "bug tracker" - at http://moodle.org/bugs - so you can file any bugs that you find and perhaps participate in discussing - and fixing them.

-

"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!

-
-
-

 

-
-
-
-

Thanks for using Moodle!
-
- Martin Dougiamas, Lead - Developer

-
-
-
-

 

-
-

 

-
-

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/en_utf8/docs/docstyles.css b/lang/en_utf8/docs/docstyles.css deleted file mode 100755 index 7ddb9a21f82..00000000000 --- a/lang/en_utf8/docs/docstyles.css +++ /dev/null @@ -1,134 +0,0 @@ -body, td, th, li { - font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif; - background-color: #FFFFFF; -} - -th { - font-weight: bold; -} - -a:link { - text-decoration: none; - color: blue; -} - -a:visited { - text-decoration: none; - color: blue; -} - -a:hover { - text-decoration: underline; - color: red; -} - -form { - margin-bottom: 0; -} - - -li { - margin-bottom: 10px; - -} - -.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; -} - -.normaltext { - font-family: "Trebuchet MS", Verdana, Arial, Helvetica, sans-serif; - font-size: medium; - border: none; - margin-left: 30px; - -} - -.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; -} - -.examplecode { - font-family: "Courier New", Courier, mono; - font-size: small; - border: thin dashed #999999; - background-color: #FBFBFB; - margin: auto; - padding: 30px; - height: auto; - width: auto; -} -h1 { - font-weight: bold; - color: #000000; - background-color: #CCCCCC; - padding: 5px; - font-size: large; - border-width: 1px; - border-color: #CCCCCC; - -moz-border-radius: 10px; -} -h2 { - font-weight: bold; - color: #FFFFFF; - background-color: #666666; - padding: 5px; - font-size: medium; - border-width: 1px; - border-color: #666666; - -moz-border-radius: 10px; -} -h3 { - font-weight: normal; - color: #FFFFFF; - background-color: #666666; - padding: 5px; - font-size: medium; - -moz-border-radius: 10px; -} -.spaced { - - margin-bottom: 30px; -} - -ul { - margin-top: 10px; - -} -.commandline { - font-family: "Courier New", Courier, mono; - font-size: x-small; - background-color: #FBFBFB; - margin: auto auto 20px 30px; - padding: 5px; - height: auto; - width: auto; - font-weight: bold; - border: 1px solid #999999; - white-space: nowrap; - display: compact; - clear: both; - float: none; -} diff --git a/lang/en_utf8/docs/faq.html b/lang/en_utf8/docs/faq.html deleted file mode 100644 index 2173c5faa69..00000000000 --- a/lang/en_utf8/docs/faq.html +++ /dev/null @@ -1,806 +0,0 @@ - - - -Moodle Docs: Frequently Asked Questions (FAQ) - - - - - -

Frequently Asked Questions (FAQ)

-

This page contains answers to some of the most - frequently asked questions by people installing Moodle. If you have - followed the installation instructions but - you still have a problem, then this page is probably the best place to be.

- -

If you don't find your answer here try the Using - Moodle 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.

- - -

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. - - - -

Use this list to jump to the appropriate answer below:

- -

Whenever I try to access or view a file that I uploaded, I get an error "File not Found"

- - - -

PHP - is it installed and what version do I have?

- - - -

Why are all my pages blank?

- - - -

My pages show fatal errors such as : call to undefined function: get_string()

- - - -

Why do I keep getting error messages about "headers already sent"?

- - - -

I keep getting this error: Failed opening required '/web/moodle/lib/setup.php'

- - - -

Any text I add with an apostrophe (') or a quote (") causes errors or comes up with a slash added

- - - -

I keep getting error messages about session_start

- - - -

When I go to the admin page, I get told to make dirroot blank!

- - - -

I login but the login link doesn't change. I am logged in and can navigate freely.

- - - -

When trying to add a resource I receive error messages.

- - - -

During the initial setting-up process, I never get asked to create an admin account!

- -

I can't log in at all- I just stay stuck on the login screen.

- -

How do I backup my Moodle site?

- -

Why doesn't my Moodle site display the - - time & date correctly?

- -

Email copies are not being sent - - from my forums

- -

 

- - - - - - - -

Whenever I try to access or view - - - - a file that I uploaded, I get an error "File not Found"

- - - -

For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg - - - - was not found on this server.

- - - -

Your web server needs to be configured to allow the part of - - - - the URL after a script name to be passed directly to the script. This is usually - - - - enabled in Apache 1, but is usually disabled by default in Apache 2. To turn - - - - it on, add this line to your httpd.conf, or to a .htaccess file in your local - - - - directory (see the Install documentation - - - - for more details):

- - - -

AcceptPathInfo on

- - - -

Note, this will ONLY work for Apache versions 2.x.

- - - -

If you are not using Apache 2 and you still have this problem - - - - (unlikely) then you can switch Moodle to use an alternative method. The disadvantages - - - - are a slight loss of performance for your users and you won't be able to use - - - - relative links within HTML resources.

- - - -

To use this alternative method: login as Admin, go into the - - - - "Configure Variables" page and change the setting for "slasharguments". - - - - You should now be able to access your uploaded files.

- - - -

 

- - - - - - - -

PHP - is it installed and what version - - - - do I have?

- - - -

Make a new file on your web site called info.php, containing the following - - - - text, and call it from your browser:

- - - - - - - -

<?PHP phpinfo() ?>

- - - -

If nothing happens then you don't have PHP installed. See the - - - - installation docs for some information about where to download it for your computer.

- - - -

 

- - - -

Why are all my pages blank?

- - - -

Check the dirroot variable in config.php. You must use complete, - - - - absolute pathnames, eg:

- - - -

$CFG->dirroot = "d:\inetpub\sites\www.yoursite.com\web\moodle";

- - - -

 

- - - -

Redhat Linux platform please see: Redhat Linux

- - - -

 

- - - -

My pages show fatal errors such - - - - as : call to undefined function: get_string()

- - - -

If you see errors like:

- - - -

Parse error: parse error, unexpected T_VARIABLE in c:\program - - - - files\easyphp\www\moodle\config.php on line 94
- - - - Fatal error: Call to undefined function: get_string() in c:\program files\easyphp\www\moodle\mod\resource\lib.php - - - - on line 11

- - - -

then it's likely you have left out a semi-colon or ending quote - - - - from a line in config.php (previous to line 94).

- - - -

Another reason could be that you have opened config.php in a - - - - program like Word to edit it, and saved it as a HTML web page, instead of a - - - - proper text file.

- - - -

 

- - - -

Why do I keep getting error messages - - - - about "headers already sent"?

- - - -

If you see errors like this:

- - - -

Warning: Cannot add header information - headers already - - - - sent by (output started at /webs/moodle/config.php:87) in /webs/moodle/lib/moodlelib.php - - - - on line 1322

- - - -

Warning: Cannot add header information - headers already - - - - sent by (output started at /webs/moodle/config.php:87) in /webs/moodle/lib/moodlelib.php - - - - on line 1323

- - - -

Warning: Cannot add header information - headers already - - - - sent by (output started at /webs/moodle/config.php:87) in /webs/moodle/login/index.php - - - - on line 54

- - - -

You have blank lines or spaces after the final ?> in your config.php - - - - file. Sometimes text editors add these - for example Notepad on Windows - so - - - - you may have to try a different text editor to remove these spaces or blank - - - - lines completely.

- - - -

 

- - - -

I keep getting this error: Failed - - - - opening required '/web/moodle/lib/setup.php'

- - - -

In your config.php, the setting that you use for the dirroot - - - - variable must be the complete path from the root of your server's hard - - - - drive.

- - - -

Sometimes people only use the path from their home directory, - - - - or relative to the root of the web server directory.

- - - -

 

- - - -

Any text I add with an apostrophe - - - - (') or a quote (") causes errors or comes up with a slash added

- - - -

Problems caused by apostrophes are caused by incorrect "magic - - - - quotes" settings. Moodle requires the following settings (which are usually - - - - the default):

- - - -

magic_quotes_gpc = On
- - - - magic_quotes_runtime = Off

- - - -

See the section on webserver - - configuration in the Installation docs for more details.

- -

 

- - - - - - - - - - - - - - - -

I keep getting error messages about session_start

- - - -

If you see errors like this:

- - - -

Warning: session_start() [function.session-start]: open(/tmp\sess_d40f380d37d431fc1516e9a895ad9ce0, O_RDWR) failed: No such file or directory (2) in G:\web\moodle\lib\setup.php on line 123

- - - -

Warning: session_start() [function.session-start]: open(/tmp\sess_d40f380d37d431fc1516e9a895ad9ce0, O_RDWR) failed: No such file or directory (2) in G:\web\moodle\lib\setup.php on line 123

- - - -

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at G:\web\moodle\lib\setup.php:1) in G:\web\moodle\lib\setup.php on line 123

- - - - - - - -

... these are all related to the fact that PHP is failing to save - - - - "session" files on your hard disk (in a directory called /tmp). Usually the - - - - reason is that you don't HAVE a directory called /tmp on your computer. This - - - - is usually the case with Windows installations. - - - - - - - -

The solution is to fix the PHP setting for this path to point to a real directory. You can do this in your php.ini file:

- - - -

session.save_path = C:\temp

- - - -

or otherwise in a .htaccess file in your main moodle directory:

- - - -

php_value session.save_path "/home/moodle/sessions"

- -

 

- - - - - - - -

When I go to the admin page, I get told to make dirroot blank!

- - - -

If you see errors like this in Moodle 1.0.9:

- - - - - - - - - - - - - - - - - - - -
Please fix your settings in config.php: - - - -

You have: - - - -

$CFG->dirroot = "/home/users/fred/public_html/moodle"; - - - -

but it should be: - - - -

$CFG->dirroot = "";

- - - - - - - -

then you have encountered a small bug that occurs on some servers. The problem is with the error-checking mechanism, not with your actual path. To fix it, find this line (line 66) in the file admin/index.php:

- - - -

if ($dirroot != $CFG->dirroot) {

- - - -

and change it to this:

- - - -

if (!empty($dirroot) and $dirroot != $CFG->dirroot) {

- -

 

- - - - - -

I login but don't appear to be. I am logged in and can navigate freely.

- - - -

Make sure the URL in your $CFG->wwwroot setting is exactly the - - same as the one you are actually using to access the site.

- -

 

- - - -

When trying to add a resource I receive error messages.

- - - -

Assuming you are using Apache, then it's quite likely that your - - setting in config.php for $CFG->wwwroot is different from the actual URL you - - are using to access the site. Also try turning off "secureforms" in the - - admin settings.

- -

 

- - - - - - - -

During the initial setting-up process, I never get asked to create an admin account!

- - - -

This is a known bug in versions of Moodle up to 1.0.9, now fixed in the main code and version 1.1.

- - - -

It doesn't affect all people, it only occurs when the person installing Moodle has a - - cookie in their browser from another program on the same site, called "user", "admin", or "teacher".

- - - -

Quick fixes include deleting those cookies from your browser before installing, using a different browser, or editing the file moodle/admin/user.php to insert these lines near the top:

- - - -

unset($user);
unset($admin);
unset($teacher);

- - - -

After performing any of these fixes it might be a good idea - - to drop all the tables in your database and re-install again from scratch.

- -

 

- - - - - - - -

I can't log in - I just stay stuck on the login screen.

- - - -

The most common cause for this is that your own computer (not your Moodle server) - - has a firewall that is stripping referrer information from the browser. Here are - - some instructions for fixing Norton firewall products.

- - - -

The server admin can also fix this for everyone by editing the Moodle configuration - - page and changing the variable "secureforms" to "No".

- - - -

Another possible cause of this problem is that sessions are - - not configured properly on the server. You can test this by calling the script - - http://yourserver/moodle/lib/session-test.php.

- -

 

- - - - - - - -

How do I backup my whole Moodle site?

- - - -

There are two main things you need to make a copy of: the database and the uploaded files. The Moodle scripts themselves are less important, since you can always download a fresh copy if you have to.

- - - -

There are many ways to do such backups. Here is an outline of a little script you can run on Unix to backup the database (it works well to have such a script run daily via a cron task

- -

cd /my/backup/directory

- -

mv moodle-database.sql.gz moodle-database-old.sql.gz

- -

mysqldump -h example.com -u myusername --password=mypassword -C -Q -e -a mydatabasename > moodle-database.sql

- -

gzip moodle-database.sql

- -

For the files, you can use rsync regularly to copy only the changed files to another host:

- -

rsync -auvtz --delete -e ssh mysshusername@example.com:/my/server/directory - - /my/backup/directory/

- -

 

- - - - - -

Why doesn't my Moodle site display the time & date correctly?

- - - -

Each language requires a specific language code (called a locale - - code) to allow dates to be displayed correctly. The language packs contain default - - standard codes, but sometimes these don't work on Windows servers.

- -

You can find the correct locale codes for Windows on these two - - pages: Language - - codes and Country/region - - codes.(eg "esp_esp" for spanish)

- -

These new locale codes can be entered on the Admin -> Configure - - -> Variables page, where they override the ones in the currently chosen language - - pack.

- -

 

- -

Email copies are not being sent - - from my forums

- -

You must set up cron properly if you want Moodle - - to send out automatic email from forums, assignments etc. This same - - process also performs a number of clean-up tasks such as deleting old unconfirmed - - users, unenrolling old students and so on.

- -

Basically, you need to set up a process to regularly call the - - script http://yoursite/admin/cron.php. Please see the - - section on cron in the Installation documentation.

- -

Tip: Try the default setting in Moodle variables page. Leave the smtphost blank. - -This will be acceptable for the majority of users. -

  -

  - - -

- - - -

Suggest - - - - a new FAQ (include the answer!)

- - - -
- - - -

Thanks to John Eyre for helping to maintain this - - - - FAQ.

- - - -

Moodle Documentation

- - - -

Version: $Id: faq.html,v 1.6 2003/03/30 13:54:28 - - - - moodler Exp $

- - - - - - - - - - - - - diff --git a/lang/en_utf8/docs/features.html b/lang/en_utf8/docs/features.html deleted file mode 100644 index dc68dffbdfc..00000000000 --- a/lang/en_utf8/docs/features.html +++ /dev/null @@ -1,211 +0,0 @@ - - - - -Moodle Docs: Features - - - - - - - -

Features

-
-

Moodle is an active and evolving product. This page lists just some of the - many features it contains:

-

Overall design

- -

Site management

- -

User management

- -

Course management

- -

Assignment Module

- - -

Chat Module

- -

Choice Module

- -

Forum Module

- -

Quiz Module

- -

Resource Module

- -

Survey Module

- -

Workshop Module

- -

 

-
-

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/en_utf8/docs/files.php b/lang/en_utf8/docs/files.php deleted file mode 100644 index 7b53b24c96a..00000000000 --- a/lang/en_utf8/docs/files.php +++ /dev/null @@ -1,32 +0,0 @@ - diff --git a/lang/en_utf8/docs/future.html b/lang/en_utf8/docs/future.html deleted file mode 100644 index f5d0e93062d..00000000000 --- a/lang/en_utf8/docs/future.html +++ /dev/null @@ -1,62 +0,0 @@ - - - - -Moodle Docs: Future - - - - - - - - -

Future

-
-

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 moodle.org/bugs. - Your contributions in the form of ideas, code, - feedback and promotion are all very welcome - see the Developers - manual and the community forums for more details. You can also pay to have certain features developed sooner- see moodle.com/development for information and a quote.

- -

Here is the current roadmap of the future, though this is always subject to change depending on sponsors and developers.

- -

Version 1.6

-
-

Blogs as the main tool for reflective activities (providing user, course and site feeds).

-

Database module, a general purpose tool for collaborative data entry, searching and browsing

-

Integration with LAMS as an activity or course format

-

Some better statistics

-

Incoming email handling

-

Basic Web Services API

-
- -

Version 1.7

-
-

My Moodle page providing a customisable overview of all courses, plus RSS feeds and so on.

-

Improved User Profile page, integrating Blogs, feeds etc in a semi-public home page

-

Preliminary support for IMS LD Level A, allowing import and export

-

Full support for SCORM 2004

-

Improved Web Services API

-

Integration with some repositories

-
- -

Version 2.0

-
-

Conditional activities, allowing dependencies and forced paths

-

Complete support for IMS LD standard

-

Improved Groups, allowing groups to be defined at site and activity level

-

Improved Roles implementation, allowing custom roles at site, course and activity level

-

Many of the main pages customisable using HTML templates.

-

Some exciting developments in making Moodle more network-aware, - with a natural evolution of Moodle's focus on collaboration. More on this here later.

-
- -
- -

 

-

Moodle Documentation

-

Version: $Id$

- diff --git a/lang/en_utf8/docs/install.html b/lang/en_utf8/docs/install.html deleted file mode 100644 index 8d949e2870c..00000000000 --- a/lang/en_utf8/docs/install.html +++ /dev/null @@ -1,448 +0,0 @@ - - - - -Moodle Docs: Basic Installation - - - - - - - - -

Installing Moodle

-

Dont panic!

-
-

This guide explains how to install Moodle for the first time. For some of these steps it goes into a lot of detail to try and cover the majority of possible - web server setups, so this document may look long and complicated. Don't panic, once you know how to do it you can install Moodle in minutes!

-

If you have problems please read this document carefully - most common issues are answered in here. - If you still have trouble, you can seek help from - Moodle Help

-

Another option is to contact a web hosting company - who can completely maintain Moodle for you, so that you can ignore all this and get straight into educating! -

-

 

-

Sections in this document:

-
    -
  1. Requirements
    2. -
  2. Download and copy files into place
    3. -
  3. Site structure
    4. -
  4. Run the installer script to create config.php -
    5. -
  5. Go to the admin page to continue configuration
    6. -
  6. Set up cron
    7. -
  7. Create a new course
    8. -
-

 

-
-

1. Requirements

-
-

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

-

The requirements for Moodle are as follows:

-
    -
  1. Web server software. Most people use Apache, - but Moodle should work fine under any web server that supports PHP, such - as IIS on Windows platforms.
    2. -
  2. PHP scripting language (version 4.1.0 - or later). PHP 5 is supported as of Moodle 1.4.
    3. -
  3. a working database server: MySQL - or PostgreSQL are - completely supported and recommended for use with Moodle.
    4. -
-

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.

-

If you want to run Moodle on your own computer and all this looks a bit daunting, - then please see our guide: Installing - Apache, MySQL and PHP. It provides some step-by-step instructions to install - all this on most popular platforms.

-

 

-
-

2. Download and copy files into place

-
-

There are two ways to get Moodle, as a compressed package and via CVS. These - are explained in detail on the download page: http://moodle.org/download/

-

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.

-

You can either place the whole folder in your web server documents directory, - in which case the site will be located at http://yourwebserver.com/moodle, - or you can copy all the contents straight into the main web server documents - directory, in which case the site will be simply http://yourwebserver.com.

-

If you are downloading Moodle to your local computer and then uploading it to your web site, it is usually better to upload the whole archive as one file, and then do the unpacking on the server. Even web hosting interfaces like Cpanel allow you to uncompress archives in the "File Manager".

-
-

 

-

3. Site structure

-
-

You can safely skip this section, but here is a quick summary of the contents of the Moodle folder, to help get - you oriented:

-
- - - - - - - - - - - - - - - -
config.php- - contains basic settings. This file does not come with Moodle - you will create it.
install.php-the script you will run to create config.php
version.php- - defines the current version of Moodle code -
index.php- - the front page of the site -
-
    -
  • admin/ - code to administrate the whole server
    • -
  • auth/ - plugin modules to authenticate users
    • -
  • blocks/ - plugin modules for the little side blocks on many pages
    • -
  • calendar/ - all the code for managing and displaying calendars
    • -
  • course/ - code to display and manage courses
    • -
  • doc/ - help documentation for Moodle (eg this page)
    • -
  • files/ - code to display and manage uploaded files
    • -
  • lang/ - texts in different languages, one directory per language
    • -
  • lib/ - libraries of core Moodle code
    • -
  • login/ - code to handle login and account creation
    • -
  • mod/ - all the main Moodle course modules are in here
    • -
  • pix/ - generic site graphics
    • -
  • theme/ - theme packs/skins to change the look of the site.
    • -
  • user/ - code to display and manage users
    • -
-

 

-
-
-

4. Run the Installer script to create config.php

-
-

To run the installer script (install.php), just try to access your Moodle main URL using a web browser, or access http://yourserver/install.php directly.

-

(The Installer will try to set a session cookie. If you get a popup warning in your browser make sure you accept that cookie!)

-

Moodle will detect that configuration is necessary and will lead you through some screens to help you create a new configuration file called config.php. At the end of the process Moodle will try and write the file into the right location, otherwise you can press a button to download it from the installer and then upload config.php into the main Moodle directory on the server.

-

Along the way the installer will test your server environment and give you suggestions about how to fix any problems. For most common issues these suggestions should be sufficient, but if you get stuck, look below for more information about some of common things that might be holding you up.
-

-
-
- -

4.1 General web server settings

-
-

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).

-

In Apache, this is done using a DirectoryIndex parameter in your httpd.conf - file. Mine usually looks like this:

-
- 
DirectoryIndex index.php index.html index.htm
-
-

Just make sure index.php is in the list (and preferably towards the start - of the list, for efficiency).

-

Secondly, if you are using Apache 2, then you should turn on the AcceptPathInfo - 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.

-
- 
AcceptPathInfo on
-
-

Thirdly, Moodle requires a number of PHP settings to be active for it to - work. On most servers these will already be the default settings. - 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):

-
- 
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
-
-
-

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 often still OVERRIDE the default settings. -

-

To do this, you need to create a file called .htaccess in Moodle's - main directory that contains lines like the following. - This only works on Apache servers and only when Overrides have been allowed in the main configuration.

-
- 
-DirectoryIndex index.php index.html index.htm
-
-<IfDefine APACHE2>
-     AcceptPathInfo 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
-
-

You can also do things like define the maximum size for uploaded files: - -

-
- 
-LimitRequestBody 0
-php_value upload_max_filesize 2M
-php_value post_max_size 2M
-
-
-

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: -

-
- 
cp lib/htaccess .htaccess
-
-
-

 

-

4.2 Creating a database

- -
-

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 for a test server, 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.

-

If you are using a webhost, they will probably have a control panel web interface for you to create your database.

-

The Cpanel system is one of the most popular of these. To create a database in Cpanel,

-
    -
  1. Click on the "MySQL Databases" icon.
    2. -
  2. Type "moodle" in the database field and click "Add Database".
    3. -
  3. Type a username and password (not one you use elsewhere) in the respective fields and click "Add User".
    4. -
  4. Now use the "Add User to Database" button to give this new user account "ALL" rights to the new database.
    5. -
  5. Note that the username and database names may be prefixed by your Cpanel account name. When entering this information into the Moodle installer - use the full names.
    6. -
-

If you have access to Unix command lines then you can do the same sort of thing by typing commands.

-

Here are some example Unix command lines for MySQL:

- 
-   # 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
-
-

And some example command lines for PostgreSQL:

- 
-   # su - postgres
-   > psql -c "create user moodleuser createdb;" template1
-   > psql -c "create database moodle;" -U moodleuser template1
-   > psql -c "alter user moodleuser nocreatedb;" template1
-
-

 

- -

4.3 Creating a data directory

- -
-

Moodle will also need some space on your server's hard disk to store uploaded files, such as course documents and user pictures.

-

The Moodle installer tries hard to create this directory for you but if it fails then you will have to create a directory for this purpose manually.

-

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, but if you must have it in the web directory then protect it by creating a file in the data directory called .htaccess, containing this line:

-
- 
deny from all
AllowOverride None
-
-

To make sure that Moodle can save uploaded files in this directory, check that the web server software (eg Apache) has permission to read, write and execute in this directory.

-

On Unix machines, this means setting the owner of the directory to be something like "nobody" or "apache", and then giving that user read, write and execute permissions.

-

On Cpanel systems you can use the "File Manager" to find the folder, click on it, then choose "Change Permissions". 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. In particular some sites that use a PHP feature known as "Safe Mode" may require the administrator to create this directory properly for you.

-
- -
- - -

5. Go to the admin page to continue configuration

-
-

Once the basic config.php has been correctly created in the previous step, trying to access the front page of your site will take you the "admin" page for the rest of the configuration.

-

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.

-

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:

-
-

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

-

SUCCESS

-
-

...and so on, followed by: Main databases set up - successfully.

-
-

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 <?php phpinfo() ?> and looking at it through a browser. Check all these and - try this page again.

-
-

Scroll down the very bottom of the page and press the "Continue" - link.

-

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. The defaults are designed to be useful and secure for most sites. Scroll down to - the bottom and click "Save changes".

-
-

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.

-
-

Next you will see more pages that print lots of status messages as they set up all the tables required by the various Moodle module. As before, they should all be green.

-

Scroll down the very bottom of the page and press the "Continue" link.

-

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".

-

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. -

-
-
-
-
-
-

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.

-
-
-
-
-

(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 "admin", - with password "admin".)

-
-

Once successful, you will be returned to the home page of your new 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:

- -

But you are not done installing yet! There is one very important thing still to do (see the next section on cron).

-
-

 

-

6. Set up cron -- IMPORTANT!

-
-

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.

-

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. This kind of regular mechanism is known as a cron service.

-

Note that the machine performing the cron does not need to be the same - machine that is running Moodle. For example, if you have a limited web - hosting service that does not have a cron service, 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.

-

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.

-

First, test that the script works by running it directly from your browser:

-
- 
http://example.com/moodle/admin/cron.php
-
-

Now, you need to set up some of way of running the script automatically and - regularly.

-

On Windows systems

-
-

The simplest way is to use this little package moodle-cron-for-windows.zip which makes this whole thing very easy by installing a small Windows service. Run it and forget about it!

-
-

On web hosting services

-
-

Your web-based control panel may have a web page that allows you to set up this cron process. For example, on Cpanel system, look for a button called "Cron jobs". In there you can put the same sort of Unix commands as listed below.

-
-

Using the command line on Unix

-
-

There are different command line programs you can use to call the page from the command line. Not all of them may be available on a given server.

-

For example, you can use a Unix utility like 'wget':

-
- 
wget -q -O /dev/null http://example.com/moodle/admin/cron.php
-
-

Note in this example that the output is thrown away (to /dev/null).

-

The same thing using lynx:

-
- 
lynx -dump http://example.com/moodle/admin/cron.php > /dev/null
-
-

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.

-
- 
/opt/bin/php /web/moodle/admin/cron.php
-
-
-
-
-

Using the crontab program on Unix

-
-

All that Cpanel does is provide a web interface to a Unix utility known as crontab. If you have a command line, you can set up crontab yourself using the command:

-
- 
crontab -e
-
-

and then adding one of the above commands like:

-
- 
*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php
-
-

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 without saving using ":q!" (without the quotes).

-
-

 

-
-

7. Create a new course

-
-

Now that Moodle is running properly, you can try creating a new course to play with.

-

Select "Create a new course" from the Admin page (or the admin - links on the home page).

-

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. Note that the yellow help icons are everywhere to provide contextual help on any aspect.

-

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.

-

Once done, the course is ready to customise, and is accessible via the "Courses" - link on the home page.

-

See the "Teacher Manual" for more details - on course-building.

-

 

-

Happy exploring and happy Moodling!

-

If you like Moodle, please consider donating to help us cover our costs!

-
-

 

-

Moodle Documentation

-

Version: $Id$

- diff --git a/lang/en_utf8/docs/installamp.html b/lang/en_utf8/docs/installamp.html deleted file mode 100644 index 50fa38eb93e..00000000000 --- a/lang/en_utf8/docs/installamp.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - Moodle Docs: Installing PHP and MySQL - - - - - -

Installing Apache, MySQL and PHP

-
-

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:

- -

 

-

Hosting Service

-
-

Unfortunately hosting services vary quite a lot in the way they work. Some - will even install Moodle for you.

-

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.

-

You should work your way through the Installation - guide and take each step at a time. Ask your hosting provider if you get - stuck.

-

 

-
-

Mac OS X

-
-

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:

-
-

PHP: Download from here: http://www.entropy.ch/software/macosx/php/

-

MySQL: Download here: http://www.entropy.ch/software/macosx/mysql/

-
-

Once these are installed the standard Installation - guide should be fairly straightforward.

-

A more detailed walkthrough is here: http://moodle.org/wiki/index.php/InstallingMoodle

-

 

-
-

Redhat Linux

-
-

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.

-

Once these are installed the standard Installation - guide should be fairly straightforward.

-

A more detailed walkthrough is here: http://moodle.org/wiki/index.php/InstallingMoodle

-
-

 

-

Windows

-
-

The easiest way to do this is use EasyPHP, - a package that bundles all the software you need into a single Windows application. - Here are the steps from start to finish:

-
    -
  1. 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 c:\my.cnf and c:\windows\my.ini.You - might want to do a search and delete ANY file called my.cnf - or my.ini.
    2. -
  2. If you've ever installed PHP before delete any files called php4ts.dll - from around your Windows directory, as well as any files called php.ini.
    3. -
  3. Download EasyPHP from here: http://www.easyphp.org/telechargements/dn.php?F=easyphp1-7 - (approx 10 Mb)
    4. -
  4. Run the downloaded file: easyphp1-7_setup.exe. 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.
    5. -
  5. 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.
    6. -
  6. 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.
    7. -
  7. Some things may be in French and you may prefer English. You can download this file http://www.easyphp.org/telechargements/dn.php?F=indexUS_1.7 which contains English versions of www and home folder in the EasyPHP1-7 folder. These can be copied over the default files.
    8. -
  8. The next thing you need to do is to set up a database for Moodle to use. - Right-click the black E in the toolbar tray and choose Administration, then click DB Management (beside PHPMyAdmin).
    9. -
  9. 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.
    10. -
  10. Create a new database by typing "moodle" into the field and - hitting the "Create" button. That was easy!
    11. -
  11. 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.
    12. -
  12. You're ready to install Moodle! Download the latest release of Moodle - from http://moodle.org/download, - then unzip the archive.
    13. -
  13. Copy your moodle files into C:\Program Files\EasyPHP\www. You - can either copy the entire moodle directory (ie C:\Program Files\EasyPHP\www\moodle) - or copy all the contents 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/.
    14. -
  14. Make a new empty folder somewhere else for Moodle to store uploaded files - in, eg: C:\moodledata
    15. -
  15. Go into your Moodle folder. Make a copy of config-dist.php, and call - it config.php
    16. -
  16. Edit config.php using a text editor (Notepad will do, just be careful - that it doesn't add unwanted spaces at the end).
    17. -
  17. Put in all your new database info:
    - $CFG->dbtype = 'mysql';
    - $CFG->dbhost = 'localhost';
    - $CFG->dbname = 'moodle';
    - $CFG->dbuser = 'root';
    - $CFG->dbpass = '';
    - $CFG->dbpersist = true;
    - $CFG->prefix = 'mdl_';
    18. -
  18. And put in all your file paths:
    - $CFG->wwwroot = 'http://localhost/moodle'; // Use an external address - if you know it.
    - $CFG->dirroot = 'C:\Program Files\EasyPHP\www\moodle';
    - $CFG->dataroot = 'C:\moodledata';
    19. -
  19. Save config.php - you can ignore the other settings if there are any.
    20. -
  20. You're nearly there now! The rest of the setup is all web-based. Visit - http://localhost/moodle/admin/ - with your browser to continue the setup via your browser.
    21. -
  21. 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 (C:\Program Files\EasyPHP), 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.
    22. -
  22. Lastly, you need to set up some sort of cron. See the Installation - guide for more details on this.
    23. -
-

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:

-
    -
  • 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'. -
    • -
  • Make sure you enable the Zlib module so that you can create and unpack - zip files from within Moodle.
    • -
  • Make sure sessions is turned on - you may have to edit php.ini and fix - the directory for session.save_path - instead of the default - "/tmp" use a Windows directory like "c:/temp".
    • -
-

 

-
-
-

Moodle Documentation

-

Version: $Id$

- - - diff --git a/lang/en_utf8/docs/intro.html b/lang/en_utf8/docs/intro.html deleted file mode 100644 index b4f264132df..00000000000 --- a/lang/en_utf8/docs/intro.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - -Moodle Docs: Introduction - - - - - - - -

Introduction

-
-

Moodle is a software package for producing internet-based courses and web sites. - It's an ongoing development project designed to support a social constructionist framework of education.

-

Moodle is provided freely as - Open Source software (under the - GNU Public License). 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: provide the source to others; not - modify or remove the original license and copyrights, and apply - this same license to any derivative work. Read the license for full - details and please contact the copyright - holder directly if you have any questions. -

-

Moodle will run on any computer that can run - PHP, and can support many types of database (particularly MySQL).

-

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.

-

Come moodle with us!

-
-


-

-

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/en_utf8/docs/licence.html b/lang/en_utf8/docs/licence.html index c02ada19d28..97a2f34a82b 100644 --- a/lang/en_utf8/docs/licence.html +++ b/lang/en_utf8/docs/licence.html @@ -10,18 +10,17 @@ + +(For the most up-to-date version of this license, see Moodle Docs).

Copyright License for Moodle

The name Moodle™ is a registered trademark of The Moodle Trust.
- If you are intending to use the name to promote commercial Moodle services,
- then you must seek permission from the Trust via the moodle.com helpdesk,
- in accordance with normal trademark restrictions. There are no restrictions
- on how you use the name in other contexts.
+ If you are intending to use the name to advertise commercial generic Moodle services (eg Moodle Hosting, Moodle Support, Moodle Certification etc), then you must seek direct permission in writing from Martin Dougiamas via the moodle.com helpdesk, in accordance with normal trademark restrictions. There are no restrictions on how you use the name in other contexts (for example, if you use Moodle just to provide courses then you can use the name freely to refer to it.) If you aren't sure of a particular case, please ask us via the moodle.com helpdesk: we'll be happy to either provide you with official permission in writing or help you fix your wording.

The software Moodle is Copyright © 1999 onwards, - Martin Dougiamas.

+ Martin Dougiamas with portions contributed by many others.

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
diff --git a/lang/en_utf8/docs/other.html b/lang/en_utf8/docs/other.html deleted file mode 100644 index b216cae1ff6..00000000000 --- a/lang/en_utf8/docs/other.html +++ /dev/null @@ -1,23 +0,0 @@ - - - -Moodle Docs: Frequently Asked Questions (FAQ) - - - - - -

Other documentation

-

Here are some links to other sources of Moodle documentation:

-

Index of all Moodle - help pages - a list of all the context-sensitive help files within Moodle

-

User-contributed documentation - - this page lists documentation contributed by Moodle users

-

 

-
- -

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/en_utf8/docs/philosophy.html b/lang/en_utf8/docs/philosophy.html deleted file mode 100644 index 67e12fca3bc..00000000000 --- a/lang/en_utf8/docs/philosophy.html +++ /dev/null @@ -1,53 +0,0 @@ - - - - -Moodle Docs: Philosophy - - - - - - - -

Philosophy

- -
-

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 "social constructionist pedagogy". (Some of you scientists may already be thinking "soft education mumbo jumbo" and reaching for your mouse, but please read on - this is useful for every subject area!)

-

This page tries to explain in simple terms what that phrase means by unpacking four main concepts behind it. Note that each of these is summarising one view of an immense amount of diverse research so these definitions may seem thin if you have read about these before.

-

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.
-

-

1. Constructivism

-
-

This point of view maintains that people actively construct new knowledge as they interact with their environment.

-

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.

-

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.
-

-
-

2. Constructionism

-
-

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.

-

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.
-

-
-

3. Social Constructivism

-
-

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.

-

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 "shapes" 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.
-

-
-

4. Connected and Separate

-
-

This idea looks deeper into the motivations of individuals within a discussion. Separate 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. Connected 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. Constructed 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.

-

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.

-
-
-

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.

-

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.

-
-
-

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/en_utf8/docs/release.html b/lang/en_utf8/docs/release.html deleted file mode 100644 index 235fc449a44..00000000000 --- a/lang/en_utf8/docs/release.html +++ /dev/null @@ -1,537 +0,0 @@ - - - - -Moodle Docs: Current Release notes - - - - - - - - - - - -

Latest Release notes

- -

Moodle 1.5.3 (11th November, 2005)

- -

(Because this release contains important security fixes, we highly advise - that sites using any previous version of Moodle upgrade to this version - as soon as possible.)

- -

A few new things

- - - -

Various fixes

- -

General

- - -

Authentication

- -

Enrolment & Metacourses

- - -

Resources

- - -

Forums

- - -

Blocks

- - -

Quiz

- - -

SCORM

- - -

Wiki

- - -

Filters

- - - - -

Moodle 1.5.2 (16th July, 2005)

- -

Various fixes

- - -

Some new things

- - - -
-

Moodle 1.5.1 (8th July, 2005)

- -

Various fixes

- - -

Some new things

- - - -
- - -

Moodle 1.5 (5th June, 2005)

- -

Headline features

- - -

Other Major System-wide Improvements

-

Admin

- - -

Authentication

- - - -

Files

- - -

Filters

- - -

Themes

- - -

HTML Editor

- - -

Course management

- - - -

New blocks

- - -

Calendar

- - -

Activity Module Improvements

-

Assignment

- - -

Chat

- - -

Choice

- - -

Forum

- - -

Glossary

- - -

Journal

- - -

Lesson

- - - -

Quiz

- - - -

Scorm

- - -

Survey

- - -

Wiki

- - - - - -
-
-
If you experience any bugs in this release, please report them moodle.org/bugs so we can fix them in the next release.
-
-
-

-Old release information -

-
-
-

Moodle Documentation

-

Version: $Id$

diff --git a/lang/en_utf8/docs/releaseold.html b/lang/en_utf8/docs/releaseold.html deleted file mode 100644 index 2a0673b3358..00000000000 --- a/lang/en_utf8/docs/releaseold.html +++ /dev/null @@ -1,1253 +0,0 @@ - - - - -Moodle Docs: Old Release notes - - - - - - - - - - - -

Old Release notes

- -

Moodle 1.4.5 (7th May, 2005)

- -

(Because this release contains important security fixes, we highly advise that sites using any - previous version of Moodle upgrade to this version as soon as possible.)

- - -
-
Some important security fixes
-
-
    -
  • Preventative measures against attacks to admin functions.
    • -
  • Lesson: Safer hiding of lessons (#2733)
    • -
-
- -
A few new things
-
-
    -
  • Flash Media Player: Now playing can start before the download is complete.
    • -
  • Added/updated language support for German (DE) and Turkish (TR).
    • -
  • Release notes now link to the relevant bugs.
    • -
  • Prefetching requests from Google Web Accelerator, Mozilla etc are denied.
    • -
-
-
Performance improvements
-
-
    -
  • Added option to cache the languages list. Saves around 10MB of memory and 40 includes. See config-dist.php for details on how to enable.
    • -
  • Major efficiency improvements for Postgres databases on insert. Also fixed many calls to insert_record() which discard the returned record id to not ask for the record id.
    • -
-
- -
Other bug fixes
-
-
    -
  • HTML Editor: Fixes to some character encoding problems.
    • -
  • Quiz: fixes to export/import dropdown (#2963)
    • -
  • Quiz: Don't throw a fatal error on unknown question, try to continue.
    • -
  • Course Social Forum: Removed misleading link to unsubscribe (#2945).
    • -
  • Additional/updated translations.
    • -
  • Forums and Groups: Allow students not in a group to post into a discussion which is also not in a group, even if the course is using groups.
    • -
  • Sitewide HTML Editor settings: Fixed Can't save changes in editor configuration form bug.
    • -
  • Cron: Removed some warnings.
    • -
  • Choice: Choice shows a bad number of answers (#2452).
    • -
  • Better support for PHP5: Files uploads now use $_FILES rather than deprecated $HTTP_POST_FILES (#2828)
    • -
  • Backup/Restore: Manual links from lesson pages to resources are now preserved between backup/restore anywhere. (see this discussion)
    • -
  • Some fixes for Postgres constraint naming.
    • -
  • I18N support: Reset proper encoding upon login (#2770).
    • -
  • I18N support: Fixed some instances of garbled characters when using utf-8 in HTML Editor (#2763)
    • -
  • Flash Media Player: Turn off the autoloading of sound files.
    • -
  • Flash Media Player: Better handling of filenames files.
    • -
  • Postgres: Fixed sequences out of sequence (#2742).
    • -
  • Backup: Fixed memory limit overrun in backup config page.
    • -
  • Forums: Fixed error warnings when a teacher posts to a forum (#2723).
    • -
-
- - - -
- - -

 

- -

Moodle 1.4.4 (7th March, 2005)

- -
-
Some important security fixes
-
-
    -
  • Added strong URL validation functions.
    • -
  • Preventative measures against tampering of config settings.
    • -
  • Tighter input validation in Quiz, HTML editor and course edit.
    • -
  • More control over user's language settings.
    • -
  • Safer cleaning of HTML-formatted input.
    • -
-
- -
A few new things
-
-
    -
  • New MP3 content filter with Flash-based mp3 player.
    • -
  • Better display of options in the Choice module.
    • -
  • UI enhancements in HTML Editor's table editor.
    • -
  • $CFG settings in config.php now override database settings.
    • -
  • Enabled garbage collection for Debian systems, with the option to disable it. Fixes stale session problems.
    • -
-
- -
Performance improvements
-
-
    -
  • Serious performance optimizations in forums code.
    • -
  • Various optimizations by removing unnecessary database retrievals and sorting.
    • -
  • Major improvements in handling session locking. Downloading large files or monitoring the live logs will no longer slow down navigation in other windows.
    • -
-
- -
Other bug fixes
-
-
    -
  • Installer: Many fixes and updates from HEAD (including #2625) .
    • -
  • Installer: We now check for allow_url_fopen() before trying to validate our own URL.
    • - -
  • Fixed some forum search problems.
    • -
  • Fixed sorting bug on forums (#2613).
    • - -
  • Fixed problems in user searches with trailing spaces.
    • -
  • Fixed some instances of hardcoded /admin path.
    • -
  • Fixed some groups-related bugs (#2133, #2550, #2363)
    • -
  • Don't send HTML digests to people who want plain text email.
    • - -
  • SCORM module — fixed navbar error.
    • - -
  • Chat: Increased maximum socket read size to prevent empty pages and repeated messages
    • -
  • Files: added a "Parent Folder" icon, (#2491).
    • - -
  • Postgres support: consistency fix in mdl_log table.
    • - -
  • Auth plugins: Better cleanup and truncation of data.
    • -
  • Auth plugins: Fixed external authentication problem — if logged in as guest, logging in as external auth user fails if it is the first login ever for the account.
    • -
  • Auth LDAP: Fixed a regression from 1.4.2 where a trailing semicolon in some config fields would break authentication.
    • -
  • Auth DB: Database Authentication not fetching user data fields correctly (#2319).
    • - -
  • Paypal Enrolment plugin: Now text sent to PayPal can - be 'sanitised' to avoid some diacritics (Spanish for now) which break the - enrol process. Only German and French diacritics are supported for - now by PayPal. This functionality can be easily expanded to other - characters.
    • - -
  • Backup/restore: If the user isn't admin and the restored course hasn't teachers, add teacher (#2381)
    • -
  • Backup/restore: Fixed errors with courses with apostrophes in the fullname.
    • -
  • Backup/restore: Now group members are - only included (backup and restore) if we have selected to have - users (#2486).
    • -
  • Backup/Restore: General tidyup.
    • - -
  • Glossary: Now 0 rates are supported in glossary (#2582) and better PHP5 support (#2581).
    • -
  • Glossary & Blackboard: import fixes (#2310).
    • - -
  • Calendar: more robust handling of bad data.
    • -
  • Calendar: HTML fixes in calendar (#2350).
    • - -
  • Course sortorder was broken in 1.4.3 and would sometimes prevent course creation — all the known problems with sortorder are now fixed. Includes some related fixes in get_categories() calls that would sometimes show up in "My Courses" listings.
    • - -
  • Wiki: Several fixes.
    • -
  • Loglive now has an appropriate page footer.
    • - -
  • Plus general cleanup and tidyups of the code.
    • -
-
- - - -
- - -

 

- - -

Moodle 1.4.3 (21st December, 2004)

- -
-
Some important security fixes
-
-
    -
  • Better checking/cleaning of cookie data
    • -
  • Preventative measures for session fixation
    • -
  • Better checking/cleaning of parameters for RSS feeds, ip atlas parameters, glossary, forum, theme selection, SCORM module, document viewer
    • -
  • Added protection in viewing of uploaded files
    • -
  • Added protection against directory traversal
    • -
  • Fix for variable $FULLME necessary for cron
    • -
  • Prevention against internal libraries being called directly.
    • -
  • Prevent viewing of glossary if it's a hidden activity
    • -
  • Hidden sections hidden from students in recent activity
    • -
  • Fixed problem with guest user being able to see events in the calendar
    • -
  • Fixed encoding of TEX expressions
    • -
-
- -
A few new things
-
-
    -
  • Enforced enrolment uniqueness, this is also a performance fix.
    • -
  • Added transaction support for PostgreSQL
    • -
  • Logging in and logging out are now logged
    • -
  • Wiki and SCORM now both use new zipping code - this fixes reported SCORM issues
    • -
  • New paging system for glossary
    • -
  • User info from LDAP truncated for insertion into moodle to prevent data loss
    • -
  • Updated pclzip to new version
    • -
  • Memory_limit can be overriden by higher config settings from php.ini, commandline, httpd.conf, .htaccess
    • -
  • New translations started: Maori, Kannada, Albanian and Vietnamese
    • -
  • Many additions to other language packs
    • -
  • Teachers can now always try quizzes, even if they're not open yet
    • -
  • Glossary print view is now different for each format.
    • -
  • Glossary search now also searches aliases
    • -
  • Vastly improved multilang filter with more forgiving syntax
    • -
-
- -
Performance improvements
-
-
    -
  • Better caching headers mean improved performance on all pages when using back button
    • -
  • Database indexes added in many places to enhance performance in large scale deployments
    • -
  • Performance improvements throughout moodle where courses were being listed.
    • -
  • Various optimizations by removing unnecessary database retrievals and sorting.
    • -
-
- -
Other bug fixes
-
-
    -
  • Fixed restoring into a new course generating duplicate course idnumbers
    • -
  • Fixed many small Postgres issues
    • -
  • Fixed unnecessary notices when debug mode on
    • -
  • Fixed some more PHP5 Notices
    • -
  • Fixed support for apostrophes, quotes and backslashes in LDAP user data
    • -
  • Fix for pagination of search course results for Postgres
    • -
  • Fixed bug with whitespace in user search
    • -
  • Fixed chatroom bug where all chat users listed in multiple chatrooms
    • -
  • Fix for installation script bug
    • -
  • Case sensitive usernames in bulk user import fixed
    • -
  • Fixed bug in redirection after rating forum post
    • -
  • Fixed bug in quiz with matching questions
    • -
  • Fixed bug in quiz preview
    • -
  • Fixed bug in language editing
    • -
  • Multiple small fixes in SCORM module
    • -
  • SCORM module shows user pictures properly
    • -
  • Activity names sorted by name in activity filter
    • -
  • Glossary search will search aliases as well
    • -
  • Any RSS errors will result in a valid RSS error file rather than invalid RSS.
    • -
  • Fixed problem with SCORM package validation and PHP5
    • -
  • Fixed problem with backup/restore and empty categories
    • -
  • Better XHTML in wiki
    • -
  • Bug fix in chat reports for first chat session
    • -
  • Fixed a problem with SCORM when deleting a lot of files, or very large files
    • -
  • Fixed some problems with encyclopedia format in glossary
    • -
  • Fixed bug in SCORM integration with zipping code
    • -
  • Fixed bug in dialogue plain text email notifications
    • -
  • Fixed missing sesskey variables in social activity block
    • -
  • Excess sections for a course are now hidden in the navmenu
    • -
  • Added daylight savings time fixes for the calendar
    • -
  • First quiz edit in a new course has a default category assigned
    • -
  • Fixed bug in paypal module when accepting payment amount
    • -
  • Fixed bug in course files with loss of choose mode
    • -
-
- - - -
- - -

 

- - - -

Moodle 1.4.2 (5th November, 2004)

- -
-
Some important security fixes
-
-
    -
  • Better checking/cleaning of script parameters used in quite a few areas - throughout Moodle (a BIG thanks to Petr Skoda for his recent security audit!)
    • -
  • Quoted some SQL parameters in the glossary module to prevent possible injection
    • -
-
- -
A few small new things
-
-
    -
  • New PAM authentication module for direct authentication on Unix/Linux
    • -
  • Course creators can now restore to new or existing courses
    • -
  • Forum posts now include detailed headers to allow correct threading in mail clients
    • -
-
- -
And a bunch of other bug fixes
-
-
    -
  • Backup is now more able to cope with errors (eg if backup is interrupted) - and can clean up uncompleted files
    • -
  • Fix for database authentication against a PostgreSQL database
    • -
  • Fixes for some parts of installation to PostgreSQL
    • -
  • Forum subject lines are now only broken up in recent activity display
    • -
  • Database-based enrolments now actually work :-)
    • -
  • SQL fixes for creation of RSS feeds from PostgreSQL
    • -
  • Added rtsp to the list of allowed protocols in cleaned HTML text
    • -
  • User profile and profile editing page can be called without parameters
    • -
  • Upgraded xmlize library to latest version
    • -
  • Upgraded phpmailer library to latest version
    • -
  • Various small code-only cleanups
    • -
  • Admin menu now allows backup/restore of the "site course" (front page)
    • -
  • Fixed a display bug in the forums index which only showed in PHP5
    • -
  • Highlighting function (eg after search) was stripping backslashes
    • -
  • Info from LDAP is now decoded from utf8
    • -
  • Course listings now work better with very large amounts of courses
    • -
  • Two SCORM bugs fixed (a typo and a problem with onbeforeunload)
    • -
  • Some cleanups when printing text, headers and variables in Lesson
    • -
  • Calendar now functions as expected even when you login as someone else
    • -
  • Fixed a few remaining short PHP tags
    • -
  • Better randomness for random questions (fix for bug introduced in 1.4)
    • -
  • When a teacher is removed from a course, they are now also removed from all groups in that course
    • -
  • Fixed strip_pages bug in Wiki
    • -
  • Fixes for charset detection in backups and multilang filter under PHP5
    • -
-
- -
-
- -

Moodle 1.4.1 (12th September, 2004)

- -
-
A few little new things
-
-
    -
  • New "Email Protection" filter will obfuscate all email addresses within all texts - (to help prevent automated address-harvesting)
    • -
  • Allowed email addresses can now be restricted (see config-dist.php for details)
    • -
  • Extra instructions for translators embedded in translation interface
    • -
  • New help page for Directory Paths
    • -
-
-
And some bug fixes
-
-
    -
  • Improved performance when viewing site logs
    • -
  • Improved paging and performance in glossary
    • -
  • Glossary entries are now shown correctly if they belong to multiple categories
    • -
  • Do not redeclare auth_user_login upon failed login
    • -
  • Fixed two missing icons in the cordoroyblue theme
    • -
  • Fixed missing "New event" button on Upcoming Events page
    • -
  • Always addslashes on chat messages from daemon users before inserting into db.
    • -
  • Fixes for handling of fixed enrollment periods when this is set for a course
    • -
  • Site course ID (defined as SITEID) is no longer assumed to be always 1
    • -
  • Default memory limits are increased beyond 16M, to help Moodle continue - working even when there is some unplanned memory problem
    • -
  • Smilies are now rendered as pictures in Markdown format texts
    • -
  • Workshops work under Recent Activity again
    • -
  • file.php can now only be used to access data within courses
    • -
  • Improved behaviour of calendar blocks on home page
    • -
  • Fixed quotes bug with PostgreSQL database specification produced by installer
    • -
  • Fixed sometimes-missing display of correct answers during quiz review
    • -
  • <tt> and <code> are now allowed tags
    • -
  • Section summaries, course summaries and labels are again no longer cleaned of Javascript
    • -
  • Fixed a rare LDAP bug that could cause new accounts not to be created
    • -
-
-
-
-

Moodle 1.4 (31st August, 2004)

- -
-
Headlines
-
-
    -
  • Compatibility with PHP 5
    • -
  • New easy installer wizard leads you through the creation of the initial config.php file
    • -
  • Installation is now completely localised to your preferred language
    • -
  • Completely revamped Resource module make it easier to add new resources and to send data to them.
    • -
  • New Enrolment system featuring modules such as completely automated Paypal payments, - flatfile scanning, or external database control.
    • -
  • Blocks now work on the front page, plus you can put a topic section above the middle part
    • -
  • Chat now includes a server-side daemon (in PHP) for scalable, instant chat
    • -
  • New Wiki module!
    • -
  • New support for editing text using the Markdown format
    • -
  • Many bug fixes in all areas
    • -
-
- -
Under the hood
-
-
    -
  • Resource module has its own Add menu now, and uses class-based submodules, making it much - easier now to add new resource types to this menu
    • -
  • Quiz module has been refactored into class-based questiontype plugins.
    • -
  • Enrolment process has been refactored into class-based enrolment plugins.
    • -
  • Glossary display formats are now name-based, and it's easier to plugin new ones.
    • -
  • Improved behaviour of many modules when they are used on the site page.
    • -
  • Revised Filter structure is faster and now compatible with Turck MMcache.
    • -
  • Adding activities is now more forgiving of fields left empty
    • -
  • We can now alter PostgreSQL columns at will using table_column()
    • -
  • RSS generation has been sped up tremendously, putting much less load on cron
    • -
  • Some bigger modules have split lib.php into locallib.php for less memory usage
    • -
-
- -
Languages and localisation
-
-
    -
  • Updates to nearly every language pack
    • -
  • Moodle can override the default character set in Apache, making languages more reliable
    • -
  • Multibyte languages now wrap properly
    • -
  • Better handling of locales and encodings on very multilingual sites (like moodle.org)
    • -
  • New languages: Slovenian and Hebrew!
    • -
-
- -
Security Fixes
-
-
    -
  • Fixed a number of possible XSS entry points and path disclosures
    • -
  • Attributes of tags in HTML are now parsed even more thoroughly for naughty scripts
    • -
  • User profile pages are no longer available by default to strangers
    • -
  • All text is now cleaned on output (not just input)
    • -
  • Email addresses are not used on outgoing mail if the user requests that
    • -
  • New setting loginhttps will use secure https for the login, then switch back to http
    • -
-
- -
Administration
-
-
    -
  • Spiffy new interfaces for adding/removing students, creators and admins
    • -
  • Failed logins are now logged, and can be displayed to users upon a successful login
    • -
  • Logs now support viewing by group, and by errors
    • -
  • Modules now behave more consistently on the site front page
    • -
  • Front page "students" can be all users on site, or all users in at least one course on the site
    • -
  • Email-sending can now be enabled/disabled on any user's profile page
    • -
-
- -
Authentication
-
-
    -
  • All authentication methods will now co-exist with internally-created accounts
    • -
  • New support for authenticating against First Class servers
    • -
  • Fixes for POP3 authentication
    • -
-
- -
Navigation
-
-
    -
  • Visitors can be automatically logged in as guest
    • -
  • Jump menu now always shows "Jump to" to help distribute clues about what it does
    • -
  • Jump menu now has a much clearer way of grouping activities into sections
    • -
-
- -
Blocks
-
-
    -
  • Block system can now cope with custom course formats and changes in format
    • -
  • New login block allows login from site front page
    • -
  • Online users block on home page shows users from the whole site
    • -
-
- -
Editor
-
-
    -
  • New editor configuration screen for the admin
    • -
  • New support for anchors within pages
    • -
  • Spell-checking is now supported in the editor, it uses aspell on your server operating system
    • -
-
- -
Chat
-
-
    -
  • Chat now includes a server-side daemon (in PHP) for scalable, instant chat
    • -
-
- -
Choice
-
-
    -
  • Significantly revamped to make a lot more sense, with more option
    • -
-
- -
Forum
-
-
    -
  • Several fixes when dealing with groups
    • -
  • Users can choose to receive forum posts as daily digests of subject lines or whole posts.
    • -
  • Discussion listing is now paged
    • -
  • Teachers now have complete control over forum subscriptions, and can subscribe anyone at will
    • -
  • "Last post" date is shortened and linked to the last post
    • -
  • Forums now list RSS feeds on the index page
    • -
  • Better-looking HTML mail using the full stylesheet
    • -
  • Forum mail older than two days is never sent out (to prevent unwanted floods)
    • -
  • Blocked mail is logged so that teachers can see it
    • -
  • Discussion branches can be "split" from the main discussion, into a new discussion
    • -
-
- -
Glossary
-
-
    -
  • Glossary entries can be defined as "always editable"
    • -
  • Glossaries now list RSS feeds on the index page
    • -
  • Many fixes throughout
    • -
-
- -
Quiz
-
-
    -
  • New floating timer for timed quizzes
    • -
  • Attempts may now be restricted to specific computers
    • -
  • Quizzes can now require a special password
    • -
  • New question type for Calculated Questions
    • -
  • Numerical questions now support units
  • Questions can be previewed in the editing pages
    • -
  • Questions can now be exported in several formats
    • -
  • More intelligent handling of category listing when editing questions
    • -
  • New (and incomplete) XML export format, will eventually be quiz-feature-complete
    • -
  • Shortanswers can now contain all sorts of strange characters
    • -
-
- -
Resource
-
-
    -
  • Adding resources is now a one-step process with more control
    • -
  • Web page, Web link, Uploaded file and Program resource all combined into one type!
    • -
  • Program resources replaced by Parameters that allow a lot of of interesting interaction with external resources, both remote and uploaded into Moodle.
    • -
  • Collapsible forms with memory to make forms less daunting for beginners without slowing down experienced users
    • -
-
- -
SCORM
-
-
    -
  • Many fixes and improvements - works with an even wider variety of packages
    • -
  • Optional extra verification of the manifest file
    • -
-
-
-
- - -

New in Moodle 1.3.4 (11th August, 2004)

-
-
Updates
-
-
    -
  • Some compatibility was added for handling glossaries and resources from Moodle 1.4.
    • -
  • Forbid restricted users from changing enrolments
    • -
-
-
Bug fixes
-
-
    -
  • Fixed a reported vulnerability involving arguments to forum/post.php file
    • -
  • Fixed a possible vulnerability involving strings in Moodle texts
    • -
  • Fixed a rare glitch with attempt numbers in quizzes
    • -
  • Fixed a bug with regular expression logic in short answers
    • -
  • Fixed a typo in the PostgreSQL install
    • -
  • Fixed some documentation links
    • -
-
-
- -
- -

New in Moodle 1.3.3 (16th July, 2004)

-
-
Updates
-
-
    -
  • The ADOdb library was upgraded to a version compatible with PHP 5.0
    • -
  • Improvements to the detection and conversion of URLs in backups
    • -
-
-
Bug fixes
-
-
    -
  • A possible vulnerability involving arguments to the help.php file was fixed.
    • -
  • A possible vulnerability involving language setting was fixed.
    • -
  • Fixes for the editing of lang strings with double quotes in them
    • -
  • Several small problems fixed in Glossary
    • -
  • Some minor issues fixed in the Scorm module
    • -
-
-
- -
- - -

New in Moodle 1.3.2 (9th July, 2004)

-
-
Updates
-
-
    -
  • The SCORM module is now included as standard
    • -
  • Some new languages (Malaysian, Estonian)
    • -
  • Many more existing languages are now completed up to 1.3.x
    • -
-
-
Bug fixes
-
-
    -
  • A possible front page vulnerability with Moodle servers on some old PHP versions was fixed. If you are using a version of PHP previous to 4.3 then it might be a good idea to upgrade to this version of Moodle.
    • -
  • Important fixes to logic when forums are used for group activities
    • -
  • Editing teacher profiles are visible even to separated groups in a class
    • -
  • Subject lines in multibyte languages in recent activity are no longer broken by wrapping function
    • -
  • A few issues related to glossary export/import were fixed
    • -
  • Backup is now better at managing it's temporary files
    • -
  • Other small fixes here and there
    • -
-
-
-
- - -

New in Moodle 1.3.1 (4th June, 2004)

-
-
Bug fixes
-
-
    -
  • Some HTML code affecting stability of HTML editor under IE6 on some pages was fixed
    • -
  • Some bugs were fixed in several auto-linking text filters
    • -
  • Improved-looking navigation bar (using the » character)
    • -
  • Flash files now have their own icon
    • -
  • Adding course links using HTML editor now fixed for teachers
    • -
  • Section links block now preserves focussed view
    • -
  • Sites files now respect forcelogin setting
    • -
  • Upgrading blocks without database functions now works
    • -
  • Language updates
    • -
-
-
-
- -

New in Moodle 1.3 (25th May, 2004)

-
-
Major new features
-
-
    -
  • New Calendar feature (thanks to Jon Papaioannou and the Greek School Network!)
    • -
  • New Blocks feature, allowing blocks to be added and moved around on course pages (thanks to Jon Papaioannou, Eloy Lafuente and others!)
    • -
  • New RSS System allows Forums and Glossaries (and later other modules) to publish RSS feeds (Thanks, Eloy!)
    • -
  • Mediaplugin filter now supports auto-embedding of Quicktime, Flash, and Windows Media files.
    • -
  • A new Activity Names filter will automatically add hyperlinks to other activities in the same course whenever their name is mentioned.
    • -
-
-
Other new features
-
-
    -
  • New resource type "Directory" will display a whole directory of uploaded files (including subdirectories)
    • -
  • Resources that are files (uploaded, or webpages) now show the relevant icon on the course page
    • -
  • Most internal HTML links within forums and resources are now preserved during backup/restores
    • -
  • It is now possible to pass normal http arguments to files in the Files section. This allows some fancier HTML and Flash in resources.
    • -
  • $CFG->forceloginforprofiles can be set to prevent guests from seeing site-level user profiles (including Google).
    • -
  • When Google access is enabled, then Google web page translations now work too.
    • -
  • Sessions are now stored privately in the Moodle data directory - this makes Moodle work better on clusters, and solves some session timeout problems when using Moodle on shared web hosts
    • -
  • User pictures can now be easily deleted from the profile editing page
    • -
  • Talking in Chat now appears in the main logs.
    • -
  • Hidden sections in courses can now be completely hidden from students (course setting)
    • -
  • Improvements to text inside graphs for some non-English languages, using Unicode fonts.
    • -
  • Improved interface for managing Scales, as well as better handling in mulitlingual sites
    • -
  • All students can now be unenrolled with one button (on the Students page)
    • -
  • Subscribers to forums can now be manually subscribed or unsubscribed in groups
    • -
  • Better handling of some European characters in filenames and usernames
    • -
  • Feedback notices for a hidden assignment aren't mailed out until it's unhidden
    • -
  • Expanded support for importing Blackboard quizzes
    • -
  • The cron script can now be run using a PHP binary from any directory
    • -
  • The HTML editor has been further improved and streamlined.
    • -
  • The default recent activity display is now calculated from the last access to that course (or two days, whichever is more recent). Previously it was from the last login to the site.
    • -
  • Confirmation emails are now in HTML and Text, to help prevent breaking of confirmation link.
    • -
  • New languages: Farsi, Latvian, Norwegian Primary School, Unicode version of Traditional Chinese.
    • -
-
-
Bug fixes
-
-
    -
  • Hundreds of small bugs were fixed in all areas, generally improving appearance and robustness.
    • -
  • As always, if you find bugs in Moodle, please report them to our Bug Tracker!
    • -
-

 

-
-
Finally, don't forget to look at some of the many optional modules under development, including the SCORM module, the Wiki module, the Hot Potatoes module and many other innovations.
-
-
-
-

New in Moodle 1.2.1 (25th March, 2004)

-
-
Various small bug fixes
-
-
    -
  • Fixed some bugs that were causing survey graphs and results not to display in some circumstances
    • -
  • Improved security in the cron script
    • -
  • Fixed WebCT quiz import to deal with missing images, shortanswers and escaped characters
    • -
  • Fixed formatting on editor dialog to insert links
    • -
  • Prevent glossary from adding links to activity names that are already links
    • -
  • Fixed some timezone calculations when user isn't present
    • -
  • Characters like :( in Javascript code within filtered HTML are no longer converted to a sad smiley
    • -
  • Improved handling of ratings for single forums when secureforms is on.
    • -
  • Multichoice question creation now defaults to a single correct answer format
    • -
  • Guests can no longer see email addresses if "show only to course participants" has been set by that user
    • -
  • Primary admin is now the lowest-numbered entry in role_assignement with moodle/legacy:admin capability, rather than the admin with the lowest userid.
    • -
  • Modified flash MP3 plugin to improve brightness of Play button on darker screens
    • -
  • Various polishing and improvements in many language packs
    • -
-
-
-
- - -

New in Moodle 1.2 (20th March, 2004)

-
Major new features -
-
    -
  • New support for groups and cohorts within courses (with many options)
    • -
  • Text filters allow arbitrary processing on all text in Moodle, including automatic linking, mathematics support, multi-language content and infinitely more possibilities
    • -
  • A fantastic new Glossary module (thanks to Williams Castillo!) with many different ways to contruct learning activities based around collecting definitions
    • -
  • A great new Lesson module (thanks to Ray Kingdon!) easily creates active content with pathways and multiple-choice questions
    • -
  • A new Label module allows arbitrary HTML in the course page
    • -
  • An improved WYSIWYG editor, faster and more cross-platform than the old one
    • -
  • Automatic backups can be scheduled by the administrator for all courses at once
    • -
-
-
Courses
-
-
    -
  • Activities can now be indented on the course outline, allowing more structure
    • -
  • A new report for Recent Activity makes it easier to see what's happened recently
    • -
  • A new logs button on every activity links to the logs page to show logs per-activity
    • -
  • Restore button now always functional
    • -
  • Improved "index" view for all modules
    • -
  • Improvements to participants display, including paging and initial searching
    • -
  • Excel downloads are more compatible with different operating systems
    • -
  • Better error reporting when adding/updating activities
    • -
  • Search box no longer auto-focuses (it was causing annoying auto-scrolling on long courses)
    • -
  • Self-unenrollment link on the course page for students
    • -
  • Change password link on the course page for students
    • -
  • Students can now be allowed to see their own activity reports (course setting)
    • -
  • Teachers can browse the course files for images when using the new editor
    • -
  • New image of empty box as destination when moving activities
    • -
  • Accesses are now recorded by course, so the participant listings make more sense
    • -
  • The activity navbar now has buttons for previous and next activities
    • -
  • File dates were incorrect on some systems - this is now fixed.
    • -
  • Old chat users are no longer shown in the recent activity
    • -
-
-
Site administration
-
-
    -
  • An important security fix preventing teachers from logging in as admins who are students in their course
    • -
  • New setting "forcelogin" can force people to log in before they can see any of the site
    • -
  • New setting "opentogoogle" allows Google and people referred by Google to get in as guest
    • -
  • New setting "timezone" allows a default timezone to be set for the whole site
    • -
  • New setting "deleteunconfirmed" specifies the time we'll wait for email accounts to be confirmed
    • -
  • New setting "allowunenroll" enables/disables students from unenrolling themselves from courses
    • -
  • New setting "fullnamedisplay" allows override for the formatting of user full names so students can only see "firstname lastname", "lastname firstname" or "firstname"
    • -
  • Individual users can have their email disabled by the teacher or admin (useful for dealing with broken mail accounts that are bouncing)
    • -
  • Upload sizes can now be controlled throughout Moodle using "maxbytes". There is a site limit (bounded by the current PHP limits), which itself is the upper bound for course limits, which is the upper bound for activity limits.
    • -
  • Moodle cookies can be customised (helps when running multiple Moodles on one site)
    • -
  • Included script for analysing database performance (admin/dbperformance.php)
    • -
  • Included standalone script to check a server for Moodle compatibility (lib/compatible.php)
    • -
  • If a file called cronextra.php exists in the dataroot then cron will run that too. This allows sites to have "special" maintenance features.
    • -
  • Course formats are now more like plugins, in separate directories
    • -
  • Users can now be uploaded from text files
    • -
  • If $CFG->disableuserimages is defined (in config.php) then user images can not be changed
    • -
  • If $CFG->admineditalways is defined then the administrator can edit ANY post at any time.
    • -
  • If $CFG->filterall is defined then even little things liks forum subjects and activity names are filtered
    • -
  • Support for restricted demo users (eg the teacher demo on Moodle.org) - usernames can be added to a list of names in config.php. eg $CFG->restrictusers = 'teacher,fred';
    • -
-
-
Themes
-
-
    -
  • Fixes for Internet Explorer can be more robust at using the style sheet
    • -
  • Miscellaneous fixes and improvements to themes - custom themes need upgrading!
    • -
-
-
Translations
-
-
    -
  • New languages: Galego and Lithuanian
    • -
  • Improved language editing interface - it allows the current language to be chosen and allows each file to be edited separately.
    • -
  • The list of country names can now be translated, as can the editor buttons, smiley names and file sizes (Mb, Gb etc)
    • -
  • Language packs can now define the default language direction (RTL or LTR)
    • -
  • Language packs can now define the order that people's names should be shown in
    • -
  • Language files are now written using slightly more efficient PHP code
    • -
  • Finally got rid of the final bogus linefeeds in the multi-line strings
    • -
  • Courses can now "force" a language on all users
    • -
-
-
Backup / Restore
-
-
    -
  • Automatic backups can be scheduled by the administrator for all courses at once
    • -
  • Logs are now fully restored
    • -
  • All needed users are now included in course backups (even if no longer enrolled)
    • -
  • Miscellaneous fixes and improvements
    • -
-
-
Text Filters and Formatting
-
-
    -
  • Warning: the new text filters can increase the load on your server, particularly when used with complex filters. Use them with caution.
    • -
  • The new glossary filter can create links to glossary entries from matching words throughout Moodle.
    • -
  • The new TeX filter can convert TeX code found anywhere in Moodle into true Mathematics notation (GIF format image). There is also an algebra filter with a simpler input format (more like calculators).
    • -
  • The new censor filter can be enabled to filter out bad words.
    • -
  • The new multilang filter allows texts to be entered in multiple languages, and only the best one will be shown to each user (depending on their language setting)
    • -
  • The <nolink> tag can be used to prevent autolinking within a passage of text.
    • -
  • More tags are now allowed, including <acronym> and all <math> tags.
    • -
  • Some areas where text wasn't properly filtered before (security risk) have now been fixed.
    • -
-
-
Developer API
-
-
    -
  • A new coding guide is available
    • -
  • A new Philosophy guide is available ;-)
    • -
  • Improvements to the template for new modules
    • -
  • Modules should now specify the minimum version of Moodle they are compatible with
    • -
  • Scripts can specify to print_header() whether the page is pure XML
    • -
  • Any module can save and retrieve user preferences that stay around between logins
    • -
-
-
Chats
-
-
    -
  • Chat sessions can now be deleted
    • -
  • Scheduled chat times now show the timezone to make it clearer
    • -
-
-
Forums
-
-
    -
  • Forum viewing preferences are remembered between logins
    • -
  • "Show parent" link on all posts for faster navigation around forums
    • -
  • Anchor tags allow individual posts to be referenced in all views
    • -
  • Improvements to cron job when manually run, as well as logging of mailer errors
    • -
  • Only print the ratings button when there are ratings to be made
    • -
  • Vastly improved email text versions of HTML forum posts
    • -
  • When replying, an outline of other replies is shown.
    • -
  • When using the HTML editor to post, other formatting options are no longer provided.
    • -
-
-
Journals
-
-
    -
  • Journal questions can now use the HTML editor
    • -
  • Some fixes to the report page when assessing journal entries
    • -
-
-
Quizzes
-
-
    -
  • Questions and categories can now be edited without needing to open a quiz
    • -
  • All questions can now use any of the Moodle editing formats
    • -
  • New import format: GIFT format (this is the new default format)
    • -
  • New import format: Course Test Manager
    • -
  • New import format: WebCT format
    • -
  • New import format: Aiken format
    • -
  • Short-Answer questions can now use wildcards for matching eg wild*rds
    • -
  • Images now work in questions from external published categories
    • -
  • Improved the overview reports to show more info and allow deletion of attempts
    • -
  • Added a new detailed quiz report for statistical anaylsis
    • -
  • All question types can now have up to 10 answers each
    • -
  • Menus in quiz editing no longer need submit buttons (just select from menu)
    • -
  • Fixed bug that occurred when re-grading SOME quizzes with random questions in them
    • -
  • Fixed bug that occurred in backups of quizzes with random questions in them
    • -
  • Many other small bugs fixed
    • -
-
-
Resources
-
-
    -
  • Teachers can browse files more directly when creating uploaded file
    • -
  • New settings to allow a default URL, a default search page and default popup settings
    • -
  • Uploaded files can appear in popups too.
    • -
  • Much better display of popups when using the navbar to go there
    • -
  • MP3 files are now streamed using a built-in Flash MP3 player
    • -
  • Video files (Media player, Quicktime) are embedded using local plugins
    • -
-
-
Workshops
-
-
    -
  • Changes to handling of peer assessments
    • -
  • New assessment phase
    • -
  • New options for the league table
    • -
-
-
Miscellaneous
-
-
    -
  • Moodle now ignores any folders that Frontpage may have added to it (_vti_cnf).
    • -
  • Improved HTML -> XHTML in many places
    • -
  • Many fixes for non-MySQL databases
    • -
  • A few hard-coded text strings around the place were made translatable
    • -
  • User profile data is now properly cleaned
    • -
  • FIxes for when Moodle is embedded within a frame (eg in Postnuke)
    • -
  • Bug fixes to Wiki mode
    • -
  • Admin can no longer edit external accounts
    • -
  • Qmail users can use "qmail" in the smtphosts field for better results
    • -
  • Multiple methods of redirecting, to work around some browser bugs
    • -
  • Small improvements to the display of grades in the gradebook
    • -
  • More student profile fields can be edited, such as department and institution, and these are also written to grade dumps in text or Excel.
    • -
  • When a student is added as a teacher, they are now automatically unenrolled from being a student
    • -
  • Upgraded ADOdb (database layer)
    • -
-
-
-
-

New in Moodle 1.1.1 (10 September, 2003):

-
-
General Fixes
-
-
    -
  • Translation improvements in many languages
    • -
  • Frame fix when switching languages in documentation
    • -
  • All short PHP tags removed ... short_tags is no longer a requirement
    • -
  • Forum search results link using anchor tag for better context
    • -
  • Removed target from "delete" link on user editing page
    • -
  • 'Search' on social format moved closer to the top to prevent browser - self-scrolling
    • -
  • Page redirection is faster and no longer causes intermediate page - to be stored in IE history
    • -
  • Course listings improved when courses are displayed, including more - information
    • -
  • Category listings show courses in full when there are under ten courses
    • -
  • Invisible courses are always shown last in My Courses
    • -
  • Course creators can now see all hidden categories and courses
    • -
  • Styles added for category and course names
    • -
  • Removed tags from question text on quiz 'simplestat' report
    • -
  • Added percentages to downloaded data from 'simplestat' report
    • -
  • Allow external deep linking using guest account ?username=guest
    • -
  • Any admin can now add/remove course creators
    • -
  • Primary admin can now update own username/password even with external authentication
    • -
  • Quizzes can now be specified as having "no grade" and no grades will be shown
    • -
  • When editing a language, missing strings files are created if possible
    • -
  • Fixed bug in weekly journal date calculations
    • -
  • Fixed bug in config.php that made error_reporting not work
    • -
  • Fixed bug when editing user name with quotes in it
    • -
  • Fixed bug in email obfuscation for email addresses with numbers in - them
    • -
  • Fixed missing PostgreSQL schema for chat module
    • -
  • Fixed several typos in PostgreSQL upgrading code
    • -
  • Fixed some uninitialised variables
    • -
  • Several bugs fixed in Workshop module
    • -
-
-
-
- - - -

New in Moodle 1.1 (28 August, 2003):

-
-
Major Changes
-
-
    -
  • A completely new backup system for backup and restore - of courses (Thanks, Eloy!)
    • -
  • A new workshop module for peer grading (Thanks, Ray!)
    • -
  • A new chat module for synchronous discussions
    • -
  • All-new course manager to handle very large numbers - of courses (tested with 3700)
    • -
  • Custom-defined grading scales that can be used throughout - a course
    • -
  • Performance improvements in many areas
    • -
-
-
General
-
-
    -
  • Clean up of the whole admin menu organisation to make it clearer
    • -
  • Categories can be nested and sorted alphabetically or manually
    • -
  • Courses and whole categories can be hidden from students
    • -
  • Course descriptions and names can be searched for keywords
    • -
  • Large categories are now completely paged
    • -
  • Improved web caching for stylesheets and images
    • -
  • "My courses" display on the home page when logged in.
    • -
  • Inclusion of non-linked page to display ALL user pictures at once - (see /userpix)
    • -
  • The "secureforms" feature now defaults to OFF.
    • -
  • Moodle now doesn't care if "magic quotes" is on or off.
    • -
  • Images in /pix were rearranged and tidied up
    • -
  • HTML email is better formatted for wider compatibility
    • -
  • Mail bounces are now sent to the admin user
    • -
  • Better cron tasks (less CPU used) and duplicate enrolments are now - cleaned
    • -
  • Improved display of logs with infinite paging and increased flexibility
    • -
  • User log graphs now work at site-level (showing ALL logs on the site)
    • -
  • People with manual accounts can now recover their password
    • -
  • Improved system for defining/printing help files for major activity - modules
    • -
  • Activity modules can now have settings
    • -
  • Email addresses are all completely obfuscated (to fool web spiders)
    • -
  • There is now an index to the help files
    • -
  • Library (Mark Kimes' add-on) is now supported if it is installed (see Moodle contrib for Library source)
    • -
-
-
Courses
-
-
    -
  • Teachers can now have their course editing privileges removed
    • -
  • Teachers can now manually enrol students if they want to
    • -
  • Teacher management is now all combined in one interface
    • -
  • Activities can be moved any distance with two clicks
    • -
  • Topics/weeks can now be moved up and down
    • -
  • Pop-up menu to quickly switch between topics/weeks when collapsed
    • -
  • When self-enrolling, students are notified and given a chance to cancel
    • -
  • Teachers and students see list of "My Courses" on course - home pages.
    • -
  • Grades can be hidden from students if not needed
    • -
-
-
Languages
-
-
    -
  • Hungarian and Greek 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 http://moodle.org/download/lang/.
    • -
  • Updates and fixes to most languages
    • -
  • Languages now have a parent language (for displaying missing strings)
    • -
  • Some fixes for locales and time display in several languages
    • -
  • es_mx is being phased out in favour of "es" (International - Spanish)
    • -
-
-
Forum
-
-
    -
  • Much improved searching, with multiple keywords, paging etc
    • -
  • Forum grading can be either off, used by everyone, or used only by teachers
    • -
  • Forum grading can use custom scales or numbers
    • -
  • A date range can be set to restrict the posts that can be graded.
    • -
  • Admin now has access to some settings via Admin -> Modules -> Forums
    • -
  • After editing a post, user is returned to post in context
    • -
  • Attached images are displayed inline
    • -
  • Email copies in plain text format now print URLs nicely
    • -
-
-
Quiz
-
-
    -
  • New question type: Embedded Answers (Cloze) - allows text passages - with embedded answers
    • -
  • New question type: Numerical - allows a range of numerical answers - to be entered
    • -
  • New question type: Description - not a real question, it allows text/graphics - to be inserted anywhere
    • -
  • Expanded quiz reporting with modular report plugins
    • -
  • New feature for repeat attempts, where each attempt builds on the - last
    • -
  • 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.
    • -
  • Some refactoring to the quiz code to make it easier to extend with - new question types
    • -
-
-
Resources
-
-
    -
  • Web links can now be in very customisable pop-up windows.
    • -
  • Admin now has access to some settings via Admin -> Modules -> - Resources
    • -
-
-
Some of the more annoying bugs recently fixed
-
-
    -
  • Moving posts now also moves attachments
    • -
  • No more warnings when looking for uploaded files in an empty course
    • -
  • Students no longer always get plain-format mail on force-subscribed - forums
    • -
  • Cookies can no longer interfere with the admin setup during installation
    • -
  • Effectively no limit to the number of activities per section
    • -
  • Several fixes when dealing with zip files, especially on Windows
    • -
  • Admins can now edit accounts created from external databases
    • -
  • Session no longer conflicts with other software
    • -
  • Excel files now work on non-Intel machines
    • -
-
-
-
- -

New in Moodle 1.0.9 (29th May, 2003) :

-
-
General
-
-
    -
  • Various optimisations and significant performance enhancements
    • -
  • Several obscure security fixes
    • -
  • Moodle is now well-behaved when enclosed within a frame
    • -
  • Richtext editor can now be used in more text-editing fields
    • -
  • New format "Plain text format", useful when posting code or HTML.
    • -
  • New format "Wiki format", allows Wiki-style tagging in most places
    • -
  • New popup allows emoticons/smilies to be inserted by clicking on images
    • -
  • Ability to specify permissions of new folders and files created on the server
    • -
  • Some fixes for servers running in Safe Mode (some file problems remain)
    • -
  • Various fixes for cleaning some external text of quotes, etc
    • -
  • Various fixes for PostgreSQL 7.3 compatibility
    • -
  • Started migration of HTML code towards XHTML Transitional
    • -
  • Countless other little fixes all over the place
    • -
-
-
Languages
-
-
    -
  • 10 new language packs! Argentinian Spanish, Czech, Portuguese, Slovakian, Romanian, Danish, Russian, Polish, Chinese Traditional and French Canadian.
    • -
  • Fixes and upgrades to almost all language packs
    • -
  • 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
    • -
  • Language menu can be restricted to a subset of languages and even removed. -
  • Truetype fonts are now part of the language packs
    • -
  • ALL dates/times can now be reformatted as part of the language pack
    • -
  • A small but annoying bug was fixed with the web-based language editor on Windows servers that caused language files to grow
    • -
-
-
Developers
-
-
    Global debug variable gives more feedback about uninitialised variables and the like -
  • Various fixes to tidy up and further standardise some of the PHP code
    • -
  • Various fixes for robustness (ensuring variables are always initialised)
    • -
-
-
Admin
-
-
    -
  • Some changed options and code in config-dist.php (if upgrading, compare with your current config.php or rebuild your config.php from scratch)
    • -
  • Many changes to themes - authors of custom themes should read theme/UPGRADE.txt
    • -
  • New moodle.org registration function for security notifications etc
    • -
  • Admin directory can be moved from /admin to something else (see config-dist.php)
    • -
  • User listing is now paged, and can now be searched for strings
    • -
  • Module management: activity modules can now be individually disabled or deleted completely
    • -
  • Improvements to the language editing page
    • -
  • Better checking of PHP environment during installation, with warnings
    • -
  • Cleaner installation procedure.
    • -
-
-
User management
-
-
    -
  • New role: Course creator - just like teacher but can also create new courses
    • -
  • New authentication plug-in named "manual", prevents users from creating their own accounts
    • -
  • "Forgot Password" routine now uses an email confirmation before resetting password
    • -
-
-
Courses
-
-
    -
  • Activities on the course page now have a little button to hide/show that activity to students
    • -
  • Whole topics/weeks can also now be hidden or shown
    • -
  • The list of participants now has some paging, to cope with very large classes
    • -
  • 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.
    • -
-
-
Assignments
-
-
    -
  • Assignment submissions can be sorted
    • -
  • Assignment notification mail isn't sent to unenrolled students
    • -
-
-
Forums
-
-
    -
  • Display of forum discussions list is greatly improved
    • -
  • Whole discussions can be moved to any other forum with a single click
    • -
  • Date/time of posts is now "last modified", not "created"
    • -
  • Blank subject-lines or messages are now prevented
    • -
  • More intelligent parsing and display of text in posts
    • -
  • Force Subscribe now works on the "Site News" forum (mails all active students/teachers)
    • -
  • Better handling of mailouts to prevent the possibility of double copies - that sometimes happened with very large classes
    • -
-
-
Workshop Assignment module (not included: available soon as a separate download)
-
-
    -
  • A very interesting new module contributed by Ray Kingdon,
    • -
  • 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.
    • -
-
-
Quizzes
-
-
    -
  • New question type, Random Question (selects from all questions in the same category)
    • -
  • New question type, Matching Question (student must match answers to questions)
    • -
  • New question type, Random Matching Short-Answers (randomly creates Matching Questions - from the available Short Answer questions in the same category)
    • -
  • Quiz question import from text files (modular design allows expansion to new formats - a beta Blackboard module is included)
    • -
  • 'Create multiple questions' wizard to quickly create a random quiz
    • -
  • Quiz questions may be randomly shuffled
    • -
  • Quiz answers (multiple choice, etc) may be randomly shuffled
    • -
  • Fixed off-by-one error when "Save Grades" button wasn't used.
    • -
  • Regrading works properly if the quiz has been changed
    • -
  • Editing a question after it's already been used in a quiz no longer affects quiz results
    • -
  • Multiple choice answers are labelled a,b,c not 1,2,3
    • -
-
-
Resources
-
-
    -
  • Better performance when editing large text or HTML resources
    • -
  • Plain images are now display centered within a proper web page (not raw).
    • -
  • Wiki format added as a new option for Resource pages
    • -
-
-
Custom Themes
-
-
    -
  • 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 - theme/UPGRADE.txt - TO SEE THE CHANGES YOU WILL HAVE TO MAKE TO OLDER THEMES.
    • -
  • 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.
    • -
-
-
-
- - -

Older releases can be seen in the Moodle.org announcement forum. - - -

 

-

Moodle Documentation

-

Version: $Id$

diff --git a/lang/en_utf8/docs/teacher.html b/lang/en_utf8/docs/teacher.html deleted file mode 100644 index 29572e31a7f..00000000000 --- a/lang/en_utf8/docs/teacher.html +++ /dev/null @@ -1,235 +0,0 @@ - - - -Moodle Docs: Teachers Manual - - - - - -

Teacher Manual

-

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.

-

Sections in this document:

-
    -
  1. Getting started
    2. -
  2. Course settings
    3. -
  3. Uploading files
    4. -
  4. Setting up activities
    5. -
  5. Running the course
    6. -
  6. Further information
    7. -
-

Getting started

-
-

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.

-

Here are three general tips that will help you get started.

-
    -
  1. Don't be afraid to experiment: -
    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. -
    -
  2. Notice and use these little icons: -
    -

      - the edit icon - lets you edit whatever it is next to.

    -

    - the help - icon will provide you with a popup help window

    -

      - the open-eye - icon will let you hide something from students

    -

      - the closed-eye - icon will make a hidden item available

    -
    -
    3. -
  3. Use the navigation bar at the top of each page -
    this - should help remind you where you are and prevent getting lost. -
    -
    4. -
-

 

-
-

Course settings

-
-

The first thing you should do is look under the "Administration" - on your course home page and click on "Settings..." - (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).

-

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 course - format.

-

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 martin@moodle.org!)

-

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):

-

Weekly format:

-

-

 

-

Topics format:

-

-

 

-

Social format:

-

-

 

-

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.

-

See the help buttons on the Course Settings page for more details.

-

 

-
-

Uploading files

-
-

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.

-

All of this is achieved through the Files link in your Administration - menu. The Files section looks like this:

-

-

 

-

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).

-

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.

-

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 zip program 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).

-

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.

-

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.

-

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).

-

 

-
-

Setting up activities

-
-

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.

-

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.

-

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:

-
-
Assignment
-
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 you 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. -
-
-
Choice
-
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. -
-
-
Forum
-
This module is by far the most important - it is here that discussion - takes place. When you add a new forum, you will be 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. -
-
-
Resource
-
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. -
-
-
Quiz
-
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. -
-
-
Survey
-
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).
-
-
-

After adding your activities you can move them up and down in your course - layout by clicking on the little arrow icons ( - ) next to each one. You - can also delete them using the cross icon , - and re-edit them using the edit icon .

-

 

-
-

Running the course

-
-

There are some big plans to extend this document into a more comprehensive - tutorial. Until then here are a few ideas:

-
    -
  1. Subscribe yourself to all the forums so you keep in touch with your class - activity.
    2. -
  2. 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.
    3. -
  3. Keep notes to yourself in the private "Teacher's Forum" - (under Administration). This is especially useful when team teaching.
    4. -
  4. Use the "Logs" 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.
    5. -
  5. Use the "Activity Reports" (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.
    6. -
  6. 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.
    7. -
-

 

-
-

Further information

-
-

If you have any particular problems with your site, you should contact your - local site administrator.

-

If you have some great ideas for improvements to Moodle, or even some good - stories, come over to moodle.org - and join us in the course called "Using - Moodle". We'd love to hear from you, and you can help Moodle improve.

-

If you want to contribute to coding new modules, or writing documentation, - or papers, contact me: Martin - Dougiamas or browse the "bug tracker" site for Moodle, at moodle.org/bugs

-

Finally, remember to use the help icons - here is an index of all the help files in Moodle.

-

Thanks for using Moodle - and good luck with your teaching!

-
-

 

-
-

Moodle Documentation

-

Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01 - martin Exp $

- - diff --git a/lang/en_utf8/docs/translation.html b/lang/en_utf8/docs/translation.html deleted file mode 100644 index f3ca2290669..00000000000 --- a/lang/en_utf8/docs/translation.html +++ /dev/null @@ -1,249 +0,0 @@ - - - - Moodle translation guide - - - - - - -

Moodle Translation Guide

- -

Translating Moodle is not that difficult, but a few things are good to know before you start.

- -

 

- -

Structure of a Moodle language pack

- -

All Moodle language packs are located in -the lang directory, with each language in a unique directory named the -same as the language short name (en, fr, nl, es ...).

- - -

All the main files are in this -folder, with .php extensions (eg moodle.php, resource.php etc).  -These files contains short phrases, often called "strings". -

- - -

There might also be some folders containing .html web pages: -

- - - - - - -

 

- - - -

Creating a completely new language pack

- - - - -

If your language is not yet supported by -Moodle, or if you just want to make some customisations to your own -site's interface, you may want to start a new translation.

- - - -

All you need to do is create a new folder -in the lang directory using the 2-letter code for your language. You -can find these standard codes in lib/languages.php. If you are making a -local variation of another language use the code of that language with -an underscore and a meaningful two letter extension (e.g. pt for Portuguese and pt_br for Brasilian variation of the Portuguese language pack).  If you are making a Unicode version add _utf8 at the end (eg sr_utf8).
-

- - - -

Next, create in your new language folder the file "moodle.php", containing the folowing lines:

- -<?PHP
-$string['thischarset'] = 'iso-8859-1';
-$string['thisdirection'] = 'ltr';
-$string['thislanguage'] = 'new language pack';
-?> - -

-or copy the moodle.php from another -language into your new directory.  The one from the "en" folder is -usually best but it doesn't really matter as you are going to rewrite -it anyway. Creating moodle.php yourself has the advantage of starting with a completely clean and empty language pack.
-

- - - - -

You are now ready to start inserting new strings by editing your language... see below for details on this.

- - - -

For a new language pack, the very first -thing you need to edit is the string named "thischarset" in moodle.php. -It must contain a valid web character set for your language. After you -change that string, save the moodle.php file, then reload the page. You can then continue with the rest of the strings.

- - - -

 

- - - -

Editing an existing language pack

- - - - -

Making small customisations
-

- - - -

If you just want to change a few things in the interface to suit your own site better, don't start editing one of the standard language packs.  If you do then your changes will be overwritten next time you upgrade to a new Moodle.
-

-

Instead, use the instructions above for -making a brand new language pack, and set the parent language (in -moodle.php) to be the language that is most similar to yours.  For -example, a good name for a local english version would be "en_local", and the parent language would be "en" or "en_us".

-

Note that for everyone on your site to -see this new pack you have to select it as the site language and -restrict the available languages on Admin >> Configuration >> Variables.
-
-

- - - - -

Translating the Moodle interface language files (the "string" files)
-

- - - - - -
    -
  1. Log on to your Moodle server as an administrator.
    2. -
  2. Go to Administration >> Configuration >> Language, which is the language administration page.
    3. -
  3. On this page you can choose your language from the menu, then choose "Compare and Edit Language".
    4. -
  4. You should see forms you can edit for each file. If you do not, -then you may have to make sure that the files are writeable - you may -have to change file permissions.
    5. -
  5. The forms consist of three columns, the first is the name of -each string, the second is that string in English, and the last is -translation in the current language.
    6. -
  6. Edit missing strings in each files (highlighted in colour), -remembering to hit the "Save changes" button at the end of each form.
    7. -
  7. It's OK to leave strings empty - Moodle will simply use the -parent language for that string instead. You can define the parent -language in moodle.php, otherwise English is always used by default.
    8. -
  8. A quick way to see all the missing strings is by using the button to "Check for missing strings". Leave the untranslated strings completely empty or this handy tool won't work.
    -
    -
    9. - - - - - - - -
- - -

Translating the help and documentation files

- - - -

There's no built-in editor in Moodle yet to translate -the help files, but it's really not that difficult. It is important to -use the en language pack as a reference language. Copy a help file from -the en language pack and paste it on the same location in your own -language pack. Then use a plain text editor to translate the file, -making sure not to modify any code in the file (there usually is no -code, just HTML-tags). (DON'T USE A WORDPROCESSOR to write the -help-files because these programs add too much rubbish to the files). -
Don't leave untranslated help files in your language pack.

- -

Take care to write the helpfiles XHTML-compliant. This means in short:

- -

None of the files in the help folder need a doc type, html, body, head opening and closing tags - these files are included with help.php. The script will take care of welforming the pages. This means also there is not much room for HTML creativity! Please stick to the English example.

-

The files in the docs folder must be completely XHTML compliant, including doc type, header etc.

- - -

Clicking on "Check for missing strings" -in the language administration screen will also show you what files you -are missing. If you have missing files then Moodle will use the parent -language instead, so don't leave copies of untranslated help files in your language pack or this handy tool won't work.

- - -

 

- - -

Submitting your language pack to the Moodle project

- - -

Sharing your translation with Moodle will -ensure that you help other people who speak your language.   -Your interface language will be available in future versions of Moodle.
-

- - -

Simply archive your whole new language directory as a zip file and email it to translation@moodle.org.
-

-

We will get back to you with further details.
-

- - -

Checklist you can use before committing::

- - - -

Maintenance of a standard language pack
-

- - - -

If you are committed to maintaining a language in Moodle, it's best to use Moodle CVS so that you have an up-to-date version of Moodle, and can easily "check in" your changes directly into the Moodle project. Contact translation@moodle.org if you need help setting this up.
-

- -

You must also subscribe to the Languages Forum for news and discussion about issues that affect translations.
-

- -

Finally, to keep in touch with changes in the project on a day-to-day basis it is a very good idea to subscribe to the CVS mailing list.  This helps to keep your -translation as close to the English text as possible.
-

-


-

- -

Moodle Documentation

-

Version: $Id$

- - diff --git a/lang/en_utf8/docs/upgrade.html b/lang/en_utf8/docs/upgrade.html deleted file mode 100644 index 4b3376a8610..00000000000 --- a/lang/en_utf8/docs/upgrade.html +++ /dev/null @@ -1,117 +0,0 @@ - - - - Moodle Docs: Upgrading - - - - - -

Upgrading Moodle

- -
-

Moodle is designed to upgrade cleanly from any earlier version to any later - version.

-

When upgrading a Moodle installation you should follow these steps:

-

1. Backup important data

-
-

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.

-

There are three areas that need backing up:

-
-

1. The Moodle software directory itself

-
-

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
-

-
-

2. Your data directory.

-
-

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.
-

-
-

3. Your database

-
-

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":

-
-

mysqldump moodle > moodle-backup-2002-10-26.sql

-
-

You can also use the "Export" feature in Moodle's optional - "Database" web interface to do the same thing on all platforms.

-

 

-
-
-
-

2. Install the new Moodle software

-
-

Using a downloaded archive

-
-

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.

-
-

mv moodle moodle.backup
- tar xvzf moodle-1.1.tgz

-
-

Next, copy across your config.php and any other plugins such as custom - themes:

-
-

cp moodle.backup/config.php moodle
- cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme

-
-
-

Using CVS

-
-

If you are using CVS, just go into the Moodle root directory and update - to the new files:

-
-

cvs update -dP

-
-

Make sure you use the "d" parameter to create new directories - if necessary, and the "P" parameter to prune empty directories.

-

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.

-
-

 

-
-

3. Finishing the upgrade

-
-

The last step is to trigger the upgrade processes within Moodle.

-

To do this just visit the admin page of your - installation.

-
-

http://example.com/moodle/admin

-
-

It doesn't matter if you are logged in as admin or not.

-

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.

-
-

 

-

Assuming all goes well (no error messages) then you can start using your new - version of Moodle and enjoy the new features!

-

If you have trouble with the upgrade, visit moodle.org - and post on the Installation - Support Forum in the Using Moodle course.

-
-

 

-

 

-

Moodle Documentation

-

Version: $Id$

- - -