<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="ca">
	<id>https://docs.moodle.org/2x/ca/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Tmuras</id>
	<title>MoodleDocs - Contribucions de l&amp;#039;usuari [ca]</title>
	<link rel="self" type="application/atom+xml" href="https://docs.moodle.org/2x/ca/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Tmuras"/>
	<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/Especial:Contribucions/Tmuras"/>
	<updated>2026-09-28T08:17:14Z</updated>
	<subtitle>Contribucions de l&amp;#039;usuari</subtitle>
	<generator>MediaWiki 1.43.5</generator>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Blogs_FAQ&amp;diff=103879</id>
		<title>Blogs FAQ</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Blogs_FAQ&amp;diff=103879"/>
		<updated>2013-04-07T08:04:19Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Blogs}}&lt;br /&gt;
==How can I limit blogging to specific users only?==&lt;br /&gt;
&lt;br /&gt;
See the [[Blogger role]].&lt;br /&gt;
&lt;br /&gt;
==How can I change the &#039;Publish to&#039; default setting?==&lt;br /&gt;
&lt;br /&gt;
By default, all blog entries are published to &#039;Anyone on this site&#039;. To change the default setting to &#039;Yourself (draft)&#039;, see the Using Moodle discussion [http://moodle.org/mod/forum/discuss.php?d=110983 Changing the Publish to Default Setting].&lt;br /&gt;
&lt;br /&gt;
==How can blogs be disabled completely?==&lt;br /&gt;
&lt;br /&gt;
In &#039;&#039;Settings &amp;gt; Site administration &amp;gt; Appearance &amp;gt; [[Blog]]&#039;&#039; set &#039;&#039;bloglevel&#039;&#039; to &#039;Disable blogs completely&#039;.&lt;br /&gt;
&lt;br /&gt;
==How can I backup &amp;amp; restore blogs?==&lt;br /&gt;
&lt;br /&gt;
In 1.9 blogs were backed up &amp;amp; restored while doing a site backups. This has not been reimplemented for Moodle 2, so there is currently (Moodle 2.5) no way to backup blogs: [https://tracker.moodle.org/browse/MDL-22136 tracker issue].&lt;br /&gt;
&lt;br /&gt;
==Viewing blogs==&lt;br /&gt;
&lt;br /&gt;
===How can I see the blog of a particular person? (ie all the entries by a person)===&lt;br /&gt;
*In the course, Click Participants &amp;gt; Student Name &amp;gt; [a new item appears in the nav block - you need to notice it] &amp;gt; Blogs &amp;gt; you will see &amp;quot;View all entries by Student Name&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===How can I see all the blog entries for associated with a particular course?===&lt;br /&gt;
#In the blogs block &amp;gt; &amp;quot;View all entries from this course&amp;quot;&lt;br /&gt;
#In the course, click Participants &amp;gt; Blogs.  Note: The term &#039;blog&#039; here could be misleading.  What you get is &amp;quot;Blog Posts attatched with a course&amp;quot;, not &#039;blogs&#039;.&lt;br /&gt;
&lt;br /&gt;
===How can I see all the posts associated with a particular person associated with a particular course?===&lt;br /&gt;
*It&#039;s not currently possible to do this.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
[[Category:FAQ]]&lt;br /&gt;
&lt;br /&gt;
[[de:Blog FAQ]]&lt;br /&gt;
[[eu:FAQ_Blogak]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=ThreeSixty_module&amp;diff=102882</id>
		<title>ThreeSixty module</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=ThreeSixty_module&amp;diff=102882"/>
		<updated>2013-01-25T10:40:17Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: Created page with &amp;quot;{{Activities}} {{Infobox plugin |type = Activity module |entry = ...  |tracker = ... |discussion = ... |maintainer = Enovation Solutions }}&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Activities}}&lt;br /&gt;
{{Infobox plugin&lt;br /&gt;
|type = Activity module&lt;br /&gt;
|entry = ... &lt;br /&gt;
|tracker = ...&lt;br /&gt;
|discussion = ...&lt;br /&gt;
|maintainer = Enovation Solutions&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Outcomes&amp;diff=97405</id>
		<title>Outcomes</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Outcomes&amp;diff=97405"/>
		<updated>2012-05-02T07:10:48Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Grades}}&lt;br /&gt;
Outcomes are specific descriptions of what a student has demonstrated and understood at the completion of an activity or course. Each outcome is rated by some sort of [[Scales|scale]]. Other terms for outcomes are &#039;&#039;Competencies&#039;&#039; and &#039;&#039;Goals&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
In simple terms outcomes are similar to sub components of a grade.  A grade is an assessment of overall performance that may include tests, participation, attendance and projects. Outcomes assess specific levels of knowledge through a series of statements, that maybe coded with numbers or letters.   Thus an overall grade can be given for a course, along with statements about specific competencies in the form of outcomes.  &lt;br /&gt;
&lt;br /&gt;
==Enabling outcomes==&lt;br /&gt;
# Go to &#039;&#039;Site administration &amp;gt; Advanced features&#039;&#039; and ensure that &#039;&#039;Enable outcomes&#039;&#039; is checked (by default, it isn&#039;t).&lt;br /&gt;
&lt;br /&gt;
==Using outcomes==&lt;br /&gt;
&lt;br /&gt;
# Choose or define some outcomes for your course (see below).&lt;br /&gt;
# For each activity, choose which of these outcomes apply using the tickbox in the activity&#039;s settings page.&lt;br /&gt;
# When grading that activity, grade each student using the Outcome scales. Note: You can also edit the grades in the [[Grader report]] (useful for modules that don&#039;t feature inbuilt grading).&lt;br /&gt;
# Use the outcomes as part of the assessment for students, or look at the Outcomes report for some useful feedback on how students in the class in general are performing.&lt;br /&gt;
&lt;br /&gt;
==Outcomes report==&lt;br /&gt;
&lt;br /&gt;
The outcomes report in &#039;&#039;Settings &amp;gt; Course administration &amp;gt; Grades &amp;gt; Outcomes report&#039;&#039; helps teachers monitor their students&#039; progress using outcomes.  It lists site-wide outcomes and custom outcomes used in the current course, their overall average (each outcome can be measured through many [[Grade items|grade items]]).  It will show the name, course and site wide average, the activity, the average values and the number of &amp;quot;grades&amp;quot; given.&lt;br /&gt;
&lt;br /&gt;
The outcomes report is a table with 6 columns:&lt;br /&gt;
&lt;br /&gt;
*Short name - the short name of the outcome used in this course.&lt;br /&gt;
*Course average -shows two values representing the average scores given to students for each outcome used in this course.&lt;br /&gt;
*Site-wide - Whether the outcome is a site-wide outcome or not.&lt;br /&gt;
*Activities - This lists the activities that use this outcome in this course. A new row is created for each activity, and the activity name is linked to the activity&#039;s page.&lt;br /&gt;
*Average - the average score for each activity using the outcome in this course.&lt;br /&gt;
*Number of Grades - The number of grades given to students for each activity using the outcome.&lt;br /&gt;
&lt;br /&gt;
==Outcomes used in course==&lt;br /&gt;
&lt;br /&gt;
Outcomes may be set at site and/or course level. To choose outcomes for use in your course:&lt;br /&gt;
&lt;br /&gt;
# View available standard outcomes in &#039;&#039;Settings &amp;gt; Course administration &amp;gt; Outcomes&#039;&#039; or via the gradebook Outcomes tab&lt;br /&gt;
# Add outcomes from the standard available list (right side), and use the left-facing arrow button to add them to outcomes used list (left side). Multiple outcomes may be selected by holding down the Apple or Ctrl key whilst clicking on the individual outcomes.&lt;br /&gt;
&lt;br /&gt;
==Adding course-level outcomes==&lt;br /&gt;
&lt;br /&gt;
[[Image:Adding an outcome.png|thumb|Adding an outcome]]To add a course-level outcome:&lt;br /&gt;
&lt;br /&gt;
# Click the &#039;Edit outcomes&#039; link in &#039;&#039;Settings &amp;gt; Course administration &amp;gt; Outcomes&#039;&#039;&lt;br /&gt;
# Click the &#039;Add a new outcome&#039; button.&lt;br /&gt;
# Complete the form then click the &#039;Save changes&#039; button. &lt;br /&gt;
&lt;br /&gt;
==Adding standard outcomes==&lt;br /&gt;
&lt;br /&gt;
An administrator can add standard outcomes, which are available site-wide, in &#039;&#039;Settings &amp;gt; Site administration &amp;gt; Grades &amp;gt; Outcomes&#039;&#039;. Multiple standard outcomes can be added using the import outcomes functionality (see below).&lt;br /&gt;
&lt;br /&gt;
==Exporting outcomes==&lt;br /&gt;
&lt;br /&gt;
Outcomes (and their associated scales) can be exported by clicking the &amp;quot;Export all outcomes&amp;quot; button.  This will send a file (in .csv format) that can be read by Excel, OpenOffice.org or by any text editor.&lt;br /&gt;
&lt;br /&gt;
==Importing outcomes==&lt;br /&gt;
&lt;br /&gt;
Outcomes (and associated scales) may be imported by submitting a csv file. The format should be as follows:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;nicetable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Field name&lt;br /&gt;
! Description&lt;br /&gt;
! Required&lt;br /&gt;
! Format&lt;br /&gt;
|-&lt;br /&gt;
| outcome_name&lt;br /&gt;
| The full name of the outcome&lt;br /&gt;
| Yes&lt;br /&gt;
| String&lt;br /&gt;
|-&lt;br /&gt;
| outcome_shortname&lt;br /&gt;
| The short name of the outcome&lt;br /&gt;
| Yes&lt;br /&gt;
| String&lt;br /&gt;
|-&lt;br /&gt;
| outcome_description&lt;br /&gt;
| The description of the outcome&lt;br /&gt;
| No&lt;br /&gt;
| String&lt;br /&gt;
|-&lt;br /&gt;
| scale_name&lt;br /&gt;
| The name of the scale used&lt;br /&gt;
| Yes&lt;br /&gt;
| String&lt;br /&gt;
|-&lt;br /&gt;
| scale_items&lt;br /&gt;
| A comma-separated list of scale items&lt;br /&gt;
| Yes&lt;br /&gt;
| String&lt;br /&gt;
|-&lt;br /&gt;
| scale_description&lt;br /&gt;
| The description of the scale&lt;br /&gt;
| No&lt;br /&gt;
| String&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here is an example:&lt;br /&gt;
&lt;br /&gt;
 outcome_name;outcome_shortname;outcome_description;scale_name;scale_items;scale_description&lt;br /&gt;
 Participation;participation;;Participation scale;&amp;quot;Little or no participation, Satisfactory participation, Full participation&amp;quot;;&lt;br /&gt;
&lt;br /&gt;
To import outcomes:&lt;br /&gt;
&lt;br /&gt;
# Click the &#039;Import outcomes&#039; link in &#039;&#039;Settings &amp;gt; Course administration &amp;gt; Outcomes&#039;&#039;&lt;br /&gt;
# Choose &#039;Import as custom outcomes (only this course)&#039; or &#039;Import as standard outcomes&#039; as required&lt;br /&gt;
# Upload the csv file&lt;br /&gt;
&lt;br /&gt;
Note that while importing: &lt;br /&gt;
*Existing outcomes and scale will be used if available (no overwriting is done by the script)&lt;br /&gt;
*The script will stop if it detects that the file contains invalid data&lt;br /&gt;
&lt;br /&gt;
==Removing selected outcomes for activities==&lt;br /&gt;
&lt;br /&gt;
Previously selected outcomes are greyed out on the update activity page, however they can be removed via the gradebook on the categories and items page. They will appear in the list either below or above the activity they have been enabled in and will have the same icon as that activity. Note that if you have renamed the outcome since you assigned it to the activity, the orginal name will be displayed. Deleting the outcomes from this list will result in the outcomes being deselected on the update activity page.&lt;br /&gt;
&lt;br /&gt;
==Outcomes capabilities==&lt;br /&gt;
&lt;br /&gt;
* [[Capabilities/gradereport/outcomes:view|View the outcomes report]]&lt;br /&gt;
* [[Capabilities/moodle/grade:manageoutcomes|Manage grade outcomes]]&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
	&lt;br /&gt;
*[http://www.slideshare.net/mariamoodle/outcomes-2724350 Moodle 1.9 Outcomes] External link to slide show demonstration&lt;br /&gt;
*[[Outcome examples]] - An example use of Outcomes&lt;br /&gt;
*[http://www.youtube.com/watch?v=PmkEGfvjj9U Video on how to use outcomes in Moodle]&lt;br /&gt;
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=78074 Outcomes in 1.9] forum discussion&lt;br /&gt;
&lt;br /&gt;
[[Category:Report]]&lt;br /&gt;
&lt;br /&gt;
[[es:Resultados]]&lt;br /&gt;
[[fr:Objectifs]]&lt;br /&gt;
[[ja:アウトカム]]&lt;br /&gt;
[[de:Lernziele]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Flashcard_module&amp;diff=97023</id>
		<title>Flashcard module</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Flashcard_module&amp;diff=97023"/>
		<updated>2012-04-17T20:58:24Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: /* Usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The &#039;&#039;&#039;flashcard module&#039;&#039;&#039; may be downloaded from https://github.com/tmuras/Moodle-Flashcard/zipball/master .&lt;br /&gt;
&lt;br /&gt;
The flashcard module allows editing and playing flashcards. Flashcards are a &amp;quot;memory training&amp;quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.&lt;br /&gt;
&lt;br /&gt;
==Features==&lt;br /&gt;
&lt;br /&gt;
* Getting cards from a &amp;quot;matching question&amp;quot;&lt;br /&gt;
* Editing cards&lt;br /&gt;
* Multimedia cards: text, image, sound and image + sound together&lt;br /&gt;
* Automated backpropagation of cards (can be disabled)&lt;br /&gt;
* Customizable decks&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&lt;br /&gt;
[[Flashcard module: Configuration Parameters]]&lt;br /&gt;
&lt;br /&gt;
[[Flashcard module: Capabilities]]&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===Adding new cards===&lt;br /&gt;
# Add new &amp;quot;Flash Card Set&amp;quot; into the course&lt;br /&gt;
# Enter required field &amp;quot;Name&amp;quot; and click &amp;quot;Save and display&amp;quot; button&lt;br /&gt;
# Click &amp;quot;Edit the cards&amp;quot; tabs - you will be brought to screen like below&lt;br /&gt;
[[File:flashcard1.jpg]]&lt;br /&gt;
# Click &amp;quot;Add three new questions&amp;quot; button&lt;br /&gt;
# Add text for questions and answers&lt;br /&gt;
# Click &amp;quot;Update&amp;quot; button&lt;br /&gt;
&lt;br /&gt;
==Screens==&lt;br /&gt;
&lt;br /&gt;
===Student Screens=== &lt;br /&gt;
&lt;br /&gt;
*[[Flashcard module: Freeplay Screen|Freeplay Screen]]&lt;br /&gt;
* Leitner Play Screens&lt;br /&gt;
** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]&lt;br /&gt;
** [[Flashcard module: Leitner Use A Deck|Use a deck]]&lt;br /&gt;
&lt;br /&gt;
===Teacher Screens===&lt;br /&gt;
&lt;br /&gt;
* Summary Screens&lt;br /&gt;
**[[Flashcard module: By User Summary|By User Summary]]&lt;br /&gt;
**[[Flashcard module: By Card Summary|By Card Summary]]&lt;br /&gt;
*[[Flashcard module: Edit Screen|Edit Screen]]&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Lesson_module#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.&lt;br /&gt;
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]&lt;br /&gt;
&lt;br /&gt;
[[Category:Contributed code]]&lt;br /&gt;
[[fr: Flashcard]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Fitxer:flashcard1.jpg&amp;diff=97022</id>
		<title>Fitxer:flashcard1.jpg</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Fitxer:flashcard1.jpg&amp;diff=97022"/>
		<updated>2012-04-17T20:56:58Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Flashcard_module&amp;diff=97021</id>
		<title>Flashcard module</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Flashcard_module&amp;diff=97021"/>
		<updated>2012-04-17T20:56:46Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The &#039;&#039;&#039;flashcard module&#039;&#039;&#039; may be downloaded from https://github.com/tmuras/Moodle-Flashcard/zipball/master .&lt;br /&gt;
&lt;br /&gt;
The flashcard module allows editing and playing flashcards. Flashcards are a &amp;quot;memory training&amp;quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.&lt;br /&gt;
&lt;br /&gt;
==Features==&lt;br /&gt;
&lt;br /&gt;
* Getting cards from a &amp;quot;matching question&amp;quot;&lt;br /&gt;
* Editing cards&lt;br /&gt;
* Multimedia cards: text, image, sound and image + sound together&lt;br /&gt;
* Automated backpropagation of cards (can be disabled)&lt;br /&gt;
* Customizable decks&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&lt;br /&gt;
[[Flashcard module: Configuration Parameters]]&lt;br /&gt;
&lt;br /&gt;
[[Flashcard module: Capabilities]]&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===Adding new cards===&lt;br /&gt;
# Add new &amp;quot;Flash Card Set&amp;quot; into the course&lt;br /&gt;
# Enter required field &amp;quot;Name&amp;quot; and click &amp;quot;Save and display&amp;quot; button&lt;br /&gt;
# Click &amp;quot;Edit the cards&amp;quot; tabs - you will be brought to screen like below&lt;br /&gt;
[[File:flashcard1.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Screens==&lt;br /&gt;
&lt;br /&gt;
===Student Screens=== &lt;br /&gt;
&lt;br /&gt;
*[[Flashcard module: Freeplay Screen|Freeplay Screen]]&lt;br /&gt;
* Leitner Play Screens&lt;br /&gt;
** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]&lt;br /&gt;
** [[Flashcard module: Leitner Use A Deck|Use a deck]]&lt;br /&gt;
&lt;br /&gt;
===Teacher Screens===&lt;br /&gt;
&lt;br /&gt;
* Summary Screens&lt;br /&gt;
**[[Flashcard module: By User Summary|By User Summary]]&lt;br /&gt;
**[[Flashcard module: By Card Summary|By Card Summary]]&lt;br /&gt;
*[[Flashcard module: Edit Screen|Edit Screen]]&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Lesson_module#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.&lt;br /&gt;
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]&lt;br /&gt;
&lt;br /&gt;
[[Category:Contributed code]]&lt;br /&gt;
[[fr: Flashcard]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Upgrading&amp;diff=96757</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Upgrading&amp;diff=96757"/>
		<updated>2012-04-02T09:11:44Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: /* Using CVS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Installing Moodle}}	&lt;br /&gt;
&#039;&#039;&#039;Before you do anything else, read [[Upgrading to Moodle 2.2]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Moodle is designed to upgrade itself from one version to the next. The procedure is&lt;br /&gt;
# [[Site backup|Back up everything]].&lt;br /&gt;
# Replace the old version of the code with the new one.&lt;br /&gt;
# Visit the [[Site_administration_block#Notifications|administrator notifications]] link, which triggers Moodle to self-update.&lt;br /&gt;
These steps are explained in more detail below.&lt;br /&gt;
&lt;br /&gt;
Sometimes there are specific considerations when upgrading to a particular version.  See the [[dev:Releases|Releases page]] for more information on this.  You also have to be more careful if you have installed additional plug-ins or customised the code.&lt;br /&gt;
&lt;br /&gt;
See this tutorial if you are [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf upgrading Moodle on cpanel]. It is a bit rough around the edges and is a little dated, but you should get the idea.&lt;br /&gt;
&lt;br /&gt;
There is also a separate page about [[Ubuntu_Debian_Upgrades|upgrading Moodle if you installed it using the Ubuntu/Kubuntu/Debian package manager]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
When upgrading a Moodle installation you should follow these steps:&lt;br /&gt;
&lt;br /&gt;
==Before you upgrade your site for real==&lt;br /&gt;
&lt;br /&gt;
You are strongly advised to make a copy of your entire Moodle site onto another computer (see [[Moodle migration]]) and run the upgrade there to verify it will work. If you decide not to do this, make sure you have good backups. If the upgrade fails you will need the backups to go back.&lt;br /&gt;
&lt;br /&gt;
==Check the requirements==&lt;br /&gt;
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the target version you want to upgrade-to in &#039;&#039;Settings &amp;gt; Site administration &amp;gt; Server &amp;gt; [[Environment]]&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Put your Site into Maintenance Mode==&lt;br /&gt;
Before you begin upgrading your site, you should put it into [[Maintenance_mode | Maintenance Mode]] to stop any non-admin users from logging in.&lt;br /&gt;
&lt;br /&gt;
== Backup important data ==&lt;br /&gt;
See [[Site backup]] for more specific information.&lt;br /&gt;
&lt;br /&gt;
There are three areas that should be backed up before any upgrade:&lt;br /&gt;
#Moodle software (For example, everything in server/htdocs/moodle)&lt;br /&gt;
#Moodle uploaded files (For example, server/moodledata)&lt;br /&gt;
#Moodle database (For example, the SQL or Postgres database)&lt;br /&gt;
&lt;br /&gt;
Experienced site administrators know that it is a best practice (a very good idea) to make a backup of any production system before a major upgrade. In fact, it is a good idea to automate your server to backup your Moodle installation daily.  Most upgrades on sites that have used the standard Moodle packages (no contributed code and no little tweaks to the php files), will not have any major issues with the upgrade process.  &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; One more time, &amp;quot;do not risk what you can not afford to lose&amp;quot;: do regular backups, make sure it is really backed up and know how to restore a backup!&lt;br /&gt;
&lt;br /&gt;
== Install the new Moodle software ==&lt;br /&gt;
Upgrading can be a simple process or a more complicated process.  Sites that have not used contributed code and are migrating from say Moodle 2.x.1 to 2.x.3 &#039;&#039;&#039;should&#039;&#039;&#039; not have a problem.  However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files.  &lt;br /&gt;
&lt;br /&gt;
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.&lt;br /&gt;
&lt;br /&gt;
=== Standard install package ===&lt;br /&gt;
Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.&lt;br /&gt;
*It is probably a good idea to use the [[Site administration block]]&amp;gt;Server&amp;gt;Maintenance mode to prevent user activity as the site upgrades. &lt;br /&gt;
*Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server.  Moodle will adjust SQL and [[Moodledata directory|moodledata]] if it needs to in the upgrade.&lt;br /&gt;
*Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. If you&#039;ve defined individual blocks for new courses you have to delete &#039;admin&#039; block definition and replace by &#039;settings&#039; for the new block.&lt;br /&gt;
*If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet). &lt;br /&gt;
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress.  &lt;br /&gt;
*After a successful upgrade, turn off the maintenance mode, so your users can get into the site.&lt;br /&gt;
&lt;br /&gt;
=== Using a downloaded archive ===&lt;br /&gt;
In some installs, the site administrator may overwrite the Moodle code with a backup copy.  Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders). &lt;br /&gt;
&lt;br /&gt;
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or &amp;quot;cleaned&amp;quot; installations. The best way is to rename the current Moodle code directory (for example rename &amp;quot;moodle&amp;quot; to &amp;quot;moodleold&amp;quot;), then unpack the new Moodle archive into the old location (for example, a new directory called &amp;quot;moodle&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
====Linux====&lt;br /&gt;
 mv moodle moodle.backup&lt;br /&gt;
 tar xvzf moodle-1.1.tgz&lt;br /&gt;
&lt;br /&gt;
Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one (&#039;&#039;&#039;check that optional/custom plugins are the correct version for your new Moodle first&#039;&#039;&#039;):&lt;br /&gt;
&lt;br /&gt;
 cp moodle.backup/config.php moodle&lt;br /&gt;
 cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme&lt;br /&gt;
 cp -pr moodle.backup/mod/mymod moodle/mod/mymod&lt;br /&gt;
&lt;br /&gt;
Don&#039;t forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writable by your server.&lt;br /&gt;
&lt;br /&gt;
If you use cron, take care that cron.php is executeable and uses the correct php command: &lt;br /&gt;
 chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)&lt;br /&gt;
 copy the first line from cron.php (if it looks like &#039;#!/usr/local/bin/php&#039; or &#039;#!/usr/local/bin/php5.3&#039;, no need to copy &#039;&amp;lt;?php&#039;)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
if necessary.&lt;br /&gt;
&lt;br /&gt;
=== Using Git ===&lt;br /&gt;
&lt;br /&gt;
You can use [[Git]] for updating or upgrading your Moodle. New sites are recommended to use this rather than CVS since all Moodle development has moved to Git.&lt;br /&gt;
&lt;br /&gt;
See [[Git for Administrators]] for further details.&lt;br /&gt;
&lt;br /&gt;
== Finishing the upgrade ==&lt;br /&gt;
&lt;br /&gt;
The last step is to trigger the upgrade processes within Moodle. &lt;br /&gt;
&lt;br /&gt;
To do this just visit the [[Site administration block]] admin page (or &#039;&#039;&amp;lt;nowiki&amp;gt;http://example.com/moodle/admin&amp;lt;/nowiki&amp;gt;&#039;&#039;) and the &amp;quot;Notifications&amp;quot; link.&lt;br /&gt;
&lt;br /&gt;
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can&#039;t do itself (very rare) then you will see messages telling you what you need to do.&lt;br /&gt;
&lt;br /&gt;
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; Use the site administration block&amp;gt;Server&amp;gt;Maintenance mode to prevent users from changing data during the upgrade.&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing.  Post a thread or check the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and check [[Tracker]] for potential issues.&lt;br /&gt;
&lt;br /&gt;
== Verify the upgrade (optional) ==&lt;br /&gt;
&lt;br /&gt;
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].&lt;br /&gt;
&lt;br /&gt;
==Upgrading more than one version==&lt;br /&gt;
&lt;br /&gt;
Normally you can upgrade directly from any Moodle version to any later version. So, for example you could upgrade from 2.0 to 2.1, or from 1.9 to 2.2.&lt;br /&gt;
&lt;br /&gt;
However, every so often, this general rule gets broken, because supporting really large jumps (for example Moodle 1.6 to 2.2 in one step) would be impossible. Recent break points have been:&lt;br /&gt;
* You must have upgraded to version 1.9.x before you can upgrade to a later 2.x version.&lt;br /&gt;
* You must have upgraded to version 2.2.x before you can upgrade to 2.3 or later.&lt;br /&gt;
&lt;br /&gt;
If you are upgrading from a pre-1.6 version it is recommended that you upgrade first to the latest 1.6.x, then to the latest 1.9.x and finally to the latest 2.x. See Petr&#039;s forum post [http://moodle.org/mod/forum/discuss.php?d=197602#p861964 Re: Continuing on Upgrade docs] for further information.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Environment]]&lt;br /&gt;
*[[Git]] Version control and upgrading&lt;br /&gt;
*[[How to fix just one bug without upgrading]]&lt;br /&gt;
*Moodle.org [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] &lt;br /&gt;
*[http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial] - screencasts of older Moodle/Cpanel install but useful (also, a very large file that will take some time to load).&lt;br /&gt;
&lt;br /&gt;
Documentation on upgrading to particular versions:&lt;br /&gt;
*[[Upgrading to Moodle 2.2]]&lt;br /&gt;
*[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to Moodle 2.1]&lt;br /&gt;
*[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to Moodle 2.0]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to Moodle 1.9]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.8 Upgrading to Moodle 1.8]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.7 Upgrading to Moodle 1.7]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.6 Upgrading to Moodle 1.6]&lt;br /&gt;
&lt;br /&gt;
Using Moodle.org forum discussions:&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=198123 Language customizations lost on upgrade]&lt;br /&gt;
*[[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration]]&lt;br /&gt;
&lt;br /&gt;
[[es:Actualización de moodle]]&lt;br /&gt;
[[fr:Mise à jour]]&lt;br /&gt;
[[ja:Moodleをアップグレードする]]&lt;br /&gt;
[[de:Aktualisierung von Moodle]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Upgrading&amp;diff=96756</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Upgrading&amp;diff=96756"/>
		<updated>2012-04-02T09:07:27Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: /* Linux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Installing Moodle}}	&lt;br /&gt;
&#039;&#039;&#039;Before you do anything else, read [[Upgrading to Moodle 2.2]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Moodle is designed to upgrade itself from one version to the next. The procedure is&lt;br /&gt;
# [[Site backup|Back up everything]].&lt;br /&gt;
# Replace the old version of the code with the new one.&lt;br /&gt;
# Visit the [[Site_administration_block#Notifications|administrator notifications]] link, which triggers Moodle to self-update.&lt;br /&gt;
These steps are explained in more detail below.&lt;br /&gt;
&lt;br /&gt;
Sometimes there are specific considerations when upgrading to a particular version.  See the [[dev:Releases|Releases page]] for more information on this.  You also have to be more careful if you have installed additional plug-ins or customised the code.&lt;br /&gt;
&lt;br /&gt;
See this tutorial if you are [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf upgrading Moodle on cpanel]. It is a bit rough around the edges and is a little dated, but you should get the idea.&lt;br /&gt;
&lt;br /&gt;
There is also a separate page about [[Ubuntu_Debian_Upgrades|upgrading Moodle if you installed it using the Ubuntu/Kubuntu/Debian package manager]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
When upgrading a Moodle installation you should follow these steps:&lt;br /&gt;
&lt;br /&gt;
==Before you upgrade your site for real==&lt;br /&gt;
&lt;br /&gt;
You are strongly advised to make a copy of your entire Moodle site onto another computer (see [[Moodle migration]]) and run the upgrade there to verify it will work. If you decide not to do this, make sure you have good backups. If the upgrade fails you will need the backups to go back.&lt;br /&gt;
&lt;br /&gt;
==Check the requirements==&lt;br /&gt;
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the target version you want to upgrade-to in &#039;&#039;Settings &amp;gt; Site administration &amp;gt; Server &amp;gt; [[Environment]]&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Put your Site into Maintenance Mode==&lt;br /&gt;
Before you begin upgrading your site, you should put it into [[Maintenance_mode | Maintenance Mode]] to stop any non-admin users from logging in.&lt;br /&gt;
&lt;br /&gt;
== Backup important data ==&lt;br /&gt;
See [[Site backup]] for more specific information.&lt;br /&gt;
&lt;br /&gt;
There are three areas that should be backed up before any upgrade:&lt;br /&gt;
#Moodle software (For example, everything in server/htdocs/moodle)&lt;br /&gt;
#Moodle uploaded files (For example, server/moodledata)&lt;br /&gt;
#Moodle database (For example, the SQL or Postgres database)&lt;br /&gt;
&lt;br /&gt;
Experienced site administrators know that it is a best practice (a very good idea) to make a backup of any production system before a major upgrade. In fact, it is a good idea to automate your server to backup your Moodle installation daily.  Most upgrades on sites that have used the standard Moodle packages (no contributed code and no little tweaks to the php files), will not have any major issues with the upgrade process.  &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; One more time, &amp;quot;do not risk what you can not afford to lose&amp;quot;: do regular backups, make sure it is really backed up and know how to restore a backup!&lt;br /&gt;
&lt;br /&gt;
== Install the new Moodle software ==&lt;br /&gt;
Upgrading can be a simple process or a more complicated process.  Sites that have not used contributed code and are migrating from say Moodle 2.x.1 to 2.x.3 &#039;&#039;&#039;should&#039;&#039;&#039; not have a problem.  However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files.  &lt;br /&gt;
&lt;br /&gt;
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.&lt;br /&gt;
&lt;br /&gt;
=== Standard install package ===&lt;br /&gt;
Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.&lt;br /&gt;
*It is probably a good idea to use the [[Site administration block]]&amp;gt;Server&amp;gt;Maintenance mode to prevent user activity as the site upgrades. &lt;br /&gt;
*Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server.  Moodle will adjust SQL and [[Moodledata directory|moodledata]] if it needs to in the upgrade.&lt;br /&gt;
*Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. If you&#039;ve defined individual blocks for new courses you have to delete &#039;admin&#039; block definition and replace by &#039;settings&#039; for the new block.&lt;br /&gt;
*If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet). &lt;br /&gt;
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress.  &lt;br /&gt;
*After a successful upgrade, turn off the maintenance mode, so your users can get into the site.&lt;br /&gt;
&lt;br /&gt;
=== Using a downloaded archive ===&lt;br /&gt;
In some installs, the site administrator may overwrite the Moodle code with a backup copy.  Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders). &lt;br /&gt;
&lt;br /&gt;
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or &amp;quot;cleaned&amp;quot; installations. The best way is to rename the current Moodle code directory (for example rename &amp;quot;moodle&amp;quot; to &amp;quot;moodleold&amp;quot;), then unpack the new Moodle archive into the old location (for example, a new directory called &amp;quot;moodle&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
====Linux====&lt;br /&gt;
 mv moodle moodle.backup&lt;br /&gt;
 tar xvzf moodle-1.1.tgz&lt;br /&gt;
&lt;br /&gt;
Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one (&#039;&#039;&#039;check that optional/custom plugins are the correct version for your new Moodle first&#039;&#039;&#039;):&lt;br /&gt;
&lt;br /&gt;
 cp moodle.backup/config.php moodle&lt;br /&gt;
 cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme&lt;br /&gt;
 cp -pr moodle.backup/mod/mymod moodle/mod/mymod&lt;br /&gt;
&lt;br /&gt;
Don&#039;t forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writable by your server.&lt;br /&gt;
&lt;br /&gt;
If you use cron, take care that cron.php is executeable and uses the correct php command: &lt;br /&gt;
 chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)&lt;br /&gt;
 copy the first line from cron.php (if it looks like &#039;#!/usr/local/bin/php&#039; or &#039;#!/usr/local/bin/php5.3&#039;, no need to copy &#039;&amp;lt;?php&#039;)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
if necessary.&lt;br /&gt;
&lt;br /&gt;
=== Using CVS ===&lt;br /&gt;
&lt;br /&gt;
New sites should now use Git rather than CVS (see next section). If your site already uses CVS, to update, just go into the Moodle root directory and update to the new files:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ cd /path/to/your/moodle/&lt;br /&gt;
$ cvs update -dP&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
To update from an older version type in the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ cd /path/to/your/moodle/&lt;br /&gt;
$ cvs -Q update -dP -r MOODLE_18_STABLE&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure you use the &amp;quot;d&amp;quot; parameter to create new directories if necessary, and the &amp;quot;P&amp;quot; parameter to prune empty directories.&lt;br /&gt;
&lt;br /&gt;
=== Using Git ===&lt;br /&gt;
&lt;br /&gt;
You can use [[Git]] for updating or upgrading your Moodle. New sites are recommended to use this rather than CVS since all Moodle development has moved to Git.&lt;br /&gt;
&lt;br /&gt;
See [[Git for Administrators]] for further details.&lt;br /&gt;
&lt;br /&gt;
== Finishing the upgrade ==&lt;br /&gt;
&lt;br /&gt;
The last step is to trigger the upgrade processes within Moodle. &lt;br /&gt;
&lt;br /&gt;
To do this just visit the [[Site administration block]] admin page (or &#039;&#039;&amp;lt;nowiki&amp;gt;http://example.com/moodle/admin&amp;lt;/nowiki&amp;gt;&#039;&#039;) and the &amp;quot;Notifications&amp;quot; link.&lt;br /&gt;
&lt;br /&gt;
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can&#039;t do itself (very rare) then you will see messages telling you what you need to do.&lt;br /&gt;
&lt;br /&gt;
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; Use the site administration block&amp;gt;Server&amp;gt;Maintenance mode to prevent users from changing data during the upgrade.&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing.  Post a thread or check the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and check [[Tracker]] for potential issues.&lt;br /&gt;
&lt;br /&gt;
== Verify the upgrade (optional) ==&lt;br /&gt;
&lt;br /&gt;
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].&lt;br /&gt;
&lt;br /&gt;
==Upgrading more than one version==&lt;br /&gt;
&lt;br /&gt;
Normally you can upgrade directly from any Moodle version to any later version. So, for example you could upgrade from 2.0 to 2.1, or from 1.9 to 2.2.&lt;br /&gt;
&lt;br /&gt;
However, every so often, this general rule gets broken, because supporting really large jumps (for example Moodle 1.6 to 2.2 in one step) would be impossible. Recent break points have been:&lt;br /&gt;
* You must have upgraded to version 1.9.x before you can upgrade to a later 2.x version.&lt;br /&gt;
* You must have upgraded to version 2.2.x before you can upgrade to 2.3 or later.&lt;br /&gt;
&lt;br /&gt;
If you are upgrading from a pre-1.6 version it is recommended that you upgrade first to the latest 1.6.x, then to the latest 1.9.x and finally to the latest 2.x. See Petr&#039;s forum post [http://moodle.org/mod/forum/discuss.php?d=197602#p861964 Re: Continuing on Upgrade docs] for further information.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Environment]]&lt;br /&gt;
*[[Git]] Version control and upgrading&lt;br /&gt;
*[[How to fix just one bug without upgrading]]&lt;br /&gt;
*Moodle.org [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] &lt;br /&gt;
*[http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial] - screencasts of older Moodle/Cpanel install but useful (also, a very large file that will take some time to load).&lt;br /&gt;
&lt;br /&gt;
Documentation on upgrading to particular versions:&lt;br /&gt;
*[[Upgrading to Moodle 2.2]]&lt;br /&gt;
*[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to Moodle 2.1]&lt;br /&gt;
*[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to Moodle 2.0]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to Moodle 1.9]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.8 Upgrading to Moodle 1.8]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.7 Upgrading to Moodle 1.7]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.6 Upgrading to Moodle 1.6]&lt;br /&gt;
&lt;br /&gt;
Using Moodle.org forum discussions:&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=198123 Language customizations lost on upgrade]&lt;br /&gt;
*[[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration]]&lt;br /&gt;
&lt;br /&gt;
[[es:Actualización de moodle]]&lt;br /&gt;
[[fr:Mise à jour]]&lt;br /&gt;
[[ja:Moodleをアップグレードする]]&lt;br /&gt;
[[de:Aktualisierung von Moodle]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Upgrading&amp;diff=96755</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Upgrading&amp;diff=96755"/>
		<updated>2012-04-02T09:05:07Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: /* Linux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Installing Moodle}}	&lt;br /&gt;
&#039;&#039;&#039;Before you do anything else, read [[Upgrading to Moodle 2.2]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Moodle is designed to upgrade itself from one version to the next. The procedure is&lt;br /&gt;
# [[Site backup|Back up everything]].&lt;br /&gt;
# Replace the old version of the code with the new one.&lt;br /&gt;
# Visit the [[Site_administration_block#Notifications|administrator notifications]] link, which triggers Moodle to self-update.&lt;br /&gt;
These steps are explained in more detail below.&lt;br /&gt;
&lt;br /&gt;
Sometimes there are specific considerations when upgrading to a particular version.  See the [[dev:Releases|Releases page]] for more information on this.  You also have to be more careful if you have installed additional plug-ins or customised the code.&lt;br /&gt;
&lt;br /&gt;
See this tutorial if you are [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf upgrading Moodle on cpanel]. It is a bit rough around the edges and is a little dated, but you should get the idea.&lt;br /&gt;
&lt;br /&gt;
There is also a separate page about [[Ubuntu_Debian_Upgrades|upgrading Moodle if you installed it using the Ubuntu/Kubuntu/Debian package manager]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
When upgrading a Moodle installation you should follow these steps:&lt;br /&gt;
&lt;br /&gt;
==Before you upgrade your site for real==&lt;br /&gt;
&lt;br /&gt;
You are strongly advised to make a copy of your entire Moodle site onto another computer (see [[Moodle migration]]) and run the upgrade there to verify it will work. If you decide not to do this, make sure you have good backups. If the upgrade fails you will need the backups to go back.&lt;br /&gt;
&lt;br /&gt;
==Check the requirements==&lt;br /&gt;
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the target version you want to upgrade-to in &#039;&#039;Settings &amp;gt; Site administration &amp;gt; Server &amp;gt; [[Environment]]&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Put your Site into Maintenance Mode==&lt;br /&gt;
Before you begin upgrading your site, you should put it into [[Maintenance_mode | Maintenance Mode]] to stop any non-admin users from logging in.&lt;br /&gt;
&lt;br /&gt;
== Backup important data ==&lt;br /&gt;
See [[Site backup]] for more specific information.&lt;br /&gt;
&lt;br /&gt;
There are three areas that should be backed up before any upgrade:&lt;br /&gt;
#Moodle software (For example, everything in server/htdocs/moodle)&lt;br /&gt;
#Moodle uploaded files (For example, server/moodledata)&lt;br /&gt;
#Moodle database (For example, the SQL or Postgres database)&lt;br /&gt;
&lt;br /&gt;
Experienced site administrators know that it is a best practice (a very good idea) to make a backup of any production system before a major upgrade. In fact, it is a good idea to automate your server to backup your Moodle installation daily.  Most upgrades on sites that have used the standard Moodle packages (no contributed code and no little tweaks to the php files), will not have any major issues with the upgrade process.  &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; One more time, &amp;quot;do not risk what you can not afford to lose&amp;quot;: do regular backups, make sure it is really backed up and know how to restore a backup!&lt;br /&gt;
&lt;br /&gt;
== Install the new Moodle software ==&lt;br /&gt;
Upgrading can be a simple process or a more complicated process.  Sites that have not used contributed code and are migrating from say Moodle 2.x.1 to 2.x.3 &#039;&#039;&#039;should&#039;&#039;&#039; not have a problem.  However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files.  &lt;br /&gt;
&lt;br /&gt;
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.&lt;br /&gt;
&lt;br /&gt;
=== Standard install package ===&lt;br /&gt;
Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.&lt;br /&gt;
*It is probably a good idea to use the [[Site administration block]]&amp;gt;Server&amp;gt;Maintenance mode to prevent user activity as the site upgrades. &lt;br /&gt;
*Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server.  Moodle will adjust SQL and [[Moodledata directory|moodledata]] if it needs to in the upgrade.&lt;br /&gt;
*Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. If you&#039;ve defined individual blocks for new courses you have to delete &#039;admin&#039; block definition and replace by &#039;settings&#039; for the new block.&lt;br /&gt;
*If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet). &lt;br /&gt;
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress.  &lt;br /&gt;
*After a successful upgrade, turn off the maintenance mode, so your users can get into the site.&lt;br /&gt;
&lt;br /&gt;
=== Using a downloaded archive ===&lt;br /&gt;
In some installs, the site administrator may overwrite the Moodle code with a backup copy.  Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders). &lt;br /&gt;
&lt;br /&gt;
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or &amp;quot;cleaned&amp;quot; installations. The best way is to rename the current Moodle code directory (for example rename &amp;quot;moodle&amp;quot; to &amp;quot;moodleold&amp;quot;), then unpack the new Moodle archive into the old location (for example, a new directory called &amp;quot;moodle&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
====Linux====&lt;br /&gt;
 mv moodle moodle.backup&lt;br /&gt;
 tar xvzf moodle-1.1.tgz&lt;br /&gt;
&lt;br /&gt;
Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one (&#039;&#039;&#039;check that optional/custom plugins are the correct version for your new Moodle first&#039;&#039;&#039;):&lt;br /&gt;
&lt;br /&gt;
 cp moodle.backup/config.php moodle&lt;br /&gt;
 cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme&lt;br /&gt;
 cp -pr moodle.backup/mod/mymod moodle/mod/mymod&lt;br /&gt;
&lt;br /&gt;
Don&#039;t forget to make moodle/config.php readable by your www server.&lt;br /&gt;
&lt;br /&gt;
If you use cron, take care that cron.php is executeable and uses the correct php command: &lt;br /&gt;
 chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)&lt;br /&gt;
 copy the first line from cron.php (if it looks like &#039;#!/usr/local/bin/php&#039; or &#039;#!/usr/local/bin/php5.3&#039;, no need to copy &#039;&amp;lt;?php&#039;)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
if necessary.&lt;br /&gt;
&lt;br /&gt;
=== Using CVS ===&lt;br /&gt;
&lt;br /&gt;
New sites should now use Git rather than CVS (see next section). If your site already uses CVS, to update, just go into the Moodle root directory and update to the new files:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ cd /path/to/your/moodle/&lt;br /&gt;
$ cvs update -dP&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
To update from an older version type in the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ cd /path/to/your/moodle/&lt;br /&gt;
$ cvs -Q update -dP -r MOODLE_18_STABLE&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure you use the &amp;quot;d&amp;quot; parameter to create new directories if necessary, and the &amp;quot;P&amp;quot; parameter to prune empty directories.&lt;br /&gt;
&lt;br /&gt;
=== Using Git ===&lt;br /&gt;
&lt;br /&gt;
You can use [[Git]] for updating or upgrading your Moodle. New sites are recommended to use this rather than CVS since all Moodle development has moved to Git.&lt;br /&gt;
&lt;br /&gt;
See [[Git for Administrators]] for further details.&lt;br /&gt;
&lt;br /&gt;
== Finishing the upgrade ==&lt;br /&gt;
&lt;br /&gt;
The last step is to trigger the upgrade processes within Moodle. &lt;br /&gt;
&lt;br /&gt;
To do this just visit the [[Site administration block]] admin page (or &#039;&#039;&amp;lt;nowiki&amp;gt;http://example.com/moodle/admin&amp;lt;/nowiki&amp;gt;&#039;&#039;) and the &amp;quot;Notifications&amp;quot; link.&lt;br /&gt;
&lt;br /&gt;
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can&#039;t do itself (very rare) then you will see messages telling you what you need to do.&lt;br /&gt;
&lt;br /&gt;
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; Use the site administration block&amp;gt;Server&amp;gt;Maintenance mode to prevent users from changing data during the upgrade.&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing.  Post a thread or check the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and check [[Tracker]] for potential issues.&lt;br /&gt;
&lt;br /&gt;
== Verify the upgrade (optional) ==&lt;br /&gt;
&lt;br /&gt;
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].&lt;br /&gt;
&lt;br /&gt;
==Upgrading more than one version==&lt;br /&gt;
&lt;br /&gt;
Normally you can upgrade directly from any Moodle version to any later version. So, for example you could upgrade from 2.0 to 2.1, or from 1.9 to 2.2.&lt;br /&gt;
&lt;br /&gt;
However, every so often, this general rule gets broken, because supporting really large jumps (for example Moodle 1.6 to 2.2 in one step) would be impossible. Recent break points have been:&lt;br /&gt;
* You must have upgraded to version 1.9.x before you can upgrade to a later 2.x version.&lt;br /&gt;
* You must have upgraded to version 2.2.x before you can upgrade to 2.3 or later.&lt;br /&gt;
&lt;br /&gt;
If you are upgrading from a pre-1.6 version it is recommended that you upgrade first to the latest 1.6.x, then to the latest 1.9.x and finally to the latest 2.x. See Petr&#039;s forum post [http://moodle.org/mod/forum/discuss.php?d=197602#p861964 Re: Continuing on Upgrade docs] for further information.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Environment]]&lt;br /&gt;
*[[Git]] Version control and upgrading&lt;br /&gt;
*[[How to fix just one bug without upgrading]]&lt;br /&gt;
*Moodle.org [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] &lt;br /&gt;
*[http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial] - screencasts of older Moodle/Cpanel install but useful (also, a very large file that will take some time to load).&lt;br /&gt;
&lt;br /&gt;
Documentation on upgrading to particular versions:&lt;br /&gt;
*[[Upgrading to Moodle 2.2]]&lt;br /&gt;
*[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to Moodle 2.1]&lt;br /&gt;
*[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to Moodle 2.0]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to Moodle 1.9]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.8 Upgrading to Moodle 1.8]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.7 Upgrading to Moodle 1.7]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.6 Upgrading to Moodle 1.6]&lt;br /&gt;
&lt;br /&gt;
Using Moodle.org forum discussions:&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=198123 Language customizations lost on upgrade]&lt;br /&gt;
*[[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration]]&lt;br /&gt;
&lt;br /&gt;
[[es:Actualización de moodle]]&lt;br /&gt;
[[fr:Mise à jour]]&lt;br /&gt;
[[ja:Moodleをアップグレードする]]&lt;br /&gt;
[[de:Aktualisierung von Moodle]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Upgrading&amp;diff=96754</id>
		<title>Upgrading</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Upgrading&amp;diff=96754"/>
		<updated>2012-04-02T09:03:45Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: /* Linux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Installing Moodle}}	&lt;br /&gt;
&#039;&#039;&#039;Before you do anything else, read [[Upgrading to Moodle 2.2]]&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Moodle is designed to upgrade itself from one version to the next. The procedure is&lt;br /&gt;
# [[Site backup|Back up everything]].&lt;br /&gt;
# Replace the old version of the code with the new one.&lt;br /&gt;
# Visit the [[Site_administration_block#Notifications|administrator notifications]] link, which triggers Moodle to self-update.&lt;br /&gt;
These steps are explained in more detail below.&lt;br /&gt;
&lt;br /&gt;
Sometimes there are specific considerations when upgrading to a particular version.  See the [[dev:Releases|Releases page]] for more information on this.  You also have to be more careful if you have installed additional plug-ins or customised the code.&lt;br /&gt;
&lt;br /&gt;
See this tutorial if you are [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf upgrading Moodle on cpanel]. It is a bit rough around the edges and is a little dated, but you should get the idea.&lt;br /&gt;
&lt;br /&gt;
There is also a separate page about [[Ubuntu_Debian_Upgrades|upgrading Moodle if you installed it using the Ubuntu/Kubuntu/Debian package manager]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
When upgrading a Moodle installation you should follow these steps:&lt;br /&gt;
&lt;br /&gt;
==Before you upgrade your site for real==&lt;br /&gt;
&lt;br /&gt;
You are strongly advised to make a copy of your entire Moodle site onto another computer (see [[Moodle migration]]) and run the upgrade there to verify it will work. If you decide not to do this, make sure you have good backups. If the upgrade fails you will need the backups to go back.&lt;br /&gt;
&lt;br /&gt;
==Check the requirements==&lt;br /&gt;
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the target version you want to upgrade-to in &#039;&#039;Settings &amp;gt; Site administration &amp;gt; Server &amp;gt; [[Environment]]&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Put your Site into Maintenance Mode==&lt;br /&gt;
Before you begin upgrading your site, you should put it into [[Maintenance_mode | Maintenance Mode]] to stop any non-admin users from logging in.&lt;br /&gt;
&lt;br /&gt;
== Backup important data ==&lt;br /&gt;
See [[Site backup]] for more specific information.&lt;br /&gt;
&lt;br /&gt;
There are three areas that should be backed up before any upgrade:&lt;br /&gt;
#Moodle software (For example, everything in server/htdocs/moodle)&lt;br /&gt;
#Moodle uploaded files (For example, server/moodledata)&lt;br /&gt;
#Moodle database (For example, the SQL or Postgres database)&lt;br /&gt;
&lt;br /&gt;
Experienced site administrators know that it is a best practice (a very good idea) to make a backup of any production system before a major upgrade. In fact, it is a good idea to automate your server to backup your Moodle installation daily.  Most upgrades on sites that have used the standard Moodle packages (no contributed code and no little tweaks to the php files), will not have any major issues with the upgrade process.  &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; One more time, &amp;quot;do not risk what you can not afford to lose&amp;quot;: do regular backups, make sure it is really backed up and know how to restore a backup!&lt;br /&gt;
&lt;br /&gt;
== Install the new Moodle software ==&lt;br /&gt;
Upgrading can be a simple process or a more complicated process.  Sites that have not used contributed code and are migrating from say Moodle 2.x.1 to 2.x.3 &#039;&#039;&#039;should&#039;&#039;&#039; not have a problem.  However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files.  &lt;br /&gt;
&lt;br /&gt;
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.&lt;br /&gt;
&lt;br /&gt;
=== Standard install package ===&lt;br /&gt;
Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.&lt;br /&gt;
*It is probably a good idea to use the [[Site administration block]]&amp;gt;Server&amp;gt;Maintenance mode to prevent user activity as the site upgrades. &lt;br /&gt;
*Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server.  Moodle will adjust SQL and [[Moodledata directory|moodledata]] if it needs to in the upgrade.&lt;br /&gt;
*Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. If you&#039;ve defined individual blocks for new courses you have to delete &#039;admin&#039; block definition and replace by &#039;settings&#039; for the new block.&lt;br /&gt;
*If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet). &lt;br /&gt;
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress.  &lt;br /&gt;
*After a successful upgrade, turn off the maintenance mode, so your users can get into the site.&lt;br /&gt;
&lt;br /&gt;
=== Using a downloaded archive ===&lt;br /&gt;
In some installs, the site administrator may overwrite the Moodle code with a backup copy.  Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders). &lt;br /&gt;
&lt;br /&gt;
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or &amp;quot;cleaned&amp;quot; installations. The best way is to rename the current Moodle code directory (for example rename &amp;quot;moodle&amp;quot; to &amp;quot;moodleold&amp;quot;), then unpack the new Moodle archive into the old location (for example, a new directory called &amp;quot;moodle&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
====Linux====&lt;br /&gt;
 mv moodle moodle.backup&lt;br /&gt;
 tar xvzf moodle-1.1.tgz&lt;br /&gt;
&lt;br /&gt;
Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one (&#039;&#039;&#039;check that optional/custom plugins are the correct version for your new Moodle first&#039;&#039;&#039;):&lt;br /&gt;
&lt;br /&gt;
 cp moodle.backup/config.php moodle&lt;br /&gt;
 cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme&lt;br /&gt;
 cp -pr moodle.backup/mod/mymod moodle/mod/mymod&lt;br /&gt;
&lt;br /&gt;
Don&#039;t forget to make moodle/config.php readable by your www server.&lt;br /&gt;
&lt;br /&gt;
If you use cron, take care that cron.php is executeable and uses the correct php command: &lt;br /&gt;
 chmod 740 admin/cli/cron.php (some configurations need chmod 750)&lt;br /&gt;
 copy the first line from cron.php (if it looks like &#039;#!/usr/local/bin/php&#039; or &#039;#!/usr/local/bin/php5.3&#039;, no need to copy &#039;&amp;lt;?php&#039;)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
if necessary.&lt;br /&gt;
&lt;br /&gt;
where www-data is whatever user the Apache user is on your system. This is often &#039;apache&#039; or &#039;www&#039;.&lt;br /&gt;
You can find out by doing &#039;ls -l&#039; in your /var/www/moodle folder (or wherever your moodle site is)&lt;br /&gt;
and then looking at the owner and group.&lt;br /&gt;
&lt;br /&gt;
so you may see something like&lt;br /&gt;
&lt;br /&gt;
 ls -l&lt;br /&gt;
 ...lots of lines...&lt;br /&gt;
 -rw-r--r--   1 apache system     784 Jun 28  2007 config.php &lt;br /&gt;
 ...lots more lines...&lt;br /&gt;
&lt;br /&gt;
so the owner is apache and the group is system. &lt;br /&gt;
&lt;br /&gt;
To replicate this on your new system you can do  &#039;chown apache:system config.php&#039; &lt;br /&gt;
&lt;br /&gt;
or to do a whole group do&lt;br /&gt;
&lt;br /&gt;
 chown apache:system ./*&lt;br /&gt;
&lt;br /&gt;
and recursively&lt;br /&gt;
&lt;br /&gt;
 chown -R apache:system ./*&lt;br /&gt;
&lt;br /&gt;
=== Using CVS ===&lt;br /&gt;
&lt;br /&gt;
New sites should now use Git rather than CVS (see next section). If your site already uses CVS, to update, just go into the Moodle root directory and update to the new files:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ cd /path/to/your/moodle/&lt;br /&gt;
$ cvs update -dP&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
To update from an older version type in the following:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ cd /path/to/your/moodle/&lt;br /&gt;
$ cvs -Q update -dP -r MOODLE_18_STABLE&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure you use the &amp;quot;d&amp;quot; parameter to create new directories if necessary, and the &amp;quot;P&amp;quot; parameter to prune empty directories.&lt;br /&gt;
&lt;br /&gt;
=== Using Git ===&lt;br /&gt;
&lt;br /&gt;
You can use [[Git]] for updating or upgrading your Moodle. New sites are recommended to use this rather than CVS since all Moodle development has moved to Git.&lt;br /&gt;
&lt;br /&gt;
See [[Git for Administrators]] for further details.&lt;br /&gt;
&lt;br /&gt;
== Finishing the upgrade ==&lt;br /&gt;
&lt;br /&gt;
The last step is to trigger the upgrade processes within Moodle. &lt;br /&gt;
&lt;br /&gt;
To do this just visit the [[Site administration block]] admin page (or &#039;&#039;&amp;lt;nowiki&amp;gt;http://example.com/moodle/admin&amp;lt;/nowiki&amp;gt;&#039;&#039;) and the &amp;quot;Notifications&amp;quot; link.&lt;br /&gt;
&lt;br /&gt;
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can&#039;t do itself (very rare) then you will see messages telling you what you need to do.&lt;br /&gt;
&lt;br /&gt;
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; Use the site administration block&amp;gt;Server&amp;gt;Maintenance mode to prevent users from changing data during the upgrade.&lt;br /&gt;
:&#039;&#039;TIP:&#039;&#039; If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing.  Post a thread or check the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and check [[Tracker]] for potential issues.&lt;br /&gt;
&lt;br /&gt;
== Verify the upgrade (optional) ==&lt;br /&gt;
&lt;br /&gt;
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].&lt;br /&gt;
&lt;br /&gt;
==Upgrading more than one version==&lt;br /&gt;
&lt;br /&gt;
Normally you can upgrade directly from any Moodle version to any later version. So, for example you could upgrade from 2.0 to 2.1, or from 1.9 to 2.2.&lt;br /&gt;
&lt;br /&gt;
However, every so often, this general rule gets broken, because supporting really large jumps (for example Moodle 1.6 to 2.2 in one step) would be impossible. Recent break points have been:&lt;br /&gt;
* You must have upgraded to version 1.9.x before you can upgrade to a later 2.x version.&lt;br /&gt;
* You must have upgraded to version 2.2.x before you can upgrade to 2.3 or later.&lt;br /&gt;
&lt;br /&gt;
If you are upgrading from a pre-1.6 version it is recommended that you upgrade first to the latest 1.6.x, then to the latest 1.9.x and finally to the latest 2.x. See Petr&#039;s forum post [http://moodle.org/mod/forum/discuss.php?d=197602#p861964 Re: Continuing on Upgrade docs] for further information.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
&lt;br /&gt;
*[[Environment]]&lt;br /&gt;
*[[Git]] Version control and upgrading&lt;br /&gt;
*[[How to fix just one bug without upgrading]]&lt;br /&gt;
*Moodle.org [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] &lt;br /&gt;
*[http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial] - screencasts of older Moodle/Cpanel install but useful (also, a very large file that will take some time to load).&lt;br /&gt;
&lt;br /&gt;
Documentation on upgrading to particular versions:&lt;br /&gt;
*[[Upgrading to Moodle 2.2]]&lt;br /&gt;
*[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to Moodle 2.1]&lt;br /&gt;
*[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to Moodle 2.0]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to Moodle 1.9]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.8 Upgrading to Moodle 1.8]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.7 Upgrading to Moodle 1.7]&lt;br /&gt;
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.6 Upgrading to Moodle 1.6]&lt;br /&gt;
&lt;br /&gt;
Using Moodle.org forum discussions:&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]&lt;br /&gt;
*[http://moodle.org/mod/forum/discuss.php?d=198123 Language customizations lost on upgrade]&lt;br /&gt;
*[[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration]]&lt;br /&gt;
&lt;br /&gt;
[[es:Actualización de moodle]]&lt;br /&gt;
[[fr:Mise à jour]]&lt;br /&gt;
[[ja:Moodleをアップグレードする]]&lt;br /&gt;
[[de:Aktualisierung von Moodle]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Flashcard_module&amp;diff=84935</id>
		<title>Flashcard module</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Flashcard_module&amp;diff=84935"/>
		<updated>2011-06-12T10:18:02Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The &#039;&#039;&#039;flashcard module&#039;&#039;&#039; may be downloaded from https://github.com/tmuras/Moodle-Flashcard/zipball/master .&lt;br /&gt;
&lt;br /&gt;
The flashcard module allows editing and playing flashcards. Flashcards are a &amp;quot;memory training&amp;quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.&lt;br /&gt;
&lt;br /&gt;
==Features==&lt;br /&gt;
&lt;br /&gt;
* Getting cards from a &amp;quot;matching question&amp;quot;&lt;br /&gt;
* Editing cards&lt;br /&gt;
* Multimedia cards: text, image, sound and image + sound together&lt;br /&gt;
* Automated backpropagation of cards (can be disabled)&lt;br /&gt;
* Customizable decks&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&lt;br /&gt;
[[Flashcard module: Configuration Parameters]]&lt;br /&gt;
&lt;br /&gt;
[[Flashcard module: Capabilities]]&lt;br /&gt;
&lt;br /&gt;
==Screens==&lt;br /&gt;
&lt;br /&gt;
===Student Screens=== &lt;br /&gt;
&lt;br /&gt;
*[[Flashcard module: Freeplay Screen|Freeplay Screen]]&lt;br /&gt;
* Leitner Play Screens&lt;br /&gt;
** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]&lt;br /&gt;
** [[Flashcard module: Leitner Use A Deck|Use a deck]]&lt;br /&gt;
&lt;br /&gt;
===Teacher Screens===&lt;br /&gt;
&lt;br /&gt;
* Summary Screens&lt;br /&gt;
**[[Flashcard module: By User Summary|By User Summary]]&lt;br /&gt;
**[[Flashcard module: By Card Summary|By Card Summary]]&lt;br /&gt;
*[[Flashcard module: Edit Screen|Edit Screen]]&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Lesson_module#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.&lt;br /&gt;
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]&lt;br /&gt;
&lt;br /&gt;
[[Category:Contributed code]]&lt;br /&gt;
[[fr: Flashcard]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Flashcard_module&amp;diff=82498</id>
		<title>Flashcard module</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Flashcard_module&amp;diff=82498"/>
		<updated>2011-04-02T09:06:09Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The &#039;&#039;&#039;flashcard module&#039;&#039;&#039; may be downloaded (for Moodle 2.0) from https://github.com/tmuras/Moodle-Flashcard/zipball/master (updated on 2 Apr 2011) .&lt;br /&gt;
&lt;br /&gt;
Actual stable version is at http://download.moodle.org/plugins19/mod/flashcard.zip .&lt;br /&gt;
&lt;br /&gt;
The flashcard module allows editing and playing flashcards. Flashcards are a &amp;quot;memory training&amp;quot; device that uses the concept of repetition. Checking a flashcard deck will present the student the couples of relationships to be memorized. More often the associations are reviewed, deeper the memorization will be engraved into our memorial circuits.&lt;br /&gt;
&lt;br /&gt;
==Features==&lt;br /&gt;
&lt;br /&gt;
* Getting cards from a &amp;quot;matching question&amp;quot;&lt;br /&gt;
* Editing cards&lt;br /&gt;
* Multimedia cards: text, image, sound and image + sound together&lt;br /&gt;
* Automated backpropagation of cards (can be disabled)&lt;br /&gt;
* Customizable decks&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&lt;br /&gt;
[[Flashcard module: Configuration Parameters]]&lt;br /&gt;
&lt;br /&gt;
[[Flashcard module: Capabilities]]&lt;br /&gt;
&lt;br /&gt;
==Screens==&lt;br /&gt;
&lt;br /&gt;
===Student Screens=== &lt;br /&gt;
&lt;br /&gt;
*[[Flashcard module: Freeplay Screen|Freeplay Screen]]&lt;br /&gt;
* Leitner Play Screens&lt;br /&gt;
** [[Flashcard module: Leitner Choose A Deck|Choose a deck to play with]]&lt;br /&gt;
** [[Flashcard module: Leitner Use A Deck|Use a deck]]&lt;br /&gt;
&lt;br /&gt;
===Teacher Screens===&lt;br /&gt;
&lt;br /&gt;
* Summary Screens&lt;br /&gt;
**[[Flashcard module: By User Summary|By User Summary]]&lt;br /&gt;
**[[Flashcard module: By Card Summary|By Card Summary]]&lt;br /&gt;
*[[Flashcard module: Edit Screen|Edit Screen]]&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Lesson_module#The_Flash_card_lesson|Flash card presentation]] in the [[Lesson module]] is an alternative to this module.&lt;br /&gt;
* Using Moodle [http://moodle.org/mod/forum/view.php?id=7180 Flashcard module forum]&lt;br /&gt;
&lt;br /&gt;
[[Category:Contributed code]]&lt;br /&gt;
[[fr: Flashcard]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Timetrack_block&amp;diff=80589</id>
		<title>Timetrack block</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Timetrack_block&amp;diff=80589"/>
		<updated>2011-01-18T10:38:09Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
The Timetrack Block allows Admin and Teacher users to log entries of activities undertaken, such as Tutorials, Assignment marking, to the database. The date, task, quantity and pre-defined payment value will be logged.&lt;br /&gt;
&lt;br /&gt;
The Block also allows reporting on the values logged, filtered by a date range. This report can be exported to CSV,&lt;br /&gt;
&lt;br /&gt;
It was developed by [http://www.enovation.ie Enovation Solutions].&lt;br /&gt;
&lt;br /&gt;
=Installation=&lt;br /&gt;
* Extract and upload code to the blocks/ directory&lt;br /&gt;
* Log in to Moodle as the administrator and visit the Notifications page&lt;br /&gt;
* timetrack and timetrack_options tables will be created&lt;br /&gt;
* Permissions will be created which provide system roles of teachers and editing teachers with access&lt;br /&gt;
* If the timetrack_options table is empty it will be populated with some values&lt;br /&gt;
* Click the Turn Editing On button&lt;br /&gt;
* Add the Tutor Time Tracking block to the page&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The permissions added by this block allow teachers and editing teachers access to the block.  Administrators also have access to the block.&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;The make the block accessible to the teachers/tutors, the relevant users should have been added to the teacher/editingteacher system groups.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==To add a teacher to the system group==&lt;br /&gt;
* Click on the Moodle Menu  Users &amp;gt; Permissions &amp;gt; Assign System Roles&lt;br /&gt;
* Click on the system group (Teachers or Editing Teachers)&lt;br /&gt;
* Add the users to the system group&lt;br /&gt;
&lt;br /&gt;
==To set the block content==&lt;br /&gt;
The block contains three content elements: the title, the link text and the footer text.  These can be set by turning edit mode on and clicking on the configuration icon which will appear in the block in edit mode.&lt;br /&gt;
&lt;br /&gt;
=Usage=&lt;br /&gt;
&lt;br /&gt;
==Tutor Time Tracking Entries==&lt;br /&gt;
&lt;br /&gt;
* The Block provides access to a single page, block/timetrack/add.php (the Task entry page).&lt;br /&gt;
&lt;br /&gt;
[[Image:timetrackblock.jpg]]&lt;br /&gt;
&lt;br /&gt;
* The entry page contains 5 rows consisting of Users Name, Date, Task Allocation dropdown, Quantity input&lt;br /&gt;
* The user completes as many rows as they desire and submits them. &lt;br /&gt;
* Upon submit They are then presented with confirmation screen which allows them to cancel and return to the entry page, or confirm their entries and write them to the database.&lt;br /&gt;
* Some of the teacher tasks require a quantity entry.  If these quantities are not entered, the user will be asked to enter them prior to the confirmation screen  &lt;br /&gt;
* Some other teacher tasks do not require a quantity - these will default to a quantity of 1 and the user will go directly to the confirmation screen&lt;br /&gt;
[[Image:timetrack_entryscreenerror.jpg]] &lt;br /&gt;
* After the user confirms the entries, the value totals are calculated, and the data is written to the database, the user will be returned to add.php and a success message displayed.&lt;br /&gt;
&lt;br /&gt;
==Tutor Time Tracking Reports==&lt;br /&gt;
&lt;br /&gt;
* The Time Tracking reports are accessed through add.php. add.php contains a link to view.php.&lt;br /&gt;
* The time tracking report page have two date selection points, the start of the report period and the end of the report period.&lt;br /&gt;
* Once a date range has been selected, pressing the Find Tracking Entries button will produce the report on screen.&lt;br /&gt;
* The report contains the teacher&#039;s name, date, task allocation, quantity, rate for the task, total&lt;br /&gt;
* A button titled &#039;Export to Excel&#039; is located at the bottom of the report.  This will offer a CSV file for download.&lt;br /&gt;
* The CSV file contains the same data that is visible on screen, with one addition column containing the teacher&#039;s name.&lt;br /&gt;
&lt;br /&gt;
[[Image:timetrack_reportscreen.jpg]]&lt;br /&gt;
&lt;br /&gt;
=Test cases=&lt;br /&gt;
==Admin data entry==&lt;br /&gt;
* Log in as admin&lt;br /&gt;
* Turn editing on&lt;br /&gt;
* Add the Tutor Time Tracking block&lt;br /&gt;
* Click on the link in the Tutor Time Tracking Block&lt;br /&gt;
* Select task allocations, from 0 allocations to 5&lt;br /&gt;
* Enter integer quantities&lt;br /&gt;
* Some quantities must be entered for some (currently Assignments and Special Event) task allocations&lt;br /&gt;
* Click Submit times&lt;br /&gt;
&lt;br /&gt;
==Admin report==&lt;br /&gt;
* Log in as admin&lt;br /&gt;
* Use the steps above to add the block if it has not already been added&lt;br /&gt;
* Click on the link in the block&lt;br /&gt;
* Click on the link &#039;View Time Tracking History&#039;&lt;br /&gt;
* Select a day, month and year for the start of the report period&lt;br /&gt;
* Select a day, month and year for the end of the report period&lt;br /&gt;
* Select a tutor from the dropdown list (if any).  This will default to the current user, and will only list users who have entered time tracking data. Only admin users should see this dropdown selection of tutors, the tutors themselves will only see their own name.&lt;br /&gt;
* Click on the button titled &#039;Find tracking entries&#039;&lt;br /&gt;
* At the bottom of the report (if any) click on the button titled &#039;Export to Excel&#039;&lt;br /&gt;
* A CSV file should be offered for download containing the report data, plus an additional column (col 1) containing the user&#039;s name&lt;br /&gt;
&lt;br /&gt;
==Teacher with a system role data entry and report==&lt;br /&gt;
* Log in as a teacher (any user assigned the system role of &#039;Teacher&#039; or &#039;Editing Teacher&#039; : Users &amp;gt; Permissions &amp;gt; Assign system roles)&lt;br /&gt;
* Repeat the steps above to enter Tutor Time Tracking Data and generate reports&lt;br /&gt;
* The Block should function in the same way for Teachers as it does for admins, with the exception that teachers can only view their own report and cannot select a different user&#039;s report&lt;br /&gt;
&lt;br /&gt;
==Teacher WITHOUT a system role data entry and report ==&lt;br /&gt;
* Log in as a teacher who has not been assign a system role, but has been assign the role of &#039;Teach&#039; or &#039;Editing Teacher&#039; in a single course&lt;br /&gt;
* Repeat the steps above (Admin Report) to enter Tutor Time Tracking Data and generate reports&lt;br /&gt;
* The Block should function in the same way for Teachers as it does for admins, with the exception that teachers can only view their own report and cannot select a different user&#039;s report&lt;br /&gt;
&lt;br /&gt;
==Student==&lt;br /&gt;
* Log in as a student&lt;br /&gt;
* The Tutor Time Tracking block should not be displayed&lt;br /&gt;
* A student should not be able to access:&lt;br /&gt;
**/blocks/timetrack/add.php&lt;br /&gt;
**/blocks/timetrack/view.php&lt;br /&gt;
**/blocks/timetrack/excel.php&lt;br /&gt;
&lt;br /&gt;
=Known issues and TODO=&lt;br /&gt;
Please report bugs on [http://tracker.moodle.org/browse/CONTRIB/component/10870 Moodle tracker]. We happily accept the patches, source code is tracked in [https://github.com/enovation/Moodle-Timetrack-block github].&lt;br /&gt;
&lt;br /&gt;
* Download excel data as the administrator.  The current setup may be sufficient (the admin can select a tutor), but they may want to download data across selected multiple teachers, or all data for all tutors.&lt;br /&gt;
* Once data is submitted and confirmed, the tutor is returned to the data entry page.  They may need to be redirected to the report, or the moodle homepage, or the course homepage.&lt;br /&gt;
* Once data is submitted, it is written to the database after the tutor clicks the &#039;confirm submission&#039; button.  This may be unclear; instructions could be entered to make this clearer and save the loss of data.&lt;br /&gt;
* Very high quantity values (9999999999999999999999999) will hit the system upper limited and become (9223372036854775807).  Sane max values should be enforced.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Contributed code]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Timetrack_block&amp;diff=80588</id>
		<title>Timetrack block</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Timetrack_block&amp;diff=80588"/>
		<updated>2011-01-18T10:37:07Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: /* Known issues and TODO */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
The Timetrack Block allows Admin and Teacher users to log entries of activities undertaken, such as Tutorials, Assignment marking, to the database. The date, task, quantity and pre-defined payment value will be logged.&lt;br /&gt;
&lt;br /&gt;
The Block also allows reporting on the values logged, filtered by a date range. This report can be exported to CSV, &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Installation=&lt;br /&gt;
* Extract and upload code to the blocks/ directory&lt;br /&gt;
* Log in to Moodle as the administrator and visit the Notifications page&lt;br /&gt;
* timetrack and timetrack_options tables will be created&lt;br /&gt;
* Permissions will be created which provide system roles of teachers and editing teachers with access&lt;br /&gt;
* If the timetrack_options table is empty it will be populated with some values&lt;br /&gt;
* Click the Turn Editing On button&lt;br /&gt;
* Add the Tutor Time Tracking block to the page&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The permissions added by this block allow teachers and editing teachers access to the block.  Administrators also have access to the block.&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;The make the block accessible to the teachers/tutors, the relevant users should have been added to the teacher/editingteacher system groups.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==To add a teacher to the system group==&lt;br /&gt;
* Click on the Moodle Menu  Users &amp;gt; Permissions &amp;gt; Assign System Roles&lt;br /&gt;
* Click on the system group (Teachers or Editing Teachers)&lt;br /&gt;
* Add the users to the system group&lt;br /&gt;
&lt;br /&gt;
==To set the block content==&lt;br /&gt;
The block contains three content elements: the title, the link text and the footer text.  These can be set by turning edit mode on and clicking on the configuration icon which will appear in the block in edit mode.&lt;br /&gt;
&lt;br /&gt;
=Usage=&lt;br /&gt;
&lt;br /&gt;
==Tutor Time Tracking Entries==&lt;br /&gt;
&lt;br /&gt;
* The Block provides access to a single page, block/timetrack/add.php (the Task entry page).&lt;br /&gt;
&lt;br /&gt;
[[Image:timetrackblock.jpg]]&lt;br /&gt;
&lt;br /&gt;
* The entry page contains 5 rows consisting of Users Name, Date, Task Allocation dropdown, Quantity input&lt;br /&gt;
* The user completes as many rows as they desire and submits them. &lt;br /&gt;
* Upon submit They are then presented with confirmation screen which allows them to cancel and return to the entry page, or confirm their entries and write them to the database.&lt;br /&gt;
* Some of the teacher tasks require a quantity entry.  If these quantities are not entered, the user will be asked to enter them prior to the confirmation screen  &lt;br /&gt;
* Some other teacher tasks do not require a quantity - these will default to a quantity of 1 and the user will go directly to the confirmation screen&lt;br /&gt;
[[Image:timetrack_entryscreenerror.jpg]] &lt;br /&gt;
* After the user confirms the entries, the value totals are calculated, and the data is written to the database, the user will be returned to add.php and a success message displayed.&lt;br /&gt;
&lt;br /&gt;
==Tutor Time Tracking Reports==&lt;br /&gt;
&lt;br /&gt;
* The Time Tracking reports are accessed through add.php. add.php contains a link to view.php.&lt;br /&gt;
* The time tracking report page have two date selection points, the start of the report period and the end of the report period.&lt;br /&gt;
* Once a date range has been selected, pressing the Find Tracking Entries button will produce the report on screen.&lt;br /&gt;
* The report contains the teacher&#039;s name, date, task allocation, quantity, rate for the task, total&lt;br /&gt;
* A button titled &#039;Export to Excel&#039; is located at the bottom of the report.  This will offer a CSV file for download.&lt;br /&gt;
* The CSV file contains the same data that is visible on screen, with one addition column containing the teacher&#039;s name.&lt;br /&gt;
&lt;br /&gt;
[[Image:timetrack_reportscreen.jpg]]&lt;br /&gt;
&lt;br /&gt;
=Test cases=&lt;br /&gt;
==Admin data entry==&lt;br /&gt;
* Log in as admin&lt;br /&gt;
* Turn editing on&lt;br /&gt;
* Add the Tutor Time Tracking block&lt;br /&gt;
* Click on the link in the Tutor Time Tracking Block&lt;br /&gt;
* Select task allocations, from 0 allocations to 5&lt;br /&gt;
* Enter integer quantities&lt;br /&gt;
* Some quantities must be entered for some (currently Assignments and Special Event) task allocations&lt;br /&gt;
* Click Submit times&lt;br /&gt;
&lt;br /&gt;
==Admin report==&lt;br /&gt;
* Log in as admin&lt;br /&gt;
* Use the steps above to add the block if it has not already been added&lt;br /&gt;
* Click on the link in the block&lt;br /&gt;
* Click on the link &#039;View Time Tracking History&#039;&lt;br /&gt;
* Select a day, month and year for the start of the report period&lt;br /&gt;
* Select a day, month and year for the end of the report period&lt;br /&gt;
* Select a tutor from the dropdown list (if any).  This will default to the current user, and will only list users who have entered time tracking data. Only admin users should see this dropdown selection of tutors, the tutors themselves will only see their own name.&lt;br /&gt;
* Click on the button titled &#039;Find tracking entries&#039;&lt;br /&gt;
* At the bottom of the report (if any) click on the button titled &#039;Export to Excel&#039;&lt;br /&gt;
* A CSV file should be offered for download containing the report data, plus an additional column (col 1) containing the user&#039;s name&lt;br /&gt;
&lt;br /&gt;
==Teacher with a system role data entry and report==&lt;br /&gt;
* Log in as a teacher (any user assigned the system role of &#039;Teacher&#039; or &#039;Editing Teacher&#039; : Users &amp;gt; Permissions &amp;gt; Assign system roles)&lt;br /&gt;
* Repeat the steps above to enter Tutor Time Tracking Data and generate reports&lt;br /&gt;
* The Block should function in the same way for Teachers as it does for admins, with the exception that teachers can only view their own report and cannot select a different user&#039;s report&lt;br /&gt;
&lt;br /&gt;
==Teacher WITHOUT a system role data entry and report ==&lt;br /&gt;
* Log in as a teacher who has not been assign a system role, but has been assign the role of &#039;Teach&#039; or &#039;Editing Teacher&#039; in a single course&lt;br /&gt;
* Repeat the steps above (Admin Report) to enter Tutor Time Tracking Data and generate reports&lt;br /&gt;
* The Block should function in the same way for Teachers as it does for admins, with the exception that teachers can only view their own report and cannot select a different user&#039;s report&lt;br /&gt;
&lt;br /&gt;
==Student==&lt;br /&gt;
* Log in as a student&lt;br /&gt;
* The Tutor Time Tracking block should not be displayed&lt;br /&gt;
* A student should not be able to access:&lt;br /&gt;
**/blocks/timetrack/add.php&lt;br /&gt;
**/blocks/timetrack/view.php&lt;br /&gt;
**/blocks/timetrack/excel.php&lt;br /&gt;
&lt;br /&gt;
=Known issues and TODO=&lt;br /&gt;
Please report bugs on [http://tracker.moodle.org/browse/CONTRIB/component/10870 Moodle tracker]. We happily accept the patches, source code is tracked in [https://github.com/enovation/Moodle-Timetrack-block github].&lt;br /&gt;
&lt;br /&gt;
* Download excel data as the administrator.  The current setup may be sufficient (the admin can select a tutor), but they may want to download data across selected multiple teachers, or all data for all tutors.&lt;br /&gt;
* Once data is submitted and confirmed, the tutor is returned to the data entry page.  They may need to be redirected to the report, or the moodle homepage, or the course homepage.&lt;br /&gt;
* Once data is submitted, it is written to the database after the tutor clicks the &#039;confirm submission&#039; button.  This may be unclear; instructions could be entered to make this clearer and save the loss of data.&lt;br /&gt;
* Very high quantity values (9999999999999999999999999) will hit the system upper limited and become (9223372036854775807).  Sane max values should be enforced.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Contributed code]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Timetrack_block&amp;diff=80587</id>
		<title>Timetrack block</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Timetrack_block&amp;diff=80587"/>
		<updated>2011-01-18T10:29:31Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: /* Usage */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
The Timetrack Block allows Admin and Teacher users to log entries of activities undertaken, such as Tutorials, Assignment marking, to the database. The date, task, quantity and pre-defined payment value will be logged.&lt;br /&gt;
&lt;br /&gt;
The Block also allows reporting on the values logged, filtered by a date range. This report can be exported to CSV, &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Installation=&lt;br /&gt;
* Extract and upload code to the blocks/ directory&lt;br /&gt;
* Log in to Moodle as the administrator and visit the Notifications page&lt;br /&gt;
* timetrack and timetrack_options tables will be created&lt;br /&gt;
* Permissions will be created which provide system roles of teachers and editing teachers with access&lt;br /&gt;
* If the timetrack_options table is empty it will be populated with some values&lt;br /&gt;
* Click the Turn Editing On button&lt;br /&gt;
* Add the Tutor Time Tracking block to the page&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The permissions added by this block allow teachers and editing teachers access to the block.  Administrators also have access to the block.&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;The make the block accessible to the teachers/tutors, the relevant users should have been added to the teacher/editingteacher system groups.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==To add a teacher to the system group==&lt;br /&gt;
* Click on the Moodle Menu  Users &amp;gt; Permissions &amp;gt; Assign System Roles&lt;br /&gt;
* Click on the system group (Teachers or Editing Teachers)&lt;br /&gt;
* Add the users to the system group&lt;br /&gt;
&lt;br /&gt;
==To set the block content==&lt;br /&gt;
The block contains three content elements: the title, the link text and the footer text.  These can be set by turning edit mode on and clicking on the configuration icon which will appear in the block in edit mode.&lt;br /&gt;
&lt;br /&gt;
=Usage=&lt;br /&gt;
&lt;br /&gt;
==Tutor Time Tracking Entries==&lt;br /&gt;
&lt;br /&gt;
* The Block provides access to a single page, block/timetrack/add.php (the Task entry page).&lt;br /&gt;
&lt;br /&gt;
[[Image:timetrackblock.jpg]]&lt;br /&gt;
&lt;br /&gt;
* The entry page contains 5 rows consisting of Users Name, Date, Task Allocation dropdown, Quantity input&lt;br /&gt;
* The user completes as many rows as they desire and submits them. &lt;br /&gt;
* Upon submit They are then presented with confirmation screen which allows them to cancel and return to the entry page, or confirm their entries and write them to the database.&lt;br /&gt;
* Some of the teacher tasks require a quantity entry.  If these quantities are not entered, the user will be asked to enter them prior to the confirmation screen  &lt;br /&gt;
* Some other teacher tasks do not require a quantity - these will default to a quantity of 1 and the user will go directly to the confirmation screen&lt;br /&gt;
[[Image:timetrack_entryscreenerror.jpg]] &lt;br /&gt;
* After the user confirms the entries, the value totals are calculated, and the data is written to the database, the user will be returned to add.php and a success message displayed.&lt;br /&gt;
&lt;br /&gt;
==Tutor Time Tracking Reports==&lt;br /&gt;
&lt;br /&gt;
* The Time Tracking reports are accessed through add.php. add.php contains a link to view.php.&lt;br /&gt;
* The time tracking report page have two date selection points, the start of the report period and the end of the report period.&lt;br /&gt;
* Once a date range has been selected, pressing the Find Tracking Entries button will produce the report on screen.&lt;br /&gt;
* The report contains the teacher&#039;s name, date, task allocation, quantity, rate for the task, total&lt;br /&gt;
* A button titled &#039;Export to Excel&#039; is located at the bottom of the report.  This will offer a CSV file for download.&lt;br /&gt;
* The CSV file contains the same data that is visible on screen, with one addition column containing the teacher&#039;s name.&lt;br /&gt;
&lt;br /&gt;
[[Image:timetrack_reportscreen.jpg]]&lt;br /&gt;
&lt;br /&gt;
=Test cases=&lt;br /&gt;
==Admin data entry==&lt;br /&gt;
* Log in as admin&lt;br /&gt;
* Turn editing on&lt;br /&gt;
* Add the Tutor Time Tracking block&lt;br /&gt;
* Click on the link in the Tutor Time Tracking Block&lt;br /&gt;
* Select task allocations, from 0 allocations to 5&lt;br /&gt;
* Enter integer quantities&lt;br /&gt;
* Some quantities must be entered for some (currently Assignments and Special Event) task allocations&lt;br /&gt;
* Click Submit times&lt;br /&gt;
&lt;br /&gt;
==Admin report==&lt;br /&gt;
* Log in as admin&lt;br /&gt;
* Use the steps above to add the block if it has not already been added&lt;br /&gt;
* Click on the link in the block&lt;br /&gt;
* Click on the link &#039;View Time Tracking History&#039;&lt;br /&gt;
* Select a day, month and year for the start of the report period&lt;br /&gt;
* Select a day, month and year for the end of the report period&lt;br /&gt;
* Select a tutor from the dropdown list (if any).  This will default to the current user, and will only list users who have entered time tracking data. Only admin users should see this dropdown selection of tutors, the tutors themselves will only see their own name.&lt;br /&gt;
* Click on the button titled &#039;Find tracking entries&#039;&lt;br /&gt;
* At the bottom of the report (if any) click on the button titled &#039;Export to Excel&#039;&lt;br /&gt;
* A CSV file should be offered for download containing the report data, plus an additional column (col 1) containing the user&#039;s name&lt;br /&gt;
&lt;br /&gt;
==Teacher with a system role data entry and report==&lt;br /&gt;
* Log in as a teacher (any user assigned the system role of &#039;Teacher&#039; or &#039;Editing Teacher&#039; : Users &amp;gt; Permissions &amp;gt; Assign system roles)&lt;br /&gt;
* Repeat the steps above to enter Tutor Time Tracking Data and generate reports&lt;br /&gt;
* The Block should function in the same way for Teachers as it does for admins, with the exception that teachers can only view their own report and cannot select a different user&#039;s report&lt;br /&gt;
&lt;br /&gt;
==Teacher WITHOUT a system role data entry and report ==&lt;br /&gt;
* Log in as a teacher who has not been assign a system role, but has been assign the role of &#039;Teach&#039; or &#039;Editing Teacher&#039; in a single course&lt;br /&gt;
* Repeat the steps above (Admin Report) to enter Tutor Time Tracking Data and generate reports&lt;br /&gt;
* The Block should function in the same way for Teachers as it does for admins, with the exception that teachers can only view their own report and cannot select a different user&#039;s report&lt;br /&gt;
&lt;br /&gt;
==Student==&lt;br /&gt;
* Log in as a student&lt;br /&gt;
* The Tutor Time Tracking block should not be displayed&lt;br /&gt;
* A student should not be able to access:&lt;br /&gt;
**/blocks/timetrack/add.php&lt;br /&gt;
**/blocks/timetrack/view.php&lt;br /&gt;
**/blocks/timetrack/excel.php&lt;br /&gt;
&lt;br /&gt;
=Known issues and TODO=&lt;br /&gt;
* Download excel data as the administrator.  The current setup may be sufficient (the admin can select a tutor), but they may want to download data across selected multiple teachers, or all data for all tutors.&lt;br /&gt;
* Once data is submitted and confirmed, the tutor is returned to the data entry page.  They may need to be redirected to the report, or the moodle homepage, or the course homepage.&lt;br /&gt;
* Once data is submitted, it is written to the database after the tutor clicks the &#039;confirm submission&#039; button.  This may be unclear; instructions could be entered to make this clearer and save the loss of data.&lt;br /&gt;
* Very high quantity values (9999999999999999999999999) will hit the system upper limited and become (9223372036854775807).  Sane max values should be enforced.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Contributed code]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Fitxer:timetrack_reportscreen.jpg&amp;diff=80586</id>
		<title>Fitxer:timetrack reportscreen.jpg</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Fitxer:timetrack_reportscreen.jpg&amp;diff=80586"/>
		<updated>2011-01-18T10:25:56Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Fitxer:timetrack_entryscreenerror.jpg&amp;diff=80585</id>
		<title>Fitxer:timetrack entryscreenerror.jpg</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Fitxer:timetrack_entryscreenerror.jpg&amp;diff=80585"/>
		<updated>2011-01-18T10:25:29Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Fitxer:timetrackblock.jpg&amp;diff=80584</id>
		<title>Fitxer:timetrackblock.jpg</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Fitxer:timetrackblock.jpg&amp;diff=80584"/>
		<updated>2011-01-18T10:24:15Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
	<entry>
		<id>https://docs.moodle.org/2x/ca/index.php?title=Timetrack_block&amp;diff=80583</id>
		<title>Timetrack block</title>
		<link rel="alternate" type="text/html" href="https://docs.moodle.org/2x/ca/index.php?title=Timetrack_block&amp;diff=80583"/>
		<updated>2011-01-18T10:23:19Z</updated>

		<summary type="html">&lt;p&gt;Tmuras: New page: =Introduction= The Timetrack Block allows Admin and Teacher users to log entries of activities undertaken, such as Tutorials, Assignment marking, to the database. The date, task, quantity ...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
The Timetrack Block allows Admin and Teacher users to log entries of activities undertaken, such as Tutorials, Assignment marking, to the database. The date, task, quantity and pre-defined payment value will be logged.&lt;br /&gt;
&lt;br /&gt;
The Block also allows reporting on the values logged, filtered by a date range. This report can be exported to CSV, &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Installation=&lt;br /&gt;
* Extract and upload code to the blocks/ directory&lt;br /&gt;
* Log in to Moodle as the administrator and visit the Notifications page&lt;br /&gt;
* timetrack and timetrack_options tables will be created&lt;br /&gt;
* Permissions will be created which provide system roles of teachers and editing teachers with access&lt;br /&gt;
* If the timetrack_options table is empty it will be populated with some values&lt;br /&gt;
* Click the Turn Editing On button&lt;br /&gt;
* Add the Tutor Time Tracking block to the page&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;The permissions added by this block allow teachers and editing teachers access to the block.  Administrators also have access to the block.&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;The make the block accessible to the teachers/tutors, the relevant users should have been added to the teacher/editingteacher system groups.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
==To add a teacher to the system group==&lt;br /&gt;
* Click on the Moodle Menu  Users &amp;gt; Permissions &amp;gt; Assign System Roles&lt;br /&gt;
* Click on the system group (Teachers or Editing Teachers)&lt;br /&gt;
* Add the users to the system group&lt;br /&gt;
&lt;br /&gt;
==To set the block content==&lt;br /&gt;
The block contains three content elements: the title, the link text and the footer text.  These can be set by turning edit mode on and clicking on the configuration icon which will appear in the block in edit mode.&lt;br /&gt;
&lt;br /&gt;
=Usage=&lt;br /&gt;
&lt;br /&gt;
==Tutor Time Tracking Entries==&lt;br /&gt;
&lt;br /&gt;
* The Block provides access to a single page, block/timetrack/add.php (the Task entry page).&lt;br /&gt;
&lt;br /&gt;
[[Image:timetrackblock.jpg]]&lt;br /&gt;
&lt;br /&gt;
* The entry page contains 5 rows consisting of Users Name, Date, Task Allocation dropdown, Quantity input&lt;br /&gt;
* The user completes as many rows as they desire and submits them. &lt;br /&gt;
* Upon submit They are then presented with confirmation screen which allows them to cancel and return to the entry page, or confirm their entries and write them to the database.&lt;br /&gt;
* Some of the teacher tasks require a quantity entry.  If these quantities are not entered, the user will be asked to enter them prior to the confirmation screen  &lt;br /&gt;
* Some other teacher tasks do not require a quantity - these will default to a quantity of 1 and the user will go directly to the confirmation screen&lt;br /&gt;
[[Image:timetrack_entryscreenerror.jpg]] &lt;br /&gt;
* After the user confirms the entries, the value totals are calculated, and the data is written to the database, the user will be returned to add.php and a success message displayed.&lt;br /&gt;
&lt;br /&gt;
==Tutor Time Tracking Reports==&lt;br /&gt;
&lt;br /&gt;
* The Time Tracking reports are accessed through add.php. add.php contains a link to view.php.&lt;br /&gt;
* The time tracking report page have two date selection points, the start of the report period and the end of the report period.&lt;br /&gt;
* Once a date range has been selected, pressing the Find Tracking Entries button will produce the report on screen.&lt;br /&gt;
* The report contains the teacher&#039;s name, date, task allocation, quantity, rate for the task, total&lt;br /&gt;
* A button titled &#039;Export to Excel&#039; is located at the bottom of the report.  This will offer a CSV file for download.&lt;br /&gt;
* The CSV file contains the same data that is visible on screen, with one addition column containing the teacher&#039;s name.&lt;br /&gt;
&lt;br /&gt;
[[Image:timetrack_reportscreen.jpg]]&lt;br /&gt;
&lt;br /&gt;
==Admin data entry==&lt;br /&gt;
* Log in as admin&lt;br /&gt;
* Turn editing on&lt;br /&gt;
* Add the Tutor Time Tracking block&lt;br /&gt;
* Click on the link in the Tutor Time Tracking Block&lt;br /&gt;
* Select task allocations, from 0 allocations to 5&lt;br /&gt;
* Enter integer quantities&lt;br /&gt;
* Some quantities must be entered for some (currently Assignments and Special Event) task allocations&lt;br /&gt;
* Click Submit times&lt;br /&gt;
&lt;br /&gt;
==Admin report==&lt;br /&gt;
* Log in as admin&lt;br /&gt;
* Use the steps above to add the block if it has not already been added&lt;br /&gt;
* Click on the link in the block&lt;br /&gt;
* Click on the link &#039;View Time Tracking History&#039;&lt;br /&gt;
* Select a day, month and year for the start of the report period&lt;br /&gt;
* Select a day, month and year for the end of the report period&lt;br /&gt;
* Select a tutor from the dropdown list (if any).  This will default to the current user, and will only list users who have entered time tracking data. Only admin users should see this dropdown selection of tutors, the tutors themselves will only see their own name.&lt;br /&gt;
* Click on the button titled &#039;Find tracking entries&#039;&lt;br /&gt;
* At the bottom of the report (if any) click on the button titled &#039;Export to Excel&#039;&lt;br /&gt;
* A CSV file should be offered for download containing the report data, plus an additional column (col 1) containing the user&#039;s name&lt;br /&gt;
&lt;br /&gt;
==Teacher with a system role data entry and report==&lt;br /&gt;
* Log in as a teacher (any user assigned the system role of &#039;Teacher&#039; or &#039;Editing Teacher&#039; : Users &amp;gt; Permissions &amp;gt; Assign system roles)&lt;br /&gt;
* Repeat the steps above to enter Tutor Time Tracking Data and generate reports&lt;br /&gt;
* The Block should function in the same way for Teachers as it does for admins, with the exception that teachers can only view their own report and cannot select a different user&#039;s report&lt;br /&gt;
&lt;br /&gt;
==Teacher WITHOUT a system role data entry and report ==&lt;br /&gt;
* Log in as a teacher who has not been assign a system role, but has been assign the role of &#039;Teach&#039; or &#039;Editing Teacher&#039; in a single course&lt;br /&gt;
* Repeat the steps above (Admin Report) to enter Tutor Time Tracking Data and generate reports&lt;br /&gt;
* The Block should function in the same way for Teachers as it does for admins, with the exception that teachers can only view their own report and cannot select a different user&#039;s report&lt;br /&gt;
&lt;br /&gt;
==Student==&lt;br /&gt;
* Log in as a student&lt;br /&gt;
* The Tutor Time Tracking block should not be displayed&lt;br /&gt;
* A student should not be able to access:&lt;br /&gt;
**/blocks/timetrack/add.php&lt;br /&gt;
**/blocks/timetrack/view.php&lt;br /&gt;
**/blocks/timetrack/excel.php&lt;br /&gt;
&lt;br /&gt;
=Known issues and TODO=&lt;br /&gt;
* Download excel data as the administrator.  The current setup may be sufficient (the admin can select a tutor), but they may want to download data across selected multiple teachers, or all data for all tutors.&lt;br /&gt;
* Once data is submitted and confirmed, the tutor is returned to the data entry page.  They may need to be redirected to the report, or the moodle homepage, or the course homepage.&lt;br /&gt;
* Once data is submitted, it is written to the database after the tutor clicks the &#039;confirm submission&#039; button.  This may be unclear; instructions could be entered to make this clearer and save the loss of data.&lt;br /&gt;
* Very high quantity values (9999999999999999999999999) will hit the system upper limited and become (9223372036854775807).  Sane max values should be enforced.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Contributed code]]&lt;/div&gt;</summary>
		<author><name>Tmuras</name></author>
	</entry>
</feed>