MoodleDocs - User contributions [en]

Mobile app

2013-10-02T09:02:33Z

Ghillenb:

{{Mobile}}
<p class="note">'''Mobile app latest''': The ''Moodle Mobile'' app (developed on HTML5 and Phonegap) replaces the old mobile app for iPhone, ''My Moodle''. It requires Moodle 2.4 or above.</p>

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

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

=== Screenshots ===

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

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

=== Translation ===

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

=== Style customization ===

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

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

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

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

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

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

Moodle 2.4 or above is mandatory.

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

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

==Installing the mobile app==

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

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

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

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

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

==Testing the app on a demo site==

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

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

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

==How to report a bug==

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

=== Report a bug by email ===

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

== See also ==

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

[[ja:モバイルアプリ]]
[[de:Mobile App]]

New features

2013-05-18T06:44:45Z

Ghillenb:

{{Main page}}
Moodle 2.5 brings a lot of exciting new features for teachers, students and administrators. This page highlights a few of the most interesting!

Full details of the release, with technical information, can be found in the [https://docs.moodle.org/dev/Moodle_2.5_release_notes Moodle 2.5 Release notes].

(Click any screenshot below to see it enlarged)

==For teachers and students:==

===Badges===
[[Badges]] are a nice way to acknowledge good work, and it's now possible for teachers to award course badges based on a variety of chosen criteria. These badges are fully compatible with [http://openbadges.org/ Mozilla Open Badges].

{|
| [[File:teacherbadgeview.png|thumb|Teacher sets up a badge]]
| [[File:studentbadgeview.png|thumb|Student view of allocated badges]]
| [[File:backpack.png|thumb|Badges from backpack.openbadges.org on student profile]]
|}

This blog post has some interesting reflection on when badges might be most appropriate: [http://alex.halavais.net/ozbadge The Badges of Oz]

===Forms are much shorter===

Moodle has a lot of settings and features, which means some of our forms have been getting rather long. We know this is daunting for new users!

We've made changes so that non-essential settings on forms are collapsed by default, yet you can quickly access them when you need them.

{|
| [[File:shorterforms.png|thumb|Note the "expand all" option and condensed links]]
| [[File:showmoreshowless.png|thumb|"Show more" (and "show less" options]]
|}

The rich text editor is collapsed and can be expanded:

{|
|[[File:collapsedassignment.png|thumb|Formatting options collapsed and box is narrow]]
|[[File:expandedassignment.png|thumb|Formatting options shown and box expanded]]
|}

In a similar space-saver, you can choose whether or not to enable the rich text editor when creating quiz questions:

{|
| [[File:quizform1.png|thumb|Without the editing tools]]
| [[File:quizform2.png|thumb|With the editing tools]]
|}

===Reports moved to the Administration block===

Reports have moved and can now be seen in the newly named ''Administration'' block, (formerly ''Settings''.)

{|
|[[File:reportsinadmin.png|thumb|Administration block with Reports]]
|}
=== Quickly "Jump to.." another section===
If you're using the 'one section per page' setting, you can now move to other sections from a drop down menu:
{|
|[[File:jumpto25.png|thumb|The 'jump to' drop down menu returns]]
|}
===Drag and drop media and text onto the course page===
You can now drag an image or some text onto your course page and choose whether to display it embedded in a label or as a clickable resource. See the [[Label|Label documentation]] for more information.

{|
| [[File:dragdrop1.png|thumb|Drag an image onto your course page]]
|[[File:dragdrop2.png|thumb|Choose "add image.."]]
|[[File:dragdrop3.png|thumb|And here it is!]]
|}

{|
|[[File:textdragdrop1.png|thumb|Text selected from a Word document is dragged over]]
|[[File:textdragdrop2.png|thumb|Choose "add a label" (or page if you prefer)]]
|[[File:textdragdrop3.png|thumb|And here it is!]]
|}

===Folders can be displayed inline on a course page===

You can now choose whether to have a [[Folder resource|folder]] show its contents in a separate screen, as previously, or to have it display them inline with any subfolders expanded:

{|
| [[File:folder1.png|thumb|Typical folder display before 2.5]]
| [[File:folder2.png|thumb|Folder displayed inline]]
| [[File:folder3.png|thumb|Folder displayed inline with subfolders expanded]]
|}

===Assignment enhancements===
Along with neater options for choosing submission and feedback types, resubmitting options are much improved. See [[Assignment settings]] for more information.

{|
| [[File:assignmentandfeedbackcondensed.png|thumb|Neater assignment set up screen]]
| [[File:attemptsreopened.png|thumb|New settings for resubmissions]]
|}

===Word count in forum posts===
A new setting in forums will display the number of words in a post:

{|
| [[File:bonding.png|thumb|Note word count bottom left]]
|
|}

===Templates for Essay question types===
When using the Essay question type in a quiz, you can now set a template which appears in the students' text editor for scaffolding their response:

{|
| [[File:templatebox.png|thumb|Response template in question set up screen]]
| [[File:quiztemplate.png|thumb|What the student sees]]
|
|}

===Glossary block enhancements===

You can now use a global glossary in the random glossary block, and you can display the entries in alphabetical order:
{|
| [[File:glossaryalphabetical.png|thumb|Entries will display in alphabetical order]]
|}

===Search the list of enrolled users===
A new [[Enrolled users]] search box makes finding users in very large courses much easier:

{|
| [[File:Searchenrolledusers.png|thumb|A search facility allows teachers to search for specific users.]]
|}

==For administrators:==

===New themes suited to all screen sizes===

Many of your favourite sites around the web these days use Bootstrap as a base framework and now Moodle does too! We have a new 'base' theme called "'''Bootstrapbase'''" that implements the basics, and a new usable theme called ''''''Clean'''''' which extends it with some simple configuration options and also functions as a good template example for developing your own Bootstrap-based themes. It also (along with ''Afterburner'') allows you to upload a logo directly from the file picker.

The Bootstrap framework allows us to responsively reformat the layout according to the screensize of the device used - on phone or tablet screens blocks move to the bottom, freeing up space for the main content at the top. In the future we hope everyone will want to migrate their Moodle themes to be Bootstrap-based.

{|
| [[File:Bootrap2.png|thumb|Clean theme on standard screen]]
| [[File:Bootstrap1.png|thumb|Clean theme on smaller screen; note position of Navigation block]]
| [[File:filepickerlogo.png|thumb|Add your logo from the file picker in Clean theme]]
|}

===Install add-ons from inside Moodle===
It's now possible to [[Installing add-ons|install add-ons]] from within Moodle, rather than accessing folders on the server; useful for those admins who do not have FTP access. Add-ons can be uploaded and installed from a zip file or located and installed from the [https://moodle.org/plugins Moodle plugins directory]:

{|
| [[File:Selection_011.png|thumb|Add-on install tool]]
| [[File:AddonValidation.png|thumb|Add-on passes validation; ready to go]]
|}

==See also==

* [[:Category:New features|Category:New features]] - list of pages documenting new features in Moodle 2.5

[[es:Nuevas características de Moodle 2.5]]
[[de:Neue Funktionalitäten]]

Badges settings

2013-05-16T10:30:49Z

Ghillenb:

{{Badges}}

==Individual user settings==
*A user can [[Managing badges|manage badges]] from ''Navigation>My profile>My badges''.
*A user can view available course badges from ''Navigation>Current course>Badges''.

{|
|[[File:coursebadgenav1.png|thumb|Viewing course badges]]
|}

==Course administration settings==
*A teacher can add and manage badges in their course if the administrator has enabled course badges in ''Administration>Site administration>Badges settings.''
*They will see a link to badges in ''Administration>Course administration>Badges.'' where badges may be [[Managing badges| managed]] and added.

==Site administration settings==
*Badges are enabled by default and can be disbled in ''Administration>Site administration>Advanced features.'' (Note that disabling the feature once badges have been awarded does not prevent those badges being verifed by external backpacks.)
*The site settings for badges are located in ''Administration>Site administration>Badges>Badges settings''
===Default badge issuer===
Here you set the name and email address of the issuer. The name will appear where the badges are displayed and might typically be the name of the organisation.
===Salt for hashing recipient's email address===
If a hash is used (numbers and letters only) then backpack services can confirm a badge earner without exposing their email address.
===Enable connection to external backpacks===
This should be enabled in order to connect to, for example [http://openbadges.org/ Mozilla Open Badges]. Note that this will not work on a Moodle hosted locally/offline.
===Enable course badges===
Ticking this box will allow teachers to add and manage badges in their courses.

==Badges capabilities==
There are a number of capabilities associated with badges:

*[[Capabilities/block/badges:addinstance|Add a new My latest badges block]]
*[[Capabilities/block/badges:myaddinstance|Add a new My latest badges block to My home]]
*[[Capabilities/moodle/badges:awardbadge| Award a badge]]
*[[Capabilities/moodle/badges:configurecriteria|Set up criteria for awarding a badge]]
*[[Capabilities/moodle/badges:configuredetails|Set up and edit badge details]]
*[[Capabilities/moodle/badges:configuremessages|Configure badges messages]]
*[[Capabilities/moodle/badges:createbadge| Create or duplicate badges]]
*[[Capabilities/moodle/badges:deletebadge| Delete badges]]
*[[Capabilities/moodle/badges:earnbadge|Earn badges]]
*[[Capabilities/moodle/badges:manageglobalsettings | Manage badges site administration settings]]
*[[Capabilities/moodle/badges:manageownbadges|View and manage your own earned badges]]
*[[Capabilities/moodle/badges:viewawarded|View users who earned a specific badge without being able to award a badge]]
*[[Capabilities/moodle/badges:viewbadges |View badges without earning them]]
*[[Capabilities/moodle/badges:viewotherbadges|View public badges in other users' profiles]]

[[de:Auszeichnungen konfigurieren]]

Managing badges

2013-05-16T10:30:25Z

Ghillenb:

{{Badges}}

Badges may be managed at the course or site level. (Note that teachers in a course cannot by default access site badges unless they have been given a system role with badge managing capabilities) For information on adding course or site badges, see [[Using badges]]. Individual users can manage their badges from their profile.

==Managing course badges==

*If course badges have been enabled in ''Administration>Site administration>Badges>Badges settings'', then a teacher will see a link ''Administration>Course administration>Badges>Managing badges''. This will show a list of badges created and available for allocation, along with actions which may be performed on them:

[[File:Managingcoursebadges.png]]

**Badge status: Badges may be made available or not by enabling or disabling with the "eye" icon or enable/disable button
**Criteria : This shows how the badge is awarded
**Recipients: This shows the number of users awarded the badge
**Actions: The following actions are available

[[File:Badge actions.png]]

'''Note''': Availability of enable and disable access actions depends on the current status of a badge (e.g. if a badge is available to users, "disable access" icon will be shown).

Before a badge has been issued to at least one user, all its details and settings can be edited by clicking the "Edit badge" action icon.

Clicking on the name of a badge takes you to the screen where you can manage details of that particular badge. The following tabs are available:
===Overview===
This screen provides an overview of the badge details:

===Edit details===
If you wish to change the details of a badge once you have set it up, you must first click to "disable access". Once you have edited the details, you must then click to "enable access" again.

===Criteria===
Here you can see the criteria set when [[Using badges|adding the badge]]

===Message===

This setting allows you to edit the message which goes to a badge earner. Among additional options here are "Attach badge to message" which allows adding an image file to an email and "Notify badge creator" selector which allows to set frequency of notifications sent to badge creator when this badge is issued to users.

===Recipients===
This tab displays a list of users who have already earned the badge
{|
|[[File:coursebadgemanagement.png|thumb|Course badge overview]]
|[[File:disableaccess.png|thumb|Disabling access in order to edit details]]
|[[File:Badge_message.png|thumb|Adding a message]]
|[[File:Badge_recipients.png|thumb|Badge recipients]]
|}

==Managing site badges==

*Badges should be enabled by default in ''Administration>Site administration>Advanced features'' and can be managed from ''Administration>Site administration>Badges>Manage badges.'' (For information on adding site badges see [[Using badges]]

*All existing badges are displayed in a table showing current badge image, name, status, criteria, how many users have already earned this badge and a set of available actions.

*Other settings are the same as for course badges.Badges that have manual award among their criteria can be issued by one user to another. Users who issue a badge must have "moodle/badges:awardbadge" capability. Site administrators can choose their role when issuing a badge.
{|
|[[File:Managing badges.png|thumb|The Manage badges screen for site admins]]
|[[File:Badge_recipients2.png|thumb|Site administrators choose a role to award a badge]]
|}

==Individual user badge management==
*Users may manage their site and external badges by clicking on ''Navigation>My profile>My badges'' From here, they can view, search for and download badges.
{|
|[[File:13_mybadges.png|thumb|Example of a My badges screen]]
|}
*This then displays "badges" in the Administration block.
===Preferences===
Here users can decide whether to automatically display all badges earned. (Badges can be individually displayed or hidden from ''Navigation>My profile>My badges'')
===Backpack settings===
====Backpack connection====
If the email address a user has for Moodle is the same as their [http://backpack.openbadges.org Open Badges] email address, then they will be automatically connected here and may choose to disconnnect if they wish.
If the email address a user has for Moodle is not the same, then they can add the email address which will connect them to their [http://backpack.openbadges.org backpack].
They can then choose to "push" to their backpack badges which they have earned on Moodle.The badge must then be added to a public collection for it to be visble on their Moodle profile.

====Badge import settings====
Here, a user is prompted to choose which public collections to import and display.

[[de:Auszeichnungen verwalten]]

Badges

2013-05-15T08:47:30Z

Ghillenb:

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

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

[[File:BadgesIntro2.png]]

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

[[Category:Badges]]

[[de:Auszeichnungen]]

Google Drive repository

2013-04-19T12:47:54Z

Ghillenb:

{{Repositories}}
Google Drive can serve both as a repository from which users can "pull" files they need for their course and also a [[Google Docs portfolio|portfolio]] into which they can "push" files they want to keep. Both options need to be enabled by the administrator before they are available for teachers and students.

'''New in 2.5''': The Google Drive repository was called 'Google Docs' repository in earlier versions of Moodle.

==Enabling the Google Drive repository==

Note: In order to use either the Google Drive or Picasa repositories (also the Google Docs or Picasa portfolios) an administrator must register their Moodle site with Google, as described in [[Google OAuth 2.0 setup]], and obtain a client ID and secret. The client ID and secret can then be used to configure all Google Docs and Picasa plugins.

'''New in 2.5''': Upgraded sites for which an administrator has previously registered the Moodle site with Google now also need to enable the Drive API in the Google APIs Console, as described in [[Google OAuth 2.0 setup]].

# Log in as an administrator and go to ''Settings > Site administration > Plugins > Repositories > Manage Repositories''
# Activate the Google Docs repository by selecting 'Enable and visible' in the dropdown menu
# Configure the Google Docs repository by entering the client ID and secret
# Save changes

==Getting ("pulling") your files from Google Drive==

* From the file picker, click on the Google Drive link and a prompt to log in will appear:

* If it is your first time, the click the "Allow access" button to log in

{|
| [[File:newgoogledocs.png|thumb|Log into your account]]
| [[File:newgooglepermission.png|thumb|Allow access]]

|}

* Your files will display for you to choose from.
*You can view them in three ways by clicking one of the options at the top right.

{|
| [[File:googledocsrepothumb.png|thumb|Icon view]]
| [[File:googledocstableview.png|thumb|Table view]]
| [[File:googledocslistview.png|thumb|List view]]
|}

{{New features}}In Moodle 2.5 onwards, folders as well as files are shown in the Google Drive repository.

==Repository capabilities==

There is just one capability, [[Capabilities/repository/googledocs:view|View Google Drive repository]], which is allowed for the default authenticated user role.

[[Category:Site administration]]

[[de:Google Drive Repository]]

Course list

2013-03-13T11:59:14Z

Ghillenb:

{{Site appearance}}
The order in which courses are listed on the front page can be set by an administrator in ''Settings > Site administration > Courses > Add/edit courses''.

An administrator can change the following course settings in ''Settings > Site administration > Appearance > Courses''.

===Course contacts===

Users with the selected role(s) e.g. teachers are listed in the course description.

[[File:Course list.png]]

By default, users with the role of teacher in a course are listed in the course description for that course. If a course has several teachers, the course description can become rather long. In this case, you can create a role e.g. head of subject with no capabilities set and assign it to selected users in addition to their teacher role. If you then select only the head of subject role in the course managers setting, the course description will be shorter.

===Display extended course names===

By default, only course full names are displayed in the list of courses. If you check this box, then the course short name will also be displayed. Enabling this will also allow you to edit the wording using [[Language customization]]. See the forum discussion [https://moodle.org/mod/forum/discuss.php?d=223924 Course Extended Name Display Language Modification for further details.

===Courses per page===
Here you can select how many courses you wish to be displayed per page in the course listing

===Courses with summaries limit===
{{New features}}
When courses are listed, they show the full course summary. Displaying the full summary is very useful, but can make pages very long. If you have a great number of courses, it might be better to display the clickable icon taking you to more information (ie, the full summary) Here you can decide the number of courses that will display the full summary before Moodle reverts to the "more information" icon.

==See also==

* [[Courses]]

[[Category:Course]]
[[de:Kursliste]]

Conditional user fields

2012-12-17T07:31:55Z

Ghillenb:

{{Conditional activities}}{{New features}}
This page explains how to restrict an activity, resource or course section via user fields and/or custom profile fields.

==Instructions==

# Conditional access must be enabled (see [[Conditional activities]] for instructions on how to enable this for your site).
# When adding or editing an activity, resource or course section scroll to the user fields in the 'Restrict Access' section.
# Choose which fields you want to restrict by (adding more if needed), select the restriction you want to put in place and then enter a value.
# Save the settings.

==Example==

This is an example of the interface in Moodle when adding an activity to a course with the conditional functionality enabled

[[File:conditional_user_setup.jpg]]

This is how it will appear to users who fail to meet the restrictions set in place.

[[File:conditional_user_courseview.jpg]]

==User fields==

You can restrict by using one of the user fields that are located in the Moodle user table. Not all the user fields are included, as not all of them would make sense in this context. The ones included are listed below.

* AIM ID - This is the value in the 'aim' column
* Address - This is the value in the 'address' column
* City/town - This is the value in the 'city' column
* Country - This is the value in the 'country' column
* Department - This is the value in the 'department' column
* Email Address - This is the value in the 'email' column
* First name - This is the value in the 'firstname' column
* ICQ number - This is the value in the 'icq' column
* ID number - This is the value in the 'idnumber' column
* Institution - This is the value in the 'institution' column
* Interests - This is the value in the 'interests' column
* MSN ID - This is the value in the 'msn' column
* Mobile phone - This is the value in the 'phone2' column
* Phone - This is the value in the 'phone1' column
* Skype ID - This is the value in the 'skype' column
* Surname - This is the value in the 'lastname' column
* Web page - This is the value in the 'url' column
* Yahoo ID - This is the value in the 'yahoo' column

==Custom profile fields==

These are all the custom profile fields that have been created on the Moodle site. See [[User profile fields]].

==Operators==

The operators define the relationship between the field chosen and the value entered. For example, when the user's email must contain @school.com, the field chosen is 'Email address', the operator is 'contains' and the value is '@school.com'.

;Contains
:This operator restricts access to those whose chosen field contains the value provided.

;Does not contain
:This operator restricts access to those whose chosen field does not contain the value provided.

;Is Equal To
:This operator restricts access to those whos chosen field equals the value provided.

;Starts With
:This operator restricts access to the activity to those whos chosen field starts with the value provided.

;Ends With
:This operator restricts access to the activity to those whos chosen field ends with the value provided.

;Is Empty
:This operator restricts access to the activity to those whos chosen field is empty. Note, if any value is provided in this case, it is ignored.

[[de:Bedingte Nutzerfelder]]

Available update notifications

2012-12-05T10:16:43Z

Ghillenb:

{{Security}}
==Update notifications==
[[File:Pluginsoverview.png|thumb|left|Checking for available updates via the plugins overview page]]An administrator can configure update notifications for both Moodle core code and any contributed plugins installed on the site (from the [http://moodle.org/plugins plugins directory]) in ''Settings > Site Administration > Server > Update notifications''.

If the automatic check for available updates is enabled and there is a new update available, a notification will be sent to all site admins via email and/or popup message (according to the admin's messaging preferences in their profile settings).

{{New features}}In Moodle 2.4 onwards, updates deployment i.e. the option to update installed plugins from within Moodle may be enabled by ticking the updateautodeploy checkbox. When updates are available, ''Install this update'' buttons are shown on the [[Plugins overview]] page (''Settings > Site Administration > Plugins > Plugins overview''). See [[Automatic updates deployment]] for more details.

An administrator can specify the required code maturity (stable, alpha, beta or release candidate) for update notifications, also whether notifications of new builds (normally released each week) are sent.

[[File:updates check button.png|thumb|Checking for available updates via the notifications page]]An admin can also check for available updates for contributed plugins installed on the site using the 'Check for available updates' button in ''Settings > Site Administration > Plugins > [[Installing plugins|Plugins overview]]''. Any updates available are highlighted, with further information and a download link in the notes column opposite the plugin.

Available updates for core code can also be checked via ''Settings > Site administration > Notifications''.

== How it works ==

# The information about available updates are available as a web service at download.moodle.org
# When ''Check for updates'' button is pressed (or daily via cron), your Moodle fetches information about available updates from the web service and stores it locally.
# The list of installed plugins is compared with the list of available updates. If a newer version of Moodle or a plugin is available, the Moodle informs site administrators.

When calling the web service, your site must provide its own version and the list of all installed add-ons. No sensitive data (like the location of your site, any user data etc) are submitted.

== Disabling update notifications ==

In a few circumstances (such as completely managed servers, which may have a lot of local modifications) it is desirable to not have the check for updates active. The feature may be disabled completely by adding the following code to the [[Configuration file|config.php file]]:

$CFG->disableupdatenotifications = true;

== Errors and exceptions ==

When experiencing an error, please turn debugging on. The debug info will contain additional information about the reason of the error.

=== Unable to fetch available updates data - unexpected cURL error ===

See the debug info for the actual cURL error number and the error text.

; cURL error 7 couldn't connect to host : Make sure that the site http://download.moodle.org is up and running at the moment. If it is down, your site can't call the web service to fetch the available updates info. Wait for the download.moodle.org site is up again and try to re-check.
; cURL error 60 (SSL certificate problem) : This suggests problems with the validation of the SSL certificate of the remote (moodle.org) site. See [[SSL certificate for moodle.org]] for more info.

This error may also raise if your Moodle is configured to run behind a mis-configured proxy server.

=== Unable to fetch available updates data - unexpected HTTP response code ===

See the debug info for the actual HTTP response code. On success, the HTTP response code is 200. All other response codes throw this error.

=== Unexpected version of the response format ===

This could happen if you check for updates during the major Moodle upgrade. Please try to re-check for available updates once you finish upgrading your Moodle.

[[de:Aktualisierungsmitteilung]]

Caching

2012-12-05T08:47:30Z

Ghillenb:

{{Performance}}{{New features}}
A cache is a collection of data that is kept on hand and made readily available in order to avoid costly fetching and moulding upon every request.

Moodle 2.4 saw the implementation of MUC Stage 1: Implement some core caching architecture.

Two links, that might be useful to anyone considering testing the new features on their own servers:

* [http://www.iteachwithmoodle.com/2012/10/12/moodle-performance-testing-how-much-more-horsepower-do-each-new-versions-of-moodle-require/ Moodle performance testing: how much more horsepower do each new versions of Moodle require?]
* [http://www.iteachwithmoodle.com/2012/10/11/how-to-stress-test-your-moodle-server-using-loadstorm/ How to load test your Moodle server using Loadstorm]

==See also==

* Using Moodle [https://moodle.org/mod/forum/discuss.php?d=217195 MUC is here, now what?] forum discussion

Developer documentation:
* [[:dev:The Moodle Universal Cache (MUC)]]
* [[:dev:Cache API]]
* [[:dev:Cache API - Quick reference]]

{{stub}}
[[de:Caching]]

Upgrade overview

2012-12-05T08:46:15Z

Ghillenb:

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

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

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

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

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

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

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

==Step 3: Replace your Moodle code==

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

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

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

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

==How did you go?==

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

==See also==

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

[[Category:Installation]]

[[de:Aktualisierung in Kürze]]

Automatic updates deployment

2012-12-05T08:34:19Z

Ghillenb:

{{Installing Moodle}}
{{New features}}
==Enabling updates deployment==

[[File:plugins overview.png|thumb|left|Plugins overview highlighting available update with install button]]In Moodle 2.4 onwards, an administrator can enable updates deployment in ''Settings > Site Administration > Server > Update notifications''. Then when updates are available, 'Install this update' buttons are shown on Plugins overview and Plugins check pages.

This functionality requires that [[Available update notifications]] are enabled at the site.

== How it works ==

As a part of the information about available updates for the site, URL of the ZIP package with the new version of an installed plugin is returned. When ''Install this update'' button is pressed and the the deployment is confirmed at the next page, a standalone utility called ''mdeploy.php'' is executed.

# The mdeploy utility authorizes the request to make sure you are coming ''exactly'' from the confirmation page displayed in the previous step.
# The ZIP package with the new version is fetched from the [https://moodle.org/plugins Moodle plugins directory].
# A simple integrity check is performed to make sure the ZIP was downloaded correctly.
# The current version of the plugin code is archived into a directory at ''moodledata/mdeploy/archive/'' so you have a backup (just in case you had some local tweaks in the code, for example).
# The current directory with the plugin is removed and replaced with the content of the downloaded ZIP.
# Your browser is redirected to the page where the normal upgrade procedure happens.

At this moment, you can deploy another available update (if there is such) or perform the upgrade procedure as if you uploaded the ZIP contents to your site manually.

== Disabling updates deployment ==

In a few circumstances (such as completely managed servers, which may have a lot of local modifications, or sites that have their own solution for updates deployment - for example via [[Git for Administrators|Git checkouts]]) it is desirable to not to allow automatic updates deployment. The feature may be disabled completely by adding the following code to the [[Configuration file|config.php file]]:

$CFG->disableupdateautodeploy = true;

== Missing install button ==

If the updates deployment feature is not enabled (or if it was disabled at the config.php file), no button to install the update is displayed. If the feature is enabled, the page displaying the list of available updates performs some pre-checks to make sure the deployment will work. If a pre-check fails, a short information with a help pop-up is displayed.

=== Plugin files not writable ===

During the deployment, Moodle will replace the whole folder with the plugin code with a new version. The web server process has to have write access to the folder and all its contents. There are several ways how to achieve this, depending on your web server setup and personal preferences. The exact location of the plugin folder depends on the type of the plugin. For a full list of locations see the Moodle path on https://docs.moodle.org/dev/Plugins

Example: Let us assume your web server is an Apache running at a Linux server as the user ''www-data''. Your Moodle is installed at ''/var/www/vhosts/moodle/htdocs''. You want to give it write access to the folder with your Stamp collection activity module:

# cd /var/www/vhosts/moodle/htdocs
# cd mod
# chown -R www-data stampcoll
# chmod -R u+w stampcoll

See also more about [[Installing plugins]].

=== Can not download the package ===

Make sure that the site http://moodle.org/plugins is up and running at the moment. If it is down, your site can't fetch the ZIP packages from it. Wait for the moodle.org site is up again and try to repeat the deployment procedure.

There can also be a problem with the validation of the SSL certificate of the moodle.org site. See [[SSL certificate for moodle.org]] for more info.

== Errors and exceptions ==

[[File:mdeploy-exception.png|thumb|left|Error screen during the plugin deployment]]If anything goes wrong during the deployment, please read the error page carefully and copy the error message together with the debugging information for later reference. Also, check the mdeploy.log file. The mdeploy utility logs all the steps into this file located at ''moodledata/mdeploy/mdeploy.log''. The log file usually contains additional details and debugging information describing the reason of the failure.

When you navigate back from the error screen, always remember to go back up to the screen with the list of available plugins (where you clicked the ''Install this update'' button originally). Just going back to the previous confirmation screen or even reloading the current page will not work as the request would not be authorized any more. Doing so leads to the ''unauthorized_access_exception'' with the message ''Unable to read the passphrase file.''

The following section describes some errors that may raise and how to deal with them.<br clear="all" />

=== Unable to download the package (download_file_exception) ===

Check the bottom of the mdeploy.log file. It will probably contain a line starting with "cURL error" followed by the error number and the cURL error description.

==== cURL error 7 couldn't connect to host ====

Make sure that the site http://moodle.org/plugins is up and running at the moment. If it is down, your site can't fetch the ZIP packages from it. Wait for the moodle.org site is up again and try to repeat the deployment procedure.

==== cURL error 60 SSL certificate problem ====

This suggests problems with the validation of the SSL certificate of the remote (moodle.org) site when fetching the ZIP package. See [[SSL certificate for moodle.org]] for more info.

[[de:Automatische Aktualisierungen]]

Capabilities/moodle/course:movesections

2012-11-30T09:54:03Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to move a section on the [[Course homepage]]
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Course]]
[[Category:Course]]

[[de:Capabilities/moodle/course:movesections]]

Block layout

2012-11-30T09:36:23Z

Ghillenb:

{{Blocks}}
==Default block layout for new courses==

To amend the default block layout for new courses, one or more of the following lines (omitting the forward slashes) from ''config-dist.php'' may be added to ''[[Configuration_file|config.php]]'', amending the block names as required.

// These variables define DEFAULT block variables for new courses
// If this one is set it overrides all others and is the only one used.
// $CFG->defaultblocks_override = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
//
// These variables define the specific settings for defined course formats.
// They override any settings defined in the formats own config file.
// $CFG->defaultblocks_site = 'site_main_menu,admin,course_list:course_summary,calendar_month';
// $CFG->defaultblocks_social = 'participants,search_forums,calendar_month,calendar_upcoming,social_activities,recent_activity,admin,course_list';
// $CFG->defaultblocks_topics = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
// $CFG->defaultblocks_weeks = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';
// These blocks are used when no other default setting is found.
// $CFG->defaultblocks = 'participants,activity_modules,search_forums,admin,course_list:news_items,calendar_upcoming,recent_activity';</pre>

For example, to set the default block layout for topics format courses to People, Tags and Administration on the left, and Messages, Online users and Recent activity on the right, simply add the following line to your ''config.php'' file:

$CFG->defaultblocks_topics = 'participants,tags,admin:messages,online_users,recent_activity';

Note how the colon is used to separate those blocks appearing on the left, from those appearing on the right.

==Resetting the block layout for existing courses==

The block layout for existing courses may be reset by copying the following script into a text file, saving it as ''resetblocks.php'', copying it into the Moodle root directory, then visiting <code><nowiki>http://yourmoodlesite.org/resetblocks.php</nowiki></code>.

'''Warning''': This script may change the layout of your course pages and also remove blocks from those pages if they have not been specified in the config.php line. Check which of your courses has blocks which are not in the config.php line and be prepared to spend time adding blocks to your course pages again. ''Please note that a database backup is recommended before using the script''.

<?php
//moodle 2.x
require_once('config.php');
require_once($CFG->libdir.'/blocklib.php');
$courses = get_courses();//can be feed categoryid to just effect one category
foreach($courses as $course) {
$context = get_context_instance(CONTEXT_COURSE,$course->id);
blocks_delete_all_for_context($context->id);
blocks_add_default_course_blocks($course);
}
?>

==See also==

Using Moodle [http://moodle.org/mod/forum/discuss.php?d=98808 Default Block Layout for moodle 1.9] forum discussion

[[ja:ブロックレイアウト]]

Automated course backup

2012-11-29T09:03:31Z

Ghillenb:

{{Backup}}
A site administrator can configure a schedule for automated course backups in ''Settings > Site administration > > Courses > Backups > Automated backup setup''.

Automated course backups runs the same functions as individual [[Course backup|course backups]]. 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 ''Settings > 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/ if the path is not recognized a red X is shown after saving, otherwise a green check.
#Make your choices of which courses to skip. See [[#Skipping backup of certain courses]]
#Click the "Save changes" button.

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.

Note: Automated course backups automatically skip courses which are unavailable to students.

===Skipping backup of certain courses===
{{New features}}

The automated backup setup screen offers the possiblity to select whether or not you wish to skip backup of:
#courses which are hidden;
#courses which haven't been modified for a specified time. The default is 30 days but you can specify any time between one day and one year;
#courses which have not been modified since the previous backup.

===Use course names for your backups===
By default, the backups will be named according to the course ID, which is not always easily recognisable. Check the box ''Use course name in backup filename'' in ''Settings>Site Administration>Courses>Backups>Automated backup setup'' to have them saved with the course shortname instead.

==Backups report==

A last execution log of scheduled course backups can be found in ''Settings > 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 on a particular course name will cause a detailed execution log to be displayed, including date, hour and minute when each step of the backup was performed.

[[Image:Reports_Site_Backups_1.jpg]]

===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 course name in the backups log), 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|site backups]]).

==See also==

* MDL-30725 Automated backups with external storage fill trashdir

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]
*[http://moodle.org/mod/forum/discuss.php?d=191275 the story of the mysteriously filling up hard disk]

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

[[eu:Ikastaroen_segurtasun-kopia_automatikoa]]
[[fr:Sauvegarde (administrateur)]]
[[ja:自動コースバックアップ]]
[[de:Automatische Kurssicherung]]

Using Activity completion

2012-11-28T09:04:17Z

Ghillenb:

{{Activity completion}}
==Why use Activity completion?==
*If this feature is enabled, it is a helpful way for students to be able to track their progress in a course. The student has an easy to see checklist of what they have done so far.
*It can also be linked to [[Course_completion| Course completion]] in order to allow both students and teachers to watch progress through a course. As each activity is checked off as "complete", the student moves futher towards final completion of the course.
*It can also be linked to [[Conditional_activities| Conditional activities]] in order to allow the teacher to set criteria upon which a student is allowed to progress through a course and access materials.

==Activity completion icons==

{|
| [[File:completion-manual-n.png]] manual - not yet marked as complete
|-
| [[File:completion-manual-enabled.png]] manual - enabled
|-
| [[File:completion-manual-y.png]] manually completed
|-
| [[File:completion-auto-y.png]] automatically completed
|-
| [[File:completion-auto-fail.png]] automatically failed
|-
| [[File:completion-auto-n.png]] automatic - not completed
|-
| [[File:completion-auto-pass.png]] automatically passed
|-
| [[File:completion-auto-enabled.png]] automatic - enabled
|}

==Activity completion report==

Activity completion info can be viewed by managers, teachers and non-editing teachers (and any other users with the capability [[Capabilities/report/progress:view|report/progress:view]]) in ''Navigation > Courses > My course > Reports > Activity completion''.

[[File:Reports_Activity_completion.png]]

[[Category:Report]]

[[de:Einsatzszenarien für den Aktivitätsabschluss]]

Capabilities/block/tags:myaddinstance

2012-11-26T08:20:34Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Tags block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Tags]]

[[de:Capabilities/block/tags:myaddinstance]]

Capabilities/block/tags:addinstance

2012-11-26T08:19:22Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Tags block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Tags]]

[[de:Capabilities/block/tags:addinstance]]

Capabilities/block/tag youtube:addinstance

2012-11-26T08:18:23Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Youtube block]] to a [[Tags]] page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Tags]]

[[de:Capabilities/block/tag youtube:addinstance]]

Capabilities/block/tag flickr:addinstance

2012-11-26T08:15:54Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Flickr block]] to a [[Tags]] page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Tags]]

[[de:Capabilities/block/tag flickr:addinstance]]

Capabilities/block/social activities:addinstance

2012-11-26T08:14:11Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Social activities block]] to a course in social format.
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Course]]

[[de:Capabilities/block/social activities:addinstance]]

Capabilities/block/site main menu:addinstance

2012-11-26T08:11:14Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Main menu block]] to a course page
*This capability is allowed for the default roles of manager and teacher

As it's not possible to add a main menu block to a course page, this capability doesn't make sense, and so is due for removal - see MDL-36755.

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

[[de:Capabilities/block/site main menu:addinstance]]

Capabilities/block/settings:myaddinstance

2012-11-26T08:09:37Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Settings block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

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

[[de:Capabilities/block/settings:myaddinstance]]

Capabilities/block/settings:addinstance

2012-11-26T08:07:43Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Settings block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/settings:addinstance]]

Capabilities/block/selfcompletion:addinstance

2012-11-26T08:01:18Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Self completion block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Completion]]

[[de:Capabilities/block/selfcompletion:addinstance]]

Capabilities/block/section links:addinstance

2012-11-26T08:00:37Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Section links block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/section links:addinstance]]

Capabilities/block/section links:addinstance

2012-11-26T07:59:50Z

Ghillenb:

Capabilities/block/search forums:addinstance

2012-11-26T07:58:40Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Search forums block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Forum]]

[[de:Capabilities/block/search forums:addinstance]]

Capabilities/block/rss client:myaddinstance

2012-11-26T07:57:52Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Remote RSS feeds block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:RSS]]

[[de:Capabilities/block/rss client:myaddinstance]]

Capabilities/block/rss client:addinstance

2012-11-26T07:56:16Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Remote RSS feeds block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:RSS]]

[[de:Capabilities/block/rss client:addinstance]]

Capabilities/block/recent activity:addinstance

2012-11-26T07:55:04Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Recent activity block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Course]]

[[en:Capabilities/block/recent activity:addinstance]]

Capabilities/block/recent activity:addinstance

2012-11-26T07:54:55Z

Ghillenb:

Capabilities/block/quiz results:addinstance

2012-11-26T07:53:00Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Quiz results block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Quiz]]

[[de:Capabilities/block/quiz_results:addinstance]]

Capabilities/block/private files:addinstance

2012-11-26T07:51:44Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[My private files block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Messaging]]

[[de:Capabilities/block/private files:addinstance]]

Capabilities/block/participants:addinstance

2012-11-26T07:50:24Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[People block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/participants:addinstance]]

Capabilities/block/online users:myaddinstance

2012-11-26T07:48:34Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add an [[Online users block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

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

[[de:Capabilities/block/online users:myaddinstance]]

Capabilities/block/online users:addinstance

2012-11-26T07:47:24Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add an [[Online users block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/online_users:addinstance]]

Capabilities/block/news items:myaddinstance

2012-11-26T07:45:52Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Latest news block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Forum]]

[[de:Capabilities/block/news_items:myaddinstance]]

Capabilities/block/news items:addinstance

2012-11-26T07:44:23Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Latest news block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Forum]]

[[de:Capabilities/block/news items:addinstance]]

Capabilities/block/navigation:myaddinstance

2012-11-25T19:07:15Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Navigation block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

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

[[de:Capabilities/block/navigation:myaddinstance]]

Capabilities/block/navigation:addinstance

2012-11-25T19:05:59Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Navigation block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/navigation:addinstance]]

Capabilities/block/myprofile:myaddinstance

2012-11-25T19:04:04Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Logged in user block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

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

[[de:Capabilities/block/myprofile:myaddinstance]]

Capabilities/block/myprofile:addinstance

2012-11-25T19:01:31Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Logged in user block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/myprofile:addinstance]]

Capabilities/block/mnet hosts:myaddinstance

2012-11-25T18:45:40Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Network servers block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:MNet]]

[[de:Capabilities/block/mnet hosts:myaddinstance]]

Capabilities/block/mnet hosts:addinstance

2012-11-25T18:44:06Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Network servers block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:MNet]]

[[de:Capabilities/block/mnet hosts:addinstance]]

Capabilities/block/messages:addinstance

2012-11-25T18:42:52Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Messages block]] to a course page
*This capability is allowed for the default roles of manager and teacher

[[Category:Capabilities|Block]]
[[Category:Block]]
[[Category:Messaging]]

[[de:Capabilities/block/messages:addinstance]]

Capabilities/block/mentees:myaddinstance

2012-11-25T18:42:10Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Mentees block]] to [[My Moodle]]
*This capability is allowed for the default role of authenticated user

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

[[de:Capabilities/block/mentees:myaddinstance]]

Capabilities/block/mentees:addinstance

2012-11-25T18:40:57Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Mentees block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/mentees:addinstance]]

Capabilities/block/login:addinstance

2012-11-25T18:39:56Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add a [[Login block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/login:addinstance]]

Capabilities/block/html:addinstance

2012-11-25T18:38:49Z

Ghillenb:

{{Capabilities}}{{New features}}
*This allows a user to add an [[HTML block]] to a course page
*This capability is allowed for the default roles of manager and teacher

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

[[de:Capabilities/block/html:addinstance]]