MoodleDocs - User contributions [en]

FontAwesome filter

2017-06-11T11:23:40Z

ColinFraser:

{{Filters}}
This is a [[:Category:Contributed_code|contributed (third party)]] filter for Moodle written by Julian (Moodleman) Ridden and shared on Moodle.org

Font Awesome provides sites with scalable vector icons that can instantly be customized — size, color, drop shadow, and anything that can be done with the power of CSS. Font Awesome is fully open source and is GPL compatible. No attribution is required when using the fonts although the project does say it is appreciated.

This filter makes it easy to add FontAwesome icons to course content in any FontAwesome enabled moodle site. Please be sure to target any questions related to this filter in the [https://moodle.org/mod/forum/discuss.php?d=240159 Filter's forums] at moodle.org and bugs to the [[Tracker|Moodle Tracker]]

==Filter Objectives==
The aim of this filter was to provide an easy and functional way for content creators to easily add FontAwesome icons anywhere in course content. If using the recommended method provide by FontAwesome which involves creating custom classes you will find that the text editor strips these out automatically as unrecognised/bad code. This filter provides another mechanism to add FontAwesome icons that won't be stripped out by the editor.

==Enabling FontAwesome in Moodle==
FontAwesom icon's will not work just by adding this filter to your Moodle. The filter just facilitates adding them to content. You will need to first ensure your site has the FontAwesome font enabled before you can use this filter. You can get FontAwesome running one of two ways.

==Install a FontAwesome enabled theme==

Some Moodle themes are now coming with FontAwesome already enabled. To find out if they do just read the information found about them in the Modules and Plugins Database.

One such theme that already has FontAwesome contained within is the [[https://moodle.org/plugins/view.php?plugin=theme_essential Essential Theme]] by Julian Ridden.

==Load FontAwesome via CDN==
A content delivery network or content distribution network (CDN) is a large distributed system of servers deployed in multiple data centers across the Internet. The goal of a CDN is to serve content to end-users with high availability and high performance. You can pull FontAwesome into your site using any theme by adding a single line to your Admin settings. This line will connect to a dedicated CDN to reliably load FontAwesome into your moodle site.

To add the CDN to your Moodle you need to add the following line to your '''"Additional HTML"''' settings in Site Administration. You can find this located under the "Appearance" menu.

[[File:additionalhtml.png]]

Once you are in the "Additional HTML" settings we need to add the following line to the '''"Within HEAD"''' section. This will then load the FontAwesome as part of every page load.

<link href="//netdna.bootstrapcdn.com/font-awesome/3.2.1/css/font-awesome.min.css" rel="stylesheet">

It should look like the image below. Once done you are now ready to use the FontAwesome filter.

[[File:fontawesomecdn.png]]

==Adding an icon==

Adding an icon to anywhere in your course that you wish is now a simple process. The hardest part is finding the icon you wish to use. To browse the full list of over 360 icons please visit [[http://fontawesome.io/icons/ this link]]. Once you have found the icon you are after you just have to surround it with a set of square brackets. e.g.:

[fa-retro-camera]

If you have typed in the icon name correctly you will see the icon appear once you have hit save.

==Configurable Options==

If you wish to make the icon larger you can use a multiplier. e.g.:

[fa-camera-retro fa-2x] or [fa-camera-retro fa-4x]

If you wish to rotate the icon you can specify how many degrees clockwise. e.g.:

[fa-camera-retro fa-rotate-90]

You can also flip an icon horizontally or vertically. e.g.:

[fa-camera-retro fa-flip-horizontal] or [fa-camera-retro fa-flip-vertical]

You can mute the colour to a dull grey. e.g.:

[fa-camera-retro fa-muted]

You can "pull" the icon to the left or right. If it is "pulled" to the left text will wrap to the right. e.g.:

[fa-camera-retro pull-left]

===Advanced Tip===

All the settings above can be mixed and matched. For example if I was to type in:

[fa-quote-left fa-4x pull-left fa-muted]

Use a few of the new styles together, and you've got easy pull quotes or a great introductory article image. Or spinning icons for loading and refreshing content. Or fun big icons in multi-line buttons. You can combine all of them in any combination to get lots of new possibilities.

You would generate:

[[File:fontawesome_advancedtip.png]]

==Download link==
This filter is only available for Moodle 2.5 and above.
You can download the filter from https://moodle.org/plugins/view.php?plugin=filter_fontawesome

==See also==
*[https://moodle.org/plugins/view.php?plugin=filter_fontawesome FontAwesome Filter]'s Plugin database listing
*[https://github.com/moodleman/moodle-filter_fontawesome/archive/FontAwesomeFilter_1.0.zip Download latest version]
*[https://github.com/moodleman/moodle-filter_fontawesome Browse GIT]
*[https://moodle.org/mod/forum/discuss.php?d=240159#p1052928 Discussion in English] in the Forum
*[http://features.demo.moodle.com.au/ Demo site]
*[http://fontawesome.io/ FontAwesome Official website]

[[Category:Contributed code]]
[[es:Filtro FontAwesome]]

Talk:Security FAQ

2016-09-21T10:56:13Z

ColinFraser:

Not sure how long it has been (at least Moodle 2.5) since it was changed however to enable ReCAPTCHA you need to go to:

Site administration > Plugins > Authentication > Manage authentication

... not ...

Site Administration > Users > Authentication > Manage authentication.

Please update the Security FAQ as there is no Authentication under Users.

Best regards,

Michael Milette

:Thanks Michael, I have amended the text. --[[User:Helen Foster|Helen Foster]] ([[User talk:Helen Foster|talk]]) 14:53, 4 February 2014 (WST)

Hi,
Can you please add [[es:Seguridad FAQ]] to this protected page for the English Moodle 3.0, 2.x and 1.9 docs? Thanks in advance. [[User:German Valero|German Valero]] ([[User talk:German Valero|talk]])

:Thanks German, I have added the link to the 2.8 - 3.0 English docs. --[[User:Helen Foster|Helen Foster]] ([[User talk:Helen Foster|talk]]) 22:39, 17 November 2015 (AWST)
:Thanks Helen. That was fast :) [[User:German Valero|German Valero]] ([[User talk:German Valero|talk]])

I understand that reCaptcha has been hacked as recently as April 2016. Not a big fan of using Captcha or reCaptcha, is there anything else that can be used to validate human/nonhuman identities? Something that is free and maybe not easy to hack? Also, bearing in mind the blind and visually impaired who have difficulty with reCaptcha, there has to be some discussion or some alternative. --[[User:Colin Fraser|Colin Fraser]] ([[User talk:Colin Fraser|talk]]) 17:06, 19 September 2016 (AWST)

A little digging and I ran across this article from Vision Australia on Effective alternatives to [https://www.visionaustralia.org/business-and-professionals/digital-access-consulting/resources/blog---accessibility-and-assistive-technology-blog/blog/accessibility-blog/2014/12/09/effective-alternatives-to-inaccessible-captchas inaccessible CAPTCHAS]. --[[User:Colin Fraser|Colin Fraser]] ([[User talk:Colin Fraser|talk]]) 19:54, 19 September 2016 (AWST)

:Hi Colin, if you've not done so already, I suggest you post on moodle.org about alternatives to Captcha and also make sure there is an issue for it in the tracker, since not many people watch pages in Moodle Docs. --[[User:Helen Foster|Helen Foster]] ([[User talk:Helen Foster|talk]]) 20:08, 19 September 2016 (AWST)

Yes, of course, I knew that...:) Doh!!--[[User:Colin Fraser|Colin Fraser]] ([[User talk:Colin Fraser|talk]]) 18:56, 21 September 2016 (AWST)

Talk:Security FAQ

2016-09-19T11:54:45Z

ColinFraser:

Talk:Security FAQ

2016-09-19T09:11:11Z

ColinFraser:

Talk:Security FAQ

2016-09-19T09:08:09Z

ColinFraser:

Talk:Security FAQ

2016-09-19T09:07:06Z

ColinFraser:

Help:Editing

2016-04-07T11:25:45Z

ColinFraser:

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

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

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

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

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

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

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

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

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

== Formatting ==

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

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

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

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

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

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

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

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

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

=== Preserving formatting ===

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

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

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

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

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

The HTML edit tool bar has a nowiki icon.

===PHP syntax higlighting===

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

===Tables===

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

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

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

| <pre><nowiki>A table:

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

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

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

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

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

(from mediaWiki Help pages)

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

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

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

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

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

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

==Embedding videos==

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

== Links and Anchors ==

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

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

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

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

=== External links ===

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

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

===Tracker links===

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

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

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

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

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

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

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

===Inter-language links===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:MoodleDocs]]

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

Installation FAQ

2016-04-07T11:20:11Z

ColinFraser: /* How to enable and check PHP error logs */

{{Installing Moodle}}
== System information needed for Installation problems forum ==
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Consider providing some or all of the following:
* Server Operating System name (version also if possible):
* PHP version (e.g. PHP 5.4.4)
* Database server type and version (e.g. MySQL 5.5.18)
* Browser and version (e.g. Firefox, IE8):
* Moodle version (e.g. 3.0):
* Moodle install type? (New/Upgrade):
* Moodle config.php attached (please remove passwords):
* Phpinfo attached?:

Make sure you provide a sensible description (never HELP! or URGENT!) and a full description of what you did and what happened. Copy and paste any error messages accurately in full. 'Nothing' is not a symptom, even a blank page is something!

[[#top|Top]]

==PHP - is it installed and what version do I have?==

Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:

<code php>
<?PHP phpinfo() ?>
</code>

If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.

[[#top|Top]]

==I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x==
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

[[#top|Top]]

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions ('''Windows Only''')
{| class="nicetable"
|-
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

[[#top|Top]]

==What & where are Moodle's configuration settings stored?==
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the [[Configuration file]] docs.
[[#top|Top]]

==Downloading previous releases of Moodle==
It is possible to download previous versions of Moodle that are not found on the [http://download.moodle.org Standard Moodle Download page]. There are zip and tgz compressed located at <nowiki>http://download.moodle.org/stable[version_number]</nowiki> (see links below).

{| style="width:75%; height:75px" border="0"
|-
| 2.0 Versions || [http://download.moodle.org/stable19 1.9 Versions] || [http://download.moodle.org/stable18 1.8 Versions]
|-
|[http://download.moodle.org/stable17 1.7 Versions] || [http://download.moodle.org/stable16 1.6 Versions] || [http://download.moodle.org/stable15/ 1.5 Versions]
|-
| [http://download.moodle.org/stable14 1.4 Versions] || [http://download.moodle.org/stable13 1.3 Versions] ||
|}

You can download previous releases by using wget, lynx or curl with this URL:
<nowiki>http://download.moodle.org/stable[version_number]</nowiki>.
:For example: to download Moodle version 1.5, use <nowiki>http://download.moodle.org/stable15</nowiki>. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki>
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac packages], use either of these URLs (depending on whether you need the Intel or PPC package):
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki>
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki>

[[#top|Top]]

== How to enable and check PHP error logs==
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[dev:PHP error logs|PHP_error_logs]].

== "Could not find a top level course" ==
If this appears immediately after you have attempted to install Moodle it almost certainly means that the installation did not complete. A complete installation will ask you for the administrator profile and to name the site just before it completes. Check your logs for errors. Then drop the database and start again. If you used the web-based installer try the command line one. Does your computer definitely have sufficient resource to run Moodle?

==Email copies are not being sent from my forums==

You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on. Please refer to the [[Cron|cron instructions]].

Tips:
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.
* Check your firewall or ask your network administrator. Many mail servers are heavily locked down and you may need permission to send mail through them.

[[#top|Top]]

==I can't log in - I just stay stuck on the login screen==

This may also apply if you are seeing “Your session has timed out. Please login again” or "A server error that affects your login session was detected. Please login again or restart your browser" and cannot log in.

The following are possible causes and actions you can take (in no particular order):

* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.
* Check that your hard disk is not full or if your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in.
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)
* Try deleting cookies on your computer and/or try another browser or another client computer
* In ''Settings > Site administration > Server > Session Handling'', try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser.
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values.
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations.
* Check config.php - it should NOT have any spaces/new lines at the end of code.
* You are using the correct username and password, yes?

If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it - see [[Administration FAQ]].

[[#top|Top]]

==I log in but the login link doesn't change. I am logged in and can navigate freely.==

Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.

[[#top|Top]]
==Uploaded files give "File not found"==

For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.

This indicates that slash arguments are not enabled on your web server. Please see [[Using slash arguments]] for details.

[[#top|Top]]

==Why are all my pages blank?==

Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (e.g.)

<code php>
$CFG->dirroot = "/var/www/moodle";
</code>

Another reason might be that PHP has not been configured to support MySQL (or whatever other database you are using). This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].

To determine if database support is your problem, insert this as the second line in your ''config.php'' file

<code php>
phpinfo();
</code>

then reload the web page. Examine the output closely to see if you chosen database is supported. If not, look for a package you are missing.

[[#top|Top]]

== Why is a particular page blank or incomplete? ==

*'''Check your web server log files!!'''
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.

*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".

*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.

*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion

==Installation hangs when setting-up database tables==
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there.

See [[Unexpected installation halts]] for more about solutions that involve:
*Checking for MySQL limits
*Checking the .htaccess files
*Code customizations issues
*Checking memory limit
*Upgrade incrementally
*Fix fopen function

[[#top|Top]]

==Why can't I upload a new image into my profile?==

If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:
*The permissions associated with the role you are using are preventing you from changing your profile picture.
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > PHP info'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.

If Moodle thinks GD is not installed, then you will need to '''install the GD library'''.
*On Unix you may need to re-compile PHP with arguments something like this:

./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars
--enable-versioning --with-zlib

* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:
extension=php_gd2.dll

:Windows users should see the [[Installing AMP|installation instructions]] for further help.

3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.

'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.

== Why doesn't my Moodle site display the time and date correctly? ==

Please check the timezone settings in settings in ''Administration > Site administration > Location > Location settings''.

== How do I uninstall Moodle?==

'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):
<pre>sql>DROP DATABASE moodle;</pre>
:In the above example replace 'moodle' with the name of the moodle database you created when installing.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:
*Open cmd.exe and navigate to this directory within your installation directory:
<pre>server/mysql/bin</pre>
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre>
*Enter your database password at the prompt (the default is "" [blank]).
*Enter "y" to confirm the database drop.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

==Migrating Moodle to a new site or server==
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the [[Search and replace tool]], your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.

[[#top|Top]]

==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php).
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].

[[#top|Top]]
==Maximum upload file size - how to change it?==
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].

If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server. [http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size NGINX] system administrators should also add client_max_body_size=XXX to the "http" section of their nginx main configuration file. ([https://rtcamp.com/tutorials/php/increase-file-upload-size-limit/#change-in-nginx-config see more info])

For more help see:
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]
*[[Installing_Moodle#Recheck_PHP_settings]]
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]
*[[Site_policies#Maximum_uploaded_file_size]]
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650

[[#top|Top]]

==Moodle claims PHP float handling is not compatible==

The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".

[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.

You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.

Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding
ini_set('precision', 14);
to your config.php file, and report your success in MDL-18253.

==When upgrading Moodle claims my MySQL database is not UTF8 when I'm sure it is==

The UTF-8 detection for MySQL databases was finally fixed in Moodle 2.5, some incorrectly configured databases were previously reported as compatible.

Please note it is not enough to alter the charset and collation of the database, you must fix each text column in each database table!

Before going any further make sure you understand the difference between character encoding (how text is stored) and collations (the rules for comparing text strings). Collation problems will never cause this error but have a bunch of problems of their own.

See [[Converting your MySQL database to UTF8]]

[[#top|Top]]

== How do I run multiple instances of Moodle without duplicating base code? ==

See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].

== What is FreeTDS and how can I use it in my installation? ==
[[Installing MSSQL for PHP|FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.

== How do I install a plugin? ==

Please see [[Installing plugins]].

==I can't enable a plugin on the Plugins overview page because the icon is not clickable==
The open and closed eye icon on the Plugins overview page is simply there to show whether or not a plugin is enabled. You can't edit plugins from this screen. If you wish to enable a plugin, to to the appropriate page for managing the type of plugin you need, for instance ''Settings>Site administration>Plugins>Repositories>Manage repositories'' or ''Settings>Site administration>Plugins>Activity modules>Manage activities.''

== See also ==

* [[Errors FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]

Installing Moodle in a shared web hosting environment:
* [[Finding_and_Selecting_A_Web_Host|Finding and Selecting a web host]]
* [[Installing_Moodle_on_SmarterASP.NET|Installing Moodle on SmarterASP.NET web hosting]]

[[Category:FAQ]]

[[es:FAQ Instalación]]
[[fr:FAQ d'installation]]
[[ja:インストールFAQ]]
[[de:Installation FAQ]]

Errors FAQ

2015-12-27T22:15:48Z

ColinFraser:

{{Managing a Moodle site}}==Error: database connection failed==

If you get errors like "database connection failed" or "could not connect to the database you specified", here are some possible reasons and some possible solutions.

* Your '''database server''' isn't installed or running. To check this for MySQL try typing the following command line
$telnet database_host_name 3306
:You should get a cryptic response which includes the version number of the MySQL server.
* If you are attempting to run '''two instances of Moodle on different ports''', use the ip address of the host (not localhost) in the $CFG->dbhost setting, e.g. $CFG->dbhost = 127.0.0.1:3308.
* You don't have the '''PHP mysql or postgresql extensions''' installed (please refer to FAQ re. whether PHP is installed).
* You haven't created a '''Moodle database and assigned a user''' with the correct privileges to access it.
* The '''Moodle database settings''' are incorrect. The database name, database user or database user password in your Moodle configuration file ''config.php'' are incorrect. Use phpMyAdmin to set up and check your MySQL installation.
* Check that there are '''no apostrophes or non-alphabetic letters''' in your MySQL username or password.
* You are using MySQL version 4.1 or higher but the PHP MySQL extension is pre-4.1 (check in your phpinfo output). In this case the '''default password hashing algorithm''' is incompatible with that available in the PHP mysql extension versions 4.x.x. Use these MySQL commands to change the passwords to the old format:

mysql>SET PASSWORD FOR 'root'@'localhost' = OLD_PASSWORD('password');
mysql>SET PASSWORD FOR 'moodleuser'@'localhost' = OLD_PASSWORD('password');

:Also, consider upgrading your PHP MySQL extension. See [http://dev.mysql.com/doc/mysql/en/old-client.html this MySQL document] for further information on how to deal with this problem.
* You are using Fedora core 3 or some other Linux system with '''SELinux installed''' and enabled. See the following URL for information on how to disable SELinux: http://fedora.redhat.com/projects/selinux/ If you don't want to disable SELinux, you have to allow httpd process to create network connections:

setsebool httpd_can_network_connect true

* Mac OSX users -- if you are running MySQL on a Mac OSX, try changing '''$CFG->dbhost''' from 'localhost' to '127.0.0.1'
'''See also''': MySQL page on [http://dev.mysql.com/doc/refman/5.0/en/common-errors.html common errors] which lists several possible scenarios for connection failure, with advice on how to fix the problems.

==I can't log in with message "Please verify that the current setting of session.save_path is correct" ==

This error occurs when PHP is having problems saving its session files. You may also see these other error messages displayed on the screen or in your log files:

Warning: Unknown: open(some-path/sessions/sess_acbf942a7399db3489ffa910e35d5242, O_RDWR)
failed: Permission denied (13) in Unknown on line 0

Warning: Unknown(): open(some-path/sessions/sess_acbf942a7399db3489ffa910e35d5242, O_RDWR)
failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current
setting of session.save_path is correct (some-path/sessions) in Unknown on line 0

To temporarily bypass these errors, '''use database sessions''' by editing your [[Configuration_file | moodle configuration file]] and adding this line:

$CFG->dbsessions = true;

Database sessions may overload your mysql database and are not ideal in a shared hosting environment, so if this solves the problem, you can start fixing the problem as follows:
* Check '''access rights'''. The session.save_path should be accessible by the apache user. Try this command:

chown -R apache:apache some-path/sessions

:This assumes that 'apache' is the name of the user your webserver runs under - it could also be 'nobody'.
* Check the '''permissions''' to the directory that PHP is trying to save to (session.save_path = some-path/sessions). Set the permissions initially to 0777 (everyone read, write, execute) with this command:

chmod -R 0777 some-path/sessions

:If this fixes the problem, reduce the permissions (700 is recommended).

'''See also''': Session problems can be specific to your server environment. As an example, see [http://moodle.org/mod/forum/discuss.php?d=55925#254596 this forum discussion] about session problems with Lycos hosting.

==Error: A server error that affects your login session was detected==
If restarting your browser and logging in again to your Moodle site does not work, see the Using Moodle [http://moodle.org/mod/forum/discuss.php?d=73716 forum discussion about this error message].

If this was received at a Moodle.org site, the site could be in the process of updating. Please try the suggestion and/or wait and try it again. Or report it in [[Tracker]].

==Error: Failed opening required '/web/moodle/lib/setup.php'==

In your ''config.php'', the setting that you use for the dirroot variable must be the complete path from the root of your server's hard drive.

Sometimes people only use the path from their home directory, or relative to the root of the web server directory.

==My pages show fatal errors such as : Parse error, call to undefined function: get_string()==

If you see errors like:

Parse error: parse error, unexpected T_VARIABLE in /path/to/moodle/config.php on line 94
Fatal error: Call to undefined function: get_string() in /path/to/moodle/mod/resource/lib.php
on line 11

then you have probably left out a semi-colon or closing quote from a line in ''config.php'' (previous to line 94).

Another possibility is that you edited ''config.php'' in a program like Word and saved it as a HTML web page, instead of using a plain text editor like Notepad.

Another thing to check, particularly if you are using additional plugins, is whether any of the php scripts use short open tags (<? ?>) instead of proper ones (<?php ?>). Short tags are bad for various reasons, so first contact the author of that extension to tell them about the problem. Then either replace short tags with conventional ones, or set this line in php.ini:

short_open_tag = On

You should never find short tags in core moodle code. If you do, please file a bug in the tracker.

==When I go to the admin page, I get told to make dirroot blank!==

If you see errors like this:

Please fix your settings in config.php:
You have: $CFG->dirroot = "/home/users/fred/public_html/moodle";
but it should be: $CFG->dirroot = "";

then you have encountered a small bug that occurs on some servers. The problem is with the error-checking mechanism, not with your actual path. To fix it, find this line (line 66) in the file ''admin/index.php'':

if ($dirroot != $CFG->dirroot) {

and change it to this:

if (!empty($dirroot) and $dirroot != $CFG->dirroot) {

==Why do I keep getting error messages about "headers already sent"?==

If you see errors like this:

Warning: Cannot add header information - headers already sent by
(output started at /webs/moodle/config.php:87) in /webs/moodle/lib/moodlelib.php
on line 1322

Warning: Cannot add header information - headers already sent by
(output started at /webs/moodle/config.php:87) in /webs/moodle/lib/moodlelib.php
on line 1323

Warning: Cannot add header information - headers already sent by
(output started at /webs/moodle/config.php:87) in /webs/moodle/login/index.php
on line 54

you have blank lines or spaces after the final <code>?></code> in your ''config.php'' file. Sometimes text editors add these - for example Notepad on Windows - so you may have to try a different text editor to remove these spaces or blank lines completely.

==Error: "500:Internal Server Error"==
There are several possible causes for this error. It is a good idea to start by checking your web server error log which should have a more comprehensive explanation. However, here are some known possibilities....

1. '''Syntax error''': There is a syntax error in your .htaccess or httpd.conf files. The way in which directives are written [http://httpd.apache.org/docs/1.3/howto/htaccess.html#when differs] depending on which file you are using. You can test for configuration errors in your Apache files using the command:
#apachectl configtest

2. '''PHPsuexec''': Your server does not support .htaccess files, especially if it is running PHPsuexec, which is an Apache module used for increasing the security of a site on a hosted system. In this situation:

- you may also see a 403: Forbidden error.

- the webserver executes under your own username and all files have a maximum permissions level of 755. Check that this is set for your Moodle directory in your control panel or (if you have access to the shell) use this command:
#chmod -R 755 moodle

- use a PHP.INI file instead of a .htaccess in the directory where the Moodle PHP script is being executed. For example: if you are receiving a memory exhausted error when your server is executing the file moodle/admin/cron.php, use a PHP.INI file to change your memory_limit and copy it to the moodle/admin directory. Remember that for PHP4, PHP.INI files are per-directory, so you'll need to copy it to each sub-directory. If you are using PHP5 or higher on a shared host, check with your host on whether they support custom PHP.INI files, and how to create them. The syntax used in a PHP.INI file is different from a .htaccess file and you need to take out php_value/php_flag at the beginning of the line and use an equals sign to assign a value, e.g.
php_value memory_limit 128M <-- .htaccess
memory_limit = 128M <-- php.ini equivalent

3. '''Incompatible directive''': You may have a directive in your .htaccess or httpd.conf files which are not compatible with your web server version. Check your webserver documentation.

==Error "403: Forbidden" ==

Check your webserver configuration. See also the section above "500:Internal Server Error".

==Fatal error allowed memory size exhausted. How do I increase my php memory limit?==
You will sometimes see an error message something like this:
Fatal error: Allowed memory size of 67108864 bytes exhausted
(tried to allocate xx bytes) in /var/www/moodle/yyyy.php
This error means that the php memory_limit value is not enough for the php script. The memory_limit value is the "allowed memory size" - 64M in the example above (67108864 bytes / 1024 = 65536 KB. 65536 KB / 1024 = 64 MB). You will need to increase the php memory_limit value until this message is not shown anymore. There are two methods of doing this.
*On a hosted installation you should ask your host's support how to do this. However, many allow .htaccess files. If yours does, add the following line to your .htaccess file (or create one in the moodle directory if it does not already exist):
php_value memory_limit <value>M
Example: php_value memory_limit 40M
*If you have your own server with shell access, edit your php.ini file (make sure it's the correct one by checking in your phpinfo output) as follows:
memory_limit <value>M
Example: memory_limit 40M
* For later versions of Moodle you could be looking at figures in the region of 512M for all functions to work properly (backup and restore are particularly memory hungry). It is sensible to monitor the memory usage on your server if using these large settings.
Remember that you need to restart your web server to make changes to php.ini effective. An alternative is to disable the memory_limit by using the command ''memory_limit 0''.

==Error: "Your session has timed out. Please login again." or "The page isn't redirecting properly" or "This webpage has a redirect loop"==

Please do one/all of the following:
* Try deleting cookies manually from your browser and close it down, then access your site again. Sometimes this clears up the problem.
* Check that your ''moodledata/sessions'' directory has write permissions. When you access Moodle a new file should be created there.
* If you are running two versions of Moodle on the same computer, set a cookie prefix in ''Administration > Server > [[Session handling]]''.

The discussion [http://moodle.org/mod/forum/discuss.php?d=46580 Your session has timed out. Please login again] has further suggested solutions:
* Browse to: http://yoursite/subdir/admin/purgecaches.php , it should prompt you to login first and then redirect to a page that has a button to purge all caches.
* If you can access your server files, go to the 'moodledata' folder, go to the 'cache' folder inside and erase all the contents there (usually only two files). Moodle will delete the frozen session with the redirect loop and Moodle will work again.

==Fatal error: Maximum execution time of 30 seconds exceeded in...(when installing)==
* Your computer is taking too much time to execute the installation scripts.
* Press F5 (refresh) until it finishes the installation process.

==How can I fix just one bug, without upgrading my whole site?==

Suppose:
* You are running an older Moodle version.
* You are experiencing a particular bug.
* You have searched in the [http://tracker.moodle.org/ tracker], and found that your problem is MDL-abc, and that it has been fixed in the latest version.
* For some reason, you cannot upgrade your whole site, even though the latest version probably has security fixes.

Then, how can you get the fix for just this one bug, without upgrading your whole site? Well, if you are prepared to manually patch the code, you can probably get this information from the tracker. Please see [[How to fix just one bug without upgrading|this guide]].

==error/moodle/cannot finish ui if not setting ui==
An occasionally reported intermittent error that may or may not be related to the php ini value of max_execution_time. So far proven intractable, as it has not been found to have a consistent cause and cannot be consistently duplicated.

==See also==

* [[:Category:Error]] for a list of Moodle error pages.

[[Category:FAQ]]
[[Category:Error]]

[[es:Errores FAQ]]

Algebra filter

2014-01-04T01:53:45Z

ColinFraser:

{{Improve}}
{{Filters}}
'''NOTE:''' While the Algebra filter is included in later versions of Moodle, a more effective way of writing mathematical notation is by using the [[TeX notation filter]]. TeX is more cross platform and appears far more flexible, than the Algebra Filter.

==Generally==

Moodle has an "algebra filter" which can display mathematical expressions as if they were typeset. The filter is included in the standard Moodle packages but the administrator must activate it before you can use it.

'''NOTE:''' the use of the algebra filter '''REQUIRES''' that the Moodle Tex filter also be working as the algebra filter simply parses math expressions in one syntax and then converts the expressions to LaTex expressions for the Tex filter to render and display. The filter uses a borrowed perl script

The filter (see http://cvs.moodle.org/moodle/filter/algebra/ ) uses algebra2tex.pl, a perl script (and its associated perl module, AlgParser.pm) to parse text expressions delimited by double@ signs as tokens (though the tokens employed can be tweaked manually.)

NOTE perl script REQUIRES '''Perl'''. This is no problem with most Linux servers, but may be the cause for malfunctions in the Win world like broken connections. Exceptions / failures are NOT catched and reported via this Moodle filter.
If there is no Perl available, activate Moodle Tex (as mentioned above) and use the JAVA Math Formula Editor. It is available after activating Tex. Minor corrections in the resulting Tex code dont need deeper digging in Tex fundamentals.

While many have argued that the algebra filter is easy to use, there is apparently no Moodle reference on its "grammar" or "syntax". Research in to Webworks produced these two links for using webworks text expressions (the first one is arguably replaced by the second):

* http://webwork.math.rochester.edu/docs/docs/pglanguage/availableFunctions.html (no longer available.)
* http://webwork.maa.org/wiki/Mathematical_notation_recognized_by_WeBWorK (the connection is not clear.)

See http://moodle.org/mod/forum/discuss.php?d=126522&parent=554632.

There is a discussion of Algebra filter syntax at http://moodle.org/mod/forum/discuss.php?d=5402 offered by [http://moodle.org/user/view.php?id=2466&course=5 Zbigniew Fiedorowicz].

It appears that as of Moodle.org moving to Moodle 2 (late 2010) the Algebra filter in the forums is no longer working. It also appears that the Algebra filter does not work in Moodle Docs (which is not Moodle code, but MediaWiki, which I don't believe has a ready filter based on algebra2tex.pl.

==Troubleshooting==
The file algebradebug.php is provided in the filter folder for the purpose of debugging. Problems may arise comes from the first tags in algebradebug.php

define('NO_MOODLE_COOKIES', true); // Because it interferes with caching

You can delete the line or set it to false.

[[Category:Mathematics]]

[[fr:Filtre Algebra]]
[[es:Filtro de álgebra]]

Talk:Algebra filter

2014-01-04T01:52:14Z

ColinFraser:

There is a question as to whether the Algebra Filter is even working in v2.x. So is this page even necessary? It is my understanding that the Algebra Filter works using a Perl script. As this is so, then why persist with it? Perl runs in Linux servers but more and more servers are surrendering to Microsoft, which does not use Perl, I am given to understand. TeX is a more accessible across platforms, so if the TeX Notation Filter was developed further, would it not make better sense to drop support for the Algebra Filter altogether in a future version of Moodle? --[[User:Colin Fraser|Colin Fraser]] ([[User talk:Colin Fraser|talk]]) 09:51, 4 January 2014 (WST)

Talk:Algebra filter

2014-01-04T01:51:34Z

ColinFraser:

There is a question as to whether the Algebra Filter is even working in v2.x. So is this page even necessary? It is my understanding that the Algebra Filter works using a Perl script. As this is so, then why persist with it? Perl runs in Linux servers but more and more servers are surrendering to Microsoft, which does not use Perl, I am given to understand. TeX is a more accessible across platforms, so if the TeX Notation Filter was developed further, it would make better sense to drop support for the Algebra Filter altogether in a future version of Moodle. --[[User:Colin Fraser|Colin Fraser]] ([[User talk:Colin Fraser|talk]]) 09:51, 4 January 2014 (WST)

Talk:Algebra filter

2014-01-04T01:51:24Z

ColinFraser: Created page with "There is a question as to whether the Algebra Filter is even working in v2.x. So is this page even necessary? It is my understanding that the Algebra Filter works using a Perl..."

There is a question as to whether the Algebra Filter is even working in v2.x. So is this page even necessary? It is my understanding that the Algebra Filter works using a Perl script. As this is so, then why persist with it? Perl runs in Linux servers but more and more servers are surrendering to Microsoft, which does not use Perl, I am given to understand. TeX is a more accessible across platforms, so if the TeX Notation Filter was developed further, it would make better sense to drop support for the Algebra Filter altogether in a future version of Moodle.

Algebra filter

2014-01-03T11:13:54Z

ColinFraser: /* Generally */

{{Improve}}
{{Filters}}
'''NOTE:''' While the Algebra filter is included in later versions of Moodle, a more effective way of writing mathematical notation is by using the [[TeX notation filter]].

==Generally==

Moodle has an "algebra filter" which can display mathematical expressions as if they were typeset. The filter is included in the standard Moodle packages but the administrator must activate it before you can use it.

'''NOTE:''' the use of the algebra filter '''REQUIRES''' that the Moodle Tex filter also be working as the algebra filter simply parses math expressions in one syntax and then converts the expressions to LaTex expressions for the Tex filter to render and display. The filter uses a borrowed perl script

The filter (see http://cvs.moodle.org/moodle/filter/algebra/ ) uses algebra2tex.pl, a perl script (and its associated perl module, AlgParser.pm) to parse text expressions delimited by double@ signs as tokens (though the tokens employed can be tweaked manually.)

NOTE perl script REQUIRES '''Perl'''. This is no problem with most Linux servers, but may be the cause for malfunctions in the Win world like broken connections. Exceptions / failures are NOT catched and reported via this Moodle filter.
If there is no Perl available, activate Moodle Tex (as mentioned above) and use the JAVA Math Formula Editor. It is available after activating Tex. Minor corrections in the resulting Tex code dont need deeper digging in Tex fundamentals.

While many have argued that the algebra filter is easy to use, there is apparently no Moodle reference on its "grammar" or "syntax". Research in to Webworks produced these two links for using webworks text expressions (the first one is arguably replaced by the second):

* http://webwork.math.rochester.edu/docs/docs/pglanguage/availableFunctions.html (no longer available.)
* http://webwork.maa.org/wiki/Mathematical_notation_recognized_by_WeBWorK (the connection is not clear.)

See http://moodle.org/mod/forum/discuss.php?d=126522&parent=554632.

There is a discussion of Algebra filter syntax at http://moodle.org/mod/forum/discuss.php?d=5402 offered by [http://moodle.org/user/view.php?id=2466&course=5 Zbigniew Fiedorowicz].

It appears that as of Moodle.org moving to Moodle 2 (late 2010) the Algebra filter in the forums is no longer working. It also appears that the Algebra filter does not work in Moodle Docs (which is not Moodle code, but MediaWiki, which I don't believe has a ready filter based on algebra2tex.pl.

==Troubleshooting==
The file algebradebug.php is provided in the filter folder for the purpose of debugging. Problems may arise comes from the first tags in algebradebug.php

define('NO_MOODLE_COOKIES', true); // Because it interferes with caching

You can delete the line or set it to false.

[[Category:Mathematics]]

[[fr:Filtre Algebra]]
[[es:Filtro de álgebra]]

Algebra filter

2014-01-03T11:11:05Z

ColinFraser:

{{Improve}}
{{Filters}}
'''NOTE:''' While the Algebra filter is included in later versions of Moodle, a more effective way of writing mathematical notation is by using the [[TeX notation filter]].

==Generally==

Moodle has an "algebra filter" which can display mathematical expressions as if they were typeset. The filter is included in the standard Moodle packages but the administrator must activate it before you can use it.

'''NOTE:''' the use of the algebra filter '''REQUIRES''' that the Moodle Tex filter also be working as the algebra filter simply parses math expressions in one syntax and then converts the expressions to LaTex expressions for the Tex filter to render and display. The filter uses a borrowed perl script

The filter (see http://cvs.moodle.org/moodle/filter/algebra/ ) uses algebra2tex.pl, a perl script (and its associated perl module, AlgParser.pm) to parse text expressions delimited by double@ signs as tokens (though the tokens employed can be tweaked manually.)

NOTE perl script REQUIRES '''Perl'''. This is no problem with most Linux servers, but may be the cause for malfunctions in the Win world like broken connections. Exceptions / failures are NOT catched and reported via this Moodle filter.
If there is no Perl available, activate Moodle Tex (as mentioned above) and use the JAVA Math Formula Editor. It is available after activating Tex. Minor corrections in the resulting Tex code dont need deeper digging in Tex fundamentals.

While many have argued that the algebra filter is easy to use, there is apparently no Moodle reference on its "grammar" or "syntax". Research in to Webworks produced these two links for using webworks text expressions (the first one is arguably replaced by the second):

* http://webwork.math.rochester.edu/docs/docs/pglanguage/availableFunctions.html
* http://webwork.maa.org/wiki/Mathematical_notation_recognized_by_WeBWorK

See http://moodle.org/mod/forum/discuss.php?d=126522&parent=554632.

There is a discussion of Algebra filter syntax at http://moodle.org/mod/forum/discuss.php?d=5402 offered by [http://moodle.org/user/view.php?id=2466&course=5 Zbigniew Fiedorowicz].

It appears that as of Moodle.org moving to Moodle 2 (late 2010) the Algebra filter in the forums is no longer working. It also appears that the Algebra filter does not work in Moodle Docs (which is not Moodle code, but MediaWiki, which I don't believe has a ready filter based on algebra2tex.pl.

==Troubleshooting==
The file algebradebug.php is provided in the filter folder for the purpose of debugging. Problems may arise comes from the first tags in algebradebug.php

define('NO_MOODLE_COOKIES', true); // Because it interferes with caching

You can delete the line or set it to false.

[[Category:Mathematics]]

[[fr:Filtre Algebra]]
[[es:Filtro de álgebra]]

Algebra filter

2014-01-03T11:07:07Z

ColinFraser: /* Generally */

{{Improve}}
{{Filters}}
'''NOTE:''' While the Algebra filter is included in later versions of Moodle, a more effective way of writing mathematical notation is by using the [[Using_TeX_Notation TeX Notation]] filter.

==Generally==

Moodle has an "algebra filter" which can display mathematical expressions as if they were typeset. The filter is included in the standard Moodle packages but the administrator must activate it before you can use it.

'''NOTE:''' the use of the algebra filter '''REQUIRES''' that the Moodle Tex filter also be working as the algebra filter simply parses math expressions in one syntax and then converts the expressions to LaTex expressions for the Tex filter to render and display. The filter uses a borrowed perl script

The filter (see http://cvs.moodle.org/moodle/filter/algebra/ ) uses algebra2tex.pl, a perl script (and its associated perl module, AlgParser.pm) to parse text expressions delimited by double@ signs as tokens (though the tokens employed can be tweaked manually.)

NOTE perl script REQUIRES '''Perl'''. This is no problem with most Linux servers, but may be the cause for malfunctions in the Win world like broken connections. Exceptions / failures are NOT catched and reported via this Moodle filter.
If there is no Perl available, activate Moodle Tex (as mentioned above) and use the JAVA Math Formula Editor. It is available after activating Tex. Minor corrections in the resulting Tex code dont need deeper digging in Tex fundamentals.

While many have argued that the algebra filter is easy to use, there is apparently no Moodle reference on its "grammar" or "syntax". Research in to Webworks produced these two links for using webworks text expressions (the first one is arguably replaced by the second):

* http://webwork.math.rochester.edu/docs/docs/pglanguage/availableFunctions.html
* http://webwork.maa.org/wiki/Mathematical_notation_recognized_by_WeBWorK

See http://moodle.org/mod/forum/discuss.php?d=126522&parent=554632.

There is a discussion of Algebra filter syntax at http://moodle.org/mod/forum/discuss.php?d=5402 offered by [http://moodle.org/user/view.php?id=2466&course=5 Zbigniew Fiedorowicz].

It appears that as of Moodle.org moving to Moodle 2 (late 2010) the Algebra filter in the forums is no longer working. It also appears that the Algebra filter does not work in Moodle Docs (which is not Moodle code, but MediaWiki, which I don't believe has a ready filter based on algebra2tex.pl.

==Troubleshooting==
The file algebradebug.php is provided in the filter folder for the purpose of debugging. Problems may arise comes from the first tags in algebradebug.php

define('NO_MOODLE_COOKIES', true); // Because it interferes with caching

You can delete the line or set it to false.

[[Category:Mathematics]]

[[fr:Filtre Algebra]]
[[es:Filtro de álgebra]]

User policies

2013-07-24T12:24:48Z

ColinFraser: /* Unsupported role assignments */

{{Roles}}
==User policies==
The following settings may be changed by an administrator in ''Administration > Site administration > Users > Permissions > User policies''.

===Role for visitors===
Users who are not logged in to the site will be treated as if they have the role specified here, granted to them at the site context. The role of Guest is the default and the recommended setting for standard Moodle sites. The user will still be required to login to participate in an activity.

===Role for guest===
This option specifies the role that will automatically be assigned to the guest user. This role is also temporarily assigned to non enrolled users when they enter a course that allows guests without password.

===Deny Guest Access to a site altogether===

Go to Site administration ► Plugins ► Authentication ► Manage authentication and there is a switch there that allows you to turn the Guest Access button off altogether.

===Default role for all users===

It is recommended that the default role for all users is set to [[Authenticated user]]. To set it to a custom role, the custom role must be assignable in the system context and have role archetype set to none.

Note: It is not recommended that the default role for all users is set to student, for reasons given in MDL-26805.

===Auto-login guest===

If not set, then visitors must click the "Login as a guest" button before entering a course which allows [[Guest|guest access]].

Note: If auto-login guest is set, the guest login button also needs to be set to show (in ''Administration > Site administration > Plugins > Authentication > Manage authentication''), even though visitors won't necessarily use it.

===Hide user fields===
The following user fields appear on users' profile pages. Certain user fields are also listed on the course participants page. You can increase student privacy by hiding selected user fields.

Description, city/town, country, web page, ICQ number, Skype ID, Yahoo ID, AIM ID, MSN ID, last access, My courses and first access and groups

*User fields on users' profile pages are hidden from all users with the capability [[Capabilities/moodle/user:viewhiddendetails|moodle/user:viewhiddendetails]] not set.
*User fields on the course participants page are hidden from all users with the capability [[Capabilities/moodle/course:viewhiddenuserfields|moodle/course:viewhiddenuserfields]] not set.

===Show user identity===

Any of the following fields may be shown to users with the capability [[Capabilities/moodle/site:viewuseridentity|moodle/site:viewuseridentity]] when searching for users and displaying lists of users.

*ID number
*Email address
*Phone number
*Mobile phone
*Department
*Institution

This setting is useful for sites with large number of users, where the likelihood of users with the same name is high.

Locations where user identity fields are shown are as follows:

*User selectors ([[Assign roles]] in some places, [[Groups|groups]], forum subscribers)
*[[Browse list of users]]
*Course participants
*[[Gradebook|Grader report]]
*[[Quiz reports]]
*[[Using SCORM|SCORM reports]]
*[[Using Assignment|Assignment submissions]]
*[[Using Course completion|Course completion report]]
*[[Using Activity completion|Activity completion report]]
*[[Enrolled users|Enroling users]]

Tip: Select only one or two fields that are mandatory at your institution. Do not select more than two field otherwise tables become very wide.
===Maximum users per page===
{{New features}}
You can choose here the maximum number of users to be displayed when searching in courses, groups, cohorts etc. The default is 100 but if your Moodle site is very large you can increase the number here.

===Enable Gravatar===

[http://gravatar.com/ Gravatar] (an abbreviation for globally recognized avatar) is a service for providing globally unique avatars.

An administrator can enable the use of gravatars in ''Administration > Site administration > Users > Permissions > User policies''. If a user has not uploaded a user picture, Moodle will check whether the user's email address has an associated gravatar and if so, will use the gravatar as the user's picture.

* [http://www.youtube.com/watch?v=Z4b7tJedlMA Use your Gravatar in Moodle 2.2 screencast]

===Gravatar default image URL===

In Moodle 2.3.3 onwards, if gravatars are enabled, an alternative default user picture may be specified. The options are:

* A gravatar default image - by entering a code such as mm. See https://en.gravatar.com/site/implement/images/ for codes of other gravatar default images.
* A specified image - by entering the image URL

If the field is left empty then the theme's default user picture is used.

==Unsupported role assignments==

Unsupported role assignments are role assignments in contexts that make no sense for that role, such as the course creator role in the course or activity context, or the teacher role in the user context.

Prior to Moodle 2.0, there was no 'Context types where this role may be assigned' setting in the edit role form, and so any role could be assigned in any context. Upon upgrading a site from 1.9, any role assignments in contexts that make no sense for that role are listed as unsupported role assignments in ''Settings > Site administration > Users > Permissions > Unsupported role assignments''.

In general, it is safe to delete all unsupported role assignments. In doing so, the worst that can happen is for a user to be unassigned a custom role; no other data loss will occur.

===Is it possible to remove the open door with green arrow icon that represents Self enrolment? Disable Self enrolment altogether?===

Yes, as an Administrator, go into

Site Administration > Plugins > Authentication > Manage Authentication

In Common Settings, turn Self Registration to Disable and then if you do not want the Guest login button to show, turn it to Hide. Consider also the Authentication methods you want to use, you can set them on by clicking on any closed eye. This removes the self enrolment option completely.

If you just want to remove/hide the icon and not remove the ability to self enrol then you can take one of a couple of different options.

The Self Enrolment icon itself is theme dependent which means it is not always an open door with a green arrow. One way would be to replace it in whichever theme you are using with a transparent png of the same size. If you use something like Firebug, click on the icon to see its properties, (right click in Windows, or Cmd+Click in Mac) you should be able to see the path to the icon and its name - then you replace it with a file of the same name which is transparent (ie, invisible, hopefully) or one pixel by one pixel.

You can isolate the image and disable it using CSS but first you need to know the css path for that image.

For the Front Page it is this...

#page-site-index .enrolmenticons {visibility: hidden;}

Depending on your theme, you can either add the CSS to your theme's Custom Settings page, or add that CSS rule directly into yourtheme/style/core.css or whatever name your CSS stylesheet is called. If you add the CSS to the stylesheet you need to add it at the very bottom of that file.

Before you do any of this it is best enabling Theme Designer Mode from Site Administration > Appearance > themes > Theme settings as this will allow the changes to be seen. You will also need to refresh your browser window to using Ctrl + F5 which forces the page to reload. Or, you can click the Clear Theme Caches button in the Site Administration > Appearance > themes > Theme selector page.

Thanks to Mary Cooch and Mary Evans.

[[Category:Site administration]]

[[de:Einstellungen für Rollen]]
[[fr:Réglages des rôles]]
[[ja:ユーザポリシー]]

User policies

2013-07-24T12:22:38Z

ColinFraser: /* Role for guest */

{{Roles}}
==User policies==
The following settings may be changed by an administrator in ''Administration > Site administration > Users > Permissions > User policies''.

===Role for visitors===
Users who are not logged in to the site will be treated as if they have the role specified here, granted to them at the site context. The role of Guest is the default and the recommended setting for standard Moodle sites. The user will still be required to login to participate in an activity.

===Role for guest===
This option specifies the role that will automatically be assigned to the guest user. This role is also temporarily assigned to non enrolled users when they enter a course that allows guests without password.

===Deny Guest Access to a site altogether===

Go to Site administration ► Plugins ► Authentication ► Manage authentication and there is a switch there that allows you to turn the Guest Access button off altogether.

===Default role for all users===

It is recommended that the default role for all users is set to [[Authenticated user]]. To set it to a custom role, the custom role must be assignable in the system context and have role archetype set to none.

Note: It is not recommended that the default role for all users is set to student, for reasons given in MDL-26805.

===Auto-login guest===

If not set, then visitors must click the "Login as a guest" button before entering a course which allows [[Guest|guest access]].

Note: If auto-login guest is set, the guest login button also needs to be set to show (in ''Administration > Site administration > Plugins > Authentication > Manage authentication''), even though visitors won't necessarily use it.

===Hide user fields===
The following user fields appear on users' profile pages. Certain user fields are also listed on the course participants page. You can increase student privacy by hiding selected user fields.

Description, city/town, country, web page, ICQ number, Skype ID, Yahoo ID, AIM ID, MSN ID, last access, My courses and first access and groups

*User fields on users' profile pages are hidden from all users with the capability [[Capabilities/moodle/user:viewhiddendetails|moodle/user:viewhiddendetails]] not set.
*User fields on the course participants page are hidden from all users with the capability [[Capabilities/moodle/course:viewhiddenuserfields|moodle/course:viewhiddenuserfields]] not set.

===Show user identity===

Any of the following fields may be shown to users with the capability [[Capabilities/moodle/site:viewuseridentity|moodle/site:viewuseridentity]] when searching for users and displaying lists of users.

*ID number
*Email address
*Phone number
*Mobile phone
*Department
*Institution

This setting is useful for sites with large number of users, where the likelihood of users with the same name is high.

Locations where user identity fields are shown are as follows:

*User selectors ([[Assign roles]] in some places, [[Groups|groups]], forum subscribers)
*[[Browse list of users]]
*Course participants
*[[Gradebook|Grader report]]
*[[Quiz reports]]
*[[Using SCORM|SCORM reports]]
*[[Using Assignment|Assignment submissions]]
*[[Using Course completion|Course completion report]]
*[[Using Activity completion|Activity completion report]]
*[[Enrolled users|Enroling users]]

Tip: Select only one or two fields that are mandatory at your institution. Do not select more than two field otherwise tables become very wide.
===Maximum users per page===
{{New features}}
You can choose here the maximum number of users to be displayed when searching in courses, groups, cohorts etc. The default is 100 but if your Moodle site is very large you can increase the number here.

===Enable Gravatar===

[http://gravatar.com/ Gravatar] (an abbreviation for globally recognized avatar) is a service for providing globally unique avatars.

An administrator can enable the use of gravatars in ''Administration > Site administration > Users > Permissions > User policies''. If a user has not uploaded a user picture, Moodle will check whether the user's email address has an associated gravatar and if so, will use the gravatar as the user's picture.

* [http://www.youtube.com/watch?v=Z4b7tJedlMA Use your Gravatar in Moodle 2.2 screencast]

===Gravatar default image URL===

In Moodle 2.3.3 onwards, if gravatars are enabled, an alternative default user picture may be specified. The options are:

* A gravatar default image - by entering a code such as mm. See https://en.gravatar.com/site/implement/images/ for codes of other gravatar default images.
* A specified image - by entering the image URL

If the field is left empty then the theme's default user picture is used.

==Unsupported role assignments==

Unsupported role assignments are role assignments in contexts that make no sense for that role, such as the course creator role in the course or activity context, or the teacher role in the user context.

Prior to Moodle 2.0, there was no 'Context types where this role may be assigned' setting in the edit role form, and so any role could be assigned in any context. Upon upgrading a site from 1.9, any role assignments in contexts that make no sense for that role are listed as unsupported role assignments in ''Settings > Site administration > Users > Permissions > Unsupported role assignments''.

In general, it is safe to delete all unsupported role assignments. In doing so, the worst that can happen is for a user to be unassigned a custom role; no other data loss will occur.

[[Category:Site administration]]

[[de:Einstellungen für Rollen]]
[[fr:Réglages des rôles]]
[[ja:ユーザポリシー]]

Installation FAQ

2013-07-24T12:16:13Z

ColinFraser: /* What & where are Moodle's configuration settings stored? */

{{Installing Moodle}}
== System information needed for Installation problems forum ==
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Consider providing some or all of the following:
* Server Operating System name (version also if possible):
* PHP version (e.g. PHP 5.3.2)
* Database server type and version (e.g. MySQL 5.5.18)
* Browser and version (e.g. Internet Explorer 8):
* Moodle version (e.g. 2.1):
* Moodle install type? (New/Upgrade):
* Moodle config.php attached (please remove passwords):
* Phpinfo attached?:

Make sure you provide a sensible description (never HELP! or URGENT!) and a full description of what you did and what happened. Copy and paste any error messages accurately in full. 'Nothing' is not a symptom, even a blank page is something!

[[#top|Top]]

==PHP - is it installed and what version do I have?==

Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:

<code php>
<?PHP phpinfo() ?>
</code>

If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.

[[#top|Top]]

==I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x==
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

[[#top|Top]]

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

[[#top|Top]]

==What & where are Moodle's configuration settings stored?==
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the [[Configuration file]] docs.
[[#top|Top]]

==Downloading previous releases of Moodle==
It is possible to download previous versions of Moodle that are not found on the [http://download.moodle.org Standard Moodle Download page]. There are zip and tgz compressed located at <nowiki>http://download.moodle.org/stable[version_number]</nowiki> (see links below).

{| style="width:75%; height:75px" border="0"
|-
| 2.0 Versions || [http://download.moodle.org/stable19 1.9 Versions] || [http://download.moodle.org/stable18 1.8 Versions]
|-
|[http://download.moodle.org/stable17 1.7 Versions] || [http://download.moodle.org/stable16 1.6 Versions] || [http://download.moodle.org/stable15/ 1.5 Versions]
|-
| [http://download.moodle.org/stable14 1.4 Versions] || [http://download.moodle.org/stable13 1.3 Versions] ||
|}

You can download previous releases by using wget, lynx or curl with this URL:
<nowiki>http://download.moodle.org/stable[version_number]</nowiki>.
:For example: to download Moodle version 1.5, use <nowiki>http://download.moodle.org/stable15</nowiki>. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki>
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac packages], use either of these URLs (depending on whether you need the Intel or PPC package):
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki>
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki>

[[#top|Top]]

== How to enable and check PHP error logs==
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[PHP error logs]].

== "Could not find a top level course" ==
If this appears immediately after you have attempted to install Moodle it almost certainly means that the installation did not complete. A complete installation will ask you for the administrator profile and to name the site just before it completes. Check your logs for errors. Then drop the database and start again. If you used the web-based installer try the command line one. Does your computer definitely have sufficient resource to run Moodle?

==Email copies are not being sent from my forums==

You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on. Please refer to the [[Cron|cron instructions]].

Tips:
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.
* Check your firewall or ask your network administrator. Many mail servers are heavily locked down and you may need permission to send mail through them.

[[#top|Top]]

==I can't log in - I just stay stuck on the login screen==

This may also apply if you are seeing “Your session has timed out. Please login again” or "A server error that affects your login session was detected. Please login again or restart your browser" and cannot log in.

The following are possible causes and actions you can take (in no particular order):

* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.
* Check that your hard disk is not full or if your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in.
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)
* Try deleting cookies on your computer and/or try another browser or another client computer
* In ''Settings > Site administration > Server > Session Handling'', try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser.
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values.
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations.
* Check config.php - it should NOT have any spaces/new lines at the end of code.
* You are using the correct username and password, yes?

If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it - see [[Administration FAQ]].

[[#top|Top]]

==I log in but the login link doesn't change. I am logged in and can navigate freely.==

Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.

[[#top|Top]]
==Uploaded files give "File not found"==

For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.

Your web server needs to be configured to allow the part of the URL after a script name to be passed directly to the script. This is usually enabled in Apache 1, but is usually disabled by default in Apache 2. To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory (see [[Installing Moodle]] for more details):

'''AcceptPathInfo''' on

Note, this will ONLY work for Apache versions 2.x.

For IIS you need to configure URL rewriting. This feature is not available in IIS 6 so you need to install a 3rd party IIS extension - see http://msdn.microsoft.com/en-us/library/ms972974.aspx.

IIS 7 now comes with the new URL Rewrite Module so a 3rd part extension is no longer required if you are running IIS 7. See http://learn.iis.net/page.aspx/734/url-rewrite-module for more details.

Once you've got URL rewriting working the recommended rewriting rule is:

'''RewriteRule''' ^([^\?]+?\.php)(\/.+)$ $1\?file=$2 [QSA]

In theory you could try to use path info on IIS too, but it is not reliable, especially when using unicode file names.

If you are unable to configure your server properly then you can switch Moodle to use an alternative method. The major disadvantages is that you will not be able to use SCORM packages at all and some Adobe Flash and Java applets will not work either.

To use this alternative method, you should change the ''slasharguments'' variable. For moodle versions < 1.7, this is located in the Operating System section of ''Administration > Configuration > [[admin/config|Variables]]''. In later versions, this option is located in ''Site Administration > Server > HTTP''. You should now be able to access your uploaded files.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=145422 Troubleshooting Guide - 404 Errors] forum discussion.

[[#top|Top]]

==Why are all my pages blank?==

Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (e.g.)

<code php>
$CFG->dirroot = "/var/www/moodle";
</code>

Another reason might be that PHP has not been configured to support MySQL (or whatever other database you are using). This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].

To determine if database support is your problem, insert this as the second line in your ''config.php'' file

<code php>
phpinfo();
</code>

then reload the web page. Examine the output closely to see if you chosen database is supported. If not, look for a package you are missing.

[[#top|Top]]

== Why is a particular page blank or incomplete? ==

*'''Check your web server log files!!'''
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.

*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".

*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.

*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion

==Installation hangs when setting-up database tables==
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there.

See [[Unexpected installation halts]] for more about solutions that involve:
*Checking for MySQL limits
*Checking the .htaccess files
*Code customizations issues
*Checking memory limit
*Upgrade incrementally
*Fix fopen function

[[#top|Top]]

==Why can't I upload a new image into my profile?==

If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:
*The permissions associated with the role you are using are preventing you from changing your profile picture.
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > PHP info'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.

If Moodle thinks GD is not installed, then you will need to '''install the GD library'''.
*On Unix you may need to re-compile PHP with arguments something like this:

./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars
--enable-versioning --with-zlib

* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:
extension=php_gd2.dll

:Windows users should see the [[Installing AMP|installation instructions]] for further help.

3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.

'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.

== Why doesn't my Moodle site display the time and date correctly? ==

Each language requires a specific language code (called a '''locale''' code) to allow dates to be displayed correctly. The language packs contain default standard codes, but sometimes these don't work on Windows servers.

You can find the correct locale codes for Windows on these two pages: [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_language_strings.asp Language codes] and [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_country_strings.asp Country/region] codes (e.g. "esp_esp" for spanish)

These new locale codes can be entered on the Administration >> Configuration >> [[admin/config|Variables]] page, where they override the ones in the currently chosen language pack.
[[#top|Top]]
== How do I uninstall Moodle?==

'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):
<pre>sql>DROP DATABASE moodle;</pre>
:In the above example replace 'moodle' with the name of the moodle database you created when installing.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:
*Open cmd.exe and navigate to this directory within your installation directory:
<pre>server/mysql/bin</pre>
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre>
*Enter your database password at the prompt (the default is "" [blank]).
*Enter "y" to confirm the database drop.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

==Migrating Moodle to a new site or server==
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the admin/replace.php script, your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.

[[#top|Top]]
==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php).
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].

[[#top|Top]]
==Maximum upload file size - how to change it?==
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].

If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server.

For more help see:
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]
*[[Installing_Moodle#Recheck_PHP_settings]]
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]
*[[Site_policies#Maximum_uploaded_file_size]]
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650

[[#top|Top]]

==Moodle claims PHP float handling is not compatible==

The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".

[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.

You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.

Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding
ini_set('precision', 14);
to your config.php file, and report your success in MDL-18253.

==When upgrading Moodle claims my database is not UTF8 when I'm sure it is==

The symptom is that you are upgrading a post-1.6 Moodle to a newer version. The Environment check tells you that your database is not UTF8 and refuses to upgrade.

The database may not have it's character encoding set quite correctly. You can safely try this command on the database (mySQL):

ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

(Change 'moodle' for the name of your database). You need to copy this into your MySQL client program that comes packaged with it.

Alternatively, you maybe adding a new clean install Moodle version to an existing web server and the UTF8 check error will not allow you to proceed. Use [[phpMyAdmin]] to help you. This web client is available as a plugin for Moodle or through your web hosting control panel. Using this program, create an empty database (for example moodle199) and make sure "MySQL connection collation" is a utf8 entry, such as utf8_general_ci. Go back to the Moodle installation screen with the check error, hit the previous button on the bottom and make sure the databae has the same name as your new empty database (for example moodle199).

If your Moodle site is version 1.5 or older then it's telling the truth.

[[#top|Top]]

== How do I run multiple instances of Moodle without duplicating base code? ==

See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].

== What is FreeTDS and how can I use it in my installation? ==
[[FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.

== How do I install a plugin? ==

Please see [[Installing plugins]].

==I can't enable a plugin on the Plugins overview page because the icon is not clickable==
The open and closed eye icon on the Plugins overview page is simply there to show whether or not a plugin is enabled. You can't edit plugins from this screen. If you wish to enable a plugin, to to the appropriate page for managing the type of plugin you need, for instance ''Settings>Site administration>Plugins>Repositories>Manage repositories'' or ''Settings>Site administration>Plugins>Activity modules>Manage activities.''

== See also ==

* [[Errors FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Installing Moodle in a shared web hosting environment
** [https://docs.moodle.org/24/en/Finding_and_Selecting_A_Web_Host Finding and Selecting a web host]
** [https://docs.moodle.org/24/en/Install_Moodle2.2_on_godaddy Installing on GoDaddy]
** [https://docs.moodle.org/24/en/Installing_Moodle_on_SmarterASP.NET Installing Moodle on SmarterASP.NET web hosting]

[[Category:FAQ]]

[[es:FAQ Instalación]]
[[fr:FAQ d'installation]]
[[ja:インストールFAQ]]
[[de:Installation FAQ]]

Installation FAQ

2013-07-24T12:14:16Z

ColinFraser: /* PHP - is it installed and what version do I have? */

{{Installing Moodle}}
== System information needed for Installation problems forum ==
When posting questions to the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum], try to provide as much background information as possible about your Moodle system. Consider providing some or all of the following:
* Server Operating System name (version also if possible):
* PHP version (e.g. PHP 5.3.2)
* Database server type and version (e.g. MySQL 5.5.18)
* Browser and version (e.g. Internet Explorer 8):
* Moodle version (e.g. 2.1):
* Moodle install type? (New/Upgrade):
* Moodle config.php attached (please remove passwords):
* Phpinfo attached?:

Make sure you provide a sensible description (never HELP! or URGENT!) and a full description of what you did and what happened. Copy and paste any error messages accurately in full. 'Nothing' is not a symptom, even a blank page is something!

[[#top|Top]]

==PHP - is it installed and what version do I have?==

Make a new file on your web site called ''info.php'', containing the following text, and call it from your browser:

<code php>
<?PHP phpinfo() ?>
</code>

If nothing happens then you don't have PHP installed or your webserver is not configured to handle .php files properly. See the installation docs for some information about where to download it for your computer. See the [[phpinfo]] page for details about the content of this page.

[[#top|Top]]

==I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x==
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

[[#top|Top]]

==What & where are Moodle's configuration settings stored?==
Configuration settings are stored in the config.php file stored in your moodle folder. This file is created during the installation process. If there is a problem and the installation cannot create the file, you can try creating it manually from the [[Configuration file]] docs.
[[#top|Top]]

==Downloading previous releases of Moodle==
It is possible to download previous versions of Moodle that are not found on the [http://download.moodle.org Standard Moodle Download page]. There are zip and tgz compressed located at <nowiki>http://download.moodle.org/stable[version_number]</nowiki> (see links below).

{| style="width:75%; height:75px" border="0"
|-
| 2.0 Versions || [http://download.moodle.org/stable19 1.9 Versions] || [http://download.moodle.org/stable18 1.8 Versions]
|-
|[http://download.moodle.org/stable17 1.7 Versions] || [http://download.moodle.org/stable16 1.6 Versions] || [http://download.moodle.org/stable15/ 1.5 Versions]
|-
| [http://download.moodle.org/stable14 1.4 Versions] || [http://download.moodle.org/stable13 1.3 Versions] ||
|}

You can download previous releases by using wget, lynx or curl with this URL:
<nowiki>http://download.moodle.org/stable[version_number]</nowiki>.
:For example: to download Moodle version 1.5, use <nowiki>http://download.moodle.org/stable15</nowiki>. You'll see a directory tree with the files displayed. Click on the one you want and download as normal - if you require the latest update of the version, scroll to the end of the list and download the "moodle-latest" file.
* '''Windows Packages''': To download other releases not found in [http://download.moodle.org/windows/ Moodle packages for Windows], use this URL:
:<nowiki>http://download.moodle.org/windows/MoodleWindowsInstaller-latest-[version_number].zip</nowiki>
* '''Mac Packages''': To download other releases not found in [http://download.moodle.org/macosx/ Mac packages], use either of these URLs (depending on whether you need the Intel or PPC package):
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-Intel-[version_number].dmg</nowiki>
:<nowiki>http://download.moodle.org/macosx/Moodle4Mac-PPC-[version_number}.dmg</nowiki>

[[#top|Top]]

== How to enable and check PHP error logs==
PHP can be set up to log errors in a variety of different ways: two of these involve the use of the php.ini file and the ini_set command. See [[PHP error logs]].

== "Could not find a top level course" ==
If this appears immediately after you have attempted to install Moodle it almost certainly means that the installation did not complete. A complete installation will ask you for the administrator profile and to name the site just before it completes. Check your logs for errors. Then drop the database and start again. If you used the web-based installer try the command line one. Does your computer definitely have sufficient resource to run Moodle?

==Email copies are not being sent from my forums==

You ''must'' set up cron properly if you want Moodle to send out automatic email from forums, assignments etc. This same process also performs a number of clean-up tasks such as deleting old unconfirmed users, unenrolling old students and so on. Please refer to the [[Cron|cron instructions]].

Tips:
* Try the default settings in ''Settings > Site administration > Plugins > Message outputs > Email''. This generally works. Except...
* On a Windows server you *must* supply the address of an SMTP server (Windows, unlike Unix, does not have a build in mail server) in the above settings page
* Make sure that ''allowuseremailcharset'' in ''Settings > Site administration > Plugins > Message outputs > Email'' is set to No unless you really know what you are doing. Setting this to Yes can cause a problem in some versions of Moodle.
* Check your firewall or ask your network administrator. Many mail servers are heavily locked down and you may need permission to send mail through them.

[[#top|Top]]

==I can't log in - I just stay stuck on the login screen==

This may also apply if you are seeing “Your session has timed out. Please login again” or "A server error that affects your login session was detected. Please login again or restart your browser" and cannot log in.

The following are possible causes and actions you can take (in no particular order):

* Check first that your main admin account (which will be a manual account) is also a problem. If your users are using an external authentication method (e.g. LDAP) that could be the problem. Isolate the fault and make sure it really is Moodle before going any further.
* Check that your hard disk is not full or if your server is on shared hosting check that you have not reached your disk space quota. This will prevent new sessions being created and nobody will be able to log in.
* Carefully check the permissions in your 'moodledata' area. The web server needs to be able to write to the 'sessions' subdirectory.
* Your own computer (not your Moodle server) may have a firewall that is stripping referrer information from the browser. Here are some instructions for fixing [http://service1.symantec.com/SUPPORT/nip.nsf/46f26a2d6dafb0a788256bc7005c3fa3/b9b47ad7eddd343b88256c6b006a85a8?OpenDocument&src=bar_sch_nam Norton firewall products].
* Try deleting the ''sessions'' folder in your moodledata directory (anybody currently logged in will be thrown out)
* Try deleting cookies on your computer and/or try another browser or another client computer
* In ''Settings > Site administration > Server > Session Handling'', try setting a value for 'Cookie prefix'. You can also do this by setting <code>$CFG->sessioncookie='something';</code> in config.php. This is especially true if you are using multiple Moodles on the same browser.
* Make sure you have not removed or changed the [[Password salting|Password Salt]] value(s) in config.php. If passwords were created using a salt the correct salt must be in config.php for those passwords to continue to work. This is easily done if you recreate config.php while performing an upgrade and forget to transfer the salt values.
* Do you have a .htaccess file in your Moodle folder (or its parent directories). If so, is there anything in there that might be causing trouble (strange redirects, access restrictions etc.)?
* Check the value of '''mnet_localhost_id''' in the mdl_config database table. It's normally 1 but must match the '''mnet_hostid''' field in your user records in the mdl_user table for the user to be recognised. It can sometimes get changed spuriously during upgrades or site migrations.
* Check config.php - it should NOT have any spaces/new lines at the end of code.
* You are using the correct username and password, yes?

If you are still having problems, read the [[Can_not_log_in | Cannot log in]] page. You '''could''' also try changing the admin password. Proceed as if you have lost it - see [[Administration FAQ]].

[[#top|Top]]

==I log in but the login link doesn't change. I am logged in and can navigate freely.==

Make sure the URL in your <code>$CFG->wwwroot</code> setting is exactly the same as the one you are actually using to access the site.

[[#top|Top]]
==Uploaded files give "File not found"==

For example: Not Found: The requested URL /moodle/file.php/2/myfile.jpg was not found on this server.

Your web server needs to be configured to allow the part of the URL after a script name to be passed directly to the script. This is usually enabled in Apache 1, but is usually disabled by default in Apache 2. To turn it on, add this line to your ''httpd.conf'', or to a ''.htaccess'' file in your local directory (see [[Installing Moodle]] for more details):

'''AcceptPathInfo''' on

Note, this will ONLY work for Apache versions 2.x.

For IIS you need to configure URL rewriting. This feature is not available in IIS 6 so you need to install a 3rd party IIS extension - see http://msdn.microsoft.com/en-us/library/ms972974.aspx.

IIS 7 now comes with the new URL Rewrite Module so a 3rd part extension is no longer required if you are running IIS 7. See http://learn.iis.net/page.aspx/734/url-rewrite-module for more details.

Once you've got URL rewriting working the recommended rewriting rule is:

'''RewriteRule''' ^([^\?]+?\.php)(\/.+)$ $1\?file=$2 [QSA]

In theory you could try to use path info on IIS too, but it is not reliable, especially when using unicode file names.

If you are unable to configure your server properly then you can switch Moodle to use an alternative method. The major disadvantages is that you will not be able to use SCORM packages at all and some Adobe Flash and Java applets will not work either.

To use this alternative method, you should change the ''slasharguments'' variable. For moodle versions < 1.7, this is located in the Operating System section of ''Administration > Configuration > [[admin/config|Variables]]''. In later versions, this option is located in ''Site Administration > Server > HTTP''. You should now be able to access your uploaded files.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=145422 Troubleshooting Guide - 404 Errors] forum discussion.

[[#top|Top]]

==Why are all my pages blank?==

Check the dirroot variable in ''config.php''. You must use complete, absolute pathnames (e.g.)

<code php>
$CFG->dirroot = "/var/www/moodle";
</code>

Another reason might be that PHP has not been configured to support MySQL (or whatever other database you are using). This is common on RedHat and OpenBSD installations. In this case, an error is generated, but since error displays are often disabled by default, all that is seen on the browser is a blank screen. To enable PHP error displays see [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | How to enable and check PHP error logs]].

To determine if database support is your problem, insert this as the second line in your ''config.php'' file

<code php>
phpinfo();
</code>

then reload the web page. Examine the output closely to see if you chosen database is supported. If not, look for a package you are missing.

[[#top|Top]]

== Why is a particular page blank or incomplete? ==

*'''Check your web server log files!!'''
:If a particular page is blank or incomplete (it doesn't display the footer), before you do anything else switch on [[Debugging]] and [[Installation_FAQ#How_to_enable_and_check_PHP_error_logs | check your PHP error logs]]. Having established that PHP error logging is working, reproduce the error. Immediately check the error log file right at the end. Hopefully you will see a PHP error message at or very near the end of the file. This may solve your problem directly or makes it a lot easier to diagnose the problem in the Moodle forums.

*If you are '''upgrading to a new version of Moodle''', check that you do not have an old version of a non-standard block or module installed. Remove any such blocks or modules installed using the admin settings page and start the install process again. However, do also make sure that you have included all optional plugins that were required by your courses. This is particularly common with "editing on".

*If you '''do not see any blocks listed''', turn editing on and remove any blocks that you have added to that page and try reloading.

*You may get this error immediately after '''selecting a language'''. At this stage of the installation process your Moodle computer may need to connect to the Internet and download a language pack, so check that the computer can access the Internet by using a browser. Check also that your PHP settings are as given in the Moodle [[Installing_Moodle#Requirements | Moodle Requirements]] page.

'''See also''':
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97734 PHP configuration error] forum discussion

==Installation hangs when setting-up database tables==
Sometimes the installation will hang when setting up tables, where only half the page displayed in the browser and/or other outputs are removed. You may see truncated MySQL statements, or the “Scroll to continue” link is displayed but no “Continue” button is there.

See [[Unexpected installation halts]] for more about solutions that involve:
*Checking for MySQL limits
*Checking the .htaccess files
*Code customizations issues
*Checking memory limit
*Upgrade incrementally
*Fix fopen function

[[#top|Top]]

==Why can't I upload a new image into my profile?==

If you don't see anything on your user profile pages to let you upload user images then it's usually one of the following:
*The permissions associated with the role you are using are preventing you from changing your profile picture.
* GD is not installed, or is not enabled on your server. Make sure '''GD has been included in your PHP installation'''. You can check this by going to ''Site Administration > Server > PHP info'' and looking for the gdversion setting. This setting is chosen automatically every time you visit that page. If it shows GD version 1 or version 2 then everything should be fine. Save that configuration page and go back to your user profile.
* GD is installed, but is in some way corrupt. For instance, [http://moodle.org/mod/forum/discuss.php?d=44271#p386194 see this discussion on empty lines or white spaces in config files.]
GD is a library that allows image processing. For example, when all is well with your system, and you upload a new profile image, GD compresses the image and produces two thumbnails, one is 100x100 pixels, and the other is 35x35 pixels.

If Moodle thinks GD is not installed, then you will need to '''install the GD library'''.
*On Unix you may need to re-compile PHP with arguments something like this:

./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --with-gd
--with-jpeg-dir=/usr/local --with-png-dir=/usr --with-ttf --enable-gd-native-ttf
--enable-magic-quotes --with-mysql --enable-sockets --enable-track-vars
--enable-versioning --with-zlib

* On Windows this is usually a matter of "turning on" the extension in PHP by editing your php.ini file. To do this remove the semicolon for the php_gd2.dll extension - check that this file is actually present in your php extensions folder first (search your php.ini for extension_dir to determine where this points to on your hard disk). You should then have a line that looks like this:
extension=php_gd2.dll

:Windows users should see the [[Installing AMP|installation instructions]] for further help.

3. Remember to '''restart your webserver''' (if possible) and re-visit the Moodle configuration page after making any changes to PHP so it can pick up the correct version of GD.

'''See also''': Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=44271 Profile pictures] for additional information.

== Why doesn't my Moodle site display the time and date correctly? ==

Each language requires a specific language code (called a '''locale''' code) to allow dates to be displayed correctly. The language packs contain default standard codes, but sometimes these don't work on Windows servers.

You can find the correct locale codes for Windows on these two pages: [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_language_strings.asp Language codes] and [http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/_crt_country_strings.asp Country/region] codes (e.g. "esp_esp" for spanish)

These new locale codes can be entered on the Administration >> Configuration >> [[admin/config|Variables]] page, where they override the ones in the currently chosen language pack.
[[#top|Top]]
== How do I uninstall Moodle?==

'''Webhost/manual installation''': If you have installed Moodle manually or have installed onto a webhost, follow these steps:
*Delete the moodle database using this mysql command (or delete using your mysql client, e.g. PHPMyAdmin):
<pre>sql>DROP DATABASE moodle;</pre>
:In the above example replace 'moodle' with the name of the moodle database you created when installing.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

'''XAMPP windows installation''': If you have installed Moodle on windows through the XAMPP package, follow these steps:
*Open cmd.exe and navigate to this directory within your installation directory:
<pre>server/mysql/bin</pre>
*Run this command, replacing USERNAME with your database username (the default is "root") and DATABASE with your database name (the default is "moodle"):
<pre>mysqladmin.exe -u USERNAME -p drop DATABASE</pre>
*Enter your database password at the prompt (the default is "" [blank]).
*Enter "y" to confirm the database drop.
*Delete the moodledata directory. If you, or your users, have uploaded materials into this directory take a copy of these before deleting this directory.
*Delete the moodle directory itself. This will delete all of the moodle PHP script files.

==Migrating Moodle to a new site or server==
Migrating Moodle means that you have to move the current installation to a new server, and so may have to change IP addresses or DNS entries. To do this you will need to change the $CFG->wwwroot value in the config.php on the new server. You will also have to change any absolute links stored in the database backup file (before restoring the file on the new server) either using the admin/replace.php script, your text editor or another "search and replace" tool, e.g. sed. For more details see the [[Moodle_migration | Moodle Migration]] page.

[[#top|Top]]
==Why does my new installation display correctly on the server, but when I view it from a different machine, styles and images are missing?==
In the installation instructions, one of the suggested settings for 'webroot' is 'localhost'. This is fine if all you want to do is some local testing of your new Moodle installation. If, however, you want to view your new installation from another machine on the same local area network, or view your site on the internet, you will have to change this setting:
*For local testing, 'localhost' is fine for the webroot ($CFG->wwwroot in config.php).
*If you want to test your site from other machines on the same local area network (LAN), then you will have to use the private ip address of the serving machine, (e.g. 192.168.1.2/moodle) or the network name of the serving computer (e.g. network_name_of_serving_machine/moodle) as the web root. Depending on your LAN setup, it may be better to use the network name of the computer rather than its (private) ip address, because the ip address can and will change from time to time. If you don't want to use the network name, then you will have to speak to your network administrator and have them assign a permanent ip address to the serving machine.
*Finally, if you want to test your new installation across the internet, you will have to use either a domain name or a permanent (public) ip address/moodle as your web root. To handle both types of access, see [https://docs.moodle.org/en/masquerading masquerading].

[[#top|Top]]
==Maximum upload file size - how to change it?==
There are several places to change the maximum file upload size. The first place to check is the Administration block. Security -> Site Policies -> and look for "Maximum Uploaded File Size". This is the "maxbyte" variable found in older versions of Moodle (under Admin > Variables). Teachers may also set the maximum file size by the [[Course_settings#Maximum_upload_size|course administration block]].

If the above does not provide a large enough figure you will need to make changes in your server settings. The usual place is in your php.ini file (go to Site administration > Server > PHPinfo and check a few lines down for its location). Look for settings '''upload_max_filesize''' and '''post_max_size''', setting them both to your desired new value (e.g. '64MB'). You will need to restart the web server for these changes to take effect - e.g. on Linux, '''/etc/init.d/apache2 force-reload'''. Check your documentation or just reboot the server.

For more help see:
*[[Administration_FAQ#How_do_the_limits_on_uploaded_files_work.3F]]
*[[Installing_Moodle#Recheck_PHP_settings]]
*[[Installing_Moodle#Using_a_.htaccess_file_for_webserver_and_PHP_settings]]
*[[Site_policies#Maximum_uploaded_file_size]]
*These forum posts: http://moodle.org/mod/forum/discuss.php?d=63840#287960 and http://moodle.org/mod/forum/discuss.php?d=93882#p414650

[[#top|Top]]

==Moodle claims PHP float handling is not compatible==

The symptom is that when you try to install or upgrade your Moodle, you get a message "Detected unexpected problem in handling of PHP float numbers".

[http://moodle.org/mod/forum/discuss.php?d=114945 This forum thread] and MDL-18253 have more information. In short, this problem should not happen, you can help us by telling posting information about exactly which version of PHP, and OS you are using. That may let us find a way to work around this problem.

You may be able to solve this issue by installing a more recent PHP versions. If you compile PHP yourself from source, changing the compilation options may help. However, since we don't understand the cause, we don't really know. If you do find a solution that works for you, please do tell us about it.

Update: we have a guess that the problem may be the [http://au2.php.net/manual/en/ini.core.php#ini.precision 'precision' setting in your php.ini file]. In a default PHP install this is set of 14. On at least one server that exhibited this problem it had been changed to a smaller value. So, if you see this problem, please try adding
ini_set('precision', 14);
to your config.php file, and report your success in MDL-18253.

==When upgrading Moodle claims my database is not UTF8 when I'm sure it is==

The symptom is that you are upgrading a post-1.6 Moodle to a newer version. The Environment check tells you that your database is not UTF8 and refuses to upgrade.

The database may not have it's character encoding set quite correctly. You can safely try this command on the database (mySQL):

ALTER DATABASE moodle DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;

(Change 'moodle' for the name of your database). You need to copy this into your MySQL client program that comes packaged with it.

Alternatively, you maybe adding a new clean install Moodle version to an existing web server and the UTF8 check error will not allow you to proceed. Use [[phpMyAdmin]] to help you. This web client is available as a plugin for Moodle or through your web hosting control panel. Using this program, create an empty database (for example moodle199) and make sure "MySQL connection collation" is a utf8 entry, such as utf8_general_ci. Go back to the Moodle installation screen with the check error, hit the previous button on the bottom and make sure the databae has the same name as your new empty database (for example moodle199).

If your Moodle site is version 1.5 or older then it's telling the truth.

[[#top|Top]]

== How do I run multiple instances of Moodle without duplicating base code? ==

See [http://moodle.org/mod/forum/discuss.php?d=13211 this thread] for a detailed explanation by [[User:Martin_Langhoff| Martin Langhoff]].

== What is FreeTDS and how can I use it in my installation? ==
[[FreeTDS]] is an open source implementation of the Tabular Data Stream protocol used by Microsoft SQL Server and Sybase for their databases. Unfortunately, Microsoft servers don't usually accept TDS 5.0 connections. FreeTDS allows your Unix/Linux applications to talk to these other database products and import and export data between different systems successfully.

== How do I install a plugin? ==

Please see [[Installing plugins]].

==I can't enable a plugin on the Plugins overview page because the icon is not clickable==
The open and closed eye icon on the Plugins overview page is simply there to show whether or not a plugin is enabled. You can't edit plugins from this screen. If you wish to enable a plugin, to to the appropriate page for managing the type of plugin you need, for instance ''Settings>Site administration>Plugins>Repositories>Manage repositories'' or ''Settings>Site administration>Plugins>Activity modules>Manage activities.''

== See also ==

* [[Errors FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration FAQ]]
* Installing Moodle in a shared web hosting environment
** [https://docs.moodle.org/24/en/Finding_and_Selecting_A_Web_Host Finding and Selecting a web host]
** [https://docs.moodle.org/24/en/Install_Moodle2.2_on_godaddy Installing on GoDaddy]
** [https://docs.moodle.org/24/en/Installing_Moodle_on_SmarterASP.NET Installing Moodle on SmarterASP.NET web hosting]

[[Category:FAQ]]

[[es:FAQ Instalación]]
[[fr:FAQ d'installation]]
[[ja:インストールFAQ]]
[[de:Installation FAQ]]

Admin tools

2013-07-24T12:09:21Z

ColinFraser:

{{Managing a Moodle site}}
The following admin tools can be managed by an administrator in ''Settings > Site administration > Plugins > Admin tools > Manage admin tools''.

*[[:dev:Acceptance testing]] (new in 2.5)
*[[Installing add-ons|Add-on installer]] (new in 2.5)
*[[Upgrade tool|Assignment upgrade helper]]
*[[Permissions|Capability overview]] - in ''Site Administration > Users > Permissions > Capability report''
*[[Migration from MyISAM to InnoDB|Convert to InnoDB]]
*[[Database transfer]]
*[[Search and replace|DB search and replace]]
*Health center
*[[Language customization]] in ''Settings > Site administration > Language> Language customization''
*[[Language packs]] in ''Settings > Site administration > Language > Language packs''
*Multilang upgrade
*[[:dev:PHPUnit|PHPUnit tests]]
*[[:dev:Profiling PHP|Profiling runs]]
*[[Question engine upgrade helper]]
*Random course generator
*[[Reducing spam in Moodle|Spam cleaner]] in ''Settings > Site administration > Reports > Spam cleaner''
*[[Location|Timezones updater]] in ''Settings > Site administration > Location > Update timezones''
*[[Roles settings|Unsupported role assignments]] in ''Settings > Site administration > Users > Permissions > Unsupported role assignments''
*[[Upload users|User upload]] in ''Settings > Site administration > Users > Accounts > Upload users''
*[[:dev:XMLDB editor|XMLDB editor]] in ''Site administration > Development > XMLDB editor''

==What kind of technical skills do I need to take on Moodle Administration?==
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. If you need them, you will pick these skills up as you go, and if you already have any programming skills, it is going to be fairly easy to do so. If you have never done any programming before, it is a little more difficult, but once you have the idea, it becomes a lot easier. Unless you intend on developing your Moodle, e.g. build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things available, useful plugins and extra blocks and so on, but the majority of those things are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to make things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

==See also==

*[[:dev:Admin tools|Admin tools developer documentation]]
* MDL-29029

[[Category:Site administration]]

[[es:Herramientas administrativas]]

Talk:Table of Contents

2012-10-25T10:52:33Z

ColinFraser: Created page with "==='''Page layout'''=== The layout of this page is not good. While it is linear, it becomes a long scroll to the bottom of the page. Perhaps each part could be in a multi-columne..."

==='''Page layout'''===
The layout of this page is not good. While it is linear, it becomes a long scroll to the bottom of the page. Perhaps each part could be in a multi-columned table? Each group of topics would be in its own cell. Would make it easier to find something.

Backup and restore FAQ

2012-10-21T11:47:24Z

ColinFraser: /* Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict" */

{{Backup}}
==How do I backup a course?==

See [[Course backup]] and [[Automated backup setup]].

==How do I restore a course?==

See [[Course restore]].

==How do I backup my site?==

See [[Site backup]].

==What are the pros and cons of course versus site backups?==

[[Site backup|Site backups]] are recommended in order to have all data saved with the best confidence and the shortest recovery time.

For a site administrator, [[Automated course backup|automated course backups]] are more expensive in terms of time, CPU usage and storage. The recovery time to have a site running again takes longer than a site backup. However, teachers and site administrators might find a course backups as a way to create a "fresh" copy of a course that can be re-used (in older versions of Moodle, in newer versions see [[Import course data]]) or as a method to distribute a course(s) to other Moodle sites.

==Why is my automated course backup much smaller in size than my manual course backup?==

This is an intentional design decision. Because of the way files are stored in Moodle 2.x, there is no need to include the files in the backup if you are planning to restore them to the same Moodle site. Leaving them out saves huge amounts of disc space and makes the backup procedure much faster.

==What data is not contained in course backups?==

By selecting all the options when setting up the backup you can include almost all the data in the course. However you should be aware of the fact that some things are not backed up:
* Quiz questions are only backed up if at least one question from their category has been added to a quiz.
* Scales are only backed up if they are used by at least one activity.
* Users' passwords are not backed up when the "Include enrolled users" option is selected.

==Why is there no "all/none" feature when selecting items to backup?==
This was enabled in MDL-32705 and is available in Moodle 2.3.2 onwards.

==The process ends with: "Error: An error occurred deleting old backup data". What should I do?==

This part of the backup (or restore) procedure tries to delete old info, used in previous executions, performing the following tasks:

# Delete old records from "backup_ids" table: Check the table exists, repair it and try again.
# Delete old records from "backup_files" table: Check the table exists, repair it and try again.
# Delete old files from "moodledata/temp/backup": Delete the dir completely and try again.

[[Image:BackupProblem.gif|thumb|Backup error message]]For points 1 & 2, there are various ways of repairing tables, including using MySQL Admin.
For point 3 see below:

The error message states that the "directory not empty" and gives the path to that directory. If you go there with an FTP program you can see what is there and clean up. It could be just some empty subfolders that were leftover. Deleting these has been able to help. One can also delete the dir "moodledata/temp/backup" completely. That can take a bit longer but may solve several problems at once.

==The process ends with: "XML error: not well-formed (invalid token) at line YYYY". What can I do?==

This problem can appear at any point in the restore process. It's caused when the XML parser detects something incorrect in the backup file that prevent correct operation. Usually, it's caused by some "illegal" characters added in the original course due to some copy/paste of text containing them (control characters, or invalid sequences...).

The best method to handle this issue is:

* Unzip the problematic backup file under one empty folder.

* Open the moodle.xml with Firefox. It will show you where (exact char) the problem is happening.

* Edit the moodle.xml file with some UTF8-compatible editor and delete such characters. Save changes.

* Test the moodle.xml file again with Firefox until no error was displayed.

* Zip everything again (all the folder contents but not the folder itself!).

* Restore the course. It should work now.

* Restore still not working? See the next question.

Also, if possible, it's highly recommended to solve those problems in the original course too from Moodle itself. Once "repaired" there, problems will be out if you create new backup files in the future.

==The process ends with: "moodle xml not found at root level of zip file". What can I do?==
If you are restoring from a zip file backup make sure the moodle.xml file is at the root level. To ensure this:
#Unzip the backup file of the course (example: mycourse.zip)
#Once the file is unzipped, open the folder (example: mycourse).
#Select the folders within the mycourse folder AND the moodle.xml file and create a zip of those item (example: mycourse_new.zip)
#Upload the new zip file (example: mycourse_new.zip) and restore from that.

If the backup file is guaranteed to be correct, check paths to external files (zip, unzip). Incorrect settings also lead to this error message (see the Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=140355 moodle.xml not found in root...] and MDL-14812).

==The process ends with: "An error occurred while copying the zip file..."==

This problem is most likely caused by a permissions issue in the destination directory. Backup files are copied to "XXX/backupdata" under your dataroot directory (where XXX is the id of the course being backed up).

On Windows systems, if you have configured Moodle to use an external zip program then the IIS IUSR_computername user needs to have Execute access to cmd.exe so that it can run the zip program. See the Note in [https://docs.moodle.org/en/System_paths#Path_to_zip Path to zip] for more details.

The problem could also be caused by a disk being full, though this is far less likely.

To obtain precise information about what's happening, you can enable debug messages in ''Administration > Server > [[Debugging]]'' (select the maximum level - DEVELOPER) and/or check the web server error logs.

==I Still get an XML error. How can I clean the borked XML file?==

In some cases XML backup files may contain characters causing the restore process to abort, even after the steps described in the previous question. In such cases you may want to try the following:

* Download the [http://repository.atlassian.com/atlassian-xml-cleaner/jars/atlassian-xml-cleaner-0.1.jar Atlassian XML Cleaner Utility] from the [http://confluence.atlassian.com/display/JIRA/Removing+invalid+characters+from+XML+backups JIRA Atlassian site].

* Unzip the problematic Moodle backup file under one empty folder. Moodle will create the course file folders as long as the unclean moodle.xml file. Please unzip using the Moodle unzip feature.

* Rename the unclean moodle.xml file to moodle-unclean.xml.

* If you don't have access to your Moodle server's command prompt, using the Moodle zip feature, zip the moodle-unclean.xml file only, download the zip file locally and unzip it. It is very important to download the xml file in zipped format to avoid unwanted character encoding when transferring from an operating system to another.

* Move the downloaded Atlassian XML Cleaner Utility in the same folder where is your moodle-unclean.xml file.

* Issue the following command from the command prompt:

java -jar atlassian-xml-cleaner-0.1.jar moodle-unclean.xml > moodle.xml

* If you launched the utility on your local computer, zip the just created (and hopefully cleaned) moodle.xml file and upload it in the same place from where you downloaded the moodle-unclean.xml file. Once uploaded, unzip it using the Moodle unzip feature.

* Zip everything again (all the folder contents but the folder itself!).

* Restore the course. It should work now.

==What does "Some of your courses weren't saved!!" mean?==

There are three possible causes of this problem:
# Error - this happens when the backup procedure has found an error and so hasn't finished the backup of a particular course. These are "controlled" errors and the scheduled backup continues with the next course.
# Unfinished - this happens when the backup procedure dies without knowing why. When the cron is next executed it detects that the last execution went wrong, and continues skipping the problematic course. A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), or if there is some exact point were all the courses are breaking (generally internal zip libraries, try to switch to external executables instead).
# Skipped - this happens when a course is unavailable to students and has not been changed in the last month (31 days). This isn't an error situation - it's a feature, especially useful for sites with many unavailable old courses, saving process time.

==Why are some courses being skipped?==

Course backups automatically skip courses which are unavailable to students and have not been changed in the last month.

The [http://moodle.org/mod/forum/discuss.php?d=80367#p714733 Hide courses excluded from automatic backup] discussion in the Using Moodle forum describes a way that you can disable or override this thirty day check. This could be useful if, for example, you wanted to change the period from thirty days to six months.

==Why does restore stop, rather than completing?==

Attempting to restore a course to an older version of Moodle than the one the course was backed up on can result in the restore process failing to complete. To ensure a successful restore, make sure that the version of Moodle you are restoring the course to is the same, or newer, than the one the course was backed up on.

If it stop unexpectedly with no errors shown try again with [[Debugging]] switched on. Any errors you now see can help experts in the support forums diagnose your problem. You can also check the discussion links in the See also section below for further advice.

==Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict"==

[[Image:Moodle 2.0 Restore breaks.png|thumb|Error message in Moodle 2.0]]

This message is displayed when:

# Your target site has one xxxx user (xxxx being the username)
# The backup being restored also has one xxxx user
# After various comparisons, Moodle has detected that the xxxx user in 1. and the xxxx user in 2. aren't the same user.

If 1, 2 and 3 above happens, restore stops before performing any action as far as restoring that user will end associating "things" (create activities, posts, attempts... whatever...) to the xxxx user in the target site, when those "things" weren't performed by the same user at all.

Those checks and behaviour were introduced in Moodle 1.9.x and continue being valid under 2.0. Usually the xxxx user in the messages is the "admin" user (that exists in practically all Moodle installations).

There are two possible solutions to make both xxxx users in 1 and 2 to match (and avoid the conflict):

a) Modify the backup's '''users.xml''' file and make the ''email'' or ''firstaccess'' fields match with the ones in target site. 
b) Modify the '''target site''' and set the user ''email'' or ''firstaccess'' fields to match with the ones in backup's user.xml file.

Method a) is recommended so the restore process will match both xxxx users and every "thing" in the backup file belonging to xxxx will be associated to the already existing xxxx user in the target site.

'''NOTE:''' When using method a) be aware that the ''moodle-filename-backup.'''mbz''''' is a zip file and can be renamed to ''moodle-filename-backup.'''zip''''' and unzipped.
When editing is complete, rezip and then rename using the original file name with the "*.mbz" extention.

==Why are certain course links broken in a restored course?==

Inter-activity links must be absolute (full) URLs e.g. <code><nowiki>http://site.com/mod/resource/view.php?id=xxx</nowiki></code> in order to be processed properly during backup and restore.

Any relative URLs e.g. <code>/mod/resource/view.php?id=xxx</code>, <code>../resource/view.php?id=xxx</code> or <code>view.php?id=xxx</code> will result in broken links when the course is restored.

== See also ==

*Using Moodle [http://moodle.org/mod/forum/view.php?f=128 Backup and Restore forum]
*[http://www.databasejournal.com/features/mysql/article.php/10897_3300511_2 databasejournal.com article on repairing database corruption in MySQL]
* [[Site backup]]
* [[Moodle migration]]
* [[Beginning Moodle 2.0 Administration]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=142720 Trying to restore user 'admin' from backup file will cause conflict]
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]

[[Category:FAQ]]

[[es:FAQ Backup]]
[[pl:Backup FAQ]]
[[fr:FAQ de sauvegarde]]
[[ja:バックアップFAQ]]
[[pt:FAQ sobre cópias de segurança]]

Backup and restore FAQ

2012-10-21T11:47:06Z

ColinFraser: /* Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict" */

{{Backup}}
==How do I backup a course?==

See [[Course backup]] and [[Automated backup setup]].

==How do I restore a course?==

See [[Course restore]].

==How do I backup my site?==

See [[Site backup]].

==What are the pros and cons of course versus site backups?==

[[Site backup|Site backups]] are recommended in order to have all data saved with the best confidence and the shortest recovery time.

For a site administrator, [[Automated course backup|automated course backups]] are more expensive in terms of time, CPU usage and storage. The recovery time to have a site running again takes longer than a site backup. However, teachers and site administrators might find a course backups as a way to create a "fresh" copy of a course that can be re-used (in older versions of Moodle, in newer versions see [[Import course data]]) or as a method to distribute a course(s) to other Moodle sites.

==Why is my automated course backup much smaller in size than my manual course backup?==

This is an intentional design decision. Because of the way files are stored in Moodle 2.x, there is no need to include the files in the backup if you are planning to restore them to the same Moodle site. Leaving them out saves huge amounts of disc space and makes the backup procedure much faster.

==What data is not contained in course backups?==

By selecting all the options when setting up the backup you can include almost all the data in the course. However you should be aware of the fact that some things are not backed up:
* Quiz questions are only backed up if at least one question from their category has been added to a quiz.
* Scales are only backed up if they are used by at least one activity.
* Users' passwords are not backed up when the "Include enrolled users" option is selected.

==Why is there no "all/none" feature when selecting items to backup?==
This was enabled in MDL-32705 and is available in Moodle 2.3.2 onwards.

==The process ends with: "Error: An error occurred deleting old backup data". What should I do?==

This part of the backup (or restore) procedure tries to delete old info, used in previous executions, performing the following tasks:

# Delete old records from "backup_ids" table: Check the table exists, repair it and try again.
# Delete old records from "backup_files" table: Check the table exists, repair it and try again.
# Delete old files from "moodledata/temp/backup": Delete the dir completely and try again.

[[Image:BackupProblem.gif|thumb|Backup error message]]For points 1 & 2, there are various ways of repairing tables, including using MySQL Admin.
For point 3 see below:

The error message states that the "directory not empty" and gives the path to that directory. If you go there with an FTP program you can see what is there and clean up. It could be just some empty subfolders that were leftover. Deleting these has been able to help. One can also delete the dir "moodledata/temp/backup" completely. That can take a bit longer but may solve several problems at once.

==The process ends with: "XML error: not well-formed (invalid token) at line YYYY". What can I do?==

This problem can appear at any point in the restore process. It's caused when the XML parser detects something incorrect in the backup file that prevent correct operation. Usually, it's caused by some "illegal" characters added in the original course due to some copy/paste of text containing them (control characters, or invalid sequences...).

The best method to handle this issue is:

* Unzip the problematic backup file under one empty folder.

* Open the moodle.xml with Firefox. It will show you where (exact char) the problem is happening.

* Edit the moodle.xml file with some UTF8-compatible editor and delete such characters. Save changes.

* Test the moodle.xml file again with Firefox until no error was displayed.

* Zip everything again (all the folder contents but not the folder itself!).

* Restore the course. It should work now.

* Restore still not working? See the next question.

Also, if possible, it's highly recommended to solve those problems in the original course too from Moodle itself. Once "repaired" there, problems will be out if you create new backup files in the future.

==The process ends with: "moodle xml not found at root level of zip file". What can I do?==
If you are restoring from a zip file backup make sure the moodle.xml file is at the root level. To ensure this:
#Unzip the backup file of the course (example: mycourse.zip)
#Once the file is unzipped, open the folder (example: mycourse).
#Select the folders within the mycourse folder AND the moodle.xml file and create a zip of those item (example: mycourse_new.zip)
#Upload the new zip file (example: mycourse_new.zip) and restore from that.

If the backup file is guaranteed to be correct, check paths to external files (zip, unzip). Incorrect settings also lead to this error message (see the Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=140355 moodle.xml not found in root...] and MDL-14812).

==The process ends with: "An error occurred while copying the zip file..."==

This problem is most likely caused by a permissions issue in the destination directory. Backup files are copied to "XXX/backupdata" under your dataroot directory (where XXX is the id of the course being backed up).

On Windows systems, if you have configured Moodle to use an external zip program then the IIS IUSR_computername user needs to have Execute access to cmd.exe so that it can run the zip program. See the Note in [https://docs.moodle.org/en/System_paths#Path_to_zip Path to zip] for more details.

The problem could also be caused by a disk being full, though this is far less likely.

To obtain precise information about what's happening, you can enable debug messages in ''Administration > Server > [[Debugging]]'' (select the maximum level - DEVELOPER) and/or check the web server error logs.

==I Still get an XML error. How can I clean the borked XML file?==

In some cases XML backup files may contain characters causing the restore process to abort, even after the steps described in the previous question. In such cases you may want to try the following:

* Download the [http://repository.atlassian.com/atlassian-xml-cleaner/jars/atlassian-xml-cleaner-0.1.jar Atlassian XML Cleaner Utility] from the [http://confluence.atlassian.com/display/JIRA/Removing+invalid+characters+from+XML+backups JIRA Atlassian site].

* Unzip the problematic Moodle backup file under one empty folder. Moodle will create the course file folders as long as the unclean moodle.xml file. Please unzip using the Moodle unzip feature.

* Rename the unclean moodle.xml file to moodle-unclean.xml.

* If you don't have access to your Moodle server's command prompt, using the Moodle zip feature, zip the moodle-unclean.xml file only, download the zip file locally and unzip it. It is very important to download the xml file in zipped format to avoid unwanted character encoding when transferring from an operating system to another.

* Move the downloaded Atlassian XML Cleaner Utility in the same folder where is your moodle-unclean.xml file.

* Issue the following command from the command prompt:

java -jar atlassian-xml-cleaner-0.1.jar moodle-unclean.xml > moodle.xml

* If you launched the utility on your local computer, zip the just created (and hopefully cleaned) moodle.xml file and upload it in the same place from where you downloaded the moodle-unclean.xml file. Once uploaded, unzip it using the Moodle unzip feature.

* Zip everything again (all the folder contents but the folder itself!).

* Restore the course. It should work now.

==What does "Some of your courses weren't saved!!" mean?==

There are three possible causes of this problem:
# Error - this happens when the backup procedure has found an error and so hasn't finished the backup of a particular course. These are "controlled" errors and the scheduled backup continues with the next course.
# Unfinished - this happens when the backup procedure dies without knowing why. When the cron is next executed it detects that the last execution went wrong, and continues skipping the problematic course. A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), or if there is some exact point were all the courses are breaking (generally internal zip libraries, try to switch to external executables instead).
# Skipped - this happens when a course is unavailable to students and has not been changed in the last month (31 days). This isn't an error situation - it's a feature, especially useful for sites with many unavailable old courses, saving process time.

==Why are some courses being skipped?==

Course backups automatically skip courses which are unavailable to students and have not been changed in the last month.

The [http://moodle.org/mod/forum/discuss.php?d=80367#p714733 Hide courses excluded from automatic backup] discussion in the Using Moodle forum describes a way that you can disable or override this thirty day check. This could be useful if, for example, you wanted to change the period from thirty days to six months.

==Why does restore stop, rather than completing?==

Attempting to restore a course to an older version of Moodle than the one the course was backed up on can result in the restore process failing to complete. To ensure a successful restore, make sure that the version of Moodle you are restoring the course to is the same, or newer, than the one the course was backed up on.

If it stop unexpectedly with no errors shown try again with [[Debugging]] switched on. Any errors you now see can help experts in the support forums diagnose your problem. You can also check the discussion links in the See also section below for further advice.

==Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict"==

[[Image:Moodle 2.0 Restore breaks.png|thumb|Error message in Moodle 2.0]]

This message is displayed when:

# Your target site has one xxxx user (xxxx being the username)
# The backup being restored also has one xxxx user
# After various comparisons, Moodle has detected that the xxxx user in 1. and the xxxx user in 2. aren't the same user.

If 1, 2 and 3 above happens, restore stops before performing any action as far as restoring that user will end associating "things" (create activities, posts, attempts... whatever...) to the xxxx user in the target site, when those "things" weren't performed by the same user at all.

Those checks and behaviour were introduced in Moodle 1.9.x and continue being valid under 2.0. Usually the xxxx user in the messages is the "admin" user (that exists in practically all Moodle installations).

There are two possible solutions to make both xxxx users in 1 and 2 to match (and avoid the conflict):

a) Modify the backup's '''users.xml''' file and make the ''email'' or ''firstaccess'' fields match with the ones in target site. 
b) Modify the '''target site''' and set the user ''email'' or ''firstaccess'' fields to match with the ones in backup's user.xml file.

Method a) is recommended so the restore process will match both xxxx users and every "thing" in the backup file belonging to xxxx will be associated to the already existing xxxx user in the target site.

'''NOTE:''' When using method a) be aware that the ''moodle-filename-backup.'''mbz''''' is a zip file and can be renamed to ''moodle-filename-backup.'''zip''''' and unzipped.
When editing complete, rezip and then rename using the original file name with the "*.mbz" extention.

==Why are certain course links broken in a restored course?==

Inter-activity links must be absolute (full) URLs e.g. <code><nowiki>http://site.com/mod/resource/view.php?id=xxx</nowiki></code> in order to be processed properly during backup and restore.

Any relative URLs e.g. <code>/mod/resource/view.php?id=xxx</code>, <code>../resource/view.php?id=xxx</code> or <code>view.php?id=xxx</code> will result in broken links when the course is restored.

== See also ==

*Using Moodle [http://moodle.org/mod/forum/view.php?f=128 Backup and Restore forum]
*[http://www.databasejournal.com/features/mysql/article.php/10897_3300511_2 databasejournal.com article on repairing database corruption in MySQL]
* [[Site backup]]
* [[Moodle migration]]
* [[Beginning Moodle 2.0 Administration]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=142720 Trying to restore user 'admin' from backup file will cause conflict]
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]

[[Category:FAQ]]

[[es:FAQ Backup]]
[[pl:Backup FAQ]]
[[fr:FAQ de sauvegarde]]
[[ja:バックアップFAQ]]
[[pt:FAQ sobre cópias de segurança]]

Backup and restore FAQ

2012-10-21T11:46:30Z

ColinFraser: /* Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict" */

{{Backup}}
==How do I backup a course?==

See [[Course backup]] and [[Automated backup setup]].

==How do I restore a course?==

See [[Course restore]].

==How do I backup my site?==

See [[Site backup]].

==What are the pros and cons of course versus site backups?==

[[Site backup|Site backups]] are recommended in order to have all data saved with the best confidence and the shortest recovery time.

For a site administrator, [[Automated course backup|automated course backups]] are more expensive in terms of time, CPU usage and storage. The recovery time to have a site running again takes longer than a site backup. However, teachers and site administrators might find a course backups as a way to create a "fresh" copy of a course that can be re-used (in older versions of Moodle, in newer versions see [[Import course data]]) or as a method to distribute a course(s) to other Moodle sites.

==Why is my automated course backup much smaller in size than my manual course backup?==

This is an intentional design decision. Because of the way files are stored in Moodle 2.x, there is no need to include the files in the backup if you are planning to restore them to the same Moodle site. Leaving them out saves huge amounts of disc space and makes the backup procedure much faster.

==What data is not contained in course backups?==

By selecting all the options when setting up the backup you can include almost all the data in the course. However you should be aware of the fact that some things are not backed up:
* Quiz questions are only backed up if at least one question from their category has been added to a quiz.
* Scales are only backed up if they are used by at least one activity.
* Users' passwords are not backed up when the "Include enrolled users" option is selected.

==Why is there no "all/none" feature when selecting items to backup?==
This was enabled in MDL-32705 and is available in Moodle 2.3.2 onwards.

==The process ends with: "Error: An error occurred deleting old backup data". What should I do?==

This part of the backup (or restore) procedure tries to delete old info, used in previous executions, performing the following tasks:

# Delete old records from "backup_ids" table: Check the table exists, repair it and try again.
# Delete old records from "backup_files" table: Check the table exists, repair it and try again.
# Delete old files from "moodledata/temp/backup": Delete the dir completely and try again.

[[Image:BackupProblem.gif|thumb|Backup error message]]For points 1 & 2, there are various ways of repairing tables, including using MySQL Admin.
For point 3 see below:

The error message states that the "directory not empty" and gives the path to that directory. If you go there with an FTP program you can see what is there and clean up. It could be just some empty subfolders that were leftover. Deleting these has been able to help. One can also delete the dir "moodledata/temp/backup" completely. That can take a bit longer but may solve several problems at once.

==The process ends with: "XML error: not well-formed (invalid token) at line YYYY". What can I do?==

This problem can appear at any point in the restore process. It's caused when the XML parser detects something incorrect in the backup file that prevent correct operation. Usually, it's caused by some "illegal" characters added in the original course due to some copy/paste of text containing them (control characters, or invalid sequences...).

The best method to handle this issue is:

* Unzip the problematic backup file under one empty folder.

* Open the moodle.xml with Firefox. It will show you where (exact char) the problem is happening.

* Edit the moodle.xml file with some UTF8-compatible editor and delete such characters. Save changes.

* Test the moodle.xml file again with Firefox until no error was displayed.

* Zip everything again (all the folder contents but not the folder itself!).

* Restore the course. It should work now.

* Restore still not working? See the next question.

Also, if possible, it's highly recommended to solve those problems in the original course too from Moodle itself. Once "repaired" there, problems will be out if you create new backup files in the future.

==The process ends with: "moodle xml not found at root level of zip file". What can I do?==
If you are restoring from a zip file backup make sure the moodle.xml file is at the root level. To ensure this:
#Unzip the backup file of the course (example: mycourse.zip)
#Once the file is unzipped, open the folder (example: mycourse).
#Select the folders within the mycourse folder AND the moodle.xml file and create a zip of those item (example: mycourse_new.zip)
#Upload the new zip file (example: mycourse_new.zip) and restore from that.

If the backup file is guaranteed to be correct, check paths to external files (zip, unzip). Incorrect settings also lead to this error message (see the Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=140355 moodle.xml not found in root...] and MDL-14812).

==The process ends with: "An error occurred while copying the zip file..."==

This problem is most likely caused by a permissions issue in the destination directory. Backup files are copied to "XXX/backupdata" under your dataroot directory (where XXX is the id of the course being backed up).

On Windows systems, if you have configured Moodle to use an external zip program then the IIS IUSR_computername user needs to have Execute access to cmd.exe so that it can run the zip program. See the Note in [https://docs.moodle.org/en/System_paths#Path_to_zip Path to zip] for more details.

The problem could also be caused by a disk being full, though this is far less likely.

To obtain precise information about what's happening, you can enable debug messages in ''Administration > Server > [[Debugging]]'' (select the maximum level - DEVELOPER) and/or check the web server error logs.

==I Still get an XML error. How can I clean the borked XML file?==

In some cases XML backup files may contain characters causing the restore process to abort, even after the steps described in the previous question. In such cases you may want to try the following:

* Download the [http://repository.atlassian.com/atlassian-xml-cleaner/jars/atlassian-xml-cleaner-0.1.jar Atlassian XML Cleaner Utility] from the [http://confluence.atlassian.com/display/JIRA/Removing+invalid+characters+from+XML+backups JIRA Atlassian site].

* Unzip the problematic Moodle backup file under one empty folder. Moodle will create the course file folders as long as the unclean moodle.xml file. Please unzip using the Moodle unzip feature.

* Rename the unclean moodle.xml file to moodle-unclean.xml.

* If you don't have access to your Moodle server's command prompt, using the Moodle zip feature, zip the moodle-unclean.xml file only, download the zip file locally and unzip it. It is very important to download the xml file in zipped format to avoid unwanted character encoding when transferring from an operating system to another.

* Move the downloaded Atlassian XML Cleaner Utility in the same folder where is your moodle-unclean.xml file.

* Issue the following command from the command prompt:

java -jar atlassian-xml-cleaner-0.1.jar moodle-unclean.xml > moodle.xml

* If you launched the utility on your local computer, zip the just created (and hopefully cleaned) moodle.xml file and upload it in the same place from where you downloaded the moodle-unclean.xml file. Once uploaded, unzip it using the Moodle unzip feature.

* Zip everything again (all the folder contents but the folder itself!).

* Restore the course. It should work now.

==What does "Some of your courses weren't saved!!" mean?==

There are three possible causes of this problem:
# Error - this happens when the backup procedure has found an error and so hasn't finished the backup of a particular course. These are "controlled" errors and the scheduled backup continues with the next course.
# Unfinished - this happens when the backup procedure dies without knowing why. When the cron is next executed it detects that the last execution went wrong, and continues skipping the problematic course. A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), or if there is some exact point were all the courses are breaking (generally internal zip libraries, try to switch to external executables instead).
# Skipped - this happens when a course is unavailable to students and has not been changed in the last month (31 days). This isn't an error situation - it's a feature, especially useful for sites with many unavailable old courses, saving process time.

==Why are some courses being skipped?==

Course backups automatically skip courses which are unavailable to students and have not been changed in the last month.

The [http://moodle.org/mod/forum/discuss.php?d=80367#p714733 Hide courses excluded from automatic backup] discussion in the Using Moodle forum describes a way that you can disable or override this thirty day check. This could be useful if, for example, you wanted to change the period from thirty days to six months.

==Why does restore stop, rather than completing?==

Attempting to restore a course to an older version of Moodle than the one the course was backed up on can result in the restore process failing to complete. To ensure a successful restore, make sure that the version of Moodle you are restoring the course to is the same, or newer, than the one the course was backed up on.

If it stop unexpectedly with no errors shown try again with [[Debugging]] switched on. Any errors you now see can help experts in the support forums diagnose your problem. You can also check the discussion links in the See also section below for further advice.

==Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict"==

[[Image:Moodle 2.0 Restore breaks.png|thumb|Error message in Moodle 2.0]]

This message is displayed when:

# Your target site has one xxxx user (xxxx being the username)
# The backup being restored also has one xxxx user
# After various comparisons, Moodle has detected that the xxxx user in 1. and the xxxx user in 2. aren't the same user.

If 1, 2 and 3 above happens, restore stops before performing any action as far as restoring that user will end associating "things" (create activities, posts, attempts... whatever...) to the xxxx user in the target site, when those "things" weren't performed by the same user at all.

Those checks and behaviour were introduced in Moodle 1.9.x and continue being valid under 2.0. Usually the xxxx user in the messages is the "admin" user (that exists in practically all Moodle installations).

There are two possible solutions to make both xxxx users in 1 and 2 to match (and avoid the conflict):

a) Modify the backup's '''users.xml''' file and make the ''email'' or ''firstaccess'' fields match with the ones in target site. 
b) Modify the '''target site''' and set the user ''email'' or ''firstaccess'' fields to match with the ones in backup's user.xml file.

Method a) is recommended so the restore process will match both xxxx users and every "thing" in the backup file belonging to xxxx will be associated to the already existing xxxx user in the target site.

'''NOTE:''' When using method a) be aware that the ''moodle-filename-backup.'''mbz''''' is a zip file and can be renamed to ''moodle-filename-backup.'''zip''''' and unzipped. When editing complete, rezip and then rename using the original file name with the "*.mbz" extention.

==Why are certain course links broken in a restored course?==

Inter-activity links must be absolute (full) URLs e.g. <code><nowiki>http://site.com/mod/resource/view.php?id=xxx</nowiki></code> in order to be processed properly during backup and restore.

Any relative URLs e.g. <code>/mod/resource/view.php?id=xxx</code>, <code>../resource/view.php?id=xxx</code> or <code>view.php?id=xxx</code> will result in broken links when the course is restored.

== See also ==

*Using Moodle [http://moodle.org/mod/forum/view.php?f=128 Backup and Restore forum]
*[http://www.databasejournal.com/features/mysql/article.php/10897_3300511_2 databasejournal.com article on repairing database corruption in MySQL]
* [[Site backup]]
* [[Moodle migration]]
* [[Beginning Moodle 2.0 Administration]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=142720 Trying to restore user 'admin' from backup file will cause conflict]
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]

[[Category:FAQ]]

[[es:FAQ Backup]]
[[pl:Backup FAQ]]
[[fr:FAQ de sauvegarde]]
[[ja:バックアップFAQ]]
[[pt:FAQ sobre cópias de segurança]]

Backup and restore FAQ

2012-10-21T11:45:18Z

ColinFraser: /* Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict" */

{{Backup}}
==How do I backup a course?==

See [[Course backup]] and [[Automated backup setup]].

==How do I restore a course?==

See [[Course restore]].

==How do I backup my site?==

See [[Site backup]].

==What are the pros and cons of course versus site backups?==

[[Site backup|Site backups]] are recommended in order to have all data saved with the best confidence and the shortest recovery time.

For a site administrator, [[Automated course backup|automated course backups]] are more expensive in terms of time, CPU usage and storage. The recovery time to have a site running again takes longer than a site backup. However, teachers and site administrators might find a course backups as a way to create a "fresh" copy of a course that can be re-used (in older versions of Moodle, in newer versions see [[Import course data]]) or as a method to distribute a course(s) to other Moodle sites.

==Why is my automated course backup much smaller in size than my manual course backup?==

This is an intentional design decision. Because of the way files are stored in Moodle 2.x, there is no need to include the files in the backup if you are planning to restore them to the same Moodle site. Leaving them out saves huge amounts of disc space and makes the backup procedure much faster.

==What data is not contained in course backups?==

By selecting all the options when setting up the backup you can include almost all the data in the course. However you should be aware of the fact that some things are not backed up:
* Quiz questions are only backed up if at least one question from their category has been added to a quiz.
* Scales are only backed up if they are used by at least one activity.
* Users' passwords are not backed up when the "Include enrolled users" option is selected.

==Why is there no "all/none" feature when selecting items to backup?==
This was enabled in MDL-32705 and is available in Moodle 2.3.2 onwards.

==The process ends with: "Error: An error occurred deleting old backup data". What should I do?==

This part of the backup (or restore) procedure tries to delete old info, used in previous executions, performing the following tasks:

# Delete old records from "backup_ids" table: Check the table exists, repair it and try again.
# Delete old records from "backup_files" table: Check the table exists, repair it and try again.
# Delete old files from "moodledata/temp/backup": Delete the dir completely and try again.

[[Image:BackupProblem.gif|thumb|Backup error message]]For points 1 & 2, there are various ways of repairing tables, including using MySQL Admin.
For point 3 see below:

The error message states that the "directory not empty" and gives the path to that directory. If you go there with an FTP program you can see what is there and clean up. It could be just some empty subfolders that were leftover. Deleting these has been able to help. One can also delete the dir "moodledata/temp/backup" completely. That can take a bit longer but may solve several problems at once.

==The process ends with: "XML error: not well-formed (invalid token) at line YYYY". What can I do?==

This problem can appear at any point in the restore process. It's caused when the XML parser detects something incorrect in the backup file that prevent correct operation. Usually, it's caused by some "illegal" characters added in the original course due to some copy/paste of text containing them (control characters, or invalid sequences...).

The best method to handle this issue is:

* Unzip the problematic backup file under one empty folder.

* Open the moodle.xml with Firefox. It will show you where (exact char) the problem is happening.

* Edit the moodle.xml file with some UTF8-compatible editor and delete such characters. Save changes.

* Test the moodle.xml file again with Firefox until no error was displayed.

* Zip everything again (all the folder contents but not the folder itself!).

* Restore the course. It should work now.

* Restore still not working? See the next question.

Also, if possible, it's highly recommended to solve those problems in the original course too from Moodle itself. Once "repaired" there, problems will be out if you create new backup files in the future.

==The process ends with: "moodle xml not found at root level of zip file". What can I do?==
If you are restoring from a zip file backup make sure the moodle.xml file is at the root level. To ensure this:
#Unzip the backup file of the course (example: mycourse.zip)
#Once the file is unzipped, open the folder (example: mycourse).
#Select the folders within the mycourse folder AND the moodle.xml file and create a zip of those item (example: mycourse_new.zip)
#Upload the new zip file (example: mycourse_new.zip) and restore from that.

If the backup file is guaranteed to be correct, check paths to external files (zip, unzip). Incorrect settings also lead to this error message (see the Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=140355 moodle.xml not found in root...] and MDL-14812).

==The process ends with: "An error occurred while copying the zip file..."==

This problem is most likely caused by a permissions issue in the destination directory. Backup files are copied to "XXX/backupdata" under your dataroot directory (where XXX is the id of the course being backed up).

On Windows systems, if you have configured Moodle to use an external zip program then the IIS IUSR_computername user needs to have Execute access to cmd.exe so that it can run the zip program. See the Note in [https://docs.moodle.org/en/System_paths#Path_to_zip Path to zip] for more details.

The problem could also be caused by a disk being full, though this is far less likely.

To obtain precise information about what's happening, you can enable debug messages in ''Administration > Server > [[Debugging]]'' (select the maximum level - DEVELOPER) and/or check the web server error logs.

==I Still get an XML error. How can I clean the borked XML file?==

In some cases XML backup files may contain characters causing the restore process to abort, even after the steps described in the previous question. In such cases you may want to try the following:

* Download the [http://repository.atlassian.com/atlassian-xml-cleaner/jars/atlassian-xml-cleaner-0.1.jar Atlassian XML Cleaner Utility] from the [http://confluence.atlassian.com/display/JIRA/Removing+invalid+characters+from+XML+backups JIRA Atlassian site].

* Unzip the problematic Moodle backup file under one empty folder. Moodle will create the course file folders as long as the unclean moodle.xml file. Please unzip using the Moodle unzip feature.

* Rename the unclean moodle.xml file to moodle-unclean.xml.

* If you don't have access to your Moodle server's command prompt, using the Moodle zip feature, zip the moodle-unclean.xml file only, download the zip file locally and unzip it. It is very important to download the xml file in zipped format to avoid unwanted character encoding when transferring from an operating system to another.

* Move the downloaded Atlassian XML Cleaner Utility in the same folder where is your moodle-unclean.xml file.

* Issue the following command from the command prompt:

java -jar atlassian-xml-cleaner-0.1.jar moodle-unclean.xml > moodle.xml

* If you launched the utility on your local computer, zip the just created (and hopefully cleaned) moodle.xml file and upload it in the same place from where you downloaded the moodle-unclean.xml file. Once uploaded, unzip it using the Moodle unzip feature.

* Zip everything again (all the folder contents but the folder itself!).

* Restore the course. It should work now.

==What does "Some of your courses weren't saved!!" mean?==

There are three possible causes of this problem:
# Error - this happens when the backup procedure has found an error and so hasn't finished the backup of a particular course. These are "controlled" errors and the scheduled backup continues with the next course.
# Unfinished - this happens when the backup procedure dies without knowing why. When the cron is next executed it detects that the last execution went wrong, and continues skipping the problematic course. A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), or if there is some exact point were all the courses are breaking (generally internal zip libraries, try to switch to external executables instead).
# Skipped - this happens when a course is unavailable to students and has not been changed in the last month (31 days). This isn't an error situation - it's a feature, especially useful for sites with many unavailable old courses, saving process time.

==Why are some courses being skipped?==

Course backups automatically skip courses which are unavailable to students and have not been changed in the last month.

The [http://moodle.org/mod/forum/discuss.php?d=80367#p714733 Hide courses excluded from automatic backup] discussion in the Using Moodle forum describes a way that you can disable or override this thirty day check. This could be useful if, for example, you wanted to change the period from thirty days to six months.

==Why does restore stop, rather than completing?==

Attempting to restore a course to an older version of Moodle than the one the course was backed up on can result in the restore process failing to complete. To ensure a successful restore, make sure that the version of Moodle you are restoring the course to is the same, or newer, than the one the course was backed up on.

If it stop unexpectedly with no errors shown try again with [[Debugging]] switched on. Any errors you now see can help experts in the support forums diagnose your problem. You can also check the discussion links in the See also section below for further advice.

==Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict"==

[[Image:Moodle 2.0 Restore breaks.png|thumb|Error message in Moodle 2.0]]

This message is displayed when:

# Your target site has one xxxx user (xxxx being the username)
# The backup being restored also has one xxxx user
# After various comparisons, Moodle has detected that the xxxx user in 1. and the xxxx user in 2. aren't the same user.

If 1, 2 and 3 above happens, restore stops before performing any action as far as restoring that user will end associating "things" (create activities, posts, attempts... whatever...) to the xxxx user in the target site, when those "things" weren't performed by the same user at all.

Those checks and behaviour were introduced in Moodle 1.9.x and continue being valid under 2.0. Usually the xxxx user in the messages is the "admin" user (that exists in practically all Moodle installations).

There are two possible solutions to make both xxxx users in 1 and 2 to match (and avoid the conflict):

a) Modify the backup's '''users.xml''' file and make the ''email'' or ''firstaccess'' fields match with the ones in target site. 
b) Modify the '''target site''' and set the user ''email'' or ''firstaccess'' fields to match with the ones in backup's user.xml file.

Method a) is recommended so the restore process will match both xxxx users and every "thing" in the backup file belonging to xxxx will be associated to the already existing xxxx user in the target site.

'''NOTE:''' When using method a) be aware that the ''moodle-filename-backup.mbz'' is a zip file and can be renamed and unzipped. When editing compelte, rezip and then
rename using the original file name with the "*.mbz" extention.

==Why are certain course links broken in a restored course?==

Inter-activity links must be absolute (full) URLs e.g. <code><nowiki>http://site.com/mod/resource/view.php?id=xxx</nowiki></code> in order to be processed properly during backup and restore.

Any relative URLs e.g. <code>/mod/resource/view.php?id=xxx</code>, <code>../resource/view.php?id=xxx</code> or <code>view.php?id=xxx</code> will result in broken links when the course is restored.

== See also ==

*Using Moodle [http://moodle.org/mod/forum/view.php?f=128 Backup and Restore forum]
*[http://www.databasejournal.com/features/mysql/article.php/10897_3300511_2 databasejournal.com article on repairing database corruption in MySQL]
* [[Site backup]]
* [[Moodle migration]]
* [[Beginning Moodle 2.0 Administration]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=142720 Trying to restore user 'admin' from backup file will cause conflict]
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]

[[Category:FAQ]]

[[es:FAQ Backup]]
[[pl:Backup FAQ]]
[[fr:FAQ de sauvegarde]]
[[ja:バックアップFAQ]]
[[pt:FAQ sobre cópias de segurança]]

Backup and restore FAQ

2012-10-21T11:44:47Z

ColinFraser: /* Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict" */

{{Backup}}
==How do I backup a course?==

See [[Course backup]] and [[Automated backup setup]].

==How do I restore a course?==

See [[Course restore]].

==How do I backup my site?==

See [[Site backup]].

==What are the pros and cons of course versus site backups?==

[[Site backup|Site backups]] are recommended in order to have all data saved with the best confidence and the shortest recovery time.

For a site administrator, [[Automated course backup|automated course backups]] are more expensive in terms of time, CPU usage and storage. The recovery time to have a site running again takes longer than a site backup. However, teachers and site administrators might find a course backups as a way to create a "fresh" copy of a course that can be re-used (in older versions of Moodle, in newer versions see [[Import course data]]) or as a method to distribute a course(s) to other Moodle sites.

==Why is my automated course backup much smaller in size than my manual course backup?==

This is an intentional design decision. Because of the way files are stored in Moodle 2.x, there is no need to include the files in the backup if you are planning to restore them to the same Moodle site. Leaving them out saves huge amounts of disc space and makes the backup procedure much faster.

==What data is not contained in course backups?==

By selecting all the options when setting up the backup you can include almost all the data in the course. However you should be aware of the fact that some things are not backed up:
* Quiz questions are only backed up if at least one question from their category has been added to a quiz.
* Scales are only backed up if they are used by at least one activity.
* Users' passwords are not backed up when the "Include enrolled users" option is selected.

==Why is there no "all/none" feature when selecting items to backup?==
This was enabled in MDL-32705 and is available in Moodle 2.3.2 onwards.

==The process ends with: "Error: An error occurred deleting old backup data". What should I do?==

This part of the backup (or restore) procedure tries to delete old info, used in previous executions, performing the following tasks:

# Delete old records from "backup_ids" table: Check the table exists, repair it and try again.
# Delete old records from "backup_files" table: Check the table exists, repair it and try again.
# Delete old files from "moodledata/temp/backup": Delete the dir completely and try again.

[[Image:BackupProblem.gif|thumb|Backup error message]]For points 1 & 2, there are various ways of repairing tables, including using MySQL Admin.
For point 3 see below:

The error message states that the "directory not empty" and gives the path to that directory. If you go there with an FTP program you can see what is there and clean up. It could be just some empty subfolders that were leftover. Deleting these has been able to help. One can also delete the dir "moodledata/temp/backup" completely. That can take a bit longer but may solve several problems at once.

==The process ends with: "XML error: not well-formed (invalid token) at line YYYY". What can I do?==

This problem can appear at any point in the restore process. It's caused when the XML parser detects something incorrect in the backup file that prevent correct operation. Usually, it's caused by some "illegal" characters added in the original course due to some copy/paste of text containing them (control characters, or invalid sequences...).

The best method to handle this issue is:

* Unzip the problematic backup file under one empty folder.

* Open the moodle.xml with Firefox. It will show you where (exact char) the problem is happening.

* Edit the moodle.xml file with some UTF8-compatible editor and delete such characters. Save changes.

* Test the moodle.xml file again with Firefox until no error was displayed.

* Zip everything again (all the folder contents but not the folder itself!).

* Restore the course. It should work now.

* Restore still not working? See the next question.

Also, if possible, it's highly recommended to solve those problems in the original course too from Moodle itself. Once "repaired" there, problems will be out if you create new backup files in the future.

==The process ends with: "moodle xml not found at root level of zip file". What can I do?==
If you are restoring from a zip file backup make sure the moodle.xml file is at the root level. To ensure this:
#Unzip the backup file of the course (example: mycourse.zip)
#Once the file is unzipped, open the folder (example: mycourse).
#Select the folders within the mycourse folder AND the moodle.xml file and create a zip of those item (example: mycourse_new.zip)
#Upload the new zip file (example: mycourse_new.zip) and restore from that.

If the backup file is guaranteed to be correct, check paths to external files (zip, unzip). Incorrect settings also lead to this error message (see the Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=140355 moodle.xml not found in root...] and MDL-14812).

==The process ends with: "An error occurred while copying the zip file..."==

This problem is most likely caused by a permissions issue in the destination directory. Backup files are copied to "XXX/backupdata" under your dataroot directory (where XXX is the id of the course being backed up).

On Windows systems, if you have configured Moodle to use an external zip program then the IIS IUSR_computername user needs to have Execute access to cmd.exe so that it can run the zip program. See the Note in [https://docs.moodle.org/en/System_paths#Path_to_zip Path to zip] for more details.

The problem could also be caused by a disk being full, though this is far less likely.

To obtain precise information about what's happening, you can enable debug messages in ''Administration > Server > [[Debugging]]'' (select the maximum level - DEVELOPER) and/or check the web server error logs.

==I Still get an XML error. How can I clean the borked XML file?==

In some cases XML backup files may contain characters causing the restore process to abort, even after the steps described in the previous question. In such cases you may want to try the following:

* Download the [http://repository.atlassian.com/atlassian-xml-cleaner/jars/atlassian-xml-cleaner-0.1.jar Atlassian XML Cleaner Utility] from the [http://confluence.atlassian.com/display/JIRA/Removing+invalid+characters+from+XML+backups JIRA Atlassian site].

* Unzip the problematic Moodle backup file under one empty folder. Moodle will create the course file folders as long as the unclean moodle.xml file. Please unzip using the Moodle unzip feature.

* Rename the unclean moodle.xml file to moodle-unclean.xml.

* If you don't have access to your Moodle server's command prompt, using the Moodle zip feature, zip the moodle-unclean.xml file only, download the zip file locally and unzip it. It is very important to download the xml file in zipped format to avoid unwanted character encoding when transferring from an operating system to another.

* Move the downloaded Atlassian XML Cleaner Utility in the same folder where is your moodle-unclean.xml file.

* Issue the following command from the command prompt:

java -jar atlassian-xml-cleaner-0.1.jar moodle-unclean.xml > moodle.xml

* If you launched the utility on your local computer, zip the just created (and hopefully cleaned) moodle.xml file and upload it in the same place from where you downloaded the moodle-unclean.xml file. Once uploaded, unzip it using the Moodle unzip feature.

* Zip everything again (all the folder contents but the folder itself!).

* Restore the course. It should work now.

==What does "Some of your courses weren't saved!!" mean?==

There are three possible causes of this problem:
# Error - this happens when the backup procedure has found an error and so hasn't finished the backup of a particular course. These are "controlled" errors and the scheduled backup continues with the next course.
# Unfinished - this happens when the backup procedure dies without knowing why. When the cron is next executed it detects that the last execution went wrong, and continues skipping the problematic course. A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), or if there is some exact point were all the courses are breaking (generally internal zip libraries, try to switch to external executables instead).
# Skipped - this happens when a course is unavailable to students and has not been changed in the last month (31 days). This isn't an error situation - it's a feature, especially useful for sites with many unavailable old courses, saving process time.

==Why are some courses being skipped?==

Course backups automatically skip courses which are unavailable to students and have not been changed in the last month.

The [http://moodle.org/mod/forum/discuss.php?d=80367#p714733 Hide courses excluded from automatic backup] discussion in the Using Moodle forum describes a way that you can disable or override this thirty day check. This could be useful if, for example, you wanted to change the period from thirty days to six months.

==Why does restore stop, rather than completing?==

Attempting to restore a course to an older version of Moodle than the one the course was backed up on can result in the restore process failing to complete. To ensure a successful restore, make sure that the version of Moodle you are restoring the course to is the same, or newer, than the one the course was backed up on.

If it stop unexpectedly with no errors shown try again with [[Debugging]] switched on. Any errors you now see can help experts in the support forums diagnose your problem. You can also check the discussion links in the See also section below for further advice.

==Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict"==

[[Image:Moodle 2.0 Restore breaks.png|thumb|Error message in Moodle 2.0]]

This message is displayed when:

# Your target site has one xxxx user (xxxx being the username)
# The backup being restored also has one xxxx user
# After various comparisons, Moodle has detected that the xxxx user in 1. and the xxxx user in 2. aren't the same user.

If 1, 2 and 3 above happens, restore stops before performing any action as far as restoring that user will end associating "things" (create activities, posts, attempts... whatever...) to the xxxx user in the target site, when those "things" weren't performed by the same user at all.

Those checks and behaviour were introduced in Moodle 1.9.x and continue being valid under 2.0. Usually the xxxx user in the messages is the "admin" user (that exists in practically all Moodle installations).

There are two possible solutions to make both xxxx users in 1 and 2 to match (and avoid the conflict):

a) Modify the backup's '''users.xml''' file and make the ''email'' or ''firstaccess'' fields match with the ones in target site. 
b) Modify the '''target site''' and set the user ''email'' or ''firstaccess'' fields to match with the ones in backup's user.xml file.

Method a) is recommended so the restore process will match both xxxx users and every "thing" in the backup file belonging to xxxx will be associated to the already existing xxxx user in the target site.

NOTE: When using method a) be aware that the ''moodle-filename-backup.mbz'' is a zip file and can be renamed and unzipped. When editing compelte, rezip and then
rename using the original file name with the "*.mbz" extention.

==Why are certain course links broken in a restored course?==

Inter-activity links must be absolute (full) URLs e.g. <code><nowiki>http://site.com/mod/resource/view.php?id=xxx</nowiki></code> in order to be processed properly during backup and restore.

Any relative URLs e.g. <code>/mod/resource/view.php?id=xxx</code>, <code>../resource/view.php?id=xxx</code> or <code>view.php?id=xxx</code> will result in broken links when the course is restored.

== See also ==

*Using Moodle [http://moodle.org/mod/forum/view.php?f=128 Backup and Restore forum]
*[http://www.databasejournal.com/features/mysql/article.php/10897_3300511_2 databasejournal.com article on repairing database corruption in MySQL]
* [[Site backup]]
* [[Moodle migration]]
* [[Beginning Moodle 2.0 Administration]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=142720 Trying to restore user 'admin' from backup file will cause conflict]
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]

[[Category:FAQ]]

[[es:FAQ Backup]]
[[pl:Backup FAQ]]
[[fr:FAQ de sauvegarde]]
[[ja:バックアップFAQ]]
[[pt:FAQ sobre cópias de segurança]]

Backup and restore FAQ

2012-10-21T11:44:12Z

ColinFraser: /* Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict" */

{{Backup}}
==How do I backup a course?==

See [[Course backup]] and [[Automated backup setup]].

==How do I restore a course?==

See [[Course restore]].

==How do I backup my site?==

See [[Site backup]].

==What are the pros and cons of course versus site backups?==

[[Site backup|Site backups]] are recommended in order to have all data saved with the best confidence and the shortest recovery time.

For a site administrator, [[Automated course backup|automated course backups]] are more expensive in terms of time, CPU usage and storage. The recovery time to have a site running again takes longer than a site backup. However, teachers and site administrators might find a course backups as a way to create a "fresh" copy of a course that can be re-used (in older versions of Moodle, in newer versions see [[Import course data]]) or as a method to distribute a course(s) to other Moodle sites.

==Why is my automated course backup much smaller in size than my manual course backup?==

This is an intentional design decision. Because of the way files are stored in Moodle 2.x, there is no need to include the files in the backup if you are planning to restore them to the same Moodle site. Leaving them out saves huge amounts of disc space and makes the backup procedure much faster.

==What data is not contained in course backups?==

By selecting all the options when setting up the backup you can include almost all the data in the course. However you should be aware of the fact that some things are not backed up:
* Quiz questions are only backed up if at least one question from their category has been added to a quiz.
* Scales are only backed up if they are used by at least one activity.
* Users' passwords are not backed up when the "Include enrolled users" option is selected.

==Why is there no "all/none" feature when selecting items to backup?==
This was enabled in MDL-32705 and is available in Moodle 2.3.2 onwards.

==The process ends with: "Error: An error occurred deleting old backup data". What should I do?==

This part of the backup (or restore) procedure tries to delete old info, used in previous executions, performing the following tasks:

# Delete old records from "backup_ids" table: Check the table exists, repair it and try again.
# Delete old records from "backup_files" table: Check the table exists, repair it and try again.
# Delete old files from "moodledata/temp/backup": Delete the dir completely and try again.

[[Image:BackupProblem.gif|thumb|Backup error message]]For points 1 & 2, there are various ways of repairing tables, including using MySQL Admin.
For point 3 see below:

The error message states that the "directory not empty" and gives the path to that directory. If you go there with an FTP program you can see what is there and clean up. It could be just some empty subfolders that were leftover. Deleting these has been able to help. One can also delete the dir "moodledata/temp/backup" completely. That can take a bit longer but may solve several problems at once.

==The process ends with: "XML error: not well-formed (invalid token) at line YYYY". What can I do?==

This problem can appear at any point in the restore process. It's caused when the XML parser detects something incorrect in the backup file that prevent correct operation. Usually, it's caused by some "illegal" characters added in the original course due to some copy/paste of text containing them (control characters, or invalid sequences...).

The best method to handle this issue is:

* Unzip the problematic backup file under one empty folder.

* Open the moodle.xml with Firefox. It will show you where (exact char) the problem is happening.

* Edit the moodle.xml file with some UTF8-compatible editor and delete such characters. Save changes.

* Test the moodle.xml file again with Firefox until no error was displayed.

* Zip everything again (all the folder contents but not the folder itself!).

* Restore the course. It should work now.

* Restore still not working? See the next question.

Also, if possible, it's highly recommended to solve those problems in the original course too from Moodle itself. Once "repaired" there, problems will be out if you create new backup files in the future.

==The process ends with: "moodle xml not found at root level of zip file". What can I do?==
If you are restoring from a zip file backup make sure the moodle.xml file is at the root level. To ensure this:
#Unzip the backup file of the course (example: mycourse.zip)
#Once the file is unzipped, open the folder (example: mycourse).
#Select the folders within the mycourse folder AND the moodle.xml file and create a zip of those item (example: mycourse_new.zip)
#Upload the new zip file (example: mycourse_new.zip) and restore from that.

If the backup file is guaranteed to be correct, check paths to external files (zip, unzip). Incorrect settings also lead to this error message (see the Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=140355 moodle.xml not found in root...] and MDL-14812).

==The process ends with: "An error occurred while copying the zip file..."==

This problem is most likely caused by a permissions issue in the destination directory. Backup files are copied to "XXX/backupdata" under your dataroot directory (where XXX is the id of the course being backed up).

On Windows systems, if you have configured Moodle to use an external zip program then the IIS IUSR_computername user needs to have Execute access to cmd.exe so that it can run the zip program. See the Note in [https://docs.moodle.org/en/System_paths#Path_to_zip Path to zip] for more details.

The problem could also be caused by a disk being full, though this is far less likely.

To obtain precise information about what's happening, you can enable debug messages in ''Administration > Server > [[Debugging]]'' (select the maximum level - DEVELOPER) and/or check the web server error logs.

==I Still get an XML error. How can I clean the borked XML file?==

In some cases XML backup files may contain characters causing the restore process to abort, even after the steps described in the previous question. In such cases you may want to try the following:

* Download the [http://repository.atlassian.com/atlassian-xml-cleaner/jars/atlassian-xml-cleaner-0.1.jar Atlassian XML Cleaner Utility] from the [http://confluence.atlassian.com/display/JIRA/Removing+invalid+characters+from+XML+backups JIRA Atlassian site].

* Unzip the problematic Moodle backup file under one empty folder. Moodle will create the course file folders as long as the unclean moodle.xml file. Please unzip using the Moodle unzip feature.

* Rename the unclean moodle.xml file to moodle-unclean.xml.

* If you don't have access to your Moodle server's command prompt, using the Moodle zip feature, zip the moodle-unclean.xml file only, download the zip file locally and unzip it. It is very important to download the xml file in zipped format to avoid unwanted character encoding when transferring from an operating system to another.

* Move the downloaded Atlassian XML Cleaner Utility in the same folder where is your moodle-unclean.xml file.

* Issue the following command from the command prompt:

java -jar atlassian-xml-cleaner-0.1.jar moodle-unclean.xml > moodle.xml

* If you launched the utility on your local computer, zip the just created (and hopefully cleaned) moodle.xml file and upload it in the same place from where you downloaded the moodle-unclean.xml file. Once uploaded, unzip it using the Moodle unzip feature.

* Zip everything again (all the folder contents but the folder itself!).

* Restore the course. It should work now.

==What does "Some of your courses weren't saved!!" mean?==

There are three possible causes of this problem:
# Error - this happens when the backup procedure has found an error and so hasn't finished the backup of a particular course. These are "controlled" errors and the scheduled backup continues with the next course.
# Unfinished - this happens when the backup procedure dies without knowing why. When the cron is next executed it detects that the last execution went wrong, and continues skipping the problematic course. A possible solution would be to raise the PHP/Apache limit in your installation (memory, time of execution...). By taking a look to your log tables you should be able to see if the "crash" is happening at exact time intervals (usually a problem with the max_execution_time php's variable), or if there is some exact point were all the courses are breaking (generally internal zip libraries, try to switch to external executables instead).
# Skipped - this happens when a course is unavailable to students and has not been changed in the last month (31 days). This isn't an error situation - it's a feature, especially useful for sites with many unavailable old courses, saving process time.

==Why are some courses being skipped?==

Course backups automatically skip courses which are unavailable to students and have not been changed in the last month.

The [http://moodle.org/mod/forum/discuss.php?d=80367#p714733 Hide courses excluded from automatic backup] discussion in the Using Moodle forum describes a way that you can disable or override this thirty day check. This could be useful if, for example, you wanted to change the period from thirty days to six months.

==Why does restore stop, rather than completing?==

Attempting to restore a course to an older version of Moodle than the one the course was backed up on can result in the restore process failing to complete. To ensure a successful restore, make sure that the version of Moodle you are restoring the course to is the same, or newer, than the one the course was backed up on.

If it stop unexpectedly with no errors shown try again with [[Debugging]] switched on. Any errors you now see can help experts in the support forums diagnose your problem. You can also check the discussion links in the See also section below for further advice.

==Restore stops with the message "Trying to restore user xxxx from backup file will cause conflict"==

[[Image:Moodle 2.0 Restore breaks.png|thumb|Error message in Moodle 2.0]]

This message is displayed when:

# Your target site has one xxxx user (xxxx being the username)
# The backup being restored also has one xxxx user
# After various comparisons, Moodle has detected that the xxxx user in 1. and the xxxx user in 2. aren't the same user.

If 1, 2 and 3 above happens, restore stops before performing any action as far as restoring that user will end associating "things" (create activities, posts, attempts... whatever...) to the xxxx user in the target site, when those "things" weren't performed by the same user at all.

Those checks and behaviour were introduced in Moodle 1.9.x and continue being valid under 2.0. Usually the xxxx user in the messages is the "admin" user (that exists in practically all Moodle installations).

There are two possible solutions to make both xxxx users in 1 and 2 to match (and avoid the conflict):

a) Modify the backup's '''users.xml''' file and make the ''email'' or ''firstaccess'' fields match with the ones in target site. 
b) Modify the '''target site''' and set the user ''email'' or ''firstaccess'' fields to match with the ones in backup's user.xml file.

Method a) is recommended so the restore process will match both xxxx users and every "thing" in the backup file belonging to xxxx will be associated to the already existing xxxx user in the target site.

NOTE: When using method a) be aware that the ''moodle-filename-backup.mbz'' is a zip file and can be renamed and unzipped. When editing compelte, rezip and then rename using the original file name with the "*.mbz" extention.

==Why are certain course links broken in a restored course?==

Inter-activity links must be absolute (full) URLs e.g. <code><nowiki>http://site.com/mod/resource/view.php?id=xxx</nowiki></code> in order to be processed properly during backup and restore.

Any relative URLs e.g. <code>/mod/resource/view.php?id=xxx</code>, <code>../resource/view.php?id=xxx</code> or <code>view.php?id=xxx</code> will result in broken links when the course is restored.

== See also ==

*Using Moodle [http://moodle.org/mod/forum/view.php?f=128 Backup and Restore forum]
*[http://www.databasejournal.com/features/mysql/article.php/10897_3300511_2 databasejournal.com article on repairing database corruption in MySQL]
* [[Site backup]]
* [[Moodle migration]]
* [[Beginning Moodle 2.0 Administration]]

Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=142720 Trying to restore user 'admin' from backup file will cause conflict]
*[http://moodle.org/mod/forum/discuss.php?d=167471 Where is the Moodle 2.0 "Course Backup Filearea"?]

[[Category:FAQ]]

[[es:FAQ Backup]]
[[pl:Backup FAQ]]
[[fr:FAQ de sauvegarde]]
[[ja:バックアップFAQ]]
[[pt:FAQ sobre cópias de segurança]]

Beginning Moodle 2.x Administration 2 FAQ

2012-10-17T21:09:08Z

ColinFraser: /* My Password is not being accepted as valid. How can I login as an Admin? */

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.x, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should be able to access your Moodle as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract original files from a Moodle backup file?===
If you really want to get original files from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with any zip/unzip program you can download. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file in a text editor, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, let's assume there is a "backup_courses-120730.mbz" file of which the "files.xml" file and the "files" folder have been extracted. There is a PDF file named "Leadership.pdf" that is required for another purpose.

Open the files.xml file and:

1. Search for the string "Leadership.pdf", which in this case is found under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. Take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", open the "fb" folder inside the "files" directory (which was previously extracted), and there is a file named "fb6cf43a9b...". Rename that file as "Leadership.pdf", and then move it to another location. Repeat this for all the files required, using the correct contenthash value of course.

Thanks to Guillermo Madero S for this answer.

===How can I have two installations of Moodle on my server?===

There is always a number of reasons why you may require several different versions of Moodle on your server, or your localhost on a standalone computer. You may want to run two completely different Moodles for different purposes, so they may be the same versions. The answers are the same for all of them, and you may want to use different techniques depending on your circumstances.

First, in all versions of Moodle you are able to set the cookie prefix. Whenever you install a Moodle, it is a good idea to not just accept the default for the cookie prefix. Go to Administration menu > Server > Session Handling and you will see there is a text box that allows you to add a prefix for the Moodle. If you do this for every installation, you can have any number of installations - the problem is going to be the database.

At installation, you can create two different databases. again in some circumstances, there may be any number of valid reasons to do this, but fact is, you may not, in v2.x have to worry about it too much. Each installation will generate its own tables so, at installation, you may not have to worry too much apart from giving the databases different names.

===How can I deny Guest Access to my site altogether?===

Look at Site administration ► Plugins ► Authentication ► Manage authentication and there is a switch there that allows you to turn the Guest Access button off altogether.

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.x Administration 2 FAQ

2012-10-17T21:04:46Z

ColinFraser: /* How do I create a repository? */

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.x, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should then be able to get into your Moodle then, as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract original files from a Moodle backup file?===
If you really want to get original files from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with any zip/unzip program you can download. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file in a text editor, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, let's assume there is a "backup_courses-120730.mbz" file of which the "files.xml" file and the "files" folder have been extracted. There is a PDF file named "Leadership.pdf" that is required for another purpose.

Open the files.xml file and:

1. Search for the string "Leadership.pdf", which in this case is found under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. Take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", open the "fb" folder inside the "files" directory (which was previously extracted), and there is a file named "fb6cf43a9b...". Rename that file as "Leadership.pdf", and then move it to another location. Repeat this for all the files required, using the correct contenthash value of course.

Thanks to Guillermo Madero S for this answer.

===How can I have two installations of Moodle on my server?===

There is always a number of reasons why you may require several different versions of Moodle on your server, or your localhost on a standalone computer. You may want to run two completely different Moodles for different purposes, so they may be the same versions. The answers are the same for all of them, and you may want to use different techniques depending on your circumstances.

First, in all versions of Moodle you are able to set the cookie prefix. Whenever you install a Moodle, it is a good idea to not just accept the default for the cookie prefix. Go to Administration menu > Server > Session Handling and you will see there is a text box that allows you to add a prefix for the Moodle. If you do this for every installation, you can have any number of installations - the problem is going to be the database.

At installation, you can create two different databases. again in some circumstances, there may be any number of valid reasons to do this, but fact is, you may not, in v2.x have to worry about it too much. Each installation will generate its own tables so, at installation, you may not have to worry too much apart from giving the databases different names.

===How can I deny Guest Access to my site altogether?===

Look at Site administration ► Plugins ► Authentication ► Manage authentication and there is a switch there that allows you to turn the Guest Access button off altogether.

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T20:56:01Z

ColinFraser: /* What kind of technical skills do I need to take on Moodle Administration? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages. The questions asked here are mostly questions that I was confronted with when I first started with administering a Moodle, but I had some experience as a user which helped me a lot. The other source of questions is the Moodle Forums.

===What kind of technical skills do I need to take on Moodle Administration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. If you need them, you will pick these skills up as you go, and if you already have any programming skills, it is going to be fairly easy to do so. If you have never done any programming before, it is a little more difficult, but once you have the idea, it becomes a lot easier. Unless you intend on developing your Moodle, e.g. build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things available, useful plugins and extra blocks and so on, but the majority of those things are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to make things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T12:11:48Z

ColinFraser:

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages. The questions asked here are mostly questions that I was confronted with when I first started with administering a Moodle, but I had some experience as a user which helped me a lot. The other source of questions is the Moodle Forums.

===What kind of technical skills do I need to take on Moodle Administration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go, if you need them. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things available, useful plugins and extra blocks and so on, but the majority of those things are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to make things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T12:09:38Z

ColinFraser: /* What kind of technical skills do I need to take on Moodle Adminsitration? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Administration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go, if you need them. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things available, useful plugins and extra blocks and so on, but the majority of those things are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to make things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T12:09:07Z

ColinFraser: /* When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Adminsitration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go, if you need them. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things available, useful plugins and extra blocks and so on, but the majority of those things are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to make things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T12:01:37Z

ColinFraser: /* What kind of technical skills do I need to take on Moodle Adminsitration? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Adminsitration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go, if you need them. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things available, useful plugins and extra blocks and so on, but the majority of those things are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to make things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T12:00:37Z

ColinFraser: /* What kind of technical skills do I need to take on Moodle Adminsitration? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Adminsitration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things available, useful plugins and extra blocks and so on, but the majority of those things are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to make things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T11:49:54Z

ColinFraser: /* What kind of technical skills do I need to take on Moodle Adminsitration? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Adminsitration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things available, useful plugins and extra blocks and so on, but the majority of those things are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to ake things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T11:48:28Z

ColinFraser: /* What kind of technical skills do I need to take on Moodle Adminsitration? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Adminsitration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

[[Image:lightbulb.png|frame|left|Tip]]As a newbie Administrator, it is easy to get overwhelmed with all the different things avaiable, plugins, blocks and so on, but the majority of those plugins and blocks are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thumb, the further you move away from the standard Moodle, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to ake things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T11:47:29Z

ColinFraser: /* What kind of technical skills do I need to take on Moodle Adminsitration? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Adminsitration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

As a newbie Administrator, it is easy to get overwhelmed with all the different things avaiable, plugins, blocks and so on, but the majority of those plugins and blocks are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thimb, the further you move away from the standard Moolde, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

[[Image:lightbulb.png|frame|left|Tip]]

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to ake things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T11:46:54Z

ColinFraser: /* What kind of technical skills do I need to take on Moodle Adminsitration? */

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Adminsitration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

As a newbie Administrator, it is easy to get overwhelmed with all the different things avaiable, plugins, blocks and so on, but the majority of those plugins and blocks are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thimb, the further you move away from the standard Moolde, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.
[[Image:lightbulb.png|frame|left|Tip]]

Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to ake things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-10-17T11:46:17Z

ColinFraser:

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===What kind of technical skills do I need to take on Moodle Adminsitration?===
Reading and writing are handy skills, and probably the most useful. This is something of a loaded question, and the answer is actually, depends on what you want to do, and what skills you already have.

Do you have any HTML, CSS and PHP skills? Do you have any SQL database skills. If you do, then you have a good start, if you do not, then do not worry about it. You will pick these skills up as you go. Unless you intend on developing your Moodle, build your own home made theme, alter code to reflect your own organization, then you can get away without any of these skills. What you need is a way of developing a quick understanding of how Moodle works. With the introduction of Moodle v2, the learning curve has steepened somewhat, but it is still not that difficult.

Installing and setting up a new Moodle is not as difficult as it used to be. Some servers and service providers do have problems, from time to time, but if you work with your ISP, and the Moodle Community, you will get your Moodle up and running. Once it is going, start looking at it. You won't break anything, unless you start deleting things. Your best bet would be to read the documents. Look at the page you are working on. Somewhere on that page is a link that points to "Moodle Docs for this page". That is your best, most readily available, clues on how to do things. Once familiar with the environment, and how to get around it, how to get information on it, then the major steps have been taken, the rest is a continual refinement of that.

As a newbie Administrator, it is easy to get overwhelmed with all the different things avaiable, plugins, blocks and so on, but the majority of those plugins and blocks are third-party made, not Moodle.org in origin. Be aware that, as a general rule of thimb, the further you move away from the standard Moolde, the greater your risks of things going wrong. This does not mean the plugins are badly written, and some are really handy, just sometimes things go wrong. If you are going to use them, be deliberate in your choice, do not use them just because it might be a good idea.

[[Image:lightbulb.png|frame|left|Tip]] Perhaps the best thing is that you create a Moodle on your desktop, or laptop, and you use that as a testbed. It should be the same version as your production site, to ake things easy. Try things there first, if there is no problems, then you can replicate it on your production site.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

'''Please note:''' the book module is available as standard in Moodle 2.3

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.x Administration 2 FAQ

2012-09-23T11:54:29Z

ColinFraser: /* How can I extract original files from a Moodle backup file? */

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.0, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should then be able to get into your Moodle then, as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract original files from a Moodle backup file?===
If you really want to get original files from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with any zip/unzip program you can download. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file in a text editor, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, let's assume there is a "backup_courses-120730.mbz" file of which the "files.xml" file and the "files" folder have been extracted. There is a PDF file named "Leadership.pdf" that is required for another purpose.

Open the files.xml file and:

1. Search for the string "Leadership.pdf", which in this case is found under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. Take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", open the "fb" folder inside the "files" directory (which was previously extracted), and there is a file named "fb6cf43a9b...". Rename that file as "Leadership.pdf", and then move it to another location. Repeat this for all the files required, using the correct contenthash value of course.

Thanks to Guillermo Madero S for this answer.

===How can I have two installations of Moodle on my server?===

There is always a number of reasons why you may require several different versions of Moodle on your server, or your localhost on a standalone computer. You may want to run two completely different Moodles for different purposes, so they may be the same versions. The answers are the same for all of them, and you may want to use different techniques depending on your circumstances.

First, in all versions of Moodle you are able to set the cookie prefix. Whenever you install a Moodle, it is a good idea to not just accept the default for the cookie prefix. Go to Administration menu > Server > Session Handling and you will see there is a text box that allows you to add a prefix for the Moodle. If you do this for every installation, you can have any number of installations - the problem is going to be the database.

At installation, you can create two different databases. again in some circumstances, there may be any number of valid reasons to do this, but fact is, you may not, in v2.x have to worry about it too much. Each installation will generate its own tables so, at installation, you may not have to worry too much apart from giving the databases different names.

===How can I deny Guest Access to my site altogether?===

Look at Site administration ► Plugins ► Authentication ► Manage authentication and there is a switch there that allows you to turn the Guest Access button off altogether.

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.x Administration 2 FAQ

2012-09-23T11:48:27Z

ColinFraser: /* How can I have two installations of Moodle on my server? */

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.0, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should then be able to get into your Moodle then, as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract original files from a Moodle backup file?===
If you really want to get original files from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with any zip/unzip program you can download. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file in a text editor, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, lets assume I have a "backup_courses-120730.mbz" file of which I already extracted the "files.xml" file and the "files" folder, and that I'm looking for a PDF file named "Leadership.pdf".

So I open the files.xml file and:

1. Search for the string "Leadership.pdf", which in my case I find under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. I take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", I open the "fb" folder inside the "files" directory (which I previously extracted), and there I will find a file named "fb6cf43a9b...", so now I can rename that file as "Leadership.pdf", and then move it to another location (where I'll gather all the files I need from the backup).

Thanks to Guillermo Madero S for this answer.

===How can I have two installations of Moodle on my server?===

There is always a number of reasons why you may require several different versions of Moodle on your server, or your localhost on a standalone computer. You may want to run two completely different Moodles for different purposes, so they may be the same versions. The answers are the same for all of them, and you may want to use different techniques depending on your circumstances.

First, in all versions of Moodle you are able to set the cookie prefix. Whenever you install a Moodle, it is a good idea to not just accept the default for the cookie prefix. Go to Administration menu > Server > Session Handling and you will see there is a text box that allows you to add a prefix for the Moodle. If you do this for every installation, you can have any number of installations - the problem is going to be the database.

At installation, you can create two different databases. again in some circumstances, there may be any number of valid reasons to do this, but fact is, you may not, in v2.x have to worry about it too much. Each installation will generate its own tables so, at installation, you may not have to worry too much apart from giving the databases different names.

===How can I deny Guest Access to my site altogether?===

Look at Site administration ► Plugins ► Authentication ► Manage authentication and there is a switch there that allows you to turn the Guest Access button off altogether.

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.x Administration 2 FAQ

2012-09-21T00:52:17Z

ColinFraser: /* How can I have two installations of Moodle on my server? */

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.0, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should then be able to get into your Moodle then, as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract original files from a Moodle backup file?===
If you really want to get original files from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with any zip/unzip program you can download. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file in a text editor, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, lets assume I have a "backup_courses-120730.mbz" file of which I already extracted the "files.xml" file and the "files" folder, and that I'm looking for a PDF file named "Leadership.pdf".

So I open the files.xml file and:

1. Search for the string "Leadership.pdf", which in my case I find under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. I take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", I open the "fb" folder inside the "files" directory (which I previously extracted), and there I will find a file named "fb6cf43a9b...", so now I can rename that file as "Leadership.pdf", and then move it to another location (where I'll gather all the files I need from the backup).

Thanks to Guillermo Madero S for this answer.

===How can I have two installations of Moodle on my server?===

There is always a number of reasons why you may require several different versions of Moodle on your server, or your localhost on a standalone computer. You may want to run two completely different Moodles for different purposes, so they may be the same versions. The answers are the same for all of them, and you may want to use different techniques depending on your circumstances.

First, in all versions of Moodle you are able to set the cookie prefix. Whenever you install a Moodle, it is a good idea to not just accept the default for the cookie prefix. Go to Administration menu > Server > Session Handling and you will see there is a text box that allows you to add a prefix for the Moodle. If you do this for every installation, you can have any number of installations - the problem is going to be the database.

At installation, you can create two different databases. again in some circumstances, there may be any number of valid reasons to do this, but fact is, you may not, in v2.x have to worry about it too much. Each installation will generate its own tables so, at installation, you may not have to worry too much apart from giving the databases different names.

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.x Administration 2 FAQ

2012-09-21T00:08:02Z

ColinFraser: /* How can I extract orginal files from a Moodle backup file? */

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.0, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should then be able to get into your Moodle then, as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract original files from a Moodle backup file?===
If you really want to get original files from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with any zip/unzip program you can download. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file in a text editor, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, lets assume I have a "backup_courses-120730.mbz" file of which I already extracted the "files.xml" file and the "files" folder, and that I'm looking for a PDF file named "Leadership.pdf".

So I open the files.xml file and:

1. Search for the string "Leadership.pdf", which in my case I find under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. I take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", I open the "fb" folder inside the "files" directory (which I previously extracted), and there I will find a file named "fb6cf43a9b...", so now I can rename that file as "Leadership.pdf", and then move it to another location (where I'll gather all the files I need from the backup).

Thanks to Guillermo Madero S for this answer.

===How can I have two installations of Moodle on my server?===

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.x Administration 2 FAQ

2012-09-21T00:07:33Z

ColinFraser: /* How can I extract orginal files from a Moodle backup file? */

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.0, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should then be able to get into your Moodle then, as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract orginal files from a Moodle backup file?===
If you really want to get original files from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with any zip/unzip program you can download. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file in a text editor, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, lets assume I have a "backup_courses-120730.mbz" file of which I already extracted the "files.xml" file and the "files" folder, and that I'm looking for a PDF file named "Leadership.pdf".

So I open the files.xml file and:

1. Search for the string "Leadership.pdf", which in my case I find under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. I take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", I open the "fb" folder inside the "files" directory (which I previously extracted), and there I will find a file named "fb6cf43a9b...", so now I can rename that file as "Leadership.pdf", and then move it to another location (where I'll gather all the files I need from the backup).

Thanks to Guillermo Madero S for this answer.

===How can I have two installations of Moodle on my server?===

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-08-18T13:06:57Z

ColinFraser:

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.x. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.x Administration 2 FAQ

2012-08-15T10:53:59Z

ColinFraser: /* How can I extract orginal files from a Moodle backup file? */

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.0, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should then be able to get into your Moodle then, as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract orginal files from a Moodle backup file?===
If you really want to get original files from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with any zip/unzip program you can download. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file in a text editor, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, lets assume I have a "backup_courses-120730.mbz" file of which I already extracted the "files.xml" file and the "files" folder, and that I'm looking for a PDF file named "Leadership.pdf".

So I open the files.xml file and:

1. Search for the string "Leadership.pdf", which in my case I find under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. I take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", I open the "fb" folder inside the "files" directory (which I previously extracted), and there I will find a file named "fb6cf43a9b...", so now I can rename that file as "Leadership.pdf", and then move it to another location (where I'll gather all the files I need from the backup).

Thanks to Guillermo Madero S for this answer.

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.0 Administration

2012-08-15T10:51:20Z

ColinFraser:

The pages began life with the [https://docs.moodle.org/19/en/Beginning_Administration_FAQ Beginning v1.9 Administration FAQ] pages but are aimed specifically at Moodle 2.0. Many of the solutions to problems will work in both versions of Moodle so if you do not find something here, then you may find it in the other pages.

===I am being told that I need the '''intl php plugin''' to continue to install Moodle 2.x===
The intl.dll from Zend is part of the PHP 5.2.8 release and later. It is aimed at improving the internationalization of php pages and Moodle 2.x uses it as part of this process. If your install is on a local machine or network, then you can download the latest version of PHP and update your PHP. You then have to uncomment all the required dynamic extensions you need, including the php_intl.dll extension. The problem is then solved. If the install is on a host server, then you need to contact your host and ask them to do the same, As an alternative, you can unzip/untar the download file, copy and paste the intl.dll file to your php/ext folder and include the line:
extension=php_intl.dll
in the Dynamic Extensions section of your php.ini file.

You can also set the error level using:
intl.error_level = E_WARNING
but this is not essential

If you are using a Linux install, use your system package manager or specify compilation flag.
* Debian 5.0 (& Ubuntu) use: apt-get install php-intl or apt-get install php5-intl
* CentOS 5.5 (& RedHat) you should (probably) be using php 5.3 from remi and then use: yum install php-intl

This technique can be applied to any updated dynamic extension from Zend. You may want to use later dll files in your php/ext folder, you can do so by doing the same as above, but be careful, your version may not be able to take full advantage of the extension, or some very new extensions may cause an unexpected instability. The best option is still to update on a regular basis, perhaps once a year or so for the PHP.

===What Dynamic Extensions do I really need uncommented in my php.ini file? What else do I need to change?===
This assumes you have complete control over the installation and running of your server, if your Moodle is hosted, you need to do something different, which is also discussed below. In the php.ini you need to delete the semi-colon, the ;, from the start of any line to uncomment it. For Moodle, you really should only need to change some values, and make sure the extensions you require are available. These are:

Resource Limits
memory_limit = 128M //This is the maximum it requires and on a shared server you may get much less.

Data Handling
post_max_size = 512M //This allows postings of up to 512MB, but set it to suit yourself and your circumstances

Paths and Directories
doc_root ="driveletter:\path\to\server\active\web\directory" (e.g. d:\Apache\htdocs or e:\iis\wwwroot )
and
extension_dir = "driveletter:\path\to\php\ext" (e.g. d:\php\ext or e:\iis\php\ext)

File Uploads
upload_max_filesize = 512M (This is different from the post_max_size this is for file uploads.)

Dynamic Extensions
{| class="nicetable"
|-
! PHP 5.2.x (Moodle 1.9 with additions)
! PHP 5.3.x
|-
|
extension=php_curl.dll
extension=php_exif.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_mcrypt.dll
extension=php_mssql.dll
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
'''extension=php_intl.dll'''
'''extension=php_zip.dll''' ; Added Extensions
|
extension=php_curl.dll
extension=php_gd2.dll
extension=php_gettext.dll
extension=php_intl.dll
extension=php_imap.dll
extension=php_ldap.dll
extension=php_mbstring.dll
extension=php_exif.dll ; Must be after mbstring as it depends on it
extension=php_mysql.dll
extension=php_mysqli.dll
extension=php_openssl.dll
extension=php_pdo_mssql.dll
extension=php_pdo_mysql.dll
extension=php_soap.dll
extension=php_sockets.dll
extension=php_sqlite.dll
extension=php_xmlrpc.dll
extension=php_zip.dll
|}

:'''NOTE:''' If you are using a PHP version earlier than v5.2.8, then for Moodle 2.0.x please add the Dynamic extensions of intl.dll and zip.dll as outlined above. Be aware this structure does '''not''' work in Moodle 2.1.

These edits and Dynamic extensions cover a range of options here, there are a number of other possibilities, but these listed are the most common ones. Unless you have a specific need, there may not be any reason to deviate from these settings, but if you do, make sure you know what is going to happen. These extensions will also allow you to successfully install and run many other PHP applications.

One example is the Oracle extensions are not shown here, but Oracle can be used for the Moodle database. Another area people often get themselves into trouble is using "Magic quotes". Magic quotes really should be set to off, they were only introduced early in the use of PHP to allow for some inexperienced scripting practices, (read poor, shoddy or dodgy here). If someone is still writing poor scripts, then they deserve to draw attention to themselves and their scripts deleted.

===My Host took my Moodle 2 down from the server due to an overload of the database.===
This happens far too often on shared servers. The additional memory requirements of Moodle 2+ for installation and the additional database storage required is going to make it worse. The best bet is to find a dedicated server, that is the optimum, but reality is that costs do play a large part in making decisions about where a Moodle will be stored. A dedicated server will give you the entire disc space and all the memory on that server to use as you need. A virtual dedicated server means you are sharing with a few other users on a server, possibly as many as 10, but more likely 5 or 6. A shared server mean you are sharing one box with as many of the Host's clientele that can be put onto one server. This means sharing all resources and Moodle's demands get higher as the number of Users increases which affects all other Clients of the Host. There are any number of Moodle Partners who may be willing to host your Moodle, and the Internet also means you are not restricted by national or natural boundaries or currency transactions - politics, oceans and banks have no impact on where you host your Moodle.

===Why am I having trouble restoring my existing Moodle 1.9.x courses into Moodle 2.0?===
Simply put, the changes in coding between Moodle 1.9.x and Moodle 2.0 are large. Additional security has forced changes to the backup processes. In just looking at the databases there are an additional 60 or more tables, so that creates a number of restoring issues alone. To bring Moodle 1.9.x courses into Moodle 2.0 is a monumental challenge, and full credit to those who are trying it. There is, currently, one commercial Windows based solution but it is not fully successful in its restoration of courses.

: '''NOTE:''' Moodle 2.0 can backup and restore courses from within itself perfectly, the issue appears to be centred on v1.x.x courses.

: '''UPDATE:''' Moodle 2.1 was released on July 1, 2011 and can now restore course files from backups made in v1.9.x. Student file restorations are not yet available but are expected to be included in v2.2 to be released November, 2011.

===How do I look up the error logs in Moodle 2.0?===
First, turn the error logs on, go to

Site administration ► Development ► Debugging

and set error messages to DEVELOPER: .... Then go to

Site administration ► Reports ► Logs

set your report options to Home 2.0(Site), All Participants, All Activities or Site Errors, View, Display on Page and then click, "Get these logs". The report should give you something, and you may be able to develop an appropriate response from there.

===Do I try to upgrade to Moodle 2.0 or just create a new install?===
There is always debate around these issues, but simply put, Moodle 2.0 is a complete re-write of a tried and tested tool. This presents its own challenges, obviously, and those challenges need be met in the best way we can. It is a temptation to go all in and jump to the new tool, but this can be a dangerous practice when dealing with a lot of people who are resistant to change, and the change from Moodle 1.9.x to 2.0 is massive.
Upgrading to Moodle 2.0 has always been an option, but make sure your environment will meet the newer specifications.
Consider your own circumstances. Are you starting out on the Moodle journey or have you just been dropped into it? Perhaps you are starting out, and you have no resources or courses and you are building for the next few months when you want it to become a part of your learning centre and a showpiece for your institute. A complete new Moodle 2.x.x install and starting from scratch is most appropriate in this circumstance. All major features work in it and some of the tools are a lot more interesting than for Moodle 1.9.x.
Don't worry about Moodle 1.9.x, just use the new Moodle 2.x.x and learn it if you are starting from scratch.
If you have been dropped into it, and have a lot of courses, and you need to administer your Moodle 1.9.x as well as look at updating, then the next best option is to install a new Moodle and open it just for your Administrators and Staff. Let them get used to the new interface, develop training courses around the new Moodle, not just for staff but for Users as well. Aim at your staff first, let them learn it then they can be more confident in using the new Moodle when they come to teaching their Users/Students.
In short, best advice is NOT to install a Moodle 2.0 as a production site without thoroughly testing and training first.
To install and run more than one Moodle successfully is actually simple. Install your Moodle 2.0 and then go to '''''Site administration > Server > Session handling'''''. Look for the Cookie prefix dialogue and add a value to it. Repeat the exercise in every other Moodle you have on your server, it should all work as it is supposed to - as long as the cookie prefixes are different for every Moodle, of course.

[[Image:cookieprefix.png|frame|center|Cookie prefix for Moodle 2.0]]

Essentially, take your time and not be in too much of a rush if you have to convert your Staff and Learners to a new tool. Let the Staff get used to it first, then you can make the swap any time.

If you do update your v1.9.x to v 2.0, and experience some problems, you may want to consider putting the issues and any error messages into a [http://tracker.moodle.org/secure/Dashboard.jspa Moodle Tracker item]. If you do, you may be providing information to resolve a number of updating issues for a lot of people.

===Well, we want to try and upgrade to test our systems.===
Try, by all means. However, there are a couple of issues you may need be aware of.

A rough guide and checklist:
#Plugins that work in Moodle 1.9.x may not be updated to Moodle 2.0. Check your plugins. Are you using any non-core plugins?
#Can you remove any non-core plugins?
#Have you backed up your database?
#Have you backed up your moodledata folder?
#Have you allocated additional time make the update, as a contingency?

You may not necessarily have to remove the non-core plugins from the Moodle, or, they may still be present in the database even if you have deleted them from your Moodle Mod folder. The issue arising is that some plugins appear to be causing update errors as there is no matching core plugin from Moodle 2.0, or the plugin APIs are different and cannot accommodate the older plugins, or the older plugins that have not been properly maintained, cannot handle the newer environment.

: '''NOTE:'''This is not meant to be an exhaustive checklist or to scare people off trying to upgrade their v1.9.x to v2.0.x, just be aware that Moodle 2.0 is still a work in progress, as is this checklist.

===We have extensively used the Book for parts of our previous Moodle, can we do so for Moodle 2.0?===
The really good news is that Petr Skoda (Skodak) has the Maintainer role for the [http://moodle.org/mod/data/view.php?d=13&rid=319&filter=1 Book plugin/module]. Petr announced some time back that when his major coding tasks for Moodle 2.0 had been done, he was taking a short break then he would begin work on updating the Book for Moodle 2.0.

:'''UPDATE''': Petr's updating of the Book module is now complete, and is available at the above link. Initial testing shows it installs easily and seems to run faster than the original. Seems the code has been better optimized by Petr, who deserves a hearty congratulations!!!

===That is OK for the Book, but what about other plugins and blocks?===
As a general rule-of-thumb, if a plugin or block has not been maintained through Moodle 1.9.x then it is extremely unlikely it will make it to Moodle 2.0.x. This means the developer has not kept it current and may feel it is too much of a distraction from their current projects to keep active. This does not mean that you, or someone else, may not take it on, as long as you ensure that what you are working with is creative commons, open source or other non-proprietal software and you are not infringing either copyright or intellectual property rights. If you are not sure, try to contact the developer or last maintainer, they may be different - if required, get permission from them to continue development. Of course, you may also seek to develop an entirely new plugin, or block, but it is clear that it is actually duplicating something that already exists or was used in earlier versions of Moodle, but is no longer current. As long as you can prove the provenance of such a plugin or block, and do not use any code from anywhere else that is not original or acknowledged where the code came from, then you should be OK. For ideas and guidelines around developing or updating a plugin, look at this page from [https://docs.moodle.org/dev/Developer_documentation Developer Documentation]. You can also join a [http://dev.moodle.org/ class of developers] and learn how it can be done.

===I am getting error messages about plugins and the installation stops when upgrading. What do I do?===
Quite frequently, not a lot at all, you can just continue on. Many of these messages are just that, messages, they are not supposed to stop or break the installation, they are just warnings that not all is working as you may be used to in an install. Usually they relate to plugins that are not part of Moodle 2.0 yet. Moodle is designed to display a message, but continue on. Or, you can consider that, given the above, upgrading is not really viable and just do a fresh install. If those messages continue, then you have another problem. If there were database errors, or code errors, then it is different, you really do need to stop and investigate.

===We are installing Moodle and getting error messages about not using the unicode or UTF-8 charset===
In recent times, this has become an issue with CPanel and Fantastico installers on some Linux servers. Apparently the default charset for these tools is a latin_swedish_ci charset. Moodle requires the UTF-8 charset. This is a relatively simple fix, if you have the right tools. Install phpMyAdmin and check it is working, if you do not already have it. You can then go to the SQL page and enter the following code:
ALTER DATABASE `moodle` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been, in the past, reports of tables that do not change using this SQL code, so try:
ALTER TABLE `mdl_tablename` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;
There have been no reasons as to why some tables are missed, but you can alter individual tables by using the code above. The code should look something like:

[[Image:altertablesqlm202.png|frame|center|Changing the charset in Moodle 2.0]]

''This also works in Moodle 1.9.x IF you use the utf8_general_ci charset.''

'''NOTE:''' This SQL is supposed to work across the database, but recent reports suggest that the ALTER DATABASE seems to have a number of issues stemming from problems with the GRANT command. GRANT <nowiki>[permissiontype]</nowiki> is supposed to allow a user to access the entire database, but it no longer appears to be the case. The ALTER TABLE SQL has not been affected by this issue.

'''FURTHER NOTE:''' When using the ALTER DATABASE SQL, it appears to be diverted to altering the ''db.opt'' file, but is not continued into the tables of the database. So whether this is a deliberate security feature of more recent editions of MySQL or not is, at this stage, unknown. How this affects Postgres, or Oracle databases is also unknown.

===OK, but how can we tell what tables are not converted?===
Using phpMyAdmin, you can find out almost anything you like about your database, as long as you know where to look. There is some real documentation about using phpMyAdmin that is linked both in the left and right panels. Go to the Database tab and then select the database you want to look at.

[[Image:selectdatabasetab.png|thumb|150px|frame|center|Selecting the database tab in Moodle 2.0]]

Once selected, you will see what the charset is of each table. Any table that does not comply you can change using the table SQL code above.

[[Image:phpmyadmintablelisting.png|frame|center|Checking the table listings in phpMyAdmin]]

===How do I get and install phpMyAdmin?===
phpMyAdmin is another very useful plugin. In Moodle 2.0 the plugin has been updated and is now located in a different place than it was in earlier versions. Go to the [http://moodle.org/mod/data/view.php?d=13&rid=448&filter=1 phpMyAdmin page in Modules and Plugins] and download the Moodle 2.0 version. Unzip it to the '''moodle/local''' folder and then go to '''Notifications'''. Moodle will then tell you it has been successfully installed. If you look in Administration > Server you will now find a line "phpMyAdmin". To access your database, click the link.

===When I update over a 1.9 install, I get an error message about an incompatible plugin and it all stops. What can I do?===

One piece of advice is that you just do not do that!

Sometimes, a file/folder will be removed from the code between one version of Moodle and the next. If you upgrade Moodle by copying the new Moodle code over the top of the old code, then the older files not duplicated or no longer existent, or just disused and dropped, will remain, and can break things.

The correct way to upgrade is (assuming your Moodle code is in a folder called <tt>moodle</tt> on the server:
# Upload the new code onto the server into a folder with a temporary name, like <tt>moodle_new</tt>.
# Copy the <tt>config.php</tt> file from the moodle folder to the <tt>moodle_new</tt> folder.
# For any third-party plugins you have installed, copy the code for them into <tt>moodle_new</tt>. (Make sure the plugin is compatible with the version of Moodle you are upgrading to.)
# Then rename the <tt>moodle</tt> folder to <tt>moodle_old</tt>, and then rename <tt>moodle_new</tt> to <tt>moodle</tt>.

If you insist though, then you can expect to be getting all sorts of error messages. Given the fundamental changes to the database and the manner in which plugins are structured, and employed, in Moodle 2.0.x this is a very time consuming and, ultimately, futile (I would suggest) approach. You can, of course, remove all non-core plugins, and their corresponding tables from the database, and then you give yourself a chance at getting through it somewhat less scathed, but I doubt it.

===What is happening to my uploaded files? I cannot see them in the moodledata folder!===
To improve security, Moodle has change how files are stored in the moodledata folder. There are there, but no longer obvious. When a file is uploaded it is given a storage name, an encrypted name, and it is placed into a specific folder within the moodledata folder. That folder's name is directly related to the file storage name. So we have a file with an encrypted name, inside a folder with a related name, inside the moodledata folder. Now comes the nifty part, these encrypted names are used as connections to the database. The database stores those encrypted names as aliases for the files and uses them to link the files to the courses. You see them, but you do not see them, well they are not obvious. Unfortunately, you cannot edit them in place, like you could files in Moodle 1.9.x you have to edit them, delete the older file and upload the new ones.

==See Also==

*[[Beginning Moodle 2.x Administration 2 FAQ | Beginning Moodle 2.x Administration 2 FAQ ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]

Beginning Moodle 2.x Administration 2 FAQ

2012-08-14T09:38:43Z

ColinFraser:

This page is a follow on from the Beginning Moodle 2.0 Administration page.

===How do I create a repository?===
To setup and use a repository in Moodle 2.0, is not complex, just detailed. What follows will set up a site wide repository, that is the contents of this repository will be available to the entire site - so make sure this is really what you want. This is for the kind of resources you may want to use across a number of courses.

1. In the moodledata folder there is a folder called Repository. Create whatever folders you want in there, but it is suggested you use a consistent naming convention, so everyone knows what type of materials reside there, e.g. CalculusPDFs, EnglishCivilWarDocs, and so on. You can copy the required materials into each folder as you create them or add to it at any time thereafter.

2. In your Moodle 2.0 there are a couple of things you need to do, but first you have to activate the user repository system by going to '''Site Administration > Plugins >Repositories > Manage Repositories''' and you will see in the list contained in the right-hand panel an item named "File System". Select the dropdown list box and change the value to "Enabled and visible"
[[Image:repository01.png|frame|center|Setting the File System Repository in Moodle 2.0]]

3. Click the "Settings" link and that will take you to the "Setup repository on file system" page. Click the "Create a Repository Instance" button and this will take you to the next page. On that page you have two text boxes and two buttons. Add the name of the repository you created in the Repository folder and click "Save".

[[Image:repository02.png|frame|center|Saving the new Repository in Moodle 2.0]]

When you return to the "Setup repository on file system" page, you will now see that a list of repositories is available. When you access any course file or image picker, the repository will be available to you under the name you have given it. Any file inside the repository will be available for uploading to your course.

===How do I set up a course repository?===
Setting up the Course repository is almost exactly the same, but the major difference is that is should only be accessible to that one course.

Create a folder in your moodledata/Repository folder, naming it whatever is relevant. Add the files you want in that repository as you create the folder, or you can add them later.

In the Course Administration menu, click the Repository item which takes you to the "Course Repositories" page. You will see a list of all available Repositories so you can access one of them if you chose, or you can select the Create A Repository Instance, Create a "FileSystem" instance link. This takes you to the same page as shown above.

[[Image:repository03.png|frame|center|Creating a new Course Repository in Moodle 2.0]]

Create your repository instance in the same manner as described above and when you return to the Course Repositories page, you will see your repository listed there.

When you are adding a file to your course from the repository, you can access the stored file from the image or file picker via your repository. The repository is not available outside the course you create it for.

===How do I set the maximum upload file size limit?===
This is probably the most frequently asked question, and the answer is not that straightforward. The changes that need be made are the same in all versions of Moodle, just in different OS' they need be made in different places. Upload file sizes are restricted in a number of ways and each one in this list restricts the following ones:
Server level
Moodle site level
Course level
Activity level

Perhaps the best place to find this information is at [[File_upload_size|File upload size]] There is a full explanation for a number of different OSs but there are a few missing.

This is a contentious issue, mainly because you might think that it should be set inside the Moodle. Unfortunately, this is not so, these are environment issues that need to be set in the server and PHP folders, Moodle cannot work outside itself.

===The previous answer is OK if you control the server, but I am hosted, what can I do to override limitations set by my Host?===
Before doing this, consult with your host, they may have very different ideas about what your Moodle should be permitted - try not to tread on their toes - they may get annoyed at you breaching your user conditions. In an Apache server, you can create a file called '''.htaccess''' which can allow you to override some of the limitations set by PHP on your Moodle. Be aware that this file only applies to your Moodle, and nothing else. Your host will often place a .htaccess file into your root folder which will usually read something like:
deny from all
AllowOverride None
These are security related, so there is no need to delete them or otherwise edit them. To overwrite set values in the hosts php.ini file, you may want to use:
php_value upload_max_filesize 512M
php_value post_max_size 512M
php_value memory_limit 128M
To overwrite boolean or logical settings use:
php_flag register_globals off
or
php_flag register_globals 0

Something similar can be done in IIS, but it is a lot more complex.

Thanks Muano

===Can I still use the TeX Notation filter in Moodle 2 like I did in Moodle 1.9?===
Yes, you can. In fact there is very little that has changed in the changing version. Not that the TeX filter has not be changed, it certainly has, but it does not affect how you will [[Using_TeX_Notation|use TeX Notation]]. It is supposed to be easier to add a third party plugin for TeX, but the relationship between Moodle and such tools as MathJax or Geogebra, or similar tools, is still to be determined.

:UPDATE: Mauno Korpelainen has successfully integrated a number of Maths tools onto Moodle. These tools include Geogebra, JSXGraph, Math, MathML, MathTran, tex, DragMath, Geonext, JSQuery, MathJax and if that were not enough, Mauno had also included a version of TinyMCE that has, as native, a Maths editing toolbar. Further information can be found on the Moodle 2 [[Advanced Maths Tools]] page.

===I want to change our logo and some other images but there seems no clear way of doing it.===
Moodle 2 has done things very differently here. Logos and other images are all controlled by the theme. Each theme folder is constructed the same way so it makes it easy to edit. Native Moodle themes use the moodle/pix folder to store common images. Look in there to find the logo for any native theme and that can be replaced by a new logo. Third party themes often use the moodle/theme/pix folder to store images, including logos.

Go and look at the theme folder and in it you will find the name of the theme you are using. In it you will also find the sub-folders for different elements and you should find your layout folder contains most of the instructions for controlling the layout, the Styles folder controls the appearance and so on. Images used in the theme can all be located there as well, in the pix folder.

If you want to use a theme that does not have an image or a logo, just the default icons, then you are talking a serious revamp. For that, you need to look at the [https://docs.moodle.org/dev/Themes_2.0| Themes 2.0] page.

===What about other elements of the Front Page?===
In some ways, Moodle 2 has made it easier to setup a front page the way you want it. Different themes will use different defaults, many moving away from the traditional three collumn, blocks, categories/courses, blocks, structure that pervaded Moodle 1.9. The Moodle 2 documentation has a more complete look at the [[Front page settings]] than can be viewed here. Also, for a better overview of how this can all be done at a site level, look at the [[Customising appearance]] pages.

===My Password is not being accepted as valid. How can I login as an Admin?===
There are a couple of causes for this problem, but the main one seems to be we forget the jumble of passwords we are required to remember. There are also a number of ways of getting around it, as well.

[http://moodle.org/mod/forum/discuss.php?d=18103 This discussion] covers just about all of them. There are a couple of scripts so be careful and use the right one if you need to.

If you do not wish to use a script, then you can try this:
Using phpMyAdmin, enter the database and look for the mdl_users table. The first line of that table's data should be the Guest, and the password for Guest is "guest", without the quote marks. Copy that password and then look for your identity. Paste the "guest" password over the top of yours when you locate it. You should then be able to get into your Moodle then, as an Admin.
It has been reported this does not work in every circumstance, but most. To get around that problem you might want to try commenting out the line
$CFG->passwordsaltmain =
That should then work.

===How can I extract orginal files from a Moodle backup file?===
But just in case you really want to get them from the backup file (an ".mbz" file) you downloaded (using the backup and restore feature), here it goes...

The backup file can actually be opened with the 7zip (http://www.7-zip.org/) program I mentioned. Once you open the file, you need to extract:

The files.xml file.
The files directory (folder).

Next step would be to open the "files.xml" file, and:

Search for the name of each file you want to get.
Take note of the value of the corresponding contenthash tag.
In the "files" folder you extracted, locate the file whose name is the same as the value of the contenthash and which will always be located in a folder whose name corresponds to the two first characters of the file name.

For example, lets assume I have a "backup_courses-120730.mbz" file of which I already extracted the "files.xml" file and the "files" folder, and that I'm looking for a PDF file named "Leadership.pdf".

So I open the files.xml file and:

1. Search for the string "Leadership.pdf", which in my case I find under the following <file id...> group tag:

<file id="12345">
<contenthash>fb6cf43a9b2d432403c70a2cb4c340dbb6225631</contenthash>
:
<filename>Leadership.pdf</filename>
:
<license>allrightsreserved</license>
<sortorder>1</sortorder>
</file>

2. I take note of the corresponding contenthash value: fb6cf43a9b2d432403c70a2cb4c340dbb6225631.

3. As the first two characters of the contenthash are "fb", I open the "fb" folder inside the "files" directory (which I previously extracted), and there I will find a file named "fb6cf43a9b...", so now I can rename that file as "Leadership.pdf", and then move it to another location (where I'll gather all the files I need from the backup).

Thanks to Guillermo Madero S for this answer.

==See Also==

*[[Beginning Moodle 2.0 Administration | Beginning Moodle 2.0 Administration ]]
*[[:Category:Administrator | Index of all Administrator-related pages]]

[[Category:FAQ]]