MoodleDocs - User contributions [en]

MediaWiki:Sitenotice

2026-04-21T19:42:10Z

Tsala:

<p class="note">''Note: You are currently viewing documentation for Moodle 4.4. Up-to-date documentation for the latest stable version of Moodle may be available here: '''[[:en:{{NAMESPACE}}:{{PAGENAME}}|{{PAGENAME}}]].'''''</p>

MediaWiki:Sitenotice

2026-04-21T19:41:57Z

Tsala:

<p class="note">''Note: You are currently viewing documentation for Moodle 3.7. Up-to-date documentation for the latest stable version of Moodle may be available here: '''[[:en:{{NAMESPACE}}:{{PAGENAME}}|{{PAGENAME}}]].'''''</p>

MediaWiki:Sitenotice

2026-04-21T19:41:05Z

Tsala:

Note: You are currently viewing documentation for Moodle 4.4. Up-to-date documentation for the latest stable version of Moodle may be available here: Sitenotice.

MediaWiki:Sitenotice

2026-04-21T19:40:04Z

Tsala:

-
Note: You are currently viewing documentation for Moodle 4.4. Up-to-date documentation for the latest stable version of Moodle may be available here: Sitenotice.

Ordering question type

2025-11-26T16:57:31Z

Tsala: image updated

{{Questions}}
{{New features}}

==Overview==
Originally developed by community moodler [https://moodle.org/user/profile.php?id=8277 Gordon Bateson] the ordering question type was added to standard Moodle from Moodle 4.4 onwards thanks to sponsorship by the Moodle Users Association.

It displays several items (words, phrases, images or other media) in a random order which must then be dragged into the correct sequential order.

{{MediaPlayer | url =https://youtu.be/r-P2IZp-ysg?feature=shared| desc = Ordering question type in Moodle 4.4}}

[[File:404orderingquestion.png|frame|none|link=|alt=|An example of an ordering question with the instruction 'Put this dialogue into the correct order'.]]

==How to create an ordering question==
* Add the question name and the question text:

*Choose whether you want the items to display vertically or horizontally.
[[File:Ordering question 02.png|600px]]

* Choose the best grading type for your learners.
[[File:Ordering question 03.png|600px]]

*Add the items in the correct order:
[[File:Ordering question 04.png|600px]]

*Add hints for multiple tries if needed and tags if required.

==What the student sees==
* The student will see a jumbled list of items. The student needs to drag and drop the items until the list is in the correct order:
[[File:Ordering question 07.png|600px]]

*If the student misplaced items, they will be marked red
[[File:Ordering question 08.png|600px]]

*It may be important to have a proper feedback sentence explaining what went wrong (if anything)
[[File:Ordering question 09.png|600px]]

==External links==
* [https://moodleformulas.org/course/view.php?id=30/ MoodleFormulas] where you can try some examples of the Ordering question type.

[[es:Tipo de pregunta de Ordenamiento]]
[[de:Fragetyp Anordnung]]

File:404orderingquestion.png

2025-11-26T16:56:49Z

Tsala:

MediaWiki:MoodleDocsVersionLinks

2025-09-12T10:59:46Z

Tsala: 5.1

4.4 docs: /404/en/{{FULLPAGENAMEE}}
5.1 docs: /501/en/{{FULLPAGENAMEE}}
5.0 docs: /500/en/{{FULLPAGENAMEE}}
4.5 docs: /405/en/{{FULLPAGENAMEE}}
4.1 docs: /401/en/{{FULLPAGENAMEE}}

Upgrading

2025-05-25T14:59:06Z

Tsala: /* Possible issues that may affect you in Moodle {{Version}} */ Grade category and grade item advanced options removed (MDL-78967)

{{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}} Moodle {{Version}} release notes] for server and client software requirements.

Notes:
* You can only upgrade to Moodle {{Version}} from Moodle 4.1.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/401/en/Upgrading upgrade to 4.1.2] 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 [[Installing_plugins#Plugins_overview|plugins (including themes) 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.

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

===New activity icons===

Updated activity icons 24 x 24px are outlined with a transparent background and use an accessible colour palette.

===Course section pages===

A new section page displays the contents of an individual course section. The general section no longer appears above the selected section. Section names in the course page link to section pages. Any manually added section links of the form course/view.php?id=xx#section-z will continue working, linking to course page anchors.

===Manual enrolment course welcome message===

As for self enrolment, a course welcome message can be sent for [[Manual enrolment]]. An admin or manager can customise the message in the manual enrolment settings in the course.

===New notifications===

* [[Self enrolment]]: Users are notified before they are unenrolled due to inactivity
* Tasks: Administrators are notified when tasks fail

===TinyMCE is the default text editor===

[[TinyMCE]] becomes the default text editor of sites upgrading to 4.4. Since 4.2 it has been the default text editor of new installs.

===Topics course format renamed===

The Topics course format is renamed 'Custom sections' and new sections are no longer numbered.

===BigBlueButton credentials required===

To continue using the [[BigBlueButton]] free tier hosting, the admin needs to register with BigBlueButton to obtain credentials for their site.

===Chat and Survey activities===

[[Chat]] and [[Survey]] activities are disabled in new Moodle 4.4 installs and are due for removal in Moodle 5.0. You can check if they are used on your upgraded site in ''Site administration > Plugins > Manage activities'' and disable them if they are unused.

===Multi-factor authentication SMS factor===

To increase site security, [[Multi-factor authentication]] includes the option to authenticate via an SMS code.

===Option to show password as plain text===

You can allow users to show their entered password as plain text via a new setting 'Password visibility toggle' in ''Site administration > Plugins > [[Manage authentication]]''. The option is disabled on upgraded sites and set to 'Small screens only' on new installs.

===Browse list of users page improvements===

Site administration > Users > Browse list of users no longer shows the fields 'City' and 'Country' unless they are included as identity fields.

===Asynchronous course backups===

Asynchronous backups provide a better user experience allowing users to do other operations while a backup or restore is in progress. Asynchronous course backups are enabled for new Moodle 4.4 installs. You can enable asynchronous course backups on your upgraded site in ''Site administration > Courses > Asynchronous backup/restore''.

===Theme settings===

In ''Site administration > Appearance'', Theme settings are renamed 'Advanced theme settings'. Settings for Boost or Classic are accessed via the 'Edit theme settings' link in ''Site administration > Appearance > Themes''.

===HTML tidy filter disabled===
The HTML tidy filter no longer works and is disabled in 4.4.3 and removed in 4.5.

===Grade category and grade items advanced options removed===

In ''Site administration > Grades > Grade category settings'' the Advanced checkboxes are removed. In ''Site administration > Grades > Grade items'' the Advanced grade item options are removed.

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.4%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.4%20AND%20labels%20%3D%20ui_change ui_change-labelled issues] also the [https://moodledev.io/docs/4.4/devupdate Moodle 4.4 developer update].

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

* View all custom reports (moodle/reportbuilder:viewall)
* Access TinyMCE Premium features (tiny/premium:accesspremium)
* Use upload course tool (tool/uploadcourse:use)

== Moodle 4.1, 4.2 and 4.3 upgrading notes ==
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/401/en/Upgrading Upgrading to Moodle 4.1]
* [https://docs.moodle.org/402/en/Upgrading Upgrading to Moodle 4.2]
* [https://docs.moodle.org/403/en/Upgrading Upgrading to Moodle 4.3]

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

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

Grade category settings

2025-05-25T14:49:39Z

Tsala: advanced options removed in MDL-78967 - thanks to Przemek for pointing it out

{{Grades}}
'''Grade category settings''' in ''Settings > Site administration > Grades > Grade category settings'' enable administrators to choose which options appear for teachers when [[Grade categories|adding/editing a grade category]] in their course gradebook, and their default values. Settings are applied site-wide.

There is a "Force" check box next to most of the features on this page. The "Force" check box eliminates any other options that a teacher will see. For example, the teacher will only see and be able to use the "mean of all grades" as an aggregation if the "Force" checkbox next to "Aggregation" is checked.

==Hide forced settings==
The default is to show the forced settings (see below). If these are not to be used check this box to hide them. Unchecking the "Force" setting will simply restore each category's setting to its previous state, prior to the application of the forced global setting. Administrators can thus experiment with these settings without fear of losing any specific category settings.

==Aggregation==
Select the type of aggregation method from a pulldown menu. (See [[Category aggregation]] for a detailed explanation.) However, there are two check boxes which will effect this default, in addition to the Hide forced settings.

The "Force" checkbox only allows the selected aggregation method to apply. This results in switches and drop-down elements being disabled in all course gradebooks. For example, if the Aggregation Type setting is forced as "Mean", teachers will no longer have the option to change the aggregation type of each grade category separately, the option will not be there in the category edit form.

==Available aggregation types==

The default grade aggregation is Natural, meaning the sum of all grade values scaled by weight.

[[Image:availableaggregationtypes1.png|thumb|center|500px|Available aggregation types setting]]

Administrators may specify here which aggregation types are available for teachers to use.

Note that reducing the number of aggregation types simply results in disabled aggregation types not appearing in the aggregation type dropdown menu. All existing grade category calculations remain the same, regardless of whether the aggregation type is later disabled by an administrator.

==Aggregate only non-empty grades==
[[File:emptygrades.png|thumb|Grade category settings: Exclude empty grades option.]]
The "Exclude empty grades" option determines how Moodle handles activities that have not been graded yet.

If this option is enabled, Moodle will ignore any grade item that has no grade when calculating the category or course total. If it is disabled, Moodle will treat empty grades as zero when calculating averages or totals, as illustrated in the following example:
{| class="wikitable"
!Student
!Activity 1
!Activity 2
!Activity 3
!Category Total

(Exclude empty grades selected)
!Category Total

(Exclude empty grades unselected)
|-
|Carol
|80
|90
|Not graded
|(80 + 90) / 2 = 85
|(80 + 90 + 0) / 3 = 56.67
|}
'''With "Exclude empty grades" enabled'''

Students’ averages are based only on the work they’ve completed and been graded for. This is often used to give students the benefit of the doubt until all grades are in, encouraging continuous participation without penalising them for grades that haven't been entered yet.

'''With "Exclude empty grades" disabled'''

Any ungraded work is assumed to be a zero, which might be used to show students the impact of missing work on their overall grade. This can be a motivator for students to submit all assignments.

Choosing whether to exclude empty grades depends on your grading strategy and how you want to communicate progress to your students.

==Include outcomes in aggregation==
The default is no.

==Keep the highest==
Keeps only the X number of highest grades in the report

==Drop the lowest==
Drops the lowest X number of grades from the report.

When using natural weighting, drop the lowest is only allowed when:
* all children of the category have equal weights
* all children of the category have equal max grade
* there are no sub categories in the category
* there are no extra credit items in the category

==See also==
*[[Grade categories]] - for teachers
*[http://www.youtube.com/watch?v=p6zWwJGb9TA Video demonstrating how to use gradebook site settings and defaults]
*[http://www.youtube.com/watch?v=sUslTuZPu6A Video showing the effects of the grade category settings]

[[de:Einstellungen für Bewertungskategorien]]
[[fr:Réglages des catégories d'évaluation]]
[[ja:評定カテゴリ設定]]
[[es:Configuraciones de categoría de calificación]]

Grade items

2025-05-25T14:44:18Z

Tsala: /* Advanced grade item options */ options removed in MDL-78967

{{Managing grades}}
A grade item is a unit (typically an activity) where course participants are assessed through a grade or mark.
As such, a grade item is a container for grades and a set of settings applied to these grades. The settings affect the calculation and display of the grades in the gradebook reports and [[Grade export|exports]].

'''Grade items''' may refer to course activities (e.g. a quiz, an assignment etc.), [[Outcomes]] or manual grades.
== Grade items and gradebook ==
The three building blocks of the Gradebook are:
#The grade item
#The [[Grade categories|grade category]]
#The [[Grades|grade]]
Grade items are represented by columns in the [[grader report]].

Within a category, a [[Grades|grade]] summary is also a grade item itself. Summary grade items for a category can show up in reports, and can be used in the calculation of the grade for the parent category.
== Activity-based grade items ==
[[Image:editingradeitem.png|right|thumb|Editing a grade item]]
A number of activities such as [[Assignment]], [[Workshop]], [[Lesson]], [[Quiz]] and others communicate their grades to the gradebook. The generated grade item can later be changed directly from Course administration>Grades, but this will then freeze it in the activity itself; so, a teacher who has edited an assignment grade in the gradebook will not be able to change it from the assignment, unless they unlock it in the gradebook.

Here is a list of the settings that can be edited for an activity-based grade item:
*'''Item name''': The name given to this item, for example the assignment name
*'''Item info''': General information about the grade item. Optional.
*'''Grade to pass''': Specify the minimum grade a student must achieve to be considered to have passed this item. This must be in real grades, not a percentage. Once this is done, grades will be highlighted in red for fail and green for pass in the gradebook. (The Grade to pass may also be specified from activity set up pages.) NB - if your grade type (see below) is a scale then the grade to pass is your lowest grade that counts as a pass. For example, with the grade scale: '''Fail, Accept, Merit, Distinction''' the lowest grade that counts as a "'''pass'''" is "'''Accept'''" therefore the Grade to Pass is set to 2, as it is the second item in the list that goes from negative to positive.
*'''Grade type''': There are 4 grade types:
#None - No grading possible
#Value - A numerical value with a maximum and minimum
#Scale - An item in a list - see [[Scales]]
#Text - Feedback only
Only value and scale grade types may be aggregated. The grade type for an activity-based grade item is set on the activity settings page.
*'''Overall decimal points''': This specifies the number of decimal points to display for each grade. It has no effect on grade calculations, which are made with an accuracy of 5 decimal places.
*'''Multiplicator''': Factor by which all grade for this grade item will be multiplied, with a maximum value of the maximum grade. For example, if the multiplicator is 2 and the maximum grade is 100, then all grades less than 50 are doubled, and all grades 50 and above are changed to 100.
*'''Offset''': Number that will be added to every grade for this grade item, '''after''' the Multiplicator is applied. (Can be a negative number.)
*'''Hidden''': Whether this grade item should be hidden from students.
*'''Hidden until''': An optional date after which the grade item will no longer be hidden (i.e. a grades release date). Note that 'Hidden' and 'Hidden until' can currently both be ticked. This problem is reported as MDL-59646.
*'''Locked''': Whether or not to lock this grade item. A locked grade item doesn't accept changes to its settings or grades from its related module.
*'''Locked after''': A date after which the locking will be effective, usually after the grades release date.

== Outcome items ==
An outcome item is in most respects the same thing as a grade item. The main difference between the two is that the purpose of an outcome item is to rate students on a particular [[Outcomes|outcome/competency/goal]], whereas grade items are used for grading students, usually with the intention of aggregating the results as a measure of the student's performance in the course activities.

An outcome item is always linked with an [[Outcome|outcome]], which itself is linked to a [[Scales|scale]]. The scale may represent a quantitative measure, its values being arranged from lowest to highest; or it may represent a qualitative measure, in which the order of the scale values is irrelevant. The first type can be aggregated, but the second type shouldn't (we wouldn't want to fail a student because her favourite colour is "blue"!).

An outcome item may optionally be linked to an activity. This activity may or may not appear in the gradebook (for example, a wiki is usually not graded, so does not appear). Linking an outcome item with an activity creates a grade item with the icon of the linked activity, but there is no other way to see which activity it is linked with. For this reason, it is a good idea to include the activity name in the name of the outcome item (e.g. Wiki 1: Participation).

These can either be generated by the creation of a new activity module (by selecting [[Outcomes]] in the module creation form), or manually created like manual grade items. A grade outcome item uses a course outcome as its grading type, so such an outcome must be made available at the course level before a grade outcome item can be manually created.

The settings of the grade outcome item edit form are identical to those of manual grade items, with the addition of two settings:
*'''Outcome''': The course outcome represented by this item
*'''Linked activity''': The optional activity module to which this item will be linked
== Manual grade items ==
[[File:editingmanualgrades.png|right|thumb|Editing a manual grade item]]
These grade items are created manually from ''Course administration > Gradebook setup''. The "Add grade item" button is clicked, and the form appears. Several options are available here;
*'''Item name''': The display name of your grade item
*'''ID Number''': An arbitrary string of characters used to refer to this grade item in Formulas. If set, it must be unique.
*'''Grade type''': The type of grade: None (no grading possible), Value (a numerical value), Scale (an item in a list) or Text (arbitrary text).
*'''Scale''': Which scale to use for grading: available only when the Scale grade type is selected.
*'''Maximum grade''': The maximum grade that can be given (for scales: the number of items in the scale - 1)
*'''Minimum grade''': The minimum grade that can be given (for scales: 0)
Manual grade items are recognised in the Grader report by their icon like a pencil:

[[File:manualgradeitem2.png]]

Note that this icon is not clickable; to edit the manual grade item you have to click the edit icon just below it.
==Grade item settings==
===Site defaults===
Grade item settings, accessed from ''Administration > Grades > Grade item settings,'' are the various settings that the administrator is able to edit for the grader report used by teachers. These settings will change what items are displayed for each grade. As administrator, you would turn on or off various settings and the teacher would input the actual data.
[[Image:newgradeitemsettings.png|thumb|center|Grade item settings screen]]
===Grade display type===
This is the type of grade that is to be shown for each individual grade. Different organisations use different grade types so you can select the one that best meets your needs.

*[[Grade letters|Letter]]- Grade in the form of a letter representing a range of percentages.
*Percentage - Grade from 0 - 100% indicating the total points received divided by maximum possible amount times 100.
* Real - Actual grade or scale values, from minimum to maximum range. Default from 0-100 but may be arbitrary.

You can also choose to display two grade types, with the second in brackets.

*Letter (percentage) e.g. A (80)
*Letter (real) e.g. A (8)
*Percentage (letter) e.g. 55 (C)
*Percentage (real) e.g. 55 (5.5)

===Overall decimal points===
This setting is for display purposes only. Grade calculations are made with an accuracy of 5 decimal places and grade letters, if used, are assigned accordingly.

If rounding of grades in [[grade calculations]] is required, the round(number, count) function may be used.

[[ca:grade/edit/tree/item]]
[[de:Bewertungsaspekte]]
[[es:Ítems de calificación]]
[[fr:Éléments de note]]
[[ja:評定項目]]

MediaWiki:MoodleDocsVersionLinks

2025-04-04T10:38:17Z

Tsala:

4.4 docs: /404/en/{{FULLPAGENAMEE}}
5.0 docs: /500/en/{{FULLPAGENAMEE}}
4.5 docs: /405/en/{{FULLPAGENAMEE}}
4.1 docs: /401/en/{{FULLPAGENAMEE}}

Capabilities/moodle/cohort:configurecustomfields

2025-03-03T14:09:44Z

Tsala: Created page with "{{Capabilities}} *This allows a user to configure cohort custom fields *This capability is not set for any of the default roles ==See also== * Cohorts Cohort Category:Site administration Category:Groups"

{{Capabilities}}
*This allows a user to configure cohort custom fields
*This capability is not set for any of the default roles

==See also==

* [[Cohorts]]

[[Category:Capabilities|Cohort]]
[[Category:Site administration]]
[[Category:Groups]]

Course meta link

2025-01-02T17:38:39Z

Tsala: Updating text to use source and target wordings

{{Enrolment}}
==About Course meta link enrolment==
Course meta link enrolment synchronises enrolments and roles from a source course to a target course.

{{MediaPlayer | url = https://youtu.be/Z3N9Lbm9qiA | desc = Overview of Course meta link}}

==Site settings for Course meta link==

To use Course meta link enrolment, you need to enable it in ''Site administration > Plugins > Enrolments > Manage enrol plugins''.

Then click the settings link to review the course meta link settings.

By default all role assignments from the source course are synchronised to the target course. However, you can select particular roles to exclude in the setting "Roles that are not synchronised".

==Course settings for Course meta link==

*In a course, go to ''Course navigation > Participants > Enrolment methods''.
*Click the dropdown menu under the enrolment methods and select 'Course meta link'.

[[File:enrolmentmethods29c.png|thumb|center|300px]]
*In the screen that comes up next, either type in a search term to find your course, or select from the dropdown box the course or courses you wish to bring enrolments from (the source), then click 'Add method':

[[File:NFCoursemetalinkeg.png|thumb|center|Several courses may be selected at once|400px]]

*For each linked course, users may be added to an existing group in the new course, or a new group may be created for them. (Groups from the linked courses are not synced to groups in the new courses. All users will be added to one group when the link is made.)

:Note: A teacher can only choose courses that they are teachers in elsewhere.

*The users from the source course will now be enrolled in the current course - see the numbers in the screenshot below:

[[File:NFCoursemetalinkusers.png]]

*When new users are enrolled to the source course, they will be automatically brought into the current target course.

==Course meta link capabilities==

*[[Capabilities/enrol/meta:config|Configure meta enrol instances]]
*[[Capabilities/enrol/meta:selectaslinked|Select course as meta linked]]

==Enabling teachers to add meta links==

An administrator can enable teachers to add course meta links as follows:

* Go to ''Site Administration > Users > Permissions > Define Roles''.
* Select the Teacher role and click on the Edit button.
* Scroll down to Course meta link as shown in the images below:
{| class="wikitable"
|-
|[[Image:metacoursepermissionset00.png|Permission block for allowing Teachers to link meta courses.]]
|-
| style="text-align: center;"| The default setting is "Not Set"
|-
|[[Image:metacoursepermissionset01.png|Permission changes for editing.]]
|-
| style="text-align: center;"| When the Edit button is clicked, the panel changes to "Allow" and a checkbox.
|-
|[[Image:metacoursepermissionset02.png|Setting permission to allow Teachers to link Meta courses.]]
|-
| style="text-align: center;"| Change to "Allow" by a click on the checkbox.
|}
* Scroll to the bottom of the page to save your changes.

==Examples of meta-linked courses==

{| class="wikitable"
|-
![[Image:simplemetacourse0.png|thumb|left|200px|Created - a source course and a target course.]]
![[Image:simplemetacourse1.png|thumb|left|200px|Associating one child course and one meta course.]]
|}

Examples: one "child" course (a course linked to a meta course) can be associated with many meta courses. Or one meta course can have many child courses associated with it. Both the child courses (non-meta courses) and the meta courses are independent and can be recycled many times, that is, each can be associated with many of the other.

{| class="wikitable"
|-
![[Image:simplemetacourse2.png|thumb|left|200px|2 child courses and a meta course.]]
![[Image:simplemetacourse3.png|thumb|left|200px|1 child course and 2 meta courses.]]
![[Image:simplemetacourse4a.png|thumb|left|200px|3 child courses and 2 meta courses.]]
|}

There is one limitation: you cannot 'nest' metacourses. In other words, if you have child course A linked to meta course B, and you then link B as a child course to meta course C, a student enrolled in A will be added to B, but not to C. In this situation, you would need to add a meta link directly between A and C instead of trying to nest them. Another option might be to use [[Cohorts]], or [https://tracker.moodle.org/browse/MDL-27267?focusedCommentId=496408&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-496408 combining this enrolment method with the bulk meta course link plugin]).

==See also==

*[[Metacourse examples of use]]
* [https://moodle.org/plugins/view/enrol_metabulk Bulk meta course link plugin] - this plugins allows to meta link several courses in each role instance

[[de:Meta-Einschreibung]]
[[es:Enlace a metacurso]]
[[fr:Lien méta-cours]]
[[ja:コースメタリンク]]

Course backup

2024-12-11T13:56:48Z

Tsala: /* General backup defaults */ Include custom fields (MDL-83226)

{{Backup}}
A course can be saved with some or all of its parts by using the course backup. Typically, the site administrator will set a schedule of [[Automated course backup|automated course backups]] for the whole site. A teacher can create a backup or download an existing backup for safe keeping, or for use on another Moodle site.

{{MediaPlayer | url = https://youtu.be/DnKA95x3DWI| desc = Course backup}}

==Backing up a course==

To backup a course

# Go into the course.
# From Course navigation > More > Course reuse, select 'Backup'.
# Initial settings - Select activities, blocks, filters and other items as required then click the Next button. Users with appropriate permissions, such as administrators and managers, can choose whether to [[Backup of user data|include users]], anonymize user information, or include user role assignments, groups, groupings, user files, comments, user completion details, course logs and grade history in the backup.
# Schema settings - Select/deselect specific items to include in backup, then click the Next button.
# If desired, select specific types of activity to be backed up by clicking the link 'Show type options'
# Confirmation and review - Check that everything is as required, using the Previous button if necessary, otherwise click the 'Perform backup' button
# Complete - Click the Continue button

{|
[[File:backupsettings42.png|thumb|Backup settings]]
|
|[[File:26backuprestore1.png|thumb|Back up screen with option to select all or none]]
|
|[[File:26backuprestore2.png|thumb|Back up screen with option to select activity types]]
|}

A backup file (with distinctive .mbz extension to avoid confusion with .zip files) is then saved in the course backup area. Backup file names are of the form ''backup-moodle2-course-coursename-date-hour.mbz'', ending in ''-nu.mbz'' when backed up with no users and ''-an.mbz'' with anonymized names.

Tip: If you are satisfied with the default settings and don't wish to go through all the backup screens, you can simply click 'Jump to final step' to perform the backup.

==Anonymizing user information==

Anonymize user information is a backup feature which "protects user identities" by making each user anonymous. If this box is checked in the backup initial settings, Moodle will substitute aliases for real names, substituting @doesntexist.com email addresses and so forth. For example "Max Manager" might become "anonfirstname4 anonlastname4".

==Asynchronous course backups==

Note: With large courses it is helpful to be able to continue working while a course backup is being made. To achieve this, you need to enable asynchronous backups in ''Site Administration / Courses / Backups / Asynchronous backup/restore''.

'''New in 4.4:''' Asynchronous course backups are enabled by default in new installations of 4.4 onwards.

==Backup via CLI for administrators==

Site administrators can backup selected courses using a CLI script.

Options
--courseid=INTEGER (Course ID for backup.)
--courseshortname=STRING (Course shortname for backup.)
--destination=STRING (Path where to store backup file. If not set the backup will be stored within the course backup file area.)
-h, --help (Print out this help.)

Example
sudo -u www-data /usr/bin/php admin/cli/backup.php --courseid=2 --destination=/moodle/backup/

On Windows you will use cmd.exe to run the /admin/cli/backup.php script. If you have your Moodledata folder setup on a separate data server you can specify a UNC path to your backup folder on that data server. From the command line CD to the Moodle ''\admin\cli'' folder and run this command:
php backup.php --courseid=25 --destination=\\moodledata\backup

where '--courseid' is the id of the course that you want to backup.

The .mbz backup file for courseid=25 will be stored in the ''backup'' subfolder in the ''Moodledata'' ($CFG->dataroot) folder.

==Creative uses==
The backup and restore processes can offer the teacher and administrators many creative solutions.
*Duplicating courses or specific activities in one course to another course (similar to Import)
*Updating a production Moodle site course, with material from a localhost site course
*Transferring a course to a new Moodle site.
*In earlier versions of Moodle, a way of rolling a course forward without past student activity
*Creating a blank activity, save just that activity and then restore it to the course or another course one or more times.

==General backup defaults==

Default settings for course backups can be set by a site administrator in 'General backup defaults' in the Site administration.

{{New features}}New in Moodle 4.4.5 is the option 'Include custom fields'.

Selected settings may be locked, so that they cannot be changed when creating a course backup.

By selecting a time in the "Keep logs for.." dropdown, it is possible to specify how long backup logs information is kept before being deleted. As this information may be very large, it is recommended the length of time chosen be quite short.

==Course backup stops above 90%, not showing any errors==
This has been reported to be caused by:
* a [[Course_formats#Contributed_Course_Formats|non-standard course_format]]. Try replacing the course format.
* not enough server RAM. Adding more RAM to your server is usually the first [[Performance_recommendations|performance recommendation]].

==Course backup capabilities==

*[[Capabilities/moodle/backup:anonymise|Anonymise user data on backup]]
*[[Capabilities/moodle/backup:backupcourse|Backup courses]]
*[[Capabilities/moodle/backup:backupsection|Backup sections]]
*[[Capabilities/moodle/backup:backuptargetimport|Backup for import]]
*[[Capabilities/moodle/backup:configure|Configure backup options]]
*[[Capabilities/moodle/backup:downloadfile|Download files from backup areas]]
*[[Capabilities/moodle/backup:userinfo|Backup user data]]

==Error: Trying to restore user 'admin' from backup file will cause conflict ==
* Before proceeding, it would be advisable to have a second admin account ''just in case something goes wrong''.
* Check that the admin accounts on each server have '''different''' unique usernames and email addresses and then try again to backup up the course with user data and restore it.
** If you can not make a new backup and you must use an existing 'conflicting' backup file, you will have to change the new site's main admin account with extreme care to remember the new main admin's password and email.
* Note that the admin account from the imported file may loose the password and become unusable;
* You are advised to update/reset the 'imported' main 'admin's account's password before logging out, as this will most likely be the main 'admin' account for the site, and you would get into serious problems if this account stops working.
* If something goes terribly wrong, you can use the second admin account to fix the main admin account.

==See also==

*[[Course restore]]
*[[Backup of user data]]
*[[Activity backup]]
*[[Import course data]]
* Administrators can use [http://moosh-online.com/commands/#course-restore MOOSH] to bulk backup and restore courses from CLI

[[Category:Course]]

[[de:Kurssicherung]]
[[es:Respaldo del curso]]
[[eu:Ikastaroaren_Segurtasun-kopia]]
[[fr:Sauvegarde de cours]]
[[ja:コースバックアップ]]

Upgrading

2024-12-05T15:53:33Z

Tsala: HTML tidy filter disabled (MDL-82790)

{{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}} Moodle {{Version}} release notes] for server and client software requirements.

Notes:
* You can only upgrade to Moodle {{Version}} from Moodle 4.1.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/401/en/Upgrading upgrade to 4.1.2] 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 [[Installing_plugins#Plugins_overview|plugins (including themes) 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.

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

===New activity icons===

Updated activity icons 24 x 24px are outlined with a transparent background and use an accessible colour palette.

===Course section pages===

A new section page displays the contents of an individual course section. The general section no longer appears above the selected section. Section names in the course page link to section pages. Any manually added section links of the form course/view.php?id=xx#section-z will continue working, linking to course page anchors.

===Manual enrolment course welcome message===

As for self enrolment, a course welcome message can be sent for [[Manual enrolment]]. An admin or manager can customise the message in the manual enrolment settings in the course.

===New notifications===

* [[Self enrolment]]: Users are notified before they are unenrolled due to inactivity
* Tasks: Administrators are notified when tasks fail

===TinyMCE is the default text editor===

[[TinyMCE]] becomes the default text editor of sites upgrading to 4.4. Since 4.2 it has been the default text editor of new installs.

===Topics course format renamed===

The Topics course format is renamed 'Custom sections' and new sections are no longer numbered.

===BigBlueButton credentials required===

To continue using the [[BigBlueButton]] free tier hosting, the admin needs to register with BigBlueButton to obtain credentials for their site.

===Chat and Survey activities===

[[Chat]] and [[Survey]] activities are disabled in new Moodle 4.4 installs and are due for removal in Moodle 5.0. You can check if they are used on your upgraded site in ''Site administration > Plugins > Manage activities'' and disable them if they are unused.

===Multi-factor authentication SMS factor===

To increase site security, [[Multi-factor authentication]] includes the option to authenticate via an SMS code.

===Option to show password as plain text===

You can allow users to show their entered password as plain text via a new setting 'Password visibility toggle' in ''Site administration > Plugins > [[Manage authentication]]''. The option is disabled on upgraded sites and set to 'Small screens only' on new installs.

===Browse list of users page improvements===

Site administration > Users > Browse list of users no longer shows the fields 'City' and 'Country' unless they are included as identity fields.

===Asynchronous course backups===

Asynchronous backups provide a better user experience allowing users to do other operations while a backup or restore is in progress. Asynchronous course backups are enabled for new Moodle 4.4 installs. You can enable asynchronous course backups on your upgraded site in ''Site administration > Courses > Asynchronous backup/restore''.

===Theme settings===

In ''Site administration > Appearance'', Theme settings are renamed 'Advanced theme settings'. Settings for Boost or Classic are accessed via the 'Edit theme settings' link in ''Site administration > Appearance > Themes''.

===HTML tidy filter disabled===
The HTML tidy filter no longer works and is disabled in 4.4.3 and removed in 4.5.

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.4%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.4%20AND%20labels%20%3D%20ui_change ui_change-labelled issues] also the [https://moodledev.io/docs/4.4/devupdate Moodle 4.4 developer update].

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

* View all custom reports (moodle/reportbuilder:viewall)
* Access TinyMCE Premium features (tiny/premium:accesspremium)
* Use upload course tool (tool/uploadcourse:use)

== Moodle 4.1, 4.2 and 4.3 upgrading notes ==
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/401/en/Upgrading Upgrading to Moodle 4.1]
* [https://docs.moodle.org/402/en/Upgrading Upgrading to Moodle 4.2]
* [https://docs.moodle.org/403/en/Upgrading Upgrading to Moodle 4.3]

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

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

error/grades/gradesneedregrading

2024-12-05T12:23:35Z

Tsala: Created page with "The error "Grades need regrading" is displayed in a number of situations. See the [https://tracker.moodle.org/issues/?jql=description%20~%20%22grades%20need%20regrading*%22 list of issues with 'grades need regrading' in the description]. Category: Grades"

The error "Grades need regrading" is displayed in a number of situations. See the [https://tracker.moodle.org/issues/?jql=description%20~%20%22grades%20need%20regrading*%22 list of issues with 'grades need regrading' in the description].

[[Category: Grades]]

MediaWiki:MoodleDocsVersionLinks

2024-10-03T13:26:28Z

Tsala:

4.4 docs: /404/en/{{FULLPAGENAMEE}}
4.5 docs: /405/en/{{FULLPAGENAMEE}}
4.3 docs: /403/en/{{FULLPAGENAMEE}}

Site registration

2024-09-27T05:55:09Z

Tsala: /* I can't register my cloned site */

{{Managing a Moodle site}}
[[File:Boost-Moodle-Registrations.jpg|450px]]
==Why register my site?==
Your site must be registered if you want to use the [[Moodle app]].

Registering your site also gives us a better picture of how Moodle is used worldwide and helps us make decisions about new features and plugins.

==4 reasons to register==
# Stay up to date by email whenever there are new releases of Moodle or security alerts.
# Receive [[Moodle app notifications]] from the messaging server https://messages.moodle.net.
# Be part of the [https://stats.moodle.org/ statistics of the worldwide community].
# List your site on our [https://stats.moodle.org/sites/ list of registered sites in your country]. (But if you want to keep it private, that's fine too!)

==How about security?==
We don't share your information with anyone. We don't go into your site. We use the aggregated anonymous data to publish the statistics of the worldwide community and use the other data to help us in our decision making around new features and plugins.
==How do I register?==
Register your site by logging in as an administrator and going to ''Site administration / Registration''. If you're not the admin, ask them nicely to check!
==I don’t want my details public==
Your registration is private to us unless you choose to make it public.
==Do I have to register? What happens if I don’t?==
Registration is optional, but we wouldn't want you to miss out on any important security issues or upgrades and put your site at risk. The more people who register, the better a picture we get of how Moodle is used and which aspects we can improve. So registering is a win-win for you as well as for us.

However, if you only want to use Moodle for testing things out then you don't need to put your site online and you don't need to register it.
==I can’t register my site==
'''Note:''' Only sites which are online can be registered. If your site is "localhost", i.e. not on the internet, then we cannot connect to it for registration.

Here are some common registration problems. If your problem is different from these, or if you have tried and still cannot register, then get in touch via the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form].
=== I can't update my registration ===
Try un-registering then re-registering your site. To un-register your site, click the ‘Unregister’ link at the bottom of the Registration page.

[[File:unregistr.png|center]]
=== I registered but my site isn't listed ===
Assuming you wanted your site to be listed, be aware that the process can take a week or two, so be patient. If it is not listed after two weeks, get in touch via via the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form].
=== I obtain the message "You are trying to register a site with a URL that was previously used by a registered site" ===
Get in touch via the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form] with information about your site URL.

=== I can't register because I get the message "Your site is already registered" ===
Get in touch via the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form] with information about your site URL and we will delete the original registration.

=== I get the error 403 ===
This is not a Moodle error but an Apache configuration error that your hosts need to solve. If you are hosting the site yourself, then you can get support from the [https://moodle.org/course Moodle community forums].

Also read the section below: "The hub cannot access your site."

=== I get the error 404 ===
*See [https://moodle.org/mod/forum/discuss.php?d=349819 "Register my site function not working"] Moodle forum post.
*See also [https://moodle.org/mod/forum/discuss.php?d=442914#p1780488 "Error code 404 when registering"] Moodle forum post.

=== I get the error 503 ===
One reason might be that you are using CloudFlare for protection. Make sure you allow traffic from the AWS EU region, as you will need to whitelist stats.moodle.org. If you need a more specific IP address, get in touch via via the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form].
===I can't register my cloned site===
Please follow these steps assuming you have access to the database and the console:

1. Remove the site identifier from the database:

Delete from {config} where name = 'siteidentifier';

delete from {registration_hubs};

2. Clear the cache:

php admin/cli/purge_caches.php

3. Attempt a new manual registration (admin/registration/index.php)

=== "An error occurred during registration update (Invalid token - token not found)" ===
Try unregistering your site yourself by clicking the Unregister link at the bottom of the registration page. If that does not work, get in touch via the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form] and we will unregister your site.
=== "An error occurred during registration, please try again later. (Coding error detected...)" ===
Try unregistering your site yourself by clicking the Unregister link at the bottom of the registration page. If that does not work, get in touch via the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form] and we will unregister your site.
=== "The hub cannot access your site" ===
* Your site must be on the internet to register; we cannot connect to "localhost".
* Your site must not be in Maintenance mode as we cannot connect to it in Maintenance mode.
* Allow all incoming requests from the IP address 52.31.34.236 and the User Agent "MoodleBot"
* The stats server is in Ireland. The current valid values for the stats server are 18.202.77.12, 3.249.15.186, 3.252.152.219 and 34.254.223.201 - this IP could vary if the service is restarted) Allow requests from these addresses.
* If your site is behind a secure connection, we cannot connect to it to register. (However, you could open it up for a short time, register and then close it again)
* Make sure there are no firewalls preventing access to the Moodle server. Sites need to accept traffic from Amazon EU networks in order to register.
* If you have tried all of the above and still cannot register, get in touch via the [https://moodle.com/contact/support/?selection=community#form Moodle.com contact form]

[[Category:Site administration]]
[[de:Moodle-Site registrieren]]
[[es:Registro del sitio]]
[[it:Registrazione del sito]]
[[ja: サイト登録]]
[[fr:Enregistrement du site]]

New for teachers

2024-09-19T07:22:38Z

Tsala: /* Quiz improvements */

{{About Moodle}}
If you're a teacher in Moodle, then this page will tell you about major changes affecting you in Moodle 4.4.
__NOTOC__
===Course page improvements===
<div class="card-deck mt-3">
<div class="card">
<div class="card-body">
[[File:refinedcourselook.png|class=img-fluid]]
<h4 class="card-title">
Refined look
</h4>
<p class="card-text">
Activies and sections clearly defined.
</p>
</div>
</div>
<div class="card">
<div class="card-body">
[[File:sectiondisplay.png|class=img-fluid]]
<h4 class="card-title">
Single section page
</h4>
<p class="card-text">
Focus on one section only in its own page.
</p>
</div>
</div>
</div>
<div class="card-deck mt-3">
<div class="card">
<div class="card-body">

[[File:newviewoption.png|class=img-fluid]]

<h4 class="card-title">
New 'View' option
</h4>
<p class="card-text">
With edit mode enabled, teachers click to 'view' a single section.
</p>
</div>
</div>
<div class="card">
<div class="card-body">
[[File:courseformatdisplay.png|class=img-fluid]]

<h4 class="card-title">
Custom sections
</h4>
<p class="card-text">
Topics format is now Custom sections.
</p>
</div>
</div>
</div>
<div class="card-deck mt-3">
<div class="card">
<div class="card-body">
[[File:activityicons.png|class=img-fluid]]

<h4 class="card-title">
Activity icons
</h4>
<p class="card-text">
Updated activity icons use an accessible colour palette.
</p>
</div>
</div>
<div class="card">
<div class="card-body">
[[File:filemimetypes.png|class=img-fluid]]
File (MIME) type icons
<h4 class="card-title">
File (MIME) type icons

</h4>
<p class="card-text">
Available also in 4.1/2/3, file types can be easily identified.
</p>
</div>
</div>
</div>
===New 'Ordering' question type (MUA-sponsored project)===
<div class="card-deck mt-3">
<div class="card">
<div class="card-body">
[[File:orderingquestion2.png|class=img-fluid]]

<h4 class="card-title">
Rearrange words or phrases
</h4>
<p class="card-text">
Now standard Moodle, the Ordering question type allows teachers to create questions with single words or sentences.
</p>
</div>
</div>
<div class="card">
<div class="card-body">
[[File:orderingquestion1.png|class=img-fluid]]

<h4 class="card-title">
Reorder images
</h4>
<p class="card-text">
Images can also be rearranged if using the HTML format option.
</p>
</div>
</div>
</div>
===Quiz improvements===
<div class="card-deck mt-3">
<div class="card">
<div class="card-body">
[[File:quizlastsaved.png|class=img-fluid]]

<h4 class="card-title">
Display 'last saved'
</h4>
<p class="card-text">
Students can see from Quiz navigation when their responses were last saved.
</p>
</div>
</div>
<div class="card">
<div class="card-body">
[[File:quizgradeitems.png|class=img-fluid]]

<h4 class="card-title">
Section grading
</h4>
<p class="card-text">
Teachers can [[Building Quiz|allocate grades to groups of questions]] in a quiz.
</p>
</div>
</div>
</div>

===And more...===
<div class="card-deck mt-3">
<div class="card">
<div class="card-body">
[[File:manualcoursewelcome.png|class=img-fluid]]

<h4 class="card-title">
New notifications
</h4>
<p class="card-text">
Enabled by default in new sites, notifications now include welcome messages for manual enrolments and warnings of unenrolment due to inactivity.
</p>
</div>
</div>
<div class="card">
<div class="card-body">
[[File:matrixgroups.png|class=img-fluid]]

<h4 class="card-title">
Matrix group support
</h4>
<p class="card-text">
Matrix rooms for groups are now created in courses using groups.
</p>
</div>
</div>
</div>
<div class="card-deck mt-3">
<div class="card">
<div class="card-body">
[[File:copytoallgroups.png|class=img-fluid]]

<h4 class="card-title">
Quicker 'Post to all groups'
</h4>
<p class="card-text">
The 'Post to all groups' checkbox displays directly on the page when creating a post.
</p>
</div>
</div>
<div class="card">
<div class="card-body">
[[File:managebadgesfilter.png|class=img-fluid]]

<h4 class="card-title">
Filter course badges
</h4>
<p class="card-text">
Teachers and students can filter course badges.
</p>
</div>
</div>
</div>

===TinyMCE===
<div class="card-deck mt-3">
<div class="card">
<div class="card-body">
[[File:tinymcedefaultdocs.png|class=img-fluid]]

<h4 class="card-title">
Default editor in all sites
</h4>
<p class="card-text">
TinyMCE is now the default editor in new and upgraded sites.
</p>
</div>
</div>
<div class="card">
<div class="card-body">
[[File:tinyimageupload.png|class=img-fluid]]

<h4 class="card-title">
Improved image handling
</h4>
<p class="card-text">
Image handling is more streamlined, giving a better user experience.
</p>
</div>
</div>
</div>
[[Category:New features]]

[[es:Nuevo para profesores]]
[[de:Neu für Trainer/innen]]

MoodleDocs:Overview

2024-09-12T11:35:48Z

Tsala:

==English==
[https://docs.moodle.org/405/en/ 4.5 EN documentation]<br />
[https://docs.moodle.org/404/en/ 4.4 EN documentation]<br />
[https://docs.moodle.org/403/en/ 4.3 EN documentation]<br />

Also:<br />
[https://moodledev.io/ Developer documentation]

==Català (Catalan)==

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

==Deutsch (German)==
[https://docs.moodle.org/405/de/ 4.5 DE documentation]<br />
[https://docs.moodle.org/404/de/ 4.4 DE documentation]<br />
[https://docs.moodle.org/403/de/ 4.3 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]]

MediaWiki:MoodleDocsVersionLinks

2024-09-12T07:21:32Z

Tsala: 4.5 link

4.4 docs: /404/en/{{FULLPAGENAMEE}}
4.5 docs: /405/en/{{FULLPAGENAMEE}}
4.3 docs: /403/en/{{FULLPAGENAMEE}}
4.2 docs: /402/en/{{FULLPAGENAMEE}}
4.1 docs: /401/en/{{FULLPAGENAMEE}}

Custom menu items

2024-09-09T12:51:19Z

Tsala: Changed redirect target from Theme settings to Advanced theme settings

#redirect [[Advanced theme settings]]

Theme config

2024-09-09T12:48:32Z

Tsala: Changed redirect target from Theme settings to Advanced theme settings

#redirect [[Advanced theme settings]]

admin/setting/themesettings

2024-09-09T12:48:10Z

Tsala: Changed redirect target from Theme settings to Advanced theme settings

#redirect [[Advanced theme settings]]

ThemeConfig

2024-09-09T12:46:36Z

Tsala: Changed redirect target from Theme settings to Advanced theme settings

#redirect [[Advanced theme settings]]

Manage editors

2024-09-09T12:43:56Z

Tsala: Changed redirect target from Text editor settings to TinyMCE editor

#redirect [[TinyMCE editor]]

Text editor settings

2024-09-09T12:43:18Z

Tsala: Changed redirect target from Text editor to TinyMCE editor

#Redirect [[TinyMCE editor]]

label

2024-09-09T12:42:53Z

Tsala: Changed redirect target from Label to Text and media area

#REDIRECT [[Text and media area]]

coursefiles2

2024-09-09T12:42:39Z

Tsala: Changed redirect target from Course files to Legacy course files

#redirect [[Legacy course files]]

files/index

2024-09-09T12:42:21Z

Tsala: Changed redirect target from Course files to Legacy course files

#redirect [[Legacy course files]]

administrator

2024-09-09T12:41:33Z

Tsala: Changed redirect target from Administrator to Site administrators

#REDIRECT [[Site administrators]]

Notifications

2024-09-05T07:44:03Z

Tsala:

{{Messaging}}

'''New in 4.4:''' Web notifications are enabled by default for all users in new installations of Moodle LMS.

*Notifications alert teachers, students and other users about events in Moodle such as new forum posts, assignments needing grading or badges awarded.
*New notifications are highlighted with a number in the notifications menu at the top of the screen:
[[File:NewNotificationsMenu.png|center]]
Clicking there displays any new notifications, along with the option to mark all as read ''(1 below''), to go to the notifications preferences page ''(2)'' to change how notifications are received, and ''(3)'' to view all notifications.
[[File:NewNotificationsFeatures.png|center]]
Clicking 'View full notification' displays the notification in a full list, whereas clicking the main body of the notification will take you to the location in Moodle that the event happened, as in this example, to the assignment grading screen.
==Receiving notifications==
* Along with a visible alert to new events in the notifications menu, users can configure how they are notified of new events from their notification preferences page accessed from the user menu or from the gear icon in the notifications menu.
* Notifications may be sent via the web (when logged in to Moodle), email and mobile (for [[Moodle Mobile]]-enabled sites).
* Web offline options are for setting whether a user is notified when they next log in to Moodle.

[[File:Newloginnotifs.png|600px|frameless]]
==Admin settings==

Administrators can set the defaults from ''Site administration > General > Messaging > Notification settings''

There are three default types of notification plugins: web, email and mobile.

By default, web and email are both enabled, although email will only work of course if the site has been properly configured to deliver email. Mobile notifications are off by default and need to be configured first.
[[File:NotificationPlugins4.png|center|thumb|500px]]

====Mobile notifications====
[[File:mobilenotifications.png]]

The administrator can configure the site to push messages to mobile devices. Moodle pushes messages to a messaging server, which then pushes it to Apple or Google depending on the platform the target device is using (iOS or Android).

[[Site registration|Registered sites]] can make use of the default messaging server https://messages.moodle.net/ which is maintained by moodle.com. To connect to this, click 'Request access key' and then add it to the Airnotifier access key field.

Alternatively, you may install your own private Air notifier server and use that instead. See https://github.com/dongsheng/airnotifier for details.
===Default notification preferences===
You can specify the default notification preferences for each type of message in Site administration / Messaging / Notification settings.

You can also set to what degree each type of message is enabled, and whether users are able to change these default settings in their profiles:

* ''Enabled'' - Users are permitted or allowed to change the settings. When the user account is created, the new user will inherit the settings the administrator sets here, but will be allowed to change them afterwards in their Messaging settings. Messages will be delivered as the user sets them on their own Messaging settings page.

* ''Locked'' - Users are not permitted or allowed to change these settings. When the user account is created, the new user will inherit the settings the administrator sets here and will never be allowed to change them. Messages will be delivered for all users as you set them on this page.
====Ordering of messaging settings====
Because users might have many different messaging options, they are ordered into different components - for example, activities, system, enrolments etc.
[[File:Notification4.png|thumb|600px|center|Part of the Notification preferences screen for a teacher]]

==== List of notification types====

{| class="wikitable"
|-
! Module !! Output Name !! Description !! Recipients
|-
|Assignment||Assignment notifications||You have/Student has submitted an [[Assignment activity|assignment]] and Student has received a grade/feedback||Student, Teacher
|-
|Feedback||Feedback notifications||Notices from setting Enable notification of submissions in [[Feedback settings]]||Teacher, Feedback administrator
|-
|Feedback||Feedback reminder||[[Feedback activity|Feedback]] non-respondent reminder message|| Student feedback activity non-responders
|-
|Forum||Subscribed forum posts||Default for forum subscription handling||Anyone subscribed to a forum
|-
|Forum||Subscribed forum digests||A digest of forum subjects or subjects and posts if enabled in User - Forum Preferences, Set default for this in [[User default preferences]]|| Authenticated users
|-
|Lesson||Lesson essay graded notification||Notify students a teacher has graded a Lesson essay question||Student
|-
|Quiz||Notification of your student's quiz submissions||Message that student has submitted a quiz||Teacher
|-
|Quiz||Confirmation of your own quiz submissions||Notice to student that your quiz was successfully submitted||Student
|-
|Quiz||Warning when your quiz attempt becomes overdue||See [[Quiz settings]]||Student
|-
|Quiz||Notification that your attempt has been graded||Message that a teacher has posted feedback on an [[Quiz activity]]||Student
|-
|System||Notices about minor problems||?||Site administrators
|-
|System||Important errors with the site||Important errors - See also [[Debugging]]||Site administrators
|-
|System||Available update notifications||Notice of new releases of Moodle code||Site administrators
|-
|System||Personal messages between users||Using the Messaging interface tool||Authenticated Users
|-
|System||Backup notifications||Automated backup schedule run completed||Site administrators
|-
|System||Course creation request notification||Notice a course has been requested - See [[Course request]]||Defined in ''Site admin > Courses > Course request > Course request notification''
|-
|System||Course creation request approval notification ||Notice a requested course has been approved||User who requested the course
|-
|System||Course creation request rejection notification||Notice a requested course has been rejected||User who requested the course
|-
|System||Badge recipient notifications|| Notify recipient of a badge when it is awarded to them||Any badge recipient (typically Student role)
|-
|System||Badge creator notifications|| Notify creator of a badge when it is awarded to someone||Any badge creator (typically Teacher or Manager role)
|-
|System||Comment posted on a learning plan||?||?
|-
|System||Comment posted on a competency ||? ||?
|-
|System||Insights generated by prediction models||Notice of users that meet the Analytics criteria, see [[Managing Analytics]]||Teacher
|-
|System||Message contact requests notification||Notifies users when a non-contact user attempts to send them a message||Authenticated users
|-
|System||Asynchronous backup/restore notifications||Notifies users when a backup/restore is completed message, see [[Course backup]]||Authenticated users
|-
|System||Grade notifications||Message that a teacher has posted feedback on an [[Assignment activity|assignment]]||Student
|-
|System||Course completed||Automatic notification (congratulations note) about completing the course - sent to the student after all the course completion criteria have been achieved||Student
|-
|System||Antivirus failure notifications.||Warning message for Site Admin, see [[Antivirus plugins]]||Site Administrator
|-
|System||New login notifications||Warns a user if there was a failed login attempt with their username||Authenticated Users
|-
|System||Course content changes||Message that alerts students that a course activity was updated - activity title only, does not provide details about what has change)||Student
|-
|System||Custom report builder schedules||Notification of Report subscriptions, see [[Custom reports]]||usually Teacher or Manager
|-
|System||Welcome message for new course enrolments||Sends course welcome message to users added by manual or self enrolment||Student
|-
|Manual enrollments||Manual enrolment expiry notifications|| Notice if [[Manual enrolment]] is about to expire||Manual enrolees
|-
|Self enrollments||Self enrolment expiry notifications||Notify users when if [[Self enrolment]] is about to expire|| Enroller only, or Enroller & Enrolled user
|-
|Data privacy||Data request||Message that data review has been requested, see [[Data privacy]]||Privacy Officer
|-
|Data privacy||Data request processing results||Message that data review has been received and is processing, see [[Data privacy]]||Authenticated User
|-
|Data privacy||Data requests exceptions notifications||?||?
|-
|Inbound message configuration||Message to confirm that an inbound message came from you||See [[Incoming mail configuration]]||Authenticated Users
|-
|Inbound message configuration||Warning when an inbound message could not be processed||See [[Incoming mail configuration]]||Authenticated Users
|-
|Inbound message configuration||Confirmation that a message was successfully processed||See [[Incoming mail configuration]]||Authenticated Users
|-
|Event monitoring||Notification of rule subscriptions||Notifications from [[Event monitoring]] rules||Event rule subscribers
|}

===How to disable the 'New sign in to your account' notification===
Access Notification settings from the cog icon inside the Notifications icon at the top of your screen to the left of your profile. Disable the setting 'New login notifications'. (Note the admin can do this for the site from Site administration > Messaging > Notification settings.)

NOTE: disabling this as admin also prevents login information from being sent automatically to new users authorized via external database.

==Roles and Messaging capabilities==
The following capabilities can be applied as permissions to make custom changes to roles affecting messaging.
* [[Capabilities/moodle/course:bulkmessaging|course:bulkmessaging - Send a message to many people]]
* [[Capabilities/moodle/site:readallmessages|site:readallmessages - Read all messages on site]]
* [[Capabilities/moodle/site:sendmessage|site:sendmessage - Send messages to any user]]
* [[Capabilities/moodle/user:editownmessageprofile|user:editownmessageprofile - Edit own user messaging profile]]
* [[Capabilities/moodle/user:editmessageprofile|user:editmessageprofile - Edit user messaging profile]]
===Email===
All email messages and notifications go to the email address set in a user's profile. The administrator can optionally allow users to choose to have notifications sent to a different email address. This is off by default and can be enabled in ''Site administration > Messaging settings''.

Users can then enter their alternative email address under Preferences/User account/Notification preferences: Click on the gear icon next to "Email" in the table header and enter the alternative email.

Note: The 'messagingallowemailoverride' setting does not affect failed log in notifications as they do not go through the messaging system, and will therefore still go to the original email specified.
* [[Site notifications]] for administrators
[[de:Benachrichtigungen]]
[[es:Notificaciones]]

Site home FAQ

2024-08-23T07:16:05Z

Tsala: Update

{{Front page}}
==What do we mean by the 'site home' of Moodle?==

The site home is the front page. The link in the navigation is called 'Home'.

When logged in, a user's customised home page is called the 'Dashboard'.

==How can I change the look of the site home?==

*There are various ways of enhancing your site home without needing access to theme files on the server. First, see the section on tips and tricks in [[Site home settings]].
*If you are using Classic, Boost or other bootstrap-based themes you can then do some cool things with Bootstrap layout elements, as described in the thread [https://moodle.org/mod/forum/discuss.php?d=267662 LOOK & LEARN: How to add marketing spots as a front page topic].
*See also the simple customisation of the School demo site home in [[Standard themes]].
*You can set a different site home page for guests and logged in users with [[Conditional activities]] as described in the thread [https://moodle.org/mod/forum/discuss.php?d=268238 Show a different page to guests and logged in users].
*You may consider installing a custom theme from the [https://moodle.org/plugins/browse.php?list=category&id=3 Moodle plugins directory].

==How can I add text and a picture to the centre column?==

# In ''Administration > Site home > Site home settings '' make sure that 'Include a topic section' is ticked.
# Enable edit mode.
# Return to the Site home and click the edit icon at the top of the centre column
# Click the cog icon to add text and a picture to the Summary
# Click the 'Save changes' button

==How can I change the logo to the site home?==

# In ''Administration > Site administration > Appearance > Themes'' click the name of the theme you are using (If you're not sure which theme you are using, you can find out in ''Administration > Site administration > Appearance > Themes > Theme selector'')
# Enter the URL for your logo. (Note - you must previously have uploaded your logo somewhere online)
# Click the 'Save changes' button

Note: This setting is only available for certain themes.

==How do I get rid of a resource/activity that's appeared in "Site Pages"?==
When a resource or activity (like a page, file or forum) is added to the [[Main menu block]] on the site home page, it will appear as a site page. To remove this link, turn on the editing on, go to unhide or add the [[Main menu block]] and click to delete the item.

[[File:sitepagedelete.png]]

==How can I prevent activities I made on the site home page being seen in the navigation?==

Uncheck the box "Show site home activities in the navigation" in ''Site administration > Appearance > Navigation''.
==How can I hide site home blocks from guests but show to logged in users?==
See [[Blocks FAQ]]
==How can I show site home blocks to guests but hide from logged in users?==
See [[Blocks FAQ]]
==I want to limit the number of courses that appear on the site home page==

In ''Site administration > Appearance > Courses'', you can change the number of courses to be displayed on one page to a different number. Currently, the default is 20, but you can make it whatever you want. You can also, in the Site home settings, change what is displayed after login to show only categories.

One way of resolving this issue is to replace the course and Category list on the site home page with a HTML block that links off to the various category pages. This keeps your courses off the site home page altogether.

There are a couple of ways to do this, you can have a list of Categories, in a table, or you can use a table full of icons. Depending on your number of categories, say 11 different subject areas and one Administration area creates a table either four columns or four rows. For most people, the orderly nature of a balanced table implies an orderly site that is really welcome, particularly if the images linking to a Category are clear and the alt tag text says what it is linking to.

==How do I enable logged-in users to participate in site home page activities?==

Either:

# Go to ''Administration > Site administration > Users > Permissions > Define roles'' and edit the 'Authenticated user on frontpage' role
# Allow capabilities for the site home activities
# Click the 'Save changes' button

Or:

# Go to the Site home settings
# Set the default site home role to student
# Click the 'Save changes' button

==How can I add a page to the site home?==

#With the editing turned on, add the [[Main menu block]] if it isn't already present.
#Click ''Add and activity or resource'' and add a [[Page]].

If you wish the page to be hidden but accessible from the top dropdown menu, then:
#Copy the page's URL.
#Hide the block.
#Go to ''Site administration > Appearance > Themes > Theme settings'' and add your page URL to the custom menu items box according to the instructions.

Note that if it is possible to install plugins on your Moodle site then you can also use the [https://moodle.org/plugins/view/local_staticpage Static pages plugin].

==How can I get rid of the site short name in the navigation bar?==
Sometimes if the short and full names of your site are similar, you might wish to hide the short name. You can do this by adding lines to the custom CSS box in the theme settings page.

To hide the short name but keep the space where it used to be, add:

a.brand {visibility:hidden}

To hide the short name and also remove the space where it used to be, add:
.navbar .brand {display: none;}

[[Category:FAQ]]

[[fr:FAQ Page d'accueil]]
[[de:Startseite FAQ]]
[[es:Portada FAQ]]

Site home

2024-08-23T07:05:56Z

Tsala:

{{Site appearance}}
The Site home (formerly front page) is the initial page seen by someone reaching a Moodle site after or before a login. Typically a student will see [[Courses|courses]], some [[Blocks|blocks]] of information, displayed in a [[Themes|theme]]. In the [[Navigation bar]] and [[Navigation block]] it is called "Home".

A combination of [[Site policies|site policies]], [[Authentication|user authentication]] and [[Front page settings | front page settings]] determine who can get to the Site home. And once they get there [[Front Page settings|what they can see]] and [[Roles|what they can do]].

In many ways, the Site home has similar features and functions to those in a [[Course]]. For example, [[Activities]], [[Resources]] and [[Blocks]] can be added to the Site home to give it different looks.
{{MediaPlayer | url = https://youtu.be/F7MhkmdnCb4
| desc = Customise Site home/Front page}}

==See also==
*[[Site home settings]]
*[[Site home FAQ]]
*[[Course homepage]]

[[de:Startseite]]
[[es:Portada]]

External database enrolment

2024-08-21T07:49:59Z

Tsala: /* Creating courses */

{{Enrolment}}
==Using an external database to control enrolments==

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

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

*access
*ado
*mssql
*borland_ibase
*csv
*db2
*fbsql
*firebird
*ibase
*informix72
*informix
*mysql (deprecated, please use mysqli instead)
*mysqli
*mysqlt
*oci805
*oci8
*oci8po
*odbc
*odbc_mssql
*odbc_oracle
*oracle
*postgres64
*postgres7
*postgres
*proxy
*sqlanywhere
*sybase
*vfp

== Enrolment and unenrolment ==

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

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

== Hidden courses ==

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

== Enrolment and roles ==

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

== Unenrolment ==

The External unenrol action ("enrol_database | unenrolaction") setting in the plugin settings page defines what action should be taken when a user enrolment disappears from external enrolment source. Each setting does the following:
#'''"Unenrol user from course"''' When the user disappears from the external source, the enrolment is completely removed and all the roles removed. This means some user data and settings are purged from course during course unenrolment (that usually include grades, activity attempts, etc.)
#'''"Keep user enrolled"''' When the user disappears from the external source, the enrolment is kept as is, and the user is still able to enter the course and perform activities, access resources, etc. It's a "do nothing" option.
#'''"Disable course enrolment"''' When the user disappears from the external source, user enrolment is suspended (the user can't access the course, but user data and settings are kept), and roles are kept as is. You might use this because in some cases the user needs a role with some capability to be visible in UI - such has in gradebook, assignments, etc.
#'''"Disable course enrolment and remove roles"''' When the user disappears from the external source, the enrolment is suspended and roles assigned by enrol instance are removed. Please note that user may "disappear" from gradebook and other areas.

== Creating courses ==

Optionally courses that do not exist in the Moodle site can be created.

You can additionally specify the Category into which the new course will be placed, in the '''New course category id field'''. The data in this field must be the id of a currently existing category; it will not create a new category. The id number is number assigned by Moodle in the database when the category is created (e.g. mdl_course_categories.id).

* Do not confuse this ''category id'' with the new custom ''category id number'' field that you can manually assign to a category. (See MDL-28518 and MDL-31845).
* Leaving the category id data empty means that a course will be assigned to the default category.
* If you assign data to categories that do not exist already in Moodle, the courses will not be created.

'''Default new course category''' is the category to which courses will be assigned and created in, unless you set up and so indicate in the data field of the "New course category id field."

You may also specify a '''New course template''': a "template" course from which the new course will be copied. The data for this field should be the ''shortname'' of the template course.

== Synchronising external database enrolments ==

===Scheduled task===
A scheduled task called "Synchronise external database enrolments task" synchronises all user enrolments at once - both adding and removing user enrolments (and creating courses if specified) (MDL-59986). The settings for this are in ''Site administration > Server > Tasks > Scheduled tasks''. You should make sure that this script is enabled and set to run as often as you need to perform the enrolments. By default it is disabled and set to run only once a day.

(Note: a deprecated script had been provided from Moodle 3.6 to 3.10 to use in case of issues with the Scheduled task added to Moodle 3.6. [https://tracker.moodle.org/browse/MDL-63266 This has been removed as of Moodle 3.11]).

=== User accounts ===

This is a reminder that you need to make sure all the users present in the external enrolments are already have accounts created in Moodle, because users not existing in Moodle can't be enrolled in a course. If you are using external authentication plugins (db, ldap, etc.) you can use the scripts provided by those plugins to synchronise your users before running this script.

== Setting up enrolment sync (How to) ==

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

* Use an existing database or create a new one. Use an existing table or create a new one with the following minimum fields.
*# A unique course identifier to match one of the following fields.
*#* the "idnumber" field in Moodle's course table (varchar 100), which is manually specified as the "Course ID number" when editing a course's settings
*#* the "shortname" field in Moodle's course table (varchar 255), which is manually specified as the "Course short name" when editing a course's settings
*#* the "id" field in Moodle's course table (int 10), which is based on course creation order
*# A unique user identifier to match one of the following fields.
*#* the "idnumber" field in Moodle's user table (varchar 255), which is manually specified as the "ID number" when editing a user's profile
*#* the "username" field in Moodle's user table (varchar 100), which is manually specified as the "Username" when editing a user's profile
*#* the "email" field in Moodle's user table (varchar 100), which is manually specified as the "Email address" when editing a user's profile
*#* the "id" field in Moodle's user table (int 10), which is based on user creation order
*# (optional) A unique role identifier to match one of the following fields.
*#* the "shortname" field in Moodle's role table (varchar 100), for example editingteacher, coursecreator, student, ...
*#* the "name" field in Moodle's role table (varchar 255), for example Teacher, Course creator, Student, ...
*#* the "id" field in Moodle's role table (int 10), which is based on initial installation and new role creation order
* Populate the database table. Each user/course combination to have a record in the table.
* In Moodle, go to ''Site administration > Plugins > Enrolments > Manage enrol plugins'', find External Database in the list, enable it (click the closed-eye icon) and click Settings.
* In the top panel, select the database type (make sure you have the necessary configuration in PHP for that type) and then supply the information to connect to the database.
* The middle panel creates the mapping between Moodle and the external database. The first three settings are for the local (Moodle) field names and the last three for the remote (external database) settings. They are in the same order.
** enrol_localcoursefield / enrol_remotecoursefield - in Moodle the name of the field in the course settings the uniquely identifies the course (e.g., idnumber). In the external database the name of the matching field.
** enrol_localuserfield / enrol_remoteuserfield - in Moodle the name of the field in the user profile that uniquely identified the user (e.g., idnumber). In the external database the name of the matching field.
** enrol_db_localrolefield / enrol_db_remoterolefield - (optional) in Moodle the name of the field in the role edit page the uniquely identifies the role (e.g., shortname). In the external database the name of the matching field.
* The Roles panel specifies the role that the user will get in the course if their role is not specified in the external database.
* A new optional field enrol_database | remoteotheruserfield allows those with the role "Other users" to be added but not to be included as course participants.
* The final panel enables auto creation of courses.
* Save changes, and then tick the box to enable external database enrolment.

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

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

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

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

== Potential gotchas ==

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

==Errors and diagnostics==

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

==See also==

*[http://moodle.org/mod/forum/discuss.php?d=74133 Someone explain external database enrolment, please??] forum discussion
*Example Setup [https://docs.moodle.org/en/Talk:External_database_enrolment#Example_External_Enrollment] Example Database Enrollment Setup
*[[External database authentication]]

[[es:Inscripción por BasedeDatos externa]]
[[fr:Inscription par base de données externe]]
[[de:Einschreibung über externe Datenbank]]
[[ja:外部データベース登録]]

Access all groups

2024-08-20T06:44:36Z

Tsala: redirect

#redirect [[Capabilities/moodle/site:accessallgroups]]

Automated course backup

2024-08-16T11:55:14Z

Tsala: /* Setting an automated course backup schedule */

{{Backup}}
==Automating course backups==

Automated course backups runs the same functions as individual [[course backup]]s. It's a good idea to schedule backups for when your server isn't usually busy. Running the backup tool over all the courses can be processor-intensive, so you shouldn't run it when there are a lot of students trying to access the server. You should always alert users with an announcement on the first page that if they log on during the backup hours they may notice a decrease in performance.

In order to make scheduled backups, you have to set up CRON to run periodically. Please refer to the [[Cron|cron instructions]].

==Setting an automated course backup schedule==

To set the backup schedule:
#Go to ''Administration > Site administration > Courses > Backups > Automated backup setup''.
#Set backup_auto_active to enabled.
#Select the days of the week to run the backup.
#Set the execution time for the backup process. For most servers, early morning will be the best time. Keep in mind the time zone your server is using.
#Set the "Save to..." path. If you can, choose a backup path on another machine or on a different drive than the one Moodle is on. You don't want to lose your backups at the same time you lose your Moodle site if the drive fails. If you leave the field blank, then backup zip files will be saved in the backup folder of each course files folder. On a Linux server the path might look like: '''/home/(your user or domain)/public_html/archive/''' or if it's below the publicly accessible folders: '''/home/(your user or domain)/archive/'''. On Windows the path might look like: '''D:\Archive\'''.
If the path is not recognized a red X is shown after saving, otherwise a green check.
#Set all other options appropriately.
#Click the "Save changes" button.

'''Tip''': To save disk space, you can choose to delete backups older than a specified number of days. If so, you should also specify a minimum number of backups to be kept.

Once you've set up your backup schedule, Moodle will automatically create archives of all the courses on the server at the time you specified. Once the backup is complete, Moodle will send you an email describing the status of the backup.

==Backups report==

A last execution log of scheduled course backups can be found in ''Administration > Site administration > Reports > Backups''. It displays a list of all course backups made, the time taken to create them, their status (see below), and the next scheduled automated backup execution time.

Clicking the 'View logs' icon next to the course name (1 in screenshot below) will display a detailed backup log for a particular course, including date, hour and minute when each step of the backup was performed (2). This log is useful for troubleshooting backup errors.

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

===Backup status===

*'''OK''' - The course backup was successfully completed.
*'''Skipped''' - The course was skipped (not backed up) because the course was unavailable to students and had not been changed in the last 31 days. This is not an error, but a feature designed to save process time.
*'''Unfinished''' - The backup was not finished. This might have happened because the job to execute backups ran out of time or resources (e.g., the cron running the backups ran out of time before finishing all the courses waiting). The unfinished jobs should be completed when the next scheduled backups are repeated.
*'''Error''' - There were errors in the backup process for the course, so a backup was not completed. For additional details about the error (1) check the backup log for the affected course (i.e. click the 'View logs' icon next to the course name) or (2) back up the course manually with debugging turned on to see what error message is displayed.

==Course versus site backups==

*Automated course backups are more expensive in terms of time and CPU usage. The recovery time to have your site running again is longer.
*Course backups are useful for obtaining "fresh" copies of courses to be re-used or distributed individually, however they should never be used as a primary backup system (unless your hosting doesn't allow the preferred [[site backup]]s).

==Capabilities==

Both the [[Capabilities/moodle/backup:downloadfile|download course backup files capability]] and the [[Capabilities/moodle/restore:userinfo|restore user data from a course backup capability]] are required to be able to download automated course backups. There is also a [[Capabilities/moodle/restore:viewautomatedfilearea|restore courses from the automated backup storage capability]].

[[Category:Report]]
[[Category:Site administration]]

[[eu:Ikastaroen segurtasun-kopia automatikoa]]
[[fr:Sauvegarde (administrateurs)#Rapports Sauvegardes]]
[[ja:自動コースバックアップ]]
[[de:Automatische Kurssicherung]]
[[es:Respaldo de curso automatizado]]

Automated course backup

2024-08-16T11:54:50Z

Tsala: /* Setting an automated course backup schedule */

{{Backup}}
==Automating course backups==

Automated course backups runs the same functions as individual [[course backup]]s. It's a good idea to schedule backups for when your server isn't usually busy. Running the backup tool over all the courses can be processor-intensive, so you shouldn't run it when there are a lot of students trying to access the server. You should always alert users with an announcement on the first page that if they log on during the backup hours they may notice a decrease in performance.

In order to make scheduled backups, you have to set up CRON to run periodically. Please refer to the [[Cron|cron instructions]].

==Setting an automated course backup schedule==

To set the backup schedule:
#Go to ''Administration > Site administration > Courses > Backups > Automated backup setup''.
#Set backup_auto_active to enabled.
#Select the days of the week to run the backup.
#Set the execution time for the backup process. For most servers, early morning will be the best time. Keep in mind the time zone your server is using.
#Set the "Save to..." path. If you can, choose a backup path on another machine or on a different drive than the one Moodle is on. You don't want to lose your backups at the same time you lose your Moodle site if the drive fails. If you leave the field blank, then backup zip files will be saved in the backup folder of each course files folder. On a Linux server the path might look like: '''/home/(your user or domain)/public_html/archive/''' or if it's below the publicly accessible folders: '''/home/(your user or domain)/archive/'''. On Windows the path might look like: '''D:\Archive\'''.
If the path is not recognized a red X is shown after saving, otherwise a green check.
#Set all other options appropriately.
#Click the "Save changes" button.

'''Tip''': To save disk space, you can choose to delete backups older than a specified number of days. If so, you should also specify a minimum number of backups to be kept. (The settings 'Delete backups older than' and 'Minimum number of backups kept' are new in Moodle 3.0 onwards.)

Once you've set up your backup schedule, Moodle will automatically create archives of all the courses on the server at the time you specified. Once the backup is complete, Moodle will send you an email describing the status of the backup.

==Backups report==

A last execution log of scheduled course backups can be found in ''Administration > Site administration > Reports > Backups''. It displays a list of all course backups made, the time taken to create them, their status (see below), and the next scheduled automated backup execution time.

Clicking the 'View logs' icon next to the course name (1 in screenshot below) will display a detailed backup log for a particular course, including date, hour and minute when each step of the backup was performed (2). This log is useful for troubleshooting backup errors.

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

===Backup status===

*'''OK''' - The course backup was successfully completed.
*'''Skipped''' - The course was skipped (not backed up) because the course was unavailable to students and had not been changed in the last 31 days. This is not an error, but a feature designed to save process time.
*'''Unfinished''' - The backup was not finished. This might have happened because the job to execute backups ran out of time or resources (e.g., the cron running the backups ran out of time before finishing all the courses waiting). The unfinished jobs should be completed when the next scheduled backups are repeated.
*'''Error''' - There were errors in the backup process for the course, so a backup was not completed. For additional details about the error (1) check the backup log for the affected course (i.e. click the 'View logs' icon next to the course name) or (2) back up the course manually with debugging turned on to see what error message is displayed.

==Course versus site backups==

*Automated course backups are more expensive in terms of time and CPU usage. The recovery time to have your site running again is longer.
*Course backups are useful for obtaining "fresh" copies of courses to be re-used or distributed individually, however they should never be used as a primary backup system (unless your hosting doesn't allow the preferred [[site backup]]s).

==Capabilities==

Both the [[Capabilities/moodle/backup:downloadfile|download course backup files capability]] and the [[Capabilities/moodle/restore:userinfo|restore user data from a course backup capability]] are required to be able to download automated course backups. There is also a [[Capabilities/moodle/restore:viewautomatedfilearea|restore courses from the automated backup storage capability]].

[[Category:Report]]
[[Category:Site administration]]

[[eu:Ikastaroen segurtasun-kopia automatikoa]]
[[fr:Sauvegarde (administrateurs)#Rapports Sauvegardes]]
[[ja:自動コースバックアップ]]
[[de:Automatische Kurssicherung]]
[[es:Respaldo de curso automatizado]]

Legacy course files

2024-08-01T14:30:16Z

Tsala:

{{Repositories}}
<p class="note">Note: This page only applies to sites which have been upgraded from Moodle 1.9.</p>
In Moodle 2.0 onwards, files are stored in separate areas, rather than together in the course files area. When a site is upgraded from 1.9, the course files area is renamed 'Legacy course files'. By default, this area is not available in new courses.

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

==Enabling legacy course files areas==

To enable a legacy course files area in a new course

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

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

==Repository capabilities==

The capabilities [[Capabilities/repository/coursefiles:view|Use course files repository plugin]] and [[Capabilities/moodle/course:managefiles|Manage files]] are both required for users to access the legacy course files area.

==FAQs==
===Can you find out disk volume of legacy files?===
No. You will need a custom report of some kind. See http://moodle.org/mod/forum/discuss.php?d=201601

===Where are legacy files stored?===
For one explanation, see http://moodle.org/mod/forum/discuss.php?d=164544

If you are looking to add files to the course (such as for testing). Go to 'Administration > Course administration > Legacy course files' in your course (with all the appropriate settings set as mentioned above). You can upload and delete files here.

===Is there a way to delete legacy files en masse?===
No, see MDL-36008.

===Is there a way to prevent new additions to legacy files?===
Yes. Unchecking [[Managing_repositories#Allow adding to legacy course files|Allow adding to legacy course files]] in ''Site Administration > Plugins > Repositories > Common repository settings'' will prevent users from adding new files and directories to legacy course files, but they will still be able to delete files.

===What happens if you switch legacy files off in a site that has been upgraded and has a lot of legacy files?===
Unsure.

===Can you migrate a course from 1.9 to 2+ and NOT end up with a legacy files repository?===
Yes, you can. If you restore as a Teacher into the course you're currently present in (best if it's empty) and don't override any settings then the Legacy Files will not be added as a Repository.

===What happens to the Legacy files in a course imported from 1.9 to 2.x that is re-imported into another 2.x?===

===In backups, are legacy files included with a course?===
Yes.

===What happens if legacy files were previously enabled and then the legacy course files repository is disabled?===

Legacy course files are displayed if they have ever been enabled on the course, but can be disabled at the course level in the course settings. Any new courses created will not have a legacy course files area.

[[ja: レガシーコースファイル]]
[[de:Legacy-Kursdateien]]
[[es:Archivos de curso heredados]]
[[fr:Fichiers du cours (obsolète)]]

Course files

2024-08-01T14:27:02Z

Tsala: redirect

#redirect [[Legacy course files]]

Talk:Course files

2024-08-01T14:26:37Z

Tsala: reply

It seems like it might be time to retire this page.
--[[User:Tim Bahula 2|Tim Bahula 2]] ([[User talk:Tim Bahula 2|talk]]) 15:10, 14 July 2022 (UTC)

:You're right Tim, thanks. I'm going to redirect the page to [[Legacy course files]] so we keep the page history. --[[User:Helen Foster|Helen Foster]] ([[User talk:Helen Foster|talk]]) 14:26, 1 August 2024 (UTC)

2024-08-01T14:24:50Z

Tsala:

<div class="navtrail">[[Main page]] ► [[{{PAGENAME}}]]</div>
==[[About Moodle]]==

*[[Features]]
*[[New features]]
*[[Philosophy]]
*[[Pedagogy]]
*[[Standards]]
*[[Accessibility]]
*[[History]]
*[[Usage]]
*[[Moodle site - basic structure]]
*[[Moodle key terms]]
*[[About Moodle FAQ]]

==[[Installation]]==

*[[Installing Moodle]]
*[[Installation Quickstart]]
*[[Cron]]
*[[Installing plugins]]
*[[Installation FAQ]]
*[[Upgrading]]
*[[Upgrade overview]]
*[[Automatic updates deployment]]
*[[Git for Administrators]]
*[[Administration via command line]]
*[[Upgrading FAQ]]
*[[Moodle migration]]

==[[Managing a Moodle site]]==

*[[Guide for new administrators]]
*[[Administration FAQ]]

====[[Authentication]]====
*[[Managing authentication]]
*[[Manual accounts]]
*[[No login]]
*[[Email-based self-registration]]
*[[CAS server (SSO)]]
*[[External database authentication]]
*[[LDAP authentication]]
*[[MNet]]
*[[No authentication]]
*[[Shibboleth]]
*[[Authentication FAQ]]

====[[Managing accounts]]====
* [[Browse list of users]]
* [[Bulk user actions]]
* [[Add a new user]]
* [[Upload users]]
* [[User pictures]]
* [[User profile fields]]
* [[Additional name fields]]
* [[Accounts FAQ]]

====[[Enrolments]]====
*[[Enrolment plugins|Managing enrolment plugins]]
*[[Manual enrolment]]
*[[Self enrolment]]
*[[Cohort sync]]
*[[Course meta link]]
*[[Guest access]]
*[[Category enrolments]]
*[[External database enrolment]]
*[[Enrolment on payment]]
*[[Flat file]]
*[[IMS Enterprise]]
*[[LDAP enrolment]]
*[[MNet remote enrolments]]
*[[Paypal enrolment]]
*[[Publish as LTI tool]]
*[[Enrolment FAQ]]

====[[Payment gateways]]====

====[[Roles and permissions]]====
*[[Managing roles]]
*[[Assign roles]]
*[[User policies]]
*[[Using roles]]
*[[Standard roles]]
**[[Site administrators|Site administrator]]
**[[Manager role]]
**[[Course creator role]]
**[[Teacher role]]
**[[Non-editing teacher role]]
**[[Student role]]
**[[Guest role]]
**[[Authenticated user role]]
*[[Creating custom roles]]
*[[Permissions]]
*[[Override permissions]]
*[[Roles FAQ]]

====[[Security]]====

*[[Security recommendations]]
*[[Security checks]]
*[[Site policies]]
*[[Notifications]]
*[[Password salting]]
*[[Privacy]]
**[[Policies]]
**[[Data privacy]]
**[[Privacy officer role]]
*[[Reducing spam in Moodle|Reducing spam]]
*[[Security FAQ]]

====[[Performance]]====

*[[Performance recommendations]]
*[[Performance settings]]
*[[Performance overview]]
*[[Caching]]
*[[Performance FAQ]]
*[[MUC FAQ]]

====[[Backup]]====
*[[Site backup]]
*[[Course backup]]
*[[Course restore]]
*[[Automated course backup]]
*[[Year-end procedures]]
*[[IMS Common Cartridge import and export]]
*[[Backup and restore FAQ]]

====[[Site appearance]]====
*[[Front page]]
**[[Front page settings]]
**[[Front page FAQ]]
*[[Dashboard]]
*[[User profiles]]
*[[Navigation]]
*[[Course list]]
*[[Themes]]
**[[Theme settings]]
**[[Standard themes]]
**[[Installing a new theme]]
**[[Themes FAQ]]
*[[Header and footer]]

====[[Language]]====
*[[Language settings]]
*[[Language customisation]]
*[[Language packs]]
*[[Language FAQ]]

====[[Server settings]]====
*[[System paths]]
*[[Session handling]]
*[[HTTP]]
*[[Maintenance mode]]
*[[Cleanup]]
*[[Environment]]
*[[Site registration]]
*[[Mail configuration]]
*[[Scheduled tasks]]

====[[Site-wide reports]]====

*[[Config changes report]]
*[[Course overview report]]
*[[Events list report]]
*[[Question instances report]]
*[[Reports FAQ]]

====[[Admin tools]]====
*[[Migration from MyISAM to InnoDB|Convert to InnoDB]]
*[[Database transfer]]
*[[Search and replace tool|DB search and replace]]
*[[Reducing spam in Moodle|Spam cleaner]]
*[[Location|Timezones updater]]

====[[Developer tools]]====
*[[Experimental settings]]
*[[Debugging]]

====[[Web services]]====
*[[Using web services]]
*[[Mobile web services]]
*[[Web services FAQ]]
====[[Communication]]====
*[[Matrix]]
*[[Custom link]]

====[[More features]]====
*[[Blogs]]
**[[Blog settings]]
**[[Using Blogs]]
**[[Blogs FAQ]]
*[[Comments]]
**[[Comments FAQ]]
*[[Tags]]
**[[Tag settings]]
**[[Using tags]]
**[[Managing tags]]
**[[Tags FAQ]]
*[[Messaging]]
**[[Notifications]]
**[[Messaging settings]]
**[[Messaging FAQ]]
*[[Notes]]
**[[Notes FAQ]]
*[[RSS feeds]]
**[[RSS feeds settings]]
**[[Using RSS feeds]]
**[[RSS feeds FAQ]]
*[[Calendar]]
**[[Calendar settings]]
**[[Using Calendar]]
**[[Calendar import]]
**[[Calendar FAQ]]
*[[Global search]]
*[[Recycle bin]]

==[[Managing a Moodle course]]==

* [[Teacher quick guide]]

====[[Courses]]====
*[[Adding a new course]]
*[[Upload courses]]
*[[Course categories]]
*[[Course settings]]
*[[Course formats]]
*[[Course homepage]]
*[[Restrict access]]
**[[Restrict access settings]]
**[[Using restrict access]]
**[[Restrict access FAQ]]
*[[Stealth activities]]
*[[Course relative dates]]
*[[Course FAQ]]

====[[Editing text]]====
*[[Text editor]]
*[[Formatting text]]
*[[Text editor FAQ]]

====[[Activities]]====

*[[Managing activities]]
*[[Assignments]]
**[[Assignment settings]]
**[[Using Assignment]]
**[[Assignment FAQ]]
*[[Chat]]
**[[Chat settings]]
**[[Using Chat]]
**[[Chat FAQ]]
*[[Choice]]
**[[Choice settings]]
**[[Using Choice]]
**[[Choice FAQ]]
*[[Database]]
**[[Database settings]]
**[[Building Database]]
**[[Database templates]]
**[[Using Database]]
**[[Database FAQ]]
*[[External tool]]
**[[External tool settings]]
**[[Using External tool]]
**[[External tool FAQ]]
*[[Feedback]]
**[[Feedback settings]]
**[[Using Feedback]]
**[[Feedback FAQ]]
*[[Forum]]
**[[Forum settings]]
**[[Using Forum]]
**[[Forum FAQ]]
*[[Glossary]]
**[[Glossary settings]]
**[[Using Glossary]]
**[[Glossary FAQ]]
*[[Lesson]]
**[[Lesson settings]]
**[[Building Lesson]]
**[[Using Lesson]]
**[[Lesson FAQ]]
*[[SCORM]]
**[[SCORM settings]]
**[[Using SCORM]]
**[[SCORM FAQ]]
*[[Survey]]
**[[Survey settings]]
**[[Using Survey]]
**[[Survey FAQ]]
*[[Quiz]]
**[[Quiz settings]]
**[[Building Quiz]]
**[[Using Quiz]]
**[[Quiz reports]]
**[[Quiz FAQ]]
*[[Wiki]]
**[[Wiki settings]]
**[[Using Wiki]]
**[[Wiki FAQ]]
*[[Workshop]]
**[[Workshop settings]]
**[[Using Workshop]]
**[[Workshop FAQ]]

====[[Resources]]====

*[[Book module|Book]]
**[[Book settings]]
**[[Using Book]]
**[[Book FAQ]]
*[[File resource]]
**[[File resource settings]]
**[[File resource FAQ]]
*[[Folder]]
**[[Folder module settings]]
**[[Folder FAQ]]
*[[IMS content package]]
**[[IMS content package settings]]
**[[IMS content package FAQ]]
*[[Label]]
**[[Label module settings]]
**[[Using Label]]
**[[Label FAQ]]
*[[Page resource]]
**[[Page resource settings]]
**[[Using Page]]
**[[Page FAQ]]
*[[URL resource]]
**[[URL resource settings]]
**[[URL resource FAQ]]

====[[Blocks]]====

*[[Managing blocks]]
*[[Block settings]]
*[[Activities block]]
*[[Admin bookmarks block]]
*[[Administration block]]
*[[Blog menu block]]
*[[Blog tags block]]
*[[Calendar block]]
*[[Comments block]]
*[[Course completion status block]]
*[[Course overview block]]
*[[Course/site summary block]]
*[[Courses block]]
*[[Flickr block]]
*[[HTML block]]
*[[Latest news block]]
*[[Login block]]
*[[Logged in user block]]
*[[Main menu block]]
*[[Mentees block]]
*[[Messages block]]
*[[My latest badges block]]
*[[My private files block]]
*[[Navigation block]]
*[[Network servers block]]
*[[Online users block]]
*[[People block]]
*[[Quiz results block]]
*[[Random glossary entry block]]
*[[Recent activity block]]
*[[Recent blog entries block]]
*[[RSS feeds block]]
*[[Search forums block]]
*[[Section links block]]
*[[Self completion block]]
*[[Social activities]]
*[[Tags block]]
*[[Upcoming events block]]
*[[Youtube block]]
*[[Blocks FAQ]]

====[[Questions]]====

*[[Managing questions]]
**[[Question bank]]
**[[Question categories]]
**[[Import questions]]
**[[Export questions]]
*[[Question behaviours]]
*[[Calculated question type|Calculated]]
*[[Simple calculated question type|Simple Calculated]]
*[[Calculated multichoice question type|Calculated Multichoice]]
*[[Description question type|Description]]
*[[Essay question type|Essay]]
*[[Matching question type|Matching]]
*[[Embedded Answers (Cloze) question type|Embedded Answers (Cloze)]]
*[[Multiple Choice question type|Multiple Choice]]
*[[Short-Answer question type|Short-Answer]]
*[[Numerical question type|Numerical]]
*[[True/False question type|True/False]]
*[[Questions FAQ]]

====[[Course enrolment]]====
*[[Participants]]
*[[Enrolment methods]]
*[[Enrolment key]]
*[[Unenrolment]]
*[[Other users]]

====[[Grouping users]]====
*[[Groups]]
*[[Import groups]]
*[[Groupings]]
*[[Cohorts]]
*[[Groups FAQ]]
*[[Groupings FAQ]]

====[[Tracking progress]]====
*[[Grades]]
**[[Grading quick guide]]
**[[Grader report]]
**[[Grade settings]]
**[[Managing grades]]
**[[Scales]]
**[[Outcomes]]
**[[Grade import]]
**[[Grade export]]
**[[Advanced grading methods]]
**[[Grades FAQ]]
*[[Competencies]]
** [[Competency frameworks]]
** [[Learning plans]]
** [[Competencies FAQ]]
*[[Activity completion]]
**[[Activity completion settings]]
**[[Using Activity completion]]
**[[Activity completion FAQ]]
*[[Course completion]]
**[[Course completion settings]]
**[[Using Course completion]]
**[[Course completion FAQ]]
*[[Badges]]
**[[Managing badges]]
**[[Badges settings]]
**[[Using badges]]
**[[Badges FAQ]]
*[[Course reports]]
** [[Activity completion report]]
** [[Competency breakdown report]]
** [[Logs]]
** [[Activity report]]
** [[Participation report]]
** [[Statistics]]
** [[Event monitoring]]

====[[Reusing activities]]====
*[[Activity backup]]
*[[Activity restore]]
*[[Import course data]]
*[[Reset course]]

==[[Managing content]]==

====[[Working with files]]====
*[[File picker]]
*[[File picker FAQ]]

====[[Repositories]]====
*[[Managing repositories]]
*[[Upload a file repository]]
*[[Server files repository]]
*[[Recent files repository]]
*[[Private files]]
*[[Google Drive repository]]
*[[Youtube videos repository]]
*[[Flickr public repository]]
*[[Flickr repository]]
*[[Picasa web album repository]]
*[[URL downloader repository]]
*[[Wikimedia repository]]
*[[Amazon S3 repository]]
*[[Box.net repository]]
*[[Dropbox repository]]
*[[File system repository]]
*[[Merlot.org repository]]
*[[Skydrive repository]]
*[[EQUELLA repository|EQUELLA]]
*[[WebDAV repository]]
*[[Repositories FAQ]]

====[[Portfolios]]====
*[[Managing portfolios]]
*[[Box.net portfolio]]
*[[File download]]
*[[Flickr]]
*[[Google Docs portfolio]]
*[[Picasa]]
*[[Mahara]]
*[[Portfolios FAQ]]

====[[Working with media]]====
*[[Video]]
*[[Audio]]
*[[Images]]
*[[Media embedding]]
*[[Media FAQ]]

====[[H5P]]====

====[[Data formats]]====

====[[Document converters]]====

* [[Universal Office Converter (unoconv)]]
* [[Google Drive converter]]

====[[Filters]]====
*[[Managing filters]]
*[[Filter settings]]
*[[Activity_names_auto-linking_filter|Activity names auto-linking]]
*[[Algebra filter|Algebra notation]]
*[[Convert URLs into links filter]]
*[[Database auto-linking filter]]
*[[Display emoticons as images filter]]
*[[Display H5P filter|Display H5P]]
*[[Email protection filter]]
*[[Glossary auto-linking filter]]
*[[HTML tidy filter]]
*[[MathJax filter]]
*[[Multimedia plugins filter]]
*[[Multi-language content filter]]
*[[TeX notation filter]]
*[[Word censorship filter]]
*[[Filters FAQ]]

====[[Licenses]]====

====[[Plagiarism prevention]]====
*[[Managing plagiarism prevention]]
*[[Plagiarism prevention FAQ]]

====[[Download course content]]====

==[[Moodle Mobile]]==
* [[Moodle Mobile features]]
* [[New for mobile]]
* [[Moodle Mobile guide for admins]]
* [[Mobile app notifications]]
* [[Creating Moodle Mobile friendly sites]]
* [[Moodle Mobile FAQ]]

[[es:Tabla_de_Contenidos]]
[[it:Tavola dei Contenuti]]

Repositories

2024-08-01T14:24:17Z

Tsala: /* Additional standard repositories disabled by default */ removing legacy course files

{{Managing content}}
'''Repositories''' in Moodle enable users to add files to a course and other locations in Moodle. Repositories provide access to specific types of file sources. They can also allow, where appropriate, users to upload files, access previously uploaded files, and to easily bring content into Moodle from external sources, such as Flickr or Google Docs.

See [[Managing repositories]] for more on configuring and managing them.
==Standard repositories==
Repositories are managed in ''Site administration > Plugins > Repositories > Manage repositories''. Standard repositories come with default Moodle. It is also possible to add additional repositories via Moodle plugins.
===Repositories enabled by default===
*[[Content bank]] Gives access to H5P files created or uploaded into the content bank in courses (in 3.9 onwards)
* [[Embedded files repository|Embedded files]] - Allows linking to files and images available to the user that have been added/embedded in their course activities
* [[Server files repository|Server files]] - Gives access to files elsewhere on the Moodle site (limited by a user's permissions)
* [[Recent files repository|Recent files]] - Shows the last 50 files you have uploaded, according to the context
* [[Upload a file repository|Upload a file]] - Enables the "Upload a file" option in the site File picker to allow users to browse for and upload files
* [[Private files]] - Enables access to a personal storage area for every user
* [[URL downloader repository|URL downloader]] - Allows downloading of files and images from a particular URL
* [[Wikimedia repository|Wikimedia]] - Lets users search for and insert media (images) from Wikipedia

===Additional standard repositories disabled by default===
These may be enabled and set to visible or hidden by a site administrator.
* [[Box repository|Box]] - bring files in from your Box account
* [[Dropbox repository|Dropbox]] - link to or copy files from Dropbox
* [[EQUELLA repository|EQUELLA]] - link to files in an EQUELLA installation
* [[File system repository|File system]] - access files uploaded to a folder on your server (by, e.g. FTP)
* [[Flickr repository|Flickr]] - search for and display images from your personal Flickr account
* [[Flickr public repository|Flickr public]] - search for and display images publicly available from Flickr
* [[Google Drive repository|Google Drive]] - bring files from your Google Drive account
* [[Merlot.org repository|Merlot.org]] - bring resources in from Merlot.org
* [[Nextcloud repository|Nextcloud]]
* [[Amazon S3 repository|Amazon S3]] - enables users to copy files from Amazon S3 storage instances
* [[Skydrive repository|OneDrive]] bring in files from your Microsoft OneDrive
* [[WebDAV repository|WebDAV]] -bring in files from external sources using WebDAV protocol
* [[YouTube videos repository|YouTube videos]] - search for and display YouTube videos

==See also==
* [[Managing repositories]]
* [[Repositories FAQ]]
* [https://www.rjerz.com/professional/work/Presentations/MoodleMoot2018/Personal_Repository/Personal_Repositories.html Managing a personal repository] - keep all your files in your PC, upload them to the cloud and use them in Moodle.
* [http://www.youtube.com/watch?v=zdrdyev82bU Repositories in Moodle 2.0 video]
* [http://www.somerandomthoughts.com/blog/whitepaper-moodle-2-repositories/ Whitepaper – Moodle 2 Repositories] by Gavin Henrick
* [http://www.moodlerooms.com/resources/blog/five-tips-using-new-file-repository-system-moodle Five Tips for Using the New File Repository System in Moodle] by Marcelo Mendes
* [https://moodledev.io/docs/apis/plugintypes/repository dev:Repository plugins] developer documentation
* [http://moodle.org/plugins/browse.php?list=category&id=25 Moodle Repository Plugins database]
* [http://moodle.org/mod/forum/view.php?id=1807 Moodle Repositories discussion forum]
[[Category:Repositories]]
[[es:Repositorios]]
[[eu:Biltegiak]]
[[de:Repositories]]
[[fr:Dépôts]]
[[ja:リポジトリ]]

File handling

2024-08-01T14:20:34Z

Tsala: redirect

#redirect [[Working with files]]

Talk:File handling

2024-08-01T14:19:43Z

Tsala: reply

==Purging pages==
At what point can a page like this be purged from the documentation? It doesn't seem like this page is worth improving anymore.
--[[User:Tim Bahula 2|Tim Bahula 2]] ([[User talk:Tim Bahula 2|talk]]) 15:33, 9 June 2022 (UTC)

: I agree with you Tim. I'm going to redirect the page to 'Working with files', as Mary suggested long ago. --[[User:Helen Foster|Helen Foster]] ([[User talk:Helen Foster|talk]]) 14:19, 1 August 2024 (UTC)
==Two similar pages==
I am looking at pages needing improvement and I see that this page compares and contrasts the "old" way with the new way - but so does [[Course files]] If it is important to have a page for those used to files in 1.9 , which one should we enhance?--[[User:Mary Cooch|Mary Cooch]] 20:32, 28 March 2012 (WST)
==More thoughts on file handling==
Actually, thinking more I think this [[File handling]] page should be redirecting to [[Working with files]] and only contain Moodle 2 references. And I think that [[Course files]] should be added as a link to the Working with files page so that those used to the old way can be pointed in the right direction. Any thoughts? --[[User:Mary Cooch|Mary Cooch]] 17:14, 29 March 2012 (WST)

Capabilities/repository/coursefiles:view

2024-08-01T14:17:24Z

Tsala:

{{Capabilities}}
* This capability, together with the [[Capabilities/moodle/course:managefiles|manage files capability]], allows a user to access the [[Legacy course files]] area
* This capability is allowed for the default roles of manager, course creator, teacher and non-editing teacher

Note: Both repository/coursefiles:view and moodle/course:managefiles should be allowed for the legacy course files area to be listed in the file picker.

[[Category:Capabilities|Repository]]
[[Category:Repositories]]

Template:Repositories

2024-08-01T14:15:15Z

Tsala:

<div class="navtrail">[[Main page]] ► [[Managing content]] ► [[Repositories]] ► [[{{PAGENAME}}]]</div>
<div class="sideblock right" style="width: 12em;">
<div class="header">[[Repositories]]</div>
<div class="content">
* [[Managing repositories]]
* [[Upload a file repository|Upload a file]]
* [[Server files repository|Server files]]
* [[Recent files repository|Recent files]]
* [[Private files]]
* [[Content bank repository|Content bank]]
* [[Google Drive repository|Google Drive]]
* [[Flickr public repository|Flickr public]]
* [[Flickr repository|Flickr]]
* [[URL downloader repository|URL downloader]]
* [[Wikimedia repository|Wikimedia]]
* [[Amazon S3 repository|Amazon S3]]
* [[Box repository|Box]]
* [[Dropbox repository|Dropbox]]
* [[File_system_repository|File system]]
* [[Merlot.org repository|Merlot.org]]
* [[Nextcloud repository|Nextcloud]]
* [[OneDrive repository|OneDrive]]
* [[EQUELLA repository|EQUELLA]]
* [[WebDAV repository|WebDAV]]
* [[YouTube videos repository|YouTube videos]]
* [[Embedded_files_repository|Embedded files]]
* [[Repositories FAQ]]
</div>
</div>

<includeonly>[[Category:Repositories]]
[[Category:Site administration]]</includeonly>
<noinclude>This template will categorize articles that include it into [[:Category:Repositories]] and [[:Category:Site administration]].</noinclude>

Download course content

2024-07-31T18:28:35Z

Tsala: /* For students */

{{Template:Managing content}}
==Download course content==
Specific course items, currently content from the File, Folder, Page and Text and media area can be downloaded if enabled site wide and in individual courses.
Note: This feature was made possible with funding from the Moodle Users Association.

[[File:DownloadCourseContent4.png]]

==For students==
*''If the feature is made available by the administrator and enabled in a course by the teacher'', then students and other users with the [[Capabilities/moodle/course:downloadcoursecontent|capability to download course content]] will see the option 'Download course content' in the More menu.
* Clicking the button will display a pop-up and link to a zipped file.

==For teachers==
*''If the features is made available by the administrator'', then course teachers see an option Enable download course content in the course settings.
*They can then choose Yes to make content downloadable, or No if they prefer not to.
==For administrators==
*Download course content can be made available from Site administration > Courses > Download course content.
*Here, the admin can also specify the maximum size of files which may be downloaded.
*Optionally, from Site administration > Courses > Course default settings, the admin can make the feature enabled by default in courses.

==Capabilities==
* [[Capabilities/moodle/course:configuredownloadcontent|Configure download course content]] - allowed for the default roles of manager and teacher.
* [[Capabilities/moodle/course:downloadcoursecontent|Download course content]] - allowed for the default roles of manager, teacher, non-editing teacher and student.

[[es:Descargar contenido del curso]]
[[de:Kursinhalt herunterladen]]
[[fr:Télécharger les contenus du cours]]

Block settings

2024-07-31T10:56:44Z

Tsala: Text replacement - "Remote RSS feeds" to "RSS feeds"

{{Blocks}}
==Adding a block to a page==

Blocks can be added to a page by turning editing on then using the 'Add a block' drop-down menu.

Please see [[Blocks]] for a list of all the blocks in a standard Moodle install. Your site may have added contributed blocks and or your site administrator has disabled specific blocks on your site.

Note: The ability to add a particular block to a page is controlled by an ''addinstance'' capability (e.g. [[Capabilities/block/comments:addinstance|block/comments:addinstance]]), which is allowed for the default role of teacher.

==Block actions==

After adding a block, click the edit icon in the block header to configure it.
{|
| [[File:block actions.png|thumb|Block actions]]
|}

===Block settings===

Certain blocks, such as the HTML block, allow a block title and more to be set.

===Where this block appears===

Depending upon the context and user permissions, this area determines where this block will appear. See this forum post [https://moodle.org/mod/forum/discuss.php?d=270526#p1166400 explaining block contexts] for more information.
*Original block location: provides information about where the block was initially created.
*Display on page types: allows the user to set the context that the block can appear in. These options will vary depending upon the permissions of the user. For example, a site administrator might see a setting that will allow the block to appear on Any page, or any type of course main page, while a teacher may only see the option to place it on every page in the course.
*Default region: Usually a right column or left column option
*Default weight: Where in the column do you want it to appear if there are other blocks in that column. -10 will put it at the top, 10 will put it at the bottom. A zero is neutral.
[[File: Block configuration where appears.png]]

===On this page===
*Visible - Yes or No.
*Region - Here you can override the column preference on this page.
*Weight - Here you can override the default setting on this page.

=='Sticky blocks'==
The term 'sticky' block was used in older versions of Moodle to mean blocks which the admin added either site-wide or to the [[Dashboard]] and which could not be deleted by regular users. Although the term is no longer used, it is still possible to make blocks 'sticky' and in a wider variety of locations.

If an admin deletes a "sticky" block in a course, they receive a warning of the site-wide consequences of this action before it is deleted.

Here are a few examples:

===Making a block sticky throughout the whole site===
The Moodle administrator might wish for example to display support contact details site-wide using an [[HTML block]] called 'Helpdesk':

#As an administrator, turn on the editing on the front page and add the block you wish to make sticky to the front page.
#For ''Where this block appears > Page contexts'', choose 'Display throughout the entire site'.
#Decide other settings according to your preference and save.
#The block will now appear on all pages of your Moodle.
#TIP: if you want the block to appear throughout the site but NOT on the front page, you can hide it from that page (using the settings in the section “On this page”).

{|
| [[File:sitewidestickyblock.png|thumb|Making a block sticky throughout the site]]
|}

===Making a block sticky throughout a course===

A teacher might wish to display a block, such as the comments block, on the course page and all activity pages.

#As a teacher in the course, turn on the editing on the course main page and add the block you wish to make sticky.
#For ''Display on page types'', choose 'Any page'.
#Decide other settings according to your preferences and save.
#The block will now appear on all pages of the course.

===Making a block sticky in a category===
A user with category rights might for instance wish to display a [[RSS feeds block]] in all of the courses within a particular category, such as a Head of Science adding Science news feeds to the Physics, Biology and Chemistry courses.

===Making a block sticky in a resource or an activity===
A teacher might wish to display a block in one particular resource or activity, for example a Head of Faculty might make create a [[Book]] for departmental policies and wish to add the comments block to every chapter/page of a book so colleagues can give quick feedback. (Note that such a comments block would be the ''same'' block on each chapter/page)
#As a teacher in the course, turn on the editing and click into the resource/activity -in this case a Book and add the block.
#For ''Display on page types'', you will see (for example) 'mod-book*'
#Decide other settings according to your preferences and save.
#The block will now appear on all related screens.

{|
|[[File:bookstickyblock.png|thumb|Making a block sticky throughout a book]]
|}

===Adding a block to all user profile pages===
See [[User profiles]].

===Adding a block to the dashboard for all users===
See [[Dashboard]]. Note that such a block would not be truly 'sticky', in that users can customise their dashboard and could, if wished, delete the block.

==Block permissions==

To change role permissions for a block

# Turn editing on in the course
# In the actions menu in the header of the block, click Permissions'.

See [[Blocks FAQ]] for details of how to hide front page blocks from non-logged-in users.

[[de:Blockeinstellungen]]
[[es:Configuraciones de bloque]]
[[fr:Paramètres des blocs]]

Using Database

2024-07-31T10:56:40Z

Tsala: Text replacement - "Remote RSS feeds" to "RSS feeds"

{{Database}}
This page explores ways the [[Database activity]] may be used in your Moodle course.
==Views==
===View list===
The list view shows multiple entries, possibly in a more abbreviated form to ensure all the information fits. You may use the controls at the bottom of the screen to search and sort the contents.
* ''View single'': one item at a time
* ''View list'' : several items at a time (number is user defined)
* ''Add entry'' : add an item to the database
* ''Search'' : search the entries

[[Image:26databaseview.png]]

===Deleting multiple entries===
In List view, a checkbox will appear next to each entry. Select the entries you wish to delete and click the 'Delete selected' button. Alternatively, click the 'Select all' and the 'Delete all' buttons to delete all entries. A warning message will appear asking you to verify what you wish to delete.
==Automatically linking database entries==
If the [[Database auto-linking filter]] is enabled, any entries in a database will be automatically linked to where the concept words and/or phrases appear within the same course. This includes forum postings, internal resources, week summaries etc.

Note: If you do not want particular text to be linked (in a forum posting, say) then you should add <nolink> and </nolink> tags around the text. Alternatively the filter can be disabled for a particular activity.
==Approving and undoing approval of entries==

If, during database set up, 'Approval required' was set to 'Yes' then a teacher can view entries pending approval and click the three dots to the right in order to approve them.
[[File:docsentryapproval.png|600px|center]]

==Importing many entries==
You can import entries via a CSV file if you click the "Import entries" link from the Actions menu when clicking on a Database activity.

[[image:DatabaseExportImport.png|center]]

The easiest way to determine the format of the text file is to manually add an entry to the database and then export it. The resulting export text file may then be edited and used for importing entries.

The expected file format is a plain text file with a list of field names as the first record. The data then follows, one record per line.

The field delimiter defaults to a comma character and the field enclosure is not set by default (field enclosures are characters that surround each field in each record).

Records should be delimited by new lines (usually generated by pressing RETURN or ENTER in your text editor). Tabs can be specified using \t and newlines by \n.

Sample file:
name,height,weight
Kai,180cm,80kg
Kim,170cm,60kg
Koo,190cm,20kg
Note: Certain field types may not be supported.

Do not put spaces after your commas or upload will fail!

After upload page import.php comes back blank if it failed.
If successful you'll read a message like, "1 entries saved".

==Exporting entries==
You can export entries either in CSV (comma separated values) or ODS (OpenOffice Calc) formats by clicking the "Export entries" link from the Actions menu when clicking on the 'Database activity.

[[File:DatabaseExportImport.png|DatabaseExportImport.png]]

When exporting entries, it is possible to include files.

When using the CSV format, the user can select either the comma, semicolon, or tab to separate the fields. The selection of the proper character is important. If users select to use a comma to separate the fields and some of the fields contain data with commas then the number of columns is going to be misaligned and likely cause confusion.

Users can select which fields from the database they wish to have exported. By default, all fields are checked to be included. Choose the fields that you wish to have included in the export.

Once the export type and the fields to be exported have been selected, clicking on the Export entries pushbutton will generate the file. The user will usually have the option of either opening or saving the file.

For information on converting the date export (and import) format, see the discussion [https://moodle.org/mod/forum/discuss.php?d=220505 Standard Database Module - Dates].

==Enabling an RSS feed of recently added entries==
To enable an RSS feed from a database activity, an administrator must first enable RSS feeds for database activities across the whole site as described in [[RSS feeds settings]]. A section called 'RSS' will then appear on the edit settings page of the database activity.
# Edit the database activity settings and set the number of entries in the RSS feed e.g. 5.
# Check that the RSS template includes the required fields.
# Log out and then access the database activity as a guest.
# Copy the 'RSS feed for this activity' link in the administration block.
The RSS feed may then be displayed in an [[RSS feeds block]] or elsewhere.
==Exporting to an external portfolio==
If an external [[Portfolios|portfolio]] such as [[Mahara_portfolio|Mahara]] has been enabled by the administrator then users have the option to export individual entries to that portfolio if the ##export## tag is added to list and/or single templates. From the three dots to the right of their entry in single view, they will see the option Export to portfolio. Clicking there will present them with whichever portfolio export options are available.

[[File:44databaseportfolioexport.png|alt=database portfolio export]]

== Creative uses ==
You could use the database module to:
* allow collaboration on building a collection of web links/books/journal references related to a particular subject
* display student created photos/posters/websites/poems for peer comment and review
* gather comments and votes on a shortlist of potential logos/mascot names/project ideas
* provide a [http://moodle.org/mod/forum/discuss.php?d=52699 student file storage area]
* maintain a log of what was done in a face-to-face class each day, so that absent students can get caught up themselves. [http://moodle.org/mod/forum/discuss.php?d=115047 Example]
*add, track, and award points for CPD (or other external activity). [https://www.youtube.com/watch?v=LocVdShyErU Video demo.] [https://moodle.org/mod/forum/discuss.php?d=457599 Details].

==See also==
*[https://school.moodledemo.net/course/view.php?id=57&section=1 Examples of databases in the School demo site] (available for download)
*[[Glossary module]], which performs a similar though more specialised, text-based role
*Moodle in English [https://school.moodledemo.net/course/view.php?id=57&section=1 Database activity module forum]
*[https://moodle.org/mod/data/view.php?d=54 Moodle.org jobs database] - example of a database activity on Moodle.org.
[[de:Datenbank nutzen]]
[[es:Usando BasedeDatos]]

MoodleDocs - User contributions [en]

MediaWiki:Sitenotice

MediaWiki:Sitenotice

MediaWiki:Sitenotice

MediaWiki:Sitenotice

Ordering question type

File:404orderingquestion.png

MediaWiki:MoodleDocsVersionLinks

Upgrading

Grade category settings

Grade items

MediaWiki:MoodleDocsVersionLinks

Capabilities/moodle/cohort:configurecustomfields

Course meta link

Course backup

Upgrading

error/grades/gradesneedregrading

MediaWiki:MoodleDocsVersionLinks

Site registration

New for teachers

MoodleDocs:Overview

MediaWiki:MoodleDocsVersionLinks

Custom menu items

Theme config

admin/setting/themesettings

ThemeConfig

Manage editors

Text editor settings

label

coursefiles2

files/index

administrator

Notifications

Site home FAQ

Site home

External database enrolment

Access all groups

Automated course backup

Automated course backup

Legacy course files

Course files

Talk:Course files

Table of Contents

Repositories

File handling

Talk:File handling

Capabilities/repository/coursefiles:view

Template:Repositories

Download course content

Block settings

Using Database