MoodleDocs - User contributions [en]

Stealth activities

2017-06-08T08:25:34Z

Lsansone: Add fr page translation

{{Courses}}{{New features}}
Earlier versions of Moodle had a “quirk” that allowed activities (or resources) to be hidden inside “extra” weeks or topics, but still be accessible to students. These were known as “orphaned” activities and allowed Moodle users to achieve particular designs for their courses.

Now in Moodle 3.3 you can put any activity or resource into “stealth mode” to achieve this same effect in a more officially-supported way. To get started, watch the [https://youtu.be/Z8e3BSopTg8 Stealth activities screencast.]

==Enabling stealth activities==
From 'Advanced features', administrators may 'Allow stealth activities' in courses. Teachers will then be able to make activities (or resources) available to students but not shown on the course page. This feature is supported in "Weeks", "Topics", "Social" formats and on the front page. Other course formats may or may not implement it.

==How stealth activities work: example==

A teacher has a course with a number of quizzes. (''1 below'') They make the course page rather long. She would prefer to add the links to the quizzes in a single page ''(2 below)'' to make her course neater, but if she then hides the quizzes, students will not be able to access them:

[[File:Stealthexample1.png]]

She turns on the editing and, from the Edit menu, hides each quiz. Note the blue alert message reminding teachers the activity is hidden.

[[File:Stealthexample2.png]]

She then goes back into the Edit menu and selects the 'Make available' option. Note the blue alert message changes to remind her the activity is available but will not be displayed on the course page to students.

[[File:Stealthexample3.png]]

She will then be able to make the links to those quizzes in her single page and students will be able to see the quizzes, do them and view their results in the gradebook. Students will not see the list of quizzes:

[[File:Stealthexample4.png]]

'''Note:''' Activities may be made available but not shown in any topic section, not just the bottom section, as used to be the case for "orphaned activities".

==What if the admin setting is disabled?==

'Allow stealth activities' is an Advanced feature. If the administrator has not enabled the setting, then it is still possible to make activities available but not shown on the course page.

To make activities (or resources) available but not shown on the course page when 'Allow stealth activities' is disabled:

# Hide the whole topic which contains (for example) the quizzes. ''(1 below).''
# Make individual activities available from the Edit menu ''(2 below).''
# Ensure that the single page which will contain the quiz links is in a topic where it will be visible to students ''(3 below).''

[[File:Steallth5.png]]

[[es:Actividades sigilosas]]
[[fr:Activités furtives]]

Random glossary entry block

2017-02-15T14:52:46Z

Lsansone:

{{Blocks}}The random glossary block can be used to display random entries from a glossary, which usually take the form of dictionary style definitions. However the flexibility of Moodle's HTML editor allow users to adapt this block for other purposes such as 'Quote of the Day' or a random picture gallery that changes each time the page is refreshed.

[[Image:Randomglossaryexample.png]]

Before using the random glossary entry block you have to configure it using the edit icon. There you will have a number of fields to complete:

===Title===

Here you will write the title of that block. The default is Random Glossary Entry.

===Take entries from this glossary===

This allows you to choose from which glossary the entries in this block will be chosen.

Global glossaries are also available, (thus allowing a glossary from a course to be displayed in a block on the front page for example)

===Days before a new entry is chosen===

This sets the number of days for how long that a given entry is displayed. If set to "0," a new entry displays every time the page is refreshed.

===How a new entry is chosen===

You have four options: ''Last modified entry'' will always display the entry that was last modified, and ''Random entry'' will choose a new one at random every time. The option ''Next entry'' will cycle through the entries in order. This option is especially useful when a number of days is also chosen, allowing you to make a Quote of the week or a Tip of the day that everyone sees.

''Alphabetical'' will display the entries in strict alphabetical order.

===Show concept (heading) for each entry===

Enabling that option will show headings for each entry that appears in the block.

===Links===

You can display links to actions of the glossary this block is associated with. The block will only display links to actions which are enabled for that glossary. You can type texts to appear for whichever of the three options: ''Users can add entries to the glossary'', ''Users can view the glossary but not add entries'' or ''Users cannot edit or view the glossary''.

==See also==

* [[Glossary module]]

[[Category:Glossary]]

[[de:Glossarblock]]
[[fr:Article aléatoire d'un glossaire]]
[[es:Bloque de entrada aleatoria del glosario]]

Managing blocks

2017-02-15T14:29:39Z

Lsansone: /* See also */

{{Blocks}}
==Manage blocks==

An administrator can manage Moodle's blocks for the site in ''Administration > Site administration > Plugins > Blocks > Manage blocks'', including any contributed blocks that have been added.

===Instances===

The blocks page lists the number of instance for each block. Clicking on a number results in the list of courses containing that block being displayed. See [[Block settings]] for configuration settings that might be of interest to a site administrator or someone with Front Page editing permissions.

===Version===

Listed with each block is its version number — in the format 2012061700. This is helpful to ensure that you have the latest version of each block.

===Hiding a block===

The hide/show column allows selected blocks to be hidden i.e. they do not appear in any course "Add a block" dropdown menu and cannot be used in any course. To hide a block, click the eye icon so that it changes to a closed eye.

To reduce the length of course "Add a block" dropdown menus, you should hide blocks which will not be used, such as mentees (unless you have added a [[Parent role|mentor role]]) and network servers (unless you are using [[MNet|Moodle Networking]]).

===Protecting blocks from deletion===

By clicking the padlock against a block in this column, you are preventing it from being deleted on the site. The [[Administration block]] and [[Navigation block]] are already padlocked, as major difficulties arise if these blocks are deleted. Only unlock them if you are absolutely sure you understand the consequences and have alternative settings and navigation features in place.

===Block deletion===

Blocks can be deleted using the Uninstall link for the appropriate block (but see comments about the [[Administration block]] and [[Navigation block]] in the previous section) There is usually no reason for standard blocks to be uninstalled (they are usually hidden) However, non-standard blocks may need to be uninstalled before upgrading.

:''Note:'' To delete a block completely, in addition to uninstalling it on the blocks page, you also need to remove/delete the actual block folder from the ''moodle/blocks'' folder, otherwise Moodle will reinstall it next time you access the site administration.

===Block settings===

Certain blocks have additional settings, which can be accessed via the links in the settings column.

==Block capabilities==

*[[Capabilities/moodle/my:manageblocks|Manage dashboard blocks]]
*[[Capabilities/moodle/tag:editblocks|Edit blocks in tags pages]]
*[[Capabilities/moodle/user:manageownblocks|Manage blocks on own public user profile]]
*[[Capabilities/moodle/user:manageblocks|Manage blocks on user profile of other users]]
*[[Capabilities/moodle/block:edit|Edit a block's settings]]
*[[Capabilities/moodle/block:view|View block]]
*[[Capabilities/moodle/site:manageblocks|Manage blocks on a page]]

In addition, every block has an ''addinstance'' capability (e.g. [[Capabilities/block/comments:addinstance|block/comments:addinstance]]) and most blocks also have a ''myaddinstance'' capability (e.g. [[Capabilities/block/comments:myaddinstance|block/comments:myaddinstance]]) for controlling whether a user with a particular role can add the block to a page or to their [[Dashboard]] respectively.

==Contributed blocks==

In addition to using the blocks included in the standard download, other Moodlers have developed their own blocks which they share with the Moodle community. You can download these contributed blocks from the Moodle.org [http://moodle.org/plugins Moodle Plugins directory]. See [[Installing plugins]] for details of how to install a block.

==See also==
*[[Block layout]]

[[Category:Site administration]]

[[fr:Gestion des blocs]]
[[eu:Blokeak_%28Kudeatzailea%29]]
[[ja:ブロック管理 (管理者)]]
[[de:Administration_von_Bl%C3%B6cken]]
[[es:Gestionando bloques]]

Managing roles

2017-02-15T09:16:05Z

Lsansone: /* Roles capabilities */

{{Roles}}
Managing overall role capabilities can be done by an administrator using ''Administration > Site administration > Users > Permissions > Define roles''. This is the place to add custom roles or modify existing roles. The "Manage roles" tab, allows the system administrator to edit any one of over 350 different capabilities associated with any role. The "Allow role assignments", "Allow role overrides" and "Allow role switches" contain a matrix which give the ability for a specific role to work with other specific roles.

==Manage roles==

The 'Manage roles' tab contains a list of roles on your site. The edit column contains icons for editing, deleting roles and copying roles, and for moving them up or down in the list (affecting the way that roles are listed around Moodle).

[[Image:Manageroles2.png]]

To edit a role:
#Go to ''Administration > Site administration > Users > Permissions > Define roles''.
#Click the edit icon opposite the role you want to edit. For example "student".
#On the editing role page, change permissions as required for each capability.
#Scroll to the bottom of the page and click the "Save changes" button.

See [[Creating custom roles]] for information about adding a new role and creating a duplicate role.

==Role name localisation==

If a standard role name or description is empty Moodle uses a default string from the current language pack. Custom roles can be customised using multilang syntax.

You may also override the role names separately in each course.

==Resetting a role==

To reset a role back to the default permissions:
#Go to ''Administration > Site administration > Users > Permissions > Define roles''.
#Click on the name of the role, for example "student".
#Click the 'Reset' button.

Note that if you have students who have been given extra permissions at course and/or activity levels (such as forum ratings), then they will no longer be able to do this once the role has been reset to its default. A teacher would need to go back and set up these extra permissions in the course/activity levels again.

==Allow role assignments==

The "Allow role assignments" tab allows (or does not allow) a specific role to be able to assign specific roles to a user.

[[File:Allowroleassignments.png]]

===Enabling teachers to assign other teachers===
By default, teachers can only assign other users the roles of non-editing teachers, students and guests. If you want teachers to be able to assign other teachers in their course, you can allow the role assignment:

#Click on ''Administration > Site administration > Users > Permissions > Define roles''.
#Click the Allow role assignments tab.
#Click the checkbox where the teacher row and column intersect.
#Click the "Save changes" button.

==Allow role overrides==
The "Allow role overrides" tab allows (or does not allow) a specific role to be able to override specific roles for a user. For example, it might allow a teacher role to override a student's role to a non-editing teacher's role.

:Note that the settings only apply to roles that have the capabilities [[Capabilities/moodle/role:override|moodle/role:override]] or [[Capabilities/moodle/role:safeoverride|moodle/role:safeoverride]] allowed.

==Allow role switches==
The "Allow role switches" tab allows (or does not allow) a specific role to be able to temporarily change their role to another specific role. For example, this might allow a users assigned to a custom role in a course to see "Student" in the Settings > Switch role list.

:Note: the selected role must also have the moodle/role:switchroles capability to be able to switch.

==Roles capabilities==

*[[Capabilities/moodle/role:manage|Create and manage roles]]
*[[Capabilities/moodle/role:assign|Assign roles to users]]
*[[Capabilities/moodle/role:switchroles|Switch to other roles]]

[[Category:Site administration]]

[[es:Gestionar_roles]]
[[eu:Rolak_kudeatu]]
[[fr:Gestion des rôles]]
[[ja:ロールの管理]]
[[de:Rollen verwalten]]

Plugins FAQ

2017-02-15T09:04:43Z

Lsansone: /* See also */

{{Installing Moodle}}==What is a plugin?==

A plugin, (previously known as an add-on, contributed code, or "contrib" for short), is code enabling you to add additional features and functionality to Moodle.

A number of plugins are included in the standard Moodle download. Additional plugins may be obtained from the [http://moodle.org/plugins Moodle plugins directory].

==How do I install a plugin?==

See [[Installing plugins]] for instructions. Some, but not all, contributors include a "Read me" file with instructions in their plugin package.

In a typical install, you will probably copy some php files into one or more areas of you Moodle site's code, then click on the Site administration link called "Notifications" to start the install process.

==How do I apply a patch?==

See [[:dev:How to apply a patch]].

==Why doesn't my newly installed plugin show up in the list of plugins?==

Firstly, check that you have visited your admin index page <nowiki>http://your_moodle_site.org/admin/index.php</nowiki> to complete the installation. Next, check that you unzipped the archive to the correct folder, and that the new plugin folder is not contained within another folder.

==How do I contribute code to Moodle?==

See [[:dev:Guidelines for contributed code|Guidelines for contributed code]].

==Is there any information on creating a new plugin?==

Yes! See [[:dev:Plugins]].

==See also==

* Using Moodle [http://moodle.org/mod/forum/view.php?id=44 General plugins forum]
* [https://moodle.org/mod/forum/discuss.php?d=325804#p1309721 Moodle 2015 favorite plugins] forum thread by Gavin Henrick, with lots of useful information about Moodle plugins

[[Category:Contributed code]]
[[Category:FAQ]]

[[fr:FAQ de code tiers]]
[[es:Plugins FAQ]]

Tracker module

2012-10-13T13:44:21Z

Lsansone: lien vers la doc française

==Module overview==

This module provides a light but full featured ticket tracker within a Moodle environment. This tracker could be used by administrators to collect issues from Moodle end users, or may be as a real bug tracking tool for project oriented activities.

Recently has the semantics of the string being reviewed to allow a more general scope use of the tracker, whenever the need of "service ticketting" appears.

The internal tracker module of Moodle have following features :

===Tracker configuration===

* Setting up ticket form elements
* File attachment fields available

===Ticket management===

* Collecting tickets
* Assigning tickets to assignees
* Status workflow (posted, opened, working, testing, resolved, blocked, abandonned, transfered).
* Suscribing to ticket's notifications
* Notifying changes to suscribers
* Complete personal management of notifications and subscriptions
* Summary of capabilities and owned tickets
* Separating concluded tickets (resolved, abandonned, transferred) from working tickets (posted, working, blocked)
* Ticket dependancy chaining
* Messaging threads (globally disablable) attached to tickets

===Default assignee===

A user that is known as "resolver" can be assigned "as default" to all incoming tickets.

===Priority related features===

* Managing ticket priority (controls are active when choosing priority as ordering criteria)
* Asking for priority raise from the owner of the ticket

===State change tracking===

the tracker records and displays history of events that were attached to the ticket.

===Subtracker binding===

As this ticket has no internal ticket classification in sub tracks, the usual setup is to use several instances
bound into a super/sub-tracker structure. Each tracker can have subtrackers to which some incoming ticket can
be rerouted.

It is thus sinple to provide a global input tracker a manager will use to collect "everything" and then dispatch
each ticket.question to the appropriate instance.

===Ticket events===

*'''POSTED:''' Ticket has been posted by originator and not yet viewed by anyone.
*'''OPEN:''' Someone has opened the ticket.
*'''RESOLVING:''' Some assigned user or ticket manager starts working on the track.
*'''WAITING:''' Something blocks (external request) the work on this ticket.
*'''TESTING:''' Solution is proposed, but needs to be tested by originator
*'''RESOLVED:''' Issue is solved. This should be the final state in short life-cycle.
*'''ABANDONNED:''' Issue is abandonned as no more relevant.
*'''TRANSFERED:''' Query has been trasnfered to another tracker
*'''PUBLISHED:''' In case resolution only affects a qualification environmet, published tells the solution has been published to production instance.
*'''VALIDATED:''' Solution is finally checked as operative in production (definitive) environment. This should be the final state in long life-cycle.

====Short Life-Cycle====

This is to apply in "single step work process", when first publication of the solution is enough to get things approved.

POSTED > OPEN > RESOLVING > TESTING > RESOLVED

====Long Life-Cycle====

This is to apply in "dual step work process", that is approval is first agreed on a pre-production worplace, then published for effective production

POSTED > OPEN > RESOLVING > TESTING > RESOLVED > PUBLISHED > VALIDATED

===Moodle Network functions===

* Moodle Network across cascading from a tracker to a remote tracker (local cascade works either within the same Moodle instance).

==Local Roles Management==

Tracker has its own internal user profiles, that will merely separate population into:

*Administrators: will be allowed to change the form structure and all settigns of the tracker instance
*Resolvers: are allowed to change the ticket status and thus closing or resolving tickets. They also can assign tickets to developers.
*Developers: usually people that will handle the ticket and search for a solution.
*Requirers: any user able to post a ticket.

Internal tracker roles are bound to Moodle roles through tracker specific capabilities. See the tracker capabilities documentation beneath for more information.

==Screens==
===Common user screens===
* [[Tracker_module/Bug recollection form | Ticket recollection form]]
* Viewing ticket list
** Exploring ticket list (non manager mode)
** Searching a ticket
** Viewing a ticket description
* User profile, stats and shortcuts
** My preferences : choosing on which events to be notified
** My watches : managing which entries I receive notifications from
** My searches : managing stored search queries for my own

===Resolver screens===
* Viewing ticket list
** Exploring ticket list (manager mode)
** Exploring tickets assigned to *me*
** Editing a ticket entry

===Administrator screens===
* Activity summary
* Managing bug tracking form elements
* Configuring tracker local or remote cascade

==Capabilities==

[[Tracker_module/Capabilities|Capabilities for Tracker module]]

[[Category:Contributed code]]
[[fr:Tracker]]