Moodle Docs: Developers Manual

From c2d11417922ffde270d8f161764183b91403768d Mon Sep 17 00:00:00 2001 From: moodler Date: Thu, 29 May 2003 14:13:18 +0000 Subject: [PATCH] Some improvements - still working on these files --- lang/en/docs/developer.html | 487 ++++++++++++++++++----------------- lang/en/docs/features.html | 34 ++- lang/en/docs/files.php | 1 + lang/en/docs/install.html | 335 ++++++++++++------------ lang/en/docs/installamp.html | 141 ++++++++++ lang/en/docs/teacher.html | 106 ++++---- lang/en/docs/upgrade.html | 45 ++-- 7 files changed, 683 insertions(+), 466 deletions(-) create mode 100755 lang/en/docs/installamp.html diff --git a/lang/en/docs/developer.html b/lang/en/docs/developer.html index d7e0738088..5d8efea4d3 100644 --- a/lang/en/docs/developer.html +++ b/lang/en/docs/developer.html @@ -2,11 +2,24 @@ 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:

Moodle architecture

1. Moodle architecture

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

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

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

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

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

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

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 seven default modules: assignment, choice, forum, journal, quiz, - resource, and survey. Each module is in a separate subdirectory and consists - of the following mandatory elements (plus extra scripts unique to each module):
-
-
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: defines the theme colours used throughout - the site
-
styles.php: the style sheet, containing CSS definitions - for standard HTML elements as well as many Moodle elements.
-
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.
-
-
To create your own themes for current versions of Moodle:
+
1. Moodle architecture
+
+
From a system administrator's perspective, Moodle has been designed according + to the following criteria:

-
Copy one of the existing theme folders to one with a new name. I recommend - starting with one of the standard themes. -
Edit config.php and insert your own colours. -
Edit styles.php and change your CSS styles. -
Edit header.html and footer.html to add new logos, or change the layout. -
-
Note that all these steps are optional - you can make a radically different - look to your site simply by editing the colours in config.php
-
Note also that Moodle upgrades may break themes slightly, so check the - release notes carefully if you are using a custom theme.
-
In particular, Moodle 2.0 will have a completely new display system, probably based on - XSL transformations of XML output from Moodle. It is likely that the - themes for this will be a completely different format, but the advantage will - be a much higher possible degree of customisation (including moving elements - around the page).
-
More discussion about this 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
-
journal.php - strings for journal module
-
quiz.php - strings for quiz module
-
resource.php - strings for resource module
-
survey.php - strings for survey module
-
.... plus other modules if any.
+
Moodle should run on the widest variety of platforms

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

- eg $strdueby = get_string("assignmentdueby", "assignment", - userdate($date));
+
+
Moodle should be easy to install, learn and modify

- 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. If you are - familiar with another database (especially open source databases) and are - willing to help port the existing schema, please get in contact with me (Martin - Dougiamas).
-
-

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

-
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.com/
+
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 seven default modules: assignment, choice, forum, journal, quiz, + resource, and survey. Each module is in a separate subdirectory and consists + of the following mandatory elements (plus extra scripts unique to each module):
+
+
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: defines the theme colours used throughout + the site
+
styles.php: the style sheet, containing CSS definitions + for standard HTML elements as well as many Moodle elements.
+
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.
+
+
To create your own themes for current versions of Moodle:
+
+
Copy one of the existing theme folders to one with a new name. I recommend + starting with one of the standard themes.
+
Edit config.php and insert your own colours.
+
Edit styles.php and change your CSS styles.
+
Edit header.html and footer.html to add new logos, or change the layout. +
+
+
Note that all these steps are optional - you can make a radically different + look to your site simply by editing the colours in config.php
+
Note also that Moodle upgrades may break themes slightly, so check + the release notes carefully if you are using a custom theme.
+
In particular, Moodle 2.0 will have a completely new display system, probably + based on XSL transformations of XML output from Moodle. It is likely that + the themes for this will be a completely different format, but the advantage + will be a much higher possible degree of customisation (including moving + elements around the page).
+
More discussion about this 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
+
journal.php - strings for journal 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.1 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!

-

-
Participating in the bug tracker
-
-
Finally, I would like to invite you to register on the "bug tracker" - at bugs.moodle.org 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!
diff --git a/lang/en/docs/features.html b/lang/en/docs/features.html index 1e2f5e1996..92266c66c3 100644 --- a/lang/en/docs/features.html +++ b/lang/en/docs/features.html @@ -4,13 +4,25 @@ Moodle Docs: Background +
Features

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

Promotes a social constructionist pedagogy (collaboration, activities, critical reflection, etc)
@@ -27,7 +39,7 @@
Most text entry areas (resources, forum postings, journal entries etc) can be edited using an embedded WYSIWYG HTML editor

-
Site management
+
Site management

Site is managed by an admin user, defined during setup

Plug-in "themes" allow the admin to customise the site colours, fonts, layout @@ -40,7 +52,7 @@
The code is clearly-written PHP under a GPL license - easy to modify to suit your needs

-
User management
+
User management

Goals are to reduce admin involvement to a minimum, while retaining high security
@@ -70,7 +82,7 @@
Every user can choose the language used for the Moodle interface (English, French, German, Spanish, Portuguese etc)

-
Course management
+
Course management

Teacher has full control over all settings for a course

Choice of course formats such as by week, by topic or a discussion-focussed @@ -90,7 +102,7 @@
Mail integration - copies of forum posts, teacher feedback etc can be mailed in HTML or plain text.

-Assignment Module +
Assignment Module

Assignments can be specified with a due date and a maximum grade.

Students can upload their assignments (any file format) to the server - @@ -104,14 +116,14 @@
The teacher can choose to allow resubmission of assignments after grading (for regrading)

-
Choice Module
+
Choice Module

Like a poll. Can either be used to vote on something, or to get feedback from every student (eg research consent)

Teacher sees intuitive table view of who chose what

Students can optionally be allowed to see an up-to-date graph of results

-
Forum Module
+
Forum Module

Different types of forums are available, such as teacher-only, course news, open-to-all, and one-thread-per-user.
@@ -123,7 +135,7 @@ forum)
Discussion threads can be easily moved between forums by the teacher

-Journal Module +
Journal Module

Journals are private between student and teacher.

Each journal entry can be directed by an open question.
@@ -132,7 +144,7 @@
Teacher feedback is appended to the journal entry page, and notification is mailed out.

-
Quiz Module
+
Quiz Module

Teachers can define a database of questions for re-use in different quizzes

Questions can be stored in categories for easy access, and these categories @@ -152,7 +164,7 @@
Matching questions

Random questions

-
Resource Module
+
Resource Module

Supports display of any electronic content, Word, Powerpoint, Flash, Video, Sounds etc
@@ -162,7 +174,7 @@ the course interface.
External web applications can be linked in with data passed to them

-Survey Module +
Survey Module

Built-in surveys (COLLES, ATTLS) have been proven as instruments for analysing online classes
Online survey reports always available, including many graphs. Data is downloadable as an Excel spreadsheet or CSV text file.
Survey interface prevents partly-finished surveys.
Feedback is provided to the student of their results compared to the class averages

diff --git a/lang/en/docs/files.php b/lang/en/docs/files.php index 037b381102..cfd2005bf8 100644 --- a/lang/en/docs/files.php +++ b/lang/en/docs/files.php @@ -7,6 +7,7 @@ $string['features.html'] = "Features"; $string['release.html'] = "Release Notes"; $string['install.html'] = "Installation"; $string['faq.html'] = "Installation FAQ"; +$string['installamp.html'] = "Apache, MySQL, PHP"; $string['upgrade.html'] = "Upgrading"; $string['teacher.html'] = "Teacher Manual"; $string['developer.html'] = "Developer Manual"; diff --git a/lang/en/docs/install.html b/lang/en/docs/install.html index 116960a384..7110939daa 100644 --- a/lang/en/docs/install.html +++ b/lang/en/docs/install.html @@ -1,83 +1,95 @@ - - Moodle Docs: Installation - - - + + Moodle Docs: Installation + + + + - -
Installing Moodle
-
This guide explains how to install Moodle for the first time. It goes into some detail + +
Installing Moodle
+
This guide explains how to install Moodle for the first time. It goes into some detail about some of the steps, in order to cover the wide variety of small differences between web server setups, so this document may look long and complicated. Don't be put off by this - - I usually set Moodle up in a few minutes!
-
Take your time and work through this document carefully - it will save you time later on.
-
Sections in this document:
-
-
Requirements
-
Download
-
Site structure
-
Create a data directory
-
Create a database
-
Check web server settings
-
Edit config.php
-
Go to the admin page
-
Set up cron
-
Create a new course
-
-
1. Requirements
-
-
Moodle is primarily developed in Linux using PHP, Apache and MySQL, and regularly - tested with PostgreSQL and in Windows XP and Mac OS X environments.
-
All you should need are:
+ - I usually set Moodle up in a few minutes!
+
Take your time and work through this document carefully - it will save you time later on.
+
Sections in this document:
+
+
Requirements
+
Download
+
Site structure
+
Create a data directory
+
Create a database
+
Check web server settings
+
Edit config.php
+
Go to the admin page
+
Set up cron
+
Create a new course
+
+
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:

-
a working installation of PHP (version - 4.1.0 or later), with the following features enabled (most PHP installations - these days will have all of these): +
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.
+
PHP scripting language (version 4.1.0 + or later), with the following settings:
-
GD library with support for JPG and PNG formats
-
Sessions support
-
File uploading allowed
-
-
-
a working database server: MySQL or PostgreSQL are recommended. (MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 or ODBC are also theoretically supported but will require you to manually set up the database tables).
+
GD library turned ON, with + support for JPG and PNG formats
+
Sessions support turned ON
+
File uploading turned ON
+
Safe Mode must be turned OFF (see the forums on moodle.org for problems + caused by Safe Mode)
+ + +
a working database server: MySQL or + PostgreSQL are completely supported + and recommended for use with Moodle 1.0.9. All other databases will be supported + fully in Moodle 1.1.

-
On a Windows platform, the quickest way to satisfy these requirements is - to download FoxServ, - or EasyPHP which will install Apache, - PHP, and MySQL for you. 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_gd.dll'. You may also have to fix the directory for - session.save_path - instead of the default "/tmp" use a Windows directory - like "c:/temp".
- -
On Mac OS X I highly recommend the fink - project as a way to download easily-maintainable packages for all of this. If you are less - confident with command-line stuff then Marc Liyanage's PHP Apache Module is the easiest way to get PHP up and running on a new Mac OS X server.
- -
If you're on Linux or another Unix then I'll assume you can figure all this out for yourself! ;-)
- -
-

-
2. Download
+
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

There are two ways to get Moodle, as a compressed package and via CVS. These - are explained in detail on the download page on http://moodle.org/
+ 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, + 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.
+ directory, in which case the site will be simply http://yourwebserver.com.

-

-
3. Site structure
-
+

+
3. Site structure
+

Here is a quick summary of the contents of the Moodle folder, to help get you oriented:

-
config.php - the only file you need to edit to get started
- version.php - defines the current version of Moodle code
+
config.php - the ONLY file you need to edit to get started
+ version.php - defines the current version of Moodle code
index.php - the front page of the site

admin/ - code to administrate the whole server
@@ -95,8 +107,8 @@

-
-
4. Create a data directory
+
+
4. Create a data directory
Moodle will also need some space on your hard disk to store uploaded files, such as course documents and user pictures.
@@ -106,7 +118,7 @@ is to simply locate it OUTSIDE the web directory, otherwise protect it by creating a file in the data directory called .htaccess, containing this line:
-
deny from all
+
deny from all
To make sure that Moodle can save uploaded files in this directory, check that @@ -121,8 +133,8 @@ trouble setting this up securely.
-

-
5. Create a database
+

+
5. Create 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 @@ -132,28 +144,28 @@ just one database.

Example 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
-
+
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
-
+
(For MySQL I highly recommend the use of phpMyAdmin - to manage your databases).
+ to manage your databases - you can do all this via a web interface).

As of version 1.0.8, Moodle now supports table prefixes, and so can safely share a database with tables from other applications.
-

-
6. Check your web server settings
+

+
6. Check your 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).
@@ -174,7 +186,7 @@

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. + 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):
@@ -189,13 +201,12 @@ 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 you can OVERRIDE all of the default settings. - -
To do this, you need to create a file called .htaccess in Moodle's + have Moodle on a server with other applications that require different settings, + then don't worry, you can still OVERRIDE all of the default settings. +
To do this, you need to create a file called .htaccess in Moodle's main directory that contains definitions for these settings. This only works on Apache servers and only when Overrides have been allowed. -
+      DirectoryIndex index.php index.html index.htm
 
 <IfDefine APACHE2>
@@ -207,13 +218,13 @@ php_flag magic_quotes_runtime 0
 php_flag file_uploads 1
 php_flag short_open_tag 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: -
+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 @@ -224,33 +235,36 @@ php_value post_max_size 2M
-
7. Edit config.php
+
7. Edit config.php

Now you can edit the configuration file, config.php, using a text editor. This file is used by all other files in Moodle.
-
To start with, make a copy of config-dist.php and call it config.php. We - do this so that your config.php won't be overwritten in case you upgrade Moodle - later on.
-
Edit config.php to specify the database details that you just defined (including - a table prefix - notice this is REQUIRED for PostgreSQL), as - well as the site address, file system directory and data directory. - The config file has detailed directions.
-
For the rest of this installation document we will assume your site is at: +
To start with, make a copy of config-dist.php and name it + config.php. We do this so that your config.php won't be overwritten in case + you upgrade Moodle later on.
+
Edit config.php to specify the database details that you + just defined (including a table prefix - notice that this is REQUIRED for + PostgreSQL), as well as the site address, file system directory and data directory. + The config file itself has detailed directions and examples.
+
Once you have done this the rest of the installation is via a web interface. + For the rest of this installation document we will assume your site is at: http://example.com/moodle

-

-
8. Go to the admin page
+

+
8. Go to the admin page
The admin page should now be working at: http://example.com/moodle/admin. If you try and access the front page of your site you'll be taken there automatically anyway. The first time you access this admin page, you will be presented with - a GPL agreement with which you need to agree before you can continue with the setup.
-
(Moodle will also try to set some cookies in your browser. If you have - your browser set up to let you choose to accept cookies, then you must - accept the Moodle cookies, or Moodle won't work properly.) -
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:
+ a GPL "shrinkwrap" agreement with which you must agree before you + can continue with the setup.
+
(Moodle will also try to set some cookies in your browser. If you have your + browser set up to let you choose to accept cookies, then you must accept + the Moodle cookies, or Moodle won't work properly.) +
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 @@ -260,42 +274,35 @@ php_value post_max_size 2M 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.
+
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 often have safe mode turned - on). You can check PHP variables by creating a little file containing <? - phpinfo() ?> and looking at it through a browser. Check all these and try - this page again.
+ in a restricted "Safe Mode" (commercial web hosts sometimes have safe mode + turned on). You can check PHP variables by creating a little file containing + <? phpinfo() ?> and looking at it through a browser. Check all these and + try this page again.

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

Next you will see a similar page that sets up all the tables required by - each Moodle module. As before, they should all be green.
- + each Moodle module. As before, they should all be green.

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. Scroll down - to the bottom and click "Save changes".
- -
If (and only if) you find yourself getting stuck on this page or the next - page, unable to continue, then your server probably has what I call the - "buggy referrer" problem. This is easy to fix: just edit - your config.php and set the variable buggy_referrer to true, then - try the page again.
- -
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 go back and change these later) and then press +
You should now see a form where you can define more configuration variables + for your installation, such as the default language, SMTP hosts and so on. + Don't worry too much about getting everything right just now - you can always + come back and edit these later on using the admin interface. Scroll down to + the bottom and click "Save changes".
+
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.
+
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 @@ -305,7 +312,7 @@ php_value post_max_size 2M
-
+

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.
@@ -314,9 +321,14 @@ php_value post_max_size 2M

-
Once successful, you will be returned to the main admin page, which contain - a number of links arranged in a menu (these items also appear on the home - page when you are logged in as the admin user). All your further administration +
(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 home page of your site. Note the + administration links that appear down the left hand side of the page (these + items also appear on a separate Admin page) - these items are only visible + to you because you are logged in as the admin user. All your further administration of Moodle can now be done using this menu, such as:

creating and deleting courses
@@ -325,33 +337,37 @@ php_value post_max_size 2M
changing site-wide settings like themes etc

-

-
9. Set up cron
+

+
9. Set up cron
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 minutes). This provides + 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.
-
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 cron, then you can might choose to run cron on another - server or on your home computer. All that matters is that the cron.php file is - called every five minutes or so.
+
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 cron, then you can might choose to run + cron on another server or on your home computer. All that matters is that + the cron.php file is called regularly.
+
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
+
http://example.com/moodle/admin/cron.php
Now, you need to set up some of way of running the script automatically and regularly.
-
Running the script from a command line
+
Running the script from a command line

You can call the page from the command line just as you did in the example above. For example, you can use a Unix utility like 'wget':
-
wget -q -O /dev/null http://example.com/moodle/admin/cron.php
+
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:
@@ -363,25 +379,28 @@ php_value post_max_size 2M 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
+    /opt/bin/php /web/moodle/admin/cron.php
 
 
 (Windows) C:\apache\php\php.exe C:\apache\htdocs\moodle\admin\cron.php
 
-
+
Automatically running the script every 5 minutes
-
On Unix systems: Use cron. Edit your cron settings from the commandline +
On Unix systems: Use cron. Edit your cron settings from the commandline using "crontab -e" and add a line like:
-
*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php
+
*/5 * * * * wget -q -O /dev/null http://example.com/moodle/admin/cron.php
-
On Windows systems: The simplest way is to use my package moodle-cron-for-windows.zip - which makes this whole thing very easy. You can also explore using the built-in +
On Windows systems: The simplest way is to use this little package moodle-cron-for-windows.zip + which makes this whole thing very easy. You can also explore using the built-in Windows feature for "Scheduled Tasks".
-
+
On web hosts: Your web-based control panel may have a web page that allows + you to set up this cron process. Ask your administrator for details on how + it works.
+
-
10. Create a new course
+
10. Create a new course

Now that Moodle is running properly, you can create a course.

Select "Create a new course" from the Admin page (or the admin @@ -396,11 +415,11 @@ php_value post_max_size 2M 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 +
See the "Teacher Manual" for more details on course-building.

-

-
Moodle Documentation
-
Version: $Id$
+

+
Moodle Documentation
+
Version: $Id$
- + diff --git a/lang/en/docs/installamp.html b/lang/en/docs/installamp.html new file mode 100755 index 0000000000..a0084bf649 --- /dev/null +++ b/lang/en/docs/installamp.html @@ -0,0 +1,141 @@ + + 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.
+

+
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.
+
More details might be added here later ...
+

+
+
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.
+
More details might be added here later ...
+
+

+
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:
+
+
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.
+
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.
+
Download EasyPHP from here: http://www.easyphp.org/telechargements/dn.php?F=easyphp1-6.php3 + (approx 10 Mb)
+
Run the downloaded file: easyphp1-6_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.
+
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.
+
If all went well - congratulations! Apache, PHP and MySQL are all installed + and running! You should see a black E in your toolbar tray. You can right + click on it to get a menu which will let you control the running programs, + but you won't be needing that for now.
+
The next thing you need to do is to set up a database for Moodle to use. + Using a browser, go to http://localhost/mysql/ + (note the final slash).
+
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.
+
Create a new database by typing "moodle" into the field and + hitting the "Create" button. That was easy!
+
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.
+
You're ready to install Moodle! Download the latest release of Moodle + from http://moodle.org/download, + then unzip the archive.
+
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/.
+
Make a new empty folder somewhere else for Moodle to store uploaded files + in, eg: C:\moodledata
+
Go into your Moodle folder. Make a copy of config-dist.php, and call + it config.php
+
Edit config.php using a text editor (Notepad will do, just be careful + that it doesn't add unwanted spaces at the end).
+
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_';
+
+
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';
+
+
Save config.php - you can ignore the other settings if there are any.
+
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.
+
Lastly, you need to set up some sort of cron. See the Installation + guide for more details on this.
+
+
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_gd.dll'. +
+
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/docs/teacher.html b/lang/en/docs/teacher.html index 8952441960..a219dcfc24 100644 --- a/lang/en/docs/teacher.html +++ b/lang/en/docs/teacher.html @@ -1,26 +1,38 @@ - - Moodle Docs: Teachers Manual - - - + + Moodle Docs: Teachers Manual + + + + - + -
Teacher Manual
-
This page is a quick guide to creating online courses with Moodle. It outlines +
Teacher Manual
+
This page is a 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.
+ you'll need to make.
-
Sections in this document:
-
-
Getting started
-
Course settings
-
Uploading files
-
Setting up activities
-
Running the course
-
Further information
-
-
Getting started
+
Sections in this document:
+
+
Getting started
+
Course settings
+
Uploading files
+
Setting up activities
+
Running the course
+
Further information
+
+
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 @@ -46,7 +58,7 @@

-
Course settings
+
Course settings

The first thing you should do is look under the "Administration" on your course home page and click on "Settings..." @@ -79,9 +91,9 @@ 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
+
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. @@ -111,9 +123,9 @@
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
+
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 @@ -132,23 +144,23 @@ date they upload their file is recorded. Afterwards, you will have a single page on which ou can view each file (and how late or early it is), and then record a grade and a comment. Half an hour after you grade any particular - student, Moodle will automatically email that student a notification.
-
+ 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, yu will presented with a choice of different types - a simple single-topic discussion, a free-for-all general forum, or a one-discussion-thread-per-user.
-
-
+
+

Journal

Each journal activity is an entry in the whole course journal. For each one you can specify an open-ended question that guides what students write, @@ -157,14 +169,14 @@ these journals, as they are only available to them and you. Afterwards, you will be able to grade and comment all the entries for that week or topic, and students will receive an automatic email informing them of your feedback.
-
-
+
+

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 @@ -174,23 +186,23 @@ 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
+
Running the course

I could write a thesis about this. Actually I am writing a thesis about this.
@@ -214,25 +226,25 @@ but it's a crucial part of building and maintaining a community feel in your course. -
+

-
Further information
+
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 - in the course called "Using Moodle". + 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

Thanks for using Moodle - good luck!
-
+

-
Moodle Documentation
-
Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01 - martin Exp $
+
Moodle Documentation
+
Version: $Id: teacher.html,v 1.4 2002/08/18 10:00:01 + martin Exp $
- + diff --git a/lang/en/docs/upgrade.html b/lang/en/docs/upgrade.html index 339f6c24f4..ef5cbca8ae 100644 --- a/lang/en/docs/upgrade.html +++ b/lang/en/docs/upgrade.html @@ -1,16 +1,28 @@ - - Moodle Docs: Upgrading - - - + + Moodle Docs: Upgrading + + + + - -
Upgrading Moodle
+ +
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
+
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 @@ -45,11 +57,12 @@

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

-
2. Install the new Moodle software
+ +
2. Install the new Moodle software

Using a downloaded archive

@@ -83,7 +96,7 @@

-
3. Finishing the upgrade
+
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 @@ -102,10 +115,10 @@ 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.
+ Support Forum in the Using Moodle course.
+

-

-
Moodle Documentation
-
Version: $Id$
+
Moodle Documentation
+
Version: $Id$
- + -- 2.39.5