MoodleDocs - Wkład użytkownika [pl]

Capabilities/block/badges:myaddinstance

2014-05-08T15:18:40Z

Mits: ja link

{{Capabilities}}
* This allows a user to add a [[My latest badges block]] to [[My home]]
* This capability is allowed for the default role of authenticated user

[[Category:Badges]]
[[Category:Capabilities|Block]]
[[Category:Block]]

[[ja:ケイパビリティ/block/バッジ:myaddinstance]]

Capabilities/moodle/badges:awardbadge

2014-05-04T15:24:17Z

Mits: ja link

{{Capabilities}}
* This allows a user to award a [[Badges|badge]] to a user
* This capability is allowed for the default roles of manager, course creator, teacher and non-editing teacher, and is prevented for the role of student

[[Category:Badges]]
[[Category:Capabilities|Badges]]

[[ja:ケイパビリティ/moodle/バッジ:awardbadge]]

Capabilities/block/badges:myaddinstance

2014-05-04T15:23:04Z

Mits:

Capabilities/block/badges:myaddinstance

2014-05-04T15:22:37Z

Mits: ja link

Badges FAQ

2014-05-01T15:49:00Z

Mits: ja link

{{Badges}}
==How can teachers award site badges?==
By default, teachers can only award course badges. Only users with capabilities to manage badges in the system are able to do this, so if you wish teachers to award site badges you need to create a new, global role.
#Go to ''Administration > Site administration > Users > Permissions > Define roles'' and add a new role called for example "Site badge awarder"
#Add it to the "System" context
#Set the following capabilities to "allow": moodle/badges:awardbadge, moodle/badges:viewbadges, moodle/badges:configurecriteria
#Assign this role to the teachers you wish to award site badges.

The teacher with the role "Site badge awarder" will see a link to Badges in the Administration block.

==Can more than one teacher in a course award the same badge?==
''(copied from MDL-39189'') It's not the user who issues the badge, but a role. Users with multiple roles will have an option to use both of them to issue badges. If the badge is awarded twice by different roles, both roles are displayed and criteria (ALL/ANY) is given. In some cases it will be required for a badge to be awarded by several different roles. When there are, let's say, three teachers in the course and they go to award a badge as a teacher, each of them will see the list of users who already got the badge from a teacher, so they won't need to award the badge again.
==What's the difference between a backpack and a collection?==
When you upload a badge to the [http://backpack.openbadges.org/ Openbadges site] you are adding it to your backpack, which is the general area you put your badges in. (Like a backpack!) You then organise them into collections (like separate little bags in your backpack) and you choose which to display on your Moodle profile. So a badge may be in your backpack and not in a collection, but it must be in your backpack before it can be in a collection. (Note the 'public' box must be ticked too.) Collections allow you to control which badges you share with people.
{|
|[[File:mozillabackpack.png|thumb|A users's online backpack]]
|[[File:collections.png|thumb|Drag badges into a new collection to display on Moodle]]
|}
==What size is a badge?==

A badge is displayed with dimensions 100 X 100 pixels. However, a larger image may be uploaded, which will then be cropped.

See also [https://moodle.org/mod/forum/discuss.php?d=230591 Badge image size] discussion.

==Can I award a badge based on a specific grade?==

There are two ways of awarding a badge based on a specific grade.

Method 1:

Set a passing grade for the quiz or assignment in the gradebook, as explained in section 1.3 of [[Activity completion settings]].

Method 2:

# Create a page resource and set the restrict access conditions so that it only appears if the user obtains a certain grade in the quiz or assignment
# Set the activity completion for the page as "view"
# Set the badge criteria such that the page has to be completed (i.e. viewed)

==Do I have to use my Moodle email for my backpack?==
No, but see this forum post [https://moodle.org/mod/forum/discuss.php?d=232875#p1011613 about Badges and Identity].

==Which roles can see which badges?==
See this [https://moodle.org/mod/forum/discuss.php?d=234155&parent=1017187#p1017363 forum post on viewing badges]

==Can I change a badge images once awarded?==
The short answer is 'no', but see this forum post on [https://moodle.org/mod/forum/discuss.php?d=228553 changing badge images] for more information.

==Can I revoke a badge once it has been awarded?==
No. See MDL-40551.

==See also==

* Moodle in English [https://moodle.org/mod/forum/view.php?id=8085 Badges forum]
* [http://www.somerandomthoughts.com/blog/2013/05/06/open-badges-and-moodle/ Open Badges and Moodle] blog post from Gavin Henrick
* [http://badg.us/en-US/ badg.us] - a service for creating and issuing badges
* [https://p2pu.org/en/groups/how-do-i-make-a-badge/ P2PU Badge Maker] - a step by step guide on how to make a badge
* [https://www.openbadges.me/ OpenBadges.me] - An open-access image creator from MyKnowledgeMap to support all of your Open Badge building needs.
* [http://moodlebadges.com/ Badges For Your Moodle] - CC-licensed badges available for free download

Forum discussions:
* [https://moodle.org/mod/forum/discuss.php?d=252377 Badges Backup Requires "Include Enrolled Users"?]

[[Category:FAQ]]

[[es:Insignias FAQ]]
[[ja:バッジFAQ]]

Badges

2013-12-15T15:06:56Z

Mits: ja link

{{Tracking progress}}
Badges are a good way of celebrating achievement and showing progress. Badges may be awarded based on a variety of chosen criteria and are fully compatible with [http://openbadges.org/ Mozilla Open Badges]. Badges created in Moodle may be displayed on a user's profile or pushed to their [https://backpack.openbadges.org/ Open Badges backpack] and public badge collections in their backpack will display in their Moodle profile.

There are two categories of badges:
* Site badges - available to users site-wide and related to the site wide activities, like finishing a set of courses.
* Course badges - available to users enrolled in the course and related to the activities that happen inside the course.

[[File:BadgesIntro2.png]]

*[[Managing badges]]
*[[Badges settings]]
*[[Using badges]]
*[[Badges FAQ]]

[[Category:Badges]]

[[de:Auszeichnungen]]
[[es:Insignias]]
[[ja:バッジ]]

Web services FAQ

2013-12-03T22:14:07Z

Mits: ja link

{{Web services}}
This document lists some popular questions from the [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum].

== What is the difference between web services and MNet ==

[[MNet]] is used to authenticate some users from a Moodle A site into a Moodle B site.

Web services are functions that can be called by external applications (via SOAP, XML-RPC, REST or AMF).

== I see the term "Web services" used in different ways, what does it mean? ==

# The entire system in Moodle is referred to as the Moodle Web Service system.
# A particular action (like creating a user) is known as a Web service '''function'''.
# The admin can enable groups of these functions for outside use, and these are known as a "Web service".

== Where is the Web Service API documented? ==

Since different Moodle sites can extend or restrict the API, and the API will evolve over time, the best way to see the exact API for a particular Moodle site is to look at the automatically generated documentation.

'''Full API documentation'''
# Connect as admin
# Go to Administration Settings block > Plugins > Web services > API documentation

'''Specific documentation to a user'''
# Connect as admin, enable web service, create a service and add some Moodle functions to it. Also see [[How_to_create_and_enable_a_web_service]].
# connect as non admin, and access the service documentation on your [[How_to_get_a_security_key|security keys page]].

== Why are there not many functions in the API? ==

We have been very careful when adding new functions because we don't want to be changing the API functions once they are implemented. The ones we have in Moodle 2.0 are the most commonly requested ones (for users, courses, groups and enrolments).

We will add more functions to core over time, based on contributions from the community and feature requests. See the [[:dev:Web_services_Roadmap|web service roadmap]].

You can also extend the API on your own Moodle site by creating your own API functions (see next question).

== How can I create a new web service function? ==

The easiest and recommended way to add a web service is to write a new Moodle local plugin and to implement the web service functions there. The Moodle administrator will just need to add the plugin in Moodle (copy the files in /local/), the web service functions will be automatically added. Please read /local/readme.txt for more information about plugin development. Finally read [[:dev:Creating_a_web_service_and_a_web_service_function|how to implement a web service and a web service function]].

== How can I set up a web service? ==

* See the document [[How_to_create_and_enable_a_web_service| How to create and enable a web service]].
* ''Settings > Site administration > Plugins > Web services > Overview'' explains two use cases.
* Finally ask questions on the [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum]

== Does the Moodle SOAP server work with JAVA or .NET? ==

Unfortunately the generated WSDL isn't currently compatible with JAVA or .NET. See MDL-28988 and MDL-28989 for plans to create a JAVA-compatible SOAP WSDL.

== How to get a user token from an external application? ==
you can generate and retrieve user tokens with the /login/token.php file => [[:dev:Creating_a_web_service_client#How_to_get_a_user_token|How to get a user token]]

== What is the 'Access control exception' error ==
It means that one of this admin setting has failed:
* authorised user: ip restriction fails to authenticate the user (Administration > Plugins > Web services > Manage services > Authorized users > click on user full name)
* authorised user: valid date is expired (Administration > Plugins > Web services > Manage services > Authorized users > click on user full name)
* admin created the token: ip restriction fails to authenticate the user (Administration > Plugins > Web services > Manage tokens > check the status)
* admin created the token: valid date is expired (Administration > Plugins > Web services > Manage tokens > check the status)
* the user is not listed in the authorized list (Administration > Plugins > Web services > Manage services > Authorized users)
* the user hasn't the required capability (Administration > Plugins > Web services > Manage services > Edit service)
* site in maintenance mode
* user is suspended
* user is not confirmed
* user is deleted
* the user authentication is set to nologin (edit the user profile)
* password expired (most likely happens with external authentication like LDAP)
* web service disabled (Administration > Advanced features)
* user doesn't have the capability to use the used web service protocol (user should have the capability 'webservice/use:xmlrpc'/'webservice/use:rest'/..., on SYSTEM context).
* the user token doesn't exist
* the web service function is not included in the service

Since Moodle 2.2, if the administrator turns Moodle debug mode >= NORMAL, then an explicit error message will be returned.

==See also==

* Using Moodle [http://moodle.org/mod/forum/view.php?id=6971 Web Services forum]

[[Category:MNet]]
[[Category:FAQ]]

[[ja:ウェブサービスFAQ]]

Security keys

2013-11-24T15:26:48Z

Mits: ja link

{{RSS feeds}}
A security key or token enables other systems to access Moodle securely. A security key may be used for secure RSS feeds or web services.

A user can obtain a security key via ''Settings > My profile settings > Security keys'' then enter the key in an external application accessing Moodle.

At any time, a user can reset their key by clicking the reset link. A new different key is automatically generate which will then need to be entered in the external application.

'''Note:''' The security keys page can not generate web service keys/tokens for admins. Admins can create a token manually from the administration block: ''Settings > Site administration > Plugins > Web services > Manage tokens''.

==Secure RSS feeds==

Secure RSS feeds are a way you can read [[Using_RSS_feeds|forum posts, blog entries, etc]] while you are offline, and without having to log in. For example, if you want to read the posts in a forum, you usually need to log in to Moodle. But if your site administrator has [[RSS_feeds_settings|enabled RSS]], these posts are available as a feed you can subscribe to with a [http://en.wikipedia.org/wiki/Comparison_of_feed_aggregators feed reader], and you can read entries even when you don't have access to the Internet.

Secure RSS feeds allow your feed reader, which usually expects feeds to be publicly available, to download material from Moodle without having to log in.

Whenever you are viewing an activity that provides an RSS feed, look in the "Settings" block for a link labelled "RSS feed of posts". This link is unique to your Moodle account. Paste it into your feed reader to have it obtain new entries for you automatically.

If you ever think your RSS feed token has been compromised in some way, e.g. you have lost a mobile phone that subscribed to a news forum, you can request a new one by clicking the ''Reset'' link on the ''Security Keys'' page in your Moodle profile. This will disable the old feed token and generate a new one. You can then visit the activities you wish to subscribe to and copy the URL, which will contain your new security key.

[[Category:Web Services]]

[[ja:セキュリティキー]]

Mobile Moodle FAQ

2013-10-06T03:02:17Z

Mits: ja link

{{Mobile}}
== How can I use Moodle on mobile devices? ==
There are currently 3 main ways to use Moodle on mobile devices:

* Users can open Moodle sites in their mobile web browsers.
* Users can download native apps for their mobile devices.
* Admins can configure their Moodle site to be Mobile-accessible through server extensions.

=== Mobile Apps ===
* The official [[Mobile app]] developed by Juan Leyva with support from Jerome Mouneyrac, Moodle HQ and others.
* [http://www.moodletouch.com MoodleTouch] (aka ''mTouch'') for iOS, created by Ali OzGur
* [http://mpage.hk/ mPage] for iOS and Android (work in progress), created by Mass Media HK
* [http://codeguild.org/app/mbot/ Mbot] for Android, created by Code Guild
* The [https://docs.moodle.org/23/en/Mobile_app My Moodle app] for iPhone, created by Moodle HQ (no longer being developed)
* [https://market.android.com/details?id=com.ivoid.droodle Droodle] - an Android client for the Moodle 2.1 platform

=== Server-side ===
* [http://www.mobilemoodle.org/momo18/ MoMo] (Moodle for Mobiles) - Requires a server extension and a client app; supports most mobile OSes including Symbian.
* [http://code.google.com/p/moodbile/ Moodbile] - Reference implementation of Moodle Web Services. Under development.
* [http://iphone.moodle.com.au iPhone4Moodle] - Under development.

==Where can I download the official Mobile app for iPhone and Android?==

The app can be downloaded for free from the Google Play Store and Apple app store.

==How do I get the official Mobile app to work for my Moodle site?==

Firstly, your Moodle site must be using Moodle 2.4 or later.

Secondly mobile web services must be enabled. See [[Enable mobile web services]] for details.

==Where can I select a theme for mobile devices?==

In ''Site administration > Appearance > Themes > Theme selector''.

New in Moodle 2.2 onwards is the MyMobile theme especially designed for mobile devices.

== I can't access my Moodle site using the app ==

Notice that by default Mobile access is disabled in Moodle. The administrator of your Moodle site (which must be version 2.4 or later) must enable mobile access.

Also, authentication methods like Shibboleth, CAS or LDAP/SSO are not supported currently. See https://tracker.moodle.org/browse/MOBILE-113 for more information.

== Moodle Mobile app says I need 2.4 or higher ==

The administrator of your Moodle site (which must be version 2.4 or later) must enable mobile access as follows:

In Site administration > Plugins > Web services > Mobile tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes.

Some Moodle sites uses special authentication methods like Shibboleth, CAS or LDAP/SSO that currently are not supported. See https://tracker.moodle.org/browse/MOBILE-113 for more information.

== How can I log out of the Mobile app current site? ==

You can add a new site in Settings -> Sites -> Add a new site and then delete your previous site using the X button near your old site name.

You can also reset completely the app using Settings -> Development -> Reset the application

==I can't view the courses tab as an administrator==
Moodle Mobile app is not suited for administrators ad the app displays only the courses you are enrolled in (not the courses you can see by capabilities).Note that the targeted user of the app is mainly a student or teacher.If you want to see the courses as an admin, you must be enrolled in the courses. You can use a non visible role or something similar.

==See also==

* [http://moodle.org/mod/forum/view.php?id=7798 Moodle for mobile forum]
* Tracker area [http://tracker.moodle.org/browse/MOBILE Moodle for Mobiles]
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=162872 Proposal for Supporting Mobile Themes and Browser Detection] forum discussion
* An open course, about "[http://tempus-efa.proj.ac.il/moodle/course/view.php?id=102 Teaching using Mobile - Best practices]"
* [http://www.moodlenews.com/mobile/ Moodle News - Mobile] - a breakdown of the mobile projects and products available

[[Category:FAQ]]

[[fr:Moodle pour les mobiles]]
[[ja:モバイルMoodle FAQ]]

Mobile web services

2013-09-13T15:11:24Z

Mits: ja link

{{Web services}}
Moodle comes with a built-in web service designed for mobile applications. It is required to run the official [[dev:Moodle Mobile]]. Enable it only if you want people to use the official app or if a third party app explicitly requires it.

== Enabling mobile web services ==

A site administrator first must enable mobile web services:

*In ''Settings > Site administration > Plugins > Web services > Mobile''
*Check "Enable mobile web services" and then
*Click Save.

That's it! No other steps required.

The rest of this document explains the "behind the scenes".

== What happens when the service is enabled ==
Enabling the mobile web services will automatically:
* enable the web services system (''Settings > Site administration > Advanced features'')
* enable the built-in external service called 'Mobile web services' - you should see this new mobile service listed as enabled
* enable the xml-rpc protocol (for backward compatibility with unmaintained My Moodle app)
* enable the rest protocol
* allow the 'webservice/xmlrpc:use' capability for authenticated user role
* allow the 'webservice/rest:use' capability for authenticated user role

== Disabling mobile web services ==
When you uncheck 'Enable mobile web services', it will automatically:
* disable the external service called 'Mobile web services'.
*if 'Mobile web services' was the only external service enabled:
** disable the web services system
** disable the xml-rpc protocol
** disable the rest protocol
** remove the 'webservice/xmlrpc:use' capability for authenticated user role
** remove the 'webservice/rest:use' capability for authenticated user role

==See also==
* [[Mobile app]]

[[Category:Mobile]]

[[de:Mobile Webservices]]
[[ja:モバイルウェブサービス]]

Mobile app

2013-08-28T17:14:03Z

Mits: ja link

{{Mobile}}
'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) replaces the old mobile app for iPhone, ''My Moodle''. It requires Moodle 2.4 or above.

== Features ==
* Responsive design for phone and tablets
* Upload a picture into your private file area
* Record an audio file and upload it into your private file area
* Send a private message to a course participant (can be done offline)
* Take a personal note about a course participant (can be done offline)
* Add a course participant to your phone contact
* Call a course participant touching the phone number
* Locate a course participant address on Google map
* Download and view some resources
* Quick access to your course contents
* Remote translation (see bellow)
* Remote layout/style customization (see below)

Notice that Moodle Mobile is not a replacement of the MyMobile or Bootstrap/Simple theme. Moodle Mobile offers offline contents, camera & audio features and (in a future) Push notifications.
You can use Moodle Mobile app in combination with a Mobile theme.

=== Screenshots ===

'''Phone'''
[[File:moodlemobile01.jpg]] [[File:moodlemobile02.jpg]] [[File:moodlemobile03.jpg]] [[File:moodlemobile04.jpg]] [[File:moodlemobile05.jpg]]

'''Tablet'''
[[File:moodlemobileipad01.jpg]] [[File:moodlemobileipad02.jpg]]

=== Translation ===

The app synchronizes the translation from your Moodle site. Upload to your lang/en folder (or to your moodledata/lang/mylang folder) a valid mobile.php file containing your translation, an example can be found [http://jsfiddle.net/jleyva/9AFKN/2/embedded/result/ here]

=== Style customization ===

The app can also retrieve your custom styles from your Moodle site. Since the app is a HTML5 app, you can apply safely any CSS, CSS2 and CSS3 style.

In your Moodle installation go to Plugins / Web services / Mobile and enter in the mobilecssurl field a valid URL pointing to a CSS file containing your custom styles. The original styles to override can be found here: https://github.com/moodlehq/moodlemobile/tree/master/css

The CSS should be placed inside your Moodle installation (in your custom theme or inside a local plugin)

Once the user is logged in the app, there is a periodical process that retrieves your remote CSS files for applying your custom styles.

Notice that on the first time a user opens the app, he will see the default "orange" style. Your custom styles will be applied once the user has added a site in the app.

==Moodle sites must be enabled for the app to access them==

Moodle 2.4 or above is mandatory.

The administrator of your Moodle site must enable mobile access as follows:

* In ''Administration > Site administration > Plugins > Web services > Mobile'' tick the 'Enable web services for mobile devices' checkbox, then click the button to save changes.

==Installing the mobile app==

Apps are available in Google Play and also Apple Store. You can install the app directly from your Mobile device, search for "Moodle Mobile" the author/owner must be "Moodle Pty Ltd"

Android: https://play.google.com/store/apps/details?id=com.moodle.moodlemobile

iOS: https://itunes.apple.com/es/app/moodle-mobile/id633359593

You can find the app build for other Mobile OS (not supported officially) here:

https://build.phonegap.com/apps/314601/builds

==Testing the app on a demo site==

In the login screen, type "teacher" or "student" in the Username field and click the Add button. You will be logged automatically to a Moodle demo site for testing the app.

== Cache ==
If you connect to your Moodle site and update/create/delete anything, and then go to your mobile app, the content will not be displayed. You will have to wait a couple of minutes. The cache time for the app is currently 5 minutes.

There are developer options for purging the cache at any time (Settings -> Development)

==How to report a bug==

# Log in to the Moodle Mobile tracker [https://tracker.moodle.org/browse/MOBILE https://tracker.moodle.org/browse/MOBILE] (you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create a tracker account] if you've not done so previously)
# ''Check whether the issue has already been reported by [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE searching all the issues]''
# If not, report the bug by clicking the 'Create Issue' link at the top right of the page, selecting 'Moodle Mobile' as the project
# Add a detailed description then click the Create button
# Attach the following files to the issue by selecting 'Attach Files' in the 'More actions' dropdown menu:
#* 'Device information' - this can be found in the app (Settings -> Development -> Device info, you can send yourself this information by email using the e-mail button at the bottom)
#* App Log (''Settings -> Development -> Show Log'', again you can send yourself this information by email)

=== Report a bug by email ===

You can send us the same report by email using ''Settings -> Report a bug''. As the report is sent by email to mobile@moodle.com, the report will take more time to be filed in the tracker.

== See also ==

* [[:dev:Moodle Mobile|Moodle Mobile developer docs]]
* [[Mobile web services]]

[[ja:モバイルアプリ]]

Migration from MyISAM to InnoDB

2013-07-09T21:33:51Z

Mits:

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

== Why migrate to InnoDB? ==

InnoDB is highly recommended rather than MyISAM because it works more robustly, performs better with big sites and allows better data integrity features (transactions).

It is required if you want to use Moodle's [[Web services]] (for the [[Mobile app]] for example), and possibly for more features in future.

== 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 <nowiki>http://www.YOUR_MOODLE_SITE/admin/tool/innodb</nowiki> (v2.2.1 You should be logged into your Moodle site as an administrator - there might be timeout issues on large databases) In earlier versions of Moodle 2.x the script was at <nowiki>http://www.YOUR_MOODLE_SITE/admin/innodb.php</nowiki>
* 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). '''If using this method, be very careful to use the same file encoding on both input and output.'''
* Follow the process detailed here - https://sites.google.com/site/moodlemayhem/tcea2011-moodle-server-setup-basics/moodleacidtrip
* Use the php script (Tested on 1.9 and 2.0/2.2) http://noveckg.blogspot.com/2012/04/moodle-php-script-to-convert-mysql.html

==See also==

* [http://tag1consulting.com/MySQL_Engines_MyISAM_vs_InnoDB MySQL Engines: MyISAM vs. InnoDB] article by Tag1 Consulting
* [http://code.openark.org/blog/mysql/useful-sed-awk-liners-for-mysql An easy migration of MyISAM mysqldump to InnoDB]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=162871 Documentation for migration from MyISAM to InnoDB]
*[http://moodle.org/mod/forum/discuss.php?d=117913 New moodle.org]

[[fr:Migration de MyISAM vers InnoDB]]
[[de:Migration von MyISAM zu InnoDB]]
[[ja:MyISAMからInnoDBへの移行]]

Migration from MyISAM to InnoDB

2013-07-09T21:33:25Z

Mits: ja link

Notifications

2013-06-19T15:50:45Z

Mits: ja link

{{Security}}
==Update notifications==

An administrator can configure update notifications for both Moodle core code and any contributed plugins installed on the site in ''Settings > Site Administration > Server > Update notifications''. See [[Available update notifications]] for more details.

==Login failure notifications==

An administrator can set up login failure notification in ''Settings > Site Administration > Security > Notifications''.

===Display login failures to===

Set this to administrators to be warned of anyone attempting to steal student or teacher logins. When set, a link stating the number of failed logins appears in the top right corner of the page when an administrator logs in. Click the link to access the login error page.

===Email login failures===

If you're concerned about login failures, you can set up email notification for administrators or any/all users who can change the site configuration.

===Threshold for email notifications===

This sets the number of failed logins for a given user from a single computer that will trigger notification.

Note: The number of failed login attempts that result in account lockout may be set in ''Administration > Site administration > Security > Site policies'' (new in 2.5).

==Other notifications==

The version of Moodle used may be found in ''Settings > Site administration > Notifications''.

Other notifications listed on the page may include

* [[Upgrade warnings|"Alpha" development code warning]]
* [[Cron]] not run for at least 24 hours
* Database tables are using MyISAM database engine - see [[Migration from MyISAM to InnoDB]] for advice on what to do
* "Enabling the PHP setting display_errors is not recommended on production sites because some error messages may reveal sensitive information about your server." What you do about this is not explained. Making a php.ini file with "display_errors = off;" in it in the folder "with the script" (?) is one suggestion found by googling, but that may depend on your server.
* Site not yet [[Site registration|registered]]

==See also==

* [[:dev:Available update notifications|Available update notifications developer documentation]]

[[es:Notificaciones]]
[[eu:Jakinarazpenak]]
[[fr:Notifications]]
[[de:Benachrichtigungen]]
[[ja:通知]]

Upgrade overview

2013-03-26T17:46:42Z

Mits: ja link

<div class="navtrail">[[Main page]] ► [[Installation]] ► [[{{PAGENAME}}]]</div>
''Moodle 2.4 available now!''
Start enjoying the cool features of the latest and greatest version of Moodle in four easy steps...
__NOTOC__
==Step 1: Make sure that your server can run Moodle 2.2==
[[File:checklist.png|right]]
(Note: You need to upgrade to Moodle 2.2 before upgrading to 2.4.)

Go to ''Settings > Site administration > Server > Environment''

Status OK for everything? Great! Go to step 2...

Any problems? You probably need to upgrade your server software (such as PHP) to a more recent version.

==Step 2: Be prepared!==
[[File:backup.png|right]]
As usual with any large upgrade, you should always be prepared to "roll back" if there's an issue with your data or some custom code you've added.

; A test install: We highly advise you make a copy of your production site to practice the upgrade on first. That way, if you run into any problems that need fixing you won't affect your main site.

; Always make backups: When upgrading your production instance, make sure you have copies of everything, just in case. Full instructions are here: [[Site backup]].

==Step 3: Replace your Moodle code==

At this point you can replace the Moodle code on your server with the version you downloaded.

; Check plugins: Any plugins you have installed will also to be replaced with a version for your new Moodle version. If there is not yet an updated version of the plugin available, it will need to be uninstalled before upgrading your site.

==Step 4: Perform the upgrade!==
[[File:gears.png|right]]
Trigger the upgrade by [[Upgrading#Finishing_the_upgrade|visiting the admin page]].

If you have a large site this may take hours, so we recommend [[Administration_via_command_line#Upgrading_via_command_line|upgrading via command line]].

==How did you go?==

; Yes - it worked!: Great! Repeat the process for Moodle 2.4, and please post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and share your success with the Moodle community!
; No - I had an error: Don’t worry, help is at hand. Post in the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] where our experts are waiting to explain any errors you obtain.

==See also==

* [[Upgrading]] for full details of the process
* [[Upgrading FAQ]]

[[Category:Installation]]

[[de:Aktualisierung in Kürze]]
[[es:Visión general de actualización]]
[[ja:アップグレード概要]]

Gradebook

2013-03-06T15:05:55Z

Mits: ja link

{{Grades}}
All the grades for each student in a course can be found in the course gradebook, or 'Grader report' in ''Settings > Course administration > Grades''.

The grader report collects [[Grade_items|items]] that have been graded from the various parts of Moodle that are assessed, and allows you to view and change them as well as sort them out into [[Grade_categories|categories]] and calculate totals in various ways. When you add an assessed item in a Moodle course, the gradebook automatically creates space for the grades it will produce and also adds the grades themselves as they are generated, either by the system or by you.

The grades displayed are initially displayed as the raw marks from the assessments themselves, so will depend on how you set those up e.g. an essay out of 36 will appear as however many raw marks that student got, not a percentage (although this can be changed later, see below).

Note that various default options for the gradebook are set at system level by the administrator and can be marked as being overridable by you, or fixed. This means that the options will not always be set up the same way for every user when they see the grader report for the first time.

==Display==

Along the top of the grader report are several rows: first the course, then the category, then the columns for each graded activity (for example: Assignment, Quiz, Lesson). Any activities settings which were left "uncategorised" will appear in the general category which is named after the course by default (any category name can be changed).

You can add a row showing the range of possible scores by selecting 'Show ranges' in 'My report preferences.

There are three ways that the categories can be displayed:

* Grades only - without the category totals column
* Collapsed - Category total column only
* Full view - grades and the aggregates (the totals column for the category)

Each section has a small icon immediately to the right of its name. Clicking this will cycle through these display modes for that category. + goes to grades only view, o goes to full view and - goes to collapsed view.

[[Image:Grades grader report with categories 1.png]]

===Highlighting rows and columns===

When your gradebook starts to grow, it can be hard to keep track of which student and which assignment a cell refers to. Highlighting solves that.
* Clicking on empty space in the cell that contains the students name will toggle the highlighting of that entire row
* Clicking on empty space in the cell at the top of each column will toggle highlighting of the entire column
(Note: this requires Javascript to be enabled in your browser.)

===Sorting by columns===

You can sort by any column. Click the [[Image:Move.gif]] symbol near the top of a column to sort by that column. This will change the symbol to a single down arrow. Clicking again will sort lowest-to-highest, changing the symbol to an up arrow. The arrows will toggle between these two states until you click on a different column.

The student name columns do not have the [[Image:Move.gif]] symbol. Clicking on either the first or last name will cause the report to sort.

{| style="width:75%; border="0"
|[[Image:Grade Report unsorted column1.png|frame|center|Unsorted]]
||[[Image:Grade Report sorted column2.png|frame|center|Sorted]]
||[[Image:Grade Report unsorted name1.png|frame|center|Unsorted]]
||[[Image:Grade Report sorted lastname3.png|frame|center|Sorted ]]
|-
|}

===Highlighting scores that are either adequate or unacceptable in red and green===

Turn editing on and click on the edit icon in the controls cell at the top of the column. You can then (maybe need to click 'show advanced') see the option to enter a 'grade to pass'. Once set, any grades falling above this will be highlighted in green and any below will be highlighted in red.

Note that the highlighting will not show if the Grader report is viewed in the editing mode.

===Horizontal scrollbar===

A horizontal scrollbar enables teachers to scroll grades in the grader report. (Note that this feature is not available for IE6 users or for users who have have the screenreader setting in their profile set to Yes.)

[[Image:Gradebook horizontal scrollbar.png|thumb|Horizontal scrollbar]]

===Mouse-over tooltips===

Each grade cell in the table has a tooltip indicating the user and grade item to which the grade belongs.

===Filtering the gradebook by groups===
If you change the course settings Group mode to Visible groups or Separate groups a drop-down menu will appear in the gradebook to allow you to filter your students by groups.

==Editing==

Note: Editing anything in the gradebook refers to editing the grades '''only''' and none of the available operations bear any relationship to editing the main course page i.e. the appearance of your course page cannot be influenced by anything you do in the gradebook. The "Turn editing on" button functions separately from the main course one, so editing can be on in the gradebook, but simultaneously off when you switch back to course view. This is because editing grades and editing the course page are separate capabilities. Roles such as 'non-editing teacher' may only have one or the other.

===Altering the grades===
You can click "Turn editing on" at the top right to show an edit icon next to each grade. Clicking on the icon will bring up the editing screen for that grade which will allow you to set the grade, its written feedback and a number of other attributes.

Alternatively, you can choose "Quick grading" and "Quick feedback" in 'My preferences' to make the report appear with editable boxes containing each grade, so you can change many at once. This capability can be a real time saver, but make sure to save at reasonable intervals lest a pageful of changes be lost.

Note: If you make changes here, they are then shown highlighted to indicate grades which have been manually changed.

===Hiding columns or individual grades===
Turning on editing then clicking the "Show show/hide icons" link will give you the familiar show/hide eye icon next to each grade and at the top of each column. For more information, read about [[Grade_hiding|grade hiding]].

===Recalculating===
If you change any part of an assessment e.g. alter the maximum grade for one of the questions in a quiz, you may find that the columns do not yet reflect the change you have made. Click '''Turn editing on''' twice to force the gradebook to re-check.

==Gradebook capabilities==

There is just one gradebook capability, [[Capabilities/gradereport/grader:view|View the grader report]], which is allowed for the default roles of manager, teacher and non-editing teacher.

==See also==

*[http://www.youtube.com/watch?v=5hrLNbifiGQ Video explaining the different gradebook reports]

[[de:Bewertungen]]
[[fr:Carnet de notes]]
[[ja:評定表]]

Groups course settings

2013-02-13T15:20:32Z

Mits: ja link

{{Course admin}}
Enabling [[Groups]] will allow the teacher to create sets of students. By default, the groups settings are turned off in a course. Groups can be used in the [[Context]] of a course or in a specific course activity.

Most of this information is also repeated in the [[Course settings]] page under [[Course settings#Groups|Groups]] and on the [[Groups]] page.

==Group mode==
This settings defines the default [[Groups|group]] mode for all activities in the course, by a pull down menu. The group setting can affect what users see in the course [[Participants]] list. There are 3 group mode choices: Visible, Separate and No groups.

:''TIP:'' When force mode is set to no, group mode merely acts as a default setting for each new activity. However, when force mode is set to yes, then the course group mode overrides all activity group settings. There are some examples of the two force settings below.

:The course group mode is useful when the teacher is going to add several activities with the same group setting. In a course with many activities that have different group mode settings, a teacher might enter them in batches, using the group course setting to save time.

===Visible groups===
Each group works in their own group, but can also see other groups. The other groups' work is read-only.
[[Image:forceNo.png|frame|center|Group course settings, with result in visible mode not forced]]

:The above example shows the group section in the course settings and part of a course. The teacher wants the default activity group setting to be "visible" but has not "forced" this preference on all activities. This is show by the two forum activities, where one shows the visible group icon and the other the separate group icon.

===Separate groups===
Each group can only see their own group, others are invisible.

===No groups===
There are no sub groups, everyone is part of one big community. They can see other peoples activity and interact with them.

==Force==
A "force" group mode at the course-level, will override any individual activity "group mode" setting, with the one set in the course.

:In the course example show above in "group mode" we had two activities, one set for visible group mode and the other set for separate group and the course Force was set to "No". In the example below, the teacher changed the settings in the same course. The teacher put the course settings on visible group mode and said "yes" to the Force mode.

[[Image:[[Image:forceYes.png|frame|center|Force turned on, notice the group icons show the override]]

:''TIP:''The force setting is useful when the teacher wants to import activities from another course and not have to change each activities group settings.

==Default grouping==
Allows the teacher to set a default group.

:''TIP:'' To see other groups in this list, you will have to go to the Course administration>Groups tab and use the [[Auto-create groups]] button. One you set the auto create fields, then a group will appear under this heading in addition to "Default".

==Using groups in course or activity==

A group or grouping can be used on two levels:

* '''Course level''' - the group mode defined at the course level is the default mode for all activities defined within that course. Changing the force mode to yes, will override any individual activity group mode settings.

* '''Activity level''' - each activity that supports groups can also have its own group mode defined. The course setting under Groups must have "Force" set to "No" to allow individual activities to allow their own group settings to work.

==Tips and Tricks==

*Groups icon not showing? - remember to select something other than "none" in the Group mode.

==See Also==

*[[Groups]] for more information about how to setup and use this feature.

*[[Groups FAQ]] for some usual questions and answers about Groups

[[Category:Groups]]

[[ja:グループコース設定]]

Participants

2013-01-13T15:19:48Z

Mits: ja link

Participants are the teachers and students who are part of a course. The list of participants can be seen by clicking the ''Participants'' link in the [[Navigation block]]

[[File:mycourses.png]]

If it has been added, the'' Participants'' link in the [[People block]] will also show course participants.

The participants list may be restricted to display:
* Members of a particular [[Groups|group]]
* Users inactive for more than a particular period of time
* Users with a particular role, such as teacher

Teachers (or other users with appropriate permissions) may select particular users then perform any of the following actions:
* Send [[Messaging|message]]
* Add a [[Notes|new note]]
* Add a common note (for adding the same note to more than one user)

==See also==
''Settings>Course Administration>Users>Enrolled users'' for options to assign roles to participants or or unenrol them
[[fr:Participants]]
[[ca:Participants]]
[[de:Teilnehmerliste]]
[[ja:参加者]]

Common module settings

2012-12-18T20:54:12Z

Mits: ja link

{{Activities}}
On the settings page for many modules, there is a section called "Common module settings". This refers to settings that are common to many modules.

==Example - assignment activity==
Assignment activity has two items and a point of information in the common module setting. There is more information about [[Groups course settings]] and [[Groups]] for all activities.

=== Group mode - assignment activity===
When course group mode is turned on and force is set to no, the [[Groups|group mode]] can be one of three levels on the assignment activity level: no groups, separate groups or visible groups.

;No groups
:There are no groups and all students submit their assignments in one Assignment area

;Separate groups
:Students submit their assignments within a separate Group based submission area and teachers/trainers can sort submissions by Group or view All Participants.

;Visible groups
:All students submits their assignment within a single Assignment area but may choose which Group to associate their submission with before uploading. Teachers/trainers can sort submissions by Group or view All Participants.

=== Visible - assignment activity ===
Choose whether to Show or Hide the assignment

=== ID number - assignment activity===

Setting an ID number provides a way of identifying the assignment for grade calculation purposes. If the activity is not included in any grade calculation then the ID number field can be left blank.

The ID number can also be set on the edit grade calculation page in the [[Gradebook]], though it can only be edited on the update activity page of the module in a course context.

The ID number may also be used in integrations with other software.

==Common module settings are used in==
*[[Adding/editing an assignment]]
*[[Adding/editing a chat]]
*[[Adding/editing a choice]]
*[[Adding/editing a database]]
*[[Adding/editing a forum]]
*[[Adding/editing a glossary]]
*[[Adding/editing a lesson]]
*[[SCORM module]]
*[[Adding/editing a survey]] does not mention at all
*[[Adding/editing a quiz]]
*[[Adding/editing a wiki]]
*[[Groupings]]
*[[Grade export]]

==See also==

* [[Grade calculations#Assigning ID numbers|Assigning module ID numbers for Grade calculations]]

[[ja:共通モジュール設定]]

Using Lesson

2012-12-05T21:09:08Z

Mits: ja link

{{Lesson}}
This page outlines how students and teachers interact with Moodle lessons once they have been created. For details on how to set up and then organise a lesson, see [[Lesson settings]] and [[Building Lesson]]

== What the student sees ==
*A student clicking on a Lesson will see an introductory page with one or more buttons which they choose from to select the path they wish to take.
*The display may vary according to how the teacher has set up the lesson in [[Lesson settings]]. For example; there may or may not be a list of pages down the side; there may or may not be an ongoing score.
*Students progress through the lesson with either content pages (of information, which is not graded) or various types of question pages(which may be graded) When a question page is used, the following page gives the answer and feedback if offered:
[[File:studentviewoflesson.png]]
*The lesson is ended when the student has met the criteria set by the teacher. This could be answering a certain number of questions correctly, accessing a certain number of pages with content (text, audio or video) or following a certain navigational path. A final page appears where the student can check their score, if applicable, and return to the main course page.
[[File:studentendoflesson.png]]

==What the teacher sees==
*A teacher clicking on a lesson will see tabs at the top offering them the chance to preview, edit, view reports or grade essays in the lesson:
[[File:teacherviewoflesson.png]]
===Preview===
*The lesson opens up in preview mode for the teacher. However, it will not show the score unless the teacher switches their role to a student.
===Edit===
*The Edit tab allows teachers to alter the lesson once it has been set up. There are two views - Collapsed and Expanded. See [[Building Lesson]] for more details on editing the lesson.

===Reports===
*The reports tab shows the performance of students taking the lesson. There is a general "Overview" and a "Detailed Statistics" tab.
====Overview====
[[File:lessonreportsoverview1.png]]

By clicking on the specific attempt, the teacher can view the student's answers to specific questions. It is also possible to delete a student attempt by checking the attempt and using the pull down menu to change "Choose" to "Delete".

*Below the "Overview" can also be seen general statistics: Average score, Average time, High score, Low score, High time, Low time.
[[File:lessonreportstatistics.png]]

====Detailed Statistics====
More detailed reports on individual questions are available from this tab, as in the following screenshot:

[[File:lessonreportsdetailed.png]]

====Grade essays====
*Any essay questions which have been set in the lesson can be accessed and graded here.

==Grading lessons==
*Note that for a lesson to be graded, it must have at least one question where a student can receive a score and the lesson can not be a practice lesson. Grades are calculated when the student has completed a lesson. Grades are kept for every student attempt.

==Understanding Flow control==
*''Settings > Lesson administration > Edit settings > Flow control group''

*Here are some examples to help you understand the Lesson flow control settings. Please note:
*"Allow student review" setting applies to the review of a whole Lesson, whereas
*"Provide option to try a question again" setting applies to the review of an individual question page. When the student does not select the correct answer, 'Provide option to try a question again" setting will display 2 buttons. One will direct the student back to the question and the other to continue.
*"Maximum number of attempts" is designed to prevent a student from being stuck on "This page" where they continually put or select the wrong answer. It will override other settings, such as review or the option to try the question again. When exceeded, it will not allow a score to be recorded for that question.

====Case 1 ====
The teacher wants the student to be able to attempt any question no more than 3 times and be given the chance to answer the question again. The teacher wants the student to see the response attached to their answer.

:Flow control settings
::Allow student review '''Yes'''
::Provide option to try a question again '''No'''
::Maximum number of attempts '''3'''
::Display default feedback '''No'''
::Number of pages to show '''0'''
::Slideshow '''No'''

:Student selects wrong answer and will see:
:: "Response for the wrong answer" (if any is shown)
:: "Yes, I'd like to try again" button
:: "Continue" button.

:Student selects correct answer and will see:
:: "Response for the correct answer" (if any is shown)
:: "Continue" button

====Case 2 ====
The teacher wants to allow the student 3 attempts at all questions but not see any feedback except the site default feedback for wrong answers.
*Flow control settings
::Allow student review '''No'''
::Provide option to try a question again '''Yes'''
::Maximum number of attempts '''3'''
::Display default feedback '''No'''
::Number of pages to show '''0'''
::Slideshow '''No'''

*Student selects wrong answer and will see:
::''Not quite. Would you like to try again?'' as text over the
::"Yes, I'd like to try again" button
::'"No, I just want to go on to the next question" button

:''Note:'' If the wrong answer jump is set to "This page" and the number of attempts is under the maximum, then the student will return to the question, regardless if they select "No, I just want to go on".

*Student selects correct answer and will see:
:: "Your answer: {gives the student's answer)"
:: Response attached to the correct answer (if any)

==== Case 3 ====
"Speed bump for speed clickers". Teacher only wants the student to get once chance to record an answer on any question. They will only see the response the teacher provides for any question, or the default feedback if no response has been set for the answer the student selected.

*Flow control settings
::Allow student review '''No'''
::Provide option to try a question again '''No'''
::Maximum number of attempts '''1'''
::Display default feedback '''Yes'''
::Number of pages to show '''0'''
::Slideshow '''No'''

*Student selects wrong answer and will see:
:: "Response for the wrong answer" (if any is shown)
:: "Yes, I'd like to try again" button
:: "Continue" button.

: ''Note:'' When teacher sets the Jump to "This page" for a wrong answer, they will return to the page but their score will not change.

* Student
::"Response for the correct answer" (if any is show)
::"Continue" button

==Ideas for using Lessons==
*Because of its "branching" nature, the lesson module lends itself to a wide variety of activities, not all of which need to be graded. In addition to merely working through a list of question pages, here are some other suggestions:
====Self-directed learning of a new topic====
*Use the lesson to introduce a new topic. The learner starts out knowing nothing but can progress at his own pace, reviewing what he is not sure of and moving on when he feels ready. This can be much enhanced by...
====Allow for different learning styles====
*When using the lesson to introduce a new topic, offer pages that deliver the content in different ways, according to how the students prefer to learn. For example the button "do you prefer to read?" goes to a page of text; "do you prefer to watch a video?" goes to a screencast ; "do you prefer to listen to instructions?" -goes to a podcast and so on.
====Role play simulations/Decision-making exercises====
*Use the lesson to set up situations where the learner has to make a choice each time and the scenario changes according to their selection. This could be a medical emergency for example, deciding upon the correct treatment, or a customer relations exercise, learning how best to deal with an awkward client. In an educational establishment it could serve well in Humanities subjects considering moral/ethical issues.
====Interactive fiction====
*For younger (and not so younger!) students, the lesson can be used to create a "choose your own ending" type of story where the student reads a page (or even watches a video/listens to an audio file) and then decides upon the character's next move. Apart from the entertainment value of this, it could be used to help guide pre-teens to behave responsibly by taking decisions for a character who is in a potentially dangerous situation.
====Differentiated revision guides====
*Students can be taken to different sets of revision questions according to their answers, allowing them to progress from basic to intermediate to advanced according to their prior knowledge.
====More!====
*Have any other good ideas? Please add them here!

== See also ==

[http://school.demo.moodle.net/mod/lesson/view.php?id=1156&pageid=182&start A working example of a Lesson from the School demo site.]

*The following two tutorials refer to older versions of Moodle:
*[http://www.youtube.com/watch?v=nq3das503-Q Creating a Decision-Making exercise (role play) using a Lesson]
*[http://www.youtube.com/watch?v=4xjXelUZguw Creating a Lesson video tutorial]

[[fr:Afficher une leçon]]
[[de:Lektion nutzen]]
[[ja:レッスンの利用]]

Jumps

2012-10-03T18:22:21Z

Mits:

{{Lesson}}
}Jumps are a unique feature of the Lesson module. Jumps are links and determine what happens after a student makes a choice on a lesson page. There are two basic types of jumps - Relative and Absolute. The teacher uses a pull down menu to see a selection of all possible jumps.

For example, a teacher creates 10 Lesson pages and titles them P1 to P10.

P1, P2, P3, P4, '''P5''', P6, P7, P8, P9, P10.

On P5, the teacher may want to send the student to P7 for one student choice and to "Next Page" for other choices. In this example "P7" is an absolute jump and "Next Page is a relative jump.

== Absolute jumps ==
The absolute jump always goes to the same page that a teacher has created. In our example we used P7.

P1, P2, P3, P4, '''P5''', P6, '''P7''', P8, P9, P10.

Note that the teacher can decide to change the title of "P7" to "Grading" as the page title. The jump from P5 will automatically change.

P1, P2, P3, P4, '''P5''', P6, '''Grading''', P8, P9, P10.

Moving either page will not effect any absolute jumps. In the example below the absolute jump in P5 will now skip 4 pages in the logical order.

P1, P2, '''P5''', P3, P4, P6, P8, '''Grading''', P9, P10.

Pages can have the same title and this can be confusing when setting jumps. For example, it is a good practice to retitle an End of Branch page so you don't end up with 5 pages all called End of Branch.

== Relative jumps ==
These kinds of jumps go to a position or create an effect. In our example, a Next Page jump in P5 is the next page in the logical order of the lesson is P6.

P1, P2, P3, P4, '''P5''', '''P6''', P7, P8, P9, P10.

The teacher may decide that more information is needed for those students going to P6. The teacher can insert a page (called P5-b)immediately after P5 and the Next Page jump will now go to P5-b.

P1, P2, P3, P4, '''P5, P5-b''', P6, P7, P8, P9, P10.

Or the teacher can move another page to the position right after P5, and the Next page jump will go there. In the example below P10 has been moved and it has become the "Next page".

P1, P2, P3, P4, '''P5, P10''', P5-b, P6, P7, P8, P9.

If the teacher moves P5 to another location in the logical order, the relative jump will still look for the "Next page" in our example this will now be P10.

P1, P2, P3, P4, P6, P7, P8, P9, '''P5, P10'''.

Here are a few of the relative jumps that a teacher might find in a Lesson page.

The random relative jumps need to be planned with care. The were designed to be used within a segment of a lesson.

===Next page===
We have covered this relative jump in our above example. It is also the default jump for the first answer of any question or content (branch table) page choices.

===This page===
This page takes the student back to the page they just viewed. Lesson will usually use this jump as a default in most question and content pages, if it didn't use "Next page".

===Previous page===
The page which is in front of the current page in the logical order.

===End of lesson===
The end of lesson is the splash screen a student sees when they have completed the lesson. In the simple lesson, this follows the last page in the logical order. It may show their score, offer a link to the next lesson or just say that they have completed the lesson. This jump is often used as a content page choice to allow the student to end the lesson at that point in the Lesson.

=== Unseen question within a branch ===
This will link to a randomly chosen unseen (by the student in this attempt) question between this content page and the End of the Lesson or the next End of Branch. This might be used in a segment of a lesson, where it is used in as a jump in C2 in the example below. Use with care.

C1, '''C2, Q1, Q2, Q3, EoB''', C3, C4, C5, Q4, C6.

=== Random question within a branch ===
This will link to a randomly chosen question between the current content page and the End of Lesson or the next End of Branch. If the student has already seen the question and attempts are greater than 1, they will get another chance to earn the point(s) for that question. If attempts are set to 1, the question will be skipped and another random question shown. Use with care.

C1, '''C2, Q1, Q2, Q3, EoB''', C3, C4,C5, Q4,C6.

=== Random branch table ===
This will jump to a random Content page between the current Content page and the End of Lesson or the next End of Branch. It is used in a segment and is a jump in C2 shown below. Use with care.

C1, '''C2, C3, C4, C5 EoB''', Q1, Q2, Q3, Q4, C6.

==Lesson jump pulldown example==
[[Image:Lesson Jump pulldown 3.JPG|center]]

Here is a pull down of jumps in a demo lesson for 1.8. Notice the relative and absolute pages. The relative pages are listed at the top and the absolute pages underneath them. Depending upon the current pages in a Lesson, some of the relative jumps may not be shown.

[[Category:Teacher]]
[[Category:Lesson]]

[[fr:Sauts]]
[[de:Spr%C3%BCnge]]
[[ja:ジャンプ]]

Lesson clusters

2012-09-07T01:35:45Z

Mits: ja link

{{Lesson}}
'''Clusters''' are special group of pages in a [[Lesson_module]]. A "cluster" is formed by placing a special navigational "cluster" page at the start of the group and an "end cluster" page after the last page in the group. Clusters can be considered an advanced feature of Lesson.

== What are clusters? ==

The typical cluster group (or series of pages) contains question pages and we will focus our attention on this kind of cluster. It is a good practice to first add most of the content (branch table) and question pages in a lesson, then consider where to place the special navigation pages that define a cluster.

Consider a series of question pages: Q1, Q2, Q3, Q4, Q5, Q6, Q7, Q8. This represents 8 questions in a Lesson.

A cluster is started in the logical order with a cluster page. Clusters should be completed with an End of Cluster page for best results (otherwise they treat the End of Lesson as the End of Cluster).

The teacher might put some of them in a cluster, where C1 is the first "cluster" page and EC1 is the first "end cluster" page in the lesson.
*Q1, '''C1''', Q2, Q3, Q4, Q5, Q6, Q7, '''EC1''', Q8.

A cluster represents a set of pages from which one or more may be randomly chosen. Questions within a cluster are randomly selected by choosing "Random Question within a Cluster" as the jump in the "Start Cluster" page. Questions within a cluster may either link to the End of Cluster to exit the cluster, or jump to any other page in the lesson. They may also jump to an unseen question within the cluster but most commonly are directed back to the "Start Cluster" page.

==Sub-Clusters==

Clusters can contain sub-clusters by using Branch Tables and End of Branches. To implement this advanced feature, set up a cluster as normal with a Cluster page followed by question pages (with the jumps set up the same as above) and ended with an End of Cluster page.
* Q1, '''C1''', Q2, Q3, Q4, Q5, Q6, Q7, '''EC1''', Q8
To set up a sub-cluster, wrap a group of questions with a Branch Table and an End of Branch.
* Q1, '''C1''', Q2, Q3, '''B1''', Q4, Q5, Q6, '''EB1''', Q7, '''EC1''', Q8
Neither the content nor the jumps of the Branch Table and the End of Branch are seen by the student. Rather the two pages act as markers for the sub-cluster within the main cluster. When the student attempts the lesson, only one random question page within the sub-cluster will be displayed to the student.

==When to use a cluster?==
A cluster is used when the teacher wants a series of questions in a lesson to appear in a different random order for each student.

In the example: Q1, Q2, C1, Q3, Q4, Q5, EC1, Q6, Q7, Q8, when the student reaches C1, the teacher might set the jump to "go to an unseen question in the cluster". When a jump in Q3, Q4 and Q5 is set to go back to C1, the student will see a "new" question in the cluster. When the student has seen all the questions in the cluster, they will be sent to EC1. The student will never see EC1, just be redirected by the jump in EC1.

Any or all of the question answers inside a cluster, could exit the student from the cluster. For example, specific jumps in Q3, Q4 and Q5 could be set to Q6, thus the student would pass over EC1 and leave the cluster.

==Tips and tricks==
Remember clusters have their own adaptive logic. It is always a good idea to test a cluster when logged in as a student. New users of a cluster, might do well to create a simple lesson so they understand how clusters work when applied in a more complex adaptive lesson.

:''TIP:'' Setting an answer's jump to "Unseen question" may cause problems. For example, when a student has seen all the questions and is allowed to re-enter the cluster in the same lesson attempt. Clusters are an advanced feature and should be checked in a student role.

:''TIP:'' Looking for a page that redirects without the student seeing it? Alison Schubert discovered the start and end cluster pages are not seen by the student. The teacher can insert an "End of cluster" page in the edit order with a jump. This will automatically redirect a student to another page without the usual continue button.

==See also==
*[[Branch structures]]

[[es:Clusters]]
[[de:Cluster]]
[[fr:Groupes de questions]]
[[ja:クラスタ]]

Building Lesson

2012-08-21T19:01:11Z

Mits: ja link

{{Lesson}}
This page is about how to structure a Moodle lesson once you have created it with the [[Lesson settings]]. For information on how best to use a Moodle lesson and how students approach it, see [[Using Lesson]]

==Planning your lesson==
*A lesson is made up of pages which may have content for the student to read or questions for them to answer. The questions can be created by the teacher or imported. The teacher decides the order in which these pages appear.
*You need to have a clear idea beforehand of what you want to do with this lesson. Is it to be a graded, linear learning experience? Or an ungraded, non-linear practice session? Will students be able to go back and revisit areas or is it just a once-only opportunity?
*Even those who are very comfortable working directly online might find it useful to note down on paper the direction they want their lesson pages to go in, rather than having to remember and visualize the navigation in their head.
*For hints and ideas about using the Lesson module, look at [[Using Lesson]] and [[Lesson FAQ]]

==Adding content and questions to your lesson==
*When you have set up your lesson with the [[Lesson settings]],click "Save and display" and you will be taken to the screen in the screenshot below.
*If you click "Save and return to course" instead, then click the "update" icon next to the lesson on the page and click "edit" in the ''Settings block>Lesson Administration''
[[File:lessonbegin.png]]

===Import questions===
*If you have some questions in the following formats, you can import them to use in your lesson by clicking the Import questions link. For general information about these question types, see [[Import questions]]
[[File:importquestions.png]]

===Import a powerpoint===
*Although this setting is available, it really does not work and is not advised. See [[Import PowerPoint]] for alternatives.

===Add a cluster===
*A cluster is a group of question pages which will be offered randomly to a student as they work through the lesson.It is best if you have made the question pages beforehand and can then decide where to mark the start and end of the cluster. The start is marked by a "cluster" page and the end by an "end of cluster" page. See [[Clusters]] for more information.

===Add a content page===
*This is a page where a teacher can provide information to move the lesson forward but without requiring the student to answer specific questions.
*The student sees the page's title, some information and then one or more buttons at the bottom to select.
*When the student clicks on a button, they go to the next page but their choice is not scored.

====Title====
*The title of a content page appears to the student at the top of the page.
*A teacher will also see the title in the collapsed edit mode when they are working on the Lesson, and they will also be able to choose the title (and hence this page) from the drop down "jump" lists.
*The title in a content page is also used with the "display left menu" setting.

====Page contents====
*This is where the teacher can add information for the student, making use of the [[Text editor]] and its multimedia features.

====Content====
*Here the teacher writes the words they want the student to click on to get to the next part of the lesson.
*These words will appear to the student as a button.
*The teacher can check the box to have the buttons appear horizontally, or uncheck it for them to appear centered vertically.

====Format====
*There are 4 format types to choose from when editing text in the content description box. If you wish to have the usual rich text editing icons, choose HTML format. (Note - once you have selected an option, you cannot then go back and change your mind!)However, if you DO choose HTML format, be warned that the student will not see the changes (such as bold or different colours) in the button.

[[File:lessoncontentbuttons.png]]

====Number of options available====
*How many of these you have depends on your choice in the ''Maximum Number of Answers'' setting in [[Lesson settings]]

==== The Jump====
*Each Description in a Content page has a Jumps menu. "Jumps" take a student from one page to another.
*A "relative jump" is "next page" or "end of lesson" whereas an "absolute jump" gives the actual name of a page.
*The teacher chooses from the dropdown the correct page to send the student to if they click on the button that will be made from this particular description. Any pages created by the teacher will have their titles appear in this dropdown, allowing them to be selected.
*When a student clicks on a description button, they are sent to the page defined in the Jump associated with the button.
*See [[Jumps]] for more detailed information.

===Add a question page===
*From this link you can choose from a variety of question types which will then be added as pages to your lesson:
[[File:addquestionpage.png]]
*''(Note: These question types are not the same as for the [[Quiz]] and are in no way connected with quiz questions.)''

*The format of question pages is similar to content pages outlined in [[Building_Lesson#Add_a_content_page| Section 2.4]] above.
*A typical question page could include:
**'''Title''' - the name the student sees at the top of the question page.
**'''Page contents''' - the actual question
**[[File:examplequestion.png]]
**'''Answer/Response/Format/Jump/Score''' as in the screenshot below
**[[File:exampleanswer.png]]

===Question types===
====Multichoice====
*The student is given a question and a list of answers. The answer list will be shuffled every time the question is view by a student. By default they choose one answer but you can check the box "multiple answer" to allow them to choose more than one answer.
====Essay====
*Students can write a longer answer as part of the lesson and this can be graded manually by the teacher. If the main purpose of your lesson is for students to write an essay, consider the [[Assignment module]] instead.
====Matching====
*This allows you to set up lists which must be matched against other lists, for instance, words, pictures, numbers etc. The student must match all correctly to receive the score.
====Numerical====
*This requires a number as an answer. A number within a range may also be accepted as correct. The range separator to be used is the colon : For example, to accept as correct any number between 10 and 12 (10, 11 and 12) you would type 10:12 in the Answer box.
====Short answer====
*A student must provide a single word or short phrase answer. The teacher must anticipate the possible answers and enter them in the Jump dropdown boxes, using ** wild cards if appropriate.
====True/false====
*The student is given a sentence and must decide if it is true or false.

==Moving your lesson forward==
*Once you have added your first content or question page, you reach the next screen which displays your page title/type/jumps (ie where the responses take the student to) and actions you can take next:
[[File:lessonactions.png]]
*The '''Actions''' icons allow you to move (if you have more than one), edit, preview or delete your pages.
*The drop down allows you to create another page of your choice:
[[File:lessonactionsdropdown.png]]

*Note the different view options:

====Collapsed view====
*This gives a brief outline of the lesson structure as in the two screenshots above.

====Expanded view====
*This shows more detail as in the screenshot below:
[[File:expandedview.png]]
==Ending your lesson==
*To bring the lesson to a close, select the "End of Lesson" option from the Jump menu on any relevant pages.
*The student will then see a generic message as in the next screenshot, with a direction back to the main course page or to view their grades:
[[File:endoflesson1.png]]

[[de:Lektion erstellen]]
[[ja:レッスンの作成]]

Lesson settings

2012-07-11T15:39:02Z

Mits: ja link

{{Lesson}}

This page explains the settings involved when first creating a lesson.
To add a lesson to your Moodle course page:
*With the editing turned on,in the section you wish to add your lesson, click the "Add an activity or resource" link (or, if not present, the "Add an activity" drop down menu )and choose ''Lesson''
*This will take you to the Lesson settings page.

==Lesson administration settings==

===General===
*''Note: Click the "Show Advanced" button to the right if you don't see all the options below.''
====Name====
*The name you add here will be the link the students click on to get to your Lesson.

====Time limit====
[[Image:Lesson Timer.png|right]]
*This allows you to set a time limit on the lesson. Students will see a count down counter as they work.The timer does not stop them doing the the lesson when the time is up, but correct answers are no longer scored.
====Available from/Deadline====
*Here you can set a start and end date and time for your Lesson.
====Maximum Number of Answers====
*Here you can set the default number of answer boxes available when you add your question or content pages. For instance, if you are only going to use True/False, you would only need 2. You can change this at any time so it's not crucial.

====Password protected====
*Change to "Yes" and enter the password if you want students only to access it when they know the password.

===Grade===
*Set a grade and grade category here.

===Grade options===
====Practice lesson====
*Use this if you don't need the lesson to be scored/graded but just need students to work through some pages.

====Custom Scoring====
*Use this to give a particular number score (negative or positive) to each answer

====Re-takes allowed====
*Choose this if you want your students to be able to do the lesson more than once.

====Handling of re-takes====
*If you allow your students to re-take the lesson, then decide here if the grade for all lesson attempts is the mean or the maximum.

:Note that the Question Analysis always uses the answers from the first tries of the lesson. Re-takes by students are ignored.

====Display ongoing score====
*Choose this to let students see their score as they work through the lesson.

===Flow Control===

*''Note: Click the "Show Advanced" toggle button to the right if you don't see all the options below.''
*[[Using Lesson]] gives examples of how these settings may be put to best effect.
====Allow Student Review====
*This puts a "Review Lesson" button on the last screen of the lesson to encourage the student to navigate through the lesson again from the start. Be sure to check other settings to allow them to change their answers.

====Provide option to try a question again====
*This displays a button after an incorrectly answered question so that the student can try again (but not get credit for it)

:''TIP:'' Leave this off if you are using essay questions.
====Maximum Number of Attempts====
*Decide here how many times you want students to be able to attempt each question. When they reach the maximum, they will be taken automatically to the next page.

====Action after a Correct Answer====
*Choose here where you want a student to be sent to if they get a question right. See [[Using Lesson]] for more details on this setting. The options are:
**the next part of the Lesson (default setting)
**a random, unexpected page
**a random page which they have not yet answered.

====Display default feedback====
*Choose this if you want to show a set phrase regardless of their answer. If you have set your own default feedback such as "well done; correct" or "never mind; better luck next time" etc it will appear. If you have not, then Moodle's default feedback will appear.
====Progress bar====
*Choose this to show a bar at the bottom of the page showing how far into the lesson the student has got.
''*Note: There are currently some issues with the lesson progress bar not displaying as expected. MDL-26016''

====Display left menu====
*Choose this if you want to show a list of the pages in the Lesson so a student can see what is coming up.
====Display left menu only if grade greater than ...%====
*Choose this if you want the student to go through the lesson (and get a grade) once and then, on review, to be able to see and navigate through all the different pages.
====Number of pages to show====
*You only need this if you have set "Action after a correct answer" to show an unseen or unanswered page. Otherwise, all pages will be seen.
====Minimum Number of Questions====
*Set here the minimum number of questions that will be used to calculate a student's score.Students will be told how many they have answered and how many more they need to answer.
*If you are using Content pages, then set this to 0.
*If you use this setting, then add some explanatory text at the start of the lesson so the student knows how many questions they must answer as a minimum. (They may answer more.
====Slideshow====
*Choose this if you want your Lesson displayed as a slideshow with fixed width, height and custom background colour. The administrator sets the defaults for these in ''Settings>Site Administration>Plugins>Activity modules>Lesson.''

====Link to an activity====
*Choose this to give students a link to another activity when they reach the end of the lesson. ''(Note: this can also be achieved using [[Conditional activities]])''

===Pop-up to file or web page===
*If you want to include a link to a file on the lesson page for students to refer to, upload it here.

===Dependent on===
*This allows access to the lesson to be dependent on students' performance in another lesson in the same course. ''(Note: this can also be achieved with [[Conditional activities]])''

==Other settings==
There are the usual [[Common module settings]] and - if admin has enabled them - the Restrict access settings and Activity Completion settings in [[Conditional activities]].

==Site administration settings==

The lesson module has additional settings which may be changed by an administrator in ''Settings > Site administration > Plugins > Activity modules > Lesson''.

===Slideshow width===
Sets the width of the slideshow only when this feature is enabled in a Lesson's "Change settings".
*Variable name: lesson_slideshowwidth, Default 640.

===Slideshow height===
Sets the height of the slideshow only when this feature is enabled in a Lesson's "Change settings".
*Variable name: lesson_slideshowheight, Default 480.

===Slideshow background colour===
Background colour to for the slideshow if it is enabled.
*Variable name: lesson_slideshowbgcolor, Default #FFFFFF.

===Popup window width===
Sets the width of the popup displayed for a linked media file
*Variable name: lesson_mediawidth, Default 640.

===Popup window height===
Sets the height of the popup displayed for a linked media file
*Variable name: lesson_mediaheight, Default 480.

===Show close button:===
Displays a close button as part of the popup generated for a linked media file
*Variable name: lesson_mediaclose, Default No.

===Number of high scores displayed===
Sets the number of high scores to display
*Variable name: lesson_maxhighscores, Default: 10

===Maximum number of answers===
Default maximum number of answers per page for site
*Variable name: lesson_maxanswers, Default: 4.

===Action after correct answer===
The default action to take after a correct answer
*Variable name: lesson_defaultnextpage, Default: Normal - follow lesson path

==See also==

[[de:Lektion konfigurieren]]
[[fr:Ajouter/modifier une leçon]]
[[ja:レッスンの設定]]

Upgrading to Moodle 2.2

2012-05-15T15:31:55Z

Mits:

{{Installing Moodle}}
You can upgrade to Moodle 2.2 from Moodle 2.1, 2.0 or 1.9. If you are upgrading from 2.0, please also read [https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to Moodle 2.1] . If upgrading from 1.9, please also read that and [https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to Moodle 2.0]. After reading this you can upgrade directly to 2.2.

If you are using an earlier version of Moodle, you must upgrade to the latest 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.'''

==System requirements==

* PHP must be '''5.3.2''' or later
** Required PHP extensions: iconv, curl, ctype, zip, simplexml, spl, pcre, dom, xml, json
** Required PHP memory_limit at least 40MB (64MB or more recommended 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

Note: The above system requirements are unchanged from Moodle 2.1.

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

* Read the [[:dev:Moodle 2.2 release notes|Moodle 2.2 release notes]] and check the [[:Category:New features|list of new features]]
* Check your site to make sure it meets all system requirements for 2.2 in ''Settings > Site 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

==Possible issues that may affect you==

* If you have custom reports, there have been changes that may require (simple) changes to be made to their code. See the developer documentation [[:dev:General report plugins]] for details.
* Global search has been removed from core as it was broken. (A new global search is being written for 2.3.)
* Some web service functions have been deprecated. They still work, but check any web service connections you may have to your Moodle for the future.

==Checking database schema - old sites==

If your Moodle site has been upgraded through many prior versions it is possible that there will be some problems with the database schema (compared to a fresh 2.0 installation). This may cause the upgrade to fail. If your site started life prior to Moodle 2.0 it is a very good idea to check and correct the database schema before upgrading. See [[Verify Database Schema]]. You should also run the database integrity checks in the XMLDB editor, see the 'See also' for a link to extra scripts to check for other discrepancies.

==Now upgrade==

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

On Linux servers, Moodle 2.2 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.

==After upgrade==

The config.php file from your 2.0 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.0 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.2 config-dist.php.

==See also==

* [[dev:Moodle 2.2 release notes|Moodle 2.2 release notes]]

[[fr:Mise à jour à Moodle 2.2]]
[[ja:Moodle2.2へのアップグレード]]

External database enrolment

2012-04-19T15:26:34Z

Mits:

{{Enrolment}}
Location: External database edit settings link in ''Settings > Site administration > Plugins > Enrolments > Manage enrol plugins''

You may use a external database (of nearly any kind) to control your enrolments. It is assumed your external database contains a field containing a course ID, a field containing a user ID, and optionally a field containing a role. These are compared against fields that you choose in the local course, user tables, and role tables.

The following are the supported data sources, but note that you will need to have to compiled PHP with the appropriate options or through [[ODBC]].

*access
*ado
*mssql
*borland_ibase
*csv
*db2
*fbsql
*firebird
*ibase
*informix72
*informix
*mysql
*mysqlt
*oci805
*oci8
*oci8po
*odbc
*odbc_mssql
*odbc_oracle
*oracle
*postgres64
*postgres7
*postgres
*proxy
*sqlanywhere
*sybase
*vfp

== Enrolment & Unenrolment ==

External database enrolment happens at the moment when a user logs into Moodle. The plugin will attempt to automatically enrol the student in all their courses according to the data in the external database and, optionally, create empty courses where they do not already exist. To check if it is working, you can log in as a student and then check that their list of courses is as you would expect.

The process also unenrols users from courses if they are no longer in the database. User records are marked according to their original enrolment method. Therefore the external database plugin can only unenrol users who were enroled by the plugin in the first place.

== Hidden Courses ==

Courses that are set to "Course is not available to students" can be ignored for enrolment purposes by setting the "enrol_db_ignorehiddencourse" to '''yes'''.

== Enrolment & Roles ==

The "enrol_db_defaultcourseroleid" setting in the plugin settings page specifies the role that the user will take when they are added to the course. The default setting will set them to the course default setting (initially "student"). However, you can specify a field in the external table (specified in the "enrol_db_remoterolefield" setting) that contains the short name for the user's role. This could, for example, be used to enrol both students and teachers into courses using a suitably configured database.

== Creating Courses ==

Optionally courses that do not exist in the Moodle site can be created. Switch the "enrol_db_autocreate" option to "yes" in the plugin settings. You can additionally specify the Category into which the new course will be placed and may also specify a "template" course from which the new course will be copied.

== Synchronization Script ==

A script is provided that can synchronize all your user enrollments at once - both adding and removing user enrolments (and creating courses if specified). The script is called enrol_database_sync.php and is found in the enrol/database folder.

This script is meant to be called from a system cronjob to sync moodle enrolments with enrolments in the external database. You need to make sure all the users present in the external enrolments are already created in moodle. If you are using external authentication plugins (db, ldap, etc.) you can use the scripts provided by those plugins to synchronize your users before running this script.

Example cron entry for Moodle 2.0
# 5 minutes past 4am
5 4 * * * /usr/bin/php -c /path/to/php.ini /path/to/moodle/enrol/database/cli/sync.php

Notes:
* If you have a large number of enrolments, you may want to raise the memory limits by passing -d memory_limit=256M
* For debugging & better logging, you are encouraged to use in the command line: -d log_errors=1 -d error_reporting=E_ALL -d display_errors=0 -d html_errors=0
* This only works for users that already exist in your Moodle site (see comment above)

== Setting It Up (How to) ==

You will need to perform (as a minimum) the following steps to enable external database enrolment - only a single table is required in the database which contains a record for every user/course combination. If the table is large it is a good idea to make sure appropriate indexes have been created:

* Use an existing database or create a new one. Use an existing or create a new table with the following minimum fields:
** course identifier (to match unique course identifier in Moodle)
** user identifier (to match unique user identifier in Moodle)
** (optional) role identifier (to match unique role identifier in Moodle)
* Populate the database table. Each user/course combination to have a record in the table
* In Moodle, go to Site Administration => Courses => Enrolments, find External Database in the list and click Settings
* In the top panel, select the database type (make sure you have the necessary configuration in PHP for that type) and then supply the information to connect to the database.
* The middle panel creates the mapping between Moodle and the external database. The first three settings are for the local (Moodle) field names and the last three for the remote (external database) settings. They are in the same order.
** enrol_localcoursefield / enrol_remotecoursefield - in Moodle the name of the field in the course settings the uniquely identifies the course (e.g., idnumber). In the external database the name of the matching field.
** enrol_localuserfield / enrol_remoteuserfield - in Moodle the name of the field in the user profile that uniquely identified the user (e.g., idnumber). In the external database the name of the matching field.
** enrol_db_localrolefield / enrol_db_remoterolefield - (optional) in Moodle the name of the field in the role edit page the uniquely identifies the role (e.g., shortname). In the external database the name of the matching field.
* The Roles panel specifies the role that the user will get in the course if their role is not specified in the external database.
* The final panel enables auto creation of courses.
* Save changes, and then tick the box to enable external database enrolment.

== Database enrolment does not appear in the course enrolment drop down menu. Why? ==

The course enrolment drop down menu only lists [[Enrolment_plugins#Interactive_enrolment|'''interactive''' enrolment plugins]]. External database enrolment is not such a plugin, so it doesn't appear in the list. Similarly, the "Course Enrollable" setting (in the Course Settings) page also only applies to interactive enrolment plugins and has no effect on external database enrollment.

As of this writing, the only interactive enrolment plugins are ''manual'' (also know as ''internal''), ''paypal'' and ''authorize.net''.

== Field Mapping Example: ==
Choose your fields from the Moodle database:

*enrol_localcoursefield: A course identifier from mdl_course, e.g. "idnumber"
*enrol_localuserfield: A user identifier from mdl_user, e.g. "idnumber"
*enrol_localrolefield: (optional) A role identifier from mdl_role, e.g. "shortname"

Create a view in your external database which matches the chosen field values from Moodle:

*enrol_remotecoursefield: A matching course identifier from your external database table, e.g. "course_number"
*enrol_remoteuserfield: A matching user identifier from your external database table, e.g. "userid"
*enrol_remoterolefield: (optional) A matching role identifier from your external database table, e.g. "role_name"

== Potential Gotchas ==

* It almost goes without saying that the integrity of the external database is important. If data is missing from the database then there is a potential for users being unenrolled from some or all of their courses. The unenrollment process will remove them from any group assignments and also poll each module type to give the module the option of removing that user's data if appropriate (for example, however, forum posts are never deleted). It is therefore prudent that you take the utmost care to ensure that the data in the external bass is correct at all times.
* '''Minor Security Issue''' Consider that if the ID field you use to identify your students is editable by the students (in their profile), then there is a potential for them changing this to the id of another valid student and gaining access to resources that they should not. However, they will still appear as themselves, they cannot impersonate the other user or otherwise gain access to their resources.

==Errors and Diagnostics==

The plugin produces a number of diagnostic messages and/or errors which are recorded to the PHP error log (as defined in the php.ini file). In addition messages about courses that are in the database for the user but that do not exist in the Moodle site will only be produced if debugging is set to ALL or DEVELOPER.

==See also==
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=49475 MySQL enrolment plugin doesn't seem to work] forum discussion
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=74133 Someone explain external database enrolment, please??] forum discussion
*Example Setup [https://docs.moodle.org/en/Talk:External_database_enrolment#Example_External_Enrollment] Example Database Enrollment Setup

[[es:Matriculación Base de Datos Externa]]
[[fr:Base de données externe]]
[[de:Einschreibung über externe Datenbank]]
[[ja:外部データベース登録]]

Manual enrolment

2012-03-09T16:09:14Z

Mits: ja link

{{Enrolment}}
The manual enrolments plugin allows users to be enrolled manually via a link in the course administration settings. The plugin has to be enabled by the site administrator (see [[Enrolment plugins]]) and should normally be enabled as certain other enrolment plugins, such as self enrolment, require it.

==Course settings==
===Checking you have manual enrolment in your course===
*In a course, go to ''Settings > Course administration > Uusers > Enrolment methods''
*Make sure Manual enrolments has its "eye" opened:

[[File:Manualenrolments.png]]

===Editing the manual enrolment method===

Managers (and any other users with the capability [[Capabilities/enrol/manual:config|enrol/manual:config]]) can edit the manual enrolment method in the course and set the default enrolment period and default role in ''Settings > Course administration > Users > Enrolment methods''.

[[File:Defaultenrolmentperiod.png]]

==Admin settings==
*Default settings for manual enrolment in courses may be specified in ''Settings>Site administration>plugins>enrolments>Manual enrolments''. These are:
**Add instance to new courses- if this is enabled, then whenever a new course is created, manual enrolments will automatically be enabled
**Enable manual enrolments - this makes this plugin available throughout Moodle and it is advisable to do this.
**Default enrolment period - this sets the default length of enrolment (in seconds) and may be altered by a teacher in a course.
**Default role - this sets the default role, which is normally student but may be altered by a teacher in a course.

==Manual enrolment capabilities==

*[[Capabilities/enrol/manual:config|Configure manual enrol instances]]
*[[Capabilities/enrol/manual:enrol|Enrol users]]
*[[Capabilities/enrol/manual:manage|Manage user enrolments]]
*[[Capabilities/enrol/manual:unenrol|Unenrol users from the course]]
*[[Capabilities/enrol/manual:unenrolself|Unenrol self from the course]]

==See also==

* [[Enrolled users]] including option to manually enrol a user in the course

[[de:Manuelle Einschreibung]]
[[ja:手動登録]]

Capabilities/enrol/manual:config

2012-03-06T15:13:44Z

Mits: ja link

{{Capabilities}}
*This allows a user to edit the [[Manual enrolment]] method and set the default enrolment period and default role in ''Settings > Course administration > Users > Enrolment methods
*This capability is allowed for the default role of manager only

[[File:Defaultenrolmentperiod.png]]

[[Category:Capabilities|Enrol]]
[[Category:Enrolment]]

[[ja:ケイパビリティ/enrol/manual:config]]

Category enrolments

2012-02-24T17:56:48Z

Mits: ja link

{{Enrolment}}

The category enrolments plugin allows users to be enrolled in a category as opposed to individual courses. The plugin has to be enabled by the site administrator (see [[Enrolment plugins]]).

Note: It is recommended that [[Cohort sync]] is used in preference to category enrolments.

==Settings for category enrolment==

*Go to the category into which you wish to enrol users. '''Note:''' You need to have category rights (manager or administrator)

*In the ''Settings'' box,click ''Assign roles''. The list of possible roles you can assign will appear:
[[File:Categoryassign.png]]

== Admin settings for category enrolment==

The category enrolment plugin may be enabled or disabled throughout the site in ''Settings > Site administration > Plugins > Enrolments> Manage enrol plugins.''

===Assigning teachers or students to a category===

*By default, only managers and course creators can be assigned category-wide. If you want to add teachers or students then the site administrator needs to tick the "category" box in their role in ''Settings > Site administration > Users > Permissions > Define roles''.
*To ensure they will be automatically assigned as teachers/students in any new courses you make, the administrator needs to set to "allow" the capability ''enrol/category:synchronised'' for the role in question in ''Settings > Site Administration > Users > Permissions > Define roles''

[[File:Enrolcategorysync.png]]

[[ja:カテゴリ登録]]

Cohort sync

2012-02-15T15:30:11Z

Mits: ja link

{{Enrolment}}
Cohorts, or site-wide groups, enable all members of a cohort to be enrolled in a course in one action, either manually or synchronised automatically.

==Enrolling a cohort in a course==

In order to actually enrol users from a Cohort into courses the ''Cohort-Sync'' Enrollment plugin needs to be added to the enrollment methods for the course. The Administrator will first need to enable the ''Cohort-Sync'' enrolment plugin site wide (''Settings > Site administration > Plugins > Enrolments'') and then add it to the required Course: (''Settings > Course administration > Users > Enrolment Methods'').

[[File:Cohortsync.png]]

At this stage the ''Cohort-Sync'' instance for the course is edited and the appropriate Cohort selected. The role to which the Cohort users are assigned is also selected at this point (typically Student).

Visiting the ''Settings > Course administration > Users > Enrolled Users'' page will show users enrolled via the ''Cohort-Sync'' plugin.

Note that, by default, a teacher cannot add this plugin to their course. It needs to be configured by an Administrator or a user with the Manager role.

The required capabilities for setting up a cohort sync are:
* moodle/course:enrolconfig in the course context
* moodle/cohort:config in the course context
* moodle/cohort:view in the same context as category

The required capabilities for manually enrolling cohort members are:
* the same as cohort sync (note: this is a bug MDL-28431)
* enrol/manual:enrol in course context
* moodle/course:enrolreview in course context

==See also==

* [[Cohorts]] for information on how to create a cohort

[[de:Einschreibung über globale Gruppen]]
[[ja:コーホート同期]]

Cohorts

2012-02-14T15:20:08Z

Mits: ja link

{{Grouping users}}
Cohorts, or site-wide groups, enable all members of a cohort to be enrolled in a course in one action, either manually or synchronised automatically.

==Creating a cohort==

Cohorts can be created by site administrators and other users with appropriate permissions.

* Access ''Settings > Site administration > Users > Accounts > Cohorts''
[[File:Createcohort.png]]
* Click the Add button
*'''NOTE''' In the dropdown you can choose between making your cohort available throughout the site "system" or in a named category.
*Complete the details and save the changes.
* Follow the assign link opposite the cohort name in the list of available cohorts.
[[File:Assigncohort.png]]
* Select potential users from the list then click the Add button.

To synchronise cohort members with course participants, the [[Cohort sync]] enrolment plugin should be enabled in ''Settings > Site administration > Plugins > Enrolments > Manage enrol plugins''.

==Adding users to a cohort in bulk==

{{New features}}#Access ''Settings > Site administration > Users > Accounts > Bulk user actions''
#Find users by setting an appropriate filter
#Add users from the available list to the selected list
#Choose 'Add to cohort' with selected users

==Uploading users to a cohort==

{{New features}}An administrator can upload users via CSV file to existing cohorts as follows:
#Access ''Settings > Site administration > Users > Accounts > Upload users''
#Upload a text file with the following format:

username,password,firstname,lastname,email, cohort1
tomjones,Pass1234*,Tom,Jones,tomjones@example.com, year3
marysmith,Pass1234*,Mary,Smith,marysmith@example.com, year4

where year3 and year4 are the '''cohort ids''' of existing cohorts (i.e. ''not their names'')

==See also==
*[http://www.youtube.com/watch?v=FMWZW_n0eVI A three minute Cohort in Moodle 2.0 video]
*[http://www.youtube.com/watch?v=dMqaeOGXuHQ Cohorts in Moodle 2.0 video]
*[http://www.somerandomthoughts.com/blog/2011/11/22/using-cohorts-with-moodle-2-2/ Using cohorts with Moodle 2.2] blog entry by Gavin Henrick

[[Category:Site administration]]

[[fr:Cohortes]]
[[de:Globale Gruppen]]
[[ja:コーホート]]

HTTP

2012-01-23T16:09:44Z

Mits: ja link

{{Server settings}}
An administrator can change the following settings in ''Settings > Site administration > Server > HTTP''.

==Use slash arguments==

You will need to change this setting only if you are having trouble viewing files or images. Most of the time, Moodle will display files and pictures with no problem using the slash arguments. If you get errors when you try to view pictures or files from within Moodle, your PHP server doesn't allow the slash argument method and you will need to disable this setting.

==Proxyhost and proxyport==

Your Moodle server may need to access the Internet through a proxy server, depending on your network configuration. If you're not sure about whether you need a proxy server, contact your network administrator or ISP.

[[ja:HTTP]]

Cleanup

2012-01-19T15:56:30Z

Mits: ja link

{{Server settings}}
An administrator can limit the size of certain tables in the database by setting appropriate options in ''Settings > Site administration > Server > Cleanup''.

==Delete unconfirmed users after==

If you're using [[Email-based self-registration]] users must confirm their account within a certain time-frame. Once the time set here has passed, any account that hasn't been confirmed will be deleted. 7 days is a good setting.

==Delete incomplete users after==

The period after which old not-fully-set-up accounts are deleted may be set (from 1 day to never).

(What is the definition of a "not-fully-set-up account"? What criteria needs to be met for an account to be fully-set-up?)

==Keep logs for==

Moodle keeps extensive logs of user activity. Eventually, however, the logs will become so large that they begin to clog your server. Limiting the length of time logs are kept for will reduce database table size. Generally, a year is enough time to keep logs for.

==Disable grade history==

History tracking of changes in grades-related tables may be disabled by checking the ''disablegradehistory'' box.

==Grade history lifetime==

The length of time that the history of changes in grade-related tables is kept may be set (from 30 days to never).

==Unsubscribe users from courses after==

Note for users who have upgraded to Moodle 2.0 from 1.9: The setting 'Unsubscribe users from courses after' in Cleanup has been replaced by 'Unenrol inactive after' in [[Self enrolment]].

==See also==

*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=87795 How do I prune mdl_log table?] forum discussion

[[eu:Garbiketa]]
[[fr:Nettoyage]]
[[ja:クリーンアップ]]

Session handling

2012-01-13T16:03:37Z

Mits: ja link

{{Server settings}}
An administrator can change the following settings in ''Settings > Site administration > Server > Session Handling''.

==Timeout==

Once someone logs in to your Moodle server, the server starts a session. The session data allows the server to track users as they access different pages. If users don't load a new page during the amount of time set here, Moodle will end their session and log them out.

Be sure this time frame is long enough to cover the longest test your teachers may offer. If a student is logged out while they are taking a test, their responses to the test questions may be lost.

==Cookie prefix==

Most of the time, you can leave this blank, unless you are running more than one Moodle site on the same server. In this case, you will want to customize the name of the cookie each Moodle site uses to track the session. This enables you to be logged into more than one Moodle site at the same time.

Note: If you change "Cookie prefix" or "Cookie path" you will need to login again as the changes take effect immediately.

==See also==

*[[Sessions FAQ]]

[[cs:admin/setting/sessionhandling]]
[[ja:セッションハンドリング]]

System paths

2012-01-07T15:29:59Z

Mits: ja link

{{Server settings}}
An administrator can set the following system paths in ''Settings > Site administration > Server > System Paths''.

==GD version==

GD is a graphics library that manipulates graphics. It's used to create thumbnail images from uploaded files and other graphics on the fly. If you don't know what version is installed, leave this on the original setting.

'''Note''': When setting the system paths on Windows systems, use of the 8.3 notation for the path and filename is preferred. So instead of entering ''c:\program files\path to aspell\aspell.exe'', enter ''c:\progra~1\path~1\aspell.exe''. Check the exact 8.3 path using the ''dir /x'' command at the prompt.

==Path to aspell==

If PSpellSpell is selected as the spell engine for TinyMCE in ''Settings > Site administration > Plugins > Text editors > TinyMCE HTML editor'' then you must specify the correct path to access the aspell binary.

In addition, you MUST have aspell 0.50 or later installed on your server. On Unix/Linux systems use the which program to determine the path:

[root@moodle ~]# which aspell
/usr/bin/aspell

In this example the path to enter is ''/usr/bin/aspell''.

On a Windows system, download and install [http://aspell.net/win32 GNU aspell] together with at least one dictionary and then use the search facility in Explorer to find the aspell.exe file. The path should look like:

c:\program files\aspell\bin\aspell.exe

It can be best to install aspell in c:\aspell or use the 8.3 notation if you are installing in ''c:\program files'' so that the path looks like

c:\progra~1\aspell\bin\aspell.exe

==Path to dot==

Path to dot is for enabling image generation in profiling. The generated graphs are really useful to see what each request does. To have profiling visible (and working), the xhprof extension must be installed in PHP.

==External links==

*[http://aspell.sourceforge.net/ GNU Aspell]
*[http://aspell.net/win32/ GNU Aspell (Win32 version)]

==See also==

* [http://moodle.org/mod/forum/discuss.php?d=125912 HowTo: Installing aspell in Ubuntu (with dictionary)] forum discussion

[[cs:admin/setting/systempaths]]
[[hu:Rendszerútvonalak]]
[[ja:システムパス]]

Book module

2011-10-22T15:12:30Z

Mits: ja link

{{Book}}

The '''Book module''' makes it easy to create multi-page resources with a book-like format. It is contributed by [http://moodle.org/user/view.php?id=12863&course=5 Petr Škoda]. This module can be used to build complete book-like websites inside of your Moodle course.

Previously created websites can be imported directly into the Book module. Books can be printed entirely or by chapter.

The book module allows you to have main chapters and sub chapters, but it goes no deeper. In other words, sub chapters cannot have their own sub chapters. This was an intentional decision by the creator of the book module. He intended this to be a simple resource for teachers and students.

The book module is not interactive. You can, however, link to [[Choice module|choices]], [[Forum module|forums]] etc., from within a book. And you can include multimedia objects like [[Flash]] movies in your book.

==Books and Moodle 2.0==
The latest code is here: https://github.com/skodak/moodle-mod_book

===Can I duplicate a book within a course?===
Use the Sharing Cart. See [http://moodle.org/mod/forum/discuss.php?d=167624 Discussion:Duplicating a book within a course]

===Can I shift Books from one Moodle 2 server to another Moodle 2 server?===
Not using the backup and restore. This is not written yet. (as of 19th February 2011)

It is possible to export as an IMS package and make a couple of tweaks and then import. https://docs.moodle.org/en/IMS_content_package

==Installation==
* Select the correct version of the "book.zip" module for your Moodle installation
* Unpack the zip file into the mod folder of your Moodle site
* Login to the Moodle site as administrator and
* In site administration block click on notifications
* Moodle will install the Book module.
* [[Creating_a_book|Add a book as an activity]]

==See also==
*[http://moodle.org/mod/data/view.php?d=13&rid=319 Book Module] is a Modules and plugins database page for downloads and more information.
*Discussions: please create or find a discussion topic in the [http://moodle.org/mod/forum/view.php?id=2633 Book module forum]
*Examples: The manuals at [http://moodle.tokem.fi tokem.fi] are a series of book modules. Each book is designed for a different level of Moodle user.
* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=76092 Using a Lesson to simulate a Book] forum discussion
* [http://tracker.moodle.org/secure/attachment/23370/Moodle+Procedure+Set+up+a+Moodle+Book+and+copy+it.pdf Procedure for setting up a Book] pdf from Frances Hill

[[Category:Contributed code]]

[[es:Book]]
[[eu:Liburua]]
[[ja:ブックモジュール]]

Course files

2011-10-19T16:26:25Z

Mits: ja link

{{Working with files and folders}}
This page explains the legacy "Course files" area in Moodle 2, and related topics.

It's useful for any teacher who wants to know how to add files to a Moodle 2.0 course (especially if you previously used Moodle 1.9 or earlier).

==Files in Moodle 1.9==

In versions of Moodle before 2.0 all the files uploaded into Moodle were stored in a physical directory on disk known as the "Course files" area.

This is where a teacher might upload files to be part of the course content, but this area also included everything students uploaded, such as assignments and forum attachments. These "activity files" were stored in a special folder called ''moddata'' in a certain structure that helped modules keep track of their own files.

===Typical Moodle 1.x workflows===

The course files area was accessed in two ways through the Moodle interface by teachers.

# Through the "Files" link in the Course Administration block, or
# When a file was required in other places, such as a resource, or attachment.

When publishing a file as a resource, say a PDF file, a teacher might:

# Upload it to their course files area along with all the other files they intend to use in the course
# Add a resource to the course
# Select the PDF from the course files

Students did not have direct access to read the course files area. All they could do was upload files from their desktop computer straight into activities.

===A less typical workflow===

# Use [[wikipedia:FTP|FTP]] to push files straight into the course files area
# Add resources to the course by selecting these files
# Update the resources later by updating the files directly via FTP

This meant expert users could update course content with files or HTML mini-sites without having to change anything in Moodle.

===Problems with the Moodle 1.x model===

* If the original file was deleted from course files area, or renamed, it would result in broken links everywhere where it was previously used
* Storing files on disk meant file names were restricted (eg file names in Japanese would break on some operating systems)
* All course files had to be readable by students (if they knew the URL) because Moodle had no way of telling what context you were viewing a file in (eg the same file might be in a HTML text in a forum and also in a resource). This meant that files stored in the course files area were not as secret as teachers thought they were.
* Files could not be reused in several courses - that had to be uploaded to each course files area
* Backups had to include ALL course files, just in case they were required, even if the backup only contained one activity
* Images and other media might look fine for teachers, but others would not see it (eg in course descriptions)
* When importing activities from one course to another, ALL course files were imported, as it was impossible to tell which files were needed

==Files in Moodle 2.0==

In Moodle 2.0 the files work a lot more like Web 2.0 systems, such as Facebook and Google Docs.

Each activity and each text has its own file area, and files are associated directly with the place it is used. For example, a file attached to a forum post is stored "with" the forum post, and becomes subject to exactly the same access restrictions.

The Files system is intimately connected with the Repository system, and a file picker which makes it easy to browse external and internal repositories for files, and then copy them into Moodle. Certain repositories also allow you to link directly to their media files. Repositories in general are the way of the future for content - most Web 2.0 systems are really repositories of data with various management interfaces.

A private files area is provided for each user to store a collection of files for their own use. This is useful for students as well as teachers, and makes it easy to re-use media across the Moodle site. Only you can access your own private files.

The course files area in Moodle 2.0 is [[wikipedia:Deprecation|deprecated]] and is not available by default due to the problems described above. When a site is upgraded from 1.9, all course files are migrated into new file areas and the old course files area is hidden from view.

Internally, files are stored in a "file pool" of blobs on disk with numbers for names. All the actual names and metadata are stored in a database.

===Typical Moodle 2.0 workflow===

# Edit a text or activity
# Use the filepicker 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.

===More advanced Moodle 2.0 workflow===

# Edit a text or url resource
# Use the filepicker to easily select the 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.

===Why is it better?===

====Integrity====

If a forum post with attached files (eg images) is imported into another course, then the files move with it. Anyone in the new course will also see the files. This makes activities more portable and re-usable.

If two activities use the same file and one is deleted, then the other one is not affected.

There should be less problems with everything looking fine for teachers and not appearing for students.

====Security====

Access to files is governed the same way as the items that they attached to, which is what people expect. All files are now controlled by the settings in the Moodle interface, including roles and permissions.

====Re-usability====

It is now fast and easy to re-use files across Moodle. Using the file picker, a recently-used file may easily be chosen, or a file from any course a user has access to.

====Backups====

Backups of activities are small and accurate, because Moodle knows exactly what files to include. This is important for things like [[Community hubs]], where sharing of courses and parts of courses will become more common, and sharing every file in a course may be unacceptable.

====Internationalization====

There are no restrictions on file names - even files with names in Japanese may be used.

====Repositories====

The world is turning towards better management of files and less "dumping" of files into disks. There are many repository solutions out there that focus on better management of files, with versioning, workflow, metadata and other features.

===How to duplicate Moodle 1.x functionality in 2.0===

If you really want to mimic older workflows in 2.0 then there are some solutions, although none of them are exactly the same.

====FTP files into Moodle====

# One way to do this is via the [[admin/repository/filesystem|File system repository]]. This allows you to turn a directory on the server into a repository of files within the Moodle file picker. You can then use any server technology to access that directory from a desktop, such as FTP, [[wikipedia:Samba (software)|Samba]], [[wikipedia:AppleShare|Appleshare]] or [[wikipedia:WebDAV|WebDAV]].
# See the direct WebDAV plans below.

====Change a file once, have it update in many places====

# If you use an external repository that supports linking (such as Alfresco) then you get this behaviour for free. Files in the repository can not have exactly the same access control as Moodle, but they can implement their own access control, especially if you use some sort of single sign-on.
# If you enable the [[Legacy course files]] feature in Moodle 2.0 then you can also link directly to files there using the Course files repository in the file picker. Even HTML mini-sites work. The caveat is that it only works in places where you can '''link''' to files. So, for example, it won't work for a forum attachment or the 'resource' module. But it will work for the url module (new in 2.0) and any media embedded in HTML via the editor.

==Roadmap for future improvements==

Based on recent feedback, there are plans to improve the model in 2.0 with new features.

===File synchronization===

Instead of having to choose between linking to a course file or copying it to the current file area, we could add the option to 'Always use the latest version' of the file. This would re-copy the file to the destination whenever the source file changed. Initially this would be implemented just for the internal repositories but could also be used later for some external repositories as well (those not requiring the Moodle site to authenticate as the user).

This feature has the potential to maintain all the benefits of the 1.0 model without compromising the 2.0 model.

However this feature is complex to implement because:

* We need to cope with changing permissions in source and destination.
* We need to cope with cases like Assignment submissions (students shouldn't be able to update files after the due date, for example)
* We need some GUI solution to synchronize whole folders at once, such as a HTML mini-site.
* We need some in-GUI solution to report what the source file is for any given destination file.

===Linking ability to File system repository===

The File system repository currently does not allow linking to files. This is because the files are in a directory inside moodledata and are not exposed by any direct URL from the web.

To serve them to the web we'd have to have some script like ''/repository/filesystem/file.php'' to serve them as links, which would allow relative links like HTML mini-sites to work.

The problem with this is that we are back to the same issues as 1.9 course files (or even worse), with no access control on the files at all. Some people may not care about this, but the solution needs to make this very clear to users.

===WebDAV support for course files and user files===

This would effectively replace direct FTP access to the file system with WebDAV access to the "virtual" file system inside these file areas in Moodle. It would allow people to update files without going near the web GUI.

==See also==

* MDL-23306 META: Improve usability of new files structure
* [http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 Course Backup Filearea] Using Moodle forum dicussion
* [[Legacy course files]]

[[fr:Fichiers de cours]]
[[ja:コースファイル]]

Git for Administrators

2011-10-09T16:52:22Z

Mits: ja link

An alternative way to maintaining your Moodle server via [[CVS for Administrators|CVS]] is using Git. This page describes how to maintain a copy of Moodle on your production server which can easily be upgraded using Git. If you have customisations of Moodle core code, you are advised to follow the instructions in the [[Development:Quick Git start guide for Moodle development|Quick Git start guide for Moodle development]].

== Obtaining the code from Git ==

You can find the official Moodle git repository at git://git.moodle.org/moodle.git (with an official clone at git://github.com/moodle/moodle.git). To initialize your local checkout, use

git clone git://git.moodle.org/moodle.git (1)
cd moodle
git branch -a (2)
git branch --track local_19_STABLE origin/MOODLE_19_STABLE (3)
git checkout local_19_STABLE (4)

The command (1) initializes the new local repository as a clone of the upstream moodle.git repository. By default, this upstream repository will be known as 'origin' remote repository. The command (2) lists all available branches. Use the command (3) to create a new local branch called local_19_STABLE and set it to track the branch MOODLE_19_STABLE from the upstream repository. The command (4) actually switches to the newly created local branch. Note that the last two lines can be replaced with

git checkout -b local_19_STABLE origin/MOODLE_19_STABLE (3 + 4)

that creates a new local tracking branches and switches to it immediately.

== Updating your installation ==

The Moodle development team performs integration and testing of fixed bugs every Monday and Tuesday. On Wednesday you can install all patches by updating your code. Check the [http://git.moodle.org/gw?p=moodle.git;a=summary shortlog] to see if the official repository has been already updated or not.

cd /path/to/your/moodle/checkout
git fetch (1)
git status (2)
git merge (3)

The command (1) downloads new updates from the remote repository without touching your local checkout. The command (2) displays the information about the eventual drift between you local version and the upstream one. The command (3) actually modifies your local files with the updates. The git-fetch + git-merge couple can be replaced with a single command

git pull (1 + 3)

== Installing a contributed extension from its Git repository ==

For example, let us say we want to install the [[Book module]] form its Git repository into our Moodle 2.0.

cd /path/to/your/moodle/checkout
cd mod (1)
git clone git://github.com/skodak/moodle-mod_book.git book (2)
cd book
git checkout -b MOODLE_20_STABLE origin/MOODLE_20_STABLE (3)
git branch -d master (4)

The command (1) changes the current directory into the ''mod'' folder of your local Moodle clone. The command (2) creates a new subdirectory ''book'' and makes a local clone of Petr Škoda's vanilla Book repository. The command (3) creates a new local branch that will track the remote branch with a Book version for Moodle 2.0. The command (4) deletes the ''master'' that was created automatically by git-clone in (2) as we do not want it in this production checkout.

Now it is wise to put the new directory mod/book/ to the list of ignored files of the main Moodle clone.

cd /path/to/your/moodle/checkout
echo /mod/book/ >> .git/info/exclude

To update your Moodle installation now, you must visit both Git repositories and pull changes from upstream.

cd /path/to/your/moodle/checkout
git pull
cd /path/to/your/moodle/checkout/mod/book
git pull

Writing a shell script with these lines in the root of Moodle installation is a very good idea. Otherwise it is easy to forget what Git repositories are there within the main Moodle repository.

== See also ==

; Moodle Docs
* [[CVS for Administrators]]
* [[Moodle versions]]
* For some screenshots see [[User:Frank_Ralf/Git]] (still work in progress)

; Moodle forum discussions
* [http://moodle.org/mod/forum/discuss.php?d=168094 GIT help needed]
* [http://moodle.org/mod/forum/discuss.php?d=165236 Best way to manage CONTRIB code with GIT]
* [http://moodle.org/mod/forum/discuss.php?d=167063 Handy Git tip for tracking 3rd-party modules and plugins]
* [http://moodle.org/mod/forum/discuss.php?d=167730 Moodle Git repositories]
* [http://moodle.org/mod/forum/discuss.php?d=183693 Git and CVS]

; External resources
* [http://www.kernel.org/pub/software/scm/git/docs/everyday.html Everyday GIT With 20 Commands Or So]
* [http://gitref.org/ Git Reference]
* [http://progit.org/book/ Pro Git book]

[[Category:Git]]
[[Category:Administrator]]

[[ja:管理者用Git]]

Upgrading

2011-09-09T02:18:27Z

Mits: ja link

Moodle is designed to upgrade itself from one version to the next. The procedure is
# [[Site backup|Back up everything]].
# Replace the old version of the code with the new one.
# Visit the [[Site_administration_block#Notifications|administrator notifications]] link, which triggers Moodle to self-update.
These steps are explained in more detail below.

Sometimes there are specific considerations when upgrading to a particular version. See the [[dev:Releases|Releases page]] for more information on this. You also have to be more careful if you have installed additional plug-ins or customised the code.

See this tutorial if you are [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf upgrading Moodle on cpanel]. It is a bit rough around the edges and is a little dated, but you should get the idea.

There is also a separate page about [[Ubuntu_Debian_Upgrades|upgrading Moodle if you installed it using the Ubuntu/Kubuntu/Debian package manager]].

__TOC__

When upgrading a Moodle installation you should follow these steps:

==Before you upgrade your site for real==

You are strongly advised to make a copy of your entire Moodle site onto another computer (see [[Moodle migration]]) and run the upgrade there to verify it will work.

==Check the requirements==
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the target version you want to upgrade-to in ''Administration > Server > [[Environment]]''.
==Put your Site into Maintenance Mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | Maintenance Mode]] to stop any non-admin users from logging in.

== Backup important data ==
See [[Site backup]] for more specific information.

There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, the SQL or Postgres database)

Experienced site administrators know that it is a best practice (a very good idea) to make a backup of any production system before a major upgrade. In fact, it is a good idea to automate your server to backup your Moodle installation daily. Most upgrades on sites that have used the standard Moodle packages (no contributed code and no little tweaks to the php files), will not have any major issues with the upgrade process.

:''TIP:'' One more time, "do not risk what you can not afford to lose": do regular backups, make sure it is really backed up and know how to restore a backup!

== Install the new Moodle software ==
Upgrading can be a simple process or a more complicated process. Sites that have not used contributed code and are migrating from say Moodle 1.x.1 to 1.x.3 '''should''' not have a problem. However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files.

*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.

=== Standard install package ===
Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.
*It is probably a good idea to use the [[Site administration block]]>Server>Maintenance mode to prevent user activity as the site upgrades.
*Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and [[Moodledata directory|moodledata]] if it needs to in the upgrade.
*Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
*If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet).
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress.
*After a successful upgrade, turn off the maintenance mode, so your users can get into the site.

=== Using a downloaded archive ===
In some installs, the site administrator may overwrite the Moodle code with a backup copy. Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders).

*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or "cleaned" installations. The best way is to rename the current Moodle code directory (for example rename "moodle" to "moodleold"), then unpack the new Moodle archive into the old location (for example, a new directory called "moodle").

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

Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one ('''check that optional/custom plugins are the correct version for your new Moodle first'''):

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

Don't forget to

sudo chown www-data moodle/config.php

if necessary.

where www-data is whatever user the Apache user is on your system. This is often 'apache' or 'www'.
You can find out by doing 'ls -l' in your /var/www/moodle folder (or wherever your moodle site is)
and then looking at the owner and group.

so you may see something like

ls -l
...lots of lines...
-rw-r--r-- 1 apache system 784 Jun 28 2007 config.php
...lots more lines...

so the owner is apache and the group is system.

To replicate this on your new system you can do 'chown apache:system config.php'

or to do a whole group do

chown apache:system ./*

and recursively

chown -R apache:system ./*

=== Using CVS ===

You can use CVS for updating or upgrading your Moodle.
First you need to do a CVS checkout in your (empty) Moodle root directory.

You can use any of our [[CVS_for_Administrators#CVS_Servers|CVS Mirror servers]]. Just replace '''SERVER.cvs.moodle.org''' in the instructions below with the name of the mirror server you chose!.

====For Linux servers====

To do a CVS checkout of Moodle, you first have to logon to the Moodle CVS server.

<nowiki>cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login</nowiki>
No password for anonymous, so just hit the Enter button.

Go to the directory where you want the Moodle root to come and type

<nowiki>cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -r MOODLE_18_STABLE moodle</nowiki>
(where MOODLE_18_STABLE is the desired version)

To update, just go into the Moodle root directory and update to the new files:

cvs update -dP
To update to a new version type in the following and change 18 to whatever newest version upgrade number is
cvs -Q update -dP -r MOODLE_18_STABLE

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

====For Windows servers====

You can use Tortoise CVS to do the initial checkout and the updates.

If you have been editing Moodle files, watch the messages very closely for possible conflicts. All your customised themes and non-standard plugins will be untouched.

Do not forget to trigger the install process in the site administration block (see below).

=== Using Git ===

You can use [[Git]] for updating or upgrading your Moodle.
First you need to do a Git checkout in your (empty) Moodle root directory.

See [[Git for Administrators]] for further details.

== Finishing the upgrade ==

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

To do this just visit the [[Site administration block]] admin page (or ''<nowiki>http://example.com/moodle/admin</nowiki>'') and the "Notifications" link.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

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

:''TIP:'' Use the site administration block>Server>Maintenance mode to prevent users from changing data during the upgrade.
:''TIP:'' If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing. Post a thread or check the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and check [[Tracker]] for potential issues.

== Verify the upgrade (optional) ==

If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].

==Upgrading more than one version==

In general, it is recommended to upgrade via the newest of each major version of Moodle, for example 1.7 -> 1.9. An exception to this is when upgrading from 1.5 or 1.6, when it is recommended that 1.7 and 1.8 are skipped, in other words upgrade 1.5 -> 1.6 -> 1.9. (The main reason for this recommendation is that the default roles settings obtained when upgrading to 1.7 are not ideal for 1.8 onwards, 1.8 has problems with groups, etc.)

==See also==

*[[Installing Moodle]]
*[[Installation FAQ]]
*[[Upgrading to Moodle 1.6]]
*[[Upgrading to Moodle 1.8]]
*[[Upgrading to Moodle 1.9]]
*[[Upgrading to Moodle 2.0]]
*[[Environment]]
*[[Git]] Version control and upgrading
*Moodle.org [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
*[http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial] - screencasts of older Moodle/Cpanel install but useful (also, a very large file that will take some time to load).

Using Moodle.org forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
*[http://moodle.org/mod/forum/discuss.php?d=56915 Upgrading from 1.5.2 to 1.7]
*[http://moodle.org/mod/forum/discuss.php?d=56991 Upgrade nightmares.... any help appreciated]
*[http://moodle.org/mod/forum/discuss.php?d=62463 After upgrading i get "Your site may not be secure." msg]
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]
*[[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration]]

[[Category:Installation]]

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[nl:Upgraden]]
[[zh:升级]]
[[pl:Aktualizacja]]
[[de:Aktualisierung von Moodle]]
[[ru:Обновление]]

Dropbox repository

2011-09-07T02:40:03Z

Mits: ja link

{{Repositories}}
A Dropbox repository can be enabled by a site administrator in ''Settings > Site administration > Modules > Repositories > Manage repositories''.

==Sign up app keys at dropbox==

# Go to https://www.dropbox.com/developers/apps
# Create an app, you must change app status to Production. This feature is only availble for new API developers, but not for Moodle repository users. See MDL-26949
# Copy the app keys (scroll if necessary)

NOTE: The only way to get App stats for Production approved is to use an acceptable App name. The App name should be something like "Moodle With Dropbox" - with dropbox is the key part of the name (can't just use dropbox). Otherwise, you'll receive an email that says "Your app name does not follow Dropbox branding guidelines (found here: https://www.dropbox.com/developers/branding ). Please choose a new name and submit a request to change your app name to api-program@dropbox.com."

==Configuration==
Once enabled by the administrator a Dropbox API Key and Secret will need to be added to the Dropbox settings in order for it to work. This will be ''the'' Dropbox available to all users throughout the site (and each will need the correct Dropbox login credentials to access it from their courses). To gather the Dropbox API Key and Secret click the "Dropbox Developers" link on the Dropbox repository settings page. On the next page you'll be prompted to login with your Dropbox username and password and to create a Dropbox app.

Once the App has been created at Dropbox.com you'll have the API Secret and Key available at the bottom of the App page. Entering those on the Dropbox settings page (and clicking Save) back in Moodle will finish the configuration. Dropbox is now available to the entire site.

To access it editing teachers need only "Add..." a new file while editing or creating a resource to see Dropbox as a new option.

==See also==

* [http://www.youtube.com/watch?v=V221JLCywWs Import files from Dropbox into Moodle 2.0 video]
* MDL-19168
* MDL-26949 - Can't change the Dropbox API key and secret to production status

[[Category:Site administration]]
[[de:Dropbox]]
[[ja:Dropbox]]

Legacy course files

2011-08-30T00:31:00Z

Mits:

Note: This page only applies to sites which have been upgraded from Moodle 1.9.
{{Working with files and folders}}

In Moodle 2.0 onwards, files are stored in separate areas, rather than together in the course files area. See [[Course files]] for a detailed explanation. When a site is upgraded from 1.9, the course files area is renamed 'Legacy course files'. By default, this area is not available in new courses.

''It is recommended that teachers make use of the new [[Repositories|repositories]] in Moodle 2.0 for storing course files, rather than saving them in the legacy course files area''.

==Enabling legacy course files areas==

To enable a legacy course files area in a new course

# Enable the legacy course files repository plugin in ''Settings > Site administration > Plugins > Repositories > [[Manage repositories]]''.
# Check the legacyfilesinnewcourses box in the Manage repositories common settings then click the 'Save changes' button.
# Set 'Legacy course files' to Yes in the course settings.

A legacy course files link will then appear in the ''Settings > Course administration'' area.

[[Category:Repositories]]
[[Category:Site administration]]

[[ja: レガシーコースファイル]]

Legacy course files

2011-08-30T00:30:48Z

Mits: ja link

Private files

2011-08-21T20:40:20Z

Mits: ja link

{{Working with files and folders}}
{{Repositories}}
'''Please refer to [[Page_notes#Private files|these notes]] before editing this page.'''

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
# On the Navigation menu, click 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]]

[[eu:Fitxategi_pribatuak]]
[[fr:Fichiers personnels]]
[[ja:プライベートファイル]]

Kategoria:Files

2011-08-17T16:33:59Z

Mits:

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

[[Category:Course]]

[[eu:Kategoria:Fitxategiak]]
[[fr:Catégorie:Fichiers]]
[[ja:Category:ファイル]]

Kategoria:Files

2011-08-17T16:33:10Z

Mits: ja link

My private files block

2011-08-16T16:37:34Z

Mits: ja link

{{Moodle 2.0}}The My private files block, in Moodle 2.0 onwards, enables access to a user's [[Private files|private files]] area.

[[Category:Block]]

[[eu:Nire_fitxategi_pribatuak_blokea]]
[[de:Eigene Dateien (Block)]]
[[ja:プライベートファイルブロック]]

Import a community course

2011-08-15T16:01:41Z

Mits: ja link

{{Moodle 2.0}}
# in your [[Community block]], select''' 'Search'''' operation
# select a hub (Mooch being Moodle.org hub)
# set search settings to''' 'courses I can download'''' and select ''''Search'''' operation
# look at the result and click on Download. The course backup will be downloaded in your private files (see [https://docs.moodle.org/en/My_private_files_block private files block]) under a ''''Downloaded backup'''' folder.
# you have the choice to restore the course straight forward. Select''' 'Restore'''' operation.
# follow the common restore procedure, the you should be redirected to a newly created course (if you selected this option).
==See also==
* [https://docs.moodle.org/en/Community_hub Community hub]
* [[Community block]]

[[Category:Hub]]

[[ja: コミュニティコースをインポートする]]

Context

2011-07-22T16:07:22Z

Mits: ja link

{{Moodle site - basic structure}}
'''Please refer to [[TOC_with_notes#Moodle site - basic structure|these notes]] before editing this page.'''
A context is a "space" in Moodle. Together, they define the navigational structure of a Moodle site. A course can be a context, so can an activity, resource or block.

A course can have many contexts in its space. These might include lesson, assignment, forum and quiz modules and blocks. Or for example, [[Question bank]]'s question categories are contexts.

==Role and contexts==
A context is combined with [[Role permissions]] to define a user's [[Roles and capabilities|capabilities]] on any page in Moodle. Typically contexts have their own organization structure which allow a user's role to be passed along to the context "below" but not to the one above it.

It is possible to assign a user different permissions based upon a specific context. For example, a user might be given the role of "student" for a course but be given a teacher's role in the context of one specific forum. Or a user can be a teacher of one course and a student in another course.

Many Moodle contexts have a place to grant exceptions to specific roles.

== Graphic showing contexts within contexts ==

The image below shows a few contexts and their relationships. The "System" or Moodle site is the overall context. The user is defined iniially in this context.
*The System context has 2 contexts under it, with other context under them
**The Front page context has
*** An activity module context and
*** A block context within it
**The Course Cateory context has
***A Course context within it. The course context has
**** An activity module context and
****A block context within it

[[Image:Moodle-contexts-1.8.png]]

(Source: [[Development:Roles#Context]])

== See also ==

Moodle Docs
* [[Beginning_Administration_FAQ | Beginning Administration FAQ]]
* [[Roles FAQ]]
* [[Development:Roles#Context]]
* [[Development:Roles and modules#Context]]
* [[Roles and capabilities]]
* [[Role permissions]]

Forum discussions
* [http://moodle.org/mod/forum/discuss.php?d=60125 "Roles and contexts in Moodle 1.7"]

[[Category:Roles]]

[[ja:コンテクスト]]

Publishing a course

2011-06-28T16:02:31Z

Mits: ja 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==
You can display a link to your course on any hub your site is registered on. The hub will redirect users on your course. T

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

:Tip! When you advertise a course try to make the course easy to see for people not registered on your site (allow [https://docs.moodle.org/en/Course_settings#Guest_access guest access in your course settings] / allow [https://docs.moodle.org/en/User_policies#Auto-login_guest Auto-login guests] / allow people to register themself).

==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]]
[[ja:コースを公開する]]

Site registration

2011-06-19T01:01:04Z

Mits: ja link

{{Moodle 2.0}}Location: ''Site Administration > Registration''

[[Image:Registration.png|thumb|Registration]]In Moodle 2.0 onwards, an administrator can register their site with the moodle.org open community hub, [http://hub.moodle.org/ MOOCH], and other community hubs.

==Moodle.org registration==

When you register your site with moodle.org, you are added to a low-volume mailing list for important notifications such as security alerts and new releases of Moodle. Statistics about your site, such as the number of users and number of courses will be added to the statistics of the worldwide Moodle community http://moodle.org/stats/.

If you wish, you can choose for your site to be listed in http://moodle.org/sites/.

In addition, users with the capability [[Capabilities/moodle/course:publish|moodle/course:publish]] can publish courses on MOOCH.

To register your site with moodle.org

# Click the 'Register with moodle.org now' button
# Review the registration information, amending as necessary
# Click the 'Update registration on moodle.org' button at the bottom of the page

After registering, MOOCH will appear in the list of hubs you have registered with on the registration page.

You may change the registration information at any time by updating your registration.

Updated site statistics are sent to moodle.org automatically every 7 days.

==Specific hub registration==

You may register your site with a specific hub by selecting the hub from a list or by entering a private hub URL and password.

== Unregistering from a hub==

You may unregister from a hub at any time by clicking the unregister button. You will then be given the option to remove all courses currently being advertised on the hub and remove all courses that were uploaded to the hub.

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

[[Category:Hub]]

[[ja: サイト登録]]