MoodleDocs - Användarbidrag [sv]

Capabilities/gradereport/user:view

2022-09-16T13:46:10Z

Tsala: cap allows teachers to view user reports for all students in their course

{{Capabilities}}
* This allows a user to view the [[User report|user report]], showing grades in the course
* This capability is allowed for the default roles of manager, teacher, non-editing teacher and student

[[Category:Capabilities|Grade]]
[[Category:Grades]]

[[eu:Capabilities/gradereport/user:view]]
[[ja:ケイパビリティ/gradereport/user:view]]

Guest access

2022-08-11T09:14:27Z

Tsala: /* See also */ removing broken link

{{Enrolment}}
The Guest access facility allows users with the [[Guest_role |Guest role]] to view the contents of a course. This might be used, for example, if a Moodle site serves as a website where certain courses contain publicly available information, or else with a commercial Moodle site where courses with guest access can offers a "taster" of the kind of courses which may be purchased. (Note that the guest cannot participate in any activities; they can only view content.)

==Course settings for guest access==

{{MediaPlayer | url = https://youtu.be/LSVLLu7GzHE | desc = How to allow guests into courses}}
# From Course navigation, click 'Participants', and then from the dropdown, click 'Enrolment method> Guest access'. With other themes, click ''Administration > Course administration > Users > Enrolment methods'' and then Guest access.
#Enable guest access by clicking on the "eye" icon or by choosing it in the 'Add method' dropdown menu.
# If you wish to set a password, then click the configure icon and type in your password here.

==Admin settings for guest access==

{{MediaPlayer | url = https://youtu.be/_xGrJ9-aqIc | desc = How to allow guests onto your Moodle site}}

*In ''Administration > Site administration > Plugins > Enrolments > Manage enrol plugins'',ensure Guest access is enabled (has its eye open.) This enables Guest access.
* In ''Administration > Site administration > Plugins > Authentication > Manage authentication'' set the Guest login button to Show if you want the button on the Front page.
* Also Guest accounts can be logged - check the ''Administration> Site administration > Plugins > Logging > Log guest access'' setting
* A site policy for guests may be set in ''Site administration > Security > Site policies''. Guests then have to agree to the site policy before accessing a course with guest access.

===Default settings for guest access===
*Clicking on ''Administration > Site administration > Plugins > Enrolments > Guest access'' brings up the screen where admin can set defaults for guest access in courses.
**Clicking the 'Advanced' button next to 'Allow guest access' will hide this setting in a course and will instead display a 'Show more' link to click on to access the setting.
** Guest access can be turned on by default in all new courses and you can also:
**require each course with guest access to have a password for guests. (Note: this can confuse teachers who are not aware of the requirement.)
**use or ignore your Moodle's standard password policy for guest access passwords
**offer if needed the first letter of the password as a hint.

===Auto-login guests===
*In ''Administration > Site administration > Users > Permissions > User policies'', you can tick the box so that visitors are automatically logged in as guests when accessing a course with guest access (i.e. they don't have to click the "login as guest button".
*In ''Administration > Site administration > Plugins > Authentication > Manage Authentication'', you must have "Guest login button" set to "Show".
*In ''Administration > Site administration > Security > Site policies'' you can check "Open to Google" setting so that the Google search robot will be allowed to enter your site as a Guest. In addition, people coming in to your site via a Google search will automatically be logged in as a Guest.

==See also==

* [[Guest role]]
* [https://moodle.org/mod/forum/discuss.php?d=347107#p1400235 Re: Guest access to course sections!] forum post

[[de:Gastzugang zum Kurs]]

[[es:Acceso de invitados]]

Feedback FAQ

2022-08-01T07:06:55Z

Tsala: /* Can I make questions dependent on previous responses? */ removing link

{{Feedback}}

==How can I allow non-logged in users to give feedback?==
*As an administrator, go to ''Administration>Site Administration>Plugins>Activity Modules>Feedback''.
*Change "Allow full anonymous" to "yes"
*Note that this only works for the front page, and NOT for courses with guest access.
*You will also need to check that Authenticated User and Guest role both have permission to Submit Feedback Activity.
[[File:Anonymousfeedback.png]]

==How can I allow teachers and non editing teachers to give feedback?==
# Go into the course as admin
# Click on your feedback you want to use for your teachers
# Click on "Permissions" inside the Administration block
# In the dropdown list "Advanced role override" choose "Teacher" or how ever your teacher role is named
# Look for "mod/feedback:complete" and set it to "Allow"
# Click on "Save changes"

==How do I create a Feedback activity and add questions?==

* From the ''Add an activity...'' drop down, select ''Feedback''.
* Complete the Name, Description, and other options then save.
* To add questions to your Feedback activity, click the link for the feedback activity, click the ''Edit questions'' tab, and add questions.

==Can I make questions dependent on previous responses?==
Yes. See the section on Dependence item and Dependence value in [[Building Feedback]].

==Is Activity Completion recorded if the Feedback activity is set to anonymise usernames?==
Yes. If the Feedback activity is set to Anonymous usernames, and the Feedback activity is set to record Activity Completion, then the activity will still be marked as complete and the user will show up in the activity completion reports.
==Is Record user names Anonymous mode truly Anonymous?==
No. For the 'Record user names' setting even in Anonymous mode the username of the user who took the Feedback is still recorded in the database just as with non-anonymous Feedbacks, but the name is not show to anyone on screen in Moodle or in reports or downloads. Anyone who has direct access to the database could see and extract the name of the user who took an anonymous feedback.

This explains why Activity completion still works in Anonymous mode since it actually knows the user who completed the Feedback.

==Is Allow full anonymous mode truly Anonymous?==
Yes*. If the Administrator has enabled the 'Allow full anonymous' setting for use of a Feedback on the front page of the site, then users who are not logged in when they take the Feedback are anonymous: all attempts are recorded as from userid 0 which does not otherwise exist.

*However the IP address of the user is collected as usual in the system logs with time and date and IP address as having viewed the front page: there is no information that they have specifically taken the Feedback. Under GDPR, an IP address can be considered personally identifiable information in some cases. If you need to comply with the GDPR, consult your Data Protection Officer if you plan to use the Feedback module in this way on the Front page.

If the user has an account on the site and logs in and takes a Feedback on the frontpage, then their userid and name is recorded as usual.

==I do not see the Edit Questions tab. What should I do?==
This does happen sometimes. Usually, logging out of the course and then logging back in will take care of this problem.

==What are the differences between Feedback and Questionnaire?==

[[Questionnaire]] is an additional plugin. For a discussion about their differences, see the forum thread [https://moodle.org/mod/forum/discuss.php?d=195584#p852097 Questionnaire v Feedback]

==See also==

* [https://moodle.org/mod/forum/discuss.php?d=345660 No Export to Excel button on Analysis tab] forum discussion

==Any further questions?==

Please post in the [http://moodle.org/mod/forum/view.php?id=7152 Feedback forum] on moodle.org

[[Category:FAQ]]

[[de:Feedback FAQ]]
[[es:Retroalimentación FAQ]]

Workplace localisation

2022-07-12T13:38:22Z

Tsala: /* Multi-language content */ rewording link

{{Workplace}}
=Overview=
Localisation in Moodle Workplace covers languages (language packs, language menu, and multi-language content) and time zones.

In this document we will only focus on Moodle Workplace-specific topics related to localisation.
=Workplace language packs=
In Moodle, every locale is represented as a language pack, each containing information about the locale itself and all translations. Standardised two-letter region codes characterise locales, for example, '''pt''' represents Portuguese as spoken in Portugal, whereas '''pt_br''' represents Brazilian Portuguese. Internally, '''pt''' is the parent language, whereas '''pt_br''' is the child language, which only contains strings different from the parent language pack.

Moodle Workplace harnesses the concept of child languages by extending each supported language with Moodle Workplace-specific strings. Example language packs are '''en_wp''' (English), '''es_wp''' (Spanish) or '''pt_br_wp''' (Brazilian Portuguese).
[[File:Moodle Workplace Language Packs.png|border|center|frameless|900x900px]]
To view, install, and uninstall Moodle and Moodle Workplace language packs, navigate to '''General > Language > Language settings > Language packs'''. Here, only the Moodle Workplace language packs are shown by searching for 'Workplace':
[[File:Moodle Workplace Language Import Utility.png|border|center|frameless|900x900px]]
You find more details on the Language import utility in the [[Language packs|Language pack documentation]].

If you wish to customise a language pack, that is to change certain word or phrases, navigate to '''General > Language > Language customisation''', check out the Moodle Workplace language pack you wish to modify, and edit the relevant strings. You find more details on language editing in the [[Language customisation|Language customisation documentation]].
= Workplace language menu =
By default Moodle Workplace parent language packs are hidden in the language menu, for example, 'English (en)' is not displayed if 'English for Workplace (en_wp)' is installed. If you wish to show them, go to '''General > Language > Language settings''' and untick the '''Hide Workplace parent packs''' option.
[[File:Moodle Workplace Language menu.png|border|center|frameless|600x600px]]
For more customisation of the language menu, go to to '''General > Language > Language settings'''. Also check out the [[Language settings]] documentation.
= Multi-language content =
If some of your users deal with multilingual content, turning on the '''Multi-Language Content filter''' is recommended by going to '''Plugins > Filters > Manage filters'''. The filter supports the <code><nowiki><span lang="xx"class="multilang"></nowiki></code> tag, which lets course designers and content creators support multiple languages in all text areas entered via the Atto editor.

Note: This feature is available in standard Moodle LMS. For full details, see [[Multi-language content filter]].

= Time zones =
Moodle Workplace supports systems that span across time zones, which happens in three scenarios:
* In countries that cover more than a single time zone
* Sites that have learners from multiple countries/time zones
* In a situation where the server is hosted outside the time zone of your organisation, for example, with an Internet Service Provider
To modify the default time zone parameters, go to '''General > Location > Location settings'''.

For more information on location settings and or time zone-related information, refer to the [[Location|Moodle Docs]].

= Interesting reading =
Top benefits of a multilingual LMS for your organization: https://moodle.com/us/news/top-benefits-of-a-multilingual-lms-for-your-organization/

Building Database

2022-07-05T12:37:39Z

Tsala: /* Presets */

{{Database}}
After creating a database, as explained in [[Database activity settings]]...
* Next you define the kind of fields that define the information you wish to collect. For example, a database of famous paintings may have a picture field called ''painting'', for uploading an image file showing the painting, and two text fields called ''artist'' and ''title'' for the name of the artist and the painting. Alternatively, you can use a database preset (see below).
* It is then optional to edit the [[Database templates|database templates]] to alter the way in which the database displays entries.

==Database fields==

A '''field''' is a named unit of information. Each entry in a [[Database activity module|database activity module]] can have multiple fields of multiple types e.g. a text field called 'favourite color' which allows you to type in your favourite shade, or a menu called 'state' that lets you choose one from a list of the 50 that make up the United States of America. By combining several fields with appropriate names and types you should be able to capture all the relevant information about the items in your database.

Note that if you later edit the fields in the databases you must use the Reset template button, or manually edit the template, to ensure the new fields are added to the display.

=== Field name and description ===

The name is what is shown when an entry is added. It must be unique and short. The description is for your benefit to help identify that field.

===Required field===
If you need to ensure one or several particular fields are always completed, then tick the box 'Required field' when setting up the fields for your database. The field(s) will display a red asterisk when students contribute to the database, and they will not be able to save their work until they have entered the relevant information. A new column will show the teacher which fields are required and not:

[[File:databaserequiredfields.png]]

=== Field types ===

The following screenshots show "before" and "afters" of setting up fields. The selection in orange shows the field as it is displayed for the user when they add an entry.

;Checkbox
:This allows you to offer checkboxes for the user to select. Add the options one under the other. The word will appear next to a checkbox when the user clicks to add an entry. They can check more than one box.

[[File:Checkboxfield1.png]]

;Date
:This allows a user to enter a date by picking a day, month and year from a drop down list.

[[File:Datefield1.png]]

;File
:Users can upload a file from their computer. If it is an image file then the picture field may be a better choice.

[[File:Filefield.png]]

;Latitude/longitude
:Users can enter a geographic location using latitude and longitude. For example, [http://moodle.com/hq/ Moodle HQ] is at latitude -31.9545, longitude 115.877. When viewing the record, links are automatically generated linking to geographic data services such as [http://earth.google.com Google Earth], [http://www.openstreetmap.org/ OpenStreetMap], [http://www.geabios.com/ GeaBios],[http://www.mapstars.com/extern/deltaworks-holland Mapstars] and more. (The teacher can choose which of those links appear, if any.)

:Data input requirements: Data for this field must be input relative to North and East coordinates. To convert coordinates from West (e.g. 120W) to East, simply input them into the field with a '-' in front (e.g., -120). Also, data must also be input in decimal format, not degree format. Simple converters are a web search away.
[[File:Latlongfield.png]]

;Menu
:The text entered in the ''options'' area will be presented as a drop-down list for the user to choose from. Each line become a different option.

[[File:Menufield.png]]

;Menu (Multi-select)
:The text entered in the ''options'' area will be presented as a list for the user to choose from and each line become a different option. By holding down control or shift as they click, users will be able to select multiple options. This is a fairly advanced computer skill so it may be wise to use multiple checkboxes instead.

[[File:Multiselectfield.png]]

;Number
:This allows users to enter any number. For example:
* 42
* -1000
* 0
* 0.123
* 3.0e8
:(For those who care about the technical details, the field stores floating point numbers.)

[[File:Numberfield.png]]

;Picture
:This allows a user to upload and display an image file. "Single view" is when the image is viewed on its own; "list view" is when it is viewed in with other images. Single view can be larger than list view.

[[File:Picturefield.png]]

;Radio buttons
:The user gets radio buttons and can choose only one. They can only submit the entry when they have clicked on one button. (Note:If you only have two options and they are opposites (true/false, yes/no) then you could simply use a single checkbox instead. However checkboxes default to their unchecked status and so people could submit without actively selecting one of the options. This may not always be appropriate.)

[[File:Radiofield.png]]

;Text input
:Users can enter text up to 60 characters in length. For longer text, or for text that requires formatting such as headers and bullet points, you can use a text area field.

[[File:Textfield.png]]

;Text area
:This allows users to enter a long piece of text using the text editor.

[[File:Textareafield.png]]

;URL
:The user can add a link to a website here. If you select ''autolink'' then the URL becomes clickable.. If you also enter a ''forced name for the link'' then that text will be used for the hyperlink. For example in a database of authors you may wish people to enter the author's website. If you enter the text 'homepage' as a forced name then clicking on text "homepage" will take you to the entered URL.
You can choose to have the URL open in a new window if so desired.

[[File:Urlfield.png]]

==Presets==

To avoid the necessity of always having to create a new database from scratch, the database activity module has a presets feature. An image gallery preset is included in the database module or you can browse and download one from the [https://moodle.net/collection/dw7n7v56rcye-moodle-database-presets Database presets collection on Moodle.net]. You can create your own presets as well and share them with others.

===Importing a preset===

[[Image:databasepresetsnew.png|thumb|Database presets page]]
To use a preset:

# On the database page, click the Presets tab.
# The usual way to import a preset is clicking the "Choose file" button and browsing to the ZIP file containing the preset (e.g. "preset.zip") stored on the server. If there does not yet exist a preset ZIP file on the server, upload it from your local machine. Choose the desired preset file by clicking on its action "Choose". Finally, press the "Import" button.
# Alternatively, you can choose a previously loaded preset.
# After the import, you can start to add or import entries. All the hard work of setting up the fields and templates has been done for you. If you desire, you can still customize the fields and templates.

You will see a "Overwrite current settings" checkbox after the "Import" button has been pressed. If checked, the database activity overwrites some of its current general settings by those stored in the preset:
* the "Introduction" HTML text
* "Required entries"
* "Entries required before viewing"
* "Maximum entries"
* "Comments"
* "Require approval?"
* rssarticles

===Exporting a preset===

If you wish to share your database presets with others, you have two options:

#Export as a ZIP file, which can then be imported to another course or Moodle site.
#Save as a preset, which publishes the database for other teachers on your site to use. It will then appear in the preset list. (You can delete it from the list at any time.)

Note: Only the fields and templates of the database are copied when exporting or saving it as a preset, not the entries.

===Presets for download===

The [https://school.moodledemo.net/course/view.php?id=57 Activity Examples course] on the School demo site has a number of database activities with presets for download.

==See also==

Forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view] including moodle.org presets for download
*[http://moodle.org/mod/forum/discuss.php?d=87005 New preset, please review, and make suggestions!] including FAQ preset for download
*[http://moodle.org/mod/forum/discuss.php?d=87560 Issue 53: Encyclopedia database preset] including encyclopedia-style preset for download
*[http://moodle.org/mod/forum/discuss.php?d=88727 Issue 51 - Design a Database Preset for Document Sharing] including preset for download
*[http://moodle.org/mod/forum/discuss.php?d=94854#p457252 Looking for some stellar examples of Moodle courses] including book reviews preset for download
*[http://moodle.org/mod/forum/discuss.php?d=89117#p511029 Restricting access to database content by user?] with research diary preset for download

[[de:Datenbank erstellen]]
[[es:Construyendo BasedeDatos]]
[[fr:Construire une base de données]]

Building Database

2022-07-05T12:37:10Z

Tsala: /* Presets */ link update

{{Database}}
After creating a database, as explained in [[Database activity settings]]...
* Next you define the kind of fields that define the information you wish to collect. For example, a database of famous paintings may have a picture field called ''painting'', for uploading an image file showing the painting, and two text fields called ''artist'' and ''title'' for the name of the artist and the painting. Alternatively, you can use a database preset (see below).
* It is then optional to edit the [[Database templates|database templates]] to alter the way in which the database displays entries.

==Database fields==

A '''field''' is a named unit of information. Each entry in a [[Database activity module|database activity module]] can have multiple fields of multiple types e.g. a text field called 'favourite color' which allows you to type in your favourite shade, or a menu called 'state' that lets you choose one from a list of the 50 that make up the United States of America. By combining several fields with appropriate names and types you should be able to capture all the relevant information about the items in your database.

Note that if you later edit the fields in the databases you must use the Reset template button, or manually edit the template, to ensure the new fields are added to the display.

=== Field name and description ===

The name is what is shown when an entry is added. It must be unique and short. The description is for your benefit to help identify that field.

===Required field===
If you need to ensure one or several particular fields are always completed, then tick the box 'Required field' when setting up the fields for your database. The field(s) will display a red asterisk when students contribute to the database, and they will not be able to save their work until they have entered the relevant information. A new column will show the teacher which fields are required and not:

[[File:databaserequiredfields.png]]

=== Field types ===

The following screenshots show "before" and "afters" of setting up fields. The selection in orange shows the field as it is displayed for the user when they add an entry.

;Checkbox
:This allows you to offer checkboxes for the user to select. Add the options one under the other. The word will appear next to a checkbox when the user clicks to add an entry. They can check more than one box.

[[File:Checkboxfield1.png]]

;Date
:This allows a user to enter a date by picking a day, month and year from a drop down list.

[[File:Datefield1.png]]

;File
:Users can upload a file from their computer. If it is an image file then the picture field may be a better choice.

[[File:Filefield.png]]

;Latitude/longitude
:Users can enter a geographic location using latitude and longitude. For example, [http://moodle.com/hq/ Moodle HQ] is at latitude -31.9545, longitude 115.877. When viewing the record, links are automatically generated linking to geographic data services such as [http://earth.google.com Google Earth], [http://www.openstreetmap.org/ OpenStreetMap], [http://www.geabios.com/ GeaBios],[http://www.mapstars.com/extern/deltaworks-holland Mapstars] and more. (The teacher can choose which of those links appear, if any.)

:Data input requirements: Data for this field must be input relative to North and East coordinates. To convert coordinates from West (e.g. 120W) to East, simply input them into the field with a '-' in front (e.g., -120). Also, data must also be input in decimal format, not degree format. Simple converters are a web search away.
[[File:Latlongfield.png]]

;Menu
:The text entered in the ''options'' area will be presented as a drop-down list for the user to choose from. Each line become a different option.

[[File:Menufield.png]]

;Menu (Multi-select)
:The text entered in the ''options'' area will be presented as a list for the user to choose from and each line become a different option. By holding down control or shift as they click, users will be able to select multiple options. This is a fairly advanced computer skill so it may be wise to use multiple checkboxes instead.

[[File:Multiselectfield.png]]

;Number
:This allows users to enter any number. For example:
* 42
* -1000
* 0
* 0.123
* 3.0e8
:(For those who care about the technical details, the field stores floating point numbers.)

[[File:Numberfield.png]]

;Picture
:This allows a user to upload and display an image file. "Single view" is when the image is viewed on its own; "list view" is when it is viewed in with other images. Single view can be larger than list view.

[[File:Picturefield.png]]

;Radio buttons
:The user gets radio buttons and can choose only one. They can only submit the entry when they have clicked on one button. (Note:If you only have two options and they are opposites (true/false, yes/no) then you could simply use a single checkbox instead. However checkboxes default to their unchecked status and so people could submit without actively selecting one of the options. This may not always be appropriate.)

[[File:Radiofield.png]]

;Text input
:Users can enter text up to 60 characters in length. For longer text, or for text that requires formatting such as headers and bullet points, you can use a text area field.

[[File:Textfield.png]]

;Text area
:This allows users to enter a long piece of text using the text editor.

[[File:Textareafield.png]]

;URL
:The user can add a link to a website here. If you select ''autolink'' then the URL becomes clickable.. If you also enter a ''forced name for the link'' then that text will be used for the hyperlink. For example in a database of authors you may wish people to enter the author's website. If you enter the text 'homepage' as a forced name then clicking on text "homepage" will take you to the entered URL.
You can choose to have the URL open in a new window if so desired.

[[File:Urlfield.png]]

==Presets==

To avoid the necessity of always having to create a new database from scratch, the database activity module has a presets feature. An image gallery preset is included in the database module or you can browse and download one from the [https://moodle.net/collection/dw7n7v56rcye-moodle-database-presets Database presets database on Moodle.net]. You can create your own presets as well and share them with others.

===Importing a preset===

[[Image:databasepresetsnew.png|thumb|Database presets page]]
To use a preset:

# On the database page, click the Presets tab.
# The usual way to import a preset is clicking the "Choose file" button and browsing to the ZIP file containing the preset (e.g. "preset.zip") stored on the server. If there does not yet exist a preset ZIP file on the server, upload it from your local machine. Choose the desired preset file by clicking on its action "Choose". Finally, press the "Import" button.
# Alternatively, you can choose a previously loaded preset.
# After the import, you can start to add or import entries. All the hard work of setting up the fields and templates has been done for you. If you desire, you can still customize the fields and templates.

You will see a "Overwrite current settings" checkbox after the "Import" button has been pressed. If checked, the database activity overwrites some of its current general settings by those stored in the preset:
* the "Introduction" HTML text
* "Required entries"
* "Entries required before viewing"
* "Maximum entries"
* "Comments"
* "Require approval?"
* rssarticles

===Exporting a preset===

If you wish to share your database presets with others, you have two options:

#Export as a ZIP file, which can then be imported to another course or Moodle site.
#Save as a preset, which publishes the database for other teachers on your site to use. It will then appear in the preset list. (You can delete it from the list at any time.)

Note: Only the fields and templates of the database are copied when exporting or saving it as a preset, not the entries.

===Presets for download===

The [https://school.moodledemo.net/course/view.php?id=57 Activity Examples course] on the School demo site has a number of database activities with presets for download.

==See also==

Forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view] including moodle.org presets for download
*[http://moodle.org/mod/forum/discuss.php?d=87005 New preset, please review, and make suggestions!] including FAQ preset for download
*[http://moodle.org/mod/forum/discuss.php?d=87560 Issue 53: Encyclopedia database preset] including encyclopedia-style preset for download
*[http://moodle.org/mod/forum/discuss.php?d=88727 Issue 51 - Design a Database Preset for Document Sharing] including preset for download
*[http://moodle.org/mod/forum/discuss.php?d=94854#p457252 Looking for some stellar examples of Moodle courses] including book reviews preset for download
*[http://moodle.org/mod/forum/discuss.php?d=89117#p511029 Restricting access to database content by user?] with research diary preset for download

[[de:Datenbank erstellen]]
[[es:Construyendo BasedeDatos]]
[[fr:Construire une base de données]]

Forum settings

2022-06-27T13:21:45Z

Tsala: /* Changing the subject line of forum notifications */ updated list of available placeholders thanks to Jun's comment in MDL-75072

{{Forum}}
This page explores in more detail the settings for the [[Forum activity]] once you have added it to your course and also covers the Site administration settings.
==General==
Give the Forum a name and a description if required. (For the Single simple discussion forum type, your description must include the question or topic you wish to discuss.)

For forum type, see the section 'Which forum do I need?' in [[Using Forum]] for further details with screenshots.
==Availability==
As well as setting a due date for forum posts, you can also set a cut-off date beyond which students can no longer post.

==Attachments and word count==

The maximum file size that may be attached to a forum post depends on the Moodle site settings. The teacher may want a smaller size limit for the forum and should bear in mind the download speeds of the course participants.

If "Display word count" is enabled, then the number of words in forum posts will be shown at the bottom of each post.
==Subscription and tracking==
;Subscription mode
:When a participant is subscribed to a forum it means that they will receive notification (depending on the user’s messaging settings preferences) of each new posting. By default, forum notifications are sent about 30 minutes after the post was saved.

Participants can usually choose whether or not they want to be subscribed to each forum. However, the teacher can choose to force subscription on a particular forum then all course users will be subscribed automatically, even those that enrol at a later time.

The subscription mode and subscribe or unsubscribe links can be found via the gear menu inside the forum in Boost or via the Forum administration in Clean. Teachers can quickly change the mode via the 'Subscription mode' options and view the current subscribers via the 'Show/edit current subscribers' link. Teachers can manually subscribe or unsubscribe participants by clicking the 'Manage subscriptions' button.

Tips:
* Forcing everyone to subscribe is especially useful in the news forum and in forums towards the beginning of the course (before everyone has worked out that they can subscribe to these emails themselves).
* Changing the setting from "Auto subscription" to "Optional" will not unsubscribe existing users; it will only affect those who enrol in the course in the future. Similarly changing "Optional" to "Auto subscription" will not subscribe existing course users but only those enrolling later.
* There is also a "Subscription disabled" setting which prevents students from subscribing to a Forum. Teachers may choose to subscribe to a forum if they wish.

===Subscribe to individual forum discussions===

In a forum with optional or auto subscription you can choose which discussions to subscribe to by toggling the subscribe / unsubscribe button to the right of the discussion.
[[File:forumsubscribetoggle.png|center]]

When you reply to a post you will see a tickbox 'Discussion subscription'. It will already be ticked if you have chosen in your forum preferences to be subscribed to discussions you post in by default. If you have chosen not to subscribe to forum discussions by default, then you can tick this box to be notified of posts from this particular thread.
;Read tracking
:If this is set to Optional, students can see which posts they have not yet read if they (1) enable forum tracking in their forum preferences and (2) turn tracking on from the Actions menu
:Note that the admin can allow "Forced read tracking" which offers another option - to force this in the forum for everyone.

==Discussion locking==
This setting will close forum threads after a specified period of time. Note that teachers can also manually lock individual threads from the list by clicking the three dots:
[[File:manualdiscussionlocking.png|center]]

===RSS===
If [[RSS feeds]] are enabled for the site and for forums, then an expandable section for RSS settings will appear. Here the teacher can turn RSS feeds on or off for that forum.When set to “Discussions,” the RSS feed will send out new discussions to subscribers. When set to “Posts,” the RSS feed will send out any new posts to subscribers.

Cron must be working regularly for the RSS feed to work; otherwise participants will see ' Error reading RSS data'.

==Post threshold for blocking==
By default, course participants can post any number of messages to forums. If you want to restrict this number and block them after a certain number or time, the expandable section 'Post threshold for blocking' allows you to specify your choice. You can also send a warning that they are about to be blocked.

==Whole forum grading==

When grading is enabled from here, grading options appear, allowing the teacher to select points or a scale. Advanced grading methods such as rubrics may also be used and can be selected from the forum cog menu / Advanced grading. For more information on grading with forums, see [[Using Forum]]

==== Ratings====
Forums use a rating [[Scales|scale]] which you can customise. You can also set a "Grade to pass" which may be connected with [[Activity completion]] and [[Restrict access]] such that a student will not be able to access a follow up activity until they have obtained a required grade (rating) in the forum.

By default, only teachers can rate forum posts, though students can be given permission to do so if desired (see forum permissions below). This is a useful tool for giving students participation grades. Any ratings given in the forum are recorded in the [[Gradebook|gradebook]].

You can set an 'aggregate type' to decide how all the ratings given to posts in a forum are combined to form the final grade (for each post and for the whole forum activity). See [[Ratings]] for an explanation of aggregate types and which one is best for you.

==Other settings==
Depending on what is enabled for your site and course, you may also need to explore [[Common module settings]], [[Restrict access| Restrict access]], [[Activity completion]], [[Tags]] and [[Competencies]]

If you want your forum to display in the [[Course overview block]], you need to add an 'Expect completed by' date in the [[Activity completion]] section.

If your Forum activity doesn't display as you wish, check the site settings below:

==Using groups with Forums==
For 'Group mode' in the expandable Common module settings section allows you to specify how your forum works with groups. (Note that Single simple discussions cannot be used with groups as this feature is not implemented. Use a standard forum instead. )
For more information about using groups with forums, see the documentation [[Using Forum]].

==Site administration settings==

A description for the Forum may or may not be obligatory depending on ''Site administration > Plugins > Activity modules > Common settings''.

The forum module has additional settings which may be changed by an administrator in ''Administration > Site administration > Plugins > Activity modules > Forum'' and, for 'Maximum time to edit posts', in ''Administration > Site administration > Security > Site policies''.

Teachers (and others with the capability [[Capabilities/mod/forum:viewhiddentimedposts|mod/forum:viewhiddentimedposts]]) can then set a display period of a date and time for the forum post to appear.

[[File:timedposts.png|500px]]

===Changing the subject line of forum notifications===

Normally when forum subscribers receive emails from forums, the subject line is of the form: Course short name + Subject of post:

[[File:forum1.png]]

The subject line can be changed - for example to: Course short name + Forum name + Subject by going to ''Site administration > Language > Language customisation'' and in forum.php changing the string ''postmailsubject'' to
{$a->courseshortname} {$a->forumname} {$a->subject}

[[File:forum2.png]]

Placeholders available for use are:

* subject
* forumname
* sitefullname
* siteshortname
* courseidnumber
* coursefullname
* courseshortname

[[de:Forum konfigurieren]]
[[fr:Ajouter/modifier un forum]]
[[ja:フォーラムの追加/編集]]
[[es:Configuraciones del foro]]

Enrolment methods

2022-06-22T09:20:52Z

Tsala: /* Managing enrolment methods */ updated location

{{Course enrolment}}
==Enrolment methods==
Depending upon which enrolment methods are enabled for the site (by an administrator in ''Site administration > Plugins > Enrolments > [[Enrolment plugins|Manage enrol plugins]]''), some or all of the following are available within a course:

===Manual enrolment===
*This enables users to be enrolled manually in ''Course administration > Users > Enrolled users''.
*It allows the teacher of the course to manage individual or collective enrolment to their course themselves - for example: if a new student arrives to class unexpectedly with just a login to the site, they may be enrolled by the teacher into their course without any input from an administrator.
*See [[Manual_enrolment|Manual enrolment]] for full details of how this can work in your course.

===Self enrolment===
*This allows users to enrol themselves into a course, either directly or via an enrolment key ("course password") The teacher does not then have to manually add students.
*More than one instance of the self enrolment method can be used so that when users enrol themselves they are assigned different roles e.g. certain users can be assigned the role of student and other users can be assigned the role of non-editing teacher
*The self-enrolment method also allows for users to enrol themselves into groups by using a group enrolment key.
*See [[Self_enrolment|Self enrolment]] for full details of how this can work in your course.

===Guest access===
*This allows those with the guest role to view the contents of a course.
*Users with the "guest role" may be visitors who do not have an account on your Moodle, or users who do have an account ("authenticated users") but who would just like to explore your course.
*It is possible to add an enrolment key so that only those guest users you wish to grant access can enter the course
*Entering a course with guest access doesn't allow a user to participate in any activities; they can only view information.
*See [[Guest_access|Guest access]] for full details of how this can work in your course.

===Cohort sync===
*A cohort is a set of users which has been added either to the site as a whole or to a particular category and which can then be made available in a course through the cohort-sync enrolment plugin.
*Only an administrator or a manager can use this plugin.
*See [[Cohort_sync|Cohort sync]] for full details of how this can work in your course.

===Course meta link===
*This allows users who are in another course to be automatically enrolled into your course as well. An example might be if a Moodle site has a course for "Staff Only" and a course for "Moodle Help". If the "Staff Only" course is added to the "Moodle Help" course with the course meta link plugin, then every time a new member of staff joins the "Staff Only" course, they will automatically be enrolled in the "Moodle Help" course as well.
*Teachers can only select from courses in which they are teachers when using this method.
*See [[Course_meta_link|Course meta link]] for full details of how this can work in your course.

===PayPal===
*This allows users to pay for a course. The PayPal enrolment plugin needs to be enabled sitewide by the administrator and the plugin needs to be added to a course by the administrator or a manager.
*The course teacher can select a cost(and currency for their course) along with other course-specific requirements.
*See [[Paypal_enrolment|PayPal enrolment]] for full details of how this can work in your course.

==Managing enrolment methods==
[[Image:enrolmentmethods3031.jpg]]

Managers and teachers (and any other users with the capability [[Capabilities/moodle/course:enrolconfig|moodle/course:enrolconfig]]) can manage enrolment methods via the Participants link then selecting 'Enrolment methods' from the dropdown menu.

* To add a new method, select it from the dropdown menu.
* To remove any unused enrolment method, click the delete icon (X) opposite it.
* To temporarily disable an enrolment method, click the show/hide icon (an eye) opposite it. (This ensures that the settings are remembered if the enrolment method is later re-enabled.)
* If several self-enrolment methods are enabled, the order in which they are listed for users wanting to enrol can be changed with the up/down arrows.

==See also==

* [[Enrolment plugins]]

[[fr:Méthodes d'inscription]]
[[de:Einschreibemethoden]]
[[es:Métodos de inscripción]]

Question contexts

2022-06-07T06:39:12Z

Tsala: /* How to access the Quiz activity context */ update location

__TOC__
{{Questions}}We can share questions in different contexts. ''Context'' may be an unfamiliar word. Think of a context as an area within your Moodle site. Each different context has a separate question category hierarchy. So, now you can choose the 'context' within which your questions will be shared. And also an administrator can give their users different permissions within different context areas.

See the diagram illustrating the relationship of the different contexts below. Different colours denote different context types (though there are two hues of green, both denote the same type). Notice how question contexts contain each other. Notice also that Course category contexts can be nested. In this example we have two contexts nested within each other 'Humanities' and 'Languages'. We could have a third course category 'English' and fourth and so on. Course categories can be nested infinitely and so you can set up a very flexible system of question contexts for sharing questions and assigning question sharing permissions.

As described at [[Question categories]], questions are stored in a hierarchical structure similar to folders at the filesystem. You can imagine question context as a place where the tree of question categories is actually placed. By default, every teacher can create new questions in the course context (the blue one in the diagram) and the activity module context (the white one). We will discuss how to allow a teacher to create questions in higher contexts below.

[[Image:question-contexts.png|thumb|left|600px|Example diagram of question contexts: question categories can be stored in several nested areas]]
<br clear="both" />

Question contexts are just as a subset of the Roles and Permissions contexts. A context contained by another context inherits the permissions of the containing context. You can access question categories in any containing context if you have permission to do so. Remember, you can access the question bank in two ways: from within an activity (now only the quiz activity), or from the link in the Course admin menu to 'Questions'. When you access the question bank from the :

* Activity. If you have permissions you can access question categories in :
** that activity's context and containing contexts.
** the course in which the activity module is contained.
** the course categories in which the course that contains the activity module is contained.
** the core system context.
* Course. If you have permissions you can access question categories in :
** that course.
** the course categories in which the course is contained.
** the core system context.

So questions contexts are accessible as follows :

* '''Activity context''' : questions only available to one activity module.
* '''Course context''' : questions available to all activity modules in a course and within the course from the 'Questions' link in the course administration block.
* '''Course category contexts''' : questions available to all activity modules and courses in the course category (remember one course category can contain other course categories, you can share your questions in any parent course category).
* '''Core System context''' : questions available in all courses and activities on your site.

All Question capabilities are tested in the relevant context. So, for example, to add a question to a category you must have the add capability for that context. See [[:Category:Roles|roles and capability help]] for more info. If you don't have permission to do anything in a context, then the categories in that context will not be visible to you.

==How to access the Quiz activity context==
Moodle automatically creates a Quiz activity context each time you create or duplicate a quiz. This Quiz activity context is specific and unique to each quiz, whether created or duplicated.

You can only access the Quiz activity context of a quiz by going via the quiz to the question bank. The first context, at the top of the page, titled "Question categories for 'Quiz: name of the quiz', is the Quiz activity context.

In the Quiz activity context, Moodle also automatically creates a category called "Default for Name of the quiz ()". This is where you often want to place the questions of a quiz. Note that Moodle behaves differently when you copy a quiz and whether the questions are placed in the Quiz context or in another context. See the [[Quiz FAQ]] 'Copying a quiz'.

==See also==

*[[How to let teachers share questions between courses]]
*[[Question permissions explained with diagrams]]

[[Category:Roles]]

[[de:Fragenkontext]]
[[es:Contextos de pregunta]]
[[fr:Contextes de questions]]
[[ja:問題コンテクスト]]

Moodle app features

2022-04-22T10:50:05Z

Tsala: /* Features summary */ providing a direct link to the pdf file

{{Mobile}}
__NOTOC__
<div class="contentblock">
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:36MoodleApp.png|600px]]
<div class="caption">
<h4>See your courses at glance</h4>
<p>Your courses are listed with easy access to contents, participants, grades and notes. A useful filter field lets you find a particular course quickly. If your token expires during a session, you're prompted to re-enter your password and continue. </p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35timeline.png|600px]]
<div class="caption">
<h4>View and access activities which are due</h4>
<p> The timeline display shows you which tasks you need to complete, with quick access links. </p>
</div>
</div>
</li>
</ul>
</div>

<div class="contentblock">
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35connectparticipants1.png|600px]]
<div class="caption">
<h4>Connect with course participants</h4>
<p>Easily connect to course participants.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35dashboardbothorientations.png|600px]]
<div class="caption">
<h4> Orientation and resolution support </h4>
<p>The app displays in portrait or landscape view, whatever your screen resolution.</p>
</div>
</div>
</li>
</ul>
</div>

<div class="contentblock">
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35accesscourses.png|600px]]
<div class="caption">
<h4>Easily access course content</h4>
<p>View course activities and download materials for offline use. Work through Books and IMS Content packages directly in the app. The downloading status of resources is preserved even when changing sections or pages.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35activitycompletion.png|600px]]
<div class="caption">
<h4>Activity completion</h4>
<p>Track progress from your device with [[Activity completion]]. Automatic completion is registered, and students can also manually mark a task complete on their mobile.</p>
</div>
</div>
</li>
</ul>
</div>

<div class="contentblock">
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35gradebook.png|600px]]
<div class="caption">
<h4>Grades and grading</h4>
<p> A Grades link for each course gives fingertip access to the gradebook, and teachers can view assignment submissions on the move.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35notes.png|600px]]
<div class="caption">
<h4>Notes</h4>
<p>Teachers can view site, course and personal notes about their students and add their own notes.</p>
</div>
</div>
</li>
</ul>
</div>

<div class="contentblock">
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35messages.png|600px]]
<div class="caption">
<h4>Message participants</h4>
<p>Send and view private messages to colleagues and students from the Messages link in the side tab.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35calendar.png|600px]]
<div class="caption">
<h4>Keep up to date with calendar events</h4>
<p>Site, course and user events can be viewed in the calendar.Calendar events can now be viewed offline and infinite scrolling is available.</p>
</div>
</div>
</li>
</ul>
</div>

<div class="contentblock">
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35privatefiles.png|600px]]
<div class="caption">
<h4>View and upload to your Private files</h4>
<p>Check the contents of your private files and upload media to them on the go. You're now allowed up to 50MB storage (depending on your SD card).</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35notifications.png|600px]]
<div class="caption">
<h4>Notifications</h4>
<p>Keep up to date with notifications. The app supports both local (calendar events) and push (messages, forum posts, submitted assignments etc) notifications. See [[Mobile app notifications]] for more details. Infinite scrolling is available and local notifications have multi-site support.</p>
</div>
</div>
</li>
</ul>
</div>

<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File: mobile35choice.png|600px]]
<div class="caption">
<h4>Make choices</h4>
<p>The app supports students making and removing choices.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35chat.png|600px]]
<div class="caption">
<h4>Engage in chat, on the move</h4>
<p>Participate in a course [[Chat activity]].</p>
</div>
</div>
</li>
</ul>
</div>
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35survey.png|600px]]
<div class="caption">
<h4> Feed back to teachers with a survey</h4>
<p>[[Survey|Surveys]] may now be taken using the app.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35searchcourses.png|600px]]
<div class="caption">
<h4>Search the list of courses</h4>
<p>App users can search courses to find one they wish to take.</p>
</div>
</div>
</li>
</ul>
</div>
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35selfenrol.png|600px]]
<div class="caption">
<h4>Enrol yourself from your smartphone</h4>
<p>Found a course you like? Enrol immediately via the app.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35scorm.png|600px]]
<div class="caption">
<h4>Play SCORM packages on and off-line</h4>
<p>The [[Moodle app SCORM player]] tracks interactions and synchronises when you're back online.</p>
</div>
</div>
</li>
</ul>
</div>
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35downloadcourse.png|600px]]
<div class="caption">
<h4>Download all course sections</h4>
<p>Easily download all sections to view offline.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35glossary.png|600px]]
<div class="caption">
<h4>Browse glossary entries</h4>
<p>Search for and browse glossary entries.</p>
</div>
</div>
</li>
</ul>
</div>
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File: mobile35quiz.png|600px]]
<div class="caption">
<h4>Take quizzes on your mobile</h4>
<p>Quizzes may now be completed on the move. Find out more about the [[Moodle Mobile Quiz module|Moodle Mobile quiz]].</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35learningplans.png|600px]]
<div class="caption">
<h4>Learning plans </h4>
<p>Learning plans may be viewed and progress checked from the mobile.</p>
</div>
</div>
</li>
</ul>
</div>
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File:mobile35competencies.png|600px]]
<div class="caption">
<h4>Easiy view course competencies</h4>
<p>A Competencies tab allows you to see course competencies at a glance.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35teachergrading.png|600px]]
<div class="caption">
<h4>Teachers: Grade assignments</h4>
<p>Assignments may be graded on the move, from the app and may be graded offline</p>
</div>
</div>
</li>
</ul>
</div>
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File: mobile35badges.png|600px]]
<div class="caption">
<h4>View badges from your profile</h4>
<p>Badges are now visible from a link in the user profile</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35preferences.png|600px]]
<div class="caption">
<h4>Notifications & Messaging preferences</h4>
<p>New preferences screen lets you decide how to be alerted</p>
</div>
</div>
</li>
</ul>
</div>
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File: mobile35workshop.png|600px]]
<div class="caption">
<h4>Submit to workshops from the app</h4>
<p>Students can now do workshop activities from their mobile or tablet.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile35paypal.png|600px]]
<div class="caption">
<h4>Sign up to courses via PayPal</h4>
<p>PayPal enrolment is now supported in the app.</p>
</div>
</div>
</li>
</ul>
</div>
<div class="row-fluid">
<ul class="thumbnails">
<li class="span6">
<div class="thumbnail">
[[File: mobile39h5p.png|600px]]
<div class="caption">
<h4>Play H5P on and off-line</h4>
<p>Users can now play [[Moodle_app_H5P_support|H5P packages]] on and off-line, including grading for the H5P activity.</p>
</div>
</div>
</li>
<li class="span6">
<div class="thumbnail">
[[File:mobile39qr.png|600px]]
<div class="caption">
<h4>Scan QRs to login or open courses/activities in the app</h4>
<p>The app now includes a QR reader so users can easily authenticate in their site or open certain courses or activities in the app.</p>
</div>
</div>
</li>
</ul>
</div>
====Features summary====

For a detailed features comparison table of Moodle LMS and the Moodle app, please see [https://docs.moodle.org/en/images_en/2/2a/Moodle_features_students.pdf Moodle features for students.pdf].

==Activities & Resources Support==

[[File:moodlemobile_activities_resources.png|600px]]

=== Languages ===

The Moodle app is being translated into an increasing number of languages. As of June 2020, 47 languages are available:

(ar) عربي, (bg) Български, (ca) Català, (cs) Čeština, (da) Dansk, (de) Deutsch, (de-du) Deutsch - Du, (el) Ελληνικά, (en) English, (en-us) English - United States, (es) Español, (es-mx) Español - México, (eu) Euskara, (fa) فارسی, (fi) Suomi, (fr) Français, (he) עברית, (hu) magyar, (id) Indonesian, (it) Italiano, (ja) 日本語, (km) ខ្មែរ, (kn) ಕನ್ನಡ, (ko) 한국어, (lt) Lietuvių, (lv) Latviešu, (mn) मराठी, (mr) मराठी, (nl) Nederlands, (no) Norsk - bokmål, (pl) Polski, (pt-br) Português - Brasil, (pt) Português - Portugal, (pt-br) Português - Brasil, (ro) Română, (ru) Русский, (sl) Slovenščina, (sr-cr) Српски, (sr-lt) Srpski, (sv) Svenska, (tg) Тоҷикӣ, (tr) Türkçe, (uk) Українська, (vi) Vietnamese, (zh-cn) 简体中文, (zh-tw) 正體中文

If the Moodle app is not yet available in your language, please consider helping with the translation. See [[:dev:Translating Moodle Mobile|Translating Moodle Mobile]] for details.

[[ca:Característiques_Moodle_Mobile]]
[[es:Características de la App Moodle]]
[[fr:Fonctionnalités de l'app mobile]]
[[de:Moodle App - Funktionalitäten]]

== See also ==
* [http://www.slideshare.net/juanleyva/moodle-mobile-offline-features Moodle Mobile offline features] - Presentation in the MoodleMoot UK 2016
* [[:dev:Moodle Mobile release notes|Moodle Mobile release notes]] in the dev docs

MoodleDocs:Overview

2022-04-21T10:11:18Z

Tsala: /* Français (French) */ 4x link

==English==
[https://docs.moodle.org/400/sv/ 4.0 EN documentation]<br />
[https://docs.moodle.org/311/en/ 3.11 EN documentation]<br />
[https://docs.moodle.org/310/en/ 3.10 EN documentation]<br />
[https://docs.moodle.org/39/en/ 3.9 EN documentation]<br />

Also:<br />
[https://docs.moodle.org/dev/ Developer documentation]

==Català (Catalan)==

[https://docs.moodle.org/2x/ca/ 2.x CA documentation]<br />

==Deutsch (German)==
[https://docs.moodle.org/400/de/ 4.0 DE documentation]<br />
[https://docs.moodle.org/311/de/ 3.11 DE documentation]<br />
[https://docs.moodle.org/310/de/ 3.10 DE documentation]<br />
[https://docs.moodle.org/39/de/ 3.9 DE documentation]<br />

==Español (Spanish)==

[https://docs.moodle.org/all/es/ ES documentation]

==Euskara (Basque)==

[https://docs.moodle.org/all/eu/ EU documentation]

==Français (French)==

[https://docs.moodle.org/4x/fr/ 4.x FR documentation]<br />
[https://docs.moodle.org/3x/fr/ 3.x FR documentation]<br />

==Hrvatski (Croatian)==

[https://docs.moodle.org/all/hr/ HR documentation]

==Íslenska (Icelandic)==

[https://docs.moodle.org/all/is/ IS documentation]

==Italiano (Italian)==

[https://docs.moodle.org/35/it/ 3.5 IT documentation]

==日本語 (Japanese)==

[https://docs.moodle.org/3x/ja/ 3.x JA documentation]<br />

==Polski (Polish)==

[https://docs.moodle.org/2x/pl/ 2.x PL documentation]

==Português Brasileiro (Brazilan Portuguese)==

[https://docs.moodle.org/all/pt_br PT_BR documentation]

==Suomi (Finnish)==

[https://docs.moodle.org/3x/fi/ 3.x FI documentation]<br />

==中文 (Chinese)==

[https://docs.moodle.org/all/zh/ ZH documentation]

==See also==

* [[MoodleDocs:Read-only archives]]

MoodleDocs:Overview

2022-04-21T10:10:47Z

Tsala: /* Deutsch (German) */ 4.0 link

==English==
[https://docs.moodle.org/400/sv/ 4.0 EN documentation]<br />
[https://docs.moodle.org/311/en/ 3.11 EN documentation]<br />
[https://docs.moodle.org/310/en/ 3.10 EN documentation]<br />
[https://docs.moodle.org/39/en/ 3.9 EN documentation]<br />

Also:<br />
[https://docs.moodle.org/dev/ Developer documentation]

==Català (Catalan)==

[https://docs.moodle.org/2x/ca/ 2.x CA documentation]<br />

==Deutsch (German)==
[https://docs.moodle.org/400/de/ 4.0 DE documentation]<br />
[https://docs.moodle.org/311/de/ 3.11 DE documentation]<br />
[https://docs.moodle.org/310/de/ 3.10 DE documentation]<br />
[https://docs.moodle.org/39/de/ 3.9 DE documentation]<br />

==Español (Spanish)==

[https://docs.moodle.org/all/es/ ES documentation]

==Euskara (Basque)==

[https://docs.moodle.org/all/eu/ EU documentation]

==Français (French)==

[https://docs.moodle.org/3x/fr/ 3.x FR documentation]<br />

==Hrvatski (Croatian)==

[https://docs.moodle.org/all/hr/ HR documentation]

==Íslenska (Icelandic)==

[https://docs.moodle.org/all/is/ IS documentation]

==Italiano (Italian)==

[https://docs.moodle.org/35/it/ 3.5 IT documentation]

==日本語 (Japanese)==

[https://docs.moodle.org/3x/ja/ 3.x JA documentation]<br />

==Polski (Polish)==

[https://docs.moodle.org/2x/pl/ 2.x PL documentation]

==Português Brasileiro (Brazilan Portuguese)==

[https://docs.moodle.org/all/pt_br PT_BR documentation]

==Suomi (Finnish)==

[https://docs.moodle.org/3x/fi/ 3.x FI documentation]<br />

==中文 (Chinese)==

[https://docs.moodle.org/all/zh/ ZH documentation]

==See also==

* [[MoodleDocs:Read-only archives]]

MoodleDocs:Overview

2022-04-21T10:10:14Z

Tsala: /* English */ 4.0 link

==English==
[https://docs.moodle.org/400/sv/ 4.0 EN documentation]<br />
[https://docs.moodle.org/311/en/ 3.11 EN documentation]<br />
[https://docs.moodle.org/310/en/ 3.10 EN documentation]<br />
[https://docs.moodle.org/39/en/ 3.9 EN documentation]<br />

Also:<br />
[https://docs.moodle.org/dev/ Developer documentation]

==Català (Catalan)==

[https://docs.moodle.org/2x/ca/ 2.x CA documentation]<br />

==Deutsch (German)==
[https://docs.moodle.org/311/de/ 3.11 DE documentation]<br />
[https://docs.moodle.org/310/de/ 3.10 DE documentation]<br />
[https://docs.moodle.org/39/de/ 3.9 DE documentation]<br />

==Español (Spanish)==

[https://docs.moodle.org/all/es/ ES documentation]

==Euskara (Basque)==

[https://docs.moodle.org/all/eu/ EU documentation]

==Français (French)==

[https://docs.moodle.org/3x/fr/ 3.x FR documentation]<br />

==Hrvatski (Croatian)==

[https://docs.moodle.org/all/hr/ HR documentation]

==Íslenska (Icelandic)==

[https://docs.moodle.org/all/is/ IS documentation]

==Italiano (Italian)==

[https://docs.moodle.org/35/it/ 3.5 IT documentation]

==日本語 (Japanese)==

[https://docs.moodle.org/3x/ja/ 3.x JA documentation]<br />

==Polski (Polish)==

[https://docs.moodle.org/2x/pl/ 2.x PL documentation]

==Português Brasileiro (Brazilan Portuguese)==

[https://docs.moodle.org/all/pt_br PT_BR documentation]

==Suomi (Finnish)==

[https://docs.moodle.org/3x/fi/ 3.x FI documentation]<br />

==中文 (Chinese)==

[https://docs.moodle.org/all/zh/ ZH documentation]

==See also==

* [[MoodleDocs:Read-only archives]]

admin/setting/activitychoosersettings

2022-04-20T13:01:08Z

Tsala: redirect

#redirect [[Activity chooser]]

MediaWiki:Sitenotice

2022-04-19T05:59:50Z

Tsala: removing status note

Upgrading

2022-03-26T14:03:57Z

Tsala: /* New capabilities in Moodle {{Version}} */ formatting

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Before upgrading, check that your server meets all requirements for {{Version}} in ''Site administration > Server > [[Environment]]''.

See the [{{Release notes}} release notes] in the dev docs for both [{{Release notes}}#Server_requirements server] and [{{Release notes}}#Client_requirements client] software requirements.

Notes:

* You can only upgrade to Moodle {{Version}} from Moodle 3.6 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/36/en/Upgrading_to_Moodle_3.6 upgrade to 3.6] as a first step.

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

Consider setting the [[Upgrade key|upgrade key]] for your site.

== Backup important data ==

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, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

==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. Then you should wait for any currently running cron processes to complete before proceeding.

== Install the new Moodle software ==
You can download the latest release from [https://download.moodle.org/ Moodle downloads].

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the [[Migration]] documents.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-latest-{{Version}}.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that 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 make moodle/config.php (and the rest of the source code) readable by your www server. For maximum security the files should not be writeable by your server. This is especially important on a 'production' server open to the public internet.

chown -R root:root moodle (Linux debian - or even create a user especially for moodle. '''Don't''' use the web server user, e.g. www-data)
chmod -R 755 moodle

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle {{Version}} 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.

== Finishing the upgrade ==

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

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to ''Site administration > Notifications''.

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!

Note: If you are running multiple servers then you should purge all caches manually (via ''Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a successful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

==Possible issues that may affect you in Moodle {{Version}}==

''Please add items here...''

* [[:dev:Core plugins review for Moodle 4.0]]
* [[:dev:Add a block cleanup]]

===New user tours===

Moodle 4.0 has four new [[User tours|user tours]] highlighting new features. If desired, they can be disabled in Site administration / Appearance / User tours.

See also the list of [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.0%20AND%20labels%20%3D%20upgrade_notes upgrade_notes-labelled issues] and [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.0%20AND%20labels%20%3D%20ui_change ui_change-labelled issues].

===New capabilities in Moodle {{Version}}===

* mod/bigbluebuttonbn:addinstance
* mod/bigbluebuttonbn:addinstancewithmeeting
* mod/bigbluebuttonbn:addinstancewithrecording
* mod/bigbluebuttonbn:deleterecordings
* mod/bigbluebuttonbn:importrecordings
* mod/bigbluebuttonbn:join
* mod/bigbluebuttonbn:managerecordings
* mod/bigbluebuttonbn:protectrecordings
* mod/bigbluebuttonbn:publishrecordings
* mod/bigbluebuttonbn:unprotectrecordings
* mod/bigbluebuttonbn:unpublishrecordings
* mod/bigbluebuttonbn:view

* mod/quiz:emailnotifyattemptgraded

* moodle/question:commentall
* moodle/question:commentmine

* moodle/reportbuilder:edit
* moodle/reportbuilder:editall
* moodle/reportbuilder:scheduleviewas
* moodle/reportbuilder:view

* qbank/customfields:changelockedcustomfields
* qbank/customfields:configurecustomfields
* qbank/customfields:viewhiddencustomfields

=== Moodle 3.6, 3.7, 3.8, 3.9, 3.10 and 3.11 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/36/en/Upgrading Upgrading to Moodle 3.6]
* [https://docs.moodle.org/37/en/Upgrading Upgrading to Moodle 3.7]
* [https://docs.moodle.org/38/en/Upgrading Upgrading to Moodle 3.8]
* [https://docs.moodle.org/39/en/Upgrading Upgrading to Moodle 3.9]
* [https://docs.moodle.org/310/en/Upgrading Upgrading to Moodle 3.10]
* [https://docs.moodle.org/311/en/Upgrading Upgrading to Moodle 3.11]

==Any questions about the process?==

Please post in the [https://moodle.org/mod/forum/view.php?id=28 Installing and upgrading help forum] on moodle.org.

==See also==

* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]
* [https://moodle.org/mod/forum/discuss.php?d=393570 Problem accessing dropdown such as personal profile since 3.8 (20191118) update] forum discussion

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

Upgrading

2022-03-26T14:03:25Z

Tsala: /* New capabilities in Moodle {{Version}} */ formatting

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Before upgrading, check that your server meets all requirements for {{Version}} in ''Site administration > Server > [[Environment]]''.

See the [{{Release notes}} release notes] in the dev docs for both [{{Release notes}}#Server_requirements server] and [{{Release notes}}#Client_requirements client] software requirements.

Notes:

* You can only upgrade to Moodle {{Version}} from Moodle 3.6 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/36/en/Upgrading_to_Moodle_3.6 upgrade to 3.6] as a first step.

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

Consider setting the [[Upgrade key|upgrade key]] for your site.

== Backup important data ==

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, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

==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. Then you should wait for any currently running cron processes to complete before proceeding.

== Install the new Moodle software ==
You can download the latest release from [https://download.moodle.org/ Moodle downloads].

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the [[Migration]] documents.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-latest-{{Version}}.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that 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 make moodle/config.php (and the rest of the source code) readable by your www server. For maximum security the files should not be writeable by your server. This is especially important on a 'production' server open to the public internet.

chown -R root:root moodle (Linux debian - or even create a user especially for moodle. '''Don't''' use the web server user, e.g. www-data)
chmod -R 755 moodle

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle {{Version}} 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.

== Finishing the upgrade ==

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

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to ''Site administration > Notifications''.

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!

Note: If you are running multiple servers then you should purge all caches manually (via ''Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a successful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

==Possible issues that may affect you in Moodle {{Version}}==

''Please add items here...''

* [[:dev:Core plugins review for Moodle 4.0]]
* [[:dev:Add a block cleanup]]

===New user tours===

Moodle 4.0 has four new [[User tours|user tours]] highlighting new features. If desired, they can be disabled in Site administration / Appearance / User tours.

See also the list of [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.0%20AND%20labels%20%3D%20upgrade_notes upgrade_notes-labelled issues] and [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.0%20AND%20labels%20%3D%20ui_change ui_change-labelled issues].

===New capabilities in Moodle {{Version}}===

* mod/bigbluebuttonbn:addinstance
* mod/bigbluebuttonbn:addinstancewithmeeting
* mod/bigbluebuttonbn:addinstancewithrecording
* mod/bigbluebuttonbn:deleterecordings
* mod/bigbluebuttonbn:importrecordings
* mod/bigbluebuttonbn:join
* mod/bigbluebuttonbn:managerecordings
* mod/bigbluebuttonbn:protectrecordings
* mod/bigbluebuttonbn:publishrecordings
* mod/bigbluebuttonbn:unprotectrecordings
* mod/bigbluebuttonbn:unpublishrecordings
* mod/bigbluebuttonbn:view

* mod/quiz:emailnotifyattemptgraded

* moodle/question:commentall
* moodle/question:commentmine

* moodle/reportbuilder:edit
* moodle/reportbuilder:editall
* moodle/reportbuilder:scheduleviewas
* moodle/reportbuilder:view

qbank/customfields:changelockedcustomfields
qbank/customfields:configurecustomfields
qbank/customfields:viewhiddencustomfields

=== Moodle 3.6, 3.7, 3.8, 3.9, 3.10 and 3.11 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/36/en/Upgrading Upgrading to Moodle 3.6]
* [https://docs.moodle.org/37/en/Upgrading Upgrading to Moodle 3.7]
* [https://docs.moodle.org/38/en/Upgrading Upgrading to Moodle 3.8]
* [https://docs.moodle.org/39/en/Upgrading Upgrading to Moodle 3.9]
* [https://docs.moodle.org/310/en/Upgrading Upgrading to Moodle 3.10]
* [https://docs.moodle.org/311/en/Upgrading Upgrading to Moodle 3.11]

==Any questions about the process?==

Please post in the [https://moodle.org/mod/forum/view.php?id=28 Installing and upgrading help forum] on moodle.org.

==See also==

* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]
* [https://moodle.org/mod/forum/discuss.php?d=393570 Problem accessing dropdown such as personal profile since 3.8 (20191118) update] forum discussion

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

Upgrading

2022-03-26T14:02:09Z

Tsala: /* New capabilities in Moodle {{Version}} */ 4.0 caps thanks to David Mudrak for list

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Before upgrading, check that your server meets all requirements for {{Version}} in ''Site administration > Server > [[Environment]]''.

See the [{{Release notes}} release notes] in the dev docs for both [{{Release notes}}#Server_requirements server] and [{{Release notes}}#Client_requirements client] software requirements.

Notes:

* You can only upgrade to Moodle {{Version}} from Moodle 3.6 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/36/en/Upgrading_to_Moodle_3.6 upgrade to 3.6] as a first step.

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

Consider setting the [[Upgrade key|upgrade key]] for your site.

== Backup important data ==

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, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

==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. Then you should wait for any currently running cron processes to complete before proceeding.

== Install the new Moodle software ==
You can download the latest release from [https://download.moodle.org/ Moodle downloads].

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the [[Migration]] documents.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-latest-{{Version}}.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that 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 make moodle/config.php (and the rest of the source code) readable by your www server. For maximum security the files should not be writeable by your server. This is especially important on a 'production' server open to the public internet.

chown -R root:root moodle (Linux debian - or even create a user especially for moodle. '''Don't''' use the web server user, e.g. www-data)
chmod -R 755 moodle

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle {{Version}} 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.

== Finishing the upgrade ==

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

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to ''Site administration > Notifications''.

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!

Note: If you are running multiple servers then you should purge all caches manually (via ''Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a successful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

==Possible issues that may affect you in Moodle {{Version}}==

''Please add items here...''

* [[:dev:Core plugins review for Moodle 4.0]]
* [[:dev:Add a block cleanup]]

===New user tours===

Moodle 4.0 has four new [[User tours|user tours]] highlighting new features. If desired, they can be disabled in Site administration / Appearance / User tours.

See also the list of [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.0%20AND%20labels%20%3D%20upgrade_notes upgrade_notes-labelled issues] and [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.0%20AND%20labels%20%3D%20ui_change ui_change-labelled issues].

===New capabilities in Moodle {{Version}}===

mod/bigbluebuttonbn:addinstance
mod/bigbluebuttonbn:addinstancewithmeeting
mod/bigbluebuttonbn:addinstancewithrecording
mod/bigbluebuttonbn:deleterecordings
mod/bigbluebuttonbn:importrecordings
mod/bigbluebuttonbn:join
mod/bigbluebuttonbn:managerecordings
mod/bigbluebuttonbn:protectrecordings
mod/bigbluebuttonbn:publishrecordings
mod/bigbluebuttonbn:unprotectrecordings
mod/bigbluebuttonbn:unpublishrecordings
mod/bigbluebuttonbn:view

mod/quiz:emailnotifyattemptgraded

moodle/question:commentall
moodle/question:commentmine

moodle/reportbuilder:edit
moodle/reportbuilder:editall
moodle/reportbuilder:scheduleviewas
moodle/reportbuilder:view

qbank/customfields:changelockedcustomfields
qbank/customfields:configurecustomfields
qbank/customfields:viewhiddencustomfields

=== Moodle 3.6, 3.7, 3.8, 3.9, 3.10 and 3.11 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/36/en/Upgrading Upgrading to Moodle 3.6]
* [https://docs.moodle.org/37/en/Upgrading Upgrading to Moodle 3.7]
* [https://docs.moodle.org/38/en/Upgrading Upgrading to Moodle 3.8]
* [https://docs.moodle.org/39/en/Upgrading Upgrading to Moodle 3.9]
* [https://docs.moodle.org/310/en/Upgrading Upgrading to Moodle 3.10]
* [https://docs.moodle.org/311/en/Upgrading Upgrading to Moodle 3.11]

==Any questions about the process?==

Please post in the [https://moodle.org/mod/forum/view.php?id=28 Installing and upgrading help forum] on moodle.org.

==See also==

* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]
* [https://moodle.org/mod/forum/discuss.php?d=393570 Problem accessing dropdown such as personal profile since 3.8 (20191118) update] forum discussion

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

Upgrading

2022-03-26T14:00:55Z

Tsala: /* Possible issues that may affect you in Moodle {{Version}} */ links update

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Before upgrading, check that your server meets all requirements for {{Version}} in ''Site administration > Server > [[Environment]]''.

See the [{{Release notes}} release notes] in the dev docs for both [{{Release notes}}#Server_requirements server] and [{{Release notes}}#Client_requirements client] software requirements.

Notes:

* You can only upgrade to Moodle {{Version}} from Moodle 3.6 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/36/en/Upgrading_to_Moodle_3.6 upgrade to 3.6] as a first step.

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

Consider setting the [[Upgrade key|upgrade key]] for your site.

== Backup important data ==

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, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

==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. Then you should wait for any currently running cron processes to complete before proceeding.

== Install the new Moodle software ==
You can download the latest release from [https://download.moodle.org/ Moodle downloads].

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the [[Migration]] documents.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-latest-{{Version}}.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that 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 make moodle/config.php (and the rest of the source code) readable by your www server. For maximum security the files should not be writeable by your server. This is especially important on a 'production' server open to the public internet.

chown -R root:root moodle (Linux debian - or even create a user especially for moodle. '''Don't''' use the web server user, e.g. www-data)
chmod -R 755 moodle

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle {{Version}} 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.

== Finishing the upgrade ==

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

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to ''Site administration > Notifications''.

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!

Note: If you are running multiple servers then you should purge all caches manually (via ''Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a successful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

==Possible issues that may affect you in Moodle {{Version}}==

''Please add items here...''

* [[:dev:Core plugins review for Moodle 4.0]]
* [[:dev:Add a block cleanup]]

===New user tours===

Moodle 4.0 has four new [[User tours|user tours]] highlighting new features. If desired, they can be disabled in Site administration / Appearance / User tours.

See also the list of [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.0%20AND%20labels%20%3D%20upgrade_notes upgrade_notes-labelled issues] and [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.0%20AND%20labels%20%3D%20ui_change ui_change-labelled issues].

===New capabilities in Moodle {{Version}}===

* block/accessreview:addinstance
* block/accessreview:view
* mod/quiz:viewoverrides
* moodle/contentbank:viewunlistedcontent
* tool/brickfield:viewcoursetools
* tool/brickfield:viewsystemtools

=== Moodle 3.6, 3.7, 3.8, 3.9, 3.10 and 3.11 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/36/en/Upgrading Upgrading to Moodle 3.6]
* [https://docs.moodle.org/37/en/Upgrading Upgrading to Moodle 3.7]
* [https://docs.moodle.org/38/en/Upgrading Upgrading to Moodle 3.8]
* [https://docs.moodle.org/39/en/Upgrading Upgrading to Moodle 3.9]
* [https://docs.moodle.org/310/en/Upgrading Upgrading to Moodle 3.10]
* [https://docs.moodle.org/311/en/Upgrading Upgrading to Moodle 3.11]

==Any questions about the process?==

Please post in the [https://moodle.org/mod/forum/view.php?id=28 Installing and upgrading help forum] on moodle.org.

==See also==

* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]
* [https://moodle.org/mod/forum/discuss.php?d=393570 Problem accessing dropdown such as personal profile since 3.8 (20191118) update] forum discussion

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

Upgrading

2022-03-26T13:58:15Z

Tsala: /* Possible issues that may affect you in Moodle {{Version}} */ update, dev docs links

{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''

==Check the requirements==

Before upgrading, check that your server meets all requirements for {{Version}} in ''Site administration > Server > [[Environment]]''.

See the [{{Release notes}} release notes] in the dev docs for both [{{Release notes}}#Server_requirements server] and [{{Release notes}}#Client_requirements client] software requirements.

Notes:

* You can only upgrade to Moodle {{Version}} from Moodle 3.6 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/36/en/Upgrading_to_Moodle_3.6 upgrade to 3.6] as a first step.

==Before upgrading==

'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''

Consider setting the [[Upgrade key|upgrade key]] for your site.

== Backup important data ==

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, your Postgres or MySQL database dump)

See [[Site backup]] for more specific information.

== Check for plugin updates ==

If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a {{Version}} version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

==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. Then you should wait for any currently running cron processes to complete before proceeding.

== Install the new Moodle software ==
You can download the latest release from [https://download.moodle.org/ Moodle downloads].

=== Standard install package ===

# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the [[Migration]] documents.

====Linux====
mv moodle moodle.backup
tar xvzf moodle-latest-{{Version}}.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that 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 make moodle/config.php (and the rest of the source code) readable by your www server. For maximum security the files should not be writeable by your server. This is especially important on a 'production' server open to the public internet.

chown -R root:root moodle (Linux debian - or even create a user especially for moodle. '''Don't''' use the web server user, e.g. www-data)
chmod -R 755 moodle

If you use cron, take care that cron.php is executeable and uses the correct php command:
chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.

=== Using Git ===

You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.

===Command line upgrade===

On Linux servers, Moodle {{Version}} 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.

== Finishing the upgrade ==

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

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to ''Site administration > Notifications''.

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!

Note: If you are running multiple servers then you should purge all caches manually (via ''Site administration > Development > Purge all caches'') after completing the upgrade on all servers.

===Fatal error: Maximum execution time of 30 seconds exceeded...===

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a successful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

==After upgrading==

==Possible issues that may affect you in Moodle {{Version}}==

''Please add items here...''

* [[:dev:Core plugins review for Moodle 4.0]]
* [[:dev:Add a block cleanup]]

===New user tours===

Moodle 4.0 has four new [[User tours|user tours]] highlighting new features. If desired, they can be disabled in Site administration / Appearance / User tours.

See also the list of [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%203.11%20AND%20labels%20%3D%20upgrade_notes upgrade_notes-labelled issues] and [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%203.11%20AND%20labels%20%3D%20ui_change ui_change-labelled issues].

===New capabilities in Moodle {{Version}}===

* block/accessreview:addinstance
* block/accessreview:view
* mod/quiz:viewoverrides
* moodle/contentbank:viewunlistedcontent
* tool/brickfield:viewcoursetools
* tool/brickfield:viewsystemtools

=== Moodle 3.6, 3.7, 3.8, 3.9, 3.10 and 3.11 improvements ===

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

* [https://docs.moodle.org/36/en/Upgrading Upgrading to Moodle 3.6]
* [https://docs.moodle.org/37/en/Upgrading Upgrading to Moodle 3.7]
* [https://docs.moodle.org/38/en/Upgrading Upgrading to Moodle 3.8]
* [https://docs.moodle.org/39/en/Upgrading Upgrading to Moodle 3.9]
* [https://docs.moodle.org/310/en/Upgrading Upgrading to Moodle 3.10]
* [https://docs.moodle.org/311/en/Upgrading Upgrading to Moodle 3.11]

==Any questions about the process?==

Please post in the [https://moodle.org/mod/forum/view.php?id=28 Installing and upgrading help forum] on moodle.org.

==See also==

* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]
* [https://moodle.org/mod/forum/discuss.php?d=393570 Problem accessing dropdown such as personal profile since 3.8 (20191118) update] forum discussion

[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[ja:Moodleをアップグレードする]]
[[de:Aktualisierung von Moodle]]

Aiken format

2022-03-17T13:00:17Z

Tsala: Export to Aiken format now available (MDL-21904)

{{Export questions}}
==About Aiken format==
The '''Aiken format''' is a very simple way of creating multiple choice questions using a clear human-readable format in a text file. (The [[GIFT format]] has many more options and perhaps is less prone to errors, but doesn't look as straightforward as AIKEN. ) The question must be all on one line. Each answer must start with a single uppercase letter, followed by a period '.' or a bracket ')', then a space. The answer line must immediately follow, starting with "ANSWER: " (NOTE the space after the colon) and then giving the appropriate letter.

IMPORTANT NOTES:
* You have to save the file in a '''text format'''. Don't save it as a Word document or anything like that.
* Non-ASCII characters like 'quotes' can cause import errors. To avoid this always save your text file in [[UTF-8|UTF-8 format]] (most text editors, even Word, will ask you).
* The answer letters (A,B,C etc.) and the word "ANSWER" '''must''' be capitalised as shown below, otherwise the import will fail.

Here is an example of the format:

<pre>What is the correct answer to this question?
A. Is it this one?
B. Maybe this answer?
C. Possibly this one?
D. Must be this one!
ANSWER: D

Which LMS has the most quiz import formats?
A) Moodle
B) ATutor
C) Claroline
D) Blackboard
E) WebCT
F) Ilias
ANSWER: A</pre>

Both these examples imported into Moodle gave questions looking like:

Which LMS has the most quiz import formats?
Choose one answer.
* a. Blackboard
* b. WebCT
* c. ATutor
* d. Moodle
* e. Claroline
* f. Ilias

== Importing ==

When importing there are many options, but these do not influence Aiken Format import:
* Get category from file [_]
* Get context from file [_]
* Match grades [Error if grade not listed/Nearest grade if not listed]
* Stop on error [Yes/No]

==Hints and Tips==

* Use a text editor, like PSPad, (Windows "notepad" may not save with right encoding) to write the file with questions and save as a TXT file in [[UTF-8|UTF-8 format]]. Use only simple ' not slant ones ´ ` ! Avoid other exotic characters like ... HORIZONTAL ELLIPSIS (http://www.fileformat.info/info/unicode/char/2026/index.htm, three dots as a single character).

*[http://moodle.heroku.com Moodle XML Converter] - more extensive version of AIKEN format. Supports almost all Moodle questions types - multichoice, shortanswer, cloze, essay, order, matching, numeric, truefalse

==See also==

*[[Import questions]]
*[[GIFT]]

[[Category:Questions]]
[[Category:Quiz]]
[[de:AIKEN]]
[[es:Formato Aiken]]
[[fr:Format Aiken]]

Mall:Export questions

2022-03-17T12:57:48Z

Tsala: Aiken format

<div class="navtrail">[[Main page]] ► [[Managing a Moodle course]] ► [[Questions]] ► [[Managing questions]] ► [[Export questions]] ► [[{{PAGENAME}}]]</div>
<div class="sideblock right" style="width: 12em;">
<div class="header">[[Export questions]]</div>
<div class="content">
* [[Aiken format]]
* [[GIFT format]]
* [[Moodle XML format]]
* [[XHTML format]]
</div>
</div>

<includeonly>[[Category:Questions]]</includeonly>
<noinclude>This template will categorise articles that include it into [[:Category:Questions]].</noinclude>

Aiken format

2022-03-17T12:56:03Z

Tsala: {{Export questions}}

{{Export questions}}
The '''Aiken format''' is a very simple way of creating multiple choice questions using a clear human-readable format in a text file. (The [[GIFT format]] has many more options and perhaps is less prone to errors, but doesn't look as straightforward as AIKEN. ) The question must be all on one line. Each answer must start with a single uppercase letter, followed by a period '.' or a bracket ')', then a space. The answer line must immediately follow, starting with "ANSWER: " (NOTE the space after the colon) and then giving the appropriate letter.

IMPORTANT NOTES:
* You have to save the file in a '''text format'''. Don't save it as a Word document or anything like that.
* Non-ASCII characters like 'quotes' can cause import errors. To avoid this always save your text file in [[UTF-8|UTF-8 format]] (most text editors, even Word, will ask you).
* The answer letters (A,B,C etc.) and the word "ANSWER" '''must''' be capitalised as shown below, otherwise the import will fail.

Here is an example of the format:

<pre>What is the correct answer to this question?
A. Is it this one?
B. Maybe this answer?
C. Possibly this one?
D. Must be this one!
ANSWER: D

Which LMS has the most quiz import formats?
A) Moodle
B) ATutor
C) Claroline
D) Blackboard
E) WebCT
F) Ilias
ANSWER: A</pre>

Both these examples imported into Moodle gave questions looking like:

<div class="note">
Which LMS has the most quiz import formats?
Choose one answer.
* a. Blackboard
* b. WebCT
* c. ATutor
* d. Moodle
* e. Claroline
* f. Ilias
</div>

== Importing ==

When importing there are many options, but these do not influence Aiken Format import:
* Get category from file [_]
* Get context from file [_]
* Match grades [Error if grade not listed/Nearest grade if not listed]
* Stop on error [Yes/No]

==Exporting==
Moodle does not have an Aiken format export. See MDL-21904. Jean-Michel Vedrine committed on 9 Oct 2014 [https://github.com/jmvedrine/moodle/commit/ed6bf151da57e52a4f6fd4526d85d35b763fb8bf some code in GitHub].

==Hints and Tips==

* Use a text editor, like PSPad, (Windows "notepad" may not save with right encoding) to write the file with questions and save as a TXT file in [[UTF-8|UTF-8 format]]. Use only simple ' not slant ones ´ ` ! Avoid other exotic characters like ... HORIZONTAL ELLIPSIS (http://www.fileformat.info/info/unicode/char/2026/index.htm, three dots as a single character).

*[http://moodle.heroku.com Moodle XML Converter] - more extensive version of AIKEN format. Supports almost all Moodle questions types - multichoice, shortanswer, cloze, essay, order, matching, numeric, truefalse

==See also==

*[[Import questions]]
*[[GIFT]]

[[Category:Questions]]
[[Category:Quiz]]
[[de:AIKEN]]
[[es:Formato Aiken]]
[[fr:Format Aiken]]

mod/bigbluebuttonbn/mod

2022-02-17T15:31:18Z

Tsala: redirect

#redirect [[BigBlueButton]]

Mall:Activities

2022-02-17T14:16:09Z

Tsala: BigBlueButton

<div class="navtrail">[[Main page]] ► [[Managing a Moodle course]] ► [[Activities]] ► [[{{PAGENAME}}]]</div>
<div class="sideblock right" style="width: 12em;">
<div class="header">[[Activities]]</div>
<div class="content">
* [[Managing activities]]
* [[Assignment activity|Assignment]]
* [[BigBlueButton]]
* [[Chat activity|Chat]]
* [[Choice activity|Choice]]
* [[Database activity|Database]]
* [[External tool|External tool]]
* [[Feedback activity|Feedback]]
* [[Forum activity|Forum]]
* [[Glossary activity|Glossary]]
* [[H5P activity|H5P]]
* [[Lesson activity|Lesson]]
* [[Quiz activity|Quiz]]
* [[SCORM activity|SCORM]]
* [[Survey activity|Survey]]
* [[Wiki activity|Wiki]]
* [[Workshop activity|Workshop]]
</div>
</div>

<includeonly>[[Category:Activity modules]]</includeonly>
<noinclude>This template will categorize articles that include it into [[:Category:Activity modules]].</noinclude>

BigBlueButton

2022-02-17T14:14:46Z

Tsala: {{Activities}}

{{Activities}}
{{New features}}
==What is the BigBlueButton activity?==
BigBlueButton lets you create from within Moodle links to real-time on-line classrooms using BigBlueButton, an open source web conferencing system for distance education. You can specify conference times, which are then added to the calendar, and, if allowed in your installation, the sessions may be recorded for viewing later.

Free Tier Hosting is currently restricted as follows:
# The maximum length for each session is 60 minutes;
# The maximum number of concurrent users per session is 25;
# Recordings expire after seven (7) days and are not downloadable; and
# Viewers' (student) webcams are only visible to the moderator.
==How is it set up?==
*In a course, with the editing turned, on add BigBlueButton from the activity chooser.
*Choose a name and description, and, if desired, a welcome message which will appear in the Chat box when participants join the session.
*If you tick "wait for moderator", students can only join once someone with the moderator role has entered the room.
*From the Participants list you can, if needed, give specific roles to specific people, such as a moderator role.
*In the Schedule section you can set a start time and also a time after which student will not be able to enter the room.
==How does it work?==
*Once set up, the activity appears with a link to join when the time is correct. (Before then, or if a moderator is required first. a message appears saying the conference has not yet started.)
[[File:bbb-room.png|alt=]]
*On entering the room, a message will appear asking if you want to use your microphone or just listen. If you choose microphone you will need to check your settings.
*The moderator can choose whether to allow participants to use webcams and microphones or not.
*The central area can display presentations, polls, screensharing or an interactive whiteboard.
*There is also a chat option with public and private chat.

[[Category:BigBlueButton]]
[[es:Guía rápida de BigBlueButton]]
[[File:bbb24 test-moodle.png|left|frameless|600x600px]]

Site admin presets

2022-02-10T08:16:25Z

Tsala: project page link, new features template

{{New features}}

==See also==

* The project page [[:dev:Site admin presets]]

admin/tool/admin presets/index

2022-02-10T08:14:20Z

Tsala: redirect

#redirect [[Site admin presets]]

BigBlueButton/view

2022-01-31T16:17:46Z

Tsala: redirect

#redirect [[BigBlueButton]]

BigBlueButton

2022-01-31T16:13:16Z

Tsala: new features template

{{New features}}
==What is the BigBlueButton activity?==

BigBlueButton lets you create from within Moodle links to real-time on-line classrooms using BigBlueButton, an open source web conferencing system for distance education. You can specify conference times, which are then added to the calendar, and, if allowed in your installation, the sessions may be recorded for viewing later.

Free Tier Hosting is currently restricted as follows:
# The maximum length for each session is 60 minutes;
# The maximum number of concurrent users per session is 25;
# Recordings expire after seven (7) days and are not downloadable; and
# Viewers' (student) webcams are only visible to the moderator.

==How is it set up?==
*In a course, with the editing turned, on add BigBlueButton from the activity chooser.
*Choose a name and description, and, if desired, a welcome message which will appear in the Chat box when participants join the session.
*If you tick "wait for moderator", students can only join once someone with the moderator role has entered the room.
*From the Participants list you can, if needed, give specific roles to specific people, such as a moderator role.
*In the Schedule section you can set a start time and also a time after which student will not be able to enter the room.
==How does it work?==
*Once set up, the activity appears with a link to join when the time is correct. (Before then, or if a moderator is required first. a message appears saying the conference has not yet started.)

[[File:BBB1.png]]

*On entering the room, a message will appear asking if you want to use your microphone or just listen. If you choose microphone you will need to check your settings.
*The moderator can choose whether to allow participants to use webcams and microphones or not.
*The central area can display presentations, polls, screensharing or an interactive whiteboard.
*There is also a chat option with public and private chat.

[[File:lakesbbb.png]]

[[Category:BigBlueButton]]

[[es:Guía rápida de BigBlueButton]]

BigBlueButton

2022-01-31T16:11:55Z

Tsala: Free Tier Hosting details (MDL-70658)

__NOTOC__
==What is the BigBlueButton activity?==

BigBlueButton lets you create from within Moodle links to real-time on-line classrooms using BigBlueButton, an open source web conferencing system for distance education. You can specify conference times, which are then added to the calendar, and, if allowed in your installation, the sessions may be recorded for viewing later.

Free Tier Hosting is currently restricted as follows:
# The maximum length for each session is 60 minutes;
# The maximum number of concurrent users per session is 25;
# Recordings expire after seven (7) days and are not downloadable; and
# Viewers' (student) webcams are only visible to the moderator.

==How is it set up?==
*In a course, with the editing turned, on add BigBlueButton from the activity chooser.
*Choose a name and description, and, if desired, a welcome message which will appear in the Chat box when participants join the session.
*If you tick "wait for moderator", students can only join once someone with the moderator role has entered the room.
*From the Participants list you can, if needed, give specific roles to specific people, such as a moderator role.
*In the Schedule section you can set a start time and also a time after which student will not be able to enter the room.
==How does it work?==
*Once set up, the activity appears with a link to join when the time is correct. (Before then, or if a moderator is required first. a message appears saying the conference has not yet started.)

[[File:BBB1.png]]

*On entering the room, a message will appear asking if you want to use your microphone or just listen. If you choose microphone you will need to check your settings.
*The moderator can choose whether to allow participants to use webcams and microphones or not.
*The central area can display presentations, polls, screensharing or an interactive whiteboard.
*There is also a chat option with public and private chat.

[[File:lakesbbb.png]]

[[Category:BigBlueButton]]

[[es:Guía rápida de BigBlueButton]]

BigBlueButton

2022-01-31T16:08:08Z

Tsala: info update

__NOTOC__
==What is the BigBlueButton activity?==

*BigBlueButton lets you create from within Moodle links to real-time on-line classrooms using BigBlueButton, an open source web conferencing system for distance education.
* You can specify conference times, which are then added to the calendar, and, if allowed in your installation, the sessions may be recorded for viewing later. (Recordings are not possible with [https://moodlecloud.com/en/ MoodleCloud] sites, for example.)

==How is it set up?==
*In a course, with the editing turned, on add BigBlueButton from the activity chooser.
*Choose a name and description, and, if desired, a welcome message which will appear in the Chat box when participants join the session.
*If you tick "wait for moderator", students can only join once someone with the moderator role has entered the room.
*From the Participants list you can, if needed, give specific roles to specific people, such as a moderator role.
*In the Schedule section you can set a start time and also a time after which student will not be able to enter the room.
==How does it work?==
*Once set up, the activity appears with a link to join when the time is correct. (Before then, or if a moderator is required first. a message appears saying the conference has not yet started.)

[[File:BBB1.png]]

*On entering the room, a message will appear asking if you want to use your microphone or just listen. If you choose microphone you will need to check your settings.
*The moderator can choose whether to allow participants to use webcams and microphones or not.
*The central area can display presentations, polls, screensharing or an interactive whiteboard.
*There is also a chat option with public and private chat.

[[File:lakesbbb.png]]

[[Category:BigBlueButton]]

[[es:Guía rápida de BigBlueButton]]

BigBlueButtonBN quick guide

2022-01-31T16:06:37Z

Tsala: Tsala moved page BigBlueButtonBN quick guide to BigBlueButton: BigBlueButton integrated into 4.0

#REDIRECT [[BigBlueButton]]

BigBlueButton

2022-01-31T16:06:36Z

Tsala: Tsala moved page BigBlueButtonBN quick guide to BigBlueButton: BigBlueButton integrated into 4.0

__NOTOC__
==What is the BigBlueButton activity?==
*BigBlueButtonBN lets you create from within Moodle links to real-time on-line classrooms using BigBlueButton, an open source web conferencing system for distance education.
* You can specify conference times, which are then added to the calendar, and, if allowed in your installation, the sessions may be recorded for viewing later. (Recordings are not possible with [https://moodlecloud.com/en/ MoodleCloud] sites, for example.)
*For more detailed information, see the full [[BigBlueButtonBN |BigBlueButtonBN documentation]]

==How is it set up?==
*In a course, with the editing turned, on add BigBlueButtonBN from the activity chooser.
*Choose a name and description, and, if desired, a welcome message which will appear in the Chat box when participants join the session.
*If you tick "wait for moderator", students can only join once someone with the moderator role has entered the room.
*From the Participants list you can, if needed, give specific roles to specific people, such as a moderator role.
*In the Schedule section you can set a start time and also a time after which student will not be able to enter the room.
==How does it work?==
*Once set up, the activity appears with a link to join when the time is correct. (Before then, or if a moderator is required first. a message appears saying the conference has not yet started.)

[[File:BBB1.png]]

*On entering the room, a message will appear asking if you want to use your microphone or just listen. If you choose microphone you will need to check your settings.
*The moderator can choose whether to allow participants to use webcams and microphones or not.
*The central area can display presentations, polls, screensharing or an interactive whiteboard.
*There is also a chat option with public and private chat.

[[File:lakesbbb.png]]

==How can I get it?==
BigBlueButtonBN is part of a set of contributed plugins which must be installed by the administrator from the [https://moodle.org/plugins/browse.php?list=set&id=2 plugins directory here.]

[[Category:Quick guide]]

[[es:Guía rápida de BigBlueButton]]

Git for Administrators

2022-01-28T15:09:03Z

Tsala: version update

{{Installing Moodle}}
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 [[:dev:Git for developers|Git for developers guide]].

To get the most of Git it is worth making the effort to understand its basic concepts - see the section below. It can be a bit of a steep learning curve, especially if you are used to CVS or Subversion.

== Getting hold of Git (Windows, OSX, Linux and others) ==

Support for Git was, up until recently, mostly confined to Linux but builds are now available for most popular operating systems:

* List of downloads from Git site - http://git-scm.com/download

Once you have downloaded and installed your OS relevant git installation, the git commands in this document should work with your operating system.

== Moodle branch names ==

Major Moodle versions each have their own branch in Git. For example, MOODLE_38_STABLE (3.8), MOODLE_39_STABLE (3.9). Development is generally done on branch 'master'. The entire lifetime of that version will stay on that branch. Each release is designated by adding a Git 'tag', for example v3.9.0-beta, v3.9.0-rc1, v3.9.0.

'''Important''': Even though the branch name has 'STABLE' in it, it does not mean that the code on that branch is actually stable. Soon after the branch is made it will contain 'beta' and 'release candidate' versions of the new Moodle version. It's important to check that the current state of the branch meets your needs. Generally, the easiest way is to examine the current contents of version.php - substitute the branch in this url, https://github.com/moodle/moodle/blob/MOODLE_39_STABLE/version.php

Do not use alpha, beta, release-candidates or code from the master branch for production sites. It could have significant bugs.

== Obtaining the code from Git ==

The command line version of Git is discussed here. Graphical clients are little more than wrappers around the command line version, so you should be able to deduce the correct parameters quite easily.

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
<pre>
$ cd /path/to/your/webroot
$ git clone git://git.moodle.org/moodle.git (1)
$ cd moodle
$ git branch -a (2)
$ git branch --track MOODLE_400_STABLE origin/MOODLE_400_STABLE (3)
$ git checkout MOODLE_400_STABLE (4)
</pre>
* The command (1) initializes the new local repository as a clone of the 'upstream' (i.e. the remote server based) moodle.git repository. The upstream repository is called 'origin' by default. It creates a new directory named ''moodle'', where it downloads all the files. This operation can take a while as it is actually getting the entire history of all Moodle versions
* The command (2) lists all available branches.
* Use the command (3) to create a new local branch called MOODLE_400_STABLE and set it to track the remote branch MOODLE_400_STABLE from the upstream repository.
* The command (4) actually switches to the newly created local branch.
==Git Connection Refused Error==
*If connection refused, use: $ git clone https://github.com/moodle/moodle.git
''fatal: unable to connect to git.moodle.org:
git.moodle.org[0: 34.210.133.53]: errno=Connection refused''

Note that Git has a huge number of options for each command and it's actually possible to do the above process with a single command (left as an exercise!!).

==Git from behind a firewall==

Git uses a read-only protocol that may be blocked by your firewall (port 9418). If this is a problem, you can use GitHub's http version <nowiki>https://github.com/moodle/moodle.git</nowiki>. It's a bit slower, so use the Git protocol if you can.

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

To update your code to the latest version (on the MOODLE_400_STABLE branch) '''all''' you have to do is:
<pre>
$ cd /path/to/your/moodle/
$ git pull
</pre>
If this is a production site you should still consider the [[Upgrade]] instructions (e.g. take backups).

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

This is one way to handle adding plugins from other Git repositories into your Moodle repository. Another way is to use Git Submodules. However, at the time of writing, this is one of Git's rougher features and should be regarded as an advanced option.

For example, let us say we want to install the [[Certificate module]] from its Git repository into our Moodle {{Version}}.
<pre>
$ cd /path/to/your/moodle/
$ cd mod (1)
$ git clone https://github.com/markn86/moodle-mod_certificate.git certificate (2)
$ cd certificate
$ git checkout -b MOODLE_400_STABLE origin/MOODLE_400_STABLE (3)
$ git branch -d master (4)
</pre>
The command (1) changes the current directory into the ''mod'' folder of your local Moodle clone. The command (2) creates a new subdirectory ''certificate'' and makes a local clone of vanilla Certificate repository. The command (3) creates a new local branch that will track the remote branch with a Certificate version for Moodle {{Version}}. 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.

Note: you should check first the compatibility of a module with your Moodle branch by asking directly to the Maintainer before cloning the repo or - if you want to guess it - by issuing the command below before running the command (3), in order to verify what is available among the branches:
<pre>
$ git branch -a
* master
remotes/origin/HEAD -> origin/master
remotes/origin/MOODLE_20_STABLE
remotes/origin/MOODLE_21_STABLE
remotes/origin/MOODLE_22_STABLE
remotes/origin/MOODLE_23_STABLE
remotes/origin/MOODLE_24_STABLE
remotes/origin/MOODLE_25_STABLE
remotes/origin/MOODLE_26_STABLE
remotes/origin/MOODLE_27_STABLE
remotes/origin/MOODLE_28_STABLE
remotes/origin/MOODLE_29_STABLE
remotes/origin/MOODLE_30_STABLE
remotes/origin/MOODLE_31_STABLE
remotes/origin/master
</pre>
This will avoid an error message when you issue the command (3) against a nonexistent branch, e.g.:
<pre>
§ git checkout -b MOODLE_31_STABLE origin/MOODLE_31_STABLE
fatal: git checkout: updating paths is incompatible with switching branches.
Did you intend to checkout 'origin/MOODLE_31_STABLE' which can not be resolved as commit?
</pre>

Note: To fix above error, use: "git fetch origin MOODLE_31_STABLE:LOCAL_MOODLE_31_STABLE"

Now it is wise to add the new directory mod/certificate/ to the list of ignored files of the main Moodle clone, otherwise a status of the main clone will keep reminding you that the new code has not been checked in.
<pre>
$ cd /path/to/your/moodle/
$ echo /mod/certificate/ >> .git/info/exclude
</pre>
To update your Moodle installation now, you must visit both Git repositories and pull changes from upstream.
<pre>
$ cd /path/to/your/moodle/
$ git pull
$ cd mod/certificate
$ git pull
</pre>
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.

== Installing and maintaining contributed extensions using Git submodules ==

As it was said in the previous section, this is for advanced users only.
Therefore, it is necessary, that you have some experience with Git and its commands.
A step-by-step explanation will be provided, but in order to follow these steps it is helpful to understand, what these commands do.

Advanced options and commands can be found at [https://git-scm.com/book/en/v2/Git-Tools-Submodules|the Git book].
If you have any questions about Git submodules, please visit the site above first.

=== Installing a new extension into an existing Moodle ===

As an example we use the [[Certificate module]] from the previous section.
<pre>
$ cd /path/to/your/moodle
$ git submodule add https://github.com/markn86/moodle-mod_certificate.git mod/certificate
</pre>

Note, that Git is reporting two new files in the repository:
<pre>
$ git status
# On branch MOODLE_29_STABLE
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# new file: .gitmodules
# new file: mod/certificate
#
</pre>

The file '''.gitmodules''' contains the local path and url of all your submodules.
It has to be committed, if you intend to clone the repository later (see the page [[Moodle development environment with Git submodules]]).
Before commiting, make sure to check the configuration of the plugin's Git repository, since the automatically generated settings may be not sufficient.
For future updates it is helpful, to track the remote branch, which corresponds to the Moodle version of your repository.
<pre>
$ cd mod/certificate
$ git branch -avv
* master 345f5b1 [origin/master] Replaced deprecated function
remotes/origin/HEAD -> origin/master
remotes/origin/MOODLE_20_STABLE 1aa1040 Added option to print 'grade category' grade
remotes/origin/MOODLE_21_STABLE 1aa1040 Added option to print 'grade category' grade
remotes/origin/MOODLE_22_STABLE 1aa1040 Added option to print 'grade category' grade
remotes/origin/MOODLE_23_STABLE fe047de Check that the function exists rather than relying on the Moodle version
remotes/origin/MOODLE_24_STABLE 1051f7d CONTRIB-4892 Fixed the email to others functionality
remotes/origin/MOODLE_25_STABLE cdb221a CONTRIB-4946: Removed character from language file breaking AMOS
remotes/origin/MOODLE_26_STABLE 696802a Increased version
remotes/origin/MOODLE_27_STABLE d3c0379 Increased version
remotes/origin/MOODLE_28_STABLE fa8df83 Increased version
remotes/origin/MOODLE_29_STABLE 3f03740 Replaced deprecated function
remotes/origin/master 345f5b1 Replaced deprecated function
</pre>

Git created the branch '''master''' which tracks '''origin/master''' automatically, because the remote repository has checked out '''master'''.
Therefore, create a new branch, which tracks the appropriate remote branch.
Of course, this is only possible, if the remote repository offers those branches.
<pre>
$ git checkout -b MOODLE_29_STABLE origin/MOODLE_29_STABLE
Branch MOODLE_29_STABLE set up to track remote branch MOODLE_29_STABLE from origin.
Switched to a new branch 'MOODLE_29_STABLE'
$ git branch -D master
Deleted branch master (was 345f5b1).
</pre>
It is not necessary to delete the '''master''' branch, but it's useless to keep it.
In fact, these settings don't need to be touched afterwards.

The final step is to commit the changes to the main repository.
<pre>
$ cd /path/to/your/moodle
$ git commit -a -m "New extension mod_certificate installed"
</pre>

It has to be ensured, that the commit includes only the changes for the new Git submodule (since '''-a''' commits all non-staged changes).

=== Maintaining Git submodules ===

Maintaining a set of submodules is extremely easy.
Consider a Moodle repository with several submodules installed.
Keep in mind, that the extension '''mod_mylittleextension''' is a fake plugin, created for a test scenario in this example.
It is not an official Moodle module. For updating all your submodules at once, type in:
<pre>
$ cd /path/to/your/moodle
$ git submodule foreach git pull
Entering 'block/coursefeedback'
Already up-to-date.
Entering 'mod/certificate'
Already up-to-date.
Entering 'mod/mylittleextension'
remote: Counting objects: 6, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 4 (delta 0), reused 0 (delta 0)
Unpacking objects: 100% (4/4), done.
From /local/repositories/mle
89d9eae..64c122d master -> origin/master
Updating 89d9eae..64c122d
Fast-forward
index.html | 9 +++++++++
version.php | 6 +++---
2 files changed, 12 insertions(+), 3 deletions(-)
create mode 100644 index.html
$ git status
# On branch MOODLE_29_STABLE
# Changes not staged for commit:
# (use "git add <file>..." to update what will be committed)
# (use "git checkout -- <file>..." to discard changes in working directory)
#
# modified: mod/mylittleextension (new commits)
#
</pre>

The command '''git submodule foreach [another command]''' walks through all submodule repositiories and executes what is specified by '''[another command]'''.
In this case it is '''git pull'''.
Therefore, the module mylittleextension was updated and the main repository isn't clean anymore until changes are committed:
<pre>
$ git commit -a -m "Plugin updates"
</pre>

Maintaining plugins with Git submodules has also another application than simplifying the update process.
In a greater scale it can be used to maintain a Moodle project, where multiple developers need to have an exact copy of your moodle without organizing external plugins manually.
You can read more about this topic at the page [[Moodle development environment with Git submodules]].

== See also ==

* [[Windows installation using Git]]
* [[Git for Mac]]
* [[:dev:Moodle versions]]
* For fixing a Tracker Issue (MDL) / Forking Moodle / CONTRIButing code [[:dev:User:Sam Hemelryk/My Moodle Git workflow|User:Sam_Hemelryk/My_Moodle_Git_workflow]]
* [[Moodle Production Server with GIT|Case study Git + Moodle from Technical University Berlin]]

; Moodle forum discussions
* [https://moodle.org/mod/forum/discuss.php?d=255175 Github and Moodle deployment for production]
* [http://moodle.org/mod/forum/discuss.php?d=168094 GIT help needed]
* [https://moodle.org/mod/forum/discuss.php?d=231046 Clear git guide for Admins (not developers)]
* [https://moodle.org/mod/forum/discuss.php?d=393756 Best way to use Git]

; External resources
* [http://thamblings.blogspot.com.au/2013/07/upgrading-moodle-from-git.html Deploying Moodle from git - Blog post from a production experience]
* [http://gitref.org/ Git Reference]
* [http://progit.org/book/ Pro Git book]

[[ja:管理者用Git]]
[[fr:Git pour administrateurs]]
[[es:Git para Administradores]]
[[en:Git für Administratoren]]

Mall:Version2

2022-01-28T15:06:41Z

Tsala: version update

400

Mall:Version

2022-01-28T15:06:12Z

Tsala: version update

4.0

Upgrading to Moodle 4.0

2022-01-28T14:44:29Z

Tsala: redirect

#redirect [[Upgrading]]

Kategori:New features

2022-01-28T14:43:32Z

Tsala: version update

{{Main page}}
A list of pages documenting new features in Moodle 4.0

==See also==

* [[New features]] highlights

[[es:Categoría:Nuevas características de Moodle 4.0]]
[[de:Category:Neue Funktionalität]]

Mall:New features

2022-01-28T14:42:41Z

Tsala: version update

<span class="small-info-right">[[:Category:New features|New feature<br />in '''Moodle 4.0'''!]]</span>
<includeonly>[[Category:New features]]</includeonly>
<noinclude>This template will categorize articles that include it into [[:Category:New features]].</noinclude>

MediaWiki:Sitenotice

2022-01-28T12:19:08Z

Tsala: status note

<div class="alert alert-info">We're currently working on documenting the new features and improvements in 4.0, ready for its release.</div>

Main page

2022-01-28T12:18:18Z

Tsala: version update

{{#addbodyclass:moodledocs-logo}}
<div class="navtrail">[https://docs.moodle.org/overview/ Docs overview] ► [[{{PAGENAME}}|Moodle Docs 4.0]]</div>

<div class="card-deck">
<div class="card">
<div class="card-body">
<h4 class="card-title">Get started</h4>
<p class="card-text">
* [[Features|Browse features]]
* [[Teacher quick guide]]
* [[Admin quick guide]]
* [[Installation quick guide]]
</p>
</div>
<div class="card-footer">
: [[:Category:Quick guide|More quick guides <i class="fa fa-sm fa-arrow-right" aria-hidden="true"></i>]]
</div>
</div>

<div class="card">
<div class="card-body">
<h4 class="card-title">Manage your course</h4>
<p class="card-text">
* [[Course homepage|Set up your course]]
* [[Add students|Add students]]
* [[Tracking progress|Track progress]]
* [[Working with files|Upload files]]
</p>
</div>
<div class="card-footer">
: [[Managing a Moodle course|More for teachers <i class="fa fa-sm fa-arrow-right" aria-hidden="true"></i>]]
</div>
</div>

<div class="card">
<div class="card-body">
<h4 class="card-title">Add activities</h4>
<p class="card-text">
* [[Assignment activity|Use assignments to assess]]
* [[Forum activity|Discuss in forums]]
* [[Quiz activity|Test students with a quiz]]
* [[Workshop activity|Peer-assess with a workshop]]
</p>
</div>
<div class="card-footer">
: [[Activities|More activities <i class="fa fa-sm fa-arrow-right" aria-hidden="true"></i>]]
</div>
</div>
</div>

<div class="card-deck mt-3">
<div class="card">
<div class="card-body">
<h4 class="card-title">What's new</h4>
<p class="card-text">
* [[New for teachers|For teachers]]
* [[New for students|For students]]
* [[New for administrators|For admins]]
* [[New for mobile|Mobile]]
</p>
</div>
<div class="card-footer">
: [[New features|New features list <i class="fa fa-sm fa-arrow-right" aria-hidden="true"></i>]]
</div>
</div>

<div class="card">
<div class="card-body">
<h4 class="card-title">Manage your site</h4>
<p class="card-text">
* [[Add users|Add users]]
* [[Adding a new course|Add courses]]
* [[Site appearance|Change the look and feel]]
* [[Installing plugins|Install plugins]]
</p>
</div>
<div class="card-footer">
: [[Managing a Moodle site|More for administrators <i class="fa fa-sm fa-arrow-right" aria-hidden="true"></i>]]
</div>
</div>

<div class="card">
<div class="card-body">
<h4 class="card-title">Moodle app</h4>
<p class="card-text">
* [[Moodle app features|View app features]]
* [[Moodle app notifications|Keep up-to-date with notifications]]
* [[Creating Moodle-app-friendly courses|Create mobile-friendly courses]]
* [[Moodle app additional features|Add more app features]]
</p>
</div>
<div class="card-footer">
: [[Moodle app|More about the Moodle app <i class="fa fa-sm fa-arrow-right" aria-hidden="true"></i>]]
</div>
</div>
</div>

__NOTOC__

[[de:Hauptseite]]
[[es:Página Principal]]
[[eu:Azala]]
[[fr:Accueil]]
[[hr:Glavna stranica]]
[[it:Pagina_principale]]
[[ja:メインページ]]
[[pt-br:Página_principal]]
[[zh:首页]]

MediaWiki:MoodleDocsVersionLinks

2022-01-28T12:16:27Z

Tsala: typo fix

4.0 docs: /400/en/{{FULLPAGENAMEE}}
3.11 docs: /311/en/{{FULLPAGENAMEE}}
3.10 docs: /310/en/{{FULLPAGENAMEE}}
3.9 docs: /39/en/{{FULLPAGENAMEE}}

MediaWiki:MoodleDocsVersionLinks

2022-01-28T12:16:04Z

Tsala: 4.0 link

4.00 docs: /400/en/{{FULLPAGENAMEE}}
3.11 docs: /311/en/{{FULLPAGENAMEE}}
3.10 docs: /310/en/{{FULLPAGENAMEE}}
3.9 docs: /39/en/{{FULLPAGENAMEE}}

Capabilities/moodle/calendar:manageentries

2022-01-18T17:01:46Z

Tsala: manual entries

{{Capabilities}}
*This allows a user to add, update or delete manual [[Calendar|calendar]] entries in the context this capability applies to (system, course category or course)
*This capability is allowed for the default roles of manager, teacher and non-editing teacher

==Example usage==
*[[Calendar editor role]]

[[Category:Capabilities|Calendar]]
[[Category:Calendar]]

[[fr:Capabilities/moodle/calendar:manageentries]]
[[ja:ケイパビリティ/moodle/calendar:manageentries]]

Course homepage

2022-01-18T15:14:45Z

Tsala: /* Activities and resources */ removing mention of activity chooser user preference (MDL-73616)

{{Courses}}
===Parts of a course homepage===

Watch the screencasts '''[https://youtu.be/ZsNK44EqRkg What is a course?]''' and '''[https://youtu.be/y12xYdGOq0s How to lay out your course]''' for an introduction on setting up your course homepage.

A Moodle course can look very different according to the theme and course format (layout). Here are a blank course page using the [[Boost theme]] and the Classic theme, both with standard weekly format:

[[File:BoostExampleBlocks.png|thumb|center||600px|Empty course with Boost theme showing side blocks]]

[[File:ExampleClassic.png|thumb|600px|center|Empty course with Classic theme]]

1.[[Navigation block]]

Normally visible on all pages, this block helps you find your way around the course and site.

2.[[Administration block]]

Again, normally visible on all pages, this block gives different levels of access to teachers and students.

3.[[Course formats|Course sections]]

Here is where the learning materials are displayed. This element may be arranged in one or multiple weeks, topics, forums or other (non-standard) layouts.

4.[[Blocks|Side blocks]]

Which blocks you see depend on what the administrator has selected and what you as teacher choose to add.

5. Navigation drawer

This replaces the [[Navigation block]] and [[Administration block]] in the Boost theme. For course section links to appear, 'Always link course sections' (linkcoursesections) must be enabled by an administrator in the Site administration.

6. Gear menu

This replaces the course administration settings in the Boost theme.

===To edit a course section===

# Turn editing on
# Click the pencil icon (1 in screenshot below) to quickly rename the section
# Click the Edit menu (2 in screenshot below) to edit the description and other settings.
[[File:31editsection.png|thumb|center|600px|Section editing menu]]

If [[Restrict access]] is enabled for the site, access to the section (including all activities and resources within it) may be restricted.

===To move a course section===
#Turn editing on
#Click the up/down arrow or the crosshairs icon to move the section
#Drag the section to where you want to position it and let go

Note: The ability to move course sections is controlled by the capability [[Capabilities/moodle/course:movesections|moodle/course:movesections]], which is allowed for the default role of teacher.
===To add course sections===
#Turn editing on
#Click 'Add topics/weeks' underneath the bottom section
#Select the number of extra sections you wish and press 'Add topics/weeks':

[[File:33Addtopics.png|thumb|400px|center|Adding sections]]

===To delete a course section===

With the editing turned on, click the 'Edit' link to the right of the course section you wish to delete and then, from the menu that displays, click 'X Delete'. You will be prompted to confirm your wish to delete the section and its contents. Note that all activities inside the section and their user data will also be deleted. Use the [[Recycle bin]] to reverse this if you do it by mistake.

===To link course sections===

An admin setting ''Always link course sections'' can be enabled from ''Site administration > Appearance > Navigation'' and will link course sections so that when a course section name is clicked in the navigation block or the central content area, it will go directly to that section.

==Blocks==

Depending on the theme, blocks are displayed in the right and/or left columns of the course page. The [[Boost theme]] only displays blocks on the right, and when using the [[Moodle Mobile app]] blocks do not display at all.

To add a block to the course page

#Turn on the editing from the gear menu of the button top right depending on your theme.
#Select a block from the "Add block" link, either at the bottom of the nav drawer on the left or a drop down menu usually on the right.

To move a block
#Ensure editing is turned on then click onto the block title until the crosshair icon appears
#While keeping the block selected, drag it to where you want to position it and let go.

Alternatively
#Click on the up/down arrow
#Click on the place holder (a zone with a dashed border) where you want the block to appear.

{|
| [[File:moveblocksnew.png|thumb|Crosshair icon for moving a block]]
| [[File:Moveblocks.png|thumb|Up/down arrow icon for moving a block]]
|}

==Activities and resources==

To add an activity or resource to the course
*Turn on the editing from the button top right.

*Click 'Add an activity or resource' to open the activity chooser. Double-click to add an activity or resource; click the i for more information and click the star icon to add it to a separate, starred tab.

Alternatively, certain resources and activities may be added using drag and drop:

*To add a [[File|file]], simply drag and drop it onto the course section where you'd like it to appear
*To add a [[Folder|folder of files]], simply zip the folder then drag and drop it onto the course section where you'd like it to appear, answer 'Unzip files and create folder' to the popup dialogue, then click the upload button
*To add a [[SCORM module|SCORM package]], simply drag and drop it onto the course section where you'd like it to appear, answer 'Add a SCORM package' to the popup dialogue, then click the upload button

===Moving between activities===
Underneath each activity is a link on the left to the previous activity and on the right to the next activity. A jump-to menu also allows you to choose other activities from the course page:

[[File:CHPActivityLinks.png]]

==Editing elements on your course homepage==
With the editing turned on, activities, resources and blocks will have icons performing different functions such as edit/move/copy/delete/hide.

''Note:''' ''Your theme may have icons different from these below:''

:[[Image:pencil.png]] - the pencil icon allows you to edit inline the title of the resource / activity

:[[Image:26actionicon.png|150px]] - this icon groups actions together for easier editing on smaller screens. Click to reveal the options.

:[[Image:moveajax24.png]]- the move icon allows you to move items or sections by dragging and dropping. (If you have many activities to scroll through while moving, see the Tips and Tricks section below for a useful suggestion.)

:[[Image:movenoajaz241.png]] - this move icon appears if you don't have Ajax enabled.

:[[File:groups24.png]] - the groups icon allows you to change between no groups or separate/visible groups

:[[Image:movenoajax24.png]] - the move here icon appears when moving a course element without Ajax. Click into the box to re-locate your item.

:[[File:topicmove24.png]] - the up/down arrows allow you to move course sections up or down and appear if you do not have Ajax enabled.

==Tips and tricks==
===Moving items in a course with many activities===
If you click and drag an activity or resource on a course page which has many items, this might cause you difficulties with "scroll of death" issues. Instead of dragging the activity to move it, click on it. It will display a list of all the items on your page and you just need to click to select where on the course page you want the item to be moved to.

[[File:alternativemovemethod.png|thumb|center|500px]]

*Make your course home page look more like a webpage - see [[Stealth activities]]
*Activity and resource descriptions can be displayed on the course page just below the link to the activity or resource by clicking the 'Display description on course page' checkbox in the activity or resource settings.

==Course homepage capabilities==

*[[Capabilities/moodle/course:sectionvisibility|Control section visibility]]
*[[Capabilities/moodle/course:setcurrentsection|Set current section]]

[[es:Página principal del curso]]
[[fr:Page d'accueil de cours]]
[[ja:コースホームページ]]
[[de:Kursseite]]

Language FAQ

2021-12-06T10:28:00Z

Tsala: /* Why are my changes not saved if I edit a language pack with the Moodle language pack editor? */ https://moodle.org/mod/forum/discuss.php?d=429283

{{Language}}

== General ==

=== Which is the official language for Moodle? ===
The [http://lang.moodle.org/mod/forum/discuss.php?d=2617 "official"] language for Moodle is actually the Australian English (''hey mate!'') , which is 100% the same as UK English. The default language on a new installation of Moodle, unless you change it, will be this version of English, denoted by the language code "en".

=== What do codes like "en" and "en_us" or "es" and "es_mx" and "es_ve" mean?? ===

These are the language codes for each language. There is a standard for these, see [https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO language code list].

The second part, "_us" or "_mx" and "_ve" for example, represent localisations of the main language for a particular country or dialect. Typically these will include variant spellings and other preferred local terminology and phrasing. So "es_mx" has spellings and idioms (and a very important [[Decimal separator]]) used in Mexican Spanish which are distinct from international Spanish. The es_ve has small differences from the international spanish that are of significance to Moodle users in Venezuela.

"en_us" is the English - United States language pack; "en" is Australian English, which is practically the same as British English.

=== I found a mistake or typo in a language pack. Or my language is only partial, much of it is still English. What do I do? ===

Language packs have maintainers and Moodle has its own language translation toolkit, known as AMOS. Other than some core languages maintained by Moodle HQ, most languages are maintained by volunteer maintainers.

See the [https://docs.moodle.org/dev/Translation_FAQ Translation FAQ page] for how to report issues and [https://lang.moodle.org/mod/page/view.php?id=9 the AMOS for newcomers page] for more information.

== Default Language ==

=== Where can I set the default language for the site? ===

''Site Administration > Language > [[Language settings]]''

Note you can only choose to set as default a Language pack that is already installed. If the language you want is not on the list, you will need to install the language pack first. See [[Language packs]].

=== When I change to a new default language, users still have the old language. ===

Correct. When you change to a new site default language, this does not update the language setting in the profile for already existing users. It only sets a new default for new user accounts you create from now on.

To do updates for already existing users, you can:

* Tell users how to change it themselves in their user profiles by setting their Preferences > Preferred language
* Use the [[Upload users]] tool to do a mass update from a csv file changing the lang field
* If you have access to the database, you can change this with a simple query. See [[ad-hoc_contributed_reports#List_of_users_with_language|here for an example]] of how to do this.

=== When I log in, the language switches to English. Why? ===

* For logged-in users, the language is set to the one they have set as their preferred language (Preferences > User account > Preferred language).
* For logged-out visitors (before they log in) the situation depends on whether the language auto-detection is enabled. They can either get the language their browser claims to be the requested one, or the site default language.

=== I've set a default site language, but the Moodle calendar is in English. Why? ===

* If your Moodle calendar is not translated, then the string 'locale' (for *nix and Mac servers) or the string 'localewin' (for Windows servers) in the 'langconfig.php' file is wrong (or your server is not configured to support the language).
* There are quite a few languages that are not supported by Windows servers and the localewin server can not be set. In that case, you have to run your Moodle on a *nix server to make the translation of your Moodle calendar work.
* Mac OSs have very poor locale support.
* See [[:dev:Translation_langconfig]] for details.

Actually, the one and only place where Moodle requires some locales to be installed on the machine is when handling date translation (according to [https://tracker.moodle.org/browse/MDL-31622 this information]).

=== How can I disable (hide) the language dropdown menu on the site front page? ===

Go to ''Site administration > Language > Language settings'' and un-tick the 'Display language menu' checkbox.

Because it is a customisation, Moodle will not erase the xx_local language files in Moodledata with an upgrade. Moodle will upgrade any language folders it finds in the moodle/lang folder.

==Warning message: Your server does not seem to fully support the following languages:==
When you install or update a language pack, your server might display the following warning:
Your server does not seem to fully support the following languages:
followed by a list of non-supported languages and the text:
Instead, the global locale (en_AU.UTF-8) will be used to format certain strings such as dates and numbers.
[[File:Your_server_does_not_seem_to_fully_support.png|400px]]

* This is caused by either:
** a problem with the locale (Linux and Mac) or localewin (windows) setting in langconfig.php for your language pack (you can contact your language pack maintainer listed in the [https://lang.moodle.org/local/amos/credits.php translation credits])
** or the configuration of your server.
* If you have a Linux server (or a [[MoodleBox]]), see the documentation about [https://docs.moodle.org/dev/Table_of_locales installing additional locales].
* If you have a Windows or a Mac Moodle server that lacks the proper locales, we can not help you :(

* See the [https://docs.moodle.org/dev/Translation_langconfig developer's documentation]

== Language Customisation and Multi-language ==

=== How can I change a word or phrase used in Moodle? ===

In ''Administration > Site Administration > Language > Language customisation''.

See [[Language customisation]] for details.

=== How can I find where a language string is located? ===

See the section 'Finding the component and string identifier' in [[Language customisation]].

===Why are my changes not saved in my MoodleCloud site?===
Unfortunately customising language strings is not supported in MoodleCloud. (The same string cache is used for for all sites and is read-only.)

=== Why are my changes not saved if I edit a language pack with the Moodle language pack editor? ===

This could be caused by the caching on the server. Language strings are cached into server memory for performance reasons and when you save changes, they may not be immediately picked up. First, refresh your own browser cache to refresh the pages from the site. Then if the strings are still not there, an administrator can purge the cache of the server.

Another possibility is editing one language pack but testing with another. For more possibilities, see the discussion [https://moodle.org/mod/forum/discuss.php?d=429283 Dashboard "Timeline Block" Strings].

===How can I provide course content in more than one language?===

Labels, web pages, activity descriptions etc. may be provided in more than one language using the [[Multi language content|Multi language content filter]].

Another option is to create activities in different languages and restrict access to them using the [https://moodle.org/plugins/availability_language Restriction by language plugin].

See the discussion [https://moodle.org/mod/forum/discuss.php?d=383302 Multiple Languages] for further options.

===How can I provide course headings in more than one language?===

Set the multi language content filter to apply to content AND headings in ''Site administration > Plugins > Filters > Manage filters''.

===Are there any short cuts for editing a language?===
Yes, but be careful. You can make use of the customise language process. Basically copy the php files that contain the strings you want to change to the moodledata/lang/local folder. For example, copy the /lang/en/moodle.php file to someplace. Edit the file with a search and replace with whole word and case sensitive turned on, change Teacher to Instructor and Teachers to Instructors, do the same for teacher and teachers. Now copy that saved copy of the moodle.php file to the moodledata/lang/en_local folder. Be careful not to change the String name.

===Is it possible to customise language strings per theme?===
Not by default, as when strings are customised, they are customised for the whole site. However, it is possible to make a new language pack based on your main language and apply that pack to the course which has the theme. See this forum post for more information: https://moodle.org/mod/forum/discuss.php?d=220671

===Is it possible to use a translation extension in the browser to display a Moodle site in another language===
Yes, according to [https://moodle.org/mod/forum/discuss.php?d=414236#p1669886 this forum post]:

* For Firefox:
** Install the [https://www.mozilla.org/en-US/exp/firefox/new/ Firefox brower] if not already installed on your computer.
** Open Firefox.
** Go to Firefox [https://addons.mozilla.org/en-US/firefox/ Browser Add-ons].
** Search the [https://addons.mozilla.org/en-US/firefox/addon/traduzir-paginas-web/ Translate Web Pages extension], by Filipe Ps, and add it to Firefox.
** Follow the instructions for this extension.

* For Chrome:
** Install [https://www.google.com/intl/en/chrome/ Google Chrome] if not already installed on your computer.
** Open Chrome.
** From the Google Web Store, install the [https://chrome.google.com/webstore/detail/google-translate/aapbdbdomjkkjkaonfhkkikfgjllcleb?utm_source=chrome-ntp-icon Google Translate extension].
** Turn translation on by following [https://www.howtogeek.com/407924/how-to-turn-translation-on-or-off-in-chrome/ these steps] (from How-To Geek).

===Is it possible to change the logo according to language selected, similar to multi-language content?===
Yes. See [https://moodle.org/mod/forum/discuss.php?d=345919 this forum thread]

== Other Language Questions ==

===Will installing several language packs decrease my server performance?===
Installing many (20+) language packs have [https://moodle.org/mod/forum/discuss.php?d=241098 almost 0 impact] on Moodle performance. A copy of the language packs installed are stored in your site's local /mooodledata directory. Also, actively used language strings are cached in memory by your server as well to help performance, so as long as your server has sufficient RAM there will be no impact from having many language packs installed.

=== What is this Pirate version of English doing on my site? ===

It has become something of a custom in the Moodle community over the years to observe [https://en.wikipedia.org/wiki/International_Talk_Like_a_Pirate_Day 'Talk Like a Pirate Day'] (September 19th) by temporarily changing the language of a site to allow the English - Pirate (en_ar) language pack. See the discussion [https://moodle.org/mod/forum/discuss.php?d=132888 here] for more.

===Lang pack download failed with 'HTTP response code: HTTP/1.1 404 Not Found' after new release ===

After we branch for a new release, Moodle will try and download the new version of lang packs, however for a while development is on-sync and no new language string differences will be introduced between the two branches. During this period, AMOS is not branched and so Moodle will fail to download new language packs.

This is expected and it will be resolved once AMOS is opened up for new changes in the new version. See MDL-34028 for example.

===Why do the characters for my language (not English) show up as hollow squares ?===

[[File:Language_pack_name_not_displayed.png|400px]]

This problem may be caused by a missing/wrong character set or using a font that does not support the character map needed (see [https://moodle.org/mod/forum/discuss.php?d=327521 this forum thead]).

[[File:Language pack name is displayed.png|400px]]

===Are there statistics for language packs downloads?===
Yes. There are download stats for the past 60 days at [https://download.moodle.org/local/downloadmoodleorg/stats.php Moodle downloads stats]. See under Languages a long list of the different packs that have been downloaded:
[[File:Language packs downloads stats.png]]

===Is it possible to streamline the translation of a Moodle course?===
Kind of... See [https://docs.moodle.org/dev/Translation#Translating_a_Moodle_course Translating a Moodle course] in the developer's documentation.

===Can I disable google page translation on my Moodle site?===
Yes, according to [https://moodle.org/mod/forum/discuss.php?d=419424#p1690452 this post]:
The general answer is to add translate="no" to the html tag of your page, but that requires a code change.
So the Moodle html-page starts with (source https://stackoverflow.com/questions/12238396/how-to-disable-google-translate-from-html-in-chrome)
There are more options in the source discussion that are finer to control.
In moodle/admin/settings.php?section=additionalhtml, you can add in the section
<meta name="google" content="notranslate" />
and that should stop Google chrome to translate...
===Can I add another language key to my Windows PC?===
Yes. If you have an English keyboard in your PC, but you want to write Spanish words like "Hasta mañana" and you need to type the 'ñ' letter, see [https://support.microsoft.com/en-us/windows/manage-the-input-and-display-language-settings-in-windows-10-12a10cb4-8626-9b77-0ccb-5013e0c7c7a2 this link].

== See also ==

Forum discussions:
* [http://moodle.org/mod/forum/discuss.php?d=131927#p604462 Edited Strings Not Visible]
* [https://moodle.org/mod/forum/discuss.php?d=316623#unread Months names in Arabic language pack]
* [https://moodle.org/mod/forum/discuss.php?d=395788#p1595968 Multilingual moodle]

* MDL-57867 - Email notification language strings lose line breaks when customised bug

==Any further questions?==

Please post in the [http://moodle.org/mod/forum/view.php?f=26 Languages forum] on moodle.org.

[[Category:FAQ]]

[[fr:FAQ de langue]]
[[de:Sprache FAQ]]
[[es:Idioma FAQ]]

Course overview report

2021-12-03T13:12:31Z

Tsala: rearranging content

{{Sitewide reports}}
An administrator can generate course overview reports in ''Administration > Site administration > Reports > Course overview''. [[Statistics]] must be enabled first.

You can choose to view reports of the most active courses or the most participatory courses over a certain time period. Results are displayed in a bar chart and in a table.

These reports refer to the concepts of Activity, Views and Posts.

==Report examples==
<gallery caption="Report examples - click on any chart to enlarge" widths="200px" heights="200px" perrow="3">
Image:Most participatory courses.png |Chart of top 20 participatory courses)
Image:Most active courses.png| Most active courses
Image:Most active courses (weighted).png| Most active courses (weighted)
</gallery>

==Report measures==

===What is Activity?===

Activity = number of Views + number of Posts from users in the course, over the period of interest.

===What's the difference between a View and a Post?===

*"Views" are instances of a user accessing a Moodle resource or activity to "read" or download it.
*"Posts" are more active responses such as: submit a quiz, submit an assignment, respond to a discussion forum etc. Posts are not just discussion forum posts!

===What is the Participation ratio?===

For the report type 'Most participatory courses (posts/views)'

Participation ratio = posts / views

- in other words the number of posts divided by the number of views

For the report type 'Most participatory courses (enrolments)'

Participation ratio = active users / users enrolled

Active users are users with activity in the time period specified.

==Available reports==
Here's a list of View and Post action reports, with a brief summary of the type of reports.

===Core module reports===
*'''Assignment''' Views: view ; Posts: upload
*'''Chat''' Views: view, view all, report; Posts: talk
*'''Choice''' Views: view, view all, report; Posts: choose, choose again
*'''Database''' Views: view; Posts: add, update, record delete
*'''Forum''' Views: view discussion, search, forum, forums, subscribers; Posts: add discussion, add post, delete discussion, delete post, move discussion, prune post, update post
*'''Glossary''' Views: view, view all, view entry; Posts: add category, add comment, add entry, approve entry, delete category, delete comment, delete entry, edit category, update comment, update entry
*'''Lesson''' Views: view, view all; Posts: end, start, update grade attempt
*'''Quiz''' Views: view, view all, report; Posts: attempt, edit questions, review, submit
*'''Resource''' Views: view, view all; Posts:
*'''SCORM/AICC''' Views: preview, view, view all, report; Posts:
*'''Survey''' Views: download, view all, view form, view graph, view report; Posts: submit

===Some contributed module reports===
*'''Hot Potatoes Quiz''' Views: view, view all, report; Posts: attempt, review, submit
*'''Journal''' Views: view, view all, view responses; Posts: add entry, update entry, update feedback
*'''Lightbox Gallery''' Views: view, view all, search; Posts: comment, addimage, editimage

When a user accesses a resource or activity, these actions are usually captured in the Moodle site database, ready for counting when a Course Overview Report is run. However, some additional plugins do not have the code necessary to register a View or Post action, and so such activities are not captured.

[[de:Kursübersicht-Bericht]]
[[es:Reporte de vista general del curso]]
[[eu:Ikastaroaren_ikuspegi_orokorra]]
[[fr:Rapports de vue d'ensemble de cours]]

Content bank

2021-12-01T15:13:39Z

Tsala: /* Course restoring */ small rewording

{{Managing content}}
==What is the content bank?==
The content bank is an area in Moodle where content (currently [[H5P]] content) may be stored, edited and created.

The content bank repository gives access to these files from the file picker.
[[File:H5Pcontentbank.png|center|Content bank]]
==Where is the content bank?==
As a teacher, when you are in a course you'll find a link to the content bank in the Navigation drawer (Boost-based themes) or the Navigation block, under Site pages (Classic-based themes).

Files may be viewed in list view by clicking the icon top right of the content bank.

The content bank repository is available from the file picker to locate and add H5P files into courses.
==How does the content bank work?==
New H5P content may be created via the Add button. It can be edited by clicking into the content then clicking Edit:
[[File:EditH5P.png|center|Editing existing H5P]]
H5P activities can also be uploaded into the content bank then edited if required.

H5P activity types available in the content back are automatically downloaded via CRON or can manually be added by uploading h5p activity files (*.h5p).
==Renaming, downloading, replacing and deleting H5P==
Click into an H5P activity and from the cog icon top right, access your chosen option.
[[File:H5Poptions.png|center|H5P options]]
{{MediaPlayer | url = https://youtu.be/1WmygG0hgVY }}
==Searching the content bank==
*The search field above the content bank allows you to search for H5P content in the course you are in.
*When adding an H5P activity from ''Add an activity or resource > H5P'', you can search the content bank for H5P in other courses and categories, depending on permissions.
[[File:ContentBankSearch.png|center|Searching the content bank]]

== Restoring a course with a content bank ==

When restoring a course, the content bank contents are also restored to the new course. Please keep in mind that the user who restores the course will be the owner of the content bank contents in the new course, and this will affect who can edit or delete the contents based on the [[Capabilities/moodle/contentbank:deleteanycontent|Delete any content from the content bank]] and [[Capabilities/moodle/contentbank:manageanycontent|Manage any content from the content bank]] capabilities.

==Admin settings==
*From ''Site administration > Plugins > Content bank > Manage content types'', you can enable and disable H5P content.
*From ''Site administration > Repositories > Content bank'' you can rename the content bank repository if desired.
==Capabilities==
===Repository: Content bank===
* [[Capabilities/repository/contentbank:accesscoursecategorycontent|Access course category content bank files]] - allowed for the default roles of manager and course creator
* [[Capabilities/repository/contentbank:accessgeneralcontent|Access system content bank files]] - allowed for the default role of authenticated user
* [[Capabilities/repository/contentbank:accesscoursecontent|Access course content bank files]] - allowed for the default roles of manager, course creator and teacher
* [[Capabilities/repository/contentbank:view|View content bank repository]] - allowed for the default roles of manager, course creator and teacher
===Course===
* [[Capabilities/moodle/contentbank:access|Access the content bank]] - allowed for the default roles of manager, course creator and teacher
* [[Capabilities/moodle/contentbank:deleteanycontent|Delete any content from the content bank]] - allowed for the default roles of manager and course creator
* [[Capabilities/moodle/contentbank:deleteowncontent|Delete content from own content bank]] - allowed for the default role of authenticated user
* [[Capabilities/moodle/contentbank:manageanycontent|Manage any content from the content bank]] - allowed for the default roles of manager and course creator
* [[Capabilities/moodle/contentbank:manageowncontent|Manage content from own content bank]] - allowed for the default roles of manager, course creator and teacher
* [[Capabilities/moodle/contentbank:upload|Upload new content to the content bank]] - allowed for the default roles of manager, course creator and teacher
* [[Capabilities/moodle/contentbank:useeditor|Create or edit content using a content type editor]] - allowed for the default roles of manager and course creator
* [[Capabilities/moodle/contentbank:downloadcontent|Download content from the content bank]] - allowed for the default roles of manager, course creator and teacher.
===H5P===
* [[Capabilities/contenttype/h5p:access|Access H5P content in the content bank]] - allowed for the default roles of manager, course creator and teacher
* [[Capabilities/contenttype/h5p:upload|Upload new H5P content]] - allowed for the default roles of manager, course creator and teacher
* [[Capabilities/contenttype/h5p:useeditor|Create or edit content using the H5P editor]] - allowed for the default roles of manager, course creator and teacher
[[Category:H5P]]
[[Category:Content bank]]
[[es:Banco de contenido]]
[[de:Inhaltsspeicher]]

admin/reportbuilder/edit

2021-11-25T10:47:38Z

Tsala: redirect

#redirect [[Report builder]]