MoodleDocs - User contributions [en]

Site administrators

2013-02-08T08:55:42Z

Fox: French link

{{Standard roles}}
Site administrators have permissions to do anything.

Users may be assigned the role of site administrator by another site administrator in ''Settings > Site administration > Users > Permissions > Site administrators'', but the role itself cannot be edited (or deleted!).

[[File:Managesiteadministrators.png]]

Note: The primary administrator (created when the site was created) cannot be removed from the site administrator role.

[[de:Website-Administrator]]
[[fr:Administrateur]]

User:Séverin Terrier

2013-01-08T10:14:07Z

Fox:

Working in [http://www.ut-capitole.fr Université Toulouse 1 Capitole], i'm administrator of several Moodle sites.

In Moodle community, i :
* assist [[User:Nicolas Martignoni|Nicolas Martignoni]] for [http://moodle.org/course/view.php?id=20 Moodle en français].
* try to improve the [[:fr:|french Moodle documentation]]

[[fr:Utilisateur:Séverin Terrier]]

Verify Database Schema

2012-06-06T14:06:13Z

Fox: French link

If you have been upgrading your Moodle site over several versions, it is possible (likely even) that some differences may have crept in between the database table definitions (the "schema") in your database and the version you would get creating a new empty site. This happens because of small errors or oversights in the upgrade scripts. Most of these differences are not harmful, but some may cause strange or unexpected errors. For example, if a default value has been added to a field and this was not reflected in an upgrade script code that assumes the presence of the default may fail to work as expected.

The solution is after doing an upgrade (or, if your problem is that the upgrade fails, before) to compare the database schema of the "production" site to that of a newly created site (where no upgrades have been performed) using '''exactly''' the same code base. There are a number of ways of doing this, but this article outlines a simple way using the Unix command line.

* Complete the upgrade
* Generate the database schema from your recently upgraded site using the following command:
mysqldump -d -u root -p ''myproductiondb'' >production.schema
* Copy the code of your production database to a new (web accessible) location (this is important, it *must* be the same version)
* Create a new, empty database and moodledata area for the new site as per the [[Installation]] instructions
* Edit the config.php file to point at the new database and locations, or delete it and use the install script
* Run the install script to generate the (if applicable) config.php file and the database (admin and site values are not important)
* Generate the database schema from your new site using the following command:
mysqldump -d -u root -p ''mycleandb'' >clean.schema
* Run the following command to detect the differences
diff -u production.schema clean.schema >db.diff

You can now look at ''db.diff'' with your favorite editor to see the differences.

'''NOTE:''' The above obviously applies to MySQL databases. Other databases are likely to have a similar function to dump only the schema. For example PostgreSQL has the '''pg_dump''' command. The remainder of the discussion still applies.

==Interpreting the diff file==

Firstly here's a (real) example:

--
-- Table structure for table `mdl_backup_config`
@@ -129,11 +93,11 @@
DROP TABLE IF EXISTS `mdl_backup_config`;
CREATE TABLE `mdl_backup_config` (
- `id` int(10) unsigned NOT NULL auto_increment,
+ `id` bigint(10) unsigned NOT NULL auto_increment,
`name` varchar(255) NOT NULL default '',
`value` varchar(255) NOT NULL default '',
PRIMARY KEY (`id`),
- UNIQUE KEY `name` (`name`)
+ UNIQUE KEY `mdl_backconf_nam_uix` (`name`)
) ENGINE=MyISAM AUTO_INCREMENT=15 DEFAULT CHARSET=utf8 COMMENT='To store backup configuration variables';

The file may have lots of blocks of changes. The - lines show lines to be taken out and the + lines the ones to replace them (from the production to the clean). So here, the int has been replaced with a bigint and the key name changed. Both of these, technically, should have been changed at some point by upgrade scripts but have been missed. In this case they are unlikely to affect the operation of Moodle.

===Too many changes to track manually?===

You can also use database management programs to synchronize old and new Moodle databases.

For example [http://wb.mysql.com/ MySQL Workbrench] for MySQL databases.

This is very useful, if You have a lot of changes.

If you can work a Unix/Linux command line the Python script [http://schemasync.org/ Schema Sync] provides a quick and simple way to generate all the commands to update your database.

==Should I worry?==

Changes in field types (as long as they are compatible) and key name changes seem to be the common issues but '''should''' not cause problems. Things to look out for would be along the lines of missing fields and changes to default values.

If you are about to upgrade to Moodle 2.0 you should be more concerned. In order for the upgrade to proceed smoothly it is a very good idea to correct these problems.

== See also ==

* The missing indexes report in SiteAdmin->Misc->XMLDB editor->Check Indexes
* [http://moodle.org/mod/forum/view.php?id=45 Moodle Databases Forum]

[[Category:Administrator]]

[[de:Datenbank-Schema prüfen]]
[[fr:Vérification du schéma de la base de données]]

Managing content

2012-03-27T15:33:52Z

Fox: French link

{{Main page}}
Moodle is '''not''' primarily a content management system but it does offer a range of ways to import, export and manage digital content of any kind to enable and support learning. The following links will provide more information:

* [[Working with files]] - how to upload files and folders to Moodle.
* [[Repositories]] - how to import content into Moodle from external storage sites like [[Flickr repository|Flickr]], [[Youtube_videos_repository|Youtube]], [[Google_Docs_repository|Google docs]] etc.
* [[Portfolios]] - how to export content from Moodle into external portfolios like [[Mahara portfolio|Mahara]].
* [[Working with media]] - how best to upload and display images, sound, video and embedded content.
* [[Filters]] - how to display links,media players, Maths symbols, emoticons and more.
* [[Licences]] - how to display and choose an appropriate licence for your files.
* [[Plagiarism prevention]] - how to check students's submitted work is not copied.

[[fr:Gestion du contenu]]

Custom SQL queries report

2011-04-06T08:36:52Z

Fox:

{{Moodle 1.9}}
Created by The Open University

This admin report plugin allows Administrators to set up arbitrary database queries to act as ad-hoc reports. Reports can be of two types: either run on demand, or scheduled to run automatically. Other users with the right capability can go in and see a list of queries that they have access to. Results can be viewed on-screen or downloaded as CSV.

==Installing this report==

Follow the generic [[Installing contributed modules or plugins]] documentation.

==Screen shots==

Here are two example screen shots, showing the two main screens.

[[Image:Custom_report_list.png|thumb|none|600px|The list of available reports]]
[[Image:Custom_report.png|thumb|none|600px|The results of running one of the reports]]

(Note, these screen shots are in the OU theme, not the standard Moodle theme, and iCMA is OU-jargon for quiz.)

==Interface for normal users==

===List of available queries===

Users with the report/customsql:view capability can access the list of reports in the admin block. Each query is accessible only to a certain people. There are three levels of access:
* Available to any one who can access the report at all (those with report/customsql:view).
* Available to people who are able to see other system reports (those with moodle/site:viewreports)
* Available to administrators only (those with moodle/site:config)

When you go to the list, it will only show the queries you have access to. There is a note beside each query saying when it was last run, and how long it took to generate.

The list shows on-demand and scheduled queries separately.

===Running an on-demand query===

To run an on-demand query, click on its name in the list of queries.

The query will be run, and the results will be displayed as a table. Any URLs in the table will automatically be made into hyperlinks.

A description of the query may appear above the table.

The summary of when the query was run and how long it took is shown at the bottom, along with a link to download the CSV file (for example to get the data into Excel) and a link back to the list of all available queries.

===Viewing the results of scheduled queries===

Scheduled queries can work in one of two ways. Either each run of the report generates and entire table of reasults, or each run just creates one line of results, and the report builds up a row at a time.

When you click the name in the list of queries, you get taken to a display of the latest results, just like in the on-demand case.

However, if each scheduled run generates a complete report, then at the bottom of a page there will be a list of all the previous runs of the report, so that you can go and see how the report changed over time.

==Interface for administrators==

Administrators (that is, users with report/customsql:definequeries) see everything that other users see, but with some additions.

===Additional controls in the staff interface===

Administrators get shown who each report in the list is available to.

They also get an edit and a delete icon next to each query.

There is an '''Add new query button''' at the end of the list of queries.

When viewing a particular query, Administrators get an edit and a delete link underneath the table of results.

===Adding or editing a query===

When you click the '''Add new query button''', you get taken to an editing form that lets you define the query.

You must give the query a name.

You can optionally enter a description that is displayed above the results table. You should use this to explain what the results of the query mean.

You must enter the SQL to generate the results you want displayed. This must be an SQL select statement. You must use the prefix prefix_ for table names. It should not be possible to enter any SQL that would alter the contents of the database.

You choose who you want the query to be accessible to.

You choose whether the query should be run on-demand or scheduled weekly or monthly. If the report is scheduled, you can say whether the each run returns one row to be added to a single table, or whether each run generates a separate table.

When you save the new query, the SQL is checked to make sure that it will execute without errors. If you have said that the report will only return a single row, this is also checked.
After saving the query, if this was a manual query, you are taken to the query results page, so you can see what the results look like. If it was an automatic query or if you cancel the form, you are taken to the list of available queries.

Editing an existing query uses the same form as for adding a new query, but to change the properties of an existing query.

Note that at the OU, weeks start on Saturday. If you don't like that, there is a fairly obvious constant to hack at the top of locallib.php.

===Deleting a query===

When you click the delete icon or link for a query, you are taken to a confirmation page that shows you SQL of the query you are about to delete. The query is only deleted if you click Yes on the confirmation page.

After deleting a query, you are taken back to the list of queries.

==Share your interesting queries here==

If you come up with any interesting SQL to custom reports, you can share it here.

===Quiz attempts in the last week/month===

Set this up as a scheduled report:

<code sql>
SELECT COUNT(*)
FROM prefix_quiz_attempts
WHERE timefinish > %%STARTTIME%%
AND timefinish <= %%ENDTIME%%
AND preview = 0
</code>

This '''must''' be set up as a '''Scheduled, on the first day of each week''' or '''Scheduled, on the first day of each month''' report, or it will not work.

===Usage summary===

This report shows roughly the same usage statistics that are sent to moodle.org when you register your site. The ones that are aggregated at http://moodle.org/stats/. (The only difference is that the registration form does not do AND confirmed = 1 for some reason.

<code sql>
SELECT
(SELECT COUNT(id) FROM prefix_course) - 1 AS courses,
(SELECT COUNT(id) FROM prefix_user WHERE deleted = 0 AND confirmed = 1) AS users,
(SELECT COUNT(DISTINCT ra.userid)
FROM prefix_role_capabilities rc
JOIN prefix_role_assignments ra ON ra.roleid = rc.roleid
WHERE rc.capability IN ('moodle/course:upd' || 'ate', 'moodle/site:doanything')) AS teachers,
(SELECT COUNT(id) FROM prefix_role_assignments) AS enrolments,
(SELECT COUNT(id) FROM prefix_forum_posts) AS forum_posts,
(SELECT COUNT(id) FROM prefix_resource) AS resources,
(SELECT COUNT(id) FROM prefix_question) AS questions
</code>

There are two interesting queries in this blog post [http://tjhunt.blogspot.com/2010/03/when-do-students-submit-their-online.html When do students submit their online tests?].

===Monthly Usage by Role===

This report shows a distinct count of users by their role, accessing your site. Each instance of user and role is counted once per month, no matter how many courses they access. We use this to show the total number of students and teachers accessing our site.

<code sql>
SELECT
month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)) AS calendar_month,
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)) AS calendar_year,
prefix_role.name as user_role,
COUNT(DISTINCT prefix_stats_user_monthly.userid) AS total_users
FROM
prefix_stats_user_monthly
Inner Join prefix_role_assignments ON prefix_stats_user_monthly.userid = prefix_role_assignments.userid
Inner Join prefix_context ON prefix_role_assignments.contextid = prefix_context.id
Inner Join prefix_role ON prefix_role_assignments.roleid = prefix_role.id
WHERE prefix_context.contextlevel = 50
AND `prefix_stats_user_monthly`.`stattype` = 'activity'
AND prefix_stats_user_monthly.courseid <>1
GROUP BY month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),
prefix_stats_user_monthly.stattype,
prefix_role.name
ORDER BY
year(from_unixtime(`prefix_stats_user_monthly`.`timeend`)), month(from_unixtime(`prefix_stats_user_monthly`.`timeend`)),
prefix_role.name
</code>

You must have Statistics turned on to be able to generate any data with this report.

===Show all Quiz results across a site===
I'm sure someone will be able to improve upon this, but this is a query that will show Quiz results across a site. --[[User:Stuart Mealor|Stuart Mealor]] 22:07, 9 April 2010 (UTC)

<code sql>
SELECT
prefix_grade_items.itemname,
prefix_grade_items.grademax,
ROUND(prefix_grade_grades.finalgrade, 0) AS finalgrade,
prefix_user.firstname,
prefix_user.lastname,
prefix_user.username
FROM
prefix_grade_grades
INNER JOIN prefix_user ON prefix_grade_grades.userid = prefix_user.id
INNER JOIN prefix_grade_items ON prefix_grade_grades.itemid = prefix_grade_items.id
WHERE (prefix_grade_items.itemname IS NOT NULL)
AND (prefix_grade_items.itemtype = 'mod' OR prefix_grade_items.itemtype = 'manual')
AND (prefix_grade_items.itemmodule = 'quiz' OR prefix_grade_items.itemmodule IS NULL)
AND (prefix_grade_grades.timemodified IS NOT NULL)
AND (prefix_grade_grades.finalgrade > 0)
AND (prefix_user.deleted = 0)
</code>

==See also==

* [[Reports_(administrator)]] for other admin reports
* [[Installing contributed modules or plugins]]
* [http://moodle.org/mod/forum/discuss.php?d=136484 Custom SQL queries report] forum announcement
* list of [[ad-hoc contributed reports]]
* [http://moodle.org/mod/forum/discuss.php?d=153059 Forum post] with some more useful queries.

[[Category: Administrator]]
[[Category:Report]]
[[Category:Contributed_code]]

[[fr:admin/report/customsql/index]]

MoodleDocs talk:Moodle Docs reorganisation

2011-03-31T14:52:51Z

Fox: /* How do maintainers of non-English wikis like this? */

== Namespaces or... separate wikis? ==
One really "silly" (or no) thought I had yesterday...

I think we are going to have some problems when using namespaces to separate versions, because all the "common bits" (templates, categories, images, user, talk...) need to be also moved to namespaces, and some of them, really, cannot be moved as far as already belong to one namespace (for example, templates).

So, thinking on this... I just began thinking if wouldn't be better, instead... to have complete new wikies for this. So, for example, we'll end having:

* https://docs.moodle.org/en/2.0/
* https://docs.moodle.org/en/2.1/
* ....

I know it is a completely different beast from what had been thought until now, but it has some great advantages:

# Each version is 100% autocontained. So work is completely isolated.
# Easy to create new versions (just duplicate DB and Filesystem structures)
# No conficts with templates/images/categories at all.
# Each Moodle "knows" what to call, without problems. Just set the X.Y prefix in the URL accordingly with its version.
# One process can be run daily, looking for pagename coincidences across DBs, in order to display information in the header of each page.

In the other side, it also has some drawbacks:

# One change in, say, the "en/2.0/Backup_FAQ" will need to be '''manually replicated''' to all the pages in other wikies if necessary (note that happens also in the original "by namespace split" alternative.
# Size. The server needed space will grow. No doubt about that.
# Surely other things I haven't been able to imagine. Please think!

So that is... just one alternative that seems to solve some of the conflicts that will happen with the namespaces way. Discuss, discuss!

'''Edited:''' Just to make things more complex in our minds... perhaps another alternative could be to have one "commons" wiki (current one) for all the pages not tidied with versions, and then the 2.0, 2.1... above for information susceptible to change. That way common stuff could be edited only once (about, help, releases info, FAQs...) and Developers/Teacher/Admin.. pages would had their place in the versioned wikis, for easier evolution.

Ciao :-) --[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 14:38, 18 March 2011 (UTC)

== How do maintainers of non-English wikis like this? ==

As I have expressed in the chat, I am a bit afraid of how this reorganization would be accepted by the maintainers of non-English wikis. --[[User:David Mudrak|David Mudrak]] 09:06, 31 March 2011 (UTC)

: As primary maintainer of French Moodle Docs (With Nicolas Martignoni), i can say that there's nearly nobody involved in the French documentation :-( People would like to find usefull pages, but don't want (or don't know how) to take time to improve documentation (And they're most used to Forums). I personnally won't make the move to dedicated spaces for different Moodle versions, as i'm today not able to add all what would be needed in 1 version ! It's for me undoable to have several versions of the documentation.
:So, if the main english documentation is splitted by version, i don't really know how i could work. It's always possible to link from different english versions to 1 french page (in interlink block), but the opposit is not doable. --[[User:Séverin Terrier|Séverin Terrier]] 14:52, 31 March 2011 (UTC)

Installations 10000 plus

2011-03-29T14:05:33Z

Fox:

{{Template:Large Installations}}

Please add your school info here, if you have a Moodle installation catering (or expecting to cater) for 10,000 or more users.
==Austria==
* [http://elearning.tuwien.ac.at/ Moodle (TUWEL)] user statistics September 25th 2009 - Vienna University of Technology (TU Vienna)

- 19.250 users (students & teachers)
- 13.400 students enrolled in courses
- 1.030 teachers enrolled in courses
- 5000+ active users per day

Our mission is „technology for people“. Through our research we „develop scientific excellence“, through our teaching we „enhance comprehensive competence“.

* [http://moodle.uni-graz.at/ moodle @ uni-graz ] Primary moodle server of the Karl Franzens University Graz.

==Brazil==

* [http://www.escolatecnica.ufrgs.br Escola Técnica da Universidade Federal do Rio Grande do Sul] - Professional school in Brazil, with 1,200 students. Adopted Moodle in 2004 and has been using it since then.

==Canada==

* [http://www.athabascau.ca/ Athabasca University] - Canada's leading distance-education and online university: Canada's Open University, serving about 30,000 students per year. Athabasca has decided to adopt Moodle as a single platform instead of WebCT Vista (i.e. the top of the line version). You can read their [http://www.athabascau.ca/media/index.php?id=132 press release] for more info.

* [http://moodle.mala.bc.ca/ Malaspina University-College] - Malaspina U-C is located on Vancouver Island in British Columbia, Canada. MUC was established in 1969, and has over 10,000 full-time Canadian students, plus 1,000 international students from more than 50 countries. MUC offers graduate and undergraduate degrees, diplomas and certificates, and a 5-level English Language program. MUC offers classroom-student support through Moodle, as well as a range of fully online courses through [http://pr.malaonline.ca/ Malaspina Continuing Education]. MUC switched from WebCT to Moodle in 2006.

* [http://www.usherbrooke.ca/ Université de Sherbrooke] - L'Université de Sherbrooke accueille plus de 37 000 étudiantes et étudiants, provenant de plus de 100 pays, dont quelque 9000 inscrits à l’Université du troisième âge. Plus de 85 % de la population étudiante de l’Université de Sherbrooke provient de l’extérieur de Sherbrooke. L’Université de Sherbrooke emploie 6700 personnes. Elle compte 10 % du corps professoral québécois.

==China==

* [http://english.bit.edu.cn/ Beijing Institute of Technology]

==Czech Republic==

* [https://moodle.czu.cz Czech University of Life Sciences Prague]
** 35,590 users in 911 courses (14,665 active users in last 15 days) / 18th October 2010
** Moodle 1.9.5
** integration with LDAP and Oracle
** Administration: [http://www.oikt.czu.cz/?r=1686 E-learning Support Centre, Division of IT, CULS Prague]

==France==

* [http://cursus.uhb.fr/ Université de Rennes 2 - Haute Bretagne] - 20,000 to 30,000 users in 1400 courses
** 8,000 different users connected every month
** 300 teachers actually involved
** integration with LDAP and Esup-Portail (based on uPortal) ;
** authentication via CAS

* [http://cours.univ-tlse1.fr/ Université Toulouse 1 Capitole] - 18,000 users in 800 courses, Moodle 1.9.11+
** 300 teachers actually involved
** integration with LDAP and Esup-Portail (based on uPortal)
** authentication via CAS

==Germany==

* [http://www.isis.tu-berlin.de/ Technische Universität Berlin] - 10,400 Users in 402 courses (updated: 07.June.2007)
** After a test period, the Information System for Instructors and Students (ISIS) was launched in september 2006.

==India==
* [http://www.amieindia.net AMIE India] is a website for [http://www.amieindia.net AMIE] students currently (as of September 2007) having 239 courses, 11246 users.

* [http://www.visveswaraya.org/ AMIE] a residential AMIE Institute in Kerala, India, listed in LIMCA Book of Records with 130 All India Ranks, is best ever for AMIE coaching & IIT & NIT higher studies.

==Ireland==

* [http://www.dcu.ie Dublin City University] 18,000 users in 3,600 courses.

==Italy==

* [http://www.aulaweb.unige.it/ AulaWeb - University of Genoa] AulaWeb is an university-wide installation of Moodle, organized in virtual instances, one for each laurea degree. In March 2007, it hosts more than 78 instances used by 10.500 students.

==Jamaica==
*[http://ourvle.mona.uwi.edu The University of the West Indies] - 23,000+ users in 1600+ courses

==New Zealand==

*[http://campus.openpolytechnic.ac.nz/ The Open Polytechnic of New Zealand] - 35,000+ students, 6,500+ courses, single sign-on for library services using Ezy Proxy, single sign-on for webmail, using SquirrelMail, uses LDAP for interface with Sears Student Management System. Comments by [https://eduforge.org/wiki/wiki/nzvle/wiki?pagename=Comments%20by%20Ken%20Udas%2C%20Director%20of%20eLearning%20at%20the%20Open%20Polytechnic Ken Udas, Director of eLearning at the Open Polytechnic]

==Palestine==

*[http://eclass.alquds.edu Al-Quds University] - 12,000+ users in 900+ courses. Al-Quds University started using moodle in 2004.

== Philippines ==

* [http://eclass.adzu.edu.ph Ateneo de Zamboanga University] - with 10,000+ faculty, staff and students (started using Moodle since 2002)

== Portugal ==

[http://moodle.fct.unl.pt/ Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa] - 5000+ users in 400+ pages.

==South Africa==

* [http://www.ru.ac.za Rhodes University] in Grahamstown runs an instance of Moodle as its institutional LMS [http://ruconnected.ru.ac.za RUconnected] currently with more than 10 000 registered users, including more than 550 teachers.

== Spain ==

*[http://aulavirtual.uji.es/ Universitat Jaume I]. Official VLE since 2004. 13.600 real users (12.500 students and 1.100 teachers) and 1.300 active courses on February 2009. Moodle 1.9.x.

*[http://www.upc.edu La Universitat Politecnica de Cataluña] on september 2005 started a pilot Moodle installation with 3.000 Students. On september 2006 the migration from the old campus to Moodle will be complete with more than 30.00 students [http://atenea.upc.edu El campus Atenea 4] runs Moodle 1.4.5 y an will be updated to Moodle 1.5.3 in september 2006. [http://www.upc.edu UPC] has developed several applicatons adn bridges between its own informacion systems.
** Integration with the academic management informatio system "Prisma".
** [http://appserv.lsi.upc.es/palangana/moodle/course/view.php?id=18 Internalmail] (developed also in UPC) is used for as email internal system.
** Moodle integration with [http://bibliotecnica.upc.edu the upc library system].
** Adaptation of Moodle grades to spanish university grading system.
** And other stuff

*[http://www.urv.cat/ Universitat Rovira i Virgili] using Moodle for three academic years. At present version 1.5.4+ to be updated to 1.6.4+ in short. In march 2007, 22701 users registered and 3500 courses created aprox.
** Integration with the academic management information system
** Integration with the corporative LDAP user’s directory
** Average of 504 courses used regularly (logs at least once a week)
** Average of 3200 students login at least once a day
** Average of 7200 students login at least once a week
** 10500 users (teachers and students) accessed at least once during the last month (data from 26th march 2007)

*[http://www.ulpgc.es/index.php?pagina=campusvirtual&ver=inicio Universidad de Las Palmas de Gran Canaria (ULPGC)] - 24.000 users in aprox. 1800 courses. We started with Moodle 1.4 four years ago as a test pilot project for a small number of courses. Now offered as a basic service for all courses at ULPGC: 55 official EU titles and 5 more offered ONLY through Web.
** We are using version 1.6.3 with LDAP authentification
** Custom modules: ULPGCAssignment and ULPGCDialogUe, heavily modified Appointment/Scheduler
** Custom groupings/scopes for small team activities (e.g. group assignment)
** Regular-intense usage ranks by 60% of courses/students.

*[http://campusvirtual.ub.edu/ Universitat de Barcelona] - 60.000 users in 7.300 courses. Started in September 2006 as a project, UB Moodle site will be open for all next September.

*[http://campuvirtual.unex.es Universidad de Extremadura] - 15000 users in aprox. 700 courses.

*[http://www.juntadeandalucia.es/educacion/adistancia/semipresencial Andalusia Blended Learning ].VLE of [http://www.juntadeandalucia.es/educacion/permanente Lifelong Learning Service] of ''Junta de Andalucía''.Actually (2009/2010) 1600 courses and 25000 in aprox. Between them 1500 teachers. It's expected 35000 users next year. This VLE is complemented with [http://www.juntadeandalucia.es/educacion/adistancia/avep LifeLong Learning VLE] that offers and open access to educational materials developed for blended learning.

== Sweden ==

[http://lnu.se/?l=en Linnaeus University] - 35.000 students and and 2.000 employees in 2011 - 23.000 Moodle users in 2.000 Moodle courses.

==Taiwan==

[http://www.thu.edu.tw/english/enindex.htm Tunghai University]
*More then 17,000 registed Users
*16,000 users login in one day( Max. )
*3,000 courses per semester
*integration with novell ichan for single sign on
*integration with school support system

our moodle web site: [http://elearning.thu.edu.tw]

==Trinidad and Tobago==

[http://myelearning.sta.uwi.edu The University of the West Indies]
St. Augustine Campus
*More then 22,000 registed Users
*Over 500 Courses per semester
*Over 1500 Teachers

Using Moodle since 2006.

==United Kingdom==

*[http://www.open.ac.uk/ The Open University (OU)] - the United Kingdom's only university dedicated to distance learning. They have around 150,000 undergraduate and more than 30,000 postgraduate students. As of October 2010, the OU's Moodle database contains over 700,000 users and 7,000 courses.

*[http://openlearn.open.ac.uk/ OpenLearn] The Open University's open content initiative. Website development began in May 2006 and the site was launched in October 2006, supported by a grant from The William and Flora Hewlett Foundation. By April 2008, 5,400 learning hours of content will be available online. Currenly (early 2007) over 10,000 unique users.

*[http://www.gla.ac.uk/ The University of Glasgow] - A long-established (founded 1451) and high-profile research university in the UK, with 20,000 students (16,000 undergrad, 4,000 postgrad), 6,000 staff, 20,000 unique users of Moodle (as of Jan 2008). Uses LDAP for integration with Novell and a custom MIS system for user authentication. Their site is organised on a one Moodle site per faculty basis to facilitate both appropriate themeing and to simplify balancing across servers.

==United States==

*[http://moodle.cpcc.edu Central Piedmont Community College (CPCC) ] uses moodle for both curriculum and Corporate and Continuing Education. For curriculum it runs in parallel to Blackboard as faculty migrate to moodle over time. There are currently no plans to go moodle only, although many administrators favor this option. The server has 30,000 or so users on it, but the actual number of active users varies widely. It is used for both hybrid and full-online classes. Corporate and Continuing Education runs its own branded instance and uses only moodle for distance education. We have about 80,000 students total, covering the range from GED, adult-ed, curriculum, and other areas serviced by 7 campuses in and around Charlotte, North Carolina.

*[http://ilearn.sfsu.edu San Francisco State University (SFSU) ] uses moodle for more than three years now. We use moodle for our main campus and the College of Extended Learning (CEL). For curriculum, moodle used to run in parallel with Blackboard as faculty migrate to moodle over time (SFSU officially phased out Blackboard, as of 6/30/2007). The servers have total of 89K users (as of 09/05/2007), among these 89K users, 28K are considered as currently active. As for courses, we have total of 57K courses sitting on our database, and among them, around 53K are considered as active. We also have integrated Moodle with our SIMS/R system (see http://www.sfsu.edu/sims/overview.htm). We also have courses that have more than 1,300+ students in one course with lots of quizzes (20+) and quiz attempts. The student population in SFSU covers the range from undergraduate, graduate, and first professional students.

== Venezuela ==

* [http://moodle.unica.edu.ve Cecilio Acosta Catholic University (UNICA)] - with 10,000+ faculty, staff and students (started using Moodle since 2005)

[[Category:Administrator]]

Template:Moodle 2.1

2011-03-29T08:04:22Z

Fox: French link

Moodle 2.1
<includeonly>[[Category:Moodle 2.1]]</includeonly>
<noinclude>This template will categorize articles that include it into [[:Category:Moodle 2.1]].</noinclude>
<noinclude>[[fr:Modèle:Moodle 2.1]]</noinclude>

admin/environment/php

2011-03-29T07:58:14Z

Fox:

Moodle has different PHP requirements for different versions:

* Moodle 2.1 will require PHP 5.3.2 or later
* Moodle 2.0 requires PHP 5.2.8 or later. However PHP 5.3.x is recommended
* Moodle 1.6 to 1.9 requires PHP 4.3.0 or later
* Moodle 1.0 to 1.5 requires PHP 4.1.0 or later

==See also==

* http://www.php.net/downloads.php for the latest downloads

[[Category:Environment|PHP]]

[[eu:admin/environment/php]]
[[fr:admin/environment/php]]

Advanced features

2011-03-28T13:32:08Z

Fox: French link

{{Moodle 2.0}}Location: ''Site Administration > Advanced features''

The following features in Moodle 2.0 onwards may be enabled/disabled in Advanced features:

* [[Outcomes]]
* [[Comments 2.0]]
* [[Tags|Tags functionality]]
* [[Notes]]
* [[Portfolios]]
* [[Web Services]]
* [[Messaging]]
* [[Statistics]]
* [[RSS feeds 2.0|RSS feeds]]
* [[Blogs]]
* [[MNet|Networking]]
* [[Development:Course_completion|Completion tracking]]
* [[Conditional_activities|Conditional availability]]
* [[Plagiarism Prevention|Plagiarism plugins]]

[[Category:Administrator]]

[[eu:Funtzio_aurreratuak]]
[[de:Zusatzoptionen]]
[[fr:Fonctions avancées]]

Talk:Roadmap

2011-03-24T15:46:18Z

Fox: /* What happened to Survey module rewrite for 2.1? */

==Minimum PHP requirement==

Yes, this should be well specified on the page--[[User:Séverin Terrier|Séverin Terrier]] 02:47, 5 November 2008 (CST)

Link to PHP page (gophp5.org) is no longer valid - it's been squatted [[User:David Barber|David Barber]] 14:39, 12 June 2009 (UTC)

==Student Information API for version 2.0==

Also on a related point the student API which is down for version 2.0. Is there any more detail to here on this yet? Will this be part of the IMS Enterprise data model and therefore enrolments plug in or will someone be working on a Moodle SIF agent? In the UK SIF is likely to take off as the DfES via Becta are currently consulting on a UK SIF model and piloting SIF in Birmingham and Northern Ireland. I believe that SIF is used quite widely in the US?

== Wiki engine ==

I noticed there was some talk about making new wiki module for 1.9... what do "nWiki" and "DF wiki" refer to? I've searched online and haven't found a clear description of what these mean. I am curious if they are still based on MediaWiki. I would hate to see some of the great features of MediaWiki (mainly the scalability) be lost. When MediaWiki is configured with Memcached and Squid caching servers, they can serve thousands of requests per second: hard to beat! 
Thanks, 
-[[User:Sean Colombo|Sean Colombo]] 00:12, 13 January 2008 (CST)

None of the wikis are based on Mediawiki. Mediawiki is very difficult to use as a basis for a Moodle wiki, because of all the special features we need. [[User:Martin Dougiamas|Martin Dougiamas]] 22:10, 22 April 2008 (CDT)

You can see [[Dfwiki]] page to more details and links. --[[User:Ne Nashev|Ne Nashev]] 16:57, 28 February 2009 (CST)

== about nwiki ==

Seems that nwiki will be inside for 2.0.
Nwiki IMPLEMENTS the mediawiki markup, and the old features of the current wiki for backwards compatibility... and that is what makes it so difficult. Is really hard.

You migth get by the Using moodle wiki forum and we can discuss about it.
Cheers.
--[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 11:14, 13 January 2008 (CST)

== About Web Services ? ==

Where fit the WS layer in the roadmap?

:Please see [[Development:Web services]] and the [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum]. --[[User:Helen Foster|Helen Foster]] 14:09, 17 December 2009 (UTC)

== IMS LIT 2.0 compliance ? ==

*Wimba is working with IMS to develop an activity module that acts as a consumer of the IMS LTI 2.0 standard...
*We in UPC (dfwikiteam) are working in a way to make the moodle course a IMS LTI 2.0 producer ...
shall this be included somewhere in the roadmap?--[[User:Ludo (Marc Alier)|Ludo (Marc Alier)]] 01:05, 9 April 2008 (CDT)

== Site-wide groups ==
Site-wide (or, preferrable, context-wide) groups is much needed improvement (see votes for MDL-11826), especially in large institutions. Can it be targeted to 2.0?

Yes, it would really help lot of people...
--[[User:Séverin Terrier|Séverin Terrier]] 16:57, 13 May 2008 (CDT)

MDL-15416 seems to have been tagged for 2.0 by Petr :) [[User:Matt Gibson|Matt Gibson]] 10:46, 19 May 2008 (CDT)

It says: " Global groups - Global groups are not implemented in 1.9. They are not going to be implemented at the database level. Instead some other solution should be present in 2.0. This will require patching of enrolment framework and group/lib.php" in https://docs.moodle.org/en/Development:Groups#Global_groups - any word on whether this is planned any more definitley in 2.0?? --[[User:Derek Chirnside|Derek Chirnside]] 06:32, 7 October 2008 (CDT)

==Minted course profile plugin==
This was scheduled for 1.9, but didn't make it. Any plans to include it in 2.0? It seems to have vanished. [[User:Matt Gibson|Matt Gibson]] 10:47, 19 May 2008 (CDT)

== Instructor-led Training Session Management ==

In several of the projects we work on there is a very real need to manage instructor-led sessions by booking training rooms and assigning trainers. I've always felt that Moodle is so advanced in many areas but this is something that is not really catered for. Developing this will mean that Moodle can comfortably handle blended-learning.

There has been some fantastic work done on the Face-to-Face contrib module and the integration of the MRBS module. But in my experience, what's needed is actually a combination of the two systems that integrates to the Moodle calandar and other standard components.

I'd be happy to spec out the requirements and test in real environments.

Craig Meltzer
[http://moodle.org/user/view.php?id=34863&course=1]

==Subscribe at the thread level & Book Module==

I notice in the tracker http://tracker.moodle.org/browse/MDL-1626 there is a request for the ability for notification (subscription) at the thread level, not just the forum level.
It says it is in 2.0 in the tracker.
What does this mean? Is this definite, since it is not mentioned in the roadmap? Is it too ''small'' an enhancement to justify comment in the roadmap? To what level of detail does the roadmap get maintained?

I note there is a request for the book module to be in the core. http://tracker.moodle.org/browse/CONTRIB-283 But it does not have a fix version indicated. Does that mean the request is not considered significant to be included in 2.0?? --[[User:Derek Chirnside|Derek Chirnside]] 02:56, 6 July 2008 (CDT)

:Derek, the Book module will remain a contributed module for 2.0, but will hopefully be included in Moodle 2.1 core. --[[User:Helen Foster|Helen Foster]] 07:14, 3 March 2010 (UTC) (Thanks Helen - Derek)

Just checking to see about this. Any progress on subscribe at the thread level? Is it in 2.0? (is this the right place to ask?) --[[User:Derek Chirnside|Derek Chirnside]] 00:21, 3 March 2010 (UTC)

:Subscribe to thread is not in core yet. It is implemented in the third-party ForumNG http://moodle.org/mod/forum/discuss.php?d=137549, which is still very new, but already a very slick forum. Basically just like the standard Moodle forum, but with a slicker interface and a few more features. Some of us hope that ForumNG will replace the standard Moodle forum in due course.--[[User:Tim Hunt|Tim Hunt]] 08:39, 3 March 2010 (UTC)

:Thanks Tim: Martin posted yesterday here: http://tracker.moodle.org/browse/MDL-1626 Nothing due until 2.1. I also note your comment about voting here: http://tracker.moodle.org/browse/MDL-21538 And ForumNG beta until June. Hmm. Something to look forward to. --[[User:Derek Chirnside|Derek Chirnside]] 19:53, 8 March 2010 (UTC)

==Blog & Comments in 2.0==

This is a similar comment to above. There is a lot of talk about blogs on the various forums here in Moodle.org, and in particular the Moodle implmentation of them.

Particularly here: http://moodle.org/mod/forum/discuss.php?d=94623#p418128 and here: http://moodle.org/mod/forum/discuss.php?d=44830&mode=3

There is an issue tracker here: http://tracker.moodle.org/browse/MDL-8776 but there doesn't seem to be any sort of focus to the discussion in the details. From the roadmap: comments are coming. What about the other suggestions in the tracker? Where do we find out what is coming and what is planned? How are decisions arrived at?

I'm curious about the OU blogs as well. --[[User:Derek Chirnside|Derek Chirnside]] 03:13, 6 July 2008 (CDT)

==No longer called Activitiy locking==

Now called: Conditional activities. I like this terminology change. Activity locking is a little more draconican and control sounding. And there is good reason to avoid the term "Selective Release".

I'd really like it to be very very simple. A linear pathway being easy to construct, with any possible complex stuff hidden in an advanced tab. Most of what the lecturers do here is like that. --[[User:Derek Chirnside|Derek Chirnside]] 03:18, 6 July 2008 (CDT)

== are calendar improvements planned? ==

Is there any plan to change the way calendar are used in moodle?

:Hi, as the calendar is not mentioned in the roadmap, I don't think there is any plan to change the way it is used. However, this situation may change according to available funding and developers. --[[User:Helen Foster|Helen Foster]] 08:39, 18 November 2008 (CST)

== Support for Simple content management on the front page of Moodle (like Janne's CMS) ==

Is this feature still in the plans as it was when MDL-10285 was flagged with: "Fix Version/s: 2.0" on March 20, 2008?

== Is this all for 2.0 really? ==

It seems that Moodle 2.0 is too feature loaded by now (one may even think that there will be no 2.1). It's development cycle already seems to be more than year, and it's heavily loaded with complex features. There are some disadvantages in this:
* there is some functionality in the HEAD already, that can be useful to people and address important issues, but can't be merged to 1.9 - but it is inaccessible to the productional use because of general instability of the HEAD, and concerning later information it will be inaccessible for quite some time (while Moodle developers often referred on issues fixed in 2.0 as if people can just get and use them)
* there are concerns about stability of the resulting release with so many complex features added at once, without general use and testing some of them in production environment - it may well be worse than with roles in Moodle 1.7

Maybe there can be an intermediate release, some sort of 1.10 or 2.0.0, (or what it can be, titles are no important) version with part of the new functionality added, so the people can start use it (and give more real word testing too)? --[[User:Oleg Sychev|Oleg Sychev]] 06:40, 29 November 2008 (CST)

[[User:Martin Dougiamas|Martin Dougiamas]] 00:59, 22 December 2008 (CST): Well, a lot has been been left for later already (2.1, 2.2, 2.3 etc). About testing, 2.0 will have a very long testing period to avoid situations like 1.7 (and people are already helping with testing). It's easy to say "make more interim releases" but each of these has a huge cost on our pace ... after a release new development basically stops for months, which means that some of the features coming next year in 2.0 would take even longer to arrive. Currently most of the roadmap is all proceeding at the same time (different people working on things) and we are simultaneously patching 1.9.x still. Then again there a few things that might hold up 2.0 and could still be cut, depending on volunteers, funding etc. It's a balancing act, but I think we're charting the right course for an impressive 2.0 in decent time.

== Workshop 2.0 ==

See [[Development:Workshop_module]] --[[User:David Mudrak|David Mudrak]] 07:13, 28 March 2009 (UTC)

:Thanks David, Workshop is now listed. --[[User:Helen Foster|Helen Foster]] 14:42, 17 December 2009 (UTC)

== Minor: link to summer code under quiz broken ==

link to summer code/editing quiz UI, under quiz, is broken
Correct URL: http://www.coss.fi/en/kesakoodi
--[[User:Olli Savolainen|Olli Savolainen]] 10:33, 10 August 2009 (UTC)

:Thanks Olli, the link is now fixed. --[[User:Helen Foster|Helen Foster]] 14:42, 17 December 2009 (UTC)

== Tagging ==
What exactly is meant by "tagging of courses, activities and other things"? Where I can find out how much progress has been made with this? Thanks. [[User:Myse Elmadani|Myse Elmadani]] 00:18, 10 December 2009 (UTC)

:Myse, please see MDL-13404. --[[User:Helen Foster|Helen Foster]] 14:42, 17 December 2009 (UTC)

== Will there be improvements to quiz performance with large numbers ==

I can see that the quiz reports are being rewritten, but is the underlying quiz engine being improved so that large numbers of people can take the same quiz concurrently without the servers maxing out? No worries if not. I just need to know for planning purposes.

: Yes, it is being rewritten. See [[Development:Question_Engine_2]]. however, I am not promising that it will be finished in time for Moodle 2.0. 2.1 is probably more realistic.--[[User:Tim Hunt|Tim Hunt]] 16:12, 17 December 2009 (UTC)

== What happened to Survey module rewrite for 2.1? ==

Up until recently, the roadmap page for 2.1 said that the best of questionnaire, survey and feedback features were going to be combined into a rewrite for the Survey module. It even still alludes to this on the Feedback module page

https://docs.moodle.org/en/Feedback_module

However, the item for this on the roadmap page disappeared sometime in the last few weeks. Has this been dropped from 2.1? If so why and when is it slated for?

:It's being worked on, but it's a huge job and won't be ready in time for 2.1. We have time-based releases now. [[User:Martin Dougiamas|Martin Dougiamas]] 09:36, 24 March 2011 (UTC)

::Please see [[Development:Survey 2 brainstorm]] for more details. --[[User:Helen Foster|Helen Foster]] 09:45, 24 March 2011 (UTC)

:::Perhaps with these new time-based releases, that will happen more often, it would be useful to have more than one version in Roadmap, and already add Moodle 2.2 (and 2.3 ? if you have a good idea of what should/would be included). It could help people to have an idea of what they can '''hope''' to get in next versions --[[User:Séverin Terrier|Séverin Terrier]] 15:46, 24 March 2011 (UTC)

Category:Environment

2011-03-22T15:36:58Z

Fox: French link

An index of Moodle [[Environment|environment]] documentation pages.

[[Category:Administrator]]

[[fr:Catégorie:Environnement]]
[[ja:Category:動作環境]]

admin/environment/custom check/php check php533

2011-03-22T15:28:08Z

Fox: French link

Moodle 2.0 will require PHP 5.2.8 or later. However PHP 5.3.3 or later is recommended.

PHP 5.3.3 has better stability, security and memory management compared to 5.2.8.

==See also==
* http://php.net/releases/5_3_3.php release note
* http://www.php.net/ChangeLog-5.php#5.3.3 change log
* http://www.php.net/downloads.php for the latest downloads

[[Category:Environment|PHP]]

[[eu:admin/environment/php]]
[[fr:admin/environment/custom check/php check php533]]

report/security/report security check displayerrors

2011-03-18T15:26:48Z

Fox: French link

If PHP is set to display errors, then anyone can enter a faulty URL causing PHP to give up valuable information about directory structures and so on.

(Can someone add instructions on where to turn this off please).

: If you go to ''Administration > Server > Debugging'' and set "Debug messages" to NONE and "Display debug messages" to NO you should be on the safe side. (If this instruction is correct it should be included in the Security Overview report.) --[[User:Frank Ralf|Frank Ralf]] 11:28, 7 November 2009 (UTC)

If you go to '''Administration|Reports|Security overview''', displaying of PHP errors status is Warning.
on your web server, locate php.ini, open it in wordpad and search for "'''display_errors'''". Ensure that it is set to "'''display_errors = Off'''" and then save. If this is on a hosted webserver (e.g. network solutions), insert "'''display_errors = Off'''" into the php.ini or call them for instructions (took 2 minutes) on how to do it. Very simple to modify. (by '''opconxps''' guam)

==See also==

* Using Moodle [http://moodle.org/mod/forum/view.php?id=7301 Security and Privacy forum]
* Using [http://moodle.org/mod/forum/discuss.php?d=101761 upgrade to 1.9.2 has PHP setting display_errors message] Moodle forum discussion

[[Category:Security]]

[[eu:report/security/report_security_check_displayerrors]]
[[fr:report/security/report security check displayerrors]]

report/security/report security check configrw

2011-03-18T15:21:50Z

Fox: French link

{{stub}}

It's important that you CHMOD (set permissions) on config.php as read-only. Typically this means setting it to 644, or in some cases 444.

If you cannot do this with your FTP software, try using the File Manager supplied with your webhosting account. Simply navigate to the file you want to alter permissions for, then click on the File Properties link/button and set permissions.

If you're using a Windows server, simply set the file as Read-Only for Everyone.

==See also==

* Using Moodle [http://moodle.org/mod/forum/view.php?id=7301 Security and Privacy forum]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=116140 Corrupted php files] forum discussion

[[Category:Security]]

[[fr:report/security/report security check configrw]]

File bank

2011-03-16T15:51:35Z

Fox: French link

{{Moodle 2.0}}
The file bank is the new Moodle 2.0 file repository system.

It can use a feature called the file picker to select existing files from 2 areas (Server and Private files), or a temporary area(Recent files) and an option to upload a new file.

The file picker has 2 basic views when looking at an area: Icon or List. The list view is similar to a directory tree, that can collapse directories/folders, or expand directories/folders to show their files still in the tree format. The icon view shows files and folders as thumbnails icons, the users clicks on the icon to drill down or to select the file. A breadcrumb indicates the current location in the directory tree.

The upload a file window has a browse selection feature, plus a field to rename a file, the picking author's name and the type of license that is stored when the "Upload this file" button is selected.

==Pre Moodle 2.0 description of file system==
In earlier versions, files were stored via an interface link in the course administration menu called "Files". Generally speaking, files and folders in a course, were only available in that course. (Site administrators knew that these files and folders were located in [[Moodledata directory]]).

In Moodle 2.0, files are stored and accessed via a link with the resource or activity in the course.

==See also==
*[[Course files]] - concept of pre 2.0 and 2.0 system
*[[File picker]] - used to add resource files.
*[[HTML editor 2.0]] - Insert group for images and media files
*[[Repositories]] - different media files

[[Category:Teacher]] [[Category:Files]] [[Category:Moodle 2.0]]

[[fr:Banque de fichiers]]

File handling

2011-03-16T15:45:37Z

Fox: French link

{{Moodle 2.0}}The way files are handled in Moodle 2.0 has changed from earlier versions. Students and teachers will use the [[File picker]] to upload and organize their files in areas called [[Repositories]]. Repositories can be located on the Moodle site or externally. Site administrators can [[Manage repositories|reveal, restrict, add, edit or create repositories]] for the site.

* Previously, if a file was used in different courses, it was duplicated. In Moodle 2.0, files are stored only once, saving disk space.
* Full support for Unicode file names on all operating systems.
* Metadata about each file (author, date, license, etc) and what the file is used for are stored in the database.
* Files are no longer just "uploaded to the course". Files are connected to the particular bit of Moodle content that uses them. (For example, a file may belong to a file resource, a forum post or a wiki page). Access to these files is controlled by the same [[Context|contextual]] [[Roles and capabilities|rules]] as as that bit of Moodle, increasing security.
* File picker has a list (file tree) or icon view

A video on file handling in Moodle 2.0:

<mediaplayer>http://www.youtube.com/watch?v=2bUwx675Pqo</mediaplayer>
== Typical Moodle 2.0 workflow ==
Edit text or activity. Use the file picker to easily select the file from any local or remote repository. The file is then copied to Moodle and stored securely with the text or activity.

Or Edit text or url resource. Use the file picker to select a file from any local or remote repository and select "link". The file URL is then embedded into the text and when viewed, the media comes directly from the open repository.

The standard Moodle install has 4 default areas (repositories) displayed in file picker for the teacher to select:
*Server -
*Recent -
*Upload -
*[[Private files]]

The site administrator can expand the above list to include 15 other predefined repository areas. For example, the teacher may see a file picker link to a Google Docs or UTube repositories where they can find files. As in the previous versions, the teacher can create a folder structure to store the files at the time files are uploaded.

==FAQ==
Caveat: these are just making a start on these. Subject to quality, style and accuracy improvements.

===What are ways to make files available to other teachers/designers?===
In Moodle 2, this is going to require a change of habits. Some of the philosophy is written up in a small essay on course files [[Course_files|here]]

One approach is to use a [[Repositories| repository]]. One of the easiest to set up is a [[File_system_repository_configuration|File System Repository]]

This needs server access. One such example:

[[Image:Repository-filesystem-filepicker.png]]

===What are ways to make ONE change in a file and have this reflected across a Moodle site?===
This also will require a change in thinking. You cannot just go to the file in the file picker and change it's name or upload a new file. This would cause problems if it was linked to elsewhere.

One answer is again to use repositories. '''Link''' to the files in the repository. Change the files (according to the permissions on the repository) and this is reflected everywhere int he course instantly.

==See also==
* [http://www.youtube.com/watch?v=JtePGeffl3o&feature=player_embedded Video: How teachers can upload files in Moodle 2.0]
* [[Course files]]
* [[Development:File API]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=160067 File Manager In Moodle 2.0] forum discussion

[[Category:Files]]

[[de:Dateiverwaltung in Moodle 2.0]]
[[fr:Gestion des fichiers 2.0]]

File picker

2011-03-16T15:24:51Z

Fox: French link

{{Moodle 2.0}} {{Update}}
File Picker is the standard interface that most users will use to manage a Moodle 2.0 file repository. See [[Manage repositories]]
*Select an area ([[Repositories|a repository)]] to find the file and/or to add a file that can then be selected
**Server files - files on the site. What you see here depends on your role in the course.
**Recent files - files Moodle thinks you have recently added
**Upload files - This is where you click to upload files and folders from your computer
**[[Private files]] - files that belong to the user
*Use the standard add file- create folder interface
*Save selected files

[[Image:Files_File-Picker_standard_blank_1.png|thumb|center|Empty file picker, no input area selected ]]

==Standard add file - create folder option==
When the Resource of a Folder is selected in a course, in file picker, a standard pop-up will ask you for:
*Add (a file)- selecting this will take you to the add attachment and browse popup.
*Create a folder
*Download all files
[[Image:Files_standard_add_create_folder_with_folder-file_1.png|frame|center|Existing files and a folder ready to be added]]

==Standard browse to add file popup==
The file picker will present a screen to select a file. For example, when "Upload file" is selected, but also when you select add an image in the [[HTML editor]], you will see the file picker and the "Upload file" link. The standard add a file popup will ask you:
*Attachment - Browse. This is where you find the file
*Save as - Allows changing the name of the file. This is optional. If you do use this, you must include the extension.
*Author - the default is the current user
*Choose license - a pull down menu with different licenses to select.
[[Image:Files standard add file screen 1.png|thumb|center|After a browse to a file on the C: drive]]

== Views in file picker ==
===View as icons===
[[Image:Files File picker server files icons 1.png|thumb|center|Server files at demo.moodle.net in icon form, shows breadcrumb]]

===View as list===
[[Image:Files File picker server files list collapsed 1.png|thumb|center|Server files at demo.moodle.net in list form, folders collapsed]]

==See also==
[[File picker FAQ]]

[[Category:Files]]

[[eu:Fitxategi-hautatzailea]]
[[fr:Sélecteur de fichiers]]

Talk:Updates

2011-02-11T13:00:36Z

Fox: Proposition for a better french name for this page

Nice and usefull page. Could you please add french link to "Dates de fin de support", and correct Moodle 1.6 release date to "20 June 2006". --[[User:Séverin Terrier|Séverin Terrier]] 09:18, 9 February 2011 (UTC)

:Done, thanks Séverin. --[[User:Helen Foster|Helen Foster]] 09:33, 9 February 2011 (UTC)

:: About french name : Martin wants a page title that matches the original. I think we could use "Dernières mises à jours officielles" or "Dernières mises à jour". In french, we already have "Mise à jour" (Upgrading) and i think it would be confusing to just have "Mises à jour" as translation for this page. --[[User:Séverin Terrier|Séverin Terrier]] 13:00, 11 February 2011 (UTC)

2.1 update on June 31 is problematic. Perhaps June 30? ;)

:I think it's peeeeerfect, lol. --[[User:Eloy Lafuente (stronk7)|Eloy Lafuente (stronk7)]] 18:37, 9 February 2011 (UTC)

Development:Stable branch support

2011-02-10T10:25:44Z

Fox: This page should be updated

{{Update}}
{{Template:Work_in_progress}}

Unfortunately it's not possible to continue to provide support for older stable branches of Moodle indefinitely due to the amount of work involved. This page describes the process of dropping support for older stable branches.

==Dropping support for 1.a.x==

# Decide upon the final release of 1.a.x (taking into account that generally three versions are supported at a given time)
# Propose a date in MDLSITE-737 for dropping support for 1.a.x 5 months after the final release
# Announce the final release of 1.a.x in the moodle.org news
# Document the final release of 1.a.x in the [[:Category:Release_notes|release notes]]
# Update the Moodle version message in the tracker to read: "There will not be another 1.a.x release, but critical bugs may still be backported to the branch until [''date 5 months in advance'']." (both for the [http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10011 Moodle Project] and the [http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10033 Non-core contributed modules project]).
# After 5 months, release 1.a.x+ and archive all 1.a.x versions, closing the stable version in the tracker (also in both projects).

==Dropping support for 1.6.x==

# Proposed date for dropping support for 1.6.x: 31 July 2009
# Announcement: [http://moodle.org/mod/forum/discuss.php?d=115616 New releases: Moodle 1.9.4, 1.8.8, 1.7.7 and 1.6.9]
# 1.6.9+ released and 1.6.x versions archived on 31 July 2009. 16_STABLE closed in the tracker.

==Dropping support for 1.7.x==

# Proposed date for dropping support for 1.6.x: 31 October 2009
# Announcement: [http://moodle.org/mod/forum/discuss.php?d=115616 New releases: Moodle 1.9.4, 1.8.8, 1.7.7 and 1.6.9]
# 1.7.7+ released and 1.7.x versions archived on 31 October 2009. 17_STABLE closed in the tracker.

==Dropping support for 1.8.x==

See MDLSITE-737 for tentative dates

==See also==

* MDLSITE-737 Drop support for 1.6.x and 1.7.x versions in the Tracker
* [[Updates]]

[[Category:Processes|Stable branch support]]

Talk:Updates

2011-02-09T09:18:39Z

Fox: Please add french link

Converting your MySQL database to UTF8

2011-01-19T15:18:59Z

Fox:

This document describes how to convert your MySQL database from the latin1 charset to UTF8. Moodle requires that your Database is now UTF8 and will not upgrade if your database is not.

For more information about UTF8 have a look at the doc on [[Unicode|unicode]].

==Why?==

You may see the following error when upgrading your Moodle.

''It is required that you store all your data in Unicode format (UTF-8). New installations must be performed into databases that have their default character set as Unicode. If you are upgrading, you should perform the UTF-8 migration process (see the Admin page).''

Moodle requires UTF8 in order to provide better multilingual support and has done since Moodle 1.8. However the UTF8 check during install and upgrade was only been implemented in Moodle 2.0 and you may find you are unable to upgrade because your database was not set up correctly when you first installed Moodle or because you have been running Moodle since before 1.8 and haven't previously converted your database.

==Converting an empty database==
If you have created your database schema and are receiving the error during your initial installation your Moodle database will still be empty. You can simply run the below query in your database to resolve the issue.
<code sql>
alter database mydatabasename charset=utf8;
</code>

==Converting a database containing tables==
If you have previously installed Moodle and are now getting the error the following process will allow you to convert your database.

===Linux & Mac===
<code bash>
mysqldump -uusername -ppassword -c -e --default-character-set=utf8 --single-transaction --skip-set-charset --add-drop-database -B dbname > dump.sql
cp dump.sql dump-fixed.sql
vim dump-fixed.sql
:%s/DEFAULT CHARACTER SET latin1/DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci/
:%s/DEFAULT CHARSET=latin1/DEFAULT CHARSET=utf8/
:wq
mysql -uusername -ppassword < dump-fixed.sql
</code>

or alternatively using sed:
<code bash>
# $1-dbusername $2-password $3-dbname
mysqldump -u$1 -p$2 -c -e --default-character-set=utf8 --single-transaction --skip-set-charset --add-drop-database -B $3 > dump.sql
sed 's/DEFAULT CHARACTER SET latin1/DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci/' <dump.sql | sed 's/DEFAULT CHARSET=latin1/DEFAULT CHARSET=utf8/' >dump-fixed.sql
mysql -u$1 -p$2 < dump-fixed.sql
</code>

====Explained====
The following steps will guide you in creating a database dumb, editing the database dump so that the correct charset and collation are used and then restoring the new database.

To start please open a new terminal and move to a temp directory.

<code bash>
mysqldump -uusername -ppassword -c -e --default-character-set=utf8 --single-transaction --skip-set-charset --add-drop-database -B dbname > dump.sql
</code>

The first step is of course to dump out the database and of course we will use mysqldump for this. We do however need to set several arguments in order to clean up the charsets and provide a dump that is not going to cause you any problems if you are moving this database to a different database server or find yourself having to restore on a reverted system.

; username : The username to access your database.
; password : The password for the above user.
; -c : Complete inserts for better compatibility.
; -e : Extended inserts for better performance.
; --default-character-set=utf8 : To set the default character set.
; --single-transaction : To reduce our workload if anything goes wrong.
; --skip-set-charset : Obviously not wanted or needed as we are changing it anyway.
; --add-drop-database : Required so we can restore over the top of our existing database.
; -B : We use this option so that our dump will contain drop table and create table syntax (which we will change the syntax for).
; dbname : The name of the database to convert.

When you run this command a database dump will be generated into '''dump.sql'''

<code bash>
cp dump.sql dump-fixed.sql
</code>
Next step is to copy dump.sql to dump-fixed.sql.

We will make the desired changes within dump-fixed.sql and we will keep dump.sql as it is as a backup just in case.

<code bash>
vim dump-fixed.sql
:%s/DEFAULT CHARACTER SET latin1/DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci/
:%s/DEFAULT CHARSET=latin1/DEFAULT CHARSET=utf8/
:wq
</code>
Now we need to edit the dump and correct the incorrect charsets that have been used. I have chosen to do this with VIM however you can use any search+replace editor or program. ( I choose VIM for this only because every linux user is/should be familiar with it).

First we open the file using VIM, and then run the three commands.

The first command replaces all instances of ''DEFAULT CHARACTER SET latin1'' with ''DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci''. This is used to fix up the database's default charset and collation.

The second command replaces all instances of ''DEFAULT CHARSET=latin1'' with ''DEFAULT CHARSET=utf8''. This converts all tables from using latin1 to using UTF8.

The third command simply saves it and exits.

<code bash>
mysql -uusername -ppassword < dump-fixed.sql
</code>
Now that we've made the required changes we simply need to restore the database over top of the existing database. We can do this by running the above command.

===Windows===
Could someone who is familiar with Windows please convert the above into something that will work on Windows?
There are likely several additional arguments for mysqldump you will need to specify including setting the file for output using -r to avoid newline issues.

==More information==
* [[Unicode]]

[[Category:UTF-8]]
[[Category:DB]]
[[Category:SQL_databases]]

[[fr:Convertir votre base MySQL en UTF-8]]

AMOS

2011-01-17T11:04:30Z

Fox: French link

{{Moodle 2.0}}

'''AMOS stands for Automated Manipulation Of Strings. AMOS is a central repository of Moodle strings and their history. It tracks the addition of English strings into Moodle code, gathers translations, handles common translation tasks and generates language packages to be deployed on Moodle servers.'''

The name was chosen in honour of [http://en.wikipedia.org/wiki/John_Amos_Comenius John Amos Comenius], the author of ''Janua linguarum reserata'' (Gate to Languages Unlocked). Sorry Tori ;-)

AMOS is installed at http://lang.moodle.org. If you want to use it, please create an account there. Language pack [[Translation_credits|maintainers]] should then send an email to [mailto:translation@moodle.org translation@moodle.org] (Koen) to get write access for their language.

AMOS provides support for community contributions into the translation. If you want to participate, just create an account at http://lang.moodle.org. There is no need to contact us in this case but you should definitely contact the language maintainer and coordinate your work.

== Basic concepts ==

[[image:amos-screenshot-navigation.png|100px|thumb|right|AMOS tools in the navigation block]]
AMOS consists of several tools available via the main navigation block - Translator, Stage, Stashes, Contributions and Log.

* User - AMOS is used by languages pack maintainers and by the community members who want to contribute
* Translator - is a tool that allows you to filter strings you want to work on and translate them
* Stage - is a temporary working area that holds the strings you have translated during the current session. Maintainers can permanently commit the stage into the strings repository. Contributors can submit the stage for maintainers.
* Stashes - are snapshots of the stage. Imagine them as ordinary files at your computer where you can save your work. You can submit your stash to the language pack maintainers.
* Contributions - is a database tracking all submitted contributions and their current status. Records in this database are like issues in Moodle tracker with the translated strings attached.
* Repository - a database of all Moodle strings and their history running at lang.moodle.org server
* Log - displays the log of all modifications of Moodle strings.

== Translation workflow ==

The following data flow diagram illustrates how AMOS tools are used during the translation process.

[[image:amos-workflow.png]]

The key AMOS component is the staging area or shortly the stage. It holds translated strings temporarily during your current login session. If you log out, the stage is cleared (though there is a backup - see below). There are several ways how translations can be staged, that is how translated strings can be put into the stage:

* by using AMOS translator
* by importing strings from an uploaded file
* by applying a previously created stash
* by applying a submitted contribution

Language pack maintainers have write access into the AMOS strings repository. Therefore they can commit their stage permanently. Once the stage is committed, staged strings are stored in the AMOS repository. Every hour at xx:45, AMOS generates ZIP packages from the most recent snapshot of the repository. These ZIP packages are published at http://download.moodle.org/langpack/2.0/ for download. Moodle sites can install and update language packages automatically from the ''Site administration > Language > Language packs'' page.

Community members do not have write access into the repository so they can't commit their stage. Instead, they can submit it to the maintainers. By submitting a stage, a new contribution record is created and language pack maintainers are notified by automatic email message. Maintainers can review the submitted contribution and, if they accept it, commit it on behalf of the contributor.

The stage can be also saved so you can interrupt your work and continue next time you come back to the site. The stage is saved into so called stashing area. Stashing area consists of stashes. A new stash is nothing but a snapshot copy of your current stage. AMOS automatically keeps one stash for you as a backup copy of your most recent stage. A stash can be submitted to the maintainers, too.

== AMOS tools ==

=== Using the translator tool ===

[[image:amos-screenshot-translator.png|300px|thumb|right|AMOS Translator tool]]
The translator tool page has two main parts. At the top, there is a filter form (1). You use that filter to get the strings you want to translate. When the filter settings are saved (2), a table with the filtered strings is displayed below.

Every row in the table represents a single string. The table has four columns. The first column (3) describes the version (or branch) where the string is used, its identifier and its component. You can see a text like

2.0 [completiondate,coursereport_completion]

That reads: this string is used in Moodle 2.0, its identifier is 'completiondate' and it belongs to 'courserepor_completion' component.

The second column (4) contains the English original of the string. Below the text, you can see Google icon. Click that icon to get automatic translation of the string into the language being translated. The next column contains a code of the language that this string is being translated to (for example "cs" for Czech).

Finally the last column contains the translation itself. If it is empty, the string is not translated yet, otherwise it displays the current translation. '''Click in the cell to turn it into the input editor.''' Insert the translation and click outside the cell to stage the translation. Note there is no submit button, the text is sent to the stage automatically in the background. You can see that the colour of the cell turned blue. Blue colour signalizes that the translation is currently staged.

You have many options of how to use the strings filter. You can work on a single component or all missing strings at once. You can search for strings containing a given text (either in English or the translated string) etc. You can check for strings in older versions, too but those strings are read-only. They get automatically pulled into AMOS from the CVS repository of 1.x translations.

The 'permalink' below the filter's submit button can be used to keep the current filter settings. For example, you can bookmark a setting use regularly or you can copy the link URL and send it to somebody so they can set their filter just by visiting that URL.

When you finish translating, do not forget to visit the stage page. You probably want either commit it (if you are a lang pack maintainer) or submit it to maintainers so they can review your work and include it into the language pack.

=== Using the stage ===

[[image:amos-screenshot-stage-contrib.png|300px|thumb|right|Strings staged by a contributor]]
The translated strings are put into a temporary area called ''stage'' immediately after the cursor leaves the editor field. The stage holds your work before it is either committed into the repository (if you are language pack maintainer) or submitted to the maintainers for inclusion or stashed.

The stage is cleared when you logout. You have to explicitly commit or stash the stage so it is saved permanently. If you forget to do it, or there is a problem with the connectivity, your browser crashes or whatever, you can find your most recent snapshot of the stage in autosave stash.

If you are language pack maintainer, you can commit the stage into the repository so your work is registered and the translated strings become part of the official language package. Language packages in ZIP format are generated every hour (at xx:45) and are published at http://download.moodle.org/langpack/2.0/. At the same time, they become available for Moodle sites for automatic update.

=== Importing a file ===

[[image:amos-screenshot-stage-empty.png|300px|thumb|right|Empty stage allows you to import strings from a file]]
Strings can be translated offline and uploaded back to AMOS. The only supported format at the moment is common PHP format used by Moodle where strings are defined in associative array called $string. For obvious security reasons, AMOS can not actually execute PHP files uploaded by users. Instead, it parses the uploaded file in a similar way as PHP parser, looking for patterns that are considered as valid string definition. That means that not every valid PHP code is valid string definition. AMOS parser requires following conditions are met:

* the filename is valid component name used by Moodle, for example moodle.php, enrol_manual.php or workshop.php
* the file is valid PHP code without syntax errors - that means is passes the PHP lint check
* strings are defined as elements of global array $string
* strings are single quoted constants

Example of a valid file to import into AMOS (filename countries.php, Czech translation)

<?php

$string['AE'] = 'Spojené Arabské emiráty';
$string['AF'] = 'Afghánistán';
$string['CH'] = 'Švýcarsko';
$string['HU'] = 'Maďarsko';

?>

During the import, strings found in the file are added into your stage as if they were translated via web. You can commit them into repository if you have such privilege.

=== Using stashes ===

At any moment, you can save a snapshot of the current stage. We call such snapshot a ''stash''. Stashed strings are kept forever until you drop them manually (please do not abuse this and keep your stashes reasonable big). The stash can be ''applied'' so that the stashed strings are copied back to the stage.

There is one special stash record for every user called autosave stash. This stash keeps the most recent state of the stage. You may find it useful if you loose the current stage for any reason - your browser crashes, your internet connectivity dies or you accidentally unstage all strings. If that happens, just apply the autosave stash to get your work back. The autosave stash is updated every time you stage a string. So if your stage is empty and your autosave stash is full of strings and you go into the translator first without applying the stash, the autosave will be replaced with the new translated string. We recommend to experiment a bit with this feature first.

=== Using the log tool ===

The Log page allows even anonymous users to search in the history of commits tracked by AMOS. At the top of the page there is a filter that allows you to look for a particular information or report. It is important to realize how the filter actually works. Searching and filtering happens in two steps (this was necessary for performance reasons):

* Firstly, commit records are searched based on the criteria specified in the Commit filter form. If there are more commits found matching the filter settings, only 100 most recent commits are processed.
* Then, within the commits found, either all string modification records are returned, or you can filter these records, too. Settings in String filter form section are used in that case.

By default, the filter looks for all commits since the last time you logged in and than displays only strings at the currently translated branch modified by those commits.

== Contributing to a language pack ==

AMOS allows community members to help with the translation of Moodle strings. AMOS Contributions page tracks all submitted translations and their current status. Before you start working on a translation, please communicate with the language pack maintainer (to be found on https://docs.moodle.org/en/Translation_credits).

=== Steps for the contributor ===

[[image:amos-screenshot-contribution-new.png|300px|thumb|right|Submitting a contribution form]]
# Contact the language pack maintainer about your intention to contribute to the language pack
# Use AMOS translator interface to translate missing strings or amend the current translation
# Go to the Stage page
# Click 'Submit to maintainers' button
# At 'Submitting a contribution' page, please provide a message for maintainers describing your work and why you would like to see your contribution included. You can cancel the submission at this moment yet. If you are sure, click 'Submit to maintainers'.
# Your stage will submitted into the contributions database. If there were more languages affected by your contribution, the stage will be divided into separate contribution records, one per each language. The language pack maintainers will be notified by email about your new contribution.
# Language pack maintainers will be able to apply your work into their stage, review it and eventually commit. You will receive automatically generated email when the status of contribution changes (typically when a maintainer starts a review of your work and then when they accept or reject it).
# Use contribution record comments for further communication with the maintainer about the submitted translation.

=== Steps for the maintainer ===

[[image:amos-screenshot-contribution-details.png|300px|thumb|right|Contribution details page]]
# When a user submits new contribution, you will receive automatically generated email from AMOS
# Go to the Contributions page to see a list of all new incoming contributions. Click the link in the table to open the contribution details page
# Press 'Start review' button. That will assign the contribution to yourself, change the status from 'New' to 'In review', send automatically generated email to the contributor and will copy the submitted strings into your stage. You should check that your stage is empty before you apply the submitted strings, unless you want to merge several contributions into one commit.
# Review the submitted strings, eventually edit them. Commit the stage. It is nice to mention the contributor's name in the commit message and attribute the original authorship to them.
# Go back to the contribution record and change the status to Accepted or Rejected. Automatically generated email will be sent to the contributor whenever you change the status.
# Use contribution record comments for further communication with the contributor about the submitted translation.
# Accepted and Rejected contributions are not shown at the contributions page unless you press 'Show resolved contributions' button.

== See also ==

* [[Translation 2.0]] for more information about the process of Moodle 2.x translation
* [[Development:Languages/AMOS]] for the AMOS internals documentation

[[Category:Language]]

[[fr:AMOS]]

Upgrading to Moodle 2.0

2011-01-17T10:20:40Z

Fox: Just moving some elements

{{Moodle 2.0}}When upgrading to Moodle 2.0, you must have Moodle 1.9 or later. if you are using an earlier version of Moodle (eg 1.8.x) then you need to upgrade to Moodle 1.9.x first.

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect. Moodle 2.0 is a substantial upgrade and may require more planning and testing than you have become accustomed to in prior upgrades. Please read this page carefully before proceeding.'''

==System requirements==

* PHP must be '''5.2.8 or later''' although the latest 5.3.x is better if you have a choice.
* Databases should be one of the following:
** MySQL 5.0.25 or later (InnoDB storage engine highly recommended)
** PostgreSQL 8.3 or later
** Oracle 10.2 or later
** MS SQL 2005 or later
* Any standards-supporting browser from the past few years, for example:
** Firefox 3 or later
** Safari 3 or later
** Google Chrome 4 or later
** Opera 9 or later
** MS Internet Explorer 7 or later (Even [http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html Google does not support IE6 any more])

==Before upgrading please... ==

'''NOTE''': The upgrade process will irreversibly modify the contents of your database '''and''' your moodledata file storage area. If something goes wrong you '''cannot''' go back. It is vital that you take good backups of both moodledata and the database in case you have problems with the upgrade. If you are not sure how see [[Site backup]] or ask in the moodle.org forums (explaining what your operating system is).

* It's a good idea to read the [[Latest release notes]] and the [[Moodle 2.0 release notes]]
* Always check your site to make sure it meets all system requirements for 2.0 in ''Administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* '''Do a full moodledata backup'''
* '''Check your backups carefully'''
* Remember to purge PHP cache if using any PHP accelerator

==A word about optional plugins and themes==

If you have added optional or customised plugins (whether your own custom developments or from the plugins and modules database) or are using a non-core theme you must note that these will '''not''' work in Moodle 2.0+. While some plugins have been modified to work in Moodle 2.0+ at the time of writing most have not. The themes system is completely different in 2.0+ and all custom themes will require a complete rewrite.

Do not try to include any (old 1.9) optional plugins and themes in your Moodle 2.0 - it won't work. You should check to see if a 2.0 version is available. If not, you can safely ignore the message that the code is missing for the plugin during the upgrade. You will loose the functionality but the database tables will be retained (dormant) in case a 2.0 version of the plugin is produced in the future.

==Checking database schema - old sites==

If your 1.9 Moodle site has been upgraded through many prior versions it is quite likely that there will be some problems with the database schema (compared to a fresh 1.9 installation). This may cause the upgrade to fail. If your site started life prior to Moodle 1.9 it is a very good idea to check and correct the database schema before upgrading. See [[Verify Database Schema]]

==Now upgrade==

Once you have satisfied the requirements for Moodle 2.0, follow the instructions on the [[Upgrading|upgrading]] page.

Moodle 2.0 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.

== Known and Discovered Issues ==

* Note, if you get a strange error about 'handling of PHP float numbers', please see [[Installation_FAQ#Moodle_claims_PHP_float_handling_is_not_compatible|this FAQ entry]].
* You now need some additional PHP modules installed (e.g. intl and the zip extension). If you do not have these, installation depends entirely on how your PHP was first installed and your operating system.

==See also==

*[[Moodle 2.0 release notes]]

*[[:Category:Moodle 2.0]]

[[Category:Installation]]

[[de:Auf Moodle 2.0 aktualisieren]]
[[fr:Mise à jour à Moodle 2.0]]

Capabilities/moodle/course:create

2011-01-17T09:27:29Z

Fox: French link

*This allows a user to create courses
*This permission only applies to system roles or roles assigned in the course category context and would not apply if a user is assigned a role with this permission in the course context

====Legacy Role Default Settings====
{| border="1" cellspacing="0" cellpadding="2"
|-
! Legacy Role !! Inherit !! Allow !! Prevent !! Prohibit
|-
| Administrator || - || X || - || -
|-
| Course Creator || - || X || - || -
|-
| Teacher || X || - || - || -
|-
| Non-editing Teacher || X || - || - || -
|-
| Student || X || - || - || -
|-
| Guest || X || - || - || -
|-
| Authenticated User || X || - || - || -
|}

[[Category:Capabilities|Course]]

[[eu:Capabilities/moodle/course:create]]
[[fr:Capabilities/moodle/course:create]]

Course settings

2011-01-03T11:06:54Z

Fox: French link

{{Course admin}}

[[Image:Settings.gif]]'''Course settings''' control how the things appear to the participants in a course. It is the first page viewed after creating a course. It can be edited through the '''Settings''' link in the [[Course administration block]] menu. This page has links to other pages that may describe a setting in more detail. Different versions of Moodle may not have all the settings listed below.

The Moodle 2.0 interface will look slightly different but will contain all the features of 1.9, plus the new course completion tracking feature (if it has been enabled.)

==General==
[[Image:generalsettings1.gif|thumb|General settings]]
===Category===

The site administrator may have created course categories to help teachers and students find their courses easily.

The capability [[Capabilities/moodle/course:changecategory|moodle/course:changecategory]] controls whether a user can edit the course category.

===Short name===
Many institutions have a shorthand way of referring to a course, such as BP102 or COMMS. Even if you do not already have such a name for your course, make one up here. It will be used in several places where the long name is not appropriate. The most common use is in the navigation bar that is at the top of most pages and this provides an active link to the course home page.

[[Image:Assignment nav trail.jpg|Point to Assignment, part of the Features course, in a site called Moodle]]

The above example has the short course name, "Features", in the navigation links (breadcrumb). The short name also appears in the subject line of email messages that are part of the course.

The capability [[Capabilities/moodle/course:changeshortname|moodle/course:changeshortname]] controls whether a user can edit the short name field.

===ID number===
The ID number is an alphanumeric field. It has several potential uses. Generally, it is not displayed to students. However, it can be used to match this course against an external system's ID, as your course catalog ID or can be used in the certificate module as a printed field.

The capability [[Capabilities/moodle/course:changeidnumber|moodle/course:changeidnumber]] controls whether a user can edit the ID number.

===Summary===

The summary appears on the course listings page.

The capability [[Capabilities/moodle/course:changesummary|moodle/course:changesummary]] controls whether a user can edit the course summary.

===Format===
[[Image:generalsettings3.gif|thumb|Format section in course settings]]
See [[Course formats]]

===Number of weeks/topics===
This setting is only used by the 'weekly' and 'topics' course formats. In the 'weekly' format, it specifies the number of weeks that the course will run for, starting from the course starting date. In the 'topics' format, it specifies the number of topics in the course. Both of these translate to the number of "boxes" down the middle of the course page.

[[#top|Top]]

===Course start date===
This is where you specify the starting time of the course (in your own time zone). The first week will start on the date you set here when you use the "Weekly" course format.

This setting will not affect courses using the 'social' or 'topics' formats.

However, this setting will have an effect on the display of logs, which use this date as the earliest possible date you can display. It can also make your course not visible to students even if when the course is available to students (see below).

:''TIP:'' If your institution runs on a weekly schedule, you may want to consider setting the start date for courses on the first day of the week, like a Monday.

:''TIP:'' In general, if your course does not have a real starting date then set the date to yesterday and use the availability setting to reveal the course to students.

===Hidden sections===
This option allows you to decide how the hidden sections in your course are displayed to students. By default, a small area is shown (in collapsed form, usually gray) to indicate where the hidden section is, though they still cannot actually see the hidden activities and texts. This is particularly useful in the Weekly format, so that non-class weeks are clear, or if you have quizes you don't want your students to see.

:''TIP:'' If you choose, these non-available items can be completely hidden, so that students do not even know that sections or an activity in the course are hidden.

[[#top|Top]]

===Show grades===
Many of the activities allow [[Grades|grades]] to be set. By default, the results of all grades within the course can be seen in the Grades page, available from the main course page for students and teachers.

:''TIP:'' If a teacher is not interested in using grades in a course, or just wants to hide grades from students, then they can disable the display of grades with this option. This does not prevent the teacher using or setting grades for an individual activities, it just disables the results from being displayed to students.

===Show activity reports===
[[Activity_report#Individual_Activity_Report|Activity reports]] are available to each student. These reports or logs show their activity and contributions in the current course. These reports include their detailed access log.

Student access to their own reports is controlled by the teacher via this course setting. For some courses, these reports can be a useful tool for a student to reflect on their involvement and appearance within the online environment, but for some courses, this may not be necessary.

Teachers always have access to these reports. Teachers can use the button or tab visible on each person’s profile page or use the [[Reports]] link in the course administration block.

Your site administrator may ask you to turn this feature off. Showing activity reports can place a load on the server, slowing it down at times. For large or long classes it may be more efficient to keep it off.

[[#top|Top]]

===Maximum upload size===
[[Image:Changeupload.jpg|thumb|Maximum upload size setting]]
This setting defines the largest size of file that can be uploaded by students in this course. The site administrator can determine [[Site_policies#Maximum_uploaded_file_sizefile |sizes available]] for the teacher to select. Teachers should be aware of a course's [[Files|file structure]].

It is possible to further restrict this size through settings within each activity module.

===Force theme===
If the site administrator has allowed the teacher to set a course [[Themes|theme]], this pull down menu will appear with a list of themes on the site.

===Is this a meta course?===
A [[Metacourses|metacourse]] only gets its student enrolments from one or more other courses. Students can not be enrolled directly in this kind of course. A metacourse creates a virtual family of related courses. There are [[Metacourse examples of use|many uses for a metacourse]].

[[#top|Top]]

==Enrolments==
[[Image:generalsetting4.gif|thumb|Enrolment settings]]
===Enrolment plugins===
This setting allows you to choose an interactive [[Enrolment plugins|enrolment plugin]], such as [[Internal enrolment|internal enrolment]] or [[Paypal]]. If you use a non-interactive enrolment plugin, this setting has no effect.

===Default role===

From Moodle 1.7 onwards, a default course role, such as student, may be set.

===Course enrollable===
This setting only affects interactive enrolment plugins, such as [[Internal enrolment|internal enrolment]] and [[Paypal]]. It has no affect at all on non-interactive plugins (e.g. External Database, LDAP). Setting it to "no" or if it is outside the specified date range will result in the student being told the course is "Not enrollable" and being returned to the front page, if they are attempting to enrol using an interactive plugin.

:''TIP:'' If you are using Internal enrolment and you have not set an enrolment key, you should seriously consider setting this to ''No'' otherwise any user can enrol on your course.

[[#top|Top]]
===Enrolment duration===
This setting specifies the number of days a student can be enrolled in this course (starting from the moment they enrol). Set this value with care - setting it when not required is a common origin of the complaint, "my students keep disappearing after n days".

:''TIP:'' This is useful for rolling courses without a specific start or end time. Students are automatically unenrolled after the number of days has expired in this setting.

:''TIP:'' This setting can be used as an alternative to a manually unenrolling students or using a clean-up function to remove defunct students at some future time.
:''TIP:'' If this course is a metacourse, the enrolment period will not be used.

==Enrolment expiry notification==
[[Image:generalsettings5.gif|thumb|Enrolment expiry notification settings]]
These settings determine whether teachers and/or students are notified that their enrolment is about to expire and how much notice they should be given.

[[#top|Top]]
==Groups==
[[Image:generalsettings6.gif|thumb|Groups settings]]
===Group mode===
Here you can define the [[Groups|group mode]] at the course level by a pull down menu. "[[Groups#No_groups|No groups]]", "[[Groups#Separate_groups|Separate groups]]" and "[[Groups#Visible_groups|Visible groups]]" are the choices. The selected setting will be the default group mode for all activities defined within that course. The group setting can affect what users see in the [[Participants]] list.

:''TIP:'' You may leave it set to "No groups" and still have specific activities use groups. In this case the force setting below should be set to "no". For example, the teacher can use a group setting to completely separate cohorts of students such that each group is unaware of the other in the course.

===Force===
If the group mode is "forced" at a course-level, then this particular group mode will be applied to every activity in that course. This will override any activities that may have a special group setting.

:''TIP:''The force setting is useful when the teacher wants to set up a course and not have to change each activities group settings.

[[#top|Top]]
===Default grouping===

{{Moodle 1.9}}If [[Groupings|groupings]] are enabled (in Moodle 1.9 onwards), a default grouping for course activities and resources may be set.

==Availability==

[[Image:generalsettings7.gif|thumb|Availability settings]]
This option allows you to "hide" your course completely. It will not appear on any course listings, except to teachers of the course and administrators. Even if students try to access the course URL directly, they will not be allowed to enter.

:''TIP:'' The [[Course_settings#Course_start_date|Start Date]] of the course can also effect course visibility.

[[#top|Top]]
===Enrolment key===
A course [[Enrolment key|enrolment key]] enables access to courses to be restricted to those who know the key. This feature is typically used on sites which encourage self enrolments or use an external database process to register students in a course. The idea is that Teachers or course administrators will supply the key to authorized people using another means like private email, snail mail, on the phone or even verbally in a face-to-face class.

When the key is left blank and [[Course_settings#Course_enrollable|self enrolment]] is allowed, then anyone who has a Moodle username on the site will be able to enrol in the course.

:''TIP:'' A student can be manually enroled in the course and will not have to supply the required key when they enter the course for the first time.

:''TIP:'' If this password "gets out" and you have unwanted people enrolling, you can unenrol them (see their user profile page or unassign them from the [[Assign roles|student role]] in the course) and change this key. Any legitimate students who have already enrolled will not be affected, but the unwanted people will not be able to get back in.

:''TIP:'' If you are using a non-interactive enrolment, system (e.g., External Database, LDAP) and you do not want students who fail the initial check to be asked for an enrolment key that they will not have, set ''Course Enrolable'' to ''No''.

:''TIP:'' You can control who is displayed as providing the Key when someone is requested to supply the key. See [[Internal enrolment]]

[[#top|Top]]

===Guest access===

Allows any authenticated user (i.e. logged in) to access the course (as a [[Guest role|guest]]), including those who have logged in "as guest". You can choose if they need an enrolment key or may enter without one.

People can log in as guests using the "Login as a guest" button on a login screen, where that feature is enabled for the site. When the user tries to enter a course, they will see the [[Log in|login screen]]. If you only need people authenticated via your normal authentication method to access courses (as Guest or not) it is probably wise to disable "Login as a guest" for a slight improvement in site security. See [[Manage authentication]].

Guests in a course ALWAYS have "read-only" access - meaning they cannot leave any posts or otherwise mess up the course for real students. No use information is stored for a guest.

:''TIP:'' This can be handy when you want to let a colleague in to look around at your work, or to let students see a course before they have decided to enroll.
:''TIP:'' You have a choice between two types of guest access: with the enrolment key or without. If you choose to allow guests who have the key, then the guest will need to provide the current enrolment key EVERY TIME they log in (unlike students who only need to do it once). This lets you restrict your guests. If you choose to allow guests without a key, then anyone can get straight into your course.

For more information see [[Guest role]].

[[#top|Top]]
===Cost===

If [[Paypal]] or [[Authorize.net Payment Gateway]] is set as the [[Enrolment plugins|enrolment plugin]], then the course cost can be set in the cost field.

==Language==
[[Image:generalsettings8.gif|thumb|Language settings]]

If you force a language in a course, the interface of Moodle in this course will be in this particular language, even if a student has selected a different preferred language in his/her personal profile.

==Student progress==
{{Moodle 2.0}}Has settings for [[Course completion]] criterion, a new feature in 2.0.

[[#top|Top]]

==Role renaming==
[[Image:rolesimages.gif|thumb|Role renaming settings]]
{{Moodle 1.9}}In Moodle 1.9 onwards, you can rename the [[Roles|roles]] used in your course. For example, you may wish to rename the [[Teacher role]] as "Facilitator", "Tutor" or "Guide". These new role names will appear within the course. For example on the [[Participants|participants]] and the override permissions pages.

Please note that the site administrator or a [[Course managers|course manager]] may have changed the names or added new roles. These names will appear and the teacher may rename them.

[[Roles FAQ]] contains information on changing the name for teacher in Moodle 1.7 and 1.8. Prior to Moodle 1.7, the words for teacher and student may be changed in the course settings.

:''Tip'': Do not worry about changing every role name. Only change the site roles which are used in your course. For example, you may want to ignore renaming roles such as the [[Administrator role]] or the [[Authenticated user role]].

:''Tip'': To include new role names in a course backup, users should be included in the backup.

[[#top|Top]]

==Default course settings==

An administrator can set course settings defaults in ''Administration > Courses > [[Course default settings]]'' in Moodle 1.9.5 onwards.
[[#top|Top]]

==See also==

*[http://www.youtube.com/watch?v=zWOp1oq-TvI Video showing how to create a course in Moodle]

[[Category:Course]]

[[de:Kurseinstellungen]]
[[es:Administración del curso]]
[[eu:Ikastaroaren_ezarpenak]]
[[fr:Paramètres du cours]]
[[ja:コース設定]]
[[ru:course/edit]]

Adding/editing a questionnaire

2011-01-03T10:21:32Z

Fox: French link

{{Questionnaire}}

==Timing==

Set the date window for when users can complete the questionnaire. You can leave the boxes unchecked if you want the questionnaire to be continually available.

==Response options==
===Type===

Select whether users will be allowed to respond once, daily, weekly, monthly or an unlimited number of times ('''many''').

===Respondent Type===

You can display your users' full names with each response by setting this to "fullname". You can hide your users' identities from the responses by setting this to "anonymous".

'''Note'''.- If your Moodle course allows guests, they will only be allowed to respond to a questionnaire whose responses have been set to ''anonymous''.

===Respondent Eligibility===

Decide whether everyone can answer or whether you want to restrict it to tutor only or student only responses. For restricted access options remember to assign the correct roles either at the course or activity level. For example, if you put a questionnaire on the front page, intended for teachers only, then you will have to let Moodle know which users are teachers.

===Response viewing===

You can specify who can see the responses of all respondents to submitted questionnaires (general statistics tables).

''' Students can view ALL responses -> '''

# ''' Never'''. By default, only teachers of the owning course can see all questionnaire submitted responses.
# ''' After answering the questionnaire'''. This allows students to see all responses after answering a questionnaire that is set to '''''respond once only'''''. If a questionnaire is set to respond more than once, then students cannot see all responses unless you use one of the next two options.
# ''' After the questionnaire is closed'''.
# ''' Always.'''

Please use the ''Roles and capabilities system'' to decide which course participants will be allowed to view a) their own responses b) all responses.

===Save/Resume answers===

Setting this option allows users to save their answers to a questionnaire before submitting them. Users can leave the questionnaire unfinished and resume from the save point at a later date.

'''Note''' .- If a questionnaire is set to '''Save/Resume answers''', then ''guests will not be allowed to view it''. Since there is no way for Moodle to tell one guest from another, it would not make sense for one guest to start responding to a questionnaire and another guest to finish it!

==Content Options==

Select one of the radio button options. 'Create new' is the default.

'' You can create questionnaires using three different methods: ''
:''' Create New: '''
::This option allows you to create a completely new questionnaire from scratch.
:''' Copy Existing: '''
::This option copies a pre-existing questionnaire's content to a new questionnaire, pre-seeding the content. You can copy questionnaires belonging to the course, or ones specifically marked as 'template'.
:''' Use Public: '''
::If a questionnaire has already been created (in another course on the same Moodle site) with the "public" setting, then you may use that "public" questionnaire in your own course(s). The number of settings available to such questionnaires is limited and you cannot edit its questions nor view the responses. ''''' Example '''''.- If a public questionnaire has been created in course A, it can be "used" in courses B, C, ... All the responses from courses A, B, C, ... are collected in the public questionnaire created in course A (the original course where it was created) and are viewable there by the person (admin or teacher) who originally created it.

[[Category:Teacher]]

[[fr:Ajouter/modifier un questionnaire]]

Permissions

2010-12-17T08:47:54Z

Fox: French link

{{Moodle 2.0}}Location: ''Site administration > Users > Permissions > Check system permissions'' or ''Course administration > Users > Permissions > Check permissions''
[[Image:Check permissions.png|thumb|Check permissions in a course]]
The check permissions feature provides a method to view all capabilities for a selected user based on their role assignments. These capabilities determine whether or not the selected user is allowed to perform associated tasks within the system or course.

[[Category:Roles]]

[[eu:Sistemako_baimenak_aztertu]]
[[fr:Vérifier les permissions]]

Publishing a course

2010-12-16T14:51:27Z

Fox: French link

{{Moodle 2.0}}In Moodle 2.0 onwards, users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]] can publish courses to a hub.

==Why publish a course?==
[[Image:Publication.png|thumb|Publish course page]]
Possible reasons for publishing a course include:

* To share it with the world
* To sell your course design/methodology
* To attract more participants (students, teachers...)

== Advertising a course for people to join==

# Click the button 'Advertise this course for people to join'.
# Select the hub where you want to advertise your course.
# Enter information about the course.
# Click the 'Advertise this course' button.

The course will then need to be approved by the hub administrator before it appears in the course listing.

The advert for the course may be updated or removed at any time by clicking an appropriate button in the actions column.

==Sharing a course for people to download==
[[Image:Backup_publication.png|thumb|First page of the backup process]]

# Click the button 'Share this course for people to download'.
# Select the hub where you want to share your course.
# Enter information about the course.
# Click the 'Upload this course' button.
# Select the data to be included in the backup.
# Create the course backup.

The course will then need to be approved by the hub administrator before it appears in the course listing.

The course may be removed at any time by clicking the button in the actions column. To update the course, firstly remove it from the hub, then re-share it. You may also share different versions of the same course.

== Hub listing ==

To check whether a course is included in the hub listing, click the 'Check it now' link. Your Moodle site will contact the hub and will update the status of all courses published on the hub.

==See also==
* [[Community hub]]

[[Category:Hub]]

[[fr:Publier un cours]]

Capability report

2010-12-16T14:32:51Z

Fox: French link

{{stub}}{{Moodle 2.0}}

Location: ''Site Administration > Users > Permissions > Capability report''

[[Category:Roles]]

[[fr:Rapport de capacité]]

Repositories

2010-12-16T14:16:31Z

Fox: French link

{{Moodle 2.0}}The repository feature in Moodle 2.0 onwards allows a site administrator to [[Manage repositories|manage site folders]] in the "[[Moodledata directory]]" from Site administration > Plugins > Repositories. Repositories appear in [[File picker]] for the users. Users can browse external repositories.

The Moodle 2.0 File picker standard install will show Server files, Upload files and Private files repositories along with the contextual Upload files and Recent files links. Moodle comes with 15 other hidden repositories which can be turned on and renamed if required by the site administrator.

Repositories in Moodle 2.0 video:

<mediaplayer>http://www.youtube.com/watch?v=zdrdyev82bU</mediaplayer>

==Vocabulary==
'''Repository plugin''': it is also called a repository type. It can be named Box.net, Flickr, Mahara, Youtube... Adding a plugin allow users to create instances of this plugin. Only instances are displayed into the file picker. Type only exist in order to let a Moodle administrator to deactivate/delete all instances of a type in one click.

'''Repository instance''': An instance is displayed into the file picker and it is the access point to an external repository. An instance can have specific settings (for example be linked to a personal account).

*First case: when you add the plugin, an instance is automatically created and can not be edited. The Moodle administrator cannot change the instance name. The instance name displayed into the file picker will be exactly the same as the plugin name. For example Youtube, Box.net...
*Second case: the plugin allow the Moodle administrator to add multiple instances. An instance has a name for example Flickr Public access to Martin account, Martin's Mahara... For this second case it is important to identify two different kind of instances:
#Common instances: The instances set by Moodle administrator in these same administration pages will be available into any file picker.
#Private instance: A teacher can set some instances available only for a course, and an user can set some instances only available for himself. In order to set instances for a course the teacher will go to the course page, and in order to set instances for a personal use, a user will go on his profile page. An administrator cannot add/edit private instances from the administration pages.

Import files from Dropbox into Moodle 2.0 video:

<mediaplayer>http://www.youtube.com/watch?v=V221JLCywWs</mediaplayer>
==Enabling repositories==

Repositories can be enabled by an administrator in ''Site administration > Plugins > Repositories > Manage repositories''.

A repository plugin may be set to

* Enabled and visible - appears in the file picker
* Enabled and hidden
* Disabled - default setting

The order in which repositories are shown in the file picker may be set using the up and down arrows.

==Available repository plugins==

*Upload a file
*Server files
*Recent files
*[[Private files]]
*[[Alfresco repository]]
*[[Box.net repository configuration|Box.net]]
*[[Legacy course files]]
*[[Dropbox]]
*[[File system repository configuration|File system]]
*[[Flickr repository configuration|Flickr]]
*[[Flickr public repository configuration|Flickr public]]
*Google Docs
*Merlot.org
*Picasa web album
*Amazon S3
*URL Downloader
*[[WebDAV repository]]
*Wikimedia
*Youtube videos

==Contributed repository plugins==

Additional repository plugins may be installed, such as

*[http://moodle.org/mod/data/view.php?d=13&rid=2611 Riffly] audio-only or audio-video recording
*[http://moodle.org/mod/data/view.php?d=13&rid=2612 Nanogong] audio recording
*Mahara (see MDL-21993)

==See also==

* [[Repositories FAQ]]
* [http://moodle.drupalgardens.com/article/tue-06152010-1918/ftp-files-moodle-20-repository-api FTP files into Moodle 2.0 with the repository API]

[[Category:Repositories]]

[[eu:Biltegiak_kudeatu]]
[[de:Repositories]]
[[fr:Dépôts]]

Category:Repositories

2010-12-16T14:15:15Z

Fox:

An index of pages about [[Repositories]] in Moodle 2.0 onwards.

[[Category:Administrator]]
[[Category:Teacher]]
[[Category:Developer]]

[[fr:Catégorie:Dépôts]]

Category:Files

2010-12-16T14:11:52Z

Fox: French link

An index of pages about the [[Files | files]] option of the [[Course administration block | administration block]]

[[Category:Course]]

[[fr:Catégorie:Installation]]

Private files

2010-12-16T14:06:14Z

Fox: French link

{{Moodle 2.0}}In Moodle 2.0 onwards, each user has a private files area for uploading and managing a set of files.

The private files area is accessible via ''Navigation > My home > My profile > My private files'' or the [[My private files block]]. It is available as a source within the filepicker when selecting files to use in a course.

==Private files management==

To add a file to your private files area
# Click Navigation>My profile>My private files
# Click "Manage my private files" button
# The standard file picker Add-Create folder popup will appear.
# If desired, create or move to a folder,
#Click on the Add button
#Browse for and select a file
# Click the 'Save changes' button

[[Image:Files_standard_added_files_1.png|center|frame|Standard file add- create directory, showing 2 files]]
*Uploaded files may be downloaded, renamed, moved or deleted by clicking the icon next to the file. After making any changes, '''remember to click the 'Save changes' button'''.

[[Category:Repositories]]
[[Category:Moodle 2.0]][[Category:Files]]

[[fr:Fichiers personnels]]

IP blocker

2010-12-16T13:49:02Z

Fox: French link

{{stub}}{{Moodle 2.0}}
In Moodle 2.0 onwards, administrators can set a list of allowed and/or blocked IP addresses.

[[Category:Administrator]]

[[fr:Blocage IP]]

Latest release notes

2010-12-03T09:38:41Z

Fox: Moodle 1.8.14

==Moodle 2.0==
{{:Moodle 2.0 release notes}}

==Moodle 1.9.10==
{{:Moodle 1.9.10 release notes}}

==Moodle 1.8.14==

{{:Moodle 1.8.14 release notes}}

==Moodle 1.7.7==
{{:Moodle 1.7.7 release notes}}

==Moodle 1.6.9==
{{:Moodle 1.6.9 release notes}}

== See also ==

*[[Moodle version history]] for dates of release and links to notes for earlier versions

[[Category:Release notes]]

[[es:Notas de versiones]]
[[fr:Dernières notes de mise à jour]]
[[pt:Versões do Moodle]]
[[ru:Примечания к версиям]]
[[de:Aktuellste Versionsinformationen]]

Moodle version history

2010-12-03T09:37:51Z

Fox: /* Moodle 1.8 */

==Moodle 1.0==
*Moodle 1.0 - 20 August 2002
*Moodle 1.0.1 - 26 August 2002
*Moodle 1.0.2 - 2 September 2002
*Moodle 1.0.3 - 5 September 2002
*Moodle 1.0.4 - 10 September 2002
*Moodle 1.0.5 - 27 September 2002
*Moodle 1.0.6 - 26 October 2002
:: 1.0.6.1 - 6 Nov
:: 1.0.6.2 - 11 Nov
:: 1.0.6.3 - 14 Nov
:: 1.0.6.4 - 25 Nov
*Moodle 1.0.7 - 9 December 2002
*Moodle 1.0.8 - 7 January 2003
*Moodle 1.0.9 - 30 May 2003

==Moodle 1.1==
*Moodle 1.1 - 29 August 2003
*Moodle 1.1.1 - 11 September 2003

==Moodle 1.2==
*Moodle 1.2 - 20 March 2004
*Moodle 1.2.1 - 25 March 2004

==Moodle 1.3==
*Moodle 1.3 - 25 May 2004
*Moodle 1.3.1 - 4 June 2004
*Moodle 1.3.2 - 9 July 2004
*Moodle 1.3.3 - 16 July 2004
*Moodle 1.3.4 - 11 August 2004

==Moodle 1.4==
*Moodle 1.4 - 31 August 2004
*Moodle 1.4.1 - 12 September 2004
*Moodle 1.4.2 - 5 November 2004
*Moodle 1.4.3 - 21 December 2004
*Moodle 1.4.4 - 7 March 2005
*[[Moodle 1.4.5 release notes|Moodle 1.4.5]] - 7 May 2005

==Moodle 1.5==
*[[Moodle 1.5 release notes|Moodle 1.5]] - 5 June 2005
*[[Moodle 1.5.1 release notes|Moodle 1.5.1]] - 8 July 2005
*[[Moodle 1.5.2 release notes|Moodle 1.5.2]] - 16 July 2005
*[[Moodle 1.5.3 release notes|Moodle 1.5.3]] - 11 November 2005
*[[Moodle 1.5.4 release notes|Moodle 1.5.4]] - 21 May 2006

==Moodle 1.6==
*[[Moodle 1.6 release notes|Moodle 1.6]] - 20 June 2006
*[[Moodle 1.6.1 release notes|Moodle 1.6.1]] - 20 July 2006
*[[Moodle 1.6.2 release notes|Moodle 1.6.2]] - 12 September 2006
*[[Moodle 1.6.3 release notes|Moodle 1.6.3]] - 10 October 2006
*[[Moodle 1.6.4 release notes|Moodle 1.6.4]] - 17 January 2007
*[[Moodle 1.6.5 release notes|Moodle 1.6.5]] - 30 March 2007
*Moodle 1.6.6 - 11 January 2008
*Moodle 1.6.7 - 11 July 2008
*[[Moodle 1.6.8 release notes|Moodle 1.6.8]] - 15 October 2008
*[[Moodle 1.6.9 release notes|Moodle 1.6.9]] - 28 January 2009

==Moodle 1.7==
*[[Moodle 1.7 release notes|Moodle 1.7]] - 7 November 2006
*[[Moodle 1.7.1 release notes|Moodle 1.7.1]] - 17 January 2007
*[[Moodle 1.7.2 release notes|Moodle 1.7.2]] - 30 March 2007
*[[Moodle 1.7.3 release notes|Moodle 1.7.3]] - 11 October 2007
*[[Moodle 1.7.4 release notes|Moodle 1.7.4]] - 11 January 2008
*[[Moodle 1.7.5 release notes|Moodle 1.7.5]] - 11 July 2008
*[[Moodle 1.7.6 release notes|Moodle 1.7.6]] - 15 October 2008
*[[Moodle 1.7.7 release notes|Moodle 1.7.7]] - 28 January 2009

==Moodle 1.8==
*[[Moodle 1.8 release notes|Moodle 1.8]] - 30 March 2007
*[[Moodle 1.8.1 release notes|Moodle 1.8.1]] - 14 June 2007
*[[Moodle 1.8.2 release notes|Moodle 1.8.2]] - 8 July 2007
*[[Moodle 1.8.3 release notes|Moodle 1.8.3]] - 11 October 2007
*[[Moodle 1.8.4 release notes|Moodle 1.8.4]] - 11 January 2008
*[[Moodle 1.8.5 release notes|Moodle 1.8.5]] - 8 April 2008
*[[Moodle 1.8.6 release notes|Moodle 1.8.6]] - 11 July 2008
*[[Moodle 1.8.7 release notes|Moodle 1.8.7]] - 15 October 2008
*[[Moodle 1.8.8 release notes|Moodle 1.8.8]] - 28 January 2009
*[[Moodle 1.8.9 release notes|Moodle 1.8.9]] - 15 May 2009
*[[Moodle 1.8.10 release notes|Moodle 1.8.10]] - 26 October 2009
*[[Moodle 1.8.11 release notes|Moodle 1.8.11]] - 25 November 2009
*[[Moodle 1.8.12 release notes|Moodle 1.8.12]] - 27 March 2010
*[[Moodle 1.8.13 release notes|Moodle 1.8.13]] - 8 June 2010
*[[Moodle 1.8.14 release notes|Moodle 1.8.14]] - 3 December 2010

==Moodle 1.9==
*[[Moodle 1.9 release notes|Moodle 1.9]] - 3 March 2008
*[[Moodle 1.9.1 release notes|Moodle 1.9.1]] - 15 May 2008
*[[Moodle 1.9.2 release notes|Moodle 1.9.2]] - 11 July 2008
*[[Moodle 1.9.3 release notes|Moodle 1.9.3]] - 15 October 2008
*[[Moodle 1.9.4 release notes|Moodle 1.9.4]] - 28 January 2009
*[[Moodle 1.9.5 release notes|Moodle 1.9.5]] - 13 May 2009
*[[Moodle 1.9.6 release notes|Moodle 1.9.6]] - 21 October 2009
*[[Moodle 1.9.7 release notes|Moodle 1.9.7]] - 25 November 2009
*[[Moodle 1.9.8 release notes|Moodle 1.9.8]] - 25 March 2010
*[[Moodle 1.9.9 release notes|Moodle 1.9.9]] - 8 June 2010
* [[Moodle 1.9.10 release notes|Moodle 1.9.10]] - 25 October 2010

==Moodle 2.0==
*[[Moodle 2.0 release notes|Moodle 2.0]] - 24 November 2010

[[Category:Release notes]]

[[fr:Historique des versions]]
[[es:Historia de las versiones]]
[[de:Versionshistorie]]

Migration from MyISAM to InnoDB

2010-11-30T16:30:57Z

Fox: Changed order of items

{{stub}}
This page only applies to administrators using Moodle with a MySQL database.
It's about migrating [http://dev.mysql.com/doc/refman/5.1/en/storage-engines.html MySQL storage engine].

See [http://moodle.org/mod/forum/discuss.php?d=162871 Documentation for migration from MyISAM to InnoDB] for the current discussion which prompted the creation of this page. --[[User:Frank Ralf|Frank Ralf]] 11:41, 24 November 2010 (UTC)

== Difference between MyISAM and InnoDB ==
* read [http://tag1consulting.com/MySQL_Engines_MyISAM_vs_InnoDB]
* InnoDB is best for data integrity, not so good for searching large files, and uses up more CPU cycles and storage space than MyISAM equivalent
* InnoDB is much younger than MyISAM but is becoming increasingly attractive ... but because it is more complex, some utilities written for MyISAM like mysqlhotcopy may not work
* It is perfectly OK to select InnoDB for certain tables, and MyISAM for others (based on above criteria)

== MySQL Configuration ==
Before attempting to change the table type, you should:
* '''check InnoDB is enabled'''. Log in to MySQL and run the command [http://dev.mysql.com/doc/refman/5.1/en/show-engines.html SHOW ENGINES]. Make sure that support for InnoDB shows either "YES" or "DEFAULT".
* '''set innodb_file_per_table if required'''. [http://dev.mysql.com/doc/refman/5.1/en/innodb-multiple-tablespaces.html This setting] can be useful for large installations, but it only affects newly created tables and can't be applied retrospectively.

== Various Methods described in Moodle Forums (choose one)==
* run the innodb script as a webpage http://www.YOUR_MOODLE_SITE/admin/innodb.php (there might be timeout issues on large databases)
* use the CLI script in admin/cli/mysql_engine.php (requires access to shell, and the config.php must only have one moodle instance, but has no timeout issues)
* use PHPMyAdmin entering Structure view of a table and clicking Operations tab. Look for Storage Engine parameter. This is a tedious task due to the number of tables [http://moodle.org/mod/forum/discuss.php?d=162002]
* perform a database dump (e.g. mysqldump moodle_database > dump.SQL), use an editor or sed/perl/awk command to find/replace , replacing MyISAM with InnoDB. Finally, restore back in the server. (e.g. mysql < dump.SQL or equivalent)
* Follow the process detailed here - https://sites.google.com/site/moodlemayhem/tcea2011-moodle-server-setup-basics/moodleacidtrip

==See also==

* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=117913 New moodle.org] forum discussion

[[fr:Migration de MyISAM vers InnoDB]]

Migration from MyISAM to InnoDB

2010-11-30T16:29:13Z

Fox: French link

{{stub}}
This page only applies to administrators using Moodle with a MySQL database.
It's about migrating [http://dev.mysql.com/doc/refman/5.1/en/storage-engines.html MySQL storage engine].

See [http://moodle.org/mod/forum/discuss.php?d=162871 Documentation for migration from MyISAM to InnoDB] for the current discussion which prompted the creation of this page. --[[User:Frank Ralf|Frank Ralf]] 11:41, 24 November 2010 (UTC)

== MySQL Configuration ==
Before attempting to change the table type, you should:
* '''check InnoDB is enabled'''. Log in to MySQL and run the command [http://dev.mysql.com/doc/refman/5.1/en/show-engines.html SHOW ENGINES]. Make sure that support for InnoDB shows either "YES" or "DEFAULT".
* '''set innodb_file_per_table if required'''. [http://dev.mysql.com/doc/refman/5.1/en/innodb-multiple-tablespaces.html This setting] can be useful for large installations, but it only affects newly created tables and can't be applied retrospectively.

== Various Methods described in Moodle Forums (choose one)==
* run the innodb script as a webpage http://www.YOUR_MOODLE_SITE/admin/innodb.php (there might be timeout issues on large databases)
* use the CLI script in admin/cli/mysql_engine.php (requires access to shell, and the config.php must only have one moodle instance, but has no timeout issues)
* use PHPMyAdmin entering Structure view of a table and clicking Operations tab. Look for Storage Engine parameter. This is a tedious task due to the number of tables [http://moodle.org/mod/forum/discuss.php?d=162002]
* perform a database dump (e.g. mysqldump moodle_database > dump.SQL), use an editor or sed/perl/awk command to find/replace , replacing MyISAM with InnoDB. Finally, restore back in the server. (e.g. mysql < dump.SQL or equivalent)
* Follow the process detailed here - https://sites.google.com/site/moodlemayhem/tcea2011-moodle-server-setup-basics/moodleacidtrip

== Difference between MyISAM and InnoDB ==
* read [http://tag1consulting.com/MySQL_Engines_MyISAM_vs_InnoDB]
* InnoDB is best for data integrity, not so good for searching large files, and uses up more CPU cycles and storage space than MyISAM equivalent
* InnoDB is much younger than MyISAM but is becoming increasingly attractive ... but because it is more complex, some utilities written for MyISAM like mysqlhotcopy may not work
* It is perfectly OK to select InnoDB for certain tables, and MyISAM for others (based on above criteria)

==See also==

* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=117913 New moodle.org] forum discussion

[[fr:Migration de MyISAM vers InnoDB]]

Migration from MyISAM to InnoDB

2010-11-30T16:16:46Z

Fox: This document only applies to MySQL

{{stub}}
This page only applies to administrators using Moodle with a MySQL database.
It's about migrating [http://dev.mysql.com/doc/refman/5.1/en/storage-engines.html MySQL storage engine].

See [http://moodle.org/mod/forum/discuss.php?d=162871 Documentation for migration from MyISAM to InnoDB] for the current discussion which prompted the creation of this page. --[[User:Frank Ralf|Frank Ralf]] 11:41, 24 November 2010 (UTC)

== MySQL Configuration ==
Before attempting to change the table type, you should:
* '''check InnoDB is enabled'''. Log in to MySQL and run the command [http://dev.mysql.com/doc/refman/5.1/en/show-engines.html SHOW ENGINES]. Make sure that support for InnoDB shows either "YES" or "DEFAULT".
* '''set innodb_file_per_table if required'''. [http://dev.mysql.com/doc/refman/5.1/en/innodb-multiple-tablespaces.html This setting] can be useful for large installations, but it only affects newly created tables and can't be applied retrospectively.

== Various Methods described in Moodle Forums (choose one)==
* run the innodb script as a webpage http://www.YOUR_MOODLE_SITE/admin/innodb.php (there might be timeout issues on large databases)
* use the CLI script in admin/cli/mysql_engine.php (requires access to shell, and the config.php must only have one moodle instance, but has no timeout issues)
* use PHPMyAdmin entering Structure view of a table and clicking Operations tab. Look for Storage Engine parameter. This is a tedious task due to the number of tables [http://moodle.org/mod/forum/discuss.php?d=162002]
* perform a database dump (e.g. mysqldump moodle_database > dump.SQL), use an editor or sed/perl/awk command to find/replace , replacing MyISAM with InnoDB. Finally, restore back in the server. (e.g. mysql < dump.SQL or equivalent)
* Follow the process detailed here - https://sites.google.com/site/moodlemayhem/tcea2011-moodle-server-setup-basics/moodleacidtrip

== Difference between MyISAM and InnoDB ==
* read [http://tag1consulting.com/MySQL_Engines_MyISAM_vs_InnoDB]
* InnoDB is best for data integrity, not so good for searching large files, and uses up more CPU cycles and storage space than MyISAM equivalent
* InnoDB is much younger than MyISAM but is becoming increasingly attractive ... but because it is more complex, some utilities written for MyISAM like mysqlhotcopy may not work
* It is perfectly OK to select InnoDB for certain tables, and MyISAM for others (based on above criteria)

==See also==

* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=117913 New moodle.org] forum discussion

[[fr:admin/innodb]]

Migration from MyISAM to InnoDB

2010-11-29T09:44:35Z

Fox: French link

{{stub}}

See [http://moodle.org/mod/forum/discuss.php?d=162871 Documentation for migration from MyISAM to InnoDB] for the current discussion which prompted the creation of this page. --[[User:Frank Ralf|Frank Ralf]] 11:41, 24 November 2010 (UTC)

== MySQL Configuration ==
Before attempting to change the table type, you should:
* '''check InnoDB is enabled'''. Log in to MySQL and run the command [http://dev.mysql.com/doc/refman/5.1/en/show-engines.html SHOW ENGINES]. Make sure that support for InnoDB shows either "YES" or "DEFAULT".
* '''set innodb_file_per_table if required'''. [http://dev.mysql.com/doc/refman/5.1/en/innodb-multiple-tablespaces.html This setting] can be useful for large installations, but it only affects newly created tables and can't be applied retrospectively.

[[fr:admin/innodb]]

Installing Moodle using command line

2010-11-29T09:43:28Z

Fox:

{{Template:Installing Moodle}}
{{Moodle 2.0}}

Command line installation is recommended only for experienced server administrators. Please note you have to execute the installation script as the same user used for apache. Command line installation is not compatible with Windows platforms.

You'll find more information on [[Administration via command line]] page.

[[de:Installation von Kommandozeile]]
[[fr:Installer Moodle en ligne de commande]]

Developer meeting November 2010

2010-11-29T09:37:41Z

Fox: Typo

[[Developer meetings]] > November 2010 meeting

The meeting was at 07:00 UTC on Thursday, 25 November 2010. We had 37 participants and we covered everything in around 1½ hours.
*[http://elluminate.remote-learner.net/play_recording.html?recordingId=1176914355734_1290666764310 Recording of the meeting] (login as a guest by providing your email address, name and session password ''moodle'')

''Meeting participants, if anything we discussed has been missed out, please [https://docs.moodle.org/en/index.php?title=Developer_meeting_November_2010&action=edit edit the page] and add it!''

==Moodle 2.0 release==

Martin said it was good to have the Moodle 2.0 release as a milestone. We won't branch for a while yet but will work on refining 2.0. Not branching makes things easier for migration to git. We won't be working much more with 1.8, just security fixes.

==Moving to git==

Martin described how there have been good discussions in HQ about processes and how we can go forward. We will be switching completely to git as primary repository, CVS will be a mirror, people using CVS to update their sites won't notice anything, only devs will notice. Not sure of timing of switch yet, will have a lot more control over checkins, much more defined process with more reviewing.

* [[Development:Git Migration]]
* [[Development:Process]]

The triage role makes sure all fields filled in correctly, product owner role name from scrum, development period could be 2 weeks or 1 month, may use crucible, one point of git is that people can use their own tools. We're looking for good ideas, conventions from other projects on how they name things! Component maintainer may well be external developer, QA testing role could be Helen or anyone who knows how to use moodle. If a test fails, code is reverted, goes back to integration reviewer who either rejects patch or gets it fixed, then it goes back to QA.

Where do unit tests fall into sequence? The plan is to have unit tests running automatically more often.

Tim commented that all reviewing should happen in one place, contributors should see where things are at, all requests for reviews from different people should be in one central place.

Anthony asked about contrib and git. Martin explained that we'd start with core then contrib can follow, though anyone can start using git for contrib now.

=== Git Migration Concerns ===

There has been some discussion in the developer chat room about potential git workflows. Some immediate concerns about a workflow:

* Slow moving reviews. Especially for lesser known contributors, git makes reviewing and 'commiting' as an external contributor much easier, but code reviews are a social rather than technical problem. Time needs to be allocated to 'coaching' people who don't make the cut. The code review structure needs to be such that the top doesn't become a bottleneck.

* Multiple ineffective sign-off levels. There is no point jumping through multiple levels of code review if its not done effectively. (Upon writing this I realise we need to just try it and make sure it doesn't become like this, rather than expecting it to fail--[[User:Dan Poltawski|Dan Poltawski]] 09:34, 23 November 2010 (UTC)).

* How to manage the code-review 'work-stack'? If there is a list of 'merge requests'? If we continue to use the tracker for this we're likely to get the problem of 'lost patches' sitting in bugs which have never been looked at by a core contributor.

Martin explained that the problem previously was that we never had well-defined roles, and some people were filling multiple roles. It will be much better when people know exactly what they are doing. If certain things take a long time then we know we need to get somebody extra in.

Dan Marsden commented that he saw component maintainers as a bottleneck. Martin replied that we can have multiple maintainers.

* Loss of 'kudos' for existing commiters. Like it or not, some respect comes with commit access. This can be replaced by reviewing roles having a place in the code review 'tree'.
** We can use this to ensure better code review happens though. If i'm a mid-level reviewer, I would want to improve my kudos by only letting good stuff through ;-)
** Please note git supports both Committer: and Author: field for each commit. So we can easily to respect original author of the patch. --[[User:David Mudrak|David Mudrak]] 13:08, 24 November 2010 (UTC)
*** Perhaps the solution to the original question is a general rule that nobody should commit their own work. The credit goes to the author (which would encourage more contributions) and a workflow would need to be developed that would ensure quick review when appropriate. The list of "Moodle Developers" would be those who have authored code that is committed (perhaps with an indication of the number of contributions to distinguish major developers). --[[User:Gary Anderson|Gary Anderson]] 19:19, 24 November 2010 (UTC)
*** Sorry, the problem is not that there is lack of credit, in fact its much better in git than CVS, as the original author should be retained (so new contributors get credit from the start). The problem is instead of 'established contributors' who currently have 'kudos' in the form of commit access. This will be lost, and I think there is still a place for such kudos (in the form of reviewer roles, perhaps). --[[User:Dan Poltawski|Dan Poltawski]] 20:16, 24 November 2010 (UTC)
*** In addition to having other roles like reviewer, etc. we could use something like the Linux kernel 'tag lines' (see http://www.kernel.org/doc/Documentation/SubmittingPatches sections 12-14). Then we could update moodle.org "bagdes" dynamically, like we currently do for particularly helpful moodlers, based on the number (and type) of times the user appears on those tag lines for the commits in a given time frame [[User:Iñaki Arenaza|Iñaki Arenaza]] 22:10, 24 November 2010 (UTC)

==Other stuff==

* Converting unit tests to PHPUnit
: Martin said that Petr had come across problems with PHPUnit, though they're hopefully fixed now. Martin will decide when we switch to PHP Unit in the Moodle 2 codebase, it's technically possible to do it immediately.

* Heads up: [[Development:Question Engine 2]] coming in Moodle 2.1
: Tim explained that all the code is done in OU version, the OU will release all on 6 December 2010. It's had a lot of testing, starting last May. Tim is feeling good about the code, but scared about the db upgrade. The plan is to make it a branch of Moodle 2, which will involve certain amount of rework. Tim has written a lot of unit tests which all pass.
: Martin commented that it was a very good spec as usual.
* [[Development:Scheduled Tasks Proposal|Proposal for a better cron infrastructure]]
:Tim explained that the proposal for a better cron infrastructure was a nice idea that was talked about a year ago in the hackfest. The cron is one big script, we should make it smarter e.g. call this function every 5 mins, that function at 2am, keep logs in db, admins reports so they can see everything cron is doing and anything failing.
: Martin replied that it sounds like a good idea and asked for volunteers.
* Performance Profiling
: Dan explained that his colleague Ruslan had been working on it (see the discussion [http://moodle.org/mod/forum/discuss.php?d=162045 Moodle performance testing: 1.9 vs. 2.0]). Eloy is working on xhprof, can find out all kinds of profiling info. A cool thing Eloy has done is mark a run as a reference run, then you can view profiling differences with last reference run. (See the recording of the meeting for a demo.)
: Martin said we should get it into head asap. We should be focusing on performance stuff now.

Martin concluded the meeting by mentioning that La Trobe university in Victoria is launching Moodle 2.0 in January. Martin said that he hadn't yet worked out the 2.01 roadmap. The git switch will happen pretty soon, hopefully in the next week, will give everyone a warning, take away CVS write access, CVS server will stay where it is. The new JIRA is up, have a play and report any bugs!

Finally, a big thank you to [[Moodle_2.0_release_notes#Credits|everyone who made check-ins to Moodle 2.0 code]] :-)

==See also==

*[http://moodle.org/mod/cvsadmin/view.php?conversationid=6157#c240813 Meeting subtitles developer conversation] for additional meeting notes (only available to developers with CVS write access)

[[Category:Developer]]

Environment

2010-11-29T09:31:05Z

Fox: /* Database */

Location: ''Administration > Server > Environment''

The environment page enables you to check that your site meets all system requirements for your current and future versions of Moodle. It is important to check system requirements prior to [[Upgrading|upgrading]].

Note: some of the PHP extensions are included as standard in later distributions of PHP, depending on platform:
* Iconv is included in PHP from 5.0 onwards on Windows [http://uk3.php.net/manual/en/iconv.installation.php]
* Tokenizer is included in PHP from 4.3.0 onwards [http://uk2.php.net/manual/en/tokenizer.installation.php]
* Ctype is included by default from PHP 4.2.0 onwards http://uk.php.net/manual/en/ctype.installation.php

==Moodle version 1.8==

*MySQL version 4.1.16 or later is required, or PostgreSQL 7.4.x or later
*PHP version 4.3.0 or later is required (but don't use versions 5.0.0 to 5.0.6 which were buggy)
*[[admin/environment/unicode|Unicode]] is required
*The [[admin/environment/php extension/curl|php_extension curl]] is recommended to be installed/enabled
*The [[admin/environment/php extension/iconv|php_extension iconv]] is recommended to be installed/enabled
*The [[admin/environment/php extension/mbstring|php_extension mbstring]] is recommended to be installed/enabled
*The [[admin/environment/php extension/openssl|php_extension openssl]] is recommended to be installed/enabled
*The [[admin/environment/php_extension/tokenizer|php_extension tokenizer]] is recommended to be installed/enabled
*The [[admin/environment/php_extension/xmlrpc|php_extension xmlrpc]] is recommended to be installed/enabled
*The [[admin/environment/php_extension/ctype|php_extension ctype]] is recommended to be installed/enabled

==Moodle version 1.9==
===PHP ===
* PHP version 4.3.0 or later is required
* PHP Settings. Check these settings in your php.ini or .htaccess file (if you're using Apache). For settings which use ON/OFF as their values, you can substitute 1 for ON and 0 for OFF if you prefer.
** ''register_globals'' '''MUST''' be OFF
** ''safe_mode'' needs to be OFF.
** ''memory_limit'' should be at least 16M (32M is recommended for Moodle 1.7 and 40M for Moodle 1.8 or later). Large sites may need more than 128M. PHP 5.2.x requires higher memory_limit values than previous versions of PHP. 64bit operating systems require even more memory.
** ''session.save_handler'' needs to be set to FILES.
** ''magic_quotes_gpc'' should be OFF
** ''magic_quotes_runtime'' needs to be OFF.
** ''file_uploads'' needs to be ON.
** ''session.auto_start'' needs to be OFF.
** ''session.bug_compat_warn'' needs to be OFF.
* PHP Extensions and libraries
** The mbstring extension is recommended.
** The iconv extension is recommended.
** [http://www.libgd.org/ GD library] and the [http://www.freetype.org/ FreeType 2] library and extensions are needed to be able to look at the dynamic graphs that the logs pages make. (Freetype support is available as part of the GD extension for the 5.x versions of PHP).
** The mysql extension is required if you are using the MySQL database. Note that in some Linux distributions (notably Red Hat) this is an optional installation.
** The pgsql extension is required if you are using the PostgreSQL database.
** The curl extension is recommended.
** The tokenizer extension is recommended.
** The curl and openssl extensions are required for the Moodle network functionality.
** The xmlrpc extension is required for the Moodle network functionality.
** The ctype extension is recommended.
** Other PHP extensions may be required.

===Database===
* Database (pick one):
** MySQL 4.1.16 or
** Postgres 8.0 or
** MSSQL 9.0 or
** Oracle 9.0

===See also ===
*[[Upgrading to Moodle 1.9]]

==Moodle version 2.0==
=== Hardware ===
* Disk Space: 160MB min
* Memory (RAM): 256 min, 1GB reccomnded, 50 users per 1GB RAM

=== Software ===
* Web server software. Such as [[Apache]] or [[IIS]].
* [[PHP]] scripting language. The exact requirements for PHP in Moodle 2.0 are [[#php_requires|below.]]
'''''
===PHP Configuration ===
* Version: 5.2.8 or later, it will not support any earlier version.
** PHP Settings. Check these settings in your php.ini or .htaccess file (if you're using Apache). For settings which use ON/OFF as their values, you can substitute 1 for ON and 0 for OFF if you prefer.
*** ''register_globals'' '''MUST''' be OFF
*** ''safe_mode'' needs to be OFF.
*** ''memory_limit'' should be at least 128M. Large sites may need more than 128M. PHP 5.2.x requires higher memory_limit values than previous versions of PHP. 64bit operating systems require even more memory.
*** ''session.save_handler'' needs to be set to FILES.
*** ''magic_quotes_gpc'' should be OFF. Unlike earlier versions of Moodle.
*** ''magic_quotes_runtime'' needs to be OFF.
*** ''file_uploads'' needs to be ON.
*** ''session.auto_start'' needs to be OFF.
*** ''session.bug_compat_warn'' needs to be OFF.
** PHP Extensions and libraries
*** The mbstring extension is recommended.
*** The iconv extension is recommended
*** [http://www.libgd.org/ GD library] and the [http://www.freetype.org/ FreeType 2] library and extensions are needed to be able to look at the dynamic graphs that the logs pages make. (Freetype support is available as part of the GD extension for the 5.x versions of PHP)
*** The mysql extension is required if you are using the MySQL database. Note that in some Linux distributions (notably Red Hat) this is an optional installation.
*** The pgsql extension is required if you are using the PostgreSQL database.
*** The pdo and pdo_sqlite extensions are required for the (experimental) SQLite 3 database support.
*** The curl extension is recommended.
*** The tokenizer extension is recommended.
*** The curl and openssl extensions are required for the Moodle network functionality.
*** The xmlrpc extension is required for the Moodle network functionality.
*** The ctype extension is recommended.
*** The intl extension is recommended. It is used to improve internationalization support, such as locale aware sorting.
*** Other PHP extensions may be required to support optional Moodle functionality, especially external authentication and/or enrolment (e.g. LDAP extension for LDAP authentication and the sockets extension for Chat server).

=== Database ===
* A working database server: [[MySQL]] or [[PostgreSQL]] are completely supported and recommended for use with any version of Moodle. MySQL is ''the'' choice for many people because it is very popular, but there are some [[Arguments in favour of PostgreSQL|arguments in favour of PostgreSQL]], especially if you are planning a large deployment.
** MySQL 5.0.25 or
** Postgres 8.3 or
** MSSQL 9.0 or
** Oracle 10.2
** SQLite 3 (experimental)

===See also ===
*[[Installing Moodle 2.0]]
*[[Upgrading to Moodle 2.0]]

[[Category:Environment]]
[[Category:Moodle 2.0]]
[[Category:Moodle 1.9]]
[[Category:Moodle 1.8]]

[[eu:Ingurunea]]
[[fr:Environnement]]
[[ja:動作環境]]

Administration via command line

2010-11-29T09:27:57Z

Fox: French link

{{Moodle 2.0}}

If you have shell access to your web server, you may find various CLI (command line interface) scripts useful during Moodle administration. All command line tools are located in <code>admin/cli/*</code> directory. To avoid problems with access control, you should run them as the owner of the web server process. It is especially important for CLI installation and upgrade as they create new files in moodledata directory and the web server has to have write access to them. In Linux distributions, the user that runs the web server is usually apache or wwrun or httpd or something similar. As a root, you will probably want to execute Moodle CLI scripts like this:

$ cd /path/to/your/moodle/dir
$ sudo -u apache /usr/bin/php admin/cli/somescript.php --params

Most of the scripts accept common --help (or -h) parameter to display the full usage information, for example:

$ sudo -u apache /usr/bin/php admin/cli/install.php --help

== Installation via command line ==

Since version 2.0, Moodle can be installed from the command line. There are two modes of installation. In interactive mode, the install script asks you for all data needed to properly set up new Moodle site. In non-interactive mode, you must provide all required data as the script parameters and then the new site is installed silently. The parameters can be passed in the interactive mode, too. The provided values are then used as the default values during the interactive session.

$ sudo -u apache /usr/bin/php admin/cli/install.php --lang=cs

== Maintenance mode ==

To switch your site into the maintenance mode via CLI, you can use

$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enable

To turn the maintenance mode off, just execute the same script with --disable parameter.

== Offline mode ==

In some situations, you may want to switch your Moodle site into offline mode so that it is not accessible via the web but you can not stop the web server completely (typically because there are other web pages and applications running there). If a file called <code>climaintenance.html</code> exists in the root folder of moodledata directory, Moodle will automatically display the contents of that file instead of any other page.

$ cd /var/www/sites/moodle/moodledata/
$ echo '<h1>Sorry, maintenance in progress</h1>' > climaintenance.html

You can prepare a nice formatted HTML page to inform your users about the server being down and keep in the moodledata directory under a name like <code>climaintenance.off</code> and rename it to the <code>climaintenance.html</code> if needed.

== Upgrading via command line ==

Moodle can be upgraded from the command line. As with the installation script, there is either interactive or non-interactive mode of the upgrade. The script itself does not put the site into the maintenance mode, you have to do it on your own. Also, the script does not backup any data (if you read this page, you probably have some own scripts to backup your moodledata and the database, right?)

$ sudo -u apache /usr/bin/php admin/cli/upgrade.php --non-interactive

Upgrading via command line is a very comfortable way of Moodle upgrade if you use [[CVS]] or [[Git|git]] checkout of the Moodle source code. See the following procedure how to upgrade your site within several seconds to the most recent version while preserving your eventual local customizations tracked in git repository:

$ cd /var/www/sites/moodle/htdocs/
$ git fetch
$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enable
$ git merge origin/cvshead
$ sudo -u apache /usr/bin/php admin/cli/upgrade.php
$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --disable

== Custom site defaults ==

During the install and upgrade via CLI, Moodle sets the administration variables to the default values. You can use different defaults. See MDL-17850 for details. Shortly, all you need to do is to add a file <code>local/defaults.php</code> into your Moodle installation. The format of the file is like

<code php>
<?php
$defaults['pluginname']['settingname'] = 'settingvalue'; // for plugins
$defaults['moodle']['settingname'] = 'settingvalue'; // for core settings
</code>

These defaults are used during install, upgrade and are also displayed as defaults at the Site administration pages.

== Reset user password ==

If you happen to forget your admin password (or you want to set a password for any other user of your Moodle system), you can use reset_password.php script. The script sets the correctly salted password for the given user.

$ sudo -u apache /usr/bin/php admin/cli/reset_password.php

== MySQL storage engine conversion ==

If you run your Moodle site with MySQL database backend and use the default MyISAM as the storage engine for your tables, you may want to convert them to use some more reliable engine like InnoDB (actually, you should want to switch to PostgreSQL ;-) anyway).

$ sudo -u apache /usr/bin/php admin/cli/mysql_engine.php --engine=InnoDB

== Running cron via command line ==

In versions 1.x, you could execute admin/cron.php either from command line or via the web. Since Moodle 2.0, only admin/cli/cron.php script can be run via command line.

[[Category:Administrator]]

[[fr:Administration en ligne de commande]]

Latest release notes

2010-11-25T09:18:38Z

Fox: French link

==Moodle 2.0==
{{:Moodle 2.0 release notes}}

==Moodle 1.9.10==
{{:Moodle 1.9.10 release notes}}

==Moodle 1.8.13==

{{:Moodle 1.8.13 release notes}}

==Moodle 1.7.7==
{{:Moodle 1.7.7 release notes}}

==Moodle 1.6.9==
{{:Moodle 1.6.9 release notes}}

== See also ==

*[[Moodle version history]] for dates of release and links to notes for earlier versions

[[Category:Release notes]]

[[es:Notas de versiones]]
[[fr:Dernières notes de mise à jour]]
[[pt:Versões do Moodle]]
[[ru:Примечания к версиям]]
[[de:Aktuellste Versionsinformationen]]

User site capacities

2010-11-24T09:18:48Z

Fox: /* See also */

{{Review}}
{{Template:Installing Moodle}}
In addition to the hardware and software requirements, you will also need to think about the capacity of your Moodle installation in terms of the number of users it can handle. There are two numbers to plan for:

:'''Browsing users''': the maximum number of users able to browse your Moodle site. This is the number of computers in your organization or on your course (whichever is greater).
:'''Concurrent database users''': the maximum number of concurrent database users (needed for Moodle activities such as quizzes). This is the number of users who will be using Moodle at the same time. In an educational institution, use your timetable/roster to obtain this figure.

Once you know these figures for your users, you can start work out if your Moodle installation can support this capacity. The exact number of users depends on your hardware/software/network combination. Usually the amount of memory installed (RAM) is the deciding factor but a faster overall processor speed will also help in reducing waiting times for pages to load.

The general rule of thumb for a single server is that the approx max concurrent users = RAM (GB) * 50 and the approx max browsing users = Approx max concurrent users * 5. As an example, a university with 500 total computers on campus and 100 concurrent users at any time will need approx 2GB of RAM on the one server to support the number of concurrent users.

*'''Note if you are using a hosted account''': Ask your provider what limits are placed on the number of concurrent database connections and the processor load. This will give a good estimate of the number of users your Moodle install can manage.

*'''Note:''' As of August 31, 2007, Moodle 1.8.2+ is not recommended for large installations, especially if you have large number (e.g. 20,000+) of courses. The main reason is the codes related to ROLES are still not fully optimized with database queries and still need some work. If you are planning to use 1.8.x codes for a larger institution, please make sure that you have sufficient time to do your own testing and performance profiling. Upgrade to Moodle 1.9!!

[Update|Updating from a previous version] of Moodle has been improved quite a bit from 1.8.3+ version (see this thread discussion: http://moodle.org/mod/forum/discuss.php?d=83281). Moodle 1.9 has even more improvements in all areas and is the recommended version.

== See also==
*[[Installing Moodle]]

[[de:Nutzerkapazitäten]]

Installing Moodle using command line

2010-11-24T09:17:01Z

Fox: French link

{{Template:Installing Moodle}}
{{Moodle 2.0}}

Command line installation is recommended only for experienced server administrators. Please note you have to execute the installation script as the same user used for apache. Command line installation is not compatible with Windows platforms.

[[de:Installation von Kommandozeile]]
[[fr:Installer Moodle en ligne de commande]]

Installing Moodle

2010-11-24T09:14:24Z

Fox: French link

{{Template:Installing Moodle}}
'''First, don't panic!''' [[Image:F1 35px.png]]

This guide explains how to install Moodle for the first time. There are links to other pages that go into more detail and try to cover the majority of possible web server setups.

Second, you may want to consider reviewing [[Finding and Selecting A Web Host]] to consider whether you really want to install Moodle yourself. If you decide to move forward with an installation, please read all the installation documentation carefully.

Third, if you still have a problem for which you can't find the answer, please see the Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where there are many people who can help you.

== Requirements ==

Moodle is primarily developed in Linux using [[Apache]], [[MySQL]] and [[PHP]] (also sometimes known as the LAMP platform). It is also regularly tested with Windows XP/2000/2003 (WAMP), Solaris 10 (Sparc and x64), Mac OS X and Netware 6 operating systems. Support for PostgreSQL, Oracle and Microsoft SQL Server is also available.

The requirements for Moodle are as follows:

=== Hardware ===
* Disk space: 160MB free (min). You will require more free space to store your teaching materials.
* Memory: 256MB (min), 1GB (recommended). The general rule of thumb is that Moodle can support 50 ''concurrent'' users for every 1GB of RAM, but this will vary depending on your specific hardware and software combination.
** This includes hosting limits of PHP or MySQL on a hosting service.
** The capacity can limit the number of users your Moodle site can handle. See [[User site capacities]]

=== Software ===
Moodle requires a web server environment and will run in [[Apache]] and [[IIS]] easily. Moodle should run in any server environment that supports [[PHP]].

Moodle is written in the PHP scripting language. Currently, Moodle v 1.9.x requires a minimum of PHP v4.3.0 to run. Moodle 2.0 needs PHP v 5.2.8. There have been some issues with deprecated tags in PHP v 5.3.0 which have a negative impact on a number of PHP Apps, Moodle not exempted, so please ensure your PHP version is later than v 5.3.2 if using a v5.3.x. There has also been reported some issues installing Moodle with [http://www.php-accelerator.co.uk PHP-Accelerator]. See the PHP Moodle version requirements here [[PHP settings by Moodle version]] for more information.

Moodle will use MySQL, MSSQL, PostGres or Oracle as a database, but no others. There is some real issues in the interoperability interface of different databases, which complicates the whole issue. For version information, you can go to the [http://download.moodle.org/ Download page] and that will describe version requirements for available packages.

If you want to run Moodle on your own computer, please see [[Installing Apache, MySQL and PHP]] for step-by-step instructions for installation on most popular platforms.

== Download and copy files into place ==

There are two ways to get Moodle, either as a compressed package from http://download.moodle.org/ or via [[CVS for Administrators|CVS]].

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.

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

:''Tip:'' 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".

If you're interested, [[Moodle site moodle directory]] gives a quick summary of the contents of the Moodle folder, to help get you oriented.

:''NOTE:'' The "connectionless" nature of the Internet, HTML and server-side file generation allows you to simply copy over critical files without having to uninstall then reinstall. When you do this, go to the Administration > Notifications page to see if any change has been properly registered within Moodle. Time your upgrades to periods of minimal activity, safer that way.

== Setting-up your web server ==
You need to create a blank '''database''' for Moodle to use and finally create a '''directory''' on your hard disk for Moodle to save your materials and other files you upload into your courses before you can start the installation process.

=== Create empty database ===

You need to create an empty database (eg "''moodle''") in your database system along with a special user (for example "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.

For more help with this see [[Create Moodle site database]].

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

The '''[http://www.cpanel.com/ cPanel]''' system is one of the most popular of these.
To create a database using cPanel:

# Click on the '''MySQL Databases''' icon.
# Type '''moodle''' in the New Database field and click '''Create Database'''.
# Type a ''username'' and ''password'' (not one you use elsewhere) in the respective fields and click '''Create User'''. Note that the ''username'' and ''database'' names may be prefixed by your cPanel account name and an underscore, and truncated to 16 characters. When entering this information into the Moodle installer - use the full names.
# Now use the '''Add Users to Databases''' button and give this new user account '''ALL''' rights to the new database.

=== Create the 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 the '''moodledata''' directory for you but if it fails then you will have to create a directory for this purpose manually.

<table style=background-color:lightCyan border=1 cellpadding=5 cellspacing=0 ><tr><td>
'''Security warning''': For security purposes, it is '''CRITICAL''' that this directory is '''NOT''' accessible directly via the web. The easiest way to do this is to simply locate it OUTSIDE the web site root directory (it is the folder that the main part of your URL -that is, the part up to the first single / - points to; for example, in <nowiki>http://your.domain.com/moodle/admin/cron.php</nowiki>, it is <nowiki>http://your.domain.com/</nowiki>).

'''If you don't protect the data directory from direct web access, anybody will be able to impersonate any user of your Moodle site (including the admin user!!!), and all of your course materials will be available to the web at large.'''
</table>

See [[Creating Moodle site data directory]] for more information about security in creating a data directory in CPanel in webhosts.

=== Troubleshooting ===

If you run into problems when installing Moodle you might have to tweak some of the settings for your Apache server or your PHP installation.

* [[Installing Moodle/httpd.conf setup]]
* [[Installing Moodle/Creating custom php.ini files]] for details.
* '''Alternative to ''php.ini'' and ''httpd.conf'' files''': If you do not have access to your php.ini or httpd.conf files on you web host, see [[Create .htaccess file]].
* Warning: as noted at http://moodle.org/mod/forum/discuss.php?d=124441&parent=550026 some Moodle installers such as Ubuntu populate an Apache conf.d file with php directives. Before trying to change any php directives make sure that no php directives are set in any apache conf file, including files in /etc/apache2/conf.d or similar directory.

== Start Moodle install ==
There are two basic ways to install Moodle: Most Moodlers are used to the installer script but with Moodle 2.0 you may install it from the command line.

=== Install with installer script ===

To run the installer script (install.php), just try to access your Moodle main URL using a web browser, or access '''<nowiki>http://yourserver/install.php</nowiki>''' 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, check in the Installation Forum for more help.

==== 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 to the "admin" page for the rest of the configuration.

The first time you access this admin page, you will be presented with a GPL "shrink wrap" 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. First, the main database tables are created. You should see a number of SQL statements followed by status messages. You should see SUCCESS next to each one until you see "Main databases set up successfully."

:''Tip:'' 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. Please see [[Install Moodle with installer script]] for more details and issues.

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

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. You can change this information later via the [[User profile]].

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

:''TIP:'' 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 sent to the home page of your new site! Please note the [[Site administration block]] on the left with links. 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 block.

=== Installing Moodle using command line ===
{{Moodle 2.0}}

[[Installing Moodle using command line]] is recommended only for experienced server administrators. Please note you have to execute the installation script as the same user used for apache. Command line installation is not compatible with Windows platforms.

$cd /var/www/html/moodle/admin/cli

More information about the options can be found using
$sudo -u wwwrun /usr/bin/php install.php --help

==Last tasks==

=== Set up cron ===

Moodle's background tasks (e.g. sending out forum emails and performing course backups) are performed by a script which you can set to execute at specific times of the day. This is known as a cron script. Please refer to the [[Cron|Cron instructions]].

=== Set up backups ===

Please refer to the [[Backup settings| backup instructions]].

=== Send a test email ===

Create a [[Manual_accounts|test user]] with a valid email address and [[message|send them a message]]. Do they receive an email copy of the message? If not then your email server and/or Moodle email settings may be misconfigured (see [[Email_processing|Email Processing]] for details.

===Create a new course===

Congratulations on setting up your Moodle site! You can now [[Adding/editing a course|create a new course]] and have a play ;-)

== See also ==
* [[Complete install packages]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Installing Apache, MySQL and PHP]]
* [[Upgrading Moodle]]
* [[Beginning Administration FAQ]]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=42688 Selecting a web host for Moodle] forum discussion
* [[masquerading|Masquerading]] - Running Moodle behind a masquerading/NAT firewall
* [http://ic.eflclasses.org/tutorials/settingupmoodleonhostingwitholdcpanel.swf Tutorial on choosing a host and setting up moodle via the old cpanel]
* [[Installation FAQ]]
* [[Finding and Selecting A Web Host]]
* [[experimental:Getting Help Installing and Managing Moodle]]
* [[Step-by-step Guide for Installing Moodle on Mac OS X 10.4 Client]]
* [[Installing Moodle on Windows Vista]]
* [[Step-by-step Installation Guide for Ubuntu]]
* [[RedHat Linux installation]]

[[es:Instalaci%C3%B3n_de_moodle]]
[[de:Installation von Moodle]]
[[fr:Installation de Moodle]]
[[ja:Moodleのインストール]]
{{Review}}

ad-hoc contributed reports

2010-11-23T15:35:59Z

Fox: Typos

These are community contributed reports for the [[Custom_SQL_queries_report]] site-wide report plugin (module) 
Everyone is welcome to add their own. until we find a better way to exchange reports between us. 
Enjoy :-) 

----

===Detailed ACTIONs for each MODULE===
<code sql>
SELECT module,action,count(id) as counter
FROM prefix_log
GROUP BY module,action
ORDER BY module,counter desc
</code>

===Detailed ACTIONs for each ROLE (TEACHER,NONE-EDITING TEACHER and STUDENT)===
<code sql>
SELECT r.name,l.action, count( l.userid ) as counter
FROM `prefix_log` as l
JOIN `prefix_role_assignments` AS ra on l.userid = ra.userid
JOIN prefix_role AS r ON ra.roleid = r.id
WHERE ra.roleid IN (3,4,5)
GROUP BY roleid,l.action
ORDER BY counter desc
</code>

===Detailed "VIEW" ACTION for each ROLE (TEACHER,NONE-EDITING TEACHER and STUDENT)===
<code sql>
SELECT l.action, count( l.userid ) as counter , r.name
FROM `prefix_log` as l
JOIN `prefix_role_assignments` AS ra on l.userid = ra.userid
JOIN `prefix_role` AS r ON ra.roleid = r.id
WHERE (ra.roleid IN (3,4,5)) AND (l.action LIKE '%view%' )
GROUP BY roleid,l.action
order by r.name,counter desc
</code>

===Most Active courses===
<code sql>
SELECT COUNT(l.id) hits, l.course courseId, c.fullname coursename
FROM prefix_log l INNER JOIN prefix_course c ON l.course = c.id
GROUP BY courseId
ORDER BY hits DESC
</code>

===RESOURCE count for each COURSE===
<code sql>
SELECT COUNT(l.id) count, l.course, c.fullname coursename
FROM prefix_resource l INNER JOIN prefix_course c on l.course = c.id
GROUP BY course
ORDER BY count DESC
</code>

===Most popular ACTIVITY===
<code sql>
SELECT COUNT(l.id) hits, module
FROM prefix_log l
WHERE module != 'login' AND module != 'course' AND module != 'role'
GROUP BY module
ORDER BY hits DESC
</code>

===System wide use of ACTIVITIES and RESOURCES===
<code sql>
SELECT count( cm.id ) AS counter, m.name
FROM `prefix_course_modules` AS cm
JOIN prefix_modules AS m ON cm.module = m.id
GROUP BY cm.module
ORDER BY counter DESC
</code>

===LOG file ACTIONS per MODULE per COURSE (IDs)===
<code sql>
select course,module,action,count(action) as summa from prefix_log
where action <> 'new'
group by course,action,module
order by course,module,action
</code>

==="Compose Web Page" RESOURCE count===
<code sql>
SELECT course,prefix_course.fullname, COUNT(*) AS Total
FROM `prefix_resource`
JOIN `prefix_course` ON prefix_course.id = prefix_resource.course
WHERE type='html'
GROUP BY course
</code>

===Total Activity of Roles:"Teacher" and "None-Editing Teacher" by Dates and by Hours===
The output columns of this report table can be used as base for a Pivot-Table
which will show the amount of '''activity''' per '''hour''' per '''days''' in 3D graph view.

<code sql>
SELECT DATE_FORMAT( FROM_UNIXTIME( l.time ) , '%Y/%m/%d' ) AS grptimed ,
DATE_FORMAT( FROM_UNIXTIME( l.time ) , '%k' ) AS grptimeh , count( l.userid ) AS counter
FROM `prefix_log` AS l
JOIN prefix_user AS u ON u.id = l.userid
JOIN prefix_role_assignments AS ra ON l.userid = ra.userid
JOIN prefix_role AS r ON r.id = ra.roleid
WHERE ra.roleid IN (3,4)
GROUP BY grptimed,grptimeh
ORDER BY grptimed,grptimeh
</code>

===FORUM use Count per COURSE -- not including NEWS Forum!===
<code sql>
SELECT prefix_course.fullname, prefix_forum.course, count(*) as total FROM prefix_forum
INNER JOIN prefix_course
ON prefix_course.id = prefix_forum.course
WHERE NOT(prefix_forum.type = 'news')
GROUP BY prefix_forum.course
ORDER BY total desc
</code>

===FORUM use Count per COURSE by type -- not including NEWS Forum!===
<code sql>
SELECT prefix_course.fullname, prefix_forum.course, prefix_forum.type, count(*) as total FROM prefix_forum
INNER JOIN prefix_course
ON prefix_course.id = prefix_forum.course
WHERE NOT(prefix_forum.type = 'news')
GROUP BY prefix_forum.course,prefix_forum.type
ORDER BY total desc
</code>

===LIST of all site USERS by COURSE enrolment===
Reports a site global list of all users enroled in each course
<code sql>
SELECT
user.firstname AS Firstname,
user.lastname AS Lastname,
user.email AS Email,
user.city AS City,
course.fullname AS Course
FROM
prefix_user AS user,
prefix_course AS course,
prefix_role_assignments AS asg
INNER JOIN prefix_context AS context ON asg.contextid=context.id
WHERE
context.contextlevel = 50
AND
user.id=asg.userid
AND
context.instanceid=course.id
</code>

===Permissions Overides on Categories===
(By: [http://moodle.org/mod/forum/discuss.php?d=153059#p712834 Séverin Terrier] )
<code sql>
SELECT rc.id, ct.instanceid, ccat.name, rc.roleid, rc.capability, rc.permission,
DATE_FORMAT( FROM_UNIXTIME( rc.timemodified ) , '%Y-%m-%d' ) AS timemodified, rc.modifierid, ct.instanceid, ct.path, ct.depth
FROM `prefix_role_capabilities` AS rc
INNER JOIN `prefix_context` AS ct ON rc.contextid = ct.id
INNER JOIN `prefix_course_categories` AS ccat ON ccat.id = ct.instanceid
AND `contextlevel` =40
</code>

===Lists "Totally Opened Courses" (visible, opened to guests, with no password)===
(By: [http://moodle.org/mod/forum/discuss.php?d=153059#p712837 Séverin Terrier] )
<code sql>
SELECT id , category , fullname , shortname , enrollable
FROM `prefix_course`
WHERE `guest` =1
AND `password` = ""
AND `visible` =1
</code>