MoodleDocs - User contributions [en]

User:Barcaru Victor

2021-09-02T06:28:07Z

Vbarcaru:

vbarcaru
{{DEFAULTSORT:User:vbarcaru}}

Linking Moodle and Docs

2016-10-19T12:06:38Z

Vbarcaru: /* Settings */

{{Help}}
[[Image:Information_icon.GIF|frame|Example link]]Location: ''Administration > Appearance > Moodle Docs''

Moodle Docs is an abbreviation for ''Moodle documentation''.

By default, teachers and administrators have "Moodle Docs for this page" links at the bottom of each page in Moodle for accessing context-specific documentation.

==Moodle documentation==
As you may have discovered, Moodle Docs contains many searchable pages which represents 1,000s of hours of refinement by the Moodle community. For example, it is common to see a link from a forum in Moodle.org to a specific page or section in a Moodle Docs page. Likewise, something can be added to Moodle Docs to cover a new feature or to give a more detail description of a process that is not possible or desirable in a forum or as part of the help files.

Moodle Docs is a living document that is constantly changing at docs.moodle.org . Anyone in the Moodle community who sees a need is invited to make an addition or add their opinion in the page comments tab.

==Removing Moodle Docs links for teachers==

#Access ''Site Administration > Users > Permissions > Define roles''.
#Edit the teacher role and change the capability [[Capabilities/moodle/site:doclinks|moodle/site:doclinks]] from allow to not set.
#Scroll to the bottom of the page and click the button "Save changes".

==Tips and tricks ==
It is possible to download am HTML copy of Moodle documentation at [http://wimski.org/docs/ wimski.org/docs] to another server. While useful, these are not Wiki pages and do not follow the file structure of docs.moodle.org.

It is possible to export one or more docs.moodle.org pages and then import those to another wiki via functions found in Special pages, located in the wiki Toolbox, usually located on the left of each Moodle Doc page.

*Note: Information links are different than help links [[Image:Help.gif]] which are internal links. They can be found in the Moodle site file structure. For example a lesson question's feedback help file might be found at <nowiki>C:\moodle18\moodle\lang\en_utf8\help\lesson\feedback.html</nowiki>

==See also ==
*[[Capabilities/moodle/site:doclinks]]
*[[:Category:MoodleDocs]]
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=81000 MoodleDocs link] forum discussion

[[Category:Administrator]]

[[eu:Moodle_Doc-ak]]
[[fr:Moodle Docs]]
[[de:Verknüpfung von Moodle mit den Moodle Docs]]
[[es:Enlazando Moodle y Docs]]

Help:Editing

2016-10-15T19:34:30Z

Vbarcaru: /* Edit tool bar */

{{Help}}
This page is for editing Moodle Documentation (MoodleDocs), which is based on MediaWiki format (similar to Wikipedia).

==Edit tab==
Every MoodleDoc page has an "edit" tab at the top . This link will let you edit the page you are viewing. Please try editing a page by using this [[Sandbox|sandbox link]]. We will cover more formatting and special MoodleDoc features below. The edit tool bar is easy to use.

There are 3 parts to the edit page: the content areas to edit with its toolbar at the top; the save, preview, changes and summary box; the preview area.

[[File:Capture1.jpg]]

=== Show preview ===
[[Image:MoodleDocs save edit area 1.png|frame|center|Example of the save, preview, comment area below the edit box]]
In edit mode, the show preview button at the bottom of the page lets you see what the page will look like after your edit, before you actually save. We all make mistakes; this feature lets you catch them immediately. Using Show preview before saving also lets you try format changes and other edits without cluttering up the page history, and has a number of other advantages. Don't forget to save your edits after previewing, though!

=== Edit summary ===
Before saving the page, it's considered good practice to enter a very brief summary of your changes in the summary box below the edit-box.

In the example above, the contributor used the edit link next to a heading called "Tips and tricks". MoodleDocs automatically added "/* Tips and tricks */" to the summary box. The The contributor added a comment "Put comment here about edit - will rollback".

See [[Help:Editing#Page history|Page history below]] where the example is continued.

===Show changes===
This button will change the preview area. One column will show current areas that will be changed and another column will show the resulting changes from what has been done in the content editing box.

== Formatting ==

Most '''formatting''' in MoodleDocs is usually done with MediaWiki markup - you don't have to learn HTML!

=== Bold and italics ===
'''Bolding''' and ''italicizing'' is done by surrounding a word or phrase with multiple apostrophes (<tt>'</tt>):

:<code><nowiki>''italics''</nowiki></code> appears as ''italics''. (2 apostrophes on both sides)
:<code><nowiki>'''bold'''</nowiki></code> appears as '''bold'''. (3 apostrophes on both sides)
:<code><nowiki>'''''bolded italics'''''</nowiki></code> appears as '''''bolded italics'''''. (5 apostrophes on both sides)

=== Headings and subheadings ===
Headings and subheadings are an easy way to improve the organization of an article.

Headings can be created like this:
:<code><nowiki>==Top level heading==</nowiki></code> (2 equals signs)
:<code><nowiki>===Subheading===</nowiki></code> (3 equals signs)
:<code><nowiki>====Another level down====</nowiki></code> (4 equals signs)

If an article has at least four headings, a table of contents will automatically be generated.

=== Indentations ===
The simplest way of indenting is to place a colon (<code>:</code>) at the beginning of a line. The more colons you put, the further indented the text will be. A newline marks the end of the indented paragraph e.g.
:<code>This is aligned all the way to the left.</code>
:<code><nowiki>:</nowiki>This is indented slightly.</code>
:<code><nowiki>::</nowiki>This is indented more.</code>
is shown as
:This is aligned all the way to the left.
::This is indented slightly.
:::This is indented more.

=== Lists ===
{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
* ''Unordered lists'' are easy to do:
** start every line with a star
*** more stars means deeper levels
*A newline
*in a list
marks the end of the list.

|<pre><nowiki>* Unordered Lists are easy to do:
** start every line with a star
*** more stars means deeper levels
*A newline
*in a list
marks the end of the list.
</nowiki></pre>
|-
|
# Numbered lists are also good
## very organized
## easy to follow
#A newline
#in a list
marks the end of the list.
|<pre><nowiki># Numbered lists are also good
## very organized
## easy to follow
#A newline
#in a list
marks the end of the list.
</nowiki></pre>
|-
|Descriptive lists:
; first tag : accompanying description
; second tag : more description
; third tag : surprise! more description
|<pre><nowiki>Descriptive lists:
; first tag : accompanying description
; second tag : more description
; third tag : surprise! more description
</nowiki></pre>
|}

=== Preserving formatting ===

{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
Leading spaces are another way to preserve formatting.

Putting a space at the beginning of each line
stops the text from being reformatted.
|<pre><nowiki>Leading spaces are another way to preserve formatting.

Putting a space at the beginning of each line
stops the text from being reformatted.
</nowiki></pre>
|}

You can also use <nowiki><pre></nowiki> tags.

A "nowiki" tag on either side of text area, starts and stops wiki formatting within a line of text. For example, placing the tags here <nowiki> <nowiki> turns off linking [[Main page]] </nowiki> </nowiki> and then starts the wiki formatting again. Here is the same link [[Main page]] without the tags on either side.

The HTML edit tool bar has a nowiki icon.

===PHP syntax higlighting===

{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
<code php>$user = $DB->get_record('user', array('id'=>'1');</code>
|<pre><nowiki><code php>$user = $DB->get_record('user', array('id'=>'1');</code></nowiki></pre>
|}

===Tables===

See [http://meta.wikimedia.org/wiki/Help:Table#Spreadsheet_to_wiki_table_format the Mediawiki help] for full details of the table syntax.

{| class="nicetable"
|-
!What it looks like
!What you type
|-
| A table:

{| class="nicetable"
|-
! header 1
! header 2
! header 3
|-
| row 1, cell 1
| row 1, cell 2
| row 1, cell 3
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
|}

| <pre><nowiki>A table:

{| class="nicetable"
|-
! header 1
! header 2
! header 3
|-
| row 1, cell 1
| row 1, cell 2
| row 1, cell 3
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
|}
</nowiki></pre>
|}

Note, the class="nicetable" is our local hack for Moodledocs. You can leave it out to get a table without borders.

You can also add in more attributes if you do not want to use class="nicetable"

<nowiki>border="1" cellpadding="5" cellspacing="0" align="center"</nowiki>
Or perhaps you want a floating table.
<nowiki>style="float: right;"</nowiki>

Like HTML, you can also have a combined use of "colspan" and "rowspan":
<nowiki>| rowspan="2" | A
| colspan="2" style="text-align: center;" | B</nowiki>

(from mediaWiki Help pages)

== Using Images ==
Images are included in two parts. The first part is a link in the page to an image and the second is uploading the image. For example:

<nowiki>[[Image:MoodleDocs Edit Toolbar.png|frame|center|Edit tool bar]]</nowiki>

is how an image is edited onto the page. The brackets place a link to an image. The Image name tells the wiki renderer that an image is following. The name of the image follows then after that the presentation style of that image is determined. There are a number of different styling possibilities and include thumbnails, resizing, borders, etc.

Images are initially rendered on the page as text, you click the text and a very simple upload process begins. Wikis store images automagically and maintain links internally.

For practical and stylistic reasons, Moodle Docs tend to keep images in the centre of a page and do not often use thumbnails.

For full documentation about images, see [https://www.mediawiki.org/wiki/Help:Images Mediawiki Image Docs]

==Embedding videos==

To embed a YouTube video, simply add <nowiki><mediaplayer></nowiki> tags around the video URL e.g. <nowiki><mediaplayer>http://www.youtube.com/watch?v=U7M3sZL6wts</mediaplayer></nowiki>

== Links and Anchors ==

=== Page links ===
To make a wiki page link, simply put the word in double square brackets, like this: <code><nowiki>[[Sandbox]]</nowiki></code> . Highlight text and using the "internal link" tool will do this as well.

If you want to use words other than the article title as the text of the link, you can do so by adding the pipe "|" divider followed by the alternative name or text.

For example, if you wanted to make a link to the [[Sandbox]], but wanted it to say "my text" you would write it as: <code><nowiki>[[Sandbox|my text]]</nowiki>...</code> It would appear as: [[Sandbox|my text]]... but would link to the sandbox.

There are some special internal link notations. For example <nowiki>[[#top]]</nowiki> will always jump to the top of the current page.

=== External links ===

The easiest way to make an external link is to simply type in the full URL for the page you want to link to e.g. http://school.demo.moodle.net/.

If you want the link to appear with text that you specify, add an alternative title after the address separated by a '''space''' (''not'' a pipe). So if you want the link to appear as [http://school.demo.moodle.net/ School demo site], just type <code><nowiki>[http://school.demo.moodle.net/ School demo site] </nowiki></code>.

===Tracker links===

To automatically link to an issue in the Moodle tracker, simply type the issue number MDL-xxxx e.g. MDL-1234.

=== Categories links ===
A category is a type of index page, a page of links listed in alphabetical order. In page view mode, a list of categories that a page is linked to, appears at the bottom.

To '''put a page in a category''', just type <code><nowiki>[[Category:]]</nowiki></code>, and put the name of the category between the colon and the brackets.

To '''link directly to a category''' use <code><nowiki>[[:Category:Teacher | teacher]]</nowiki></code>, this will show as [[:Category:Teacher | teacher]], note the preceding ":", which is different to <code><nowiki>[[Category:Teacher | teacher]]</nowiki></code>. The second will put the current page in the teacher category as mentioned above.

If you put a page in a category, it's usually a good idea to '''add a sort key''' to the category like so: <code><nowiki>[[Category:Developer|Eclipse]]</nowiki></code>. This will result in the page being placed under "E" like "Eclipse" in the alphabetical link list where most users will look for it.

You can also use MediaWiki's '''PAGENAME variable''' (= the article title without its namespace) as a sort key: <code><nowiki>[[Category:Developer|{PAGENAME}]]</nowiki></code>.

This page is linked to the single category "MoodleDocs".

===Inter-language links===

Simply type <code><nowiki>[[es:Corresponding page title in Spanish]]</nowiki></code> in the English Moodle Docs, or <code><nowiki>[[en:Corresponding page title in English]]</nowiki></code> in the [[:es:Portada|Spanish Moodle Docs]], at the bottom of the page, below the category link. Inter-language links will appear automatically in the "In other languages" block.

If for some reason you want to refer to a page in another language version in the running text, precede the language code by a colon. Thus, the reference in the preceeding paragraph was produced by the text <nowiki>[[:es:Portada|Spanish Moodle Docs]]</nowiki>.

You can also, using the same way, make link to developper documentation, using links like this one : <nowiki>[[:dev:Page name|Page title to use]]</nowiki>.

<nowiki>[[:en:Page name|Page title to use]]</nowiki> links to the latest version of the page in English.

=== User-page links ===
User names can be linked to a user page. For example <nowiki>[[User:Helen Foster|Helen Foster]] </nowiki> will appear [[User:Helen Foster|Helen Foster]] and link to the user's page. Comments by other users are generally left on the Users page comment tab.

=== Interwiki links ===
To link to the Moodle Development Wiki, use the notation <nowiki>[[dev:source|cue]]</nowiki>

===Manual Anchors===
Other than automated anchors ([[#Automatic_Anchors|see below]]) manual anchors can be inserted by using something this this:

<nowiki>'''My Anchor.'''</nowiki>

Which if implemented will create an anchor '''My Anchor.'''.

Inside the page I can now refer to this link as [[#anchor_one|the link to My Anchor]] by using this:

<nowiki>[[#anchor_one|the link to My Anchor]]</nowiki>

If you want to have a link back to the top of a (long) page, just insert:

<nowiki>[[#top|Back to top of page]]</nowiki>

== Page comments ==
The page comment tab is used for discussion about the page. Sometimes before making an edit on the page for the first time, it is a good idea to check the page comments. It can be formatted the same as a main page, thus can be used to show a draft of a proposed change.

Talk page contributions may be signed and dated by typing four tildes <nowiki>~~~~</nowiki>. This will appear as [[User:Helen Foster|Helen Foster]] 06:35, 19 February 2006 (WST), for example.
: There's also a handy button for signing in the toolbar of the editing field: [[Image:Signature Icon.png]]

==Page history==
The page history tab allows a way to look at changes between different edits by using the "Compare versions" button and selecting the versions to compare.

It is also possible to revert (roll back) an edit to a previous version from this tab. Usually rollback are left to the MoodleDoc Sysops (administrators), but you certainly can rollback your recent edits. Hopefully, both MoodleDoc sysops and you will comment why the rollback was performed.
[[Image:MoodleDocs history 1.png|frame|center|Example of top 2 entries on a history tab]]

==Watch and unwatch page==
A watched page will appear on "my watchlist" when ever someone edits the page. There is a tab next to history which acts as a toggle between watch and unwatch. In edit mode, there is also at the bottom of the edit area a "Watch this page" check off box.

==See also==
*[http://meta.wikimedia.org/wiki/Help:Editing MediaWiki Help:Editing]
*[http://meta.wikimedia.org/wiki/Help:HTML_in_wikitext Help:HTML in wikitext]
*[http://wikipedia.mozdev.org/ Firefox Wikipedia extension] - The Wikipedia extension makes editing of wiki pages easier by adding a new toolbar to your browser and by providing new menu items in the context menu (right mouse key).

[[Category:MoodleDocs]]

[[de:Bearbeitung von Moodle Docs Seiten]]
[[es:Ayuda:Cómo se edita una página]]
[[fr:Aide:Comment éditer une page]]
[[ja:Help:編集方法]]

Configuration file

2016-09-29T16:47:00Z

Vbarcaru: /* Changing default theme directory location */

{{Installing Moodle}}
The name for Moodle's configuration file is config.php. The file is located in the moodle directory. It is not included in the Moodle download packages and is created by the installation process from the template file config-dist.php (which is included in Moodle packages).

==config-dist.php==
Although the installation process creates the config.php file for you, there may be times when you want to do this yourself. A sample config file, called config-dist.php, is shipped with Moodle.

To get started simply copy config-dist.php to config.php, then edit config.php with you favourite editor. The file is very well commented. The important options (which you must supply) are all nearer the top. Other less common options are further down.

==Setting $CFG->wwwroot correctly==
This setting must be a fixed URL (a string constant) that points to your site. Do not try to set this with any PHP code that can generate a variable URL. This is not supported, can cause strange problems and will stop command line scripts working completely. If your site is accessed from different IP addresses this should be done with a split DNS, see [[Masquerading]]

==Enabling password salting==

See [[Password salting]].

==Including passwords in backups==

Hashed user passwords are no longer saved in backup files containing user data.

If you really need passwords to be saved (in the rare case of restoring a [[Backup of user data|backup with user data]] to a different site), the following line may be added to config.php:

$CFG->includeuserpasswordsinbackup = true;

Note regarding restoring Moodle 2.5 backups to sites with old PHP versions:

Because bcrypt is not supported in PHP versions below 5.3.7, course backups made using the $CFG->includeuserpasswordsinbackup setting on a site using PHP version 5.3.7+ that are subsequently restored to a site with PHP version < 5.3.7 will require a password reset.

==Changing default block layout for new courses==

See [[Block layout]].

==Changing default theme directory location==
The location of theme directories may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes placed in the directory specified by these variables will then be available for selection using the theme selector.

For example, should you wish to place themes in a subdirectory called 'my_moodle_themes', your config.php might look like this:
<pre>
$CFG->wwwroot = 'http://vbarcaru.net/moode1';
$CFG->dirroot = '/var/www/public_html/vbarcaru.net/moodle1';
$CFG->themewww = $CFG->wwwroot . '/my_moodle_themes';
$CFG->themedir = $CFG->dirroot . '/my_moodle_themes';
</pre>

==Disabling update notifications==

See [[Notifications]].

==Enabling debugging==

See [[Debugging]].

==See also==

* Using Moodle [http://moodle.org/mod/forum/discuss.php?d=137889 Moodle Salting] forum discussion

[[de:Konfigurationsdatei]]
[[es:config.php]]
[[fr:Fichier de configuration]]
[[ja:設定ファイル]]

File:newdraganddrop.png

2016-02-10T19:20:47Z

Vbarcaru: Vbarcaru uploaded a new version of File:newdraganddrop.png

new text

Administration via command line

2016-02-01T14:10:22Z

Vbarcaru: /* Running CLI scripts */

{{Installing Moodle}}

$ sudo -u apache /usr/bin/php admin/cli/install.php --help
$ cd /path/to/your/moodle/dir
$ sudo -u apache /usr/bin/php admin/cli/somescript.php --params

== Upgrading ==

Moodle can be upgraded from the command line. As with the installation script, there is either interactive or non-interactive mode of the upgrade. The script itself does not put the site into the maintenance mode, you have to do it on your own. Also, the script does not backup any data (if you read this page, you probably have some own scripts to backup your moodledata and the database, right?)

$ sudo -u apache /usr/bin/php admin/cli/upgrade.php

Upgrading via command line is a very comfortable way of Moodle upgrade if you use Git checkout of the Moodle source code (see [[Git for Administrators]]). See the following procedure how to upgrade your site within several seconds to the most recent version while preserving your eventual local customizations tracked in git repository:

$ cd /var/www/sites/moodle/htdocs/
$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enable
$ git pull
$ sudo -u apache /usr/bin/php admin/cli/upgrade.php
$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --disable

== Installation ==

There are two modes of installing Moodle from the command line. In interactive mode, the install script asks you for all data needed to properly set up new Moodle site. In non-interactive mode, you must provide all required data as the script parameters and then the new site is installed silently. The parameters can be passed in the interactive mode, too. The provided values are then used as the default values during the interactive session.

$ sudo -u apache /usr/bin/php admin/cli/install.php --lang=cs

{{New features}}If required, the database install may be skipped, with just config.php populated.

$ sudo -u apache /usr/bin/php admin/cli/install.php --skip-database

== Maintenance mode ==

To switch your site into the maintenance mode via CLI, you can use

$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enable

To turn maintenance mode off, just execute the same script with --disable parameter.

== Offline mode ==

In some situations, you may want to switch your Moodle site into offline mode so that it is not accessible via the web but you can not stop the web server completely (typically because there are other web pages and applications running there). If a file called <code>climaintenance.html</code> exists in the root folder of moodledata directory, Moodle will automatically display the contents of that file instead of any other page.

$ cd /var/www/sites/moodle/moodledata/
$ echo '<h1>Sorry, maintenance in progress</h1>' > climaintenance.html

You can prepare a nice formatted HTML page to inform your users about the server being down and keep in the moodledata directory under a name like <code>climaintenance.off</code> and rename it to the <code>climaintenance.html</code> if needed.

== Custom site defaults ==

During the install and upgrade via CLI, Moodle sets the administration variables to the default values. You can use different defaults. See MDL-17850 for details. Shortly, all you need to do is to add a file <code>local/defaults.php</code> into your Moodle installation. The format of the file is like

<code php>
<?php
$defaults['pluginname']['settingname'] = 'settingvalue'; // for plugins
$defaults['moodle']['settingname'] = 'settingvalue'; // for core settings
</code>

These defaults are used during install, upgrade and are also displayed as defaults on Site administration pages.

== Reset user password ==

If you happen to forget your admin password (or you want to set a password for any other user on the site), you can use reset_password.php script. The script sets the correctly salted password for the given user.

$ sudo -u apache /usr/bin/php admin/cli/reset_password.php

== MySQL storage engine conversion ==

If you run your Moodle site with MySQL database backend and use the default MyISAM as the storage engine for your tables, you may want to convert them to use some more reliable engine like InnoDB (actually, you should want to switch to PostgreSQL ;-) anyway).

$ sudo -u apache /usr/bin/php admin/cli/mysql_engine.php --engine=InnoDB

==Converting InnoDB tables to Barracuda==

Sites using MySQL with database tables using Antelope as the file format are recommended to convert the tables to the Barracuda file format.

This is because tables using Antelope as the file format cannot handle more than 10 text columns. This file formats only supports ''compact'' and ''redundant'' row formats for backward compatibility reasons. This may cause a problem on larger sites when restoring a course, in which case the following error will be displayed:

Row size too large (>8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help.

Barracuda is the newest innoDB file format. In addition to supporting ''compact'' and ''redundant'' row formats, Barracuda also supports ''compressed'' and ''dynamic'' row formats.

However, converting tables to Barracuda is only recommended, and not required, since not all MySQL users are affected. (It may only be a problem for larger sites.)

===Tool for converting tables===

A command line tool is included in Moodle for converting tables to Barracuda.

To view tables requiring conversion, use the list option:

$ php admin/cli/mysql_compressed_rows.php --list

Here is an example output:

mdl_data Compact (needs fixing)
mdl_data_fields Compact (needs fixing)
mdl_enrol_paypal Compact (needs fixing)

To proceed with the conversion, run the command using the fix option:

$ php admin/cli/mysql_compressed_rows.php --fix

Successful table conversion will be reported in the output, for example:

mdl_data ... Compressed
mdl_data_fields ... Compressed
mdl_enrol_paypal ... Compressed

Please note that the commands must be executed on your moodle directory. Once tables are fixed, the warning message will no longer be displayed.

For further information on InnoDB file formats see the [http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_antelope MySQL InnoDB glossary - Antelope] and the [http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_barracuda MySQL InnoDB glossary - Barracuda].

== Running cron via command line ==

In versions 1.x, you could execute admin/cron.php either from command line or via the web. Since Moodle 2.0, only admin/cli/cron.php script can be run via command line.

== Scheduled tasks ==

Scheduled tasks are automatically run by the cron script, but the specific tasks which run on each cron iteration are determined by the scheduled tasks configuration. It is possible to override the scheduled tasks configuration and run a single scheduled task immediately using the admin/tool/task/cli/schedule_task.php script.

This script accepts the following arguments:

--list - list all the known scheduled tasks. The tasks are listed by the class name used to run the task. This class name is required as the argument to the next option in order to run a specific task immediately.

--execute=<task> - Runs a single scheduled task immediately - regardless of scheduling settings. This will even run disabled tasks. Tasks will still use locking to prevent concurrent execution of the same task - even on clusters. The format of the <task> argument must be the same as returned by the --list option above.

'''Note:''' You must escape the "\" with an extra \ when using the --execute command. Take the following for example:

<pre>php schedule_task.php --list</pre>

will return something like:

<pre>
== List of scheduled tasks (http://yourserver.com/moodle) ==
\enrol_imsenterprise\task\cron_task 10 * * * * * ASAP
\logstore_legacy\task\cleanup_task * 5 * * * * ASAP
\logstore_standard\task\cleanup_task * 4 * * * * Wednesday, November 12, 2014, 4:35 AM
\mod_forum\task\cron_task * * * * * * ASAP
\core\task\automated_backup_task 50 * * * * * ASAP

...
</pre>

To run the first task in that list, you would execute

<pre>php schedule_task.php --execute=\\enrol_imsenterprise\\task\\cron_task</pre>

==Database transfer==

A command line script for [[Database transfer]] may be found in ''admin/tool/dbtransfer/cli/migrate.php''.

php admin/cli/purge_caches.php

==Fix course / module sequences==

In rare cases (such as after upgrading from a very old version of Moodle), the course / section / module sequence data can be out of sync. This can cause various problems for affected courses, such as sections not appearing, backups failing, pages not displaying etc. There is a specific check to check for errors caused by this problem, and to fix the data in the database if they are found. To run this script please use the command below:

php admin/cli/fix_course_sequence.php -c=* --fix

This will check every course in Moodle and report which ones had errors and were fixed.

==Fix orphaned question categories==

When a quiz is created, a new question category for the quiz is automatically created. In versions of Moodle prior to 2.9.1, if the quiz is deleted, the question category and any questions in the category remain in database. These orphaned question categories may be fixed by running the admin/cli/fix_orphaned_question_categories.php script with the --fix option.

==Search and replace text==

This script can be used to search and replace text throughout the whole database. Use carefully and backup first always. More info in [[Search and replace tool]].

php admin/tool/replace/cli/replace.php --search=//oldsitehost --replace=//newsitehost

==See also==

* MDL-35736 - Manage plugins via command line
* MDL-36237 - Resort course list via CLI
* [http://moosh-online.com/ MOOSH] - MOOdle SHell. It is a commandline tool that will allow you to perform most common Moodle tasks.

[[fr:Administration en ligne de commande]]
[[de:Administration über Kommandozeile]]
[[ja:コマンドライン経由の管理]]
[[es:Administración por línea de comando]]

Administration via command line

2016-02-01T14:08:17Z

Vbarcaru: /* Purge caches */

{{Installing Moodle}}
==Running CLI scripts==
If you have shell access to your web server, you may find various CLI (command line interface) scripts useful during Moodle administration. Core admin CLI tools are located in the <code>admin/cli/*</code> folder. Other plugins provide their CLI functionality via scripts in their own cli folder. For example, the enrol_db sync script is located in <code>enrol/db/cli/</code>.

To avoid problems with access control, you should run them as the owner of the web server process. It is especially important for CLI installation and upgrade as they create new files in moodledata directory and the web server has to have write access to them. In Linux distributions, the user that runs the web server is usually apache or wwrun or httpd or something similar. As a root, you will probably want to execute Moodle CLI scripts like this:

$ cd /path/to/your/moodle/dir
$ sudo -u apache /usr/bin/php admin/cli/somescript.php --params

Most of the scripts accept common --help (or -h) parameter to display the full usage information, for example:

$ sudo -u apache /usr/bin/php admin/cli/install.php --help

== Upgrading ==

Moodle can be upgraded from the command line. As with the installation script, there is either interactive or non-interactive mode of the upgrade. The script itself does not put the site into the maintenance mode, you have to do it on your own. Also, the script does not backup any data (if you read this page, you probably have some own scripts to backup your moodledata and the database, right?)

$ sudo -u apache /usr/bin/php admin/cli/upgrade.php

Upgrading via command line is a very comfortable way of Moodle upgrade if you use Git checkout of the Moodle source code (see [[Git for Administrators]]). See the following procedure how to upgrade your site within several seconds to the most recent version while preserving your eventual local customizations tracked in git repository:

$ cd /var/www/sites/moodle/htdocs/
$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enable
$ git pull
$ sudo -u apache /usr/bin/php admin/cli/upgrade.php
$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --disable

== Installation ==

There are two modes of installing Moodle from the command line. In interactive mode, the install script asks you for all data needed to properly set up new Moodle site. In non-interactive mode, you must provide all required data as the script parameters and then the new site is installed silently. The parameters can be passed in the interactive mode, too. The provided values are then used as the default values during the interactive session.

$ sudo -u apache /usr/bin/php admin/cli/install.php --lang=cs

{{New features}}If required, the database install may be skipped, with just config.php populated.

$ sudo -u apache /usr/bin/php admin/cli/install.php --skip-database

== Maintenance mode ==

To switch your site into the maintenance mode via CLI, you can use

$ sudo -u apache /usr/bin/php admin/cli/maintenance.php --enable

To turn maintenance mode off, just execute the same script with --disable parameter.

== Offline mode ==

In some situations, you may want to switch your Moodle site into offline mode so that it is not accessible via the web but you can not stop the web server completely (typically because there are other web pages and applications running there). If a file called <code>climaintenance.html</code> exists in the root folder of moodledata directory, Moodle will automatically display the contents of that file instead of any other page.

$ cd /var/www/sites/moodle/moodledata/
$ echo '<h1>Sorry, maintenance in progress</h1>' > climaintenance.html

You can prepare a nice formatted HTML page to inform your users about the server being down and keep in the moodledata directory under a name like <code>climaintenance.off</code> and rename it to the <code>climaintenance.html</code> if needed.

== Custom site defaults ==

During the install and upgrade via CLI, Moodle sets the administration variables to the default values. You can use different defaults. See MDL-17850 for details. Shortly, all you need to do is to add a file <code>local/defaults.php</code> into your Moodle installation. The format of the file is like

<code php>
<?php
$defaults['pluginname']['settingname'] = 'settingvalue'; // for plugins
$defaults['moodle']['settingname'] = 'settingvalue'; // for core settings
</code>

These defaults are used during install, upgrade and are also displayed as defaults on Site administration pages.

== Reset user password ==

If you happen to forget your admin password (or you want to set a password for any other user on the site), you can use reset_password.php script. The script sets the correctly salted password for the given user.

$ sudo -u apache /usr/bin/php admin/cli/reset_password.php

== MySQL storage engine conversion ==

If you run your Moodle site with MySQL database backend and use the default MyISAM as the storage engine for your tables, you may want to convert them to use some more reliable engine like InnoDB (actually, you should want to switch to PostgreSQL ;-) anyway).

$ sudo -u apache /usr/bin/php admin/cli/mysql_engine.php --engine=InnoDB

==Converting InnoDB tables to Barracuda==

Sites using MySQL with database tables using Antelope as the file format are recommended to convert the tables to the Barracuda file format.

This is because tables using Antelope as the file format cannot handle more than 10 text columns. This file formats only supports ''compact'' and ''redundant'' row formats for backward compatibility reasons. This may cause a problem on larger sites when restoring a course, in which case the following error will be displayed:

Row size too large (>8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help.

Barracuda is the newest innoDB file format. In addition to supporting ''compact'' and ''redundant'' row formats, Barracuda also supports ''compressed'' and ''dynamic'' row formats.

However, converting tables to Barracuda is only recommended, and not required, since not all MySQL users are affected. (It may only be a problem for larger sites.)

===Tool for converting tables===

A command line tool is included in Moodle for converting tables to Barracuda.

To view tables requiring conversion, use the list option:

$ php admin/cli/mysql_compressed_rows.php --list

Here is an example output:

mdl_data Compact (needs fixing)
mdl_data_fields Compact (needs fixing)
mdl_enrol_paypal Compact (needs fixing)

To proceed with the conversion, run the command using the fix option:

$ php admin/cli/mysql_compressed_rows.php --fix

Successful table conversion will be reported in the output, for example:

mdl_data ... Compressed
mdl_data_fields ... Compressed
mdl_enrol_paypal ... Compressed

Please note that the commands must be executed on your moodle directory. Once tables are fixed, the warning message will no longer be displayed.

For further information on InnoDB file formats see the [http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_antelope MySQL InnoDB glossary - Antelope] and the [http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_barracuda MySQL InnoDB glossary - Barracuda].

== Running cron via command line ==

In versions 1.x, you could execute admin/cron.php either from command line or via the web. Since Moodle 2.0, only admin/cli/cron.php script can be run via command line.

== Scheduled tasks ==

Scheduled tasks are automatically run by the cron script, but the specific tasks which run on each cron iteration are determined by the scheduled tasks configuration. It is possible to override the scheduled tasks configuration and run a single scheduled task immediately using the admin/tool/task/cli/schedule_task.php script.

This script accepts the following arguments:

--list - list all the known scheduled tasks. The tasks are listed by the class name used to run the task. This class name is required as the argument to the next option in order to run a specific task immediately.

--execute=<task> - Runs a single scheduled task immediately - regardless of scheduling settings. This will even run disabled tasks. Tasks will still use locking to prevent concurrent execution of the same task - even on clusters. The format of the <task> argument must be the same as returned by the --list option above.

'''Note:''' You must escape the "\" with an extra \ when using the --execute command. Take the following for example:

<pre>php schedule_task.php --list</pre>

will return something like:

<pre>
== List of scheduled tasks (http://yourserver.com/moodle) ==
\enrol_imsenterprise\task\cron_task 10 * * * * * ASAP
\logstore_legacy\task\cleanup_task * 5 * * * * ASAP
\logstore_standard\task\cleanup_task * 4 * * * * Wednesday, November 12, 2014, 4:35 AM
\mod_forum\task\cron_task * * * * * * ASAP
\core\task\automated_backup_task 50 * * * * * ASAP

...
</pre>

To run the first task in that list, you would execute

<pre>php schedule_task.php --execute=\\enrol_imsenterprise\\task\\cron_task</pre>

==Database transfer==

A command line script for [[Database transfer]] may be found in ''admin/tool/dbtransfer/cli/migrate.php''.

php admin/cli/purge_caches.php

==Fix course / module sequences==

In rare cases (such as after upgrading from a very old version of Moodle), the course / section / module sequence data can be out of sync. This can cause various problems for affected courses, such as sections not appearing, backups failing, pages not displaying etc. There is a specific check to check for errors caused by this problem, and to fix the data in the database if they are found. To run this script please use the command below:

php admin/cli/fix_course_sequence.php -c=* --fix

This will check every course in Moodle and report which ones had errors and were fixed.

==Fix orphaned question categories==

When a quiz is created, a new question category for the quiz is automatically created. In versions of Moodle prior to 2.9.1, if the quiz is deleted, the question category and any questions in the category remain in database. These orphaned question categories may be fixed by running the admin/cli/fix_orphaned_question_categories.php script with the --fix option.

==Search and replace text==

This script can be used to search and replace text throughout the whole database. Use carefully and backup first always. More info in [[Search and replace tool]].

php admin/tool/replace/cli/replace.php --search=//oldsitehost --replace=//newsitehost

==See also==

* MDL-35736 - Manage plugins via command line
* MDL-36237 - Resort course list via CLI
* [http://moosh-online.com/ MOOSH] - MOOdle SHell. It is a commandline tool that will allow you to perform most common Moodle tasks.

[[fr:Administration en ligne de commande]]
[[de:Administration über Kommandozeile]]
[[ja:コマンドライン経由の管理]]
[[es:Administración por línea de comando]]

Quiz settings

2016-01-18T11:42:22Z

Vbarcaru: /* General */

{{Quiz}}
Creating a new quiz is a two-step process. In the first step, you create the quiz activity and set its options which specify the rules for interacting with the quiz. In the second step you add questions to the quiz.
This page describes the options you can set for the quiz activity. The page [[Building Quiz]] describes how to set up the questions for the quiz.

==Quiz administration==
When you first set up your quiz from ''Add an activity or resource > Quiz'', (or, if you don't have this link, the dropdown ''Add an activity>Quiz'') you will get the following settings, (which can also be changed later in the Edit Settings link of the Quiz administration settings block) All settings may expanded by clicking the "Expand all" link top right.

==General==
Rezolvarea de ecuații și sisteme de ecuații.
De rezolvat ecuațiile-

==Timing==
{{Note|You can change quiz availability and duration for different groups or users in the Group or User override sections of the Quiz Administration settings block .}}
;Open the quiz
:You can specify times when the quiz is accessible for people to make attempts. Before the opening time the quiz will be unavailable to students. They will be able to view the quiz introduction but will not be able to view the questions. Quizzes with start times in the future diasplay both the open and close date for students.
;Close the quiz
:After the closing time, the students will not be able to start new attempts. Answers that the student submits after the quiz closing date will be saved but they will not be marked.
: Even after the quiz has closed students will still be able to see the quiz description and review their attempts. What exactly they will see depends on the settings you choose for review options (see below).
;Time limit
:By default, quizzes do not have a time limit, which allows students as much time as they need to complete the quiz. If you do specify a time limit, several things are done to try and ensure that quizzes are completed within that time:

[[File:quiz timer.png|thumb|Navigation block showing quiz timer]]

# A countdown timer is shown in the quiz navigation block
# When the timer has run out, the quiz is submitted automatically with whatever answers have been filled in so far
# If a student manages to cheat and goes over the allotted time, no marks are awarded for any answers entered after the time ran out
;When time expires..

There are three options as to what will happen when the time limit is up. Choose the one you need from the dropdown menu:
# Open attempts are submitted automatically (This is the default)
# There is a grace period when open attempts can be submitted, but no more questions answered
# Attempts must be submitted before time expires, or they are not counted

If you select "''There is a grace period...''" then you can check the box to enable the "Submission grace period" and specify a period of time during which learners may still submit the quiz after the time is up.

===Examples of how timing is handled===

#A student starts a quiz at noon. The quiz has a one-hour time-limit, and a 1 hour delay between attempts. The student gets distracted, and so actually does not submit (using the overdue handling) until 1:30pm. ''They are allowed to start their second attempt at 2. pm''
#The quiz count-down timer submits a student's quiz attempt at the last second when time expires. Because the server is heavily loaded, it takes 30 seconds to process the student's attempt. ''The submission is accepted nonetheless.''
#Same situation as above but with a 120 second delay: ''The submission is rejected.''
#The delay is not because of server load but because the student found a way to cheat the timer. ''Moodle cannot know what causes a delay.The behaviour is controlled by the admin setting(quiz | graceperiodmin), 60 seconds by default.''
#A student is a member of 3 groups,all of which have different override settings. Which limits will apply to this student? ''If there is any user-specific override, then that is used, and the group overrides for that setting are not used at all. Otherwise, if there are multiple group overrides, the most generous values are used (the earliest open date, the latest close date, the longest time limit, the most number of attempts, and the student can type any of the passwords).''

==Grade==
;Grade category
If you have categories in your gradebook, select the one you wish the quiz to be in here.
;Attempts allowed
:Students may be allowed to have multiple attempts at a quiz. This can help make the process of taking the quiz more of an educational activity rather than simply an assessment.
{{Note|You can change the allowed number of attempts for different groups or users in the Group or User override sections of the Quiz Administration settings block.}}
;Grade to pass
Here you can set a passing grade for the quiz. This may be connected with [[Activity completion]] and [[Conditional activities]] such that a student will not be able to access a follow up activity until they have passed the quiz.
;Grading method
:When multiple attempts are allowed, there are different ways you can use the grades to calculate the student's final grade for the quiz.
* Highest grade - the final grade is the highest (best) grade in any attempt
* Average grade - the final grade is the average (simple mean) grade of all attempts
* First grade - the final grade is the grade earned on the first attempt (other attempts are ignored)
* Last grade - the final grade is the grade earned on the most recent attempt only

==Layout==
;New page
:For longer quizzes it makes sense to stretch the quiz over several pages by limiting the number of questions per page. When adding questions to the quiz, page breaks will automatically be inserted according to the setting you choose here. However, you will also be able to move page breaks around by hand later on the editing page.
:'''''Note that changing this setting has no effect on questions you have already added to the quiz'''''. The setting will only apply to questions you add subsequently. To change the page breaks in an existing quiz, you need to go to the quiz editing screen, tick the 'Show page breaks' checkbox, then use the repaginate control.
;Navigation method (available by clicking ''Show More'')

Choose ''Sequential'' instead of ''Free'', if you want to force the student to progress through the questions in order and not go back to a previous question or skip to a later one.

==Question behaviour==
;How questions behave
:See [[Question behaviours]].
;Allow redo within an attempt (available by clicking "Show more")
:If using Interactive or Immediate feedback mode, enabling this setting means students can try a question again even if they have used up their allowed attempts. This is helpful if they wish to learn from the feedback given at the end of their attempts. They will be given a different question from the one they were working on previously if there are other questions available. A student's grade for that question slot is based on the most recent question they have started.
;Each attempt builds on the last (available by clicking "Show more")
:If multiple attempts are allowed and this setting is set to Yes, then each new attempt contains the results of the previous attempt. This allows the student on the new attempt to concentrate on just those questions that were answered incorrectly on the previous attempt. If this option is chosen then each attempt by a particular student uses the same questions in the same order, independent of randomization settings. To show a fresh quiz on every attempt, select No for this setting.

==Review options==
(These settings are collapsed by default)

[[File:quizreview.png|thumb|600px|Review options expanded]]

This section controls what information students will be shown when they review their past attempts at the quiz, and during the attempt in adaptive mode. It is a matrix with check boxes.

The various pieces of information that can be controlled are:
; The attempt: Will show how the student responded to each question.
; Whether correct: Displays whether the students response to each question is correct or incorrect.
; Marks: Reveals the marks awarded to the student and the grade for the quiz.
; Specific feedback: Will show the feedback for the response to the answer as set when adding the question to the quiz. Each response to a question can have feedback for both correct and incorrect answers.
; General feedback: Displays the general feedback for the whole question as set when adding the question to the quiz. You can use the general feedback to give students some background to what knowledge the question was testing.
; Right answer: Reveals the correct answer to each question, whether the student answered correctly or not (See note below).
; Overall feedback: Displays feedback for the entire quiz as set in the quiz settings (See note below).

For each of the above items, you can determine the timeframe when the students will see them:
; During the attempt : is only available when ''‘How questions behave’'' has been set to ''‘Immediate feedback’'', ''‘Immediate feedback with CBM’'' and ''‘Interactive with multiple tries’''. If set to one of these options then a ''‘Check’'' button will appear below the answer and when clicked the student will submit that response and then receive immediate feedback.
; Immediately after the attempt : means within 2 minutes of the student clicking "submit all and finish".
; Later, while the quiz is still open : means after 2 minutes, but before the close date (if the quiz does not have a close date, this phase never ends).
; After the quiz is closed : means what it says (you never get here for quizzes without a close date).

:''Tip:'' Checking any of the boxes in the timeframe row, will reveal the test to the student. For example, to allow students to see their quiz immediately after taking it but not later, make sure none of the boxes in "Later" or "After" rows are checked. The student will be able to see their grade but not get into the quiz.

Note: Currently, the Answers display is a bit inconsistent between different question types. For example, the matching question type shows students which of their responses are correct, but does not tell them the right answer for the ones they got wrong. The short answer and multiple choices question types do tell the student what the correct answer is.

Users with the capability 'View hidden grades' [[Capabilities/moodle/grade:viewhidden|moodle/grade:viewhidden]] (typically teachers and administrators) are not affected by these settings and will always by able to review all information about a student's attempt at any time.

In your list of review options, you must have 'The attempt' (the first option in the lists) selected before you can enable the options to show 'Whether correct', 'Specific feedback', 'General feedback', and 'Right answer'. If you choose not to let the students review the attempt, your only options are to display 'Marks' and 'Overall feedback'.

==Appearance==
;Show the user's picture
:It is now possible, when displaying the user's profile picture for proctoring purposes, to choose whether a large image or thumbnail will be displayed.
;Decimal places in grades
:This option determines how many digits will be shown after the decimal separator (see [[dev:Translation_langconfig|langconfig]] ) when the grade is displayed. A setting of 0 for example means that the grades are displayed as integers. This setting is only used for the display of grades, not for the display or marking of answers.

==Extra restrictions on attempts==
;Require password
:If you specify a password in here then participants must enter the same password before they are allowed to make an attempt on the quiz. This is useful to give only a selected group of students access to the quiz.
;Require network address
:You can restrict access for a quiz to particular subnets on the LAN or Internet by specifying a comma-separated list of partial or full IP address numbers. This is especially useful for a proctored (invigilated) quiz, where you want to be sure that only people in a certain room are able to access the quiz. For example: 192.168. , 231.54.211.0/20, 231.3.56.211

:There are three types of numbers you can use (you can not use text based domain names like example.com):

# Full IP addresses, such as 192.168.10.1 which will match a single computer (or proxy).
# Partial addresses, such as 192.168 which will match anything starting with those numbers.
# CIDR notation, such as 231.54.211.0/20 which allows you to specify more detailed subnets.

:Spaces are ignored.

;Enforced delay between attempts
:You can set a time (from seconds to weeks) between the first and second attempt of a quiz. You can also (or alternatively) set a time from seconds to weeks for subsequent attempts after the second attempt. Thus, you might allow a student to take the quiz twice immediately with no delay, but if they want to improve their score with a third attempt, they are forced to wait a week and use the time for extra revision.

;Browser security
:This is by default an advanced field, visible by clicking "Show advanced".
:The options in this section offer various ways to try to restrict how students may try to 'cheat' while attempting a quiz. However, this is not a simple issue, and what in one situation is considered 'cheating' may, in another situation, just be effective use of information technology. (For example, the ability to quickly find answers using a search engine.)

::Note also that this is not just at problem of technology with a technical solution. Cheating has been going on since long before computers, and while computers make certain actions, like copy and paste, easier, they also make it easier for teachers to detect cheating - for example using the quiz reports. The options provided here are not fool-proof, and while they do make some forms of cheating harder for students, they also make it more inconvenient for students to attempt the quizzes, and they are not fool-proof.

:'''Full screen pop-up with some JavaScript security'''

:There is a limit to what the quiz, which runs on a web server, can do to restrict what the student sitting at their computer can do while attempting the quiz. However, this option does what is possible:

:* The quiz will only start if the student has a JavaScript-enabled web-browser.
:* The quiz appears in a fullscreen popup window that covers all the other windows and has no course navigation controls.

|[[File:seb24.png|thumb|Student view of quiz question with full screen popup.]]

:* The students are prevented, as far as is possible, from using facilities like copy and paste.

:'''Require the use of Safe Exam Browser'''

:This option will only appear if your administrator has enabled it in ''Site administration > Development > Experimental > Experimental settings''.

:[[Safe exam browser|Safe Exam Browser]] is a customised web browser that must be downloaded and installed on the computer that the student uses to attempt the quiz. It restricts student use more effectively than a pop up window option. Features include full screen, without web navigation options, shortcut keys including copy and paste are disabled and of course surfing the web during an exam.

==Overall feedback==
Overall feedback is shown to a student after they have completed an attempt at the quiz. The text that is shown can depend on the grade the student got. Click "Show editing tools" to display the rich text editor, and drag the bottom right of the text box out to expand it.

For example, if you entered:

:Grade boundary: 100%
:Feedback: "Well done"
:Grade boundary: 40%
:Feedback: "Please study this week's work again"
:Grade boundary: 0%

Then students who score between 100% and 40% will see the "Well done" message, and those who score between 39.99% and 0% will see "Please study this week's work again". That is, the grade boundaries define ranges of grades, and each feedback string is displayed to scores within the appropriate range.

Grade boundaries can be specified either as a percentage, for example "31.41%", or as a number, for example "7". If your quiz is out of 10 marks, a grade boundary of 7 means 7/10 or better.

Note that the maximum and minimum grade boundaries (100% and 0%) are set automatically.

You can set as many or as few grade boundaries as you wish. The form allows you up to 5 ranges at first, but you can add more by clicking the "Add 3 fields to form" button underneath.

If you're getting confusing error messages about a boundary being out of sequence (when it's obviously *in* sequence), or "boundaries must be between 0% and 100%" (and they are) -- check that the Maximum Grade for this quiz is set to something greater than zero.

==Outcomes==
This setting will only appear if [[Outcomes]] have been enabled by the administrator and are used in the course. See [[Outcomes]] for how to remove an outcome once it has been added to a quiz.

==Common module settings==
(These settings are collapsed by default)
See [[Common module settings]]

==Restrict access/Activity completion==
(These settings are collapsed by default)

The Restrict access and Activity completion settings are visible if [[Conditional activities]] and [[Activity completion]] have been enabled in the site and the course.
===Quiz completion===

The following automatic activity completion conditions apply to the quiz:

:''Require view'' - the student clicks on the quiz to view it
:''Require grade'' - the student obtains a grade
:''Require a passing grade'' - a 'Grade to pass' is specified for the quiz in the gradebook.
:''All available attempts completed'' - a certain number of attempts were allowed on the quiz and the student has completed them all.

==Group and User overrides==

[[File:overridesquiz.png|thumb|Location of overrides]]

Dates, timing and number of allowed attempts may be changed for individual users or groups by following the links ''Group Overrides'' or ''User Overrides'' in the Quiz Administration settings block.

===Group overrides===
To change a quiz setting for a particular group, click the "add group override" button in ''Quiz Administration>Group overrides'', make the changes you wish and save or enter another override.

===User overrides===
To change a quiz setting for a particular user or users, click the "add user override"button in ''Quiz Administration>User overrides'', make the changes you wish and save or enter another override.

==Site administration settings==

The quiz module has additional settings which may be changed by an administrator in ''Administration > Site administration > Plugins > Activity modules > Quiz''.

The time period settings for a quiz (such as time limit, submission grace period, autosave period and so on) can be set here with a duration of seconds, minutes, hours, days or weeks. These defaults will then be used when new quizzes are created.

;Autosave period
:If enabled, student responses will be saved at regular period according to the selection here. the default is one minute. This is useful so that students don't lose work but does increase the load on the server.

How questions behave can be configured in ''Administration>Site administration>Plugins>Question behaviours>Manage question
behaviours''

==See also==
*[https://youtu.be/y8HOnsKt6qg The Moodle Quiz Activity] MoodleBites video on YouTube

[[fr:Ajouter/modifier un test]]
[[de:Test konfigurieren]]
[[es:Configuraciones del examen]]

MoodleDocs:Overview

2016-01-18T09:27:22Z

Vbarcaru: /* English */

==Romînă==

[https://docs.moodle.org/401/en/ 3.0 EN documentation] 
[https://docs.moodle.org/29/en/ 2.9 EN documentation] 
[https://docs.moodle.org/29/en/ 2.8 EN documentation] 
[https://docs.moodle.org/27/en/ 2.7 EN documentation] 
[https://docs.moodle.org/26/en/ 2.6 EN documentation] 
[https://docs.moodle.org/25/en/ 2.5 EN documentation] 
[https://docs.moodle.org/24/en/ 2.4 EN documentation] 
[https://docs.moodle.org/23/en/ 2.3 EN documentation] 
[https://docs.moodle.org/22/en/ 2.2 EN documentation] 
[https://docs.moodle.org/21/en/ 2.1 EN documentation] 
[https://docs.moodle.org/20/en/ 2.0 EN documentation] 
[https://docs.moodle.org/19/en/ 1.9 EN documentation]

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

MoodleDocs:Overview

2016-01-18T09:26:57Z

Vbarcaru:

==English==

[https://docs.moodle.org/401/en/ 3.0 EN documentation] 
[https://docs.moodle.org/29/en/ 2.9 EN documentation] 
[https://docs.moodle.org/29/en/ 2.8 EN documentation] 
[https://docs.moodle.org/27/en/ 2.7 EN documentation] 
[https://docs.moodle.org/26/en/ 2.6 EN documentation] 
[https://docs.moodle.org/25/en/ 2.5 EN documentation] 
[https://docs.moodle.org/24/en/ 2.4 EN documentation] 
[https://docs.moodle.org/23/en/ 2.3 EN documentation] 
[https://docs.moodle.org/22/en/ 2.2 EN documentation] 
[https://docs.moodle.org/21/en/ 2.1 EN documentation] 
[https://docs.moodle.org/20/en/ 2.0 EN documentation] 
[https://docs.moodle.org/19/en/ 1.9 EN documentation]

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

Quiz settings

2016-01-18T08:38:15Z

Vbarcaru: /* General */

{{Quiz}}
Creating a new quiz is a two-step process. In the first step, you create the quiz activity and set its options which specify the rules for interacting with the quiz. In the second step you add questions to the quiz.
This page describes the options you can set for the quiz activity. The page [[Building Quiz]] describes how to set up the questions for the quiz.

==Quiz administration==
When you first set up your quiz from ''Add an activity or resource > Quiz'', (or, if you don't have this link, the dropdown ''Add an activity>Quiz'') you will get the following settings, (which can also be changed later in the Edit Settings link of the Quiz administration settings block) All settings may expanded by clicking the "Expand all" link top right.

==General==
Rezolvarea ecuațiilor și sistemelor de ecuații

==Timing==
{{Note|You can change quiz availability and duration for different groups or users in the Group or User override sections of the Quiz Administration settings block .}}
;Open the quiz
:You can specify times when the quiz is accessible for people to make attempts. Before the opening time the quiz will be unavailable to students. They will be able to view the quiz introduction but will not be able to view the questions. Quizzes with start times in the future diasplay both the open and close date for students.
;Close the quiz
:After the closing time, the students will not be able to start new attempts. Answers that the student submits after the quiz closing date will be saved but they will not be marked.
: Even after the quiz has closed students will still be able to see the quiz description and review their attempts. What exactly they will see depends on the settings you choose for review options (see below).
;Time limit
:By default, quizzes do not have a time limit, which allows students as much time as they need to complete the quiz. If you do specify a time limit, several things are done to try and ensure that quizzes are completed within that time:

[[File:quiz timer.png|thumb|Navigation block showing quiz timer]]

# A countdown timer is shown in the quiz navigation block
# When the timer has run out, the quiz is submitted automatically with whatever answers have been filled in so far
# If a student manages to cheat and goes over the allotted time, no marks are awarded for any answers entered after the time ran out
;When time expires..

There are three options as to what will happen when the time limit is up. Choose the one you need from the dropdown menu:
# Open attempts are submitted automatically (This is the default)
# There is a grace period when open attempts can be submitted, but no more questions answered
# Attempts must be submitted before time expires, or they are not counted

If you select "''There is a grace period...''" then you can check the box to enable the "Submission grace period" and specify a period of time during which learners may still submit the quiz after the time is up.

===Examples of how timing is handled===

#A student starts a quiz at noon. The quiz has a one-hour time-limit, and a 1 hour delay between attempts. The student gets distracted, and so actually does not submit (using the overdue handling) until 1:30pm. ''They are allowed to start their second attempt at 2. pm''
#The quiz count-down timer submits a student's quiz attempt at the last second when time expires. Because the server is heavily loaded, it takes 30 seconds to process the student's attempt. ''The submission is accepted nonetheless.''
#Same situation as above but with a 120 second delay: ''The submission is rejected.''
#The delay is not because of server load but because the student found a way to cheat the timer. ''Moodle cannot know what causes a delay.The behaviour is controlled by the admin setting(quiz | graceperiodmin), 60 seconds by default.''
#A student is a member of 3 groups,all of which have different override settings. Which limits will apply to this student? ''If there is any user-specific override, then that is used, and the group overrides for that setting are not used at all. Otherwise, if there are multiple group overrides, the most generous values are used (the earliest open date, the latest close date, the longest time limit, the most number of attempts, and the student can type any of the passwords).''

==Grade==
;Grade category
If you have categories in your gradebook, select the one you wish the quiz to be in here.
;Attempts allowed
:Students may be allowed to have multiple attempts at a quiz. This can help make the process of taking the quiz more of an educational activity rather than simply an assessment.
{{Note|You can change the allowed number of attempts for different groups or users in the Group or User override sections of the Quiz Administration settings block.}}
;Grade to pass
Here you can set a passing grade for the quiz. This may be connected with [[Activity completion]] and [[Conditional activities]] such that a student will not be able to access a follow up activity until they have passed the quiz.
;Grading method
:When multiple attempts are allowed, there are different ways you can use the grades to calculate the student's final grade for the quiz.
* Highest grade - the final grade is the highest (best) grade in any attempt
* Average grade - the final grade is the average (simple mean) grade of all attempts
* First grade - the final grade is the grade earned on the first attempt (other attempts are ignored)
* Last grade - the final grade is the grade earned on the most recent attempt only

==Layout==
;New page
:For longer quizzes it makes sense to stretch the quiz over several pages by limiting the number of questions per page. When adding questions to the quiz, page breaks will automatically be inserted according to the setting you choose here. However, you will also be able to move page breaks around by hand later on the editing page.
:'''''Note that changing this setting has no effect on questions you have already added to the quiz'''''. The setting will only apply to questions you add subsequently. To change the page breaks in an existing quiz, you need to go to the quiz editing screen, tick the 'Show page breaks' checkbox, then use the repaginate control.
;Navigation method (available by clicking ''Show More'')

Choose ''Sequential'' instead of ''Free'', if you want to force the student to progress through the questions in order and not go back to a previous question or skip to a later one.

==Question behaviour==
;How questions behave
:See [[Question behaviours]].
;Allow redo within an attempt (available by clicking "Show more")
:If using Interactive or Immediate feedback mode, enabling this setting means students can try a question again even if they have used up their allowed attempts. This is helpful if they wish to learn from the feedback given at the end of their attempts. They will be given a different question from the one they were working on previously if there are other questions available. A student's grade for that question slot is based on the most recent question they have started.
;Each attempt builds on the last (available by clicking "Show more")
:If multiple attempts are allowed and this setting is set to Yes, then each new attempt contains the results of the previous attempt. This allows the student on the new attempt to concentrate on just those questions that were answered incorrectly on the previous attempt. If this option is chosen then each attempt by a particular student uses the same questions in the same order, independent of randomization settings. To show a fresh quiz on every attempt, select No for this setting.

==Review options==
(These settings are collapsed by default)

[[File:quizreview.png|thumb|600px|Review options expanded]]

This section controls what information students will be shown when they review their past attempts at the quiz, and during the attempt in adaptive mode. It is a matrix with check boxes.

The various pieces of information that can be controlled are:
; The attempt: Will show how the student responded to each question.
; Whether correct: Displays whether the students response to each question is correct or incorrect.
; Marks: Reveals the marks awarded to the student and the grade for the quiz.
; Specific feedback: Will show the feedback for the response to the answer as set when adding the question to the quiz. Each response to a question can have feedback for both correct and incorrect answers.
; General feedback: Displays the general feedback for the whole question as set when adding the question to the quiz. You can use the general feedback to give students some background to what knowledge the question was testing.
; Right answer: Reveals the correct answer to each question, whether the student answered correctly or not (See note below).
; Overall feedback: Displays feedback for the entire quiz as set in the quiz settings (See note below).

For each of the above items, you can determine the timeframe when the students will see them:
; During the attempt : is only available when ''‘How questions behave’'' has been set to ''‘Immediate feedback’'', ''‘Immediate feedback with CBM’'' and ''‘Interactive with multiple tries’''. If set to one of these options then a ''‘Check’'' button will appear below the answer and when clicked the student will submit that response and then receive immediate feedback.
; Immediately after the attempt : means within 2 minutes of the student clicking "submit all and finish".
; Later, while the quiz is still open : means after 2 minutes, but before the close date (if the quiz does not have a close date, this phase never ends).
; After the quiz is closed : means what it says (you never get here for quizzes without a close date).

:''Tip:'' Checking any of the boxes in the timeframe row, will reveal the test to the student. For example, to allow students to see their quiz immediately after taking it but not later, make sure none of the boxes in "Later" or "After" rows are checked. The student will be able to see their grade but not get into the quiz.

Note: Currently, the Answers display is a bit inconsistent between different question types. For example, the matching question type shows students which of their responses are correct, but does not tell them the right answer for the ones they got wrong. The short answer and multiple choices question types do tell the student what the correct answer is.

Users with the capability 'View hidden grades' [[Capabilities/moodle/grade:viewhidden|moodle/grade:viewhidden]] (typically teachers and administrators) are not affected by these settings and will always by able to review all information about a student's attempt at any time.

In your list of review options, you must have 'The attempt' (the first option in the lists) selected before you can enable the options to show 'Whether correct', 'Specific feedback', 'General feedback', and 'Right answer'. If you choose not to let the students review the attempt, your only options are to display 'Marks' and 'Overall feedback'.

==Appearance==
;Show the user's picture
:It is now possible, when displaying the user's profile picture for proctoring purposes, to choose whether a large image or thumbnail will be displayed.
;Decimal places in grades
:This option determines how many digits will be shown after the decimal separator (see [[dev:Translation_langconfig|langconfig]] ) when the grade is displayed. A setting of 0 for example means that the grades are displayed as integers. This setting is only used for the display of grades, not for the display or marking of answers.

==Extra restrictions on attempts==
;Require password
:If you specify a password in here then participants must enter the same password before they are allowed to make an attempt on the quiz. This is useful to give only a selected group of students access to the quiz.
;Require network address
:You can restrict access for a quiz to particular subnets on the LAN or Internet by specifying a comma-separated list of partial or full IP address numbers. This is especially useful for a proctored (invigilated) quiz, where you want to be sure that only people in a certain room are able to access the quiz. For example: 192.168. , 231.54.211.0/20, 231.3.56.211

:There are three types of numbers you can use (you can not use text based domain names like example.com):

# Full IP addresses, such as 192.168.10.1 which will match a single computer (or proxy).
# Partial addresses, such as 192.168 which will match anything starting with those numbers.
# CIDR notation, such as 231.54.211.0/20 which allows you to specify more detailed subnets.

:Spaces are ignored.

;Enforced delay between attempts
:You can set a time (from seconds to weeks) between the first and second attempt of a quiz. You can also (or alternatively) set a time from seconds to weeks for subsequent attempts after the second attempt. Thus, you might allow a student to take the quiz twice immediately with no delay, but if they want to improve their score with a third attempt, they are forced to wait a week and use the time for extra revision.

;Browser security
:This is by default an advanced field, visible by clicking "Show advanced".
:The options in this section offer various ways to try to restrict how students may try to 'cheat' while attempting a quiz. However, this is not a simple issue, and what in one situation is considered 'cheating' may, in another situation, just be effective use of information technology. (For example, the ability to quickly find answers using a search engine.)

::Note also that this is not just at problem of technology with a technical solution. Cheating has been going on since long before computers, and while computers make certain actions, like copy and paste, easier, they also make it easier for teachers to detect cheating - for example using the quiz reports. The options provided here are not fool-proof, and while they do make some forms of cheating harder for students, they also make it more inconvenient for students to attempt the quizzes, and they are not fool-proof.

:'''Full screen pop-up with some JavaScript security'''

:There is a limit to what the quiz, which runs on a web server, can do to restrict what the student sitting at their computer can do while attempting the quiz. However, this option does what is possible:

:* The quiz will only start if the student has a JavaScript-enabled web-browser.
:* The quiz appears in a fullscreen popup window that covers all the other windows and has no course navigation controls.

|[[File:seb24.png|thumb|Student view of quiz question with full screen popup.]]

:* The students are prevented, as far as is possible, from using facilities like copy and paste.

:'''Require the use of Safe Exam Browser'''

:This option will only appear if your administrator has enabled it in ''Site administration > Development > Experimental > Experimental settings''.

:[[Safe exam browser|Safe Exam Browser]] is a customised web browser that must be downloaded and installed on the computer that the student uses to attempt the quiz. It restricts student use more effectively than a pop up window option. Features include full screen, without web navigation options, shortcut keys including copy and paste are disabled and of course surfing the web during an exam.

==Overall feedback==
Overall feedback is shown to a student after they have completed an attempt at the quiz. The text that is shown can depend on the grade the student got. Click "Show editing tools" to display the rich text editor, and drag the bottom right of the text box out to expand it.

For example, if you entered:

:Grade boundary: 100%
:Feedback: "Well done"
:Grade boundary: 40%
:Feedback: "Please study this week's work again"
:Grade boundary: 0%

Then students who score between 100% and 40% will see the "Well done" message, and those who score between 39.99% and 0% will see "Please study this week's work again". That is, the grade boundaries define ranges of grades, and each feedback string is displayed to scores within the appropriate range.

Grade boundaries can be specified either as a percentage, for example "31.41%", or as a number, for example "7". If your quiz is out of 10 marks, a grade boundary of 7 means 7/10 or better.

Note that the maximum and minimum grade boundaries (100% and 0%) are set automatically.

You can set as many or as few grade boundaries as you wish. The form allows you up to 5 ranges at first, but you can add more by clicking the "Add 3 fields to form" button underneath.

If you're getting confusing error messages about a boundary being out of sequence (when it's obviously *in* sequence), or "boundaries must be between 0% and 100%" (and they are) -- check that the Maximum Grade for this quiz is set to something greater than zero.

==Outcomes==
This setting will only appear if [[Outcomes]] have been enabled by the administrator and are used in the course. See [[Outcomes]] for how to remove an outcome once it has been added to a quiz.

==Common module settings==
(These settings are collapsed by default)
See [[Common module settings]]

==Restrict access/Activity completion==
(These settings are collapsed by default)

The Restrict access and Activity completion settings are visible if [[Conditional activities]] and [[Activity completion]] have been enabled in the site and the course.
===Quiz completion===

The following automatic activity completion conditions apply to the quiz:

:''Require view'' - the student clicks on the quiz to view it
:''Require grade'' - the student obtains a grade
:''Require a passing grade'' - a 'Grade to pass' is specified for the quiz in the gradebook.
:''All available attempts completed'' - a certain number of attempts were allowed on the quiz and the student has completed them all.

==Group and User overrides==

[[File:overridesquiz.png|thumb|Location of overrides]]

Dates, timing and number of allowed attempts may be changed for individual users or groups by following the links ''Group Overrides'' or ''User Overrides'' in the Quiz Administration settings block.

===Group overrides===
To change a quiz setting for a particular group, click the "add group override" button in ''Quiz Administration>Group overrides'', make the changes you wish and save or enter another override.

===User overrides===
To change a quiz setting for a particular user or users, click the "add user override"button in ''Quiz Administration>User overrides'', make the changes you wish and save or enter another override.

==Site administration settings==

The quiz module has additional settings which may be changed by an administrator in ''Administration > Site administration > Plugins > Activity modules > Quiz''.

The time period settings for a quiz (such as time limit, submission grace period, autosave period and so on) can be set here with a duration of seconds, minutes, hours, days or weeks. These defaults will then be used when new quizzes are created.

;Autosave period
:If enabled, student responses will be saved at regular period according to the selection here. the default is one minute. This is useful so that students don't lose work but does increase the load on the server.

How questions behave can be configured in ''Administration>Site administration>Plugins>Question behaviours>Manage question
behaviours''

==See also==
*[https://youtu.be/y8HOnsKt6qg The Moodle Quiz Activity] MoodleBites video on YouTube

[[fr:Ajouter/modifier un test]]
[[de:Test konfigurieren]]
[[es:Configuraciones del examen]]

Quiz settings

2016-01-18T08:36:35Z

Vbarcaru: /* General */

{{Quiz}}
Creating a new quiz is a two-step process. In the first step, you create the quiz activity and set its options which specify the rules for interacting with the quiz. In the second step you add questions to the quiz.
This page describes the options you can set for the quiz activity. The page [[Building Quiz]] describes how to set up the questions for the quiz.

==Quiz administration==
When you first set up your quiz from ''Add an activity or resource > Quiz'', (or, if you don't have this link, the dropdown ''Add an activity>Quiz'') you will get the following settings, (which can also be changed later in the Edit Settings link of the Quiz administration settings block) All settings may expanded by clicking the "Expand all" link top right.

==General==
Rezolvarea ecuațiilor și sistemelor de ecuații
<math>X+38*y=25</math>
<math>2*x-y=32</math>

==Timing==
{{Note|You can change quiz availability and duration for different groups or users in the Group or User override sections of the Quiz Administration settings block .}}
;Open the quiz
:You can specify times when the quiz is accessible for people to make attempts. Before the opening time the quiz will be unavailable to students. They will be able to view the quiz introduction but will not be able to view the questions. Quizzes with start times in the future diasplay both the open and close date for students.
;Close the quiz
:After the closing time, the students will not be able to start new attempts. Answers that the student submits after the quiz closing date will be saved but they will not be marked.
: Even after the quiz has closed students will still be able to see the quiz description and review their attempts. What exactly they will see depends on the settings you choose for review options (see below).
;Time limit
:By default, quizzes do not have a time limit, which allows students as much time as they need to complete the quiz. If you do specify a time limit, several things are done to try and ensure that quizzes are completed within that time:

[[File:quiz timer.png|thumb|Navigation block showing quiz timer]]

# A countdown timer is shown in the quiz navigation block
# When the timer has run out, the quiz is submitted automatically with whatever answers have been filled in so far
# If a student manages to cheat and goes over the allotted time, no marks are awarded for any answers entered after the time ran out
;When time expires..

There are three options as to what will happen when the time limit is up. Choose the one you need from the dropdown menu:
# Open attempts are submitted automatically (This is the default)
# There is a grace period when open attempts can be submitted, but no more questions answered
# Attempts must be submitted before time expires, or they are not counted

If you select "''There is a grace period...''" then you can check the box to enable the "Submission grace period" and specify a period of time during which learners may still submit the quiz after the time is up.

===Examples of how timing is handled===

#A student starts a quiz at noon. The quiz has a one-hour time-limit, and a 1 hour delay between attempts. The student gets distracted, and so actually does not submit (using the overdue handling) until 1:30pm. ''They are allowed to start their second attempt at 2. pm''
#The quiz count-down timer submits a student's quiz attempt at the last second when time expires. Because the server is heavily loaded, it takes 30 seconds to process the student's attempt. ''The submission is accepted nonetheless.''
#Same situation as above but with a 120 second delay: ''The submission is rejected.''
#The delay is not because of server load but because the student found a way to cheat the timer. ''Moodle cannot know what causes a delay.The behaviour is controlled by the admin setting(quiz | graceperiodmin), 60 seconds by default.''
#A student is a member of 3 groups,all of which have different override settings. Which limits will apply to this student? ''If there is any user-specific override, then that is used, and the group overrides for that setting are not used at all. Otherwise, if there are multiple group overrides, the most generous values are used (the earliest open date, the latest close date, the longest time limit, the most number of attempts, and the student can type any of the passwords).''

==Grade==
;Grade category
If you have categories in your gradebook, select the one you wish the quiz to be in here.
;Attempts allowed
:Students may be allowed to have multiple attempts at a quiz. This can help make the process of taking the quiz more of an educational activity rather than simply an assessment.
{{Note|You can change the allowed number of attempts for different groups or users in the Group or User override sections of the Quiz Administration settings block.}}
;Grade to pass
Here you can set a passing grade for the quiz. This may be connected with [[Activity completion]] and [[Conditional activities]] such that a student will not be able to access a follow up activity until they have passed the quiz.
;Grading method
:When multiple attempts are allowed, there are different ways you can use the grades to calculate the student's final grade for the quiz.
* Highest grade - the final grade is the highest (best) grade in any attempt
* Average grade - the final grade is the average (simple mean) grade of all attempts
* First grade - the final grade is the grade earned on the first attempt (other attempts are ignored)
* Last grade - the final grade is the grade earned on the most recent attempt only

==Layout==
;New page
:For longer quizzes it makes sense to stretch the quiz over several pages by limiting the number of questions per page. When adding questions to the quiz, page breaks will automatically be inserted according to the setting you choose here. However, you will also be able to move page breaks around by hand later on the editing page.
:'''''Note that changing this setting has no effect on questions you have already added to the quiz'''''. The setting will only apply to questions you add subsequently. To change the page breaks in an existing quiz, you need to go to the quiz editing screen, tick the 'Show page breaks' checkbox, then use the repaginate control.
;Navigation method (available by clicking ''Show More'')

Choose ''Sequential'' instead of ''Free'', if you want to force the student to progress through the questions in order and not go back to a previous question or skip to a later one.

==Question behaviour==
;How questions behave
:See [[Question behaviours]].
;Allow redo within an attempt (available by clicking "Show more")
:If using Interactive or Immediate feedback mode, enabling this setting means students can try a question again even if they have used up their allowed attempts. This is helpful if they wish to learn from the feedback given at the end of their attempts. They will be given a different question from the one they were working on previously if there are other questions available. A student's grade for that question slot is based on the most recent question they have started.
;Each attempt builds on the last (available by clicking "Show more")
:If multiple attempts are allowed and this setting is set to Yes, then each new attempt contains the results of the previous attempt. This allows the student on the new attempt to concentrate on just those questions that were answered incorrectly on the previous attempt. If this option is chosen then each attempt by a particular student uses the same questions in the same order, independent of randomization settings. To show a fresh quiz on every attempt, select No for this setting.

==Review options==
(These settings are collapsed by default)

[[File:quizreview.png|thumb|600px|Review options expanded]]

This section controls what information students will be shown when they review their past attempts at the quiz, and during the attempt in adaptive mode. It is a matrix with check boxes.

The various pieces of information that can be controlled are:
; The attempt: Will show how the student responded to each question.
; Whether correct: Displays whether the students response to each question is correct or incorrect.
; Marks: Reveals the marks awarded to the student and the grade for the quiz.
; Specific feedback: Will show the feedback for the response to the answer as set when adding the question to the quiz. Each response to a question can have feedback for both correct and incorrect answers.
; General feedback: Displays the general feedback for the whole question as set when adding the question to the quiz. You can use the general feedback to give students some background to what knowledge the question was testing.
; Right answer: Reveals the correct answer to each question, whether the student answered correctly or not (See note below).
; Overall feedback: Displays feedback for the entire quiz as set in the quiz settings (See note below).

For each of the above items, you can determine the timeframe when the students will see them:
; During the attempt : is only available when ''‘How questions behave’'' has been set to ''‘Immediate feedback’'', ''‘Immediate feedback with CBM’'' and ''‘Interactive with multiple tries’''. If set to one of these options then a ''‘Check’'' button will appear below the answer and when clicked the student will submit that response and then receive immediate feedback.
; Immediately after the attempt : means within 2 minutes of the student clicking "submit all and finish".
; Later, while the quiz is still open : means after 2 minutes, but before the close date (if the quiz does not have a close date, this phase never ends).
; After the quiz is closed : means what it says (you never get here for quizzes without a close date).

:''Tip:'' Checking any of the boxes in the timeframe row, will reveal the test to the student. For example, to allow students to see their quiz immediately after taking it but not later, make sure none of the boxes in "Later" or "After" rows are checked. The student will be able to see their grade but not get into the quiz.

Note: Currently, the Answers display is a bit inconsistent between different question types. For example, the matching question type shows students which of their responses are correct, but does not tell them the right answer for the ones they got wrong. The short answer and multiple choices question types do tell the student what the correct answer is.

Users with the capability 'View hidden grades' [[Capabilities/moodle/grade:viewhidden|moodle/grade:viewhidden]] (typically teachers and administrators) are not affected by these settings and will always by able to review all information about a student's attempt at any time.

In your list of review options, you must have 'The attempt' (the first option in the lists) selected before you can enable the options to show 'Whether correct', 'Specific feedback', 'General feedback', and 'Right answer'. If you choose not to let the students review the attempt, your only options are to display 'Marks' and 'Overall feedback'.

==Appearance==
;Show the user's picture
:It is now possible, when displaying the user's profile picture for proctoring purposes, to choose whether a large image or thumbnail will be displayed.
;Decimal places in grades
:This option determines how many digits will be shown after the decimal separator (see [[dev:Translation_langconfig|langconfig]] ) when the grade is displayed. A setting of 0 for example means that the grades are displayed as integers. This setting is only used for the display of grades, not for the display or marking of answers.

==Extra restrictions on attempts==
;Require password
:If you specify a password in here then participants must enter the same password before they are allowed to make an attempt on the quiz. This is useful to give only a selected group of students access to the quiz.
;Require network address
:You can restrict access for a quiz to particular subnets on the LAN or Internet by specifying a comma-separated list of partial or full IP address numbers. This is especially useful for a proctored (invigilated) quiz, where you want to be sure that only people in a certain room are able to access the quiz. For example: 192.168. , 231.54.211.0/20, 231.3.56.211

:There are three types of numbers you can use (you can not use text based domain names like example.com):

# Full IP addresses, such as 192.168.10.1 which will match a single computer (or proxy).
# Partial addresses, such as 192.168 which will match anything starting with those numbers.
# CIDR notation, such as 231.54.211.0/20 which allows you to specify more detailed subnets.

:Spaces are ignored.

;Enforced delay between attempts
:You can set a time (from seconds to weeks) between the first and second attempt of a quiz. You can also (or alternatively) set a time from seconds to weeks for subsequent attempts after the second attempt. Thus, you might allow a student to take the quiz twice immediately with no delay, but if they want to improve their score with a third attempt, they are forced to wait a week and use the time for extra revision.

;Browser security
:This is by default an advanced field, visible by clicking "Show advanced".
:The options in this section offer various ways to try to restrict how students may try to 'cheat' while attempting a quiz. However, this is not a simple issue, and what in one situation is considered 'cheating' may, in another situation, just be effective use of information technology. (For example, the ability to quickly find answers using a search engine.)

::Note also that this is not just at problem of technology with a technical solution. Cheating has been going on since long before computers, and while computers make certain actions, like copy and paste, easier, they also make it easier for teachers to detect cheating - for example using the quiz reports. The options provided here are not fool-proof, and while they do make some forms of cheating harder for students, they also make it more inconvenient for students to attempt the quizzes, and they are not fool-proof.

:'''Full screen pop-up with some JavaScript security'''

:There is a limit to what the quiz, which runs on a web server, can do to restrict what the student sitting at their computer can do while attempting the quiz. However, this option does what is possible:

:* The quiz will only start if the student has a JavaScript-enabled web-browser.
:* The quiz appears in a fullscreen popup window that covers all the other windows and has no course navigation controls.

|[[File:seb24.png|thumb|Student view of quiz question with full screen popup.]]

:* The students are prevented, as far as is possible, from using facilities like copy and paste.

:'''Require the use of Safe Exam Browser'''

:This option will only appear if your administrator has enabled it in ''Site administration > Development > Experimental > Experimental settings''.

:[[Safe exam browser|Safe Exam Browser]] is a customised web browser that must be downloaded and installed on the computer that the student uses to attempt the quiz. It restricts student use more effectively than a pop up window option. Features include full screen, without web navigation options, shortcut keys including copy and paste are disabled and of course surfing the web during an exam.

==Overall feedback==
Overall feedback is shown to a student after they have completed an attempt at the quiz. The text that is shown can depend on the grade the student got. Click "Show editing tools" to display the rich text editor, and drag the bottom right of the text box out to expand it.

For example, if you entered:

:Grade boundary: 100%
:Feedback: "Well done"
:Grade boundary: 40%
:Feedback: "Please study this week's work again"
:Grade boundary: 0%

Then students who score between 100% and 40% will see the "Well done" message, and those who score between 39.99% and 0% will see "Please study this week's work again". That is, the grade boundaries define ranges of grades, and each feedback string is displayed to scores within the appropriate range.

Grade boundaries can be specified either as a percentage, for example "31.41%", or as a number, for example "7". If your quiz is out of 10 marks, a grade boundary of 7 means 7/10 or better.

Note that the maximum and minimum grade boundaries (100% and 0%) are set automatically.

You can set as many or as few grade boundaries as you wish. The form allows you up to 5 ranges at first, but you can add more by clicking the "Add 3 fields to form" button underneath.

If you're getting confusing error messages about a boundary being out of sequence (when it's obviously *in* sequence), or "boundaries must be between 0% and 100%" (and they are) -- check that the Maximum Grade for this quiz is set to something greater than zero.

==Outcomes==
This setting will only appear if [[Outcomes]] have been enabled by the administrator and are used in the course. See [[Outcomes]] for how to remove an outcome once it has been added to a quiz.

==Common module settings==
(These settings are collapsed by default)
See [[Common module settings]]

==Restrict access/Activity completion==
(These settings are collapsed by default)

The Restrict access and Activity completion settings are visible if [[Conditional activities]] and [[Activity completion]] have been enabled in the site and the course.
===Quiz completion===

The following automatic activity completion conditions apply to the quiz:

:''Require view'' - the student clicks on the quiz to view it
:''Require grade'' - the student obtains a grade
:''Require a passing grade'' - a 'Grade to pass' is specified for the quiz in the gradebook.
:''All available attempts completed'' - a certain number of attempts were allowed on the quiz and the student has completed them all.

==Group and User overrides==

[[File:overridesquiz.png|thumb|Location of overrides]]

Dates, timing and number of allowed attempts may be changed for individual users or groups by following the links ''Group Overrides'' or ''User Overrides'' in the Quiz Administration settings block.

===Group overrides===
To change a quiz setting for a particular group, click the "add group override" button in ''Quiz Administration>Group overrides'', make the changes you wish and save or enter another override.

===User overrides===
To change a quiz setting for a particular user or users, click the "add user override"button in ''Quiz Administration>User overrides'', make the changes you wish and save or enter another override.

==Site administration settings==

The quiz module has additional settings which may be changed by an administrator in ''Administration > Site administration > Plugins > Activity modules > Quiz''.

The time period settings for a quiz (such as time limit, submission grace period, autosave period and so on) can be set here with a duration of seconds, minutes, hours, days or weeks. These defaults will then be used when new quizzes are created.

;Autosave period
:If enabled, student responses will be saved at regular period according to the selection here. the default is one minute. This is useful so that students don't lose work but does increase the load on the server.

How questions behave can be configured in ''Administration>Site administration>Plugins>Question behaviours>Manage question
behaviours''

==See also==
*[https://youtu.be/y8HOnsKt6qg The Moodle Quiz Activity] MoodleBites video on YouTube

[[fr:Ajouter/modifier un test]]
[[de:Test konfigurieren]]
[[es:Configuraciones del examen]]

Sandbox

2016-01-18T08:20:32Z

Vbarcaru: /* First edit in sandbox */

Test page for docs

Testing email notification yet again

-Testing-

-Testing 2-

-Testing 3-

{| cellpadding="2" cellspacing="0" border="1"
!Col1
!Col2
|-
|Test1
|Test2
|-
|Test1
|Test2
|-
|Test1
|Test2
|}

==Functions and Examples==

Following are the functions that constitute the basic log API for Moodle.
<code>
add_to_log($courseid, $module, $action, $url='', $info='', $cm=0, $user=0)
user_accesstime_log($courseid=0)
get_logs($select, array $params=null, $order='l.time DESC', $limitfrom='', $limitnum='', &$totalcount)
get_logs_usercourse($userid, $courseid, $coursestart)
get_logs_userday($userid, $courseid, $daystart)
</code>
The basic working of these functions can be categorized into two categories:-
# Adding data to logs
# Fetching data from logs
Let us take a deeper look into both of these:-

<pre>something in pre tags</pre>
<code>and something in code tags</code>

<math>Insert formula here</math>==First edit in sandbox==
An additional edit to sandbox
This is where you can edit the content.
Another edit to sandox

==Testing gallery==
==Testing gallery==8/11
==Testing gallery==8/11 again
<gallery mode="packed-hover">
File:Atto_27.jpg|Atto
File:Clean27.jpg|Clean
File:MathJax.jpg|MathJax
</gallery>

more testing...

[[de:Hauptseite]]
[[es:Zona de Pruebas]]

Help:Editing

2016-01-18T08:15:31Z

Vbarcaru: /* Show preview */

{{Help}}
This page is for editing Moodle Documentation (MoodleDocs), which is based on MediaWiki format (similar to Wikipedia).

==Edit tab==
Every MoodleDoc page has an "edit" tab at the top . This link will let you edit the page you are viewing. Please try editing a page by using this [[Sandbox|sandbox link]]. We will cover more formatting and special MoodleDoc features below. The edit tool bar is easy to use.

There are 3 parts to the edit page: the content areas to edit with its toolbar at the top; the save, preview, changes and summary box; the preview area.

===Edit tool bar===
[[Image:MoodleDocs Edit Toolbar.png|frame|center|Edit tool bar]]
Hold the mouse cursor over the edit tool bar to see what functions each icon will do. From left to right: Bold, Italics, Internal (page) link, external link, Level 2 heading, embedded image, media file link, mathematical formula, no wiki, signature and time stamp, horizontal line.

<math>Insert formula here</math>=== Show preview ===
[[Image:MoodleDocs save edit area 1.png|frame|center|Example of the save, preview, comment area below the edit box]]
In edit mode, the show preview button at the bottom of the page lets you see what the page will look like after your edit, before you actually save. We all make mistakes; this feature lets you catch them immediately. Using Show preview before saving also lets you try format changes and other edits without cluttering up the page history, and has a number of other advantages. Don't forget to save your edits after previewing, though!

=== Edit summary ===
Before saving the page, it's considered good practice to enter a very brief summary of your changes in the summary box below the edit-box.

In the example above, the contributor used the edit link next to a heading called "Tips and tricks". MoodleDocs automatically added "/* Tips and tricks */" to the summary box. The The contributor added a comment "Put comment here about edit - will rollback".

See [[Help:Editing#Page history|Page history below]] where the example is continued.

===Show changes===
This button will change the preview area. One column will show current areas that will be changed and another column will show the resulting changes from what has been done in the content editing box.

== Formatting ==

Most '''formatting''' in MoodleDocs is usually done with MediaWiki markup - you don't have to learn HTML!

=== Bold and italics ===
'''Bolding''' and ''italicizing'' is done by surrounding a word or phrase with multiple apostrophes (<tt>'</tt>):

:<code><nowiki>''italics''</nowiki></code> appears as ''italics''. (2 apostrophes on both sides)
:<code><nowiki>'''bold'''</nowiki></code> appears as '''bold'''. (3 apostrophes on both sides)
:<code><nowiki>'''''bolded italics'''''</nowiki></code> appears as '''''bolded italics'''''. (5 apostrophes on both sides)

=== Headings and subheadings ===
Headings and subheadings are an easy way to improve the organization of an article.

Headings can be created like this:
:<code><nowiki>==Top level heading==</nowiki></code> (2 equals signs)
:<code><nowiki>===Subheading===</nowiki></code> (3 equals signs)
:<code><nowiki>====Another level down====</nowiki></code> (4 equals signs)

If an article has at least four headings, a table of contents will automatically be generated.

=== Indentations ===
The simplest way of indenting is to place a colon (<code>:</code>) at the beginning of a line. The more colons you put, the further indented the text will be. A newline marks the end of the indented paragraph e.g.
:<code>This is aligned all the way to the left.</code>
:<code><nowiki>:</nowiki>This is indented slightly.</code>
:<code><nowiki>::</nowiki>This is indented more.</code>
is shown as
:This is aligned all the way to the left.
::This is indented slightly.
:::This is indented more.

=== Lists ===
{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
* ''Unordered lists'' are easy to do:
** start every line with a star
*** more stars means deeper levels
*A newline
*in a list
marks the end of the list.

|<pre><nowiki>* Unordered Lists are easy to do:
** start every line with a star
*** more stars means deeper levels
*A newline
*in a list
marks the end of the list.
</nowiki></pre>
|-
|
# Numbered lists are also good
## very organized
## easy to follow
#A newline
#in a list
marks the end of the list.
|<pre><nowiki># Numbered lists are also good
## very organized
## easy to follow
#A newline
#in a list
marks the end of the list.
</nowiki></pre>
|-
|Descriptive lists:
; first tag : accompanying description
; second tag : more description
; third tag : surprise! more description
|<pre><nowiki>Descriptive lists:
; first tag : accompanying description
; second tag : more description
; third tag : surprise! more description
</nowiki></pre>
|}

=== Preserving formatting ===

{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
Leading spaces are another way to preserve formatting.

Putting a space at the beginning of each line
stops the text from being reformatted.
|<pre><nowiki>Leading spaces are another way to preserve formatting.

Putting a space at the beginning of each line
stops the text from being reformatted.
</nowiki></pre>
|}

You can also use <nowiki><pre></nowiki> tags.

A "nowiki" tag on either side of text area, starts and stops wiki formatting within a line of text. For example, placing the tags here <nowiki> <nowiki> turns off linking [[Main page]] </nowiki> </nowiki> and then starts the wiki formatting again. Here is the same link [[Main page]] without the tags on either side.

The HTML edit tool bar has a nowiki icon.

===PHP syntax higlighting===

{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
<code php>$user = $DB->get_record('user', array('id'=>'1');</code>
|<pre><nowiki><code php>$user = $DB->get_record('user', array('id'=>'1');</code></nowiki></pre>
|}

===Tables===

See [http://meta.wikimedia.org/wiki/Help:Table#Spreadsheet_to_wiki_table_format the Mediawiki help] for full details of the table syntax.

{| class="nicetable"
|-
!What it looks like
!What you type
|-
| A table:

{| class="nicetable"
|-
! header 1
! header 2
! header 3
|-
| row 1, cell 1
| row 1, cell 2
| row 1, cell 3
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
|}

| <pre><nowiki>A table:

{| class="nicetable"
|-
! header 1
! header 2
! header 3
|-
| row 1, cell 1
| row 1, cell 2
| row 1, cell 3
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
|}
</nowiki></pre>
|}

Note, the class="nicetable" is our local hack for Moodledocs. You can leave it out to get a table without borders.

You can also add in more attributes if you do not want to use class="nicetable"

<nowiki>border="1" cellpadding="5" cellspacing="0" align="center"</nowiki>
Or perhaps you want a floating table.
<nowiki>style="float: right;"</nowiki>

Like HTML, you can also have a combined use of "colspan" and "rowspan":
<nowiki>| rowspan="2" | A
| colspan="2" style="text-align: center;" | B</nowiki>

(from mediaWiki Help pages)

== Using Images ==
Images are included in two parts. The first part is a link in the page to an image and the second is uploading the image. For example:

<nowiki>[[Image:MoodleDocs Edit Toolbar.png|frame|center|Edit tool bar]]</nowiki>

is how an image is edited onto the page. The brackets place a link to an image. The Image name tells the wiki renderer that an image is following. The name of the image follows then after that the presentation style of that image is determined. There are a number of different styling possibilities and include thumbnails, resizing, borders, etc.

Images are initially rendered on the page as text, you click the text and a very simple upload process begins. Wikis store images automagically and maintain links internally.

For practical and stylistic reasons, Moodle Docs tend to keep images in the centre of a page and do not often use thumbnails.

For full documentation about images, see [https://www.mediawiki.org/wiki/Help:Images Mediawiki Image Docs]

==Embedding videos==

To embed a YouTube video, simply add <nowiki><mediaplayer></nowiki> tags around the video URL e.g. <nowiki><mediaplayer>http://www.youtube.com/watch?v=U7M3sZL6wts</mediaplayer></nowiki>

== Links and Anchors ==

=== Page links ===
To make a wiki page link, simply put the word in double square brackets, like this: <code><nowiki>[[Sandbox]]</nowiki></code> . Highlight text and using the "internal link" tool will do this as well.

If you want to use words other than the article title as the text of the link, you can do so by adding the pipe "|" divider followed by the alternative name or text.

For example, if you wanted to make a link to the [[Sandbox]], but wanted it to say "my text" you would write it as: <code><nowiki>[[Sandbox|my text]]</nowiki>...</code> It would appear as: [[Sandbox|my text]]... but would link to the sandbox.

There are some special internal link notations. For example <nowiki>[[#top]]</nowiki> will always jump to the top of the current page.

=== External links ===

The easiest way to make an external link is to simply type in the full URL for the page you want to link to e.g. http://school.demo.moodle.net/.

If you want the link to appear with text that you specify, add an alternative title after the address separated by a '''space''' (''not'' a pipe). So if you want the link to appear as [http://school.demo.moodle.net/ School demo site], just type <code><nowiki>[http://school.demo.moodle.net/ School demo site] </nowiki></code>.

===Tracker links===

To automatically link to an issue in the Moodle tracker, simply type the issue number MDL-xxxx e.g. MDL-1234.

=== Categories links ===
A category is a type of index page, a page of links listed in alphabetical order. In page view mode, a list of categories that a page is linked to, appears at the bottom.

To '''put a page in a category''', just type <code><nowiki>[[Category:]]</nowiki></code>, and put the name of the category between the colon and the brackets.

To '''link directly to a category''' use <code><nowiki>[[:Category:Teacher | teacher]]</nowiki></code>, this will show as [[:Category:Teacher | teacher]], note the preceding ":", which is different to <code><nowiki>[[Category:Teacher | teacher]]</nowiki></code>. The second will put the current page in the teacher category as mentioned above.

If you put a page in a category, it's usually a good idea to '''add a sort key''' to the category like so: <code><nowiki>[[Category:Developer|Eclipse]]</nowiki></code>. This will result in the page being placed under "E" like "Eclipse" in the alphabetical link list where most users will look for it.

You can also use MediaWiki's '''PAGENAME variable''' (= the article title without its namespace) as a sort key: <code><nowiki>[[Category:Developer|{PAGENAME}]]</nowiki></code>.

This page is linked to the single category "MoodleDocs".

===Inter-language links===

Simply type <code><nowiki>[[es:Corresponding page title in Spanish]]</nowiki></code> in the English Moodle Docs, or <code><nowiki>[[en:Corresponding page title in English]]</nowiki></code> in the [[:es:Portada|Spanish Moodle Docs]], at the bottom of the page, below the category link. Inter-language links will appear automatically in the "In other languages" block.

If for some reason you want to refer to a page in another language version in the running text, precede the language code by a colon. Thus, the reference in the preceeding paragraph was produced by the text <nowiki>[[:es:Portada|Spanish Moodle Docs]]</nowiki>.

You can also, using the same way, make link to developper documentation, using links like this one : <nowiki>[[:dev:Page name|Page title to use]]</nowiki>.

<nowiki>[[:en:Page name|Page title to use]]</nowiki> links to the latest version of the page in English.

=== User-page links ===
User names can be linked to a user page. For example <nowiki>[[User:Helen Foster|Helen Foster]] </nowiki> will appear [[User:Helen Foster|Helen Foster]] and link to the user's page. Comments by other users are generally left on the Users page comment tab.

=== Interwiki links ===
[TODO]

===Manual Anchors===
Other than automated anchors ([[#Automatic_Anchors|see below]]) manual anchors can be inserted by using something this this:

<nowiki>'''My Anchor.'''</nowiki>

Which if implemented will create an anchor '''My Anchor.'''.

Inside the page I can now refer to this link as [[#anchor_one|the link to My Anchor]] by using this:

<nowiki>[[#anchor_one|the link to My Anchor]]</nowiki>

If you want to have a link back to the top of a (long) page, just insert:

<nowiki>[[#top|Back to top of page]]</nowiki>

== Page comments ==
The page comment tab is used for discussion about the page. Sometimes before making an edit on the page for the first time, it is a good idea to check the page comments. It can be formatted the same as a main page, thus can be used to show a draft of a proposed change.

Talk page contributions may be signed and dated by typing four tildes <nowiki>~~~~</nowiki>. This will appear as [[User:Helen Foster|Helen Foster]] 06:35, 19 February 2006 (WST), for example.
: There's also a handy button for signing in the toolbar of the editing field: [[Image:Signature Icon.png]]

==Page history==
The page history tab allows a way to look at changes between different edits by using the "Compare versions" button and selecting the versions to compare.

It is also possible to revert (roll back) an edit to a previous version from this tab. Usually rollback are left to the MoodleDoc Sysops (administrators), but you certainly can rollback your recent edits. Hopefully, both MoodleDoc sysops and you will comment why the rollback was performed.
[[Image:MoodleDocs history 1.png|frame|center|Example of top 2 entries on a history tab]]

==Watch and unwatch page==
A watched page will appear on "my watchlist" when ever someone edits the page. There is a tab next to history which acts as a toggle between watch and unwatch. In edit mode, there is also at the bottom of the edit area a "Watch this page" check off box.

==See also==
*[http://meta.wikimedia.org/wiki/Help:Editing MediaWiki Help:Editing]
*[http://meta.wikimedia.org/wiki/Help:HTML_in_wikitext Help:HTML in wikitext]
*[http://wikipedia.mozdev.org/ Firefox Wikipedia extension] - The Wikipedia extension makes editing of wiki pages easier by adding a new toolbar to your browser and by providing new menu items in the context menu (right mouse key).

[[Category:MoodleDocs]]

[[de:Bearbeitung von Moodle Docs Seiten]]
[[es:Ayuda:Cómo se edita una página]]
[[fr:Aide:Comment éditer une page]]
[[ja:Help:編集方法]]

User:Barcaru Victor

2016-01-11T17:29:41Z

Vbarcaru: Blanked the page

admin/setting/theme bcu footer

2016-01-10T12:53:45Z

Vbarcaru:

Copy@2016 Victor Barcaru

User:Barcaru Victor

2016-01-10T12:36:24Z

Vbarcaru: Created page with "Copy 2016@Victor Bracaru"

Copy 2016@Victor Bracaru

admin/setting/theme bcu footer

2016-01-10T12:34:07Z

Vbarcaru: Created page with "Copy@20116 Victor Barcaru"

Copy@20116 Victor Barcaru

Help:Editing

2016-01-10T12:32:24Z

Vbarcaru: /* Using Images */

{{Help}}
This page is for editing Moodle Documentation (MoodleDocs), which is based on MediaWiki format (similar to Wikipedia).

==Edit tab==
Every MoodleDoc page has an "edit" tab at the top . This link will let you edit the page you are viewing. Please try editing a page by using this [[Sandbox|sandbox link]]. We will cover more formatting and special MoodleDoc features below. The edit tool bar is easy to use.

There are 3 parts to the edit page: the content areas to edit with its toolbar at the top; the save, preview, changes and summary box; the preview area.

===Edit tool bar===
[[Image:MoodleDocs Edit Toolbar.png|frame|center|Edit tool bar]]
Hold the mouse cursor over the edit tool bar to see what functions each icon will do. From left to right: Bold, Italics, Internal (page) link, external link, Level 2 heading, embedded image, media file link, mathematical formula, no wiki, signature and time stamp, horizontal line.

=== Show preview ===
[[Image:MoodleDocs save edit area 1.png|frame|center|Example of the save, preview, comment area below the edit box]]
In edit mode, the show preview button at the bottom of the page lets you see what the page will look like after your edit, before you actually save. We all make mistakes; this feature lets you catch them immediately. Using Show preview before saving also lets you try format changes and other edits without cluttering up the page history, and has a number of other advantages. Don't forget to save your edits after previewing, though!

=== Edit summary ===
Before saving the page, it's considered good practice to enter a very brief summary of your changes in the summary box below the edit-box.

In the example above, the contributor used the edit link next to a heading called "Tips and tricks". MoodleDocs automatically added "/* Tips and tricks */" to the summary box. The The contributor added a comment "Put comment here about edit - will rollback".

See [[Help:Editing#Page history|Page history below]] where the example is continued.

===Show changes===
This button will change the preview area. One column will show current areas that will be changed and another column will show the resulting changes from what has been done in the content editing box.

== Formatting ==

Most '''formatting''' in MoodleDocs is usually done with MediaWiki markup - you don't have to learn HTML!

=== Bold and italics ===
'''Bolding''' and ''italicizing'' is done by surrounding a word or phrase with multiple apostrophes (<tt>'</tt>):

:<code><nowiki>''italics''</nowiki></code> appears as ''italics''. (2 apostrophes on both sides)
:<code><nowiki>'''bold'''</nowiki></code> appears as '''bold'''. (3 apostrophes on both sides)
:<code><nowiki>'''''bolded italics'''''</nowiki></code> appears as '''''bolded italics'''''. (5 apostrophes on both sides)

=== Headings and subheadings ===
Headings and subheadings are an easy way to improve the organization of an article.

Headings can be created like this:
:<code><nowiki>==Top level heading==</nowiki></code> (2 equals signs)
:<code><nowiki>===Subheading===</nowiki></code> (3 equals signs)
:<code><nowiki>====Another level down====</nowiki></code> (4 equals signs)

If an article has at least four headings, a table of contents will automatically be generated.

=== Indentations ===
The simplest way of indenting is to place a colon (<code>:</code>) at the beginning of a line. The more colons you put, the further indented the text will be. A newline marks the end of the indented paragraph e.g.
:<code>This is aligned all the way to the left.</code>
:<code><nowiki>:</nowiki>This is indented slightly.</code>
:<code><nowiki>::</nowiki>This is indented more.</code>
is shown as
:This is aligned all the way to the left.
::This is indented slightly.
:::This is indented more.

=== Lists ===
{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
* ''Unordered lists'' are easy to do:
** start every line with a star
*** more stars means deeper levels
*A newline
*in a list
marks the end of the list.

|<pre><nowiki>* Unordered Lists are easy to do:
** start every line with a star
*** more stars means deeper levels
*A newline
*in a list
marks the end of the list.
</nowiki></pre>
|-
|
# Numbered lists are also good
## very organized
## easy to follow
#A newline
#in a list
marks the end of the list.
|<pre><nowiki># Numbered lists are also good
## very organized
## easy to follow
#A newline
#in a list
marks the end of the list.
</nowiki></pre>
|-
|Descriptive lists:
; first tag : accompanying description
; second tag : more description
; third tag : surprise! more description
|<pre><nowiki>Descriptive lists:
; first tag : accompanying description
; second tag : more description
; third tag : surprise! more description
</nowiki></pre>
|}

=== Preserving formatting ===

{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
Leading spaces are another way to preserve formatting.

Putting a space at the beginning of each line
stops the text from being reformatted.
|<pre><nowiki>Leading spaces are another way to preserve formatting.

Putting a space at the beginning of each line
stops the text from being reformatted.
</nowiki></pre>
|}

You can also use <nowiki><pre></nowiki> tags.

A "nowiki" tag on either side of text area, starts and stops wiki formatting within a line of text. For example, placing the tags here <nowiki> <nowiki> turns off linking [[Main page]] </nowiki> </nowiki> and then starts the wiki formatting again. Here is the same link [[Main page]] without the tags on either side.

The HTML edit tool bar has a nowiki icon.

===PHP syntax higlighting===

{| class="nicetable"
|-
!What it looks like
!What you type
|-
|
<code php>$user = $DB->get_record('user', array('id'=>'1');</code>
|<pre><nowiki><code php>$user = $DB->get_record('user', array('id'=>'1');</code></nowiki></pre>
|}

===Tables===

See [http://meta.wikimedia.org/wiki/Help:Table#Spreadsheet_to_wiki_table_format the Mediawiki help] for full details of the table syntax.

{| class="nicetable"
|-
!What it looks like
!What you type
|-
| A table:

{| class="nicetable"
|-
! header 1
! header 2
! header 3
|-
| row 1, cell 1
| row 1, cell 2
| row 1, cell 3
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
|}

| <pre><nowiki>A table:

{| class="nicetable"
|-
! header 1
! header 2
! header 3
|-
| row 1, cell 1
| row 1, cell 2
| row 1, cell 3
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
|}
</nowiki></pre>
|}

Note, the class="nicetable" is our local hack for Moodledocs. You can leave it out to get a table without borders.

You can also add in more attributes if you do not want to use class="nicetable"

<nowiki>border="1" cellpadding="5" cellspacing="0" align="center"</nowiki>
Or perhaps you want a floating table.
<nowiki>style="float: right;"</nowiki>

Like HTML, you can also have a combined use of "colspan" and "rowspan":
<nowiki>| rowspan="2" | A
| colspan="2" style="text-align: center;" | B</nowiki>

(from mediaWiki Help pages)

'''Bold text'''== Using Images ==
Images are included in two parts. The first part is a link in the page to an image and the second is uploading the image. For example:

<nowiki>[[Image:MoodleDocs Edit Toolbar.png|frame|center|Edit tool bar]]</nowiki>

is how an image is edited onto the page. The brackets place a link to an image. The Image name tells the wiki renderer that an image is following. The name of the image follows then after that the presentation style of that image is determined. There are a number of different styling possibilities and include thumbnails, resizing, borders, etc.

Images are initially rendered on the page as text, you click the text and a very simple upload process begins. Wikis store images automagically and maintain links internally.

For practical and stylistic reasons, Moodle Docs tend to keep images in the centre of a page and do not often use thumbnails.

For full documentation about images, see [https://www.mediawiki.org/wiki/Help:Images Mediawiki Image Docs]

==Embedding videos==

To embed a YouTube video, simply add <nowiki><mediaplayer></nowiki> tags around the video URL e.g. <nowiki><mediaplayer>http://www.youtube.com/watch?v=U7M3sZL6wts</mediaplayer></nowiki>

== Links and Anchors ==

=== Page links ===
To make a wiki page link, simply put the word in double square brackets, like this: <code><nowiki>[[Sandbox]]</nowiki></code> . Highlight text and using the "internal link" tool will do this as well.

If you want to use words other than the article title as the text of the link, you can do so by adding the pipe "|" divider followed by the alternative name or text.

For example, if you wanted to make a link to the [[Sandbox]], but wanted it to say "my text" you would write it as: <code><nowiki>[[Sandbox|my text]]</nowiki>...</code> It would appear as: [[Sandbox|my text]]... but would link to the sandbox.

There are some special internal link notations. For example <nowiki>[[#top]]</nowiki> will always jump to the top of the current page.

=== External links ===

The easiest way to make an external link is to simply type in the full URL for the page you want to link to e.g. http://school.demo.moodle.net/.

If you want the link to appear with text that you specify, add an alternative title after the address separated by a '''space''' (''not'' a pipe). So if you want the link to appear as [http://school.demo.moodle.net/ School demo site], just type <code><nowiki>[http://school.demo.moodle.net/ School demo site] </nowiki></code>.

===Tracker links===

To automatically link to an issue in the Moodle tracker, simply type the issue number MDL-xxxx e.g. MDL-1234.

=== Categories links ===
A category is a type of index page, a page of links listed in alphabetical order. In page view mode, a list of categories that a page is linked to, appears at the bottom.

To '''put a page in a category''', just type <code><nowiki>[[Category:]]</nowiki></code>, and put the name of the category between the colon and the brackets.

To '''link directly to a category''' use <code><nowiki>[[:Category:Teacher | teacher]]</nowiki></code>, this will show as [[:Category:Teacher | teacher]], note the preceding ":", which is different to <code><nowiki>[[Category:Teacher | teacher]]</nowiki></code>. The second will put the current page in the teacher category as mentioned above.

If you put a page in a category, it's usually a good idea to '''add a sort key''' to the category like so: <code><nowiki>[[Category:Developer|Eclipse]]</nowiki></code>. This will result in the page being placed under "E" like "Eclipse" in the alphabetical link list where most users will look for it.

You can also use MediaWiki's '''PAGENAME variable''' (= the article title without its namespace) as a sort key: <code><nowiki>[[Category:Developer|{PAGENAME}]]</nowiki></code>.

This page is linked to the single category "MoodleDocs".

===Inter-language links===

Simply type <code><nowiki>[[es:Corresponding page title in Spanish]]</nowiki></code> in the English Moodle Docs, or <code><nowiki>[[en:Corresponding page title in English]]</nowiki></code> in the [[:es:Portada|Spanish Moodle Docs]], at the bottom of the page, below the category link. Inter-language links will appear automatically in the "In other languages" block.

If for some reason you want to refer to a page in another language version in the running text, precede the language code by a colon. Thus, the reference in the preceeding paragraph was produced by the text <nowiki>[[:es:Portada|Spanish Moodle Docs]]</nowiki>.

You can also, using the same way, make link to developper documentation, using links like this one : <nowiki>[[:dev:Page name|Page title to use]]</nowiki>.

<nowiki>[[:en:Page name|Page title to use]]</nowiki> links to the latest version of the page in English.

=== User-page links ===
User names can be linked to a user page. For example <nowiki>[[User:Helen Foster|Helen Foster]] </nowiki> will appear [[User:Helen Foster|Helen Foster]] and link to the user's page. Comments by other users are generally left on the Users page comment tab.

=== Interwiki links ===
[TODO]

===Manual Anchors===
Other than automated anchors ([[#Automatic_Anchors|see below]]) manual anchors can be inserted by using something this this:

<nowiki>'''My Anchor.'''</nowiki>

Which if implemented will create an anchor '''My Anchor.'''.

Inside the page I can now refer to this link as [[#anchor_one|the link to My Anchor]] by using this:

<nowiki>[[#anchor_one|the link to My Anchor]]</nowiki>

If you want to have a link back to the top of a (long) page, just insert:

<nowiki>[[#top|Back to top of page]]</nowiki>

== Page comments ==
The page comment tab is used for discussion about the page. Sometimes before making an edit on the page for the first time, it is a good idea to check the page comments. It can be formatted the same as a main page, thus can be used to show a draft of a proposed change.

Talk page contributions may be signed and dated by typing four tildes <nowiki>~~~~</nowiki>. This will appear as [[User:Helen Foster|Helen Foster]] 06:35, 19 February 2006 (WST), for example.
: There's also a handy button for signing in the toolbar of the editing field: [[Image:Signature Icon.png]]

==Page history==
The page history tab allows a way to look at changes between different edits by using the "Compare versions" button and selecting the versions to compare.

It is also possible to revert (roll back) an edit to a previous version from this tab. Usually rollback are left to the MoodleDoc Sysops (administrators), but you certainly can rollback your recent edits. Hopefully, both MoodleDoc sysops and you will comment why the rollback was performed.
[[Image:MoodleDocs history 1.png|frame|center|Example of top 2 entries on a history tab]]

==Watch and unwatch page==
A watched page will appear on "my watchlist" when ever someone edits the page. There is a tab next to history which acts as a toggle between watch and unwatch. In edit mode, there is also at the bottom of the edit area a "Watch this page" check off box.

==See also==
*[http://meta.wikimedia.org/wiki/Help:Editing MediaWiki Help:Editing]
*[http://meta.wikimedia.org/wiki/Help:HTML_in_wikitext Help:HTML in wikitext]
*[http://wikipedia.mozdev.org/ Firefox Wikipedia extension] - The Wikipedia extension makes editing of wiki pages easier by adding a new toolbar to your browser and by providing new menu items in the context menu (right mouse key).

[[Category:MoodleDocs]]

[[de:Bearbeitung von Moodle Docs Seiten]]
[[es:Ayuda:Cómo se edita una página]]
[[fr:Aide:Comment éditer une page]]
[[ja:Help:編集方法]]

Installation guide for Windows using EasyPHP

2016-01-04T20:32:38Z

Vbarcaru: /* Install EasyPHP 1.7 - Note: Obsolete version. See Section Below. */

*Return to [[Windows installation]]

Moodle requires that a webserver, PHP and a supported database be installed to run on Windows. This may be achieved by using EasyPHP, a package that bundles all the software you need in the form of Apache (webserver), PHP and MySQL (database) into a single Windows application. Please note however, that EasyPHP is not designed to be used for a production server. Here are the steps from start to finish.

===Preparation===

# Firstly, if you have ever installed MySQL before (even as part of another package), uninstall it all, delete all the MySQL files and make sure you delete ''c:\my.cnf'' and ''c:\windows\my.ini''. You might want to do a search and delete ANY file called ''my.cnf'' or ''my.ini''.
# If you've ever installed PHP before delete any files called php4ts.dll from around your Windows directory, as well as any files called php.ini.
===Get EasyPHP===
# Download EasyPHP from here: [http://www.easyphp.org/easyphp-devserver.php EasyPhp DevServer 13.1]

===Install EasyPHP 1.7 - Note: Obsolete version. See Section Below.===
# Run the downloaded file: ''easyphp1-7_setup.exe''. The installation process is in French but is much like installing any other Windows program - I advise accepting the defaults and letting it all install. Note: that "Suivant" means Next and "Oui" means Yes.
# At the end of the install leave the checkbox selected to "Lancer EasyPHP" (Start EasyPHP) and hit the "Terminer" button. You might be taken to a information web page which you can safely ignore.
# If all went well - congratulations! Apache, PHP and MySQL are all installed and running! You should see a black E in your toolbar tray. You can right click on it to get a menu which will let you control the running programs, but you won't be needing that for now.
#Some things may be in French and you may prefer English. You can download this file http://www.easyphp.org/telechargements/dn.php?F=indexUS_1.7 which contains English versions of www and home folder in the EasyPHP1-7 folder. These can be copied over the default files.

contains English versions of www and home folder in the EasyPHP1-7 folder. These can be copied over the default files.

===Install EasyPHP 1.13===

# Run the downloaded file: EasyPHP-DevServer-13.1VC9-setup.exe (or whatever the current version is). It will prompt you to select your language. I choose all of the other defaults. Note: VC9 is for Windows XP to Windows 8. VC11 is for Windows 7 & 8.
# At the end of the install leave the checkbox selected to "Start EasyPHP".
# If you experience an error starting EasyPHP, it might be because inetinfo.exe is running. Bring up Windows Task Manager by typing CTRL+ALT+DELETE. Find inetinfo.exe in the task list, highlight it and click "End Process." Right-click on the EASYPHP icon and restart the process.
# If all went well - congratulations! Apache, PHP and MySQL are all installed and running! You should see a black E in your toolbar tray. Right click on it to get a menu which will let you control the running programs.
# Configure PHP to extend the max execution from 30 seconds to something more, otherwise your installation will fail due to exceeding this 30 second time limit.

===Create a database===
# The next thing you need to do is to set up a database for Moodle to use. Right-click the black E in the toolbar tray and choose Administration, then click DB Management (beside PHPMyAdmin). Alternatively, using a browser, go to http://localhost/mysql/ (note the final slash).
# If asked for a username, use "''root''" with a ''blank password''. You should see a phpMyAdmin web interface that allows you to create a new databases and user accounts.
# Create a new database by typing "moodle" into the field and hitting the "Create" button and don't forget to specify a utf-8 collation for the database being created. That was easy!
# You can also create a new user to access your database if you want. This can be a bit tricky for a first-time user, so you might just want to use the existing user "root" with no password in your Moodle config for now, and fix this later.

===Get Moodle!===
# You're ready to install Moodle! Download the latest release of Moodle from [http://moodle.org/download Moodle.org], then unzip the archive.
=== Installing Moodle===
# Copy your moodle files into the directory where you installed EasyPhP ''C:\Program Files\EasyPHP\www'' or ''C:\Program Files\EasyPHP-DevServer-13.1VC9\data\localweb'' for the newst EasyPHP version. You can either copy the entire moodle directory (ie ''C:\Program Files\EasyPHP\www\moodle'') or copy all the ''contents'' of the moodle directory. If you choose this second option then you will be able to access your Moodle home page using ''<nowiki>http://localhost/</nowiki>'' instead of ''<nowiki>http://localhost/moodle/</nowiki>''.
# Make a new empty folder somewhere else for Moodle to store uploaded files in, eg: ''C:\moodledata''
# Go into your Moodle folder. Make a copy of ''config-dist.php'', and call it ''config.php''
====Edting the the config.php file==== Edit ''config.php'' using a text editor (Notepad will do, just be careful that it doesn't add unwanted spaces at the end).
# Put in all your new database info:
# $CFG->dbtype = 'mysql';
#* $CFG->dbhost = 'localhost';
#* $CFG->dbname = 'moodle';
#* $CFG->dbuser = 'root';
#* $CFG->dbpass = <nowiki>''</nowiki>;
#* $CFG->dbpersist = true;
#* $CFG->prefix = 'mdl_';
# And put in all your file paths
#* $CFG->wwwroot = 'http://localhost/moodle'; // Use an external address if you know it.
#* $CFG->dirroot = 'C:\Program Files\EasyPHP\www\moodle';
#* $CFG->dataroot = 'C:\moodledata';
#Save config.php - you can ignore the other settings if there are any.

===The web based installer===
# You're nearly there now! The rest of the setup is all web-based. Visit ''<nowiki>http://localhost/moodle/admin/</nowiki>'' with your browser to continue the setup via your browser.
# To use zip files with Moodle (for example the backups use zip) you might need to enable "zlib". You can do this by going to your EasyPHP directory (C:\Program Files\EasyPHP), and running the program phpini.exe in there. Put a mark in the checkbox next to "zlib.dll". Close that window, then go to the black E in your toolbar and right-click it to get a menu - select "Restart" from this menu.
===Setting a Cron===
# Lastly, you need to set up some sort of cron. See the [[Installing Moodle#Set up cron|Installation guide]] for more details on this.
===Tips===
If you don't or can't use EasyPHP, here are a few tips to make sure your PHP is set up correctly and avoid common problems:
* Make sure you enable the GD module so Moodle can process images - you may have to edit php.ini and remove the comment (;) from this line: 'extension=php_gd2.dll'.
* Make sure you enable the Zlib module so that you can create and unpack zip files from within Moodle.
* Make sure sessions is turned on - you may have to edit php.ini and fix the directory for ''session.save_path'' - instead of the default "/tmp" use a Windows directory like "c:/temp".

[[Category:Administrator]]
[[Category:Installation]]