{{stub}}
The intent of this block is to mark pages so that an administrator role can see them as a list of links. Editing must be turned on for this block to appear, else it is hidden.

The admin bookmark block should display a link of pages where this block has been added to a context. As of October 2011 it does not.

Site administration > Plugins > Blocks > Manage Blocks then clicking on the number of instances link, will display a list of course where the block has been installed. The front page will not appear on this list.

It is possible to set the block display properties, just as any other block. The default capabilities are to allow the teacher to view, manage and edit blocks. These can be overridden in any context.

[[de:Administratorlesezeichen]]
{{Blocks}}

Dock

2012-03-27T18:14:53Z

Hrynkiw: Undo revision 96683 by Hrynkiw (talk)

{{Blocks}}

The dock is an area where blocks can be moved to and from this area with the block to dock [[Image:Block_to_dock.png]] and dock to block [[Image:Dock_to_block.png]] icons.

==Dock area and dock tool==
[[Image:Dock area.png|thumb|475px|center|The dock area with 5 docked blocks and a block with the dock tool]]
The "docked" blocks appear as vertical tabs along the left margin attached to the page.

[[Image:Dock area expanded block menu.png|thumb||center|Expanded navigation block, showing dock tool]]
The docked block can expand into a menu with a click on the tab in the dock area. Clicking on the dock icon when a block is in the docked position, will move the block back to its original position.

==Effect of using dock==
It allows users an option of changing the look of a page on their screen. For example, a student could move all blocks to the dock, creating a 1 column effect.
{| class="nicetable"
|-
| [[File:Dock all blocks docked.png|thumb|300px|center]]
| [[File:Dock no blocks docked.png|thumb|300px|center]]
|-
| A student moves all blocks to the dock area - view had 1 column
| A student un-docks all blocks - now view has 3 columns
|}

==Another docking example==
Moodle 2 introduced a dock for managing blocks. The dock is on the left and can be accessible to anyone any time on any block including navigation to an HTML block.
{| class="nicetable"
|-
| [[Image:docking01.png|thumb|200px|center]]
| [[Image:docking02.png|thumb|200px|center]]
| [[Image:docking03.png|thumb|200px|center]]
|-
| To place a block on the dock, click the docking option
| The block automatically moves to the dock
| To access the block, use the mouse-over.
|}

[[de:Dock]]

Dock

2012-03-27T17:01:13Z

Hrynkiw: added note "Arranging the Order of Docked Blocks"

Navigation

2012-03-27T16:49:13Z

Hrynkiw: added Note for Admins re: courses/categories not appearing in Navigation menu

{{Site appearance}}
There are two standard blocks on every page:

[[Image:Navigation and Settings.png|frame|right|Navigation and Settings blocks]]
=== Navigation block===
The [[Navigation block]] provide easy access to '''view''' various sections of the Moodle site and includes
*My home - a personalised home page displaying links to the courses a user is associated with and activity information (such as unread forum posts and upcoming assignments)
*Site pages - links to site pages and resources from the front page of Moodle
*My profile - quick links allowing a user to view their profile, forums posts, blogs and messages as well as manage their private files
*My courses - lists (by course shortname) and links to courses the user is associated with. Click the course's shortname to view the front page of the course or use the arrows to navigate quickly to a specific section, resource or activity.

'''Note:''' It is recommended that you do not use the Back and Forward buttons on your web browser when using Moodle. Using the Navigation links provided will ensure you always see the latest version of a page (eg a forum with all posts). Be careful to update, save or post any changes you make before moving on to another page to avoid losing your work.

====Keyboard support for navigation====
*Keyboard/Screenreader and Voice input users can access navigation by using the Tab, Space, Enter and right/left arrow keys.

===Settings block===
The [[Settings block]] provides you with easy access to '''change''' various settings of a Moodle site. This block shows contextual settings (the settings for a forum when you are viewing it as an editing user) as well as settings for anything else you have permissions for. All users have access to edit their profile and message settings from this block as well as their Blog preferences.

Navigation and Settings in Moodle 2.0 video:

<mediaplayer>http://www.youtube.com/watch?v=9AskwBwk84M</mediaplayer>

==Site administration settings==

An administrator can change navigation settings, such as the default home page, and whether to show course categories in the navigation, in ''Settings > Site administration > Appearance > Navigation''.

{{New features}}Moodle 2.2 includes an additional setting for enabling course section links in the navigation. See the screencast [http://youtu.be/7W336RjjIUE Course section links in Moodle 2.2]

==Note for Administrators==

If you are not ''directly'' associated with a course (that is, if you don't have a teacher, student or other role actually defined in the course) it will not appear in your Navigation menu. Also, if you are not directly associated with at least one course in a category, the category will not appear in your Navigation menu.

[[de:Navigation]]

Assignment settings

2012-02-11T00:03:07Z

Hrynkiw: /* Notes on Date Settings */ "Assignments without a due date..."

{{Assignment}}
This page describes the various configuration options available within the Assignment module - both at the Site level and the Activity level.

==Course administration settings==
The following configuration options are available when creating or editing/updating any Assignment activity. Settings specific to each of the assignment types are detailed separately below.

To '''add a new Assignment activity''' to your course login with the appropriate access rights (e.g.editing teacher, course creator or administrator) and Turn Editing On. Within the required Week or Topic Block click on the Add Activity dropdown menu arrow and select the required assignment type.

To '''edit an existing Assignment activity''', login to your course with the appropriate access rights (e.g.editing teacher, course creator or administrator) and Turn Editing On and select the Update icon against the relevant Assignment item. Alternatively, after logging into your course simply click on the name of the Assignment activity you wish to edit and then click the Edit Settings link under ''Assignment administration'' within the Settings block.

===Assignment name===
Give your Assignment a name (e.g. “Report on Topic 1 Content”). The title entered here will be the name that learners see in the course content area. Learners will click on this name to view the details of the assignment and, if applicable, submit their work.

===Description===
The description of the assignment, which should include precise instructions for students regarding the subject of the assignment, the form, in which it should be submitted, the grading criteria etc.

Use this area to describe the assignment and explain what learners are expected to do to complete this task. The assignment description can be as brief or as detailed as you feel is necessary to meet the needs of your learners. However, it is to your benefit to provide as much detail and information as possible, especially at the start of the course while you are still establishing procedures. Generally, the more information you are able to provide here the fewer questions and problems your learners will have completing the task.

The assignment description field can also be used to provide information or resources related to the assignment. An instructor, for example, could provide some literature, a video clip, an image, or a link to a webpage, and then ask the learners to use these materials in completing the task.

===Available from===
The Available from setting prevents students from submitting their assignment before the shown date.

This option allows an instructor to set a day, month, year and time (24 hour clock) from which learners can begin to submit their assignments. Please note that this setting does not hide the activity from the learners. Instead, the learner will see the activity, be able to view the instructions and use any materials you have include in the description, but the learner will not be able to submit or complete the assignment until the Available from date.

By default the Available from date is Enabled (ticked) and is set at the day and time you selected Add Assignment. To Disable this feature simply ensure the Enable checkbox is not marked.

===Due date===
The Due date setting prevents students from submitting their assignment after the shown date.

This option allows an instructor to set a day, month, year and time (24 hour clock) before which learners must submit their assignment.

By default the Available from date is Enabled (ticked) and is set at 7 days ahead of the day and time you selected Add Assignment. To Disable this feature simply ensure the Enable checkbox is not marked.

====Notes on Date Settings====
Both the Available from and Due dates are displayed for learners in the assignment details, but the Due date is also marked in the course Calendar as a visible reminder for participants and provides a link to the activity.

Your use of the Available from and Due date settings will probably be dependent on the overall structure of your course. If you are facilitating an open ended course or a course with rolling enrolment, then you might find it easier to not apply the Available from and Due date settings. This arrangement will allow the learners to access the assignment according to their own schedule and progress within the course.

Alternatively, if you are working within a more structured format or adhering to a timeline, the Available from and Due date settings are useful for keeping learners on schedule. Using the Available from setting will make it possible for learners to preview upcoming activities, while at the same time, prevent them from finishing the course in the first week and not returning for additional activities or information. Likewise, the Due dates help keep the learners from lagging too far behind and decrease the likelihood that the learner will become overwhelmed by having to complete several weeks worth of work at once.

Assignments without a Due date will not appear on the My home page.

===Prevent late submissions===
Setting Prevent late submissions to Yes will prevent learners from being able to submit this assignment after the Due date (where specified). If you set Prevent late submissions to No, then learners can submit the assignment as long as the assignment is visible or accessible to them but their submissions will be marked as late.

===Grade===
Specify the maximum grade or [[Scales|Scale]] to be applied to the assignment. If you will not be giving a grade for the assignment, choose No Grade.

===Grading method===

{{New features}}Select either [[Rubric]] (advanced grading form used for criteria-based assessment) or simple direct grading (entering a grade or scale item).

===Grade Category===
Any custom [[Grade_categories|Grade Categories]] that have been created within your site or course will be listed here and will be available for selection. Select the required Grade Category to add this assignment as a [[Grade_items|Grade item]] within this Category.

===Common module settings===

==== Group mode ====
When course group mode is turned on, the [[Groups|group mode]] can be one of three levels: No groups, Separate groups or Visible groups.

'''No groups''' - There are no groups and all students submit their assignments in one Assignment area

'''Separate groups''' - Students submit their assignments within a separate Group based submission area and teachers/trainers can sort submissions by Group or view All Participants.

'''Visible groups''' - All students submits their assignment within a single Assignment area but may choose which Group to associate their submission with before uploading. Teachers/trainers can sort submissions by Group or view All Participants.

====Groupings====
Groupings is an Advanced setting. A grouping is a collection of groups within a course. If a existing grouping is selected from the dropdown list, students assigned to groups within the grouping will be able to work together within the group mode specified above.

====Visible====
Choose whether to Show or Hide the assignment from learner view. A hidden assignment will be displayed greyed out on the main course page for those with teacher, creator, manager or admin type roles but invisible to students/learners.

====ID number====
Setting an ID number provides a way of identifying the assignment for grade calculation purposes. If the activity is not included in any grade calculation then the ID number field can be left blank.

The ID number can also be set in the gradebook, though it can only be edited on the activity settings page.

===Restrict access settings===
The [[Restrict_access_settings|Restrict access]] area becomes visible in Moodle activities and resource settings if [[Conditional_activities|Conditional Activities]] have been enabled.

====Allow access from====
The Access from date determines the day, month and year students may first access the activity via the assignment name link on the course page. To activate this option click in the Enable checkbox to add a tick.

====Allow access until====
The Access until date determines the day, month and year students may last access the activity via the assignment name link on the course page. To activate this option click in the Enable checkbox to add a tick.

'''Note:''' The difference between access from/to dates and availability settings for the activity is that outside the set dates the latter allows students to view the activity description, whereas access from/to dates prevent access completely.

[[Image:restrictinassignment.png|frame|center|Restrict access settings in Assignment]]

====Grade Condition====
This setting determines any grade conditions which must be met in order for students to access the activity. Multiple grade conditions may be set using the 'Add 2 grade conditions to form' button. If there are multiples completion conditions applied to an activity, it will only be accessible to learners when ''all'' grade conditions are met. See [[Conditional_activities_settings|Conditional Activities]] for more information.

====Before activity can be accessed====
Before a learner has fulfilled the the Grade Conditions specified above and the activity is still inaccessible to them, you can choose whether to show the activity greyed-out on the course page with the grade conditions listed (restriction information) or to hide the activity from learner view entirely.

==Assignment Type Specific Settings==

===Advanced uploading of files===
The Advanced upload of files assignment type allows a learner to upload and edit multiple files to form their final submission while the assignment is open and accessible to students.

[[Image:Advanceduploadsettings.png|frame|center|Advanced uploading of file Assignment Type Settings]]

====Maximum size====
This setting specifies the maximum size per file of '''each''' of the files that the students can upload as part of their submission. This maximum upload size may only be equal to or less than the course limit (which in turn may only be equal to or less than the site limit)

====Allow deleting====
If enabled, students may delete uploaded files at any time before submitting for grading.

====Maximum number of uploaded files====
The maximum number of files which may be uploaded by each learner. As this figure is not displayed anywhere, it is suggested that it is mentioned in the assignment Description.

====Allow notes====
If enabled, students may enter notes into a text area associated with the assignment
This text box can be used for communication with the grading person, assignment progress description or any other written activity.

====Hide description before available date====
If enabled, the assignment description is hidden before the "Available from" date. Only the assignment name is displayed.

====Email alerts to teachers====
If enabled, teachers receive email notification whenever students add or update an assignment submission.

Only teachers who are able to grade the particular assignment are notified. So, for example, if the course uses separate groups, teachers restricted to particular groups won't receive notification about students in other groups.

====Enable 'Send for marking' button====

Where grading is enabled, the "Send for marking" button allows students to indicate to the teacher that they have finished working on an assignment. The teacher may choose to revert the assignment to draft status (if it requires further work, for example).

'''Note:''' this means that the learner can no longer edit their submission (to do so would risk invalidating any work their assessor had done on their submission). If students regret their decision and wish to edit, they need to request that somebody with course editing access reverts them to Draft Status. This is also true if Send For Marking is never turned on and a submission is uploaded; the teacher must take steps to give the student a chance to resubmit.

To revert to the draft stage or let a student resubmit, click on the assignment activity, then click on ''View # submitted assignments,'' in the upper right. On the page with the roster and their submissions, click '''Grade''' (or '''Update''' for students who have already been graded) for the student who should get to resubmit. When the new window opens, click Revert to Draft at the lower right, or click the black '''X''' to delete their files.

===Online text===
The Online text assignment type allows a learner to compose and edit text on screen using the standard Moodle HTML Editor. The online text assignment can be set up to allow learners to compose, revise and edit over time or such that the learner only has one opportunity to enter his or her response.

====Allow resubmitting====
If set to Yes, students will be allowed to resubmit assignments after they have been graded (for them to be re-graded). This may be useful if the teacher wants to encourage an iterative process to assignment completion.

====Email alerts to teachers====
If enabled, teachers receive email notification whenever students add or update an assignment submission. Only teachers who are able to grade the particular assignment are notified.

====Comment inline====
If enabled, the submission text will be copied into the feedback comment field during grading, making it easier to comment inline (using a different colour, perhaps) or to edit the original text. Note that if the teacher makes inline comments and changes, the student's original submission is kept intact.

If inline comments are not permitted, then the teacher will see the student’s submission with a separate area for making comments.

===Upload a single file===
The Upload single file assignment type allows a learner to upload a single file for their submission while the assignment is open and accessible to students.

====Allow resubmitting====
If enabled, students will be allowed to resubmit assignments after they have been graded (for them to be re-graded).

====Email alerts to teachers====
If enabled, then teachers are alerted with a short email whenever students add or update an assignment submission. Only teachers who are able to grade the particular submission are notified. So, for example, if the course uses separate groups, then teachers restricted to particular groups won't receive any notices about students in other groups.

====Maximum Size====
This setting specifies the maximum size per file of '''each''' of the files that the students can upload as part of their submission. This maximum upload size may only be equal to or less than the course limit (which in turn may only be equal to or less than the site limit).

[[Image:uploadsingleasgn.png|frame|center|Upload single file Assignment settings]]

===Offline Activity===
The Offline Activity assignment is used when an activity or assessment process is performed outside of Moodle. It could be something elsewhere on the web or in person. Students can see a description of the assignment, but can't upload files. Grading works normally, and students will get notification of their grades.

The Offline Activity[[Assignment_module#Assignment_types|Assignment Type]] doesn't currently have any specific settings.

Finally, to save your setting changes and to create your assignment activity choose either''' Save and return to course''' or '''Save and display'''. To discard your changes click '''Cancel'''.

==Locally assigned roles==

In ''Settings > Assignment administration > Locally assigned roles'' selected users can be given additional roles in the activity. See the Using Moodle [http://moodle.org/mod/forum/discuss.php?d=98208 Custom role for 'Course Monitor'] forum discussion for an example.

==Assignment permissions==

Role permissions for the activity can be changed in ''Settings > Assignment administration > Permissions''.

==Site administration settings==

The following configuration options are available for an administrator under ''Settings > Site administration > Plugins > Activity modules > Assignment''. They apply to all four assignment types.

===Maximum size===

An Administrator can specify the maximum size of any individual file uploaded within the Upload Single File or Advanced Upload of Files Assignment type across all courses on the site. This limit may be equal to or less than course file upload limit

===Count===
Applicable the Online Text Assignment type only, you can set whether Moodle automatically counts the number of words or letters of a submission. A word or number count is displayed in parenthesis to Teachers and Learners after the Last Edited date and time stamp within the Assignment submission.

===Show recent submissions===
This option allows everyone to see notifications of submissions in [[Recent activity]] reports and the Recent Activity Block, within a course context. Note that the default for this option is Yes which means students will be able to see when classmates have submitted or updated any Assignments.

[[Image:Assignmentadmin.png|frame|center|Assignment Module Settings]]

==See also==

*[[Assignment_permissions|Assignment Permissions]]
*[http://www.youtube.com/watch?v=SahXhi3zLqs Marking and sending back work in Moodle]
*[http://moodle.org/mod/forum/discuss.php?d=126431 single file upload vs. advanced uploading forum thread]

[[de:Aufgabe anlegen]]
[[cs:Přidání/úprava úkolu]]
[[fr:Ajouter/modifier un devoir]]
[[ja:課題を追加/編集する]]

My home

2012-02-10T23:44:09Z

Hrynkiw: /* Default home page */ added Site Admin users cannot set My Moodle as default home (I looked for DAYS for this tidbit)

{{Site appearance}}
==My home==

My Moodle or My home is a customisable "dashboard" page for providing users with links to their courses and activities within them, such as unread forum posts and upcoming assignments. (The name 'My Moodle' was used in the admin menu in earlier versions of Moodle.)

The navigation block includes a My home link directly above or below the Site home link.

My Home in Moodle 2.0 video:

<mediaplayer>http://www.youtube.com/watch?v=un_pBYkeXXI</mediaplayer>

==Site administration settings==

===Default home page===

An administrator can set My home as the default home page for all logged-in users by selecting 'My Moodle' as default home page in ''Settings > Site administration > Appearance > Navigation''.

If 'User preference' is selected as default home page, each user needs to navigate to either the 'Home Page' or the 'My home' page then via the ''Settings > My profile settings'' click the "Make this my default home page" link. Note that this option only appears on the page that is not their current default home page. Once selected, Moodle will remember which page to present them each time they log on.

Users with the Site administrator role cannot set My Moodle as their default home page.

===Setting the default My Moodle page===

An administrator or manager (or other user with the capability [[Capabilities/moodle/my:configsyspages|moodle/my:configsyspages]]) can set which content (course overview, calendar, blocks) appears on the My Moodle page for all users as follows:

# Access ''Settings > Site administration > Appearance > Default My Moodle page''.
# Select the required blocks from the "Add a block" drop-down menu. [[Block settings|Configure]] each block as desired.
# Reposition blocks using the arrow icons in the block headers.

{| class="nicetable"
|-
|[[Image:myMoodle02.png|thumb|250px|center|Accessing My Moodle page]]
|[[Image:myMoodle03.png|thumb|250px|center|Editing My Moodle page]]
|}

===Managing blocks===

By default, users are allowed to add blocks to their My Moodle page. This can be prevented by editing the [[Authenticated user|authenticated user]] role and changing the [[Capabilities/moodle/my:manageblocks|moodle/my:manageblocks]] capability from allow to not set.

==My Moodle capabilities==

* [[Capabilities/moodle/my:manageblocks|Manage My Moodle page blocks]] (see above)
* [[Capabilities/moodle/my:configsyspages|Configure system templates for My Moodle pages]]

==See also==

* Using Moodle [http://moodle.org/mod/forum/view.php?id=7309 My Moodle forum]

Using Moodle forum discussions:
* [http://moodle.org/mod/forum/discuss.php?d=168292 Latest news on My Moodle]

[[eu:Nire_Moodle]]
[[fr:Mon Moodle]]
[[de:Meine Startseite]]

Quiz settings

2012-02-07T19:12:59Z

Hrynkiw: /* Review options */ added paragraph "...you must have 'the attempt' selected to enable the options..."

{{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 options'''
There are a large number of options and your administrator should already have chosen the default values for most of them so that you will not have to modify them for the type of quiz that you use most often. The administrator may also have classified some of the settings as 'advanced' which means that they will be hidden from the set-up screen by default. This can help to keep the screen simpler. You can turn on the display of these advanced options by clicking on the '''Show advanced settings''' button. They will then remain visible until you click on '''Hide advanced settings'''.

==Quiz administration==
When you first set up your quiz from ''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)

===General===
;Name
:This is the standard name field. This name will appear on the home page of the course, navigation menu and other places which will show or provide links to this quiz.

;Introduction
:Write an introduction for the quiz. A student will see the introduction immediately after clicking on the quiz name. The student will see this description before they click on the "Attempt quiz" link and thus before the quiz timer is started (if used). This is a good place to include any special instructions for taking the quiz like the number of attempts allowed, time limit or scoring rules.

;{{New features}}'''Display description on course page'''
:You can choose to make the description visible with the activity on the course page.

;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.
*NOTE: You can make the quiz available at different times for different groups or users in the Group or User override sections of the Quiz Adminstration settings block.

;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 under [[Adding/updating_a_quiz#Students_may_review_section|Students may review]].

;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:

# JavaScript support in the browser becomes mandatory - this allows the timer to work correctly.
# A floating timer window is shown with a countdown
# 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
*NOTE: You can make the quiz available last a different period of time for different groups or users in the Group or User override sections of the Quiz Adminstration settings block.

;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. If the quiz is randomized then the student will get a new version for each attempt. This is useful for practice purposes.
*NOTE: You can change the allowed number of attempts for different groups or users in the Group or User override sections of the Quiz Adminstration settings block.

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

;Question order
:If 'Shuffled randomly' is selected, then the order of questions in the quiz will be randomly shuffled each time a student starts a new attempt at the quiz. The intention is to make it a little harder for students to copy from each other.

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

===Question behaviour===

;How questions behave
* Deferred feedback - Students must enter an answer to each question and then submit the entire quiz, before anything is graded or they get any feedback.
* Adaptive mode and Adaptive mode (no penalties) - Allows students to have multiple attempts at the question before moving on to the next question. The question can adapt itself to the student's answer, for example by giving some hints before asking the student to try again.
*Manual grading - Used for essay questions (irrespective of what the quiz is set to) but you can now choose to have every question in the quiz manually graded, if you wish.
*Interactive mode - After submitting one answer, and reading the feedback, the student has to click a 'Try again' button before they can try a new response. Once the student has got the question right, they can no longer change their response. Once the student has got the question wrong too many times, they are just graded wrong (or partially correct) and get shown the feedback and can no longer change their answer. There can be different feedback after each try the student makes.
*Immediate feedback - Similar to interactive mode in that the student can submit their response immediately during the quiz attempt, and get it graded. However, they can only submit one response, they cannot change it later.
*Deferred feedback or Immediate feedback with Certainty-based marking (CBM) - With CBM, the student does not only answer the question, but they also indicate how sure they are they got the question right. The grading is adjusted by the choice of certainty, so that students have to reflect honestly on their own level of knowledge in order to get the best mark.

;Each attempt builds on the last
: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===

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 maxtrix with check boxes.

The various pieces of information that can be controlled are:
; Responses : What the student entered in response to each question.
; Answers : The correct answer to each question is shown. (See note below)
; Feedback : The pieces of feedback that are specific to the student's response to each question.
; General feedback : The general feedback for the question, which does not depend on the student's response.
; Scores : Numerical information about the score the student received on each question.
; Overall feedback : The overall feedback for the whole attempt (see below).

For each of the above items, you can determine the timeframe when the students will see them:
; 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'.

===Display===

;Decimal places in grades
:This option determines how many digits will be shown after the decimal point 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
:This field is optional.

: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
:This field is optional.

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

;Browser security
: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, with 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 navigation controls.
:* 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 ''Settings > 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.

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.

===Common module settings===
;Group mode
:Here you can choose whether the quiz should be organized by group. This only has an effect on the review screens of the teachers where it determines which groups of students they see.

;Visible to students
:Determines whether the quiz will be visible to students. If you are still in the process of setting up the quiz then it is highly advisable to leave this set to 'Hide'. Otherwise students might view or even attempt the quiz before it is tested and ready. This setting is common to all activities and can also be toggled by clicking on the eye icon behind the activity's name on the course page.

===Restrict access settings===
The [[Restrict_access_settings|Restrict access]] area becomes visible in Moodle activities and resource settings if [[Conditional_activities|Conditional Activities]] have been enabled.

==Group and User overrides==

[[File:overridesquiz.png]]

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. [[Media:groupuseroverride.png|Screenshot of settings]]

===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>Group 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 ''Settings > Site administration > Plugins > Activity modules > Quiz''.

The add a new quiz page may be simplified by selecting a number of options to be hidden by default and only displayed when users click the "Advanced settings" button.

==See also==

*[http://www.youtube.com/watch?v=rFnoNNrTx3c How to create a quiz video]

[[cs:Přidání/úprava testu]]
[[de:Test konfigurieren]]
[[fr:Ajouter/modifier un test]]

Dyskusja:Dock

2012-01-23T18:34:32Z

Hrynkiw: query re: tab ordering

How do I control the order of the docked tabs? "Weight" in the block settings doesn't seem to have an effect. Right now the default order seems to be alphabetical. (But then again, I only have two tabs.)

Dock

2012-01-23T18:32:25Z

Hrynkiw: corrected orientation of docked tabs from "horizontal" to "vertical"

Dyskusja:Dodawanie nowego kursu

2012-01-05T17:20:16Z

Hrynkiw: partial answer to previous query

"A button will then appear on the All courses page for users to request a new course."
Where is the "All courses" page in Moodle2+?

ETA: Answering my own question. Built the URL from scratch: http://your.moodle.here/course/index.php
Button is at the bottom of the page.
Haven't yet located this link anywhere (like Navigation) that Tom Teacher might find it. Building an HTML block to make it more visible.

Dyskusja:Dodawanie nowego kursu

2012-01-05T17:12:23Z

Hrynkiw: location of 'All courses' page

"A button will then appear on the All courses page for users to request a new course."

Where is the "All courses" page in Moodle2+?

Theme changes in 2.0

2010-03-17T19:25:50Z

Hrynkiw: /* Browser hacks */ Corrected minor typo

{{Work in progress}}
{{Infobox Project
|name = Theme changes
|state = Implementation
|tracker = MDL-20204
|discussion = [http://moodle.org/mod/forum/discuss.php?d=140089 HEADS UP: Major theme changes landing]
|assignee = [[User:Petr Škoda (škoďák)|Petr Škoda (škoďák)]] + feedback and ideas from other developers
}}
{{Moodle 2.0}}

=Goals=
The main goals are:
# easier theme customisations - both CSS and images
# simplify core and themes code
# significant performance improvements
# solve majority of browser caching problems
# use YUI CSS foundation
# allow themes to be stored in separate directory without www access (such as dataroot)

It should be easy to upgrade simple older themes. I think it is better if old themes are completely disabled with reasonable fallback mechanism. Why should we display broken themes during upgrade? Imagine users or teachers can select "broken" themes in the course edit page or a profile, I think it is more professional to display only new and upgraded themes in selectors instead of pretending old themes will work 100%. We have to make sure old themes will not cause fatal white screen errors.

=Design overview=

All theme files are served through two files ''/theme/styles.php'' and ''/theme/image.php''. More advanced themes may serve extra javascript files through the ''/theme/javascripts.php'' file and a new config option with list of JS files. This approach allows us to parse the resulting CSS and replace all image placeholders and theme settings with current values.

All CSS style sheets (including YUI, plugin CSS and parent themes) are merged into a single large CSS file served via the /theme/styles.php file. This script accepts following parameters:
* '''theme''' (string) - name of the theme
* '''rev''' (int) - theme revision number stored in $CFG->themerevision

All options and features are reviewed and optimised. Backwards compatibility is not a primary concern, future possibilities and easy maintenance are always favoured.

==Theme directory structure==

{| class="nicetable"
|-
! <center>''File/folder'''</center>
! <center>'''Description''</center>
|-
| db/ (optional)
| Installation and upgrade hooks - use of db tables is not recommended.
|-
| lang/
| Folder with standard language files - name of theme, usage information, settings. Standard themes store lang files in /lang/ for now.
|-
| layout/*.php
| Folder with page layout templates
|-
| pix/
| Folder with theme pictures - used from CSS or layout only, not used from other plugins.
|-
| pix_core/ (optional)
| Folder with overridden core images and icons from /pix/ folder
|-
| pix_plugins/ (optional)
| Folder with overridden plugin icons - structure is typeofplugin/pluginname/ which maps to pix folder in plugins
|-
| style/*.css
| Style sheet files referenced from the config.php.
|-
| config.php
| Theme configuration - see bellow.
|-
| lib.php (optional)
| Library functions - custom css post-processing, custom render factory, theme init function
|-
| renderers.php (optional)
| Custom renderers used from custom renderer factories.
|-
| settings.php (optional)
| Custom theme settings - colours, logos, etc. Settings are applied in custom css post-processing function.
|-
| version.php
| Needed for install and upgrade hooks, states compatibility with specific Moodle versions. Used for triggering of cache purging.
|}

==Theme config.php==

The theme config.php structure is simplified and a bit more flexible. The goal is to make overriding of parent themes simple and easy to understand. Please note global $THEME variable is not available any more, use theme property in current page instance instead.

<code php>$THEME->parents = array('standard', 'purple');</code>
Lists all parents top-down, each theme contains the full list of parents, this is non-recursive and more flexible specification without any limits. Originally the number of parent levels was restricted.

<code php>$THEME->sheets = array('styles_layout', 'styles_fonts', 'styles_color');</code>
The same as before, lists files from current theme directory.

<code php>$THEME->parents_exclude_sheets('standard'=>array('styles_moz'), 'purple'=>array('styles_fonts'));</code>
It is also posssible to use ''true'' instead of array in order to specify ''all'' sheets or all sheets in all parents, if not specified the value from the parent theme is used.

<code php>$THEME->editor_sheets = array('styles_tinymce');</code>
We can not load the full CSS file into the HTML editor's content area, instead we load editor sheet from lib/editor/editorname/editor_sheets.css and also sheets specified in theme.

<code php>$THEME->plugins_exclude_sheets('mod_book', 'gradereport_grader');</code>
Ideally all plugin specific CSS should be stored in styles.css file separately in each plugin. This option lists plugins that should be excluded from this theme, if not specified the value from the parent theme is used.

<code php>$THEME->layouts = array(...);</code>
The complete list of layouts is in theme/base/config.php. Page layouts are in fact high level templates that are using PHP syntax. The template files are stored in layout/ subdirectory. Each page layout has specification of block areas and link to template file. Themes may also reference layouts files from other themes.

<code php>$THEME->resource_mp3player_colors, $THEME->filter_mediaplugin_colors</code>
Obsoleted. If not specified the value from the parent theme is used. All these should be moved to real theme settings.

<code php>$THEME->rendererfactory = 'standard_renderer_factory';</code>
The same as before. It is the name of class that returns needed instances of core and plugin renderers. defined in core some library or theme/themename/lib.php or theme/themename/renderers.php

<code php>$THEME->csspostprocess = 'csspostprocess';</code>
Name of custom CSS post-processing function, this function is usually defined in theme/themename/lib.php.

<code php>
$THEME->javascripts = array('navigation');
$THEME->javascripts_footer = array('someJSlibrary');
</code>
List of extra javascript files that are included on each page. Themes can not include extra scripts from the theme folder because the folder may not be accessible via web.

=Implementation=

==One huge CSS sheet==

Each page includes only one huge style sheet. All theme sheets are served by a /theme/styles.php script. Page parameters specify the theme name and revision.

The CSS concatenation is done from the YUI CSS, styles.css from all plugins and theme style sheets starting with top most parent and current theme last, please note the order is very important. The algorithm is following:
# YUI2 CSS
## merge all YUI2 CSS into one file, respect correct order of files
# plugins CSS
## go through all plugins and search for styles.css - put the list into array, use component names as keys, locations as values
## filter out excluded sheets specified in current $THEME->plugins_exluded_sheetes
# theme CSS
## go through all sheets defined in all parents and store all $THEME->sheets in array
## filter out excluded sheets specified in current $THEME->parent_exluded_sheetes
# resolve real image locations
## regex search for <nowiki>[[pix:componentname|imagewithsibdirnoext]]</nowiki>
## priority is: current theme, parent themes, then plugin or YUI fodlers
## images in web accessible areas are linked directly, images in dataroot would have to go through /theme/image.php?theme=xxx&file=/sub/img&component=moodle&rev=-1
# apply theme admin settings - values and image locations

Please note that the current $PAGE->requires->css() is suitable mostly for user supplied CSS for data content such as the custom CSS used in mod/data/ module.

The YUI3 reset CSS is loaded separated before this huge combined CSS stylesheet, YUI3 loader may load CSS on the fly from Javascript.

==Theme caching==

Potential problems are:
* server performance - the merging of all CSS, parent themes and image resolving is relatively expensive
* bandwidth - longer caching, fewer files and optional gzip compression
* stale data in browser caches - different file needs to be served when anything in CSS changes

The theme CSS content depends on:
* current theme
* theme revision

The theme revision is stored in $CFG->themerev, it is an integer counter incremented after installation/upgrade of any plugin or core. The revision value -1 is used in theme designer mode to prevent the caching completely.

All images used both from PHP and CSS have to be cached too. This is handled automatically in /theme/image.php which accepts similar parameters like the styles.php script.

==The theme designer mode==

Administrator, theme designers and developers often need to tweak CSS or images. In previous versions users had to purge the browser caches manually.

In theme designer mode no CSS is cached on server or in browser, each changes are immediately visible. The switching on of this mode immediately invalidates old caches, the caching is turned on again after switching it off. This mode causes higher server load.

This mode also disables all CSS cleanup and compression, all comments are kept and extra debug information can be included in CSS.

This setting is available from the Appearance settings page.

==Performance improvements==

There are several possibilities for more performance improvements:
* storing of final CSS files in dataroot - caches need to be deleted after each theme revision change; this could significantly reduce server load
* longer lifetimes - revision parameter eliminates the stale CSS in browser cache completely , lower bandwidth consumption
* gzip compression - faster page loading on first page
* remove comments and useless white space
* etc.

==Browser hacks==

Old meta.php was used mostly for conditional loading of IE specific hacks. Open University developed alternative solution which adds browser specific classes to body html element. This can be implemented in the pagelib method returning standard body tags.

<body class="ie ie7">

#mypage .whatever {
/** normal rules */
}
.ie6#mypage .whatever {
/** broken rules */
}

OU used these hacks not only for IE ;-)

==RTL support==

Originally RTL tweaks were stored in separate files. Now we use the same body class tweaks as described above.

<body class="dir-rtl">

#mypage .whatever {
/** normal rules */
}
.dir-rtl #mypage .whatever {
/** RTL rules */
}

==YUI==

Moodle started using YUI framework around 1.7, until 2.0dev we did not use any UI widgets that required CSS. The problem is that the YUI needs to be loaded before theme and plugin CSS, second problem is that standard YUI CSS requires reset CSS which greatly improves A-grade browser compatibility and helps theme designers.

YUI3 implements new loaders both for CSS and JS, there is a complementing PHP dependency loader for YUI.

===YUI CSS foundation===

Moodle styles are based on YUI foundation? Why not? The benefits are:
* eliminates some different HTML defaults (margins, paddings, font sizes, etc.) [http://developer.yahoo.com/yui/reset/ (YUI CSS Reset)]
* consistent font sizing and better font-family degradation [http://developer.yahoo.com/yui/fonts/ (YUI CSS Fonts)]
* the standard YUI CSS is already built on top of this foundation
* incredibly simple table-less page layouts that include nesting [http://developer.yahoo.com/yui/fonts/ (YUI CSS Grids)] (optional, themes do not have to use it for layout)

===YUI widgets customisation===

The standard YUI CSS has to be loaded after YUI CSS Base (Reset+Fonts+Grids), but before our own CSS. Overriding of YUI stylesheets should not depend on the order of loading, we only guarantee that the YUI CSS foundation sheets are loaded before any other CSS, customisations of YUI skins has to use moodle class selectors.

===YUI versioning===

In 1.9 we store all YUI files in /lib/yui/ folder, this was a problem when upgrading to YUI version from upstream because the old files could be still cached in browsers.

In 2.0 we are finally replicating the YAHOO directory structures, each new version is stored in separate directory.

===Combination of YUI 2 and 3===

YUI 3 uses JS autoloading which is a great step forward and simplification. Unfortunately we still need the YUI2 libraries around for some time, luckily YUI2 libraries may coexist with YUI3 code.

==The image resolver==

Images are used in html code and in CSS style sheets. The problem is easy to solve in PHP code, partial solution was already present in Moodle 1.9 - see $CFG->pixpath

In 2.0dev there was implemented a new icon_finder class, it can be replaced by much simpler rules, we could also add pix support into all plugins.

Image locations:
* /mod/modulename/pix/, blocks/blockname/pix/ - in all plugins
* /theme/themename/pix/ - theme images
* /theme/themename/pix_core/ - overridden images from core /pix/ folder
* /theme/themename/pix_plugins/plugin/plugintype/ - overriding of plugin images in themes

The standard API is <code>$OUTPUT->pix_url($componentname, $imagename, encoded)</code> when used from PHP and <nowiki>[[pix:componentname|imagename]]</nowiki> if used in CSS.

Image resolved allows us to serve images from dataroot via /theme/image.php script and also solves all browser caching issues.

==Themes in extra directory==

Themes in dataroot is a frequently requested feature. Some admins might not like this, it should be optional. Some really advanced themes with lots of custom files might not be compatible at first. In fact it does not have to be dataroot, this location is configurable via $CFG->themedir.

In the stable branch we have a strange mix of standard themes. Moodle 2.0 is expected to include following themes:
* base - bare bones minimal theming that most other themes build on
* standard - basic theme that can be used as base for really simple themes (the exact look of new standard theme is not decided yet)
* customcolor - standard with admin specified colour palette and custom logos (not confirmed)
* and many other fancy modern themes like anomaly ( optionally with multiple configuration settings)

Other contrib themes could be available via web interface from Moodle configuration in some future Moodle version.

==Admin theme settings==

Very often users need to make small tweaks to standard themes such as different colour or logos. There should be a way to keep this settings in config_plugin and files separately in dataroot. Settings are placed in /theme/themename/settings.php. This new feature could significantly reduce known theme upgrade problems in the future.

This feature replaces the original CSS constants and will probably use the same syntax. The original CSS constants required modifications in dirroot which was in some cases unacceptable. CSS constants would not be compatible with automatic updates vie web interface anyway.

This feature requires advanced caching of CSS. These settings and files should be available in layouts and renderers too.

The actual replacing of setting placeholders by setting values is performed in custom css post-processing function specified in config.php. Logos and other custom images would be specified as external URLs, later we could also add basic support for storage of these custom theme files in standard Moodle filesystem.

==Page layout==
Each page may specify one of standard page layouts that are defined in theme/base/config.php. It is not possible to add custom layouts.

Layout definition consists of:
* template file specification - template name + file name without extension
* definition of regions
* default region

New layouts will not be added in the STABLE CVS branches.

==Renderers==

Renderers are small methods that render visual elements using functional programming - our old style PHP style.

Module may define own renderer class and use own renderer methods. Themes may override both core and plugin renderers however you need to have some more advanced understanding of PHP and Moodle design in general.

==Templates (maybe in future)==

Similar to page layouts but much smaller parts of UI that are embedded into pages. This is a new feature that is not used in Moodle core yet.

Code developers may choose to use templates instead of renderers for some larger parts of UI, they may also use renderers from templates. The major difference is that templates accept just one $DATA object with all parameters, templates might be also much easier to use&understand for typical theme designers.

The original emulated templates approach was replaced because it was designed for code developers, not designers. I think it is much easier to just copy templates from core or plugins into themes and tweak them, instead of the reverse engineering of the renderers.

Please note this does not mean that Moodle is switching to templates now, but technically we could, plugin developers would decide to do so independently. This topic should be revisited in Moodle 2.1dev.

==Other API changes==

* added ''course'' layout
* $PAGE->set_generaltype() replaced by $PAGE->set_pagelayout() because it really switches to one of the layouts from the standard theme; also the complete list of layouts is given in theme/standard/config.php - there is no way to add plugin layouts, the $PAGE->set_pagelayout() is used from core and plugin code, not from themes, so it is not possible to add new layouts at all (and never was)
* name things ''moodle_*'' only if potential conflicts exist, everything plugin related should be named ''componentname_'' (mod_ is usually an exception)- this was discussed several times before; renamed ''moodle_core_renderer' class to ''core_renderer'', etc.
* themes are now real plugins with capabilities, lang packs, upgrade code, settings, upgrade code, etc. - it is not recommended to create new db table though

=Backwards compatibility and upgrades=

BC is very limited, all themes and modules need to be manually updated. Keeping old themes during the upgrade must not cause fatal PHP errors. Old themes can be detected by searching for /theme/oldtheme/styles.php, this file will not be present in the new themes any more. Moodle core would simply use the specified parent theme or the standard theme.

==Theme upgrade steps==
# delete styles.php
# redefine all config.php options - in majority of cases change parent value to parents array
# rename styles_ie6.css and styles_ie7.css to styles_layout_ie6.css and styles_layout_ie7.css - each normal sheet may have an extra sheet with _ieX suffix now, these are loaded automatically, excluding is applied based on $THEME->parents_exclude_sheets() info from the current theme
# rename rtl.css to styles_layout_rtl.css - again each normal style sheet may have extra sheet with _rtl suffix similar to IE hacks sheets
# delete header.html, footer.html and meta.php - obsoleted by $THEME->layouts option and new layout files
# add custom layouts and rendereds

In order to minimize confusion during the upgrade, the old themes will be ignored and will be listed os "Incompatible" on the theme selection page - this page is probably the first place admins go in order to diagnose theme problems.

==Module upgrade steps==
* rename mod/modname/styles.php to styles.css
* put all images into mod/modname/pix/
* replace $CFG->pixpath with $OUTPUT->pix_url('imagename', 'mod_modname')

==Removed features==
# '''sometheme/meta.php''' - used mostly for IE6/7 hacks, custom layouts may be used instead
# '''smartpix''' - completely obsoleted by the new image location resolution algorithm
# '''styles.php''' replaced by styles.css, supported in all plugin types - the PHP syntax is not needed anymore because images are specified using <nowiki>[[pix:component|dir/image]]</nowiki> syntax and we can also use custom css post-processors
# '''$CFG->pixpath''' replaced by $OUTPUT->pix_url()
# '''CSS constants''' replaced by the admin theme settings
# separate IE6 and IE7 sheets - replaced by body class attributes
# separate RTL sheets - replaced by body class attribute

=Expected reactions=

{| class="nicetable"
|-
! <center>'''User type'''</center>
! <center>'''Negative'''</center>
! <center>'''Positive'''</center>
|-
| Core developer
| none
| No backwards compatibility headaches. Powerful new features. More flexible API.
|-
| Contrib developer
| Has to learn new API and upgrade current code.
| New useful pix folder and standard styles.css in all plugins. $OUTPUT->pix_url() more flexible then old pixpath.
|-
| Theme designer
| Has to learn new theme API. Old advanced themes has to be completely redesigned. Has to understand YUI CSS foundation.
| They can finally override core and plugin images. Easier distribution of custom themes. New income opportunity. Basic theme structure is simplified. No browser caching issues when designing themes.
|-
| Administrator
| All themes need to be updated. Old themes are ignored.
| Much easier installation (optionally in dataroot) and easy customisation without code modification (images and colours for example). Much safer upgrades. Possibility to upgrade theme via web interface. No browser caching issues when upgrading themes. Better performance and lower server load.
|}

==See also==

Using Moodle forum discussions:
* [http://moodle.org/mod/forum/discuss.php?d=131219 Yet more theme changes proposal]
* [http://moodle.org/mod/forum/discuss.php?d=140089 HEADS UP: Major theme changes landing]
* [[Development:Output_renderers]]

[[Category:Themes]]

Theme changes in 2.0

2010-03-17T19:24:05Z

Hrynkiw: /* Design overview */ Corrected minor typos

{{Work in progress}}
{{Infobox Project
|name = Theme changes
|state = Implementation
|tracker = MDL-20204
|discussion = [http://moodle.org/mod/forum/discuss.php?d=140089 HEADS UP: Major theme changes landing]
|assignee = [[User:Petr Škoda (škoďák)|Petr Škoda (škoďák)]] + feedback and ideas from other developers
}}
{{Moodle 2.0}}

=Goals=
The main goals are:
# easier theme customisations - both CSS and images
# simplify core and themes code
# significant performance improvements
# solve majority of browser caching problems
# use YUI CSS foundation
# allow themes to be stored in separate directory without www access (such as dataroot)

It should be easy to upgrade simple older themes. I think it is better if old themes are completely disabled with reasonable fallback mechanism. Why should we display broken themes during upgrade? Imagine users or teachers can select "broken" themes in the course edit page or a profile, I think it is more professional to display only new and upgraded themes in selectors instead of pretending old themes will work 100%. We have to make sure old themes will not cause fatal white screen errors.

=Design overview=

All theme files are served through two files ''/theme/styles.php'' and ''/theme/image.php''. More advanced themes may serve extra javascript files through the ''/theme/javascripts.php'' file and a new config option with list of JS files. This approach allows us to parse the resulting CSS and replace all image placeholders and theme settings with current values.

All CSS style sheets (including YUI, plugin CSS and parent themes) are merged into a single large CSS file served via the /theme/styles.php file. This script accepts following parameters:
* '''theme''' (string) - name of the theme
* '''rev''' (int) - theme revision number stored in $CFG->themerevision

All options and features are reviewed and optimised. Backwards compatibility is not a primary concern, future possibilities and easy maintenance are always favoured.

==Theme directory structure==

{| class="nicetable"
|-
! <center>''File/folder'''</center>
! <center>'''Description''</center>
|-
| db/ (optional)
| Installation and upgrade hooks - use of db tables is not recommended.
|-
| lang/
| Folder with standard language files - name of theme, usage information, settings. Standard themes store lang files in /lang/ for now.
|-
| layout/*.php
| Folder with page layout templates
|-
| pix/
| Folder with theme pictures - used from CSS or layout only, not used from other plugins.
|-
| pix_core/ (optional)
| Folder with overridden core images and icons from /pix/ folder
|-
| pix_plugins/ (optional)
| Folder with overridden plugin icons - structure is typeofplugin/pluginname/ which maps to pix folder in plugins
|-
| style/*.css
| Style sheet files referenced from the config.php.
|-
| config.php
| Theme configuration - see bellow.
|-
| lib.php (optional)
| Library functions - custom css post-processing, custom render factory, theme init function
|-
| renderers.php (optional)
| Custom renderers used from custom renderer factories.
|-
| settings.php (optional)
| Custom theme settings - colours, logos, etc. Settings are applied in custom css post-processing function.
|-
| version.php
| Needed for install and upgrade hooks, states compatibility with specific Moodle versions. Used for triggering of cache purging.
|}

==Theme config.php==

The theme config.php structure is simplified and a bit more flexible. The goal is to make overriding of parent themes simple and easy to understand. Please note global $THEME variable is not available any more, use theme property in current page instance instead.

<code php>$THEME->parents = array('standard', 'purple');</code>
Lists all parents top-down, each theme contains the full list of parents, this is non-recursive and more flexible specification without any limits. Originally the number of parent levels was restricted.

<code php>$THEME->sheets = array('styles_layout', 'styles_fonts', 'styles_color');</code>
The same as before, lists files from current theme directory.

<code php>$THEME->parents_exclude_sheets('standard'=>array('styles_moz'), 'purple'=>array('styles_fonts'));</code>
It is also posssible to use ''true'' instead of array in order to specify ''all'' sheets or all sheets in all parents, if not specified the value from the parent theme is used.

<code php>$THEME->editor_sheets = array('styles_tinymce');</code>
We can not load the full CSS file into the HTML editor's content area, instead we load editor sheet from lib/editor/editorname/editor_sheets.css and also sheets specified in theme.

<code php>$THEME->plugins_exclude_sheets('mod_book', 'gradereport_grader');</code>
Ideally all plugin specific CSS should be stored in styles.css file separately in each plugin. This option lists plugins that should be excluded from this theme, if not specified the value from the parent theme is used.

<code php>$THEME->layouts = array(...);</code>
The complete list of layouts is in theme/base/config.php. Page layouts are in fact high level templates that are using PHP syntax. The template files are stored in layout/ subdirectory. Each page layout has specification of block areas and link to template file. Themes may also reference layouts files from other themes.

<code php>$THEME->resource_mp3player_colors, $THEME->filter_mediaplugin_colors</code>
Obsoleted. If not specified the value from the parent theme is used. All these should be moved to real theme settings.

<code php>$THEME->rendererfactory = 'standard_renderer_factory';</code>
The same as before. It is the name of class that returns needed instances of core and plugin renderers. defined in core some library or theme/themename/lib.php or theme/themename/renderers.php

<code php>$THEME->csspostprocess = 'csspostprocess';</code>
Name of custom CSS post-processing function, this function is usually defined in theme/themename/lib.php.

<code php>
$THEME->javascripts = array('navigation');
$THEME->javascripts_footer = array('someJSlibrary');
</code>
List of extra javascript files that are included on each page. Themes can not include extra scripts from the theme folder because the folder may not be accessible via web.

=Implementation=

==One huge CSS sheet==

Each page includes only one huge style sheet. All theme sheets are served by a /theme/styles.php script. Page parameters specify the theme name and revision.

The CSS concatenation is done from the YUI CSS, styles.css from all plugins and theme style sheets starting with top most parent and current theme last, please note the order is very important. The algorithm is following:
# YUI2 CSS
## merge all YUI2 CSS into one file, respect correct order of files
# plugins CSS
## go through all plugins and search for styles.css - put the list into array, use component names as keys, locations as values
## filter out excluded sheets specified in current $THEME->plugins_exluded_sheetes
# theme CSS
## go through all sheets defined in all parents and store all $THEME->sheets in array
## filter out excluded sheets specified in current $THEME->parent_exluded_sheetes
# resolve real image locations
## regex search for <nowiki>[[pix:componentname|imagewithsibdirnoext]]</nowiki>
## priority is: current theme, parent themes, then plugin or YUI fodlers
## images in web accessible areas are linked directly, images in dataroot would have to go through /theme/image.php?theme=xxx&file=/sub/img&component=moodle&rev=-1
# apply theme admin settings - values and image locations

Please note that the current $PAGE->requires->css() is suitable mostly for user supplied CSS for data content such as the custom CSS used in mod/data/ module.

The YUI3 reset CSS is loaded separated before this huge combined CSS stylesheet, YUI3 loader may load CSS on the fly from Javascript.

==Theme caching==

Potential problems are:
* server performance - the merging of all CSS, parent themes and image resolving is relatively expensive
* bandwidth - longer caching, fewer files and optional gzip compression
* stale data in browser caches - different file needs to be served when anything in CSS changes

The theme CSS content depends on:
* current theme
* theme revision

The theme revision is stored in $CFG->themerev, it is an integer counter incremented after installation/upgrade of any plugin or core. The revision value -1 is used in theme designer mode to prevent the caching completely.

All images used both from PHP and CSS have to be cached too. This is handled automatically in /theme/image.php which accepts similar parameters like the styles.php script.

==The theme designer mode==

Administrator, theme designers and developers often need to tweak CSS or images. In previous versions users had to purge the browser caches manually.

In theme designer mode no CSS is cached on server or in browser, each changes are immediately visible. The switching on of this mode immediately invalidates old caches, the caching is turned on again after switching it off. This mode causes higher server load.

This mode also disables all CSS cleanup and compression, all comments are kept and extra debug information can be included in CSS.

This setting is available from the Appearance settings page.

==Performance improvements==

There are several possibilities for more performance improvements:
* storing of final CSS files in dataroot - caches need to be deleted after each theme revision change; this could significantly reduce server load
* longer lifetimes - revision parameter eliminates the stale CSS in browser cache completely , lower bandwidth consumption
* gzip compression - faster page loading on first page
* remove comments and useless white space
* etc.

==Browser hacks==

Old meta.php was used mostly for conditional loading of IE specific hacks. Open university developed alternative solution which adds browser specific classes to body html element. This can be implemented in the pagelib method returning standard body tags.

<body class="ie ie7">

#mypage .whatever {
/** normal rules */
}
.ie6#mypage .whatever {
/** broken rules */
}

OU used these hacks not only for IE ;-)

==RTL support==

Originally RTL tweaks were stored in separate files. Now we use the same body class tweaks as described above.

<body class="dir-rtl">

#mypage .whatever {
/** normal rules */
}
.dir-rtl #mypage .whatever {
/** RTL rules */
}

==YUI==

Moodle started using YUI framework around 1.7, until 2.0dev we did not use any UI widgets that required CSS. The problem is that the YUI needs to be loaded before theme and plugin CSS, second problem is that standard YUI CSS requires reset CSS which greatly improves A-grade browser compatibility and helps theme designers.

YUI3 implements new loaders both for CSS and JS, there is a complementing PHP dependency loader for YUI.

===YUI CSS foundation===

Moodle styles are based on YUI foundation? Why not? The benefits are:
* eliminates some different HTML defaults (margins, paddings, font sizes, etc.) [http://developer.yahoo.com/yui/reset/ (YUI CSS Reset)]
* consistent font sizing and better font-family degradation [http://developer.yahoo.com/yui/fonts/ (YUI CSS Fonts)]
* the standard YUI CSS is already built on top of this foundation
* incredibly simple table-less page layouts that include nesting [http://developer.yahoo.com/yui/fonts/ (YUI CSS Grids)] (optional, themes do not have to use it for layout)

===YUI widgets customisation===

The standard YUI CSS has to be loaded after YUI CSS Base (Reset+Fonts+Grids), but before our own CSS. Overriding of YUI stylesheets should not depend on the order of loading, we only guarantee that the YUI CSS foundation sheets are loaded before any other CSS, customisations of YUI skins has to use moodle class selectors.

===YUI versioning===

In 1.9 we store all YUI files in /lib/yui/ folder, this was a problem when upgrading to YUI version from upstream because the old files could be still cached in browsers.

In 2.0 we are finally replicating the YAHOO directory structures, each new version is stored in separate directory.

===Combination of YUI 2 and 3===

YUI 3 uses JS autoloading which is a great step forward and simplification. Unfortunately we still need the YUI2 libraries around for some time, luckily YUI2 libraries may coexist with YUI3 code.

==The image resolver==

Images are used in html code and in CSS style sheets. The problem is easy to solve in PHP code, partial solution was already present in Moodle 1.9 - see $CFG->pixpath

In 2.0dev there was implemented a new icon_finder class, it can be replaced by much simpler rules, we could also add pix support into all plugins.

Image locations:
* /mod/modulename/pix/, blocks/blockname/pix/ - in all plugins
* /theme/themename/pix/ - theme images
* /theme/themename/pix_core/ - overridden images from core /pix/ folder
* /theme/themename/pix_plugins/plugin/plugintype/ - overriding of plugin images in themes

The standard API is <code>$OUTPUT->pix_url($componentname, $imagename, encoded)</code> when used from PHP and <nowiki>[[pix:componentname|imagename]]</nowiki> if used in CSS.

Image resolved allows us to serve images from dataroot via /theme/image.php script and also solves all browser caching issues.

==Themes in extra directory==

Themes in dataroot is a frequently requested feature. Some admins might not like this, it should be optional. Some really advanced themes with lots of custom files might not be compatible at first. In fact it does not have to be dataroot, this location is configurable via $CFG->themedir.

In the stable branch we have a strange mix of standard themes. Moodle 2.0 is expected to include following themes:
* base - bare bones minimal theming that most other themes build on
* standard - basic theme that can be used as base for really simple themes (the exact look of new standard theme is not decided yet)
* customcolor - standard with admin specified colour palette and custom logos (not confirmed)
* and many other fancy modern themes like anomaly ( optionally with multiple configuration settings)

Other contrib themes could be available via web interface from Moodle configuration in some future Moodle version.

==Admin theme settings==

Very often users need to make small tweaks to standard themes such as different colour or logos. There should be a way to keep this settings in config_plugin and files separately in dataroot. Settings are placed in /theme/themename/settings.php. This new feature could significantly reduce known theme upgrade problems in the future.

This feature replaces the original CSS constants and will probably use the same syntax. The original CSS constants required modifications in dirroot which was in some cases unacceptable. CSS constants would not be compatible with automatic updates vie web interface anyway.

This feature requires advanced caching of CSS. These settings and files should be available in layouts and renderers too.

The actual replacing of setting placeholders by setting values is performed in custom css post-processing function specified in config.php. Logos and other custom images would be specified as external URLs, later we could also add basic support for storage of these custom theme files in standard Moodle filesystem.

==Page layout==
Each page may specify one of standard page layouts that are defined in theme/base/config.php. It is not possible to add custom layouts.

Layout definition consists of:
* template file specification - template name + file name without extension
* definition of regions
* default region

New layouts will not be added in the STABLE CVS branches.

==Renderers==

Renderers are small methods that render visual elements using functional programming - our old style PHP style.

Module may define own renderer class and use own renderer methods. Themes may override both core and plugin renderers however you need to have some more advanced understanding of PHP and Moodle design in general.

==Templates (maybe in future)==

Similar to page layouts but much smaller parts of UI that are embedded into pages. This is a new feature that is not used in Moodle core yet.

Code developers may choose to use templates instead of renderers for some larger parts of UI, they may also use renderers from templates. The major difference is that templates accept just one $DATA object with all parameters, templates might be also much easier to use&understand for typical theme designers.

The original emulated templates approach was replaced because it was designed for code developers, not designers. I think it is much easier to just copy templates from core or plugins into themes and tweak them, instead of the reverse engineering of the renderers.

Please note this does not mean that Moodle is switching to templates now, but technically we could, plugin developers would decide to do so independently. This topic should be revisited in Moodle 2.1dev.

==Other API changes==

* added ''course'' layout
* $PAGE->set_generaltype() replaced by $PAGE->set_pagelayout() because it really switches to one of the layouts from the standard theme; also the complete list of layouts is given in theme/standard/config.php - there is no way to add plugin layouts, the $PAGE->set_pagelayout() is used from core and plugin code, not from themes, so it is not possible to add new layouts at all (and never was)
* name things ''moodle_*'' only if potential conflicts exist, everything plugin related should be named ''componentname_'' (mod_ is usually an exception)- this was discussed several times before; renamed ''moodle_core_renderer' class to ''core_renderer'', etc.
* themes are now real plugins with capabilities, lang packs, upgrade code, settings, upgrade code, etc. - it is not recommended to create new db table though

=Backwards compatibility and upgrades=

BC is very limited, all themes and modules need to be manually updated. Keeping old themes during the upgrade must not cause fatal PHP errors. Old themes can be detected by searching for /theme/oldtheme/styles.php, this file will not be present in the new themes any more. Moodle core would simply use the specified parent theme or the standard theme.

==Theme upgrade steps==
# delete styles.php
# redefine all config.php options - in majority of cases change parent value to parents array
# rename styles_ie6.css and styles_ie7.css to styles_layout_ie6.css and styles_layout_ie7.css - each normal sheet may have an extra sheet with _ieX suffix now, these are loaded automatically, excluding is applied based on $THEME->parents_exclude_sheets() info from the current theme
# rename rtl.css to styles_layout_rtl.css - again each normal style sheet may have extra sheet with _rtl suffix similar to IE hacks sheets
# delete header.html, footer.html and meta.php - obsoleted by $THEME->layouts option and new layout files
# add custom layouts and rendereds

In order to minimize confusion during the upgrade, the old themes will be ignored and will be listed os "Incompatible" on the theme selection page - this page is probably the first place admins go in order to diagnose theme problems.

==Module upgrade steps==
* rename mod/modname/styles.php to styles.css
* put all images into mod/modname/pix/
* replace $CFG->pixpath with $OUTPUT->pix_url('imagename', 'mod_modname')

==Removed features==
# '''sometheme/meta.php''' - used mostly for IE6/7 hacks, custom layouts may be used instead
# '''smartpix''' - completely obsoleted by the new image location resolution algorithm
# '''styles.php''' replaced by styles.css, supported in all plugin types - the PHP syntax is not needed anymore because images are specified using <nowiki>[[pix:component|dir/image]]</nowiki> syntax and we can also use custom css post-processors
# '''$CFG->pixpath''' replaced by $OUTPUT->pix_url()
# '''CSS constants''' replaced by the admin theme settings
# separate IE6 and IE7 sheets - replaced by body class attributes
# separate RTL sheets - replaced by body class attribute

=Expected reactions=

{| class="nicetable"
|-
! <center>'''User type'''</center>
! <center>'''Negative'''</center>
! <center>'''Positive'''</center>
|-
| Core developer
| none
| No backwards compatibility headaches. Powerful new features. More flexible API.
|-
| Contrib developer
| Has to learn new API and upgrade current code.
| New useful pix folder and standard styles.css in all plugins. $OUTPUT->pix_url() more flexible then old pixpath.
|-
| Theme designer
| Has to learn new theme API. Old advanced themes has to be completely redesigned. Has to understand YUI CSS foundation.
| They can finally override core and plugin images. Easier distribution of custom themes. New income opportunity. Basic theme structure is simplified. No browser caching issues when designing themes.
|-
| Administrator
| All themes need to be updated. Old themes are ignored.
| Much easier installation (optionally in dataroot) and easy customisation without code modification (images and colours for example). Much safer upgrades. Possibility to upgrade theme via web interface. No browser caching issues when upgrading themes. Better performance and lower server load.
|}

==See also==

Using Moodle forum discussions:
* [http://moodle.org/mod/forum/discuss.php?d=131219 Yet more theme changes proposal]
* [http://moodle.org/mod/forum/discuss.php?d=140089 HEADS UP: Major theme changes landing]
* [[Development:Output_renderers]]

[[Category:Themes]]

Broken/Theme changes in 2.0

2010-03-17T19:23:06Z

Hrynkiw:

I think this is a great system. Some comments on specific issues:

1. Browser-specific stylesheets - is it time to move away from these?

The OU system for this is a lot better. We add special classes to body (in addition to whatever's normally there), so you have

<body class="ie ie7">

or

<body class="gecko gecko19">

Classes indicate the browser engine and version so that we can specify a generic engine if a problem affects all versions, or a specific version.

This means you can put the IE exceptions right next to the standard rules and they can be included in all stylesheets for any module. So you do

#mypage .whatever {
/** normal rules */
}

.ie6#mypage .whatever {
/** broken rules */
}

Note that we don't just need exceptions for IE. Over time we've needed rare (single) exceptions for Firefox (hence 'gecko' stuff above; the issue was actually only in gecko18 I think) and WebKit too.

IMO this system should be adopted in core Moodle. It's very simple and is far preferable to either CSS hacks (appalling) or separate stylesheets (unmaintainable).

2. Debugging mode

Maybe developer debug mode should send a special revision number (rev=debug) in order to regenerate the css every time, and send it without the expires header etc. That would probably make it pretty slow though.

Alternatively, this could be an additional option in the debugging page so that you can turn on 'CSS debugging' which would sent the rev=debug on every page, and turn it off when debugging other stuff that isn't css.

having to manually update the number every single time you change css would be a huge annoyance when debugging css problems imo so I think one of these solutions is better.

3. Removing comments

Removing comments would be great.

It's not only a performance issue, but:

a. Because of the performance concern developers (including me) tend to not include comments at all, this is really bad for maintainability.

b. If a student looks into our code and it says something 'unprofessional' like 'only needed because IE sucks' they might in theory complain - yes I have genuinely had a student complaint for using the word 'sucks' in public - so this is another discouragement for developers to comment properly.

4. Performance

If these are served for lifetime (ie expires 10 years in future) as they should be, I think this would actually improve performance for most sites (that see a lot of repeat visits), even if it takes 50x longer to serve the css itself...

That's it, everything else is awesome. :)

[[User:sam marshall|sam marshall]]

------

2. from sam's suggestions is already done. We should make sure it is not lost in any changes.

I don't see any point in multiple parent themes. Too complicated. Theme + parent + standard is sufficient. I guess once you are at two parents like that, it is no harder to code a general array, it is just much easier for theme developers to screw up. Oh, I guess there is not harm in the extra flexibility.

No problem that this does not include ->requires->css. We should comment that to make it clear that you rarely need to use it, but keep it as an emergency fallback for people who are doing random customisations.

I proposed getting rid of meta.php before, but martin vetoed it. Somewhere in the themes forum is a post form me where I list all the ways it is currently used in core and contrib. I still think we should get rid of it.

Moodle 1.9 themes still work in Moodle 2.0. I would like that to continue to be true. I think it is still possible. Look at the code in theme_config class for handling legacy config.php files, and the code in deprecatedlib.php that implements the old function for serving CSS.

--[[User:Tim Hunt|Tim Hunt]] 17:00, 21 August 2009 (UTC)

------

2. yes, I considered this too - I called this theme designer mode. I am not a big friend to using DEBUG_DEVELOPER for this, that is why I proposed it as separate option.

Why not multiple parents when it is so easy to implement?

I do not understand the "emergency need" for ->requires->css() - the /local/ plug-ins are the correct place for emergency hacks, not the core. You just create new dir in /local/something/styles.css and it will be included automatically on all pages. The problem with custom CSS is that it can not fit into the one huge stylesheet - you can not load it before it because YUI reset will alter it and also after because it would not by style-able via themes which is not an option imo.

I wanted to intentionally disable all old themes, I agree it should be as easy to upgrade as possible, but I still think that admins should be required to take some actions manually or else they will keep complaining that themes are "broken" in 2.0 and nobody told them they should update them. I think the ideal solution would be to allow easy downloads of themes via the Moodle UI instead of full backwards compatibility :-)

[[User:Petr Škoda (škoďák)|Petr Škoda (škoďák)]] 19:34, 21 August 2009 (UTC)

:I think the thing is that for a lot of less experienced admins, for example, the teacher in a school who does it in their same time, they may have tinkered with their theme in the past (or the person before them may have) and they may not remember what was done. Tinkering with the theme, for example changing the logo or a few colours, may be one of the most For them, we want the upgrade to be as simple as possible. If we cannot keep their old theme working, is there any way we can automate the upgrade? Or do we just encourage them to use one of Patrick Malley's nice new themes, and show them how easy it is to add their own logo to one?--[[User:Tim Hunt|Tim Hunt]] 20:09, 21 August 2009 (UTC)

------

I like the sound of these proposals generally.

1) Themes in dataroot: I assume the intention is to completely remove any executable code in these themes?

2) Breaking backwards compatibility: This is the one close to my heart, I just did a quick find and it'll mean we have to update 1003 custom themes (as today stands) which will obviously be a big barrier to Moodle 2.0 upgrade. Having said that I don't necessarily think its a bad idea. Having 'limited' backwards compatibility where by the theme 'just' works might be of limited value (i'm sure we'd need to convert all themes eventually anyway). We need to come up with clear reasons why we need to break backwards compatibility to satisfy less tolerant people than me though ;-)

3) Removing $CFG->themeww/themedir. From anecdotal evidence I think I might be the only person in the world using this feature and I think there are probably better ways to achieve what we are doing, so I am not going to argue very hard to keep it..

I wrote some guidelines to give theme authors a few years ago, which sort of documents the stupid things we get in submitted themes (overriding all styles, uncessarily altering header/footer etc). I put these in Moodle Docs, might be interesting to you or not: [[CLEO_Moodle_Theme_Guidelines]].

In most cases, the 'flexibilty/power' we give theme authors at the moment leads to more breakage due to use of unnecessary modifications in something which could be achieved in a 10 line css file..

--[[User:Dan Poltawski|Dan Poltawski]] 09:45, 22 August 2009 (UTC)

------

== Caching of 'minified' unified stylesheet? ==
Shortly after Tim did his javascript cleanup, I did a hacky little test of minifying all included javascript and caching it by md5 hash. I didn't get very far, but one thing I did notice was that the minification process was surprisingly slow. Serving the single stylesheet might suffer from this problem also if we do additional processing. Do we need caching of the compiled stylesheets?
--[[User:Dan Poltawski|Dan Poltawski]] 19:29, 25 August 2009 (UTC)

Yes, we definitely need caching. I am pretty sure that is in the proposal.--[[User:Tim Hunt|Tim Hunt]] 21:18, 25 August 2009 (UTC)

Apologies.. just found 'storing of final CSS files in dataroot - caches need to be deleted after each theme revision change; this could significantly reduce server load' --[[User:Dan Poltawski|Dan Poltawski]] 21:56, 25 August 2009 (UTC)

Suggestions for improvement of language (not content):

Replace:
It should be easy to upgrade simple older themes. I think it is better if old themes are completely disabled with reasonable fallback mechanism. Why should we display broken themes during upgrade? Imagine users or teachers can select "broken" themes in the course edit page or a profile, I think it is more professional to display only new and upgraded themes in selectors instead of pretending old themes will work 100%. We have to make sure old themes will not cause fatal white screen errors.

With:
It should be easy to upgrade simple older themes. It would be better if old themes were completely disabled with a reasonable fallback mechanism. We should not display broken themes during upgrade; users or teachers should not be able to select "broken" themes in the course edit page or profile. It is more professional to display only new and upgraded themes in the selectors. We must make sure old themes will not cause fatal white screen errors.

error/moodle/No questions found

2009-10-20T16:54:19Z

Hrynkiw: one more language tweak

Default moodle code doesn't cause an situation where it displays the error that you've just seen.

Mostly developers who play with the core files and altering the code sequence on them get these kind of errors.

This error denotes that you have created a quiz activity and have not assigned any questions to it, but calling the grade functionalities with respect to that particular quiz.

'''Note:'''

Am not sure about other languages, but in Brazilian Spanish, Brazilian Portuguese, Portuguese, Spanish these errors are not translated

--[[User:ravi s|ravi s]] 10:13, 22 May 2009 (UTC) Ravi Shankar.S

error/moodle/No questions found

2009-10-20T16:53:45Z

Hrynkiw: corrected spelling errors and capitalizations

Default moodle code doesn't cause an situation where it displays the error what you saw right now.

Mostly developers who play with the core files and altering the code sequence on them get these kind of errors.

This error denotes that you have created a quiz activity and have not assigned any questions to it, but calling the grade functionalities with respect to that particular quiz.

'''Note:'''

Am not sure about other languages, but in Brazilian Spanish, Brazilian Portuguese, Portuguese, Spanish these errors are not translated

--[[User:ravi s|ravi s]] 10:13, 22 May 2009 (UTC) Ravi Shankar.S

Quiz settings

2009-02-09T23:39:28Z

Hrynkiw: /* Overall feedback */

{{Quizzes}}

Creating a new quiz is a two-step process. In the first step you [[Teacher_documentation#Activity_modules|create]] the quiz activity and set its options which specify the rules for interacting with the quiz. In a second step you will then [[mod/quiz/edit|edit the quiz]] to add questions to it. This page describes the options you can set for the quiz activity, the page [[mod/quiz/edit|Editing a quiz]] describes how to set up the questions for the quiz.

'''Quiz options'''
There is a large number of options and your administrator should already have chosen the default values for most of them so that you will not have to modify them for the type of quiz that you use most often. The administrator may also have classified some of the settings as 'advanced' which means that they will be hidden from the set-up screen by default. This can help to keep the screen simpler. You can turn on the display of these advanced options by clicking on the '''Show advanced settings''' button. They will then remain visible until you click on '''Hide advanced settings'''.

==General section==
;Name
This is the standard name field that every activity has. The name will be used for the link text on the course page and also on the [[mod/quiz/index|quiz index screen]].

;Introduction
:Write an introduction for the quiz. Be sure to include any special instructions for taking the quiz like the number of attempts allowed or scoring rules. This introduction will be shown to the student already on the [[mod/quiz/view|quiz introduction screen]] that they reach after clicking on the quiz name on the course page. So they can see this description before they click on the "Attempt quiz" link and thus before the quiz timer is started (if used).

==Timing section==
;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.

;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 under [[Adding/updating_a_quiz#Students_may_review_section|Students may review]].

;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:

# Javascript support in the browser becomes mandatory - this allows the timer to work correctly.
# A floating timer window is shown with a countdown
# 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 spends more than 60 seconds over the allotted time then the quiz is automatically graded zero

Note: Particular students may be given unlimited time to attempt a quiz which has a time limit set by allowing the capability [[Capabilities/mod/quiz:ignoretimelimits|mod/quiz:ignoretimelimits]].

==Display section==
;Questions per 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.

;Shuffle questions
:If you enable this option, then the order of questions in the quiz will be randomly shuffled each time a student starts a new attempt at the quiz. This is '''not''' related to the use of [[Editing_a_quiz#Adding_random_questions|Random Questions]], this is only about the displayed order of questions. The intention is to make it a little harder for students to copy from each other.

;Shuffle answers
:If you enable this option, then the order of answers within each question will be randomly shuffled each time a student attempts this quiz. Of course, this only applies to questions that have multiple answers displayed, such as Multiple Choice or Matching Questions. The intention is simply to make it a little harder for students to copy from each other. This option is '''not''' related to the use of [[Editing_a_quiz#Adding_random_questions|Random Questions]].

:'''Note:''' Any matching and multiple choice questions in your quiz also have their own 'shuffle' setting. The options for these questions will shuffle '''only''' if the shuffle options for the quiz ''and'' the question are both turned on.

==Attempts section==
;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. If the quiz is randomized then the student will get a new version for each attempt. This is useful for practice purposes.

;Each attempt builds on the last
: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.

;Adaptive mode

:Adaptive questions allow students to have multiple attempts at the question before moving on to the next question. The adaptive question can adapt itself to the student's answer, for example by giving some hints before asking the student to try again. These kinds of questions are new to Moodle and will be described more on the page [[Adaptive questions]].

:If you choose Yes for this option then the student will be allowed multiple responses to a question even within the same attempt at the quiz. So for example if the student's response is marked as incorrect the student will be allowed to try again immediately. However, depending on the '''Apply penalties''' setting, a penalty will usually be subtracted from the student's score for each wrong response.

:In adaptive mode an additional Submit button is shown for each question. If the student presses this button then the response to that particular question is submitted to be scored and the mark achieved is displayed to the student. If the question is an adaptive question then it is displayed in its new state that takes the student's answer into account and will in many cases ask the student for another input. In the simplest adaptive questions this new state may differ only in the feedback text and will prompt the student to try again; in a more sophisticated adaptive question also the question text and even the interaction elements can change.

==Grades section==
;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

;Apply penalties
:If a quiz is run in adaptive mode then a student is allowed to try again after a wrong response. In this case you may want to impose a penalty for each wrong response to be subtracted from the final mark for the question. The amount of penalty is chosen individually for each question when setting up or editing the question.

:This setting has no effect unless the quiz is run in adaptive mode.

;Decimal points
:This option determines how many digits will be shown after the decimal point 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.

==Review options section==

This section controls what information students will be shown when they review their past attempts at this, and during the attempt in adaptive mode.

The various pieces of information that can be controlled are:
; Responses : What the student entered in response to the question.
; Answers : The correct answer to the question. (See note below)
; Feedback : The pieces of feedback that are specific to the student's response.
; General feedback : The general feedback for the question, which does not depend on the student's response.
; Scores : Numerical information about the score the student received.
; Overall feedback : The [[#Overall feedback]] for the whole attempt, which is set up further down the settings form.

For each of these items you can when the students can see it:
; 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).

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.

==Security section==
;Show quiz in a "secure" window
:The "secure" window tries to provide a little more security for quizzes (making copying and cheating more difficult) by restricting some of the things that students can do with their browsers.

:What happens is that:

# Javascript is made a requirement.
# The quiz appears in a new fullscreen window.
# Some mouse actions on the text are prevented.
# Some keyboard commands are prevented.

:NOTE: This security is NOT watertight. Do NOT rely on these protections as your sole strategy. It is impossible to implement complete protection of quizzes in a web environment so please do not rely on this option if you are really worried about students cheating. Other strategies you can try are to create really large databases of questions from which you randomly choose questions, or even better, rethink your overall assessment to put more value on constructive forms of activity such as forum discussions, glossary building, wiki writing, workshops, assignments etc.

;Require password

:This field is optional.

: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
:This field is optional.

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

==Common Module settings==
;Group mode
:Here you can choose whether the quiz should be organized by group. This only has an effect on the review screens of the teachers where it determines which groups of students they see.

;Visible to students
:Determines whether the quiz will be visible to students. If you are still in the process of setting up the quiz then it is highly advisable to leave this set to 'Hide'. Otherwise students might view or even attempt the quiz before it is tested and ready. This setting is common to all activities and can also be toggled by clicking on the eye icon behind the activity's name on the course page.

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

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.

==See also==

*[[Quiz permissions]]
*[http://www.youtube.com/watch?v=rFnoNNrTx3c How to create a quiz video]
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=75101 Can the default maximum time limit be extended?] forum discussion

[[cs:Přidání/úprava testu]]
[[de:Test anlegen]]
[[fr:Ajouter/modifier un test]]

NanoGong

2009-01-20T18:14:05Z

Hrynkiw: /* Tips & Tricks */

{{stub}}

NanoGong provides a very simple and transparent voice support for Moodle. Using a NanoGong activity and filter, it provides two different types of voice support for Moodle.

NanoGong icon can be used to record, playback and save a voice file, in a web page. The playback can be changed by the listener. The Listener's version of can be saved to the listener's hard disk. A NanoGong activity allows the student to submit their recording to the teacher.

==Features==
*Record at one speed
*Create individual copy at a different speed
*Save copy on local hard drive
*Student can send back to teacher

==Tips & Tricks==

*''Note:'' When downloaded, the HTML area (HTML edit tool) for a specific version of Moodle, will change the core Moodle code.
*'''Warning 2:''' When you install Nanogong in 1.9.x, you must also visit the admin page of the HTML-editor and switch the editorhidebuttons off for the Nanogong button. (default hide is on after install)
* If you install the minimum NanoGong (that is, without the HTML editor component), only the student role has the ability to record. The teacher can create a NanoGong activity and adjust the activity settings, but will not see any NanoGong recorder. To give the teacher access to the NanoGong recorder, the HTML editor component must be installed.

==See also==
*[http://moodle.org/mod/data/view.php?d=13&rid=1209&filter=1 NanoGong 3] is a Modules and plugins database page that has downloads and more information.
*Discussions:
**Please create or find a discussion topic in the [http://moodle.org/mod/forum/view.php?id=44 Contributed Code forum]
**The contributor also maintains a Moodle site that contains one or more [http://gong.ust.hk/moodle forums using and supporting NanoGong], outside of Moodle.org .
*Additional documentation
**[http://gong.ust.hk/nanogong/moodle_inst.html Installing NanoGong in Moodle] (outside of Moodle.org).

[[Category:Contributed code]]

NanoGong

2009-01-19T23:39:05Z

Hrynkiw: /* See also */ Made link to installation instructions more visible

{{stub}}

NanoGong provides a very simple and transparent voice support for Moodle. Using a NanoGong activity and filter, it provides two different types of voice support for Moodle.

NanoGong icon can be used to record, playback and save a voice file, in a web page. The playback can be changed by the listener. The Listener's version of can be saved to the listener's hard disk. A NanoGong activity allows the student to submit their recording to the teacher.

==Features==
*Record at one speed
*Create individual copy at a different speed
*Save copy on local hard drive
*Student can send back to teacher

==Tips & Tricks==

*''Note:'' When downloaded, the HTML area (HTML edit tool) for a specific version of Moodle, will change the core Moodle code.
*'''Warning 2:''' When you install Nanogong in 1.9.x, you must also visit the admin page of the HTML-editor and switch the editorhidebuttons off for the Nanogong button. (default hide is on after install)

==See also==
*[http://moodle.org/mod/data/view.php?d=13&rid=1209&filter=1 NanoGong 3] is a Modules and plugins database page that has downloads and more information.
*Discussions:
**Please create or find a discussion topic in the [http://moodle.org/mod/forum/view.php?id=44 Contributed Code forum]
**The contributor also maintains a Moodle site that contains one or more [http://gong.ust.hk/moodle forums using and supporting NanoGong], outside of Moodle.org .
*Additional documentation
**[http://gong.ust.hk/nanogong/moodle_inst.html Installing NanoGong in Moodle] (outside of Moodle.org).

[[Category:Contributed code]]

NanoGong

2009-01-19T23:11:12Z

Hrynkiw: /* Tips & Tricks */ fixed typo

{{stub}}

NanoGong provides a very simple and transparent voice support for Moodle. Using a NanoGong activity and filter, it provides two different types of voice support for Moodle.

NanoGong icon can be used to record, playback and save a voice file, in a web page. The playback can be changed by the listener. The Listener's version of can be saved to the listener's hard disk. A NanoGong activity allows the student to submit their recording to the teacher.

==Features==
*Record at one speed
*Create individual copy at a different speed
*Save copy on local hard drive
*Student can send back to teacher

==Tips & Tricks==

*''Note:'' When downloaded, the HTML area (HTML edit tool) for a specific version of Moodle, will change the core Moodle code.
*'''Warning 2:''' When you install Nanogong in 1.9.x, you must also visit the admin page of the HTML-editor and switch the editorhidebuttons off for the Nanogong button. (default hide is on after install)

==See also==
*[http://moodle.org/mod/data/view.php?d=13&rid=1209&filter=1 NanoGong 3] is a Modules and plugins database page that has downloads and more information.
*Discussions:
**Please create or find a discussion topic in the [http://moodle.org/mod/forum/view.php?id=44 Contributed Code forum]
**The contributor also maintains a Moodle site that contains one or more [http://gong.ust.hk/moodle forums using and supporting NanoGong], outside of Moodle.org .
*Additional documentation
**The contributor has additional documentation posted [http://gong.ust.hk/nanogong/moodle_inst.html for installing NanoGong on a Moodle site] outside of Moodle.org .

[[Category:Contributed code]]

Grades FAQ

2008-12-09T19:41:03Z

Hrynkiw: /* General */ Added "quiz grades disappear randomly" Q and A.

{{Grades}}
== General ==

===How can I change how grades are displayed?===

Grades may be displayed as as actual grades, as percentages (in reference to the minimum and maximum grades) or as letters.

The default grade display type for the site is set by an administrator in ''Administration > Grades > [[Grade item settings]]''. However, this may be changed at course level.

To change how grades are displayed for particular [[Grade items|grade items]], or category and course summaries (called aggregations):

# Follow the grades link in the course administration block.
# Select "Categories and items" from the gradebook dropdown menu.
# Click the edit icon for the grade item, category total or course total.
# From the Grade display type menu, select real (for actual grades), percentage or letter.
# Click the "Save changes" button at the bottom of the page.

Alternatively, to change how grades are displayed for the whole course:

# Follow the grades link in the course administration block.
# Select "Course settings" from the gradebook dropdown menu.
# From the Grade display type menu, select real (for actual grades), percentage or letter.
# Click the "Save changes" button.

===How can I hide entered grades until a specified date?===

To set a "Hidden until" date:

#Access the course gradebook via the grades link in the course administration block.
#Select "Categories and items" from the gradebook dropdown menu.
#Click on the edit icon opposite the activity for which a "Hidden until" date is to be set.
#On the edit grade item page, ensure that advanced settings are displayed. (Click the "Show advanced" button if not.)
#Enable the "Hidden until" setting by unchecking the disable checkbox, then set a date.
#Click the "Save changes" button.

=== Is it possible to show the teachers/administrators' grades in the grader report? ===
Yes, at the site level you can define which roles will appear in the grader report. This can be found in [[General_grade_settings#Graded_Roles|Administration > Grades > General settings]]. Also read [http://moodle.org/mod/forum/discuss.php?d=92612 this discussion] for some more ideas.

===Why can't I change a grade within an assignment after changing it in the gradebook?===

When you edit a grade directly in the gradebook, an "overridden" flag is set, meaning that the grade can no longer be changed from within the assignment.

However, the flag can be removed by turning editing on in the [[Grader report|grader report]], then clicking the [[Grade editing|edit grade]] icon, unchecking the overridden box and saving the changes.

===How do I get groups to show up in the grader report?===

For groups to show up in the grader report, group mode should be set to visible or separate groups in the [[Course settings|course settings]]. This will result in a groups dropdown menu being displayed, enabling a teacher to view the grades of all participants, or only the grades for a selected group.

===The quiz grades keep disappearing from the student view, even after I un-hide them!===

Check your quiz settings. Under the '''Review options''' heading, in the '''Later, while the quiz is still open''' and/or the '''After the quiz is closed''' columns, you probably have Scores un-checked. Each time a student completes a quiz, these settings are consulted and the scores will be hidden from ''all'' students. If your students don't all take the quiz at the same time, it can look like quiz scores reset themselves to 'hidden' randomly, even after you un-hide them.

== Reports ==
=== How do I create my own custom gradebook reports? ===
Here is a [[Development:Gradebook_Report_Tutorial|tutorial]] explaining all the main steps involved.

== Aggregation ==
=== I can't find where to change the aggregation type for my gradebook categories! ===
Each category has an aggregation type, which can be changed through that category's "edit" page. To access that page, you must use one of 2 ways:

1. In the grader report, turn "Editing" on, then click the little "hand" icon next to the category whose aggregation you want to change
2. In the "Edit categories and Items" page (accessible through the "choose an action" menu, top left), you see a tree view of the categories and items in your gradebook. The top category is the course category. Each category also has a "hand" icon, which leads to the category edit page

=== How can I grade some of my activities without the results affecting my students' course total? ===
#Create two [[Grade categories]], one for your "activities still being graded," and one for your "released" activities.
#Ensure that "Aggregate including subcategories" (an advanced option) is unchecked for your top level course grade category.
##Where is this? In gradebook (grader report), in the upper right corner, click the "Turn Editing On" button.
##Click the edit icon next to the "course category" (usually your course name, just above the quiz names and below all the clickable links that were revealed when you turned editing on)
##Then make sure you have the "Show Advanced" option turned on.
#Edit the "activities still being graded" category's "course total" item. (This is one of the categories you created above.)
##Where is this? Look for the edit icon under "category total" that is below this category's name
#Set the "grade type" to "none".
#Tick the "Hidden" checkbox.
#Save your changes.
#Move all your activities being graded in the "activities still being graded" category.
#Move all your activities already graded in the "released" category.

Note: I rewrote this a bit, to help people find where things are. However, this method didn't seem to work for me on Moodle 1.9.

=== My student completed only one activity out of 5, but his course total shows 100%. How do I show a more "progressive" course total? ===
By default, only non-empty grades are aggregated, the others are ignored. However, you can change this setting as well as others that affect the course total, by turning "Editing" on in the grader report, and clicking the "Edit" icon next to the course category (the very top row of the grader report).

You can untick the box "Aggregate only non-empty grades" if you want to show a more "progressive" score for each student. Their empty grades will count as a 0 and will be counted in the course mean/total.

If you prefer to show a sum of points, rather than a percentage, you can change the course category's aggregation method to "Sum of grades".

=== How can I display the average grade for my course categories (not grade categories)? ===
In Moodle 1.9 there is no way to aggregate course totals within each category. The gradebook is course-centered, and there is currently no User Interface for showing grades within an entire course category at once.

=== How can I setup weighted assignments? ===
See [[Using "Weighted Mean of Grades" to weight categories containing assignments]].

== Categories ==
=== How many depths of categories/subcategories can I create? ===
There is no programmatic limit, but there are practical limits. Very deeply nested structures are difficult to manage. 3 levels of categories should be sufficient for most situations. Note that there is always at least one level of categories, since the Course category always encompasses all other categories and grade items, can cannot be deleted.

=== I can't find setting X in the grade category edit page! Where is it? ===
If a setting documented on the [[Grade categories]] page does not appear on your edit page, it may mean that it is set globally in your site. See [[Grade_category_settings#Forcing_settings|Forcing settings]] for more information.

== Outcomes ==
=== I have just upgraded to Moodle 1.9, and I want to set up an outcome item for my course. What are the steps required? ===
# Administration > Grades > General settings > [[General_grade_settings#Enable_outcomes|Enable outcomes]]
#[[Scales#Creating_a_new_scale|Create a scale]]
#Create a course outcome (read the [[Outcomes| outcomes documentation]] for instructions). Assign to it the scale you just created.
#Assign the outcome to your course
#Enter the "Grades" section of your course, from the course administration block
#In the Actions menu (top left), select Edit -> Categories and Items
#Click "Add outcome item"
#Follow the instructions of the [[Outcome items|outcome items documentation]] to create the outcome item

You can now give your students a rating on the outcome dimension you just created. If you created a standard outcome, you will be able to use it in other courses and follow your students' performance across these courses.

===How can I remove an outcome from an activity?===

An outcome can be removed from an activity by deleting it on the gradebook edit categories and items page. This results in the outcomes being deselected on the update activity page.

== Modules ==
=== The activity module (Module name) doesn't support grading. How can I give my students a grade anyway? ===
You can create a [[Grade_items#Manual_grade_items|grade item]] manually in the gradebook. You will have to grade your students through the [[Grader report]] interface (in editing mode).

=== I just graded some of my students using the (Module name) interface, but the results aren't showing up in the grader report. What's going on? ===
Here are some of the possible reasons:

#The corresponding [[Grade items|grade item]] is [[Grade_locking#In_grade_items|locked]], or its parent [[Grade categories|category]] is [[Grade_locking#In_grade_categories|locked]].
#The module code is not using the [[Development:Grades#API_for_communication_with_modules.2Fblocks|gradebook API]] correctly

=== I just created a new assignment with the "Grade" setting set to "No grade", but it still appears in the gradebook ===
The reason is that the gradebook is now the place where both numerical and textual types of feedback are recorded for all activity modules. The word "Grading" in assignment relates only to numerical grades, but the ability to give text feedback remains, and must be recorded in the gradebook. This is why a grade item is created for it. You can hide the grade item if you do not want it to appear in the user reports.

==Weights and extra credits==

===How do I create an assignment for which students can receive a grade higher than the maximum?===
---Documentation yet to be written---

==See also==
*[[Gradebook 1.9 Tutorial]]
*Gradebook Scenarios/Use Cases [https://docs.moodle.org/en/experimental:_gb_tutoring]
*Using Moodle [http://moodle.org/mod/forum/view.php?id=2122 Gradebook forum]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=102609 Can I aggregate only non hidden items?]

[[Category:FAQ]]

[[ca:PMF de les qualificacions]]
[[fr:FAQ des notes]]

Administrator do's and don'ts

2008-11-17T19:11:15Z

Hrynkiw: reply to question

Don't use the files area in the main Moodle site course to restore course archives. You can destroy the front page very easily. You will be much better off to set up a special course just for that purpose!

: Why? How? --[[User:David Mudrak|David Mudrak]] 09:43, 10 September 2008 (CDT)
:: Accidentally restoring a faulty course archive to your main site course will break the whole site for everyone. Also -- by default, all users have access to the files in the main site course. If your course archive contains any confidential information, you're potentially exposing it to all site users. We have hidden test courses that we use to host the course archives we're going to restore. --[[User:Donna Hrynkiw|Donna Hrynkiw]] 13:11, 17 November 2008 (CST)

[[Category:Administrator]]

{{stub}}

Advanced uploading of files assignment

2008-10-20T22:13:52Z

Hrynkiw: added note to 'upload different working file for each student' allowing student to see the grades

{{Assignments}}{{Moodle 1.7}}This type of assignment allows each student to upload one or more files in any format.

==Features==
*This type also allows teachers to send files back to students in response to their submissions. A typical way to use this would be to edit the student's submitted file by adding comments and/or corrections, and then returning this file back to the student via the assignment. When a student clicks on the assignment, files sent to him or her appear as a list of Response files.
Response files can be also uploaded before submission which can be used to give each student a different file to work with. (Be sure that Gradebook settings for that assignment allow the grades/response files to be visible to the student.)
*Students may also enter notes describing the submitted files, progress status or any other text information.
*Submission of this type of assignment must be manually finalized by the student.
*Teachers can review the current status at any time, unfinished assignments are marked as Draft. Teachers can revert any ungraded assignment back to draft status.

==Settings==

These settings are in addition to the general assignment settings outlined on [[Adding/editing_an_assignment|editing an assignment]].

===Maximum size===
This setting specifies the maximum size (in total) of the file which the students can upload as their submission. If your students are uploading word processing documents or spreadsheets, typically you only need to allow for a few megabytes. If your students are submitting multimedia projects or other files with many images or audio clips, then the space allowed will need to be larger.

Remember there are other places which can place limits on the maximum file size. The course administration block, the site administration block and several server files which are outside the direct control of Moodle.

===Allow deleting===
If enabled, students may delete uploaded files at any time before submitting for grading.

===Maximum number of uploaded files===
Maximum number of files each participant may upload, this number is not shown to students, please write the actual number of requested files in assignment description.

===Allow notes===
If enabled, students may enter notes into text area associated with the assignment.

This text box can be used for communication with the grading person, assignment progress description or any other written activity.

===Hide description before available date===
If enabled, assignment description is hidden before the opening date.

===Email alerts to teachers===
If enabled, then teachers are alerted with a short email whenever students add or update an assignment submission.

Only teachers who are able to grade the particular submission are notified. So, for example, if the course uses separate groups, then teachers restricted to particular groups won't receive any notices about students in other groups.

[[Category:Teacher]]
[[Category:Assignment]]

[[cs:Úkol s pokročilým nahráváním souborů]]
[[fr:Dépôt avancé de fichiers]]

Assignment submissions

2008-10-20T17:40:36Z

Hrynkiw: fixed small typo

{{Assignments}}
To view the submitted assignment, the teacher should click on the assignment activity they wish to review. Then click on "View 'x' submitted assignments" link in the upper right corner.

==Overview of submissions page ==
The submissions page contains a table with headings:

# '''First name and Surname''' (along with the photograph)
# '''Grade''' (for the submitted assignment)
# '''Comment''' (the feedback information you have written in the feedback field while grading the assignment)
# '''Last modified (Student)''' (the date of the last modification of the assignment by the student)
# '''Last modified (Teacher)''' (the date of the last modification of the assignment by the teacher)
# '''Status''' (with which you can move to the page where you grade the submitted assignment or, in case it's been graded, update the grade and/or the comment)
# '''Final grade'''

Above the table there is an alphabetical index, which helps you narrow down the number of students shown on one page only to those whose surname (or name) starts with the same letter. That is particularly helpful in case of a large number of course participants.

The list of submissions may be sorted by clicking on a particular heading. Clicking twice on the same heading sorts the list in the opposite order. If the table is too large then columns may be collapsed by clicking on the Hide icon next to a particular column heading.

By default, 10 submissions are shown per page, though this may be changed at the bottom of the page.

==Grade submission==
===Basic grading assignments===
To grade or mark a submission, click on the Grade link opposite a particular student's name. A new window will open containing a feedback area.

Once you've reviewed the student's assignment, pick the grade for the assignment from the dropdown list. (You set the scale when you created the assignment.) Below the grade scale, you can type comments regarding their work. When you're done, click "Save changes" or "Save and show next".

===Quick grading assignments===
You may prefer to use "quick grading" by checking the box at the bottom of the submissions page. This enables you to quickly grade multiple assignments all on one page, rather than one by one in a new window. Simply add the grades and comments then when you're done, click "Save all my feedback" at the bottom of the page.

==Tutorial on feedback and grading==

#Click directly on the assignment whose submissions you wish to mark.
#Click on View submitted assignments (top right)
#Before going any further, I would like to draw your attention to some settings on this page. Scroll to the bottom and you will see: Submissions per page and Allow quick grading
##I find it useful to set the submissions per page quite large so as not to have to keep opening new pages to see more students.
##Normally you have to click on Grade on the right to open a new page where you can view the submission and enter marks and type some feedback text. If you Allow quick grading you can do this on the same line as the submission is listed.
##Save preferences if you change either of these. For the rest of this, I will assume that you have enabled Allow quick grading.
#On the line across for each person, if they have submited, you will see a link to a file. If you click on the file it will either open in a new browser window (if your browser is capable of viewing the document), or it will ask you if you wish to save to disc or open using the appropriate application program.
#Once you have viewed their submission, you can then indicate a mark from the drop down list, and/or enter your comments in the box.
#You can do this for many students, however the marks are not stored until you select Save all my feedback either at the top or the bottom of the list of student. It is advisable not to leave too long a time before doing this. After you do this, all students who you left feedback for are sent an email to let them know that there is feedback available for them.
#You might note that if you have a long list of students you can sort in many ways, firstname, lastname etc by clicking on the blue link at the top of each column. A useful way is to sort by "Last modified Student" (get the arrow pointing upwards - ie. latest first) which will show the most recently submitted. If you allow more than one submission it is also useful to compare "Last modified student" date with "Last modified Lecturer" date as you can spot who has resubmitted since you last commented.

[[Category:Assignment]]

==See also==
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=83537 Deleting Submitted Assignments] forum discussion
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=86224 Indication of submitted work...] forum discussion

[[cs:Odevzdané úkoly]]

Wiki settings

2008-09-10T22:34:34Z

Hrynkiw: tweak html mode entry

{{Wiki}}

==Adding a wiki==
[[Image:Wiki settting screen.JPG|thumb|Adding a new wiki in Moodle 1.7]]
To create a wiki:
#Click the "Turn editing on" button.
#Select Wiki from the "Add an activity" dropdown menu in the course section where you would like to add the wiki.
#On the Adding a new wiki page, give the wiki a descriptive name.
#In the summary field, describe the purpose of the wiki and what you expect students to contribute.
#Select the wiki type - groups, student or teacher. The wiki type interacts with the groups setting for your course, resulting in 9 options, as shown in the type help pop-up.
#Click the "Show Advanced" button (in Moodle 1.8 onwards) to display additional options (see below).
#Select the common module settings (see below).
#Click the "Save changes" button.

== Adding and editing wiki pages ==

After you've created a wiki, it's available for editing. [[Viewing a wiki]] contains information on adding and editing wiki pages.

==Advanced options==

===Print wiki name of every page===
If you select this option, the top of each page will have the name of the wiki.

===HTML mode===
There are three options: No HTML, safe HTML or HTML only. 'No HTML' will display all HTML tags as tags. 'Safe HTML' will allow certain tags to be displayed. 'HTML only' enables the WYSIWYG editor.

===Allow binary files===
Binary files are graphics, audio, video, and other non-text resources. If you want students to be able to add files as attachments, set this to Yes.

===Wiki auto-linking options===
A new page can be created in the wiki by typing a word using CamelCase i.e. with a capital letter at the beginning and a capital letter somewhere else in the word. It's called CamelCase because the two capital letters resemble a two-humped camel. CamelCase combines all the words for the link into one word. Each word in the link is capitalized. When a word is added in CamelCase, the wiki automatically creates a new page and makes the word a link. You can disable this feature if you wish, so that typing a word enclosed in square brackets is the only way of creating a new page.

CamelCase is not always desirable, as some text is writen in it. For example a file name might be MyFile_2007_Feb.jpg.

===Student admin options===
When students can edit a page, you can allow them certain administrative privileges in the wiki (see [[Wiki administration]]).

===Page name===
You may wish to seed the wiki with a page name for the first page.

===Choose an initial page===
This can be the first wiki page that is created, or a way to switch to a different front page. Other files in the same directory as the first wiki page you select will also become part of the initial wiki - see:
http://moodle.org/mod/forum/discuss.php?d=8501

==Common module settings==

===Group mode===
Another location to set the group mode for the activity. If group mode is forced in the course settings then this setting will be ignored.

===Visible===
This determines whether students may view the activity or not.

==See also==

*[[Wiki permissions]]

[[Category:Wiki]]

[[fr:Ajouter/modifier un wiki]]

Getting started for teachers

2008-06-13T16:30:31Z

Hrynkiw: Polished text in Basics, icon table still needs work

==Introduction==
A list of all teacher documentation articles can be found under [[:Category:Teacher]].

We are assuming that your site administrator has set up Moodle, and assigned you to a new, blank course where you have teacher privileges. You may also experiement for an hour at a time for free at [http://demo.moodle.org/ demo.moodle.org]. Your course may look a little different from the illustrations in this article.

You must be [[Log in |logged in]] in order to edit a course and use most of the features described below. We have some tips if you are having [[Can not log in | trouble logging in]].

==Basics==
A [[Course homepage|course homepage]] is broken into [[Course sections|course sections]] (often by week or topic). [[Adding resources and activities|Resources and activities]] are added to each section. When writing text in Moodle you have a range of [[Formatting options]], including using [[HTML editor|HTML in Moodle]]. There are different ways to enroll [[Students]] and assign them to one or more [[Groups]] in a course.

The illustration below shows a new course set up with topic sections in the middle column. In the right and left columns are a few of Moodle's many [[:Category:Block|blocks]] such as "Latest News" or "[[Administration block|Administration]]". [[#Editing course section|Editing has been turned on]]. The teacher is ready to add resources and activities.
[[Image:Course edit on new 2.jpg|thumb|center|500px|Getting started image - a new course]]

==Editing course section==
[[Image:Turn_edit_on_Student_on_buttons.JPG]] 
To add or alter activities or resources a teacher must [[Turn editing on|turn editing on]] using the "Turn editing on" button on the course homepage. The same button will also turn editing off.

When editing has been turned on, a variety of editing icons appear next to all editable objects in the course. The table below illustrates some of the icons you are likely to see. For more details about each editing activity, visit [[Adding/editing_a_course#Editing_a_course|editing a course]].

{| border="1" cellpadding="2" cellspacing="0"
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="140"|Effect
|-
|[[Image:Edit.gif]]|| Edit item ||[[Image:Open.gif]]* || Close/Hide item||[[Image:Delete.gif]]** || Delete/Remove ||[[Image:Move.gif]] ||Move (up/down)
|-
||[[Image:All.gif]] ||See all weeks/topics||[[Image:Closed.gif]]* || Open/Show Item ||[[Image:Right.gif]] || Indent/shift right ||[[Image:Movehere.gif]] || Move here
|-
||[[Image:One.gif]] || See one week/topic||[[Image:Help.gif]] ||Help || || ||[[Image:Marker.gif]] ||Make Current (highlight) week/topic
|}
 
'''<nowiki>*</nowiki>''' (Note that the open eye indicates that the resource is visible, while clicking it changes it to be invisible (to students), and vice versa with the closed eye. '''<nowiki>**</nowiki>''' Note that the X deletes resources and activities (with a warning) whereas it only removes blocks (which can be added at any time later)

To ADD items you must use the appropriate drop-downs for them.

Similarly, the "Turn student view on" button allows the teacher to see the course page as a student would see it.

==Activity modules==
[[Image:Activity dropdown 1 8.JPG|frame|right|Add an activity drop-down menu - Moodle 1.8.2 ]] There are a number of robust interactive learning [[:Category:Modules|activity modules]] that you may [[Adding_resources_and_activities | add to your course]] with the "Add an activity" drop down menu.

Communication and collaboration may take place using live [[Chats]] or asynchronous discussion [[Forums]] for conversational activities. You can also use [[Choices]] to gain group feedback. Adding [[Wikis]] to your courses is an excellent way to allow students to work together on a collaboratively-authored project.

Work can be uploaded and submitted by students and scored by teachers using [[Assignments]] or [[Workshops]]. Workshops such as these have several assessment options, including instructor-assessment, self-assessment, and even peer-assessment. Online [[Quizzes]] offer several options for automatic and manual scoring. You can even integrate your Hot Potato quizzes by adding a [[Hotpot]] activity.

[[Lessons]] and [[SCORM]] activities deliver content and offer ways of individualizing your presentation based upon a student's choices. [[Glossaries]] of keywords can be set up by the instructor, and can be configured to allow students to edit, add, or rate entries.

[[Surveys]] and [[Database module|Databases]] are also very powerful additions to any course.

If all of that isn't enough for you then you can also add contributed modules that are not part of the official Moodle release!

==Resources==

[[Image:Resource pulldown menu .JPG 1 8.JPG|frame|left|Add a resource drop-down menu]]

Moodle supports a range of different [[Resources|resource types]] that allow you to include almost any kind of digital content into your courses. These can be added by using the [[Adding_resources_and_activities | add a resource]] dropdown box when editing is turned on.

A [[Text page]] is a simple page written using plain text. Text pages aren't pretty, but they're a good place to put some information or instructions. If you are after more options for your new page then you should be thinking about adding a [[Web page]] and making use of Moodle's WYSIWYG editor.

Of course the resource may already exist in electronic form so you may want to [[File or website link|link to an uploaded file or external website]] or simply display the complete contents of a [[Directory|directory]] in your course files and let your users pick the file themselves. If you have an [[IMS content package]] then this can be easily added to your course.

All resources may be organized, structured, and [[Label|labeled]] for usability.

==Blocks==
[[Image:Block add dropdown list teacher 1 8.JPG |thumb|150px|right|Add Block drop-down menu]]
Each course homepage generally contains [[Blocks_%28teacher%29|blocks]] on the left and right with the centre column containing the course content. Blocks may be added, hidden, deleted, and moved up, down and left/right when editing is turned on. Examples of blocks can be seen in the Getting Started image above. [[Latest News block|"Latest News"]], "[[Blogs]]", [[Upcoming Events block|"Upcoming Events"]], and [[Recent Activity block|"Recent Activity"]] are a few examples.

A wide range of [[Blocks_%28teacher%29#Block_types|over 16 different block types]] can provide additional information or functionality to the learner by the teacher. The standard blocks that come with Moodle are shown on the right. There are also many contributed developed by Moodlers that an administrator can add to this list.

A teacher with editing rights will also have a course [[Administration_block|administration block]]. This block has sub menus for course: backup/restore, enrollments, format, reports, grades, activity logs, files and other useful tools.

==General advice==

* Subscribe yourself to all of the [[forum]]s in your course so that you can keep in touch with your class activity.
* Encourage all of the students to fill out their [[Edit profile|user profile]] (including photos) and read them all - this will help provide some context to their later writings and help you to respond in ways that are tailored to their own needs.
* Keep notes to yourself in the private "Teacher's Forum" (under Administration). This is especially useful when team teaching.
* Use the [[Logs]] link (under Administration) to get access to complete, raw logs. In there you'll see a link to a popup window that updates every sixty seconds and shows the last hour of activity. This is useful to keep open on your desktop all day so you can feel in touch with what's going on in the course.
* Use many reports. [[Reports]] in the Administration block, [[Recent_activity|Activity Reports]] (next to each name in the list of all people, or from any user profile page). These provide a great way to see what any particular person has been up to in the course.
* Respond quickly to students. Don't leave it for later - do it right away. Not only is it easy to become overwhelmed with the volume that can be generated, but it's a crucial part of building and maintaining a community feel in your course.
*Don't be afraid to experiment: feel free to poke around and change things. It's hard to break anything in a Moodle course, and even if you do it's usually easy to fix it.
* Use the [[Navigation bar|navigation bar]] at the top of each page - this should help remind you where you are and prevent getting lost

==Example installations & courses==
It might be useful to have a look at some sites where Moodle is being used to deliver courses - obviously this is only useful where access is open to anyone.

[http://www.igcse-computing.com/lms_new/ IGCSE Computing] - Moodle site with Secondary (Middle School) ICT and staff training resources under creative commons license.

[http://aiken.moodlerooms.com/wb/pages/academics/moodle/moodle-at-aiken-high-school--introduction.php] - Moodle at Aiken High School

[http://www.theingots.org/moodle/ INGOTs] - Moodle site to support INGOTs which are open source inspired courses which are fully accredited (by QCA in UK).

== See also ==
*[[Teacher documentation]]

[[Category:Teacher]]
[[cs:Rukověť učitele]]
[[es:Documentación para Profesores]]
[[eu:Irakasleentzako dokumentazioa]]
[[fi:Opettajan opas]]
[[fr:Documentation enseignant]]
[[it:Documentazione per Docenti]]
[[ja:教師ドキュメント]]
[[nl:Documentatie voor leraren]]
[[ru:Учителям]]
[[zh:教师文档]]

Getting started for teachers

2008-06-13T16:09:36Z

Hrynkiw: Re-wrote Introduction and Basics

==Introduction==
A list of all teacher documentation articles can be found under [[:Category:Teacher]].

We are assuming that your site administrator has set up Moodle, and assigned you to a new, blank course where you have teacher privileges. You may also experiement for an hour at a time for free at [http://demo.moodle.org/ demo.moodle.org].

You must be [[Log in |logged in]] in order to edit a course and use most of the features described below. We have some tips if you are having [[Can not log in | trouble logging in]].

==Basics==
A [[Course homepage|course homepage]] is broken into [[Course sections|course sections]] (often by week or topic). [[Adding resources and activities|Resources and activities]] are added to each section. When writing text in Moodle you have a range of [[Formatting options]], including using [[HTML editor|HTML in Moodle]]. There are different ways to enroll [[Students]] and assign them to one or more [[Groups]] in a course.

The illustration below shows a new course set up with topic sections in the middle column. In the right and left columns are a few of Moodle's many [[:Category:Block|blocks]] such as "Latest News" or "[[Administration block|Administration]]". Editing has been turned on. The teacher is ready to add resources and activities or a few new blocks to their brand new course.
[[Image:Course edit on new 2.jpg|thumb|left|500px|Getting started image - a new course]]

==Editing course section==
[[Image:Turn_edit_on_Student_on_buttons.JPG]] 
To add or alter activities or resources a teacher will need to [[Turn editing on|turn editing on]] and off with a button on the course homepage. The student view/change roles option allows the teacher to get a general idea of what students will see. There is also an "editing on" link in the [[Administration block|administration block]]. The turn editing option toggles between on and off, and when on, shows a variety of editing icons next to all editable objects in the course. Here are some common editing icons, for more details about them [[Adding/editing_a_course#Editing_a_course|go to adding/editing a course]]. To ADD items you must use the appropriate drop-downs for them.

{| border="1" cellpadding="2" cellspacing="0"
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="140"|Effect
|-
|[[Image:Edit.gif]]|| Edit item ||[[Image:Open.gif]]* || Close/Hide item||[[Image:Delete.gif]]** || Delete/Remove ||[[Image:Move.gif]] ||Move (up/down)
|-
||[[Image:All.gif]] ||See all weeks/topics||[[Image:Closed.gif]]* || Open/Show Item ||[[Image:Right.gif]] || Indent/shift right ||[[Image:Movehere.gif]] || Move here
|-
||[[Image:One.gif]] || See one week/topic||[[Image:Help.gif]] ||Help || || ||[[Image:Marker.gif]] ||Make Current (highlight) week/topic
|}
 
'''<nowiki>*</nowiki>''' (Note that the open eye indicates that the resource is visible, while clicking it changes it to be invisible (to students), and vice versa with the closed eye. '''<nowiki>**</nowiki>''' Note that the X deletes resources and activities (with a warning) whereas it only removes blocks (which can be added at any time later)

==Activity modules==
[[Image:Activity dropdown 1 8.JPG|frame|right|Add an activity drop-down menu - Moodle 1.8.2 ]] There are a number of robust interactive learning [[:Category:Modules|activity modules]] that you may [[Adding_resources_and_activities | add to your course]] with the "Add an activity" drop down menu.

Communication and collaboration may take place using live [[Chats]] or asynchronous discussion [[Forums]] for conversational activities. You can also use [[Choices]] to gain group feedback. Adding [[Wikis]] to your courses is an excellent way to allow students to work together on a collaboratively-authored project.

Work can be uploaded and submitted by students and scored by teachers using [[Assignments]] or [[Workshops]]. Workshops such as these have several assessment options, including instructor-assessment, self-assessment, and even peer-assessment. Online [[Quizzes]] offer several options for automatic and manual scoring. You can even integrate your Hot Potato quizzes by adding a [[Hotpot]] activity.

[[Lessons]] and [[SCORM]] activities deliver content and offer ways of individualizing your presentation based upon a student's choices. [[Glossaries]] of keywords can be set up by the instructor, and can be configured to allow students to edit, add, or rate entries.

[[Surveys]] and [[Database module|Databases]] are also very powerful additions to any course.

If all of that isn't enough for you then you can also add contributed modules that are not part of the official Moodle release!

==Resources==

[[Image:Resource pulldown menu .JPG 1 8.JPG|frame|left|Add a resource drop-down menu]]

Moodle supports a range of different [[Resources|resource types]] that allow you to include almost any kind of digital content into your courses. These can be added by using the [[Adding_resources_and_activities | add a resource]] dropdown box when editing is turned on.

A [[Text page]] is a simple page written using plain text. Text pages aren't pretty, but they're a good place to put some information or instructions. If you are after more options for your new page then you should be thinking about adding a [[Web page]] and making use of Moodle's WYSIWYG editor.

Of course the resource may already exist in electronic form so you may want to [[File or website link|link to an uploaded file or external website]] or simply display the complete contents of a [[Directory|directory]] in your course files and let your users pick the file themselves. If you have an [[IMS content package]] then this can be easily added to your course.

All resources may be organized, structured, and [[Label|labeled]] for usability.

==Blocks==
[[Image:Block add dropdown list teacher 1 8.JPG |thumb|150px|right|Add Block drop-down menu]]
Each course homepage generally contains [[Blocks_%28teacher%29|blocks]] on the left and right with the centre column containing the course content. Blocks may be added, hidden, deleted, and moved up, down and left/right when editing is turned on. Examples of blocks can be seen in the Getting Started image above. [[Latest News block|"Latest News"]], "[[Blogs]]", [[Upcoming Events block|"Upcoming Events"]], and [[Recent Activity block|"Recent Activity"]] are a few examples.

A wide range of [[Blocks_%28teacher%29#Block_types|over 16 different block types]] can provide additional information or functionality to the learner by the teacher. The standard blocks that come with Moodle are shown on the right. There are also many contributed developed by Moodlers that an administrator can add to this list.

A teacher with editing rights will also have a course [[Administration_block|administration block]]. This block has sub menus for course: backup/restore, enrollments, format, reports, grades, activity logs, files and other useful tools.

==General advice==

* Subscribe yourself to all of the [[forum]]s in your course so that you can keep in touch with your class activity.
* Encourage all of the students to fill out their [[Edit profile|user profile]] (including photos) and read them all - this will help provide some context to their later writings and help you to respond in ways that are tailored to their own needs.
* Keep notes to yourself in the private "Teacher's Forum" (under Administration). This is especially useful when team teaching.
* Use the [[Logs]] link (under Administration) to get access to complete, raw logs. In there you'll see a link to a popup window that updates every sixty seconds and shows the last hour of activity. This is useful to keep open on your desktop all day so you can feel in touch with what's going on in the course.
* Use many reports. [[Reports]] in the Administration block, [[Recent_activity|Activity Reports]] (next to each name in the list of all people, or from any user profile page). These provide a great way to see what any particular person has been up to in the course.
* Respond quickly to students. Don't leave it for later - do it right away. Not only is it easy to become overwhelmed with the volume that can be generated, but it's a crucial part of building and maintaining a community feel in your course.
*Don't be afraid to experiment: feel free to poke around and change things. It's hard to break anything in a Moodle course, and even if you do it's usually easy to fix it.
* Use the [[Navigation bar|navigation bar]] at the top of each page - this should help remind you where you are and prevent getting lost

==Example installations & courses==
It might be useful to have a look at some sites where Moodle is being used to deliver courses - obviously this is only useful where access is open to anyone.

[http://www.igcse-computing.com/lms_new/ IGCSE Computing] - Moodle site with Secondary (Middle School) ICT and staff training resources under creative commons license.

[http://aiken.moodlerooms.com/wb/pages/academics/moodle/moodle-at-aiken-high-school--introduction.php] - Moodle at Aiken High School

[http://www.theingots.org/moodle/ INGOTs] - Moodle site to support INGOTs which are open source inspired courses which are fully accredited (by QCA in UK).

== See also ==
*[[Teacher documentation]]

[[Category:Teacher]]
[[cs:Rukověť učitele]]
[[es:Documentación para Profesores]]
[[eu:Irakasleentzako dokumentazioa]]
[[fi:Opettajan opas]]
[[fr:Documentation enseignant]]
[[it:Documentazione per Docenti]]
[[ja:教師ドキュメント]]
[[nl:Documentatie voor leraren]]
[[ru:Учителям]]
[[zh:教师文档]]

Moodle in education

2008-06-13T15:54:37Z

Hrynkiw: LIghtly organized, needs more work

* '''[[Getting started]]''' - New at this Moodle thing?

==Reference==
*[[:Category:Teacher]]
*[[Moodle manuals]] - a list of links to manuals and books
*[[Using Moodle book]] - a real book you can reprint!

==Guidelines==
*[[Blogs]] - blogs in Moodle
*[[Teaching with Moodle]] - inspiring links
*[http://moodle.org/mod/forum/discuss.php?d=66854 Moodle and elearning intro] - Written by Martin Langhoff
*[[Teaching do's and don'ts|Teaching Do's and Don'ts]] - hints
*[[Teaching FAQ]] - common questions
*[http://moodle.tokem.fi/mod/book/view.php?id=16397&chapterid=8258 Example of a course teaching checklist]
*[http://moodle.tokem.fi/mod/book/view.php?id=16397 Teacher's Moodle Manual] - site specific, done in Moodle with the book module
*[[Tips and tricks]]
*[[Student documentation examples]]
*[[Student FAQ]] - students have questions about technology?
*[[Trainer]] - links that might be useful to Trainers

[[Category:Teacher]]
[[cs:Rukověť učitele]]
[[es:Documentación para Profesores]]
[[eu:Irakasleentzako dokumentazioa]]
[[fi:Opettajan opas]]
[[fr:Documentation enseignant]]
[[it:Documentazione per Docenti]]
[[ja:教師ドキュメント]]
[[nl:Documentatie voor leraren]]
[[ru:Учителям]]
[[zh:教师文档]]

Getting started for teachers

2008-06-13T15:51:34Z

Hrynkiw: Returned "example installations" to this page

If you are a new user and would like a list of all teacher documentation articles, please see [[:Category:Teacher]].

We are assuming that your site administrator has set up Moodle, you are a user with teacher privileges and the administrator has assigned you to a new, blank course. Don't forget, [http://demo.moodle.org/ demo.moodle.org] will let you play an hour at a time for free.

You will need to be [[Log in | logged into]] the course as a user who has been assigned [[Teacher|a role as a teacher]] (with editing rights) on that course to use most of the features below. We have some tips if you are having [[Can not log in | trouble logging in]].

Now onto the real details. You will find the [[Course homepage|course homepage]] is broken down into [[Course sections|course sections]]. A course is created by [[Adding resources and activities|adding resources and activities]]. When writing text in Moodle you have a range of [[Formatting options]], including using [[HTML editor|HTML in Moodle]]. There are different ways to enroll [[Students]] and assign them to one or more [[Groups]] in a course.

The example below shows a new course set up with topic sections, edit is on. There are a few of Moodle's many [[:Category:Block|blocks]] on the right and left sides of the topics, such as "Latest News" or "[[Administration block|Administration]]". The teacher is ready to add resources and activities or a few new blocks to their brand new course.
[[Image:Course edit on new 2.jpg|thumb|center|500px|Getting started image - a new course]]

==Editing course section==
[[Image:Turn_edit_on_Student_on_buttons.JPG]] 
To add or alter activities or resources a teacher will need to [[Turn editing on|turn editing on]] and off with a button on the course homepage. The student view/change roles option allows the teacher to get a general idea of what students will see. There is also an "editing on" link in the [[Administration block|administration block]]. The turn editing option toggles between on and off, and when on, shows a variety of editing icons next to all editable objects in the course. Here are some common editing icons, for more details about them [[Adding/editing_a_course#Editing_a_course|go to adding/editing a course]]. To ADD items you must use the appropriate drop-downs for them.

{| border="1" cellpadding="2" cellspacing="0"
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="140"|Effect
|-
|[[Image:Edit.gif]]|| Edit item ||[[Image:Open.gif]]* || Close/Hide item||[[Image:Delete.gif]]** || Delete/Remove ||[[Image:Move.gif]] ||Move (up/down)
|-
||[[Image:All.gif]] ||See all weeks/topics||[[Image:Closed.gif]]* || Open/Show Item ||[[Image:Right.gif]] || Indent/shift right ||[[Image:Movehere.gif]] || Move here
|-
||[[Image:One.gif]] || See one week/topic||[[Image:Help.gif]] ||Help || || ||[[Image:Marker.gif]] ||Make Current (highlight) week/topic
|}
 
'''<nowiki>*</nowiki>''' (Note that the open eye indicates that the resource is visible, while clicking it changes it to be invisible (to students), and vice versa with the closed eye. '''<nowiki>**</nowiki>''' Note that the X deletes resources and activities (with a warning) whereas it only removes blocks (which can be added at any time later)

==Activity modules==
[[Image:Activity dropdown 1 8.JPG|frame|right|Add an activity drop-down menu - Moodle 1.8.2 ]] There are a number of robust interactive learning [[:Category:Modules|activity modules]] that you may [[Adding_resources_and_activities | add to your course]] with the "Add an activity" drop down menu.

Communication and collaboration may take place using live [[Chats]] or asynchronous discussion [[Forums]] for conversational activities. You can also use [[Choices]] to gain group feedback. Adding [[Wikis]] to your courses is an excellent way to allow students to work together on a collaboratively-authored project.

Work can be uploaded and submitted by students and scored by teachers using [[Assignments]] or [[Workshops]]. Workshops such as these have several assessment options, including instructor-assessment, self-assessment, and even peer-assessment. Online [[Quizzes]] offer several options for automatic and manual scoring. You can even integrate your Hot Potato quizzes by adding a [[Hotpot]] activity.

[[Lessons]] and [[SCORM]] activities deliver content and offer ways of individualizing your presentation based upon a student's choices. [[Glossaries]] of keywords can be set up by the instructor, and can be configured to allow students to edit, add, or rate entries.

[[Surveys]] and [[Database module|Databases]] are also very powerful additions to any course.

If all of that isn't enough for you then you can also add contributed modules that are not part of the official Moodle release!

==Resources==

[[Image:Resource pulldown menu .JPG 1 8.JPG|frame|left|Add a resource drop-down menu]]

Moodle supports a range of different [[Resources|resource types]] that allow you to include almost any kind of digital content into your courses. These can be added by using the [[Adding_resources_and_activities | add a resource]] dropdown box when editing is turned on.

A [[Text page]] is a simple page written using plain text. Text pages aren't pretty, but they're a good place to put some information or instructions. If you are after more options for your new page then you should be thinking about adding a [[Web page]] and making use of Moodle's WYSIWYG editor.

Of course the resource may already exist in electronic form so you may want to [[File or website link|link to an uploaded file or external website]] or simply display the complete contents of a [[Directory|directory]] in your course files and let your users pick the file themselves. If you have an [[IMS content package]] then this can be easily added to your course.

All resources may be organized, structured, and [[Label|labeled]] for usability.

==Blocks==
[[Image:Block add dropdown list teacher 1 8.JPG |thumb|150px|right|Add Block drop-down menu]]
Each course homepage generally contains [[Blocks_%28teacher%29|blocks]] on the left and right with the centre column containing the course content. Blocks may be added, hidden, deleted, and moved up, down and left/right when editing is turned on. Examples of blocks can be seen in the Getting Started image above. [[Latest News block|"Latest News"]], "[[Blogs]]", [[Upcoming Events block|"Upcoming Events"]], and [[Recent Activity block|"Recent Activity"]] are a few examples.

A wide range of [[Blocks_%28teacher%29#Block_types|over 16 different block types]] can provide additional information or functionality to the learner by the teacher. The standard blocks that come with Moodle are shown on the right. There are also many contributed developed by Moodlers that an administrator can add to this list.

A teacher with editing rights will also have a course [[Administration_block|administration block]]. This block has sub menus for course: backup/restore, enrollments, format, reports, grades, activity logs, files and other useful tools.

==General advice==

* Subscribe yourself to all of the [[forum]]s in your course so that you can keep in touch with your class activity.
* Encourage all of the students to fill out their [[Edit profile|user profile]] (including photos) and read them all - this will help provide some context to their later writings and help you to respond in ways that are tailored to their own needs.
* Keep notes to yourself in the private "Teacher's Forum" (under Administration). This is especially useful when team teaching.
* Use the [[Logs]] link (under Administration) to get access to complete, raw logs. In there you'll see a link to a popup window that updates every sixty seconds and shows the last hour of activity. This is useful to keep open on your desktop all day so you can feel in touch with what's going on in the course.
* Use many reports. [[Reports]] in the Administration block, [[Recent_activity|Activity Reports]] (next to each name in the list of all people, or from any user profile page). These provide a great way to see what any particular person has been up to in the course.
* Respond quickly to students. Don't leave it for later - do it right away. Not only is it easy to become overwhelmed with the volume that can be generated, but it's a crucial part of building and maintaining a community feel in your course.
*Don't be afraid to experiment: feel free to poke around and change things. It's hard to break anything in a Moodle course, and even if you do it's usually easy to fix it.
* Use the [[Navigation bar|navigation bar]] at the top of each page - this should help remind you where you are and prevent getting lost

==Example installations & courses==
It might be useful to have a look at some sites where Moodle is being used to deliver courses - obviously this is only useful where access is open to anyone.

[http://www.igcse-computing.com/lms_new/ IGCSE Computing] - Moodle site with Secondary (Middle School) ICT and staff training resources under creative commons license.

[http://aiken.moodlerooms.com/wb/pages/academics/moodle/moodle-at-aiken-high-school--introduction.php] - Moodle at Aiken High School

[http://www.theingots.org/moodle/ INGOTs] - Moodle site to support INGOTs which are open source inspired courses which are fully accredited (by QCA in UK).

== See also ==
*[[Teacher documentation]]

[[Category:Teacher]]
[[cs:Rukověť učitele]]
[[es:Documentación para Profesores]]
[[eu:Irakasleentzako dokumentazioa]]
[[fi:Opettajan opas]]
[[fr:Documentation enseignant]]
[[it:Documentazione per Docenti]]
[[ja:教師ドキュメント]]
[[nl:Documentatie voor leraren]]
[[ru:Учителям]]
[[zh:教师文档]]

Moodle in education

2008-06-13T15:50:56Z

Hrynkiw: Moved "Getting started" text to its own page

* '''[[Getting started]]''' - New at this Moodle thing?

*[[Blogs]] - blogs in Moodle
*[[Teaching with Moodle]] - inspiring links
*[http://moodle.org/mod/forum/discuss.php?d=66854 Moodle and elearning intro] - Written by Martin Langhoff
*[[Teaching do's and don'ts|Teaching Do's and Don'ts]] - hints
*[[Moodle manuals]] - a list of links to manuals and books
*[[Using Moodle book]] - a real book you can reprint!
*[[Teaching FAQ]] - common questions
*[http://moodle.tokem.fi/mod/book/view.php?id=16397&chapterid=8258 Example of a course teaching checklist]
*[http://moodle.tokem.fi/mod/book/view.php?id=16397 Teacher's Moodle Manual] - site specific, done in Moodle with the book module
*[[Tips and tricks]]
*[[Student documentation examples]]
*[[Student FAQ]] - students have questions about technology?
*[[Trainer]] - links that might be useful to Trainers

[[Category:Teacher]]
[[cs:Rukověť učitele]]
[[es:Documentación para Profesores]]
[[eu:Irakasleentzako dokumentazioa]]
[[fi:Opettajan opas]]
[[fr:Documentation enseignant]]
[[it:Documentazione per Docenti]]
[[ja:教師ドキュメント]]
[[nl:Documentatie voor leraren]]
[[ru:Учителям]]
[[zh:教师文档]]

Getting started for teachers

2008-06-13T15:42:30Z

Hrynkiw: Created "Getting Started" page for teachers

If you are a new user and would like a list of all teacher documentation articles, please see [[:Category:Teacher]].

We are assuming that your site administrator has set up Moodle, you are a user with teacher privileges and the administrator has assigned you to a new, blank course. Don't forget, [http://demo.moodle.org/ demo.moodle.org] will let you play an hour at a time for free.

You will need to be [[Log in | logged into]] the course as a user who has been assigned [[Teacher|a role as a teacher]] (with editing rights) on that course to use most of the features below. We have some tips if you are having [[Can not log in | trouble logging in]].

Now onto the real details. You will find the [[Course homepage|course homepage]] is broken down into [[Course sections|course sections]]. A course is created by [[Adding resources and activities|adding resources and activities]]. When writing text in Moodle you have a range of [[Formatting options]], including using [[HTML editor|HTML in Moodle]]. There are different ways to enroll [[Students]] and assign them to one or more [[Groups]] in a course.

The example below shows a new course set up with topic sections, edit is on. There are a few of Moodle's many [[:Category:Block|blocks]] on the right and left sides of the topics, such as "Latest News" or "[[Administration block|Administration]]". The teacher is ready to add resources and activities or a few new blocks to their brand new course.
[[Image:Course edit on new 2.jpg|thumb|center|500px|Getting started image - a new course]]

==Editing course section==
[[Image:Turn_edit_on_Student_on_buttons.JPG]] 
To add or alter activities or resources a teacher will need to [[Turn editing on|turn editing on]] and off with a button on the course homepage. The student view/change roles option allows the teacher to get a general idea of what students will see. There is also an "editing on" link in the [[Administration block|administration block]]. The turn editing option toggles between on and off, and when on, shows a variety of editing icons next to all editable objects in the course. Here are some common editing icons, for more details about them [[Adding/editing_a_course#Editing_a_course|go to adding/editing a course]]. To ADD items you must use the appropriate drop-downs for them.

{| border="1" cellpadding="2" cellspacing="0"
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="120"|Effect
!width="30"|Icon
!width="140"|Effect
|-
|[[Image:Edit.gif]]|| Edit item ||[[Image:Open.gif]]* || Close/Hide item||[[Image:Delete.gif]]** || Delete/Remove ||[[Image:Move.gif]] ||Move (up/down)
|-
||[[Image:All.gif]] ||See all weeks/topics||[[Image:Closed.gif]]* || Open/Show Item ||[[Image:Right.gif]] || Indent/shift right ||[[Image:Movehere.gif]] || Move here
|-
||[[Image:One.gif]] || See one week/topic||[[Image:Help.gif]] ||Help || || ||[[Image:Marker.gif]] ||Make Current (highlight) week/topic
|}
 
'''<nowiki>*</nowiki>''' (Note that the open eye indicates that the resource is visible, while clicking it changes it to be invisible (to students), and vice versa with the closed eye. '''<nowiki>**</nowiki>''' Note that the X deletes resources and activities (with a warning) whereas it only removes blocks (which can be added at any time later)

==Activity modules==
[[Image:Activity dropdown 1 8.JPG|frame|right|Add an activity drop-down menu - Moodle 1.8.2 ]] There are a number of robust interactive learning [[:Category:Modules|activity modules]] that you may [[Adding_resources_and_activities | add to your course]] with the "Add an activity" drop down menu.

Communication and collaboration may take place using live [[Chats]] or asynchronous discussion [[Forums]] for conversational activities. You can also use [[Choices]] to gain group feedback. Adding [[Wikis]] to your courses is an excellent way to allow students to work together on a collaboratively-authored project.

Work can be uploaded and submitted by students and scored by teachers using [[Assignments]] or [[Workshops]]. Workshops such as these have several assessment options, including instructor-assessment, self-assessment, and even peer-assessment. Online [[Quizzes]] offer several options for automatic and manual scoring. You can even integrate your Hot Potato quizzes by adding a [[Hotpot]] activity.

[[Lessons]] and [[SCORM]] activities deliver content and offer ways of individualizing your presentation based upon a student's choices. [[Glossaries]] of keywords can be set up by the instructor, and can be configured to allow students to edit, add, or rate entries.

[[Surveys]] and [[Database module|Databases]] are also very powerful additions to any course.

If all of that isn't enough for you then you can also add contributed modules that are not part of the official Moodle release!

==Resources==

[[Image:Resource pulldown menu .JPG 1 8.JPG|frame|left|Add a resource drop-down menu]]

Moodle supports a range of different [[Resources|resource types]] that allow you to include almost any kind of digital content into your courses. These can be added by using the [[Adding_resources_and_activities | add a resource]] dropdown box when editing is turned on.

A [[Text page]] is a simple page written using plain text. Text pages aren't pretty, but they're a good place to put some information or instructions. If you are after more options for your new page then you should be thinking about adding a [[Web page]] and making use of Moodle's WYSIWYG editor.

Of course the resource may already exist in electronic form so you may want to [[File or website link|link to an uploaded file or external website]] or simply display the complete contents of a [[Directory|directory]] in your course files and let your users pick the file themselves. If you have an [[IMS content package]] then this can be easily added to your course.

All resources may be organized, structured, and [[Label|labeled]] for usability.

==Blocks==
[[Image:Block add dropdown list teacher 1 8.JPG |thumb|150px|right|Add Block drop-down menu]]
Each course homepage generally contains [[Blocks_%28teacher%29|blocks]] on the left and right with the centre column containing the course content. Blocks may be added, hidden, deleted, and moved up, down and left/right when editing is turned on. Examples of blocks can be seen in the Getting Started image above. [[Latest News block|"Latest News"]], "[[Blogs]]", [[Upcoming Events block|"Upcoming Events"]], and [[Recent Activity block|"Recent Activity"]] are a few examples.

A wide range of [[Blocks_%28teacher%29#Block_types|over 16 different block types]] can provide additional information or functionality to the learner by the teacher. The standard blocks that come with Moodle are shown on the right. There are also many contributed developed by Moodlers that an administrator can add to this list.

A teacher with editing rights will also have a course [[Administration_block|administration block]]. This block has sub menus for course: backup/restore, enrollments, format, reports, grades, activity logs, files and other useful tools.

==General advice==

* Subscribe yourself to all of the [[forum]]s in your course so that you can keep in touch with your class activity.
* Encourage all of the students to fill out their [[Edit profile|user profile]] (including photos) and read them all - this will help provide some context to their later writings and help you to respond in ways that are tailored to their own needs.
* Keep notes to yourself in the private "Teacher's Forum" (under Administration). This is especially useful when team teaching.
* Use the [[Logs]] link (under Administration) to get access to complete, raw logs. In there you'll see a link to a popup window that updates every sixty seconds and shows the last hour of activity. This is useful to keep open on your desktop all day so you can feel in touch with what's going on in the course.
* Use many reports. [[Reports]] in the Administration block, [[Recent_activity|Activity Reports]] (next to each name in the list of all people, or from any user profile page). These provide a great way to see what any particular person has been up to in the course.
* Respond quickly to students. Don't leave it for later - do it right away. Not only is it easy to become overwhelmed with the volume that can be generated, but it's a crucial part of building and maintaining a community feel in your course.
*Don't be afraid to experiment: feel free to poke around and change things. It's hard to break anything in a Moodle course, and even if you do it's usually easy to fix it.
* Use the [[Navigation bar|navigation bar]] at the top of each page - this should help remind you where you are and prevent getting lost

== See also ==
*[[Teacher documentation]]

[[Category:Teacher]]
[[cs:Rukověť učitele]]
[[es:Documentación para Profesores]]
[[eu:Irakasleentzako dokumentazioa]]
[[fi:Opettajan opas]]
[[fr:Documentation enseignant]]
[[it:Documentazione per Docenti]]
[[ja:教師ドキュメント]]
[[nl:Documentatie voor leraren]]
[[ru:Учителям]]
[[zh:教师文档]]

Quiz preview

2006-12-01T18:11:37Z

Hrynkiw: /* For Students */ Lifting veil of confusion over purpose of "Save Without Submitting" button

{{Quizzes}}

==For Students==

Any volunteers for writing a help text here that could later become part of the standard Moodle documentation and be made accessible to students via a question mark icon on their attempt page?

[Rough copy, needs polishing.]
The "Save Without Submitting" button does not save the quiz answers so that the quiz can be opened and continued at a later date. The "Save Without Submitting" button saves answers already entered from accidental deletiong because of browser, computer, power, or network failure during the current session. See http://moodle.org/mod/forum/discuss.php?d=39440 and http://moodle.org/mod/forum/discuss.php?d=28084

==For Teachers==
This section needs serious editing.

=== Quiz preview ===
This will show you the quiz the way the student will see it. The only difference is that you will see a little link below each question number that you can click to be taken directly to the question editing page for that question. This makes it convenient for you to correct mistakes in questions straight from the preview page.

The '''quiz preview''' enables you to try the quiz. In a preview it will say 'Preview check'. Attempting a quiz, it will say which attempt at the test it is. Also, all the questions will have a mark index, i.e. the number of points gained per the number of points that could be gained for doing a given question. You will find it under the question number. Also, each question is given a Submit button.

The quiz questions being answered, you will find three options to go for:

# '''Save without submitting''' - which, as its name says, saves the answers without submitting them
# '''Submit page''' (optional) - which submits only a given quiz page
# '''Submit all and finish''' - which saves the whole quiz

[[Category:Teacher]]
[[Category:Quiz]]