MoodleDocs - User contributions [en]

File:Overview of students.png

2014-05-07T05:42:57Z

Deraadt:

File:Bar in block - with details.png

2014-05-07T05:42:51Z

Deraadt:

Progress Bar block

2014-05-07T05:42:33Z

Deraadt: Updating after recent functional changes

[[Blocks|Back to Blocks page]]

== Features ==

[[Image:Bar_in_block_-_with_details.png|right|A progress bar for a student]]
* The Progress Bar is a time-management tool for students.
* It visually shows what activities/resources a student is supposed to interact with in a course.
* It is colour coded so students can quickly see what they have and have not completed/viewed.
* The teacher selects which pre-existing activities/resources are to be included in the Progress Bar and when they should be completed/viewed.
* Ordering can be done by times/deadlines or by the ordering of activities in the course.
[[Image:Overview_of_students.png|thumb|right|The overview page]]
* There is an overview page allowing teachers to see the progress of all students in a class, which is helpful for finding students at risk.

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

== Installation ==

The Progress Bar block is added like other blocks ([[Installing_contributed_modules_or_plugins|How to install a block]]).

== Setting up a Progress Bar ==

Once the progress bar is installed, you can use it in a course as follows.
# Turn editing on
# Create your activities/resources as normal
# Add the Progress Bar block to your page ([[Blocks|How to add a block]])
# Move your Progress Bar block into a prominent position (click and drag the block title)
# Choose to:
#* Monitor all activities (pre-fills configuration page)
#* Select which activities to monitor (start from scratch)
# Set the activities/resources you want shown in the block to "Yes" and those you don't to "No".
# Set the date and time when the activity/resource is expected to be completed/viewed by (some activities have deadlines set, if so, that deadline can be used or another can be set in the Progress Bar block configuration).
# Save changes.

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

Hidden items will not appear in the Progress Bar until they are unhidden. This is useful for a scheduled release of activities.

== Links ==

* [http://moodle.org/plugins/view.php?plugin=block_progress Block code in Plugins repository]
* [http://tracker.moodle.org/browse/CONTRIB/component/10489 Bug Tracker Page] (Please report bugs here)
* [http://cvs.moodle.org/contrib/plugins/blocks/progress/ CVS Repository]

== Acknowledgements ==

* Thanks to:
** Toshimi Hatanaka for contributing a Japanese translation
** Yvonne Schneider and Joachim Vogelgesang for contributing a German translation
** Maria João Spilker for contributing a Portuguese-Brazilian translation
** Pieter Wolters for contributing a Dutch translation
** Fernando Sánchez for contributing a Spanish translation
** Fabien Sartoretti for contributing a French translation
** Adam Levy for contributing queries and strings for Hot Potatoes support
** Petras Virzintas for contributing queries for Turnitin support
** Willian Mano for helping with the modern look CSS
** Matthieu Rolland for contributing queries for the Questionnaire module
** Johan Reinalda for contributing global config changes for block colours

[[Category:Contributed code]]

Moodle research

2013-05-01T06:53:06Z

Deraadt: Adding link to research.moodle.net

{{About Moodle}}
<p class="note">There site [http://research.moodle.net research.moodle.net] has been established as a point of contact for Moodle researchers. On that site there is a [http://research.moodle.net/mod/data/view.php?id=1 Moodle Reseach Collection] containing Moodle-related research publications.</p>

A growing, community-contributed collection of research into LMS (Learning Management Systems) and particularly Moodle.

=Moodle-specific research=
Academic, governmental, organisational research (mostly) involving Moodle (design, use, implementation...). Check [[Moodle research FAQ|here]] for details.
==Print (papers, reports, collections, theses...)==
*Al-Ajlan, A. & Zedan,H. (2008) [http://www.computer.org/portal/web/csdl/doi/10.1109/FTDCS.2008.22 Why Moodle] 12th IEEE International Workshop on Future Trends of Distributed Computing Systems, 2008
*Alier, M., Casany, J., Casado, P. (2007) [http://74.125.155.132/scholar?q=cache:9f3NRhHqyDMJ:scholar.google.com/+moodle&hl=en&as_sdt=0,5 Mobile Extension Of A Web Based Moodle Virtual Classroom]. Proceedings of E-Challenges Conference, 2007.
*Al Naddabi, Z. (2007). [http://www.editlib.org/p/26540 A Moodle Course: Design and Implementation in English for Academic Purposes Instruction]. In T. Bastiaens & S. Carliner (Eds.), Proceedings of World Conference on E-Learning in Corporate, Government, Healthcare, and Higher Education 2007
*Beatty, B. & Ulasewicz, C. (2006) [http://www.springerlink.com/content/bg0613214k409500/ Faculty Perspectives on Moving from Blackboard to the Moodle Learning Management System]. TechTrends Volume 50, Number 4, 36-45.
*Berggren, A. et al (2005) [http://74.125.155.132/scholar?q=cache:2t2PDSl4o_4J:scholar.google.com/+moodle&hl=en&as_sdt=0,5 Practical and Pedagogical Issues for Teacher Adoption of IMS Learning Design Standards in Moodle LMS]. Journal of Interactive Media in Education, 2005(02)
*Brandl, K. (2007) [http://74.125.155.132/scholar?q=cache:b1gGpxaaCR0J:scholar.google.com/+moodle&hl=en&as_sdt=0,5 Are You Ready to "Moodle"?]. Language Learning & Technology, May 2005, Vol.9(2)
*Burgos, D. et al. (2007) [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.169.251&rep=rep1&type=pdf A First Step Mapping IMS Learning Design and Moodle]. Journal of Universal Computer Science, Vol. 13 (7).
*Cowan, P. (2006). [http://www.editlib.org/p/22507 Factors influencing Pre-Service teachers’ attitudes towards using a Moodle environment for teaching and learning]. In C. Crawford et al. (Eds.), Proceedings of Society for Information Technology & Teacher Education International Conference 2006
*Deng, Y. & Hemphill, L. (2006). [http://www.editlib.org/p/22054 Demonstrating Online K12 Teaching Strategies in a Moodle Course Management Environment]. In C. Crawford et al. (Eds.), Proceedings of Society for Information Technology & Teacher Education International Conference 2006
*DeSchryver, M., Mishra, P., Koehleer, M. & Francis, A. (2009). [http://www.editlib.org/?fuseaction=Reader.ViewFullText&paper_id=30612 Moodle vs. Facebook: Does using Facebook for Discussions in an Online Course Enhance Perceived Social Presence and Student Interaction?]. In I. Gibson et al. (Eds.), Proceedings of Society for Information Technology & Teacher Education International Conference 2009
*Dougiamas, M. & Taylor, P. (2003). [http://www.editlib.org/p/13739 Moodle: Using Learning Communities to Create an Open Source Course Management System]. In D. Lassner & C. McNaught (Eds.), Proceedings of World Conference on Educational Multimedia, Hypermedia and Telecommunications 2003.
*Graf, S. &List, B.(2005) [http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1508637 An evaluation of open source e-learning platforms stressing adaptation issues]. Advanced Learning Technologies, 2005. ICALT 2005.
*Guttierez, E. et al. (2009) [http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6VCJ-4XB1967-2&_user=10&_coverDate=02%2F28%2F2010&_rdoc=1&_fmt=high&_orig=gateway&_origin=gateway&_sort=d&_docanchor=&view=c&_searchStrId=1688004089&_rerunOrigin=scholar.google&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=f9a939ec272e44d724d630209831642a&searchtype=a A new Moodle module supporting automatic verification of VHDL-based assignments]. Computers & Education, Vol 54 (2), Feb 2010.
*Hueros, D. & Sanchez, A. (2010) [http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6VDC-50HWJ4Y-4&_user=10&_coverDate=11%2F30%2F2010&_rdoc=1&_fmt=high&_orig=gateway&_origin=gateway&_sort=d&_docanchor=&view=c&_searchStrId=1687987167&_rerunOrigin=scholar.google&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=15927cf368be7fc0df80aa91ac4e92a3&searchtype=a Motivational factors that influence the acceptance of Moodle using Technology Acceptance Model (TAM)]. Computers in Human Behavior. Vol. 26(6) Nov 2010.
*Jide, W. & Li, Z. (2009) [http://en.cnki.com.cn/Article_en/CJFDTOTAL-YCJY200905004.htm New Progresses in the Domestic Research on Moodle] Journal of Distance Education.
*Knutzen, B. & Kennedy, D.M. (2008). [http://www.editlib.org/p/28913 Can Learning to Use Moodle Alter Teachers’ Approaches to Teaching?]. In J. Luca & E. Weippl (Eds.), Proceedings of World Conference on Educational Multimedia, Hypermedia and Telecommunications 2008
*Pfaffman, J. (2004). [http://www.editlib.org/p/13664 Integrating Moodle into a Course for Pre- and In-service Teachers]. In R. Ferdig et al. (Eds.), Proceedings of Society for Information Technology & Teacher Education International Conference 2004
*Kemp, J. Livingstone, D. (2008) [http://74.125.155.132/scholar?q=cache:Kvnq5aCMDSwJ:scholar.google.com/+moodle&hl=en&as_sdt=0,5 Integrating Web-Based and 3D Learning Environments: Second Life Meets Moodle]. UPGRADE Vol. IX, No. 3, June 2008
*Romero,C. et al (2009) [http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6V03-4R98K46-7&_user=10&_coverDate=03%2F31%2F2009&_rdoc=1&_fmt=high&_orig=gateway&_origin=gateway&_sort=d&_docanchor=&view=c&_searchStrId=1687992777&_rerunOrigin=scholar.google&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=f15fe515105a3c120401c2a6c6d1551e&searchtype=a Evolutionary algorithms for subgroup discovery in e-learning: A practical application using Moodle data]. Expert Systems with Applications, Volume 36(2)1, March 2009.
*Romero, S. Ventura, C. & Garcia, E. (2007) [http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6VCJ-4P7FCT6-1&_user=10&_coverDate=08%2F31%2F2008&_rdoc=1&_fmt=high&_orig=gateway&_origin=gateway&_sort=d&_docanchor=&view=c&_searchStrId=1686659096&_rerunOrigin=scholar.google&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=b77769e114cba19d78a12526b8755858&searchtype=a Data mining in course management systems: Moodle case study and tutorial]. Computers & Education. Vol. 51 (1), Aug 2008 (Abstract only, paid access).
*Li, P. et al. (2009) [http://en.cnki.com.cn/Article_en/CJFDTOTAL-YCJY200803014.htm Classroom Response Systems Based on Moodle]. Distance Education Journal;2008-03
*Martín-Blas, T. & Serrano-Fernández (2009) [http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6VCJ-4T2RYPV-1&_user=10&_coverDate=01%2F31%2F2009&_rdoc=1&_fmt=high&_orig=gateway&_origin=gateway&_sort=d&_docanchor=&view=c&_searchStrId=1687986242&_rerunOrigin=scholar.google&_acct=C000050221&_version=1&_urlVersion=0&_userid=10&md5=81ca28b957fbd194f133ad342073759a&searchtype=a The role of new technologies in the learning process: Moodle as a teaching tool in Physics]. Computers & Education. Vol. 52(1), Jan 2009.
*Meurant, R.C. (2009) [http://www.springerlink.com/content/u08884qr83704276/ Computer-Based Internet-Hosted Assessment of L2 Literacy: Computerizing and Administering of the Oxford Quick Placement Test in ExamView and Moodle].Communications in Computer and Information Science, 2009, Vol. 60.
*Rakoczi, Gergely. (2010) [http://www.fm-kp.si/zalozba/ISBN/978-961-266-066-6/prispevki/rakoczi.pdf "Cast your Eyes on Moodle: An Eye Tracking Study investigating learning with Moodle"]
*Liu Suqin & Li Jiahou (2007) [http://en.cnki.com.cn/Article_en/CJFDTOTAL-YCJY200701002.htm Curriculum Design BIG6 Mode Based on Moodle]. Distance Education Journal.
*Stewart, B. et al (2007) [http://www.igi-global.com/bookstore/article.aspx?TitleId=1705 Choosing MOODLE: An Evaluation of Learning Management Systems at Athabasca University. International Journal of Distance Education Technologies (IJDET)]. Vol. 5(3)
*Zenha-Rela,M. & Carvalho, R.(2006) [http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=4117034 Work in Progress: Self Evaluation Through Monitored Peer Review Using the Moodle Platform]. Frontiers in Education Conference.
*Zhiqiang, M & Yanli, W. (2008) [http://en.cnki.com.cn/Article_en/CJFDTOTAL-DDJY200807013.htm An Analysis of Moodle-based Online Learning Barriers]. Distance Education in China, Aug 2008.

==Presentations and videos==
==Other material (eg projects)==

=LMS research - general=
Broader academic, governmental, organisational research on LMS/VLE useful to Moodle to learn from. Check [[Moodle research FAQ|here]] for details.
==Print (papers, reports, collections, theses...)==
*Carmean, C. & Haefner,J. (2002). [http://net.educause.edu/ir/library/pdf/ERM0261.pdf Mind over matter: Transforming course management systems into effective learning environments]. EDUCAUSE Review, Vol. 37, No. 6, pp. 27–33.
*Chang, Chinhong Lim (2008) [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 Faculty Perceptions and Utilization of a Learning Management System in Higher Education] (dissertation)
*Keesee, G. & Shepard, M.(2011) [http://www.westga.edu/~distance/ojdla/spring141/keesee_shepard141.html Perceived Attributes Predict Course Management System Adopter Status]. Online Journal of Distance Learning Administration, Vol 14/1.
*Lane, L. (2009) [http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 Insidious pedagogy: How course management systems impact teaching]. First Monday, Vol. 14, Number 10 - 5 Oct 2009
*[http://en.wikipedia.org/wiki/Ofsted OFSTED] (2009) [http://www.ofsted.gov.uk/Ofsted-home/Publications-and-research/Browse-all-by/Documents-by-type/Thematic-reports/Virtual-learning-environments-an-evaluation-of-their-development-in-a-sample-of-educational-settings Virtual learning environments: an evaluation of their development in a sample of educational settings].
*Sancar, H. & Cagiltay, K. (2008). [http://www.editlib.org/p/28931 Effective Use of LMS: Pedagogy through the Technology]. In J. Luca & E. Weippl (Eds.), Proceedings of World Conference on Educational Multimedia, Hypermedia and Telecommunications 2008

==Presentations and videos==
==Other material==
=Questions? Try here=
See the growing list at [[Moodle research FAQ]]

Installing MSSQL for PHP

2012-04-27T06:30:50Z

Deraadt: Clarifying alter commands

== Introduction ==

This short manual is suitable if you are trying to run Moodle using the SQL*Server (MSSQL) RDBMS. Steps detailed below must be performed '''before''' installing Moodle itself.

Some of this may also apply if you wish to access an MSSQL server for external db authentication/enrollment.

First of all, minimum required version of MSSQL has been stabilised to MSSQL 2005 (v.9), although it '''might work with MSSQL 2000 (v.8) or newer'''. All the development process has been performed using MSSQL 2005 and there could be some '''unknown problems''' with previous releases.

While PHP comes with one, more or less, standard extension (mssql) that provides access to MSSQL databases, early we found some hard limits on it. Basically such default extension has some limits that prevent us to use it at all (you can find more info about these problems [[Development:XMLDB problems#MSSQL, PHP, UTF-8 and UCS-2|here]]).

So, in order to allow PHP (i.e. Moodle) to access to MSSQL DBs properly we have to install a '''mssql extension alternative''' to save us from the problems related above. See the sections below for details about the various options.

== Installation overview ==

1. Get MSSQL Server installed and running. ([http://www.microsoft.com/sql/editions/express/default.mspx A free limited version, SQL Server Express Edition] is available for testing.)
:Make sure that you choose mixed authentication (Windows and local accounts) to keep things simpler later. You'll be asked to define the "sa" account password (it's the default System Administrator account which has full access to all databases by default).

2. Make sure MS SQL Server can accept incoming TCP/IP connections on port 1433 (the standard one).
:You might need to explicitly allow this in your Windows firewall (see the Control Panel). You may also need to edit options in the :'''SQL Server Configuration Manager''' -> '''Network Configuration''' -> '''Protocols''' -> '''TCP/IP enabled'''

3. Open the "SQL Server Management Studio" and create a new empty database. If you are using the "sa" account then you don't need to do anything else here.

4. Configure these settings in your created (and still empty) database:

:* ANSI NULLS Enabled = true (Toggle to true in DB Properties > Options or run ALTER DATABASE xxxx SET ANSI_NULLS ON)
:* Quoted Identifiers Enabled = true (Toggle to true in DB Properties > Options or run ALTER DATABASE xxxx SET QUOTED_IDENTIFIER ON)
:* (Moodle 2.x only) Row Versioning Enabled (ALTER DATABASE xxxx SET READ_COMMITTED_SNAPSHOT ON)
:** This is not settable via the DB properties. To set READ_COMMITTED_SNAPSHOT, there must be no active connections to the database except for the connection executing the ALTER command. If you are viewing the DB in the Server Management Studio, disconnect from any servers in the "Object Explorer" (right-click > Disconnect), then create a "New Query" and run the ALTER command. See http://msdn.microsoft.com/en-us/library/bb522682.aspx for details.

5. Get PHP installed with a web server. Unless you want to do it under IIS or some other way, the packages on the [http://download.moodle.org Moodle download page] are a good solution.

6. Choose one of the following specific sections for your server to install the '''mssql extension alternative''' installed and running properly on your PHP box.

7. Set the following settings in your php.ini file
:* mssql.textlimit = 20971520
:* mssql.textsize = 20971520

8. With all this properly configured, you can continue with a [[Installing Moodle|standard Moodle installation]].

== Using the SQL Server 2005 Driver for PHP from Microsoft on Windows ==
In July 2008 Microsoft [http://social.msdn.microsoft.com/forums/en-US/sqldriverforphp/thread/a10e5202-9e41-4ff8-a33e-fbcc7b951be2/ released] a new SQL Server 2005 Driver for PHP. This is a PHP extension that allows PHP scripts to read and write data on Microsoft SQL Server databases and it overcomes the problems with the native SQL Server extension that was previously bundled with PHP.

This Microsoft driver is the standard database layer for running Moodle 2 under Microsoft SQL Server databases. See [[Using the Microsoft SQL Server Driver for PHP]] the installation and configuration details.

This driver is only supported in Moodle 2.0 and up. You should use [https://docs.moodle.org/en/Installing_MSSQL_for_PHP#Using_FreeTDS_on_Windows FreeTDS] if you are installing an older version of Moodle.

See MDL-16497 and MDL-15093 for more background information.

== Using FreeTDS on Windows ==

<p class="note">'''Important Note 1:''' Due to some previous bugs it's highly recommendable to use PHP >= 5.2.6 and FreeTDS 0.82 + post-release patches ([http://tracker.moodle.org/browse/MDL-14725 more info]).</p>

If your web server is on Windows, use '''php_dblib.dll'''. Despite the name, it's FreeTDS compiled for Windows. (Go to this page for information on [https://docs.moodle.org/en/FreeTDS Using FreeTDS for Unix].)

Originally we were using the DLLs available at [http://kromann.info/article.php?Id=11062598797760000 Frank Kromann's site], but they are outdated (using old versions of FreeTDS) and that has caused [http://tracker.moodle.org/browse/MDL-14725 some problems] in the past.

So, right now, the recommended way to use FreeTDS under Windows is to use PHP 5.2.x following the following instructions:

1. Download the appropriate copy of php_dblib.dll from the list below, and save it into your /PHP/ext directory.

{| border="1" align="center" cellpadding="5" style="text-align: center;"
|-
! PHP version !! [http://www.iis-aid.com/articles/my_word/difference_between_php_thread_safe_and_non_thread_safe_binaries Thread Safe] !! FreeTDS version !! Download URL
|-
| rowspan="2" | PHP 5.2.x (vc6) || Yes || 0.82 + 20090302 patches || [http://download.moodle.org/download.php/dblib/php52/DBLIB_TS.zip Download!]
|-
| No || 0.82 + 20090302 patches || [http://download.moodle.org/download.php/dblib/php52/DBLIB_NOTS.zip Download!]
|-
| rowspan="2" | PHP 5.3.x (vc9) || Yes || 0.82 + 20090904 patches || [http://download.moodle.org/download.php/dblib/php53/DBLIB_TS.zip Download!]
|-
| No || 0.82 + 20090904 patches || [http://download.moodle.org/download.php/dblib/php53/DBLIB_NOTS.zip Download!]
|-
| colspan="4" | Thanks to [http://remote-learner.net/ Remote-Learner]] (Moodle [http://moodle.com/partners/ Partner]) and specially to Bryan Williams, donating one Visual C++ 6.0 Pro license to Moodle. Thanks to Trevor Johnson and his builds of the dblib extensions. Thanks to Daniele, Doug, Luis, Sean and many others by their collaboration in MDL-14725. Thanks to Frediano Ziglio and James K. Lowden from [http://freetds.org freetds.org] by their support. Thanks to Alastair Hole by providing the PHP 5.3 builds of the libraries. Thanks!
|}

(alternatively here you can find some [[Development:Compiling FreeTDS under Windows|instructions to build those freetds extensions under win32]] yourself)

2. FreeTDS requires the .NET Framework v1.1 to be installed. You can [http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&DisplayLang=en download it from the Microsoft website] along with its [http://www.microsoft.com/downloads/details.aspx?FamilyID=a8f5654f-088e-40b2-bbdb-a83353618b38&DisplayLang=en service pack]. Alternatively, if you do not wish to install this framework, you can [http://kromann.info/ms-libs/msvcr71.dll download the required DLL] from Frank's site, and save it into your /PHP root directory.

3. Edit your /PHP/php.ini file and add this line:

extension=php_dblib.dll

Make sure that any lines referring to the php_mssql.dll extension are DISABLED (commented out).

4. When the PHP engine loads the FreeTDS extension it needs to be passed certain infiormation in order to be able to connect to your Moodle database. To retrieve this information FreeTDS looks for a file called '''freetds.conf''' in the root folder of the server that PHP installed on (e.g. C:\).

'''freetds.conf''' should have the following structure:

[global]
host = xxx.xxx.xxx.xxx (host name or ip of the MSSQL server)
port = 1433
client charset = UTF-8
tds version = 8.0
text size = 20971520

If you want to connect to a particular [http://msdn.microsoft.com/en-us/library/aa174516(SQL.80).aspx instance] of MSSQL you should specify the instance name:

[global]
host = xxx.xxx.xxx.xxx (host name or ip of the MSSQL server)
instance = xxx (instance name, e.g. INST2)
port = 1433
client charset = UTF-8
tds version = 8.0
text size = 20971520

'''Notes:'''
*You can configure FreeTDS to look for the freetds.conf file in any directory that you want - you don't have to use C:\. To do this create a SYSTEM environment variable called '''FREETDS''' and point it to the directory where you have installed the freetds.conf file. If you do not set this environment variable FreeTDS will look for the freetds.conf file in the C:\ folder, which is the default. One possible benefit of setting the FREETDS environment variable and using a different installation directory for freetds.conf is that C:\ is very predictable to a hacker that knows anything about FreeTDS and that is the first place that he would look if he wanted to compromise your system. So, using a different installation directory would just make your system stronger. See the FreeTDS [http://www.freetds.org/userguide/envvar.htm Setting the environment variables] documentation for more information about this FREETDS environment variable.

*Alternatively, you can [[Development:Compiling FreeTDS under Windows|recompile]] the FreeTDS extension yourself and change the default location to your preferred location at compile time. Then it is not necessary to create any environment variable. You must just ensure that freetds.conf is in the same folder that you specify when you compile php_dblib.dll.

*MSSQL is usually installed with port 1433 as the default. However, if the port was changed on your server when you installed MSSQL then you need to specify the correct port number.

5. Your Moodle '''config.php''' should include lines like these:

<code php>
$CFG->dbtype = 'mssql_n'; // Required
$CFG->dbhost = 'localhost'; // assuming MS SQL is on the same server, otherwise use an IP
$CFG->dbname = 'moodle'; // or whatever you called the database you created
$CFG->dbuser = 'yourusername'; // I usually use the 'sa' account (dbowner perms are enough)
$CFG->dbpass = 'yourpassword';
$CFG->dbpersist = false;
$CFG->prefix = 'mdl_'; //Prefix, you can change it, but NEVER leave it blank.
</code>

If you don't have a config.php file yet, it can be generated as normal from the Moodle installer. Alternatively you can use the config-dist.php file that comes with the Moodle package to create your own config.php file.

6. Restart or start your web server. If Moodle still cannot communicate with the database server, please turn display_startup_errors to "On" in your /PHP/php.ini file, then restart the web server and check for any errors that may indicate incorrect DLL versions or missing dependencies. These error reports, turned off by default in PHP, can be vital in locating a problem with new extension installations.

7. Database conection test, try this PHP script, just put in a text file called test.php change ('localhost', 'db_user', 'db_password') to suite your setup, and load from local host (http://localhost/test.php)...

<code php>
<?php
$link = mssql_connect('localhost', 'db_user', 'db_password');
if(!$link) {
echo'Could not connect';
die('Could not connect: ' . mssql_error());
}
echo'Successful connection';
mssql_close($link);
?>
</code>

8. Install Moodle as usual. Good luck!

=== Troubleshooting ===
If you encounter some problems you can try:
*check that you have DotNet framework 1.1 installed (later version are installed on Vista, but you could need this specific one)<br />
*enable TCP/IP for MSSQL: SQL Server 2005 Network Configuration -> Protocols for MSSQLSERVER -> TCP/IP (Enable) -> Properties -> Ip Addresses -> 127.0.0.1 (Active+Enable)<br />
*make sure the SQL Server Browser service is running SQL Server 2005 Network Configuration -> SQL Server Services<br />
*if you are using SQL Server 2005 and you have the error ''4004: Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier'', try the ODBTP method (next chapter). The SQL Server complaining that it doesn't support pure Unicode via TDS or older versions of ODBC. Microsoft has deprecated DB-Library a long ago, in favor of ODBC, OLE DB, or SQL Native Client. Many new features of SQL 2005 aren't accessible via DB-Library so if you need them, you could have to switch away from tools based on TDS and DB-Library :(

== FreeTDS on Linux (on Ubuntu by compiling an mssql.so extension) ==
This is a good read to [http://www.robert-gonzalez.com/2009/02/18/building-the-php-ms-sql-server-extension-from-source-on-ubuntu-810/ building a FreeTDS based mssql extension for apache on Ubuntu]. Do note that [http://www.freetds.org/news.html freeTDS] 0.91 was recently released, you can find latest versions [http://freetds.sourceforge.net/ here].

Note: the freetds.conf file you use should have "text size = 20971520" as mentioned in the FreeTDS on Windows section otherwise you might see sessions logging out or worse apache segmentation faults. Also see [[FreeTDS]].

== Using FreeTDS on Debian Lenny ==
I found the following solution using:
* PHP Version 5.2.6-1+lenny9
* Microsoft SQL Server Enterprise Edition, version: 9.00.4053.00
<pre>apt-get install libsybdb5 freetds-common php5-sybase
/etc/init.d/apache2 restart</pre>
At the end of the process, if all goes fine, you will find in the mssql section of phpinfo();

{| class="nicetable"
|-
! MSSQL Support
! enabled
|-
| Library version
| FreeTDS
|}

Once FreeTDS is correctly installed, don not forget to set it up following explanations in https://docs.moodle.org/en/FreeTDS

== See Also ==
* FreeTDS for Windows is obsolete and too slow as of 2011. See: [http://moodle.org/mod/forum/discuss.php?d=183987 Hardware and Performance Forum]
* [[Installing Moodle]]
* [[Errors FAQ]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
* [[Beginning Administration FAQ]]
* [[Installing Postgres for PHP]]
* [[Using the Microsoft SQL Server Driver for PHP]]
* [[Installing Oracle for PHP]]

[[Category:FAQ]]
[[Category:Installation]]
[[Category:Developer]]
[[Category:XMLDB]]
[[Category:DB]]
[[Category:SQL databases]]

Theme settings

2012-04-26T05:29:02Z

Deraadt: /* Allow theme changes in the URL */

{{Themes}}
== Theme settings ==
An administrator can change theme settings in ''Settings > Site administration > Appearance > Themes > Theme settings''.

[[File:Themesettings.png]]

===Theme list===
This lists the themes available for course and user themes. Leave this blank to allow any valid theme to be used. If you want to shorten the theme menu, you may specify a comma-separated list of names, though don't use spaces (e.g. standard,orangewhite).

You can preview the available themes in ''Settings > Site Administration > Appearance > Themes > Themes selector.''

===Theme designer mode===
Turn this on if you are designing and testing themes as it will stop the themes being cached and enable you to see theme changes quickly. (You can also do this with the Clear theme cache button on the theme selector page.)

===Allow user themes===
If the option ''allowuserthemes'' is enabled, each user may select their preferred theme on the edit profile page. All Moodle pages will be displayed in the user's theme, apart from courses where a course theme has been set.

===Allow course themes===
If you enable this, then teachers will be able to set their own course themes. Course themes override all other theme choices (site, user, or session themes).

*If the option ''allowcoursethemes'' is enabled, each editing teacher may select their course theme via the Force theme option on the [[course/edit|Course settings]] page. The course will always be displayed in the theme specified in the course setting, with user and the site themes being overwritten.

===Allow category themes===
When enabled, themes can be set at the category level. This will affect all child categories and courses unless they have specifically set their own theme. WARNING: Enabling category themes may affect performance.

===Allow theme changes in the URL===
*If this is checked then the theme may be changed by adding <code>?theme=theme_name</code> (or <code>&theme=theme_name</code> if there are other URL parameters) to the URL in the browser. Theme names should be in lower case with spaces replaced by underscores, for example the theme "Formal white" should be entered as <code>?theme=formal_white</code>

===Allow users to hide blocks===
Allows users to display and hide blocks

===Allow blocks to use the docks===
*If the theme allows it, then checking this will allow the user to move blocks to the side dock.

===Custom menu items===
The custommenuitems setting allows you to create a drop down menu that can be displayed by themes that support it. Currently all themes that are provided with Moodle 2.0 support this custom menu.

You are able to create the custom menu by entering custom menu items one per line into the setting. Each item is preceded by a number of hyphens (-), the number of hyphens determines the depth of the item. So items that are '''NOT''' preceded by a hyphen appear on the top level of the menu (always visible), items with a single hyphen appear on a drop down menu below the previous top level item, and items with two hyphens appear on a drop down menu below the previous first level item and so on.

The content of each item is constructed of up to three bits, each separated by a '''|''' (Shift + \) character. The bits are '''label''' | '''url''' | '''tooltip'''.
; label : This is the text that will be shown within the menu item. You must specify a label for every item on the menu.
; url : This is the URL that the user will be taken to it they click the menu item. This is optional, if not provided then the item will not link anywhere.
; tooltip : If you provide a URL you can also choose to provide a tooltip for the link that is created with the URL. This is optional and if not set the label is used as the tooltip for the menu item.

The following is an example of how you would create a custom menu:

<pre>
Moodle community|http://moodle.org
-Moodle free support|http://moodle.org/support
-Moodle development|http://moodle.org/development
--Moodle Tracker|http://tracker.moodle.org
--Moodle Docs|https://docs.moodle.org
-Moodle News|http://moodle.org/news
Moodle company
-Moodle commercial hosting|http://moodle.com/hosting
-Moodle commercial support|http://moodle.com/support
</pre>

Note: The custom menu does not escape characters within the label, if you want to use a special HTML character such as an ampersand you must escape it yourself within the label. e.g. use & instead of &.

For more information on this setting please see the ''Using Moodle'' forum discussion [http://moodle.org/mod/forum/discuss.php?d=149803 Moodle 2.0: Custom menu in core]

==== Multilanguage support ====

You can add a language code (or a comma separated list of codes) as the 4th item of the line. The line will be then printed if and only if the user has currently selected the listed language. For example:

<pre><nowiki>
English only|http://moodle.com|English only item|en
German only|http://moodle.de|Deutsch|de,de_du,de_kids
</nowiki></pre>

===Enable device detection===
Will detect mobile and tablets that identify themselves via the web browser at the time of login to Moodle. These work with the theme selector. When the theme selector has identified a default, mobile and tablet themes, this feature will use that theme.

===Device detection regular expressions===
This will allow you to customize the theme selector options. For example, you can add a custom theme for IE6 and another for Windows CE by entering the identifying expressions the browser sends and the "Return value" you want to display as the theme selectors "Device type".

==Special themes==

=== Session themes ===
Moodle offers an additional way to set a theme - the '''session theme'''. This is set with the URL and lasts until you log out. When you next login, the site/course/user themes are active again. This option is great for theme testing and works perfectly when you want to enable different themes for different situations.

For example you can offer a special link for PDA users and integrate the session theme ''orangewhitepda'' in that link. Nobody needs to change any settings, you just click on that link. The session theme is called by the URL parameter <code>&theme=orangewhitepda</code>. The whole URL without the session theme could look like <code><nowiki>http://mymoodlesite.org/course/view.php?id=18</nowiki></code> and with the parameter for the PDA theme like <code><nowiki>"http://mymoodlesite.org/course/view.php?id=18&theme=orangewhitepda"</nowiki></code>.

In a standard Moodle installation, session themes are not active. To activate them the administrator must add the parameter <code>$CFG->allowthemechangeonurl = true;</code> to the Moodle ''config.php'' file in the Moodle base directory.

=== Page theme ===
A page theme is for special page-only themes set by code.

== Theme hierarchy ==
Here is the usual order that themes are considered by the Moodle interface.

{| style="border:1px dashed #ddd"
|- style="vertical-align:top;text-align:left"
!Theme type
! style="background:#eee"|Overwrites
!Display
! style="background:#eee"|Setting type
|- style="vertical-align:top"
|Site
|style="background:#eee"| -
|all pages*
|style="background:#eee"|saved in theme profile
|- style="vertical-align:top"
|User
|style="background:#eee"|Site theme
|all pages*
|style="background:#eee"|saved in user profile
|- style="vertical-align:top"
|Course
|style="background:#eee"|Site, user and session themes
|one course
|style="background:#eee"|saved in course profile
|- style="vertical-align:top"
|Session
|style="background:#eee"|Site and user themes
|all pages*
|style="background:#eee"|temporary until logout
|}
(* except courses with the course theme set)

=== Change default hierarchy===
The priority of themes can be set via the /moodle/config.php file. The order defines which theme wins when there are several set at different levels. You can set a variable called $CFG->themeorder (see config-dist.php for more details). By default it is set to:

<code><nowiki>$CFG->themeorder = array('page', 'course', 'category', 'session', 'user', 'site');</nowiki></code>

==Particular theme settings==

Logo, tagline, link colour, column width, custom CSS and other settings for a particular theme may be set by an administrator in ''Settings > Site administration > Appearance > Themes > Theme name''.

==See also==

*[http://www.youtube.com/watch?v=mCVsJ3Wsoj8 Video demonstrating how to set a category theme in Moodle 1.9]

[[es:Configuración de temas]]
[[fr:Configuration des thèmes]]
[[ja:テーマ設定]]
[[de:Design-Einstellungen]]

Theme settings

2012-04-26T05:27:59Z

Deraadt: /* Allow theme changes in the URL */

{{Themes}}
== Theme settings ==
An administrator can change theme settings in ''Settings > Site administration > Appearance > Themes > Theme settings''.

[[File:Themesettings.png]]

===Theme list===
This lists the themes available for course and user themes. Leave this blank to allow any valid theme to be used. If you want to shorten the theme menu, you may specify a comma-separated list of names, though don't use spaces (e.g. standard,orangewhite).

You can preview the available themes in ''Settings > Site Administration > Appearance > Themes > Themes selector.''

===Theme designer mode===
Turn this on if you are designing and testing themes as it will stop the themes being cached and enable you to see theme changes quickly. (You can also do this with the Clear theme cache button on the theme selector page.)

===Allow user themes===
If the option ''allowuserthemes'' is enabled, each user may select their preferred theme on the edit profile page. All Moodle pages will be displayed in the user's theme, apart from courses where a course theme has been set.

===Allow course themes===
If you enable this, then teachers will be able to set their own course themes. Course themes override all other theme choices (site, user, or session themes).

*If the option ''allowcoursethemes'' is enabled, each editing teacher may select their course theme via the Force theme option on the [[course/edit|Course settings]] page. The course will always be displayed in the theme specified in the course setting, with user and the site themes being overwritten.

===Allow category themes===
When enabled, themes can be set at the category level. This will affect all child categories and courses unless they have specifically set their own theme. WARNING: Enabling category themes may affect performance.

===Allow theme changes in the URL===
*If this is checked then the theme may be changed by adding <code>?theme={theme_name}</code> (or <code>&theme=theme_name</code> if there are other URL parameters) to the URL in the browser. Theme names should be in lower case with spaces replaced by underscores, for example the theme "Formal white" should be entered as <code>?theme=formal_white</code>

===Allow users to hide blocks===
Allows users to display and hide blocks

===Allow blocks to use the docks===
*If the theme allows it, then checking this will allow the user to move blocks to the side dock.

===Custom menu items===
The custommenuitems setting allows you to create a drop down menu that can be displayed by themes that support it. Currently all themes that are provided with Moodle 2.0 support this custom menu.

You are able to create the custom menu by entering custom menu items one per line into the setting. Each item is preceded by a number of hyphens (-), the number of hyphens determines the depth of the item. So items that are '''NOT''' preceded by a hyphen appear on the top level of the menu (always visible), items with a single hyphen appear on a drop down menu below the previous top level item, and items with two hyphens appear on a drop down menu below the previous first level item and so on.

The content of each item is constructed of up to three bits, each separated by a '''|''' (Shift + \) character. The bits are '''label''' | '''url''' | '''tooltip'''.
; label : This is the text that will be shown within the menu item. You must specify a label for every item on the menu.
; url : This is the URL that the user will be taken to it they click the menu item. This is optional, if not provided then the item will not link anywhere.
; tooltip : If you provide a URL you can also choose to provide a tooltip for the link that is created with the URL. This is optional and if not set the label is used as the tooltip for the menu item.

The following is an example of how you would create a custom menu:

<pre>
Moodle community|http://moodle.org
-Moodle free support|http://moodle.org/support
-Moodle development|http://moodle.org/development
--Moodle Tracker|http://tracker.moodle.org
--Moodle Docs|https://docs.moodle.org
-Moodle News|http://moodle.org/news
Moodle company
-Moodle commercial hosting|http://moodle.com/hosting
-Moodle commercial support|http://moodle.com/support
</pre>

Note: The custom menu does not escape characters within the label, if you want to use a special HTML character such as an ampersand you must escape it yourself within the label. e.g. use & instead of &.

For more information on this setting please see the ''Using Moodle'' forum discussion [http://moodle.org/mod/forum/discuss.php?d=149803 Moodle 2.0: Custom menu in core]

==== Multilanguage support ====

You can add a language code (or a comma separated list of codes) as the 4th item of the line. The line will be then printed if and only if the user has currently selected the listed language. For example:

<pre><nowiki>
English only|http://moodle.com|English only item|en
German only|http://moodle.de|Deutsch|de,de_du,de_kids
</nowiki></pre>

===Enable device detection===
Will detect mobile and tablets that identify themselves via the web browser at the time of login to Moodle. These work with the theme selector. When the theme selector has identified a default, mobile and tablet themes, this feature will use that theme.

===Device detection regular expressions===
This will allow you to customize the theme selector options. For example, you can add a custom theme for IE6 and another for Windows CE by entering the identifying expressions the browser sends and the "Return value" you want to display as the theme selectors "Device type".

==Special themes==

=== Session themes ===
Moodle offers an additional way to set a theme - the '''session theme'''. This is set with the URL and lasts until you log out. When you next login, the site/course/user themes are active again. This option is great for theme testing and works perfectly when you want to enable different themes for different situations.

For example you can offer a special link for PDA users and integrate the session theme ''orangewhitepda'' in that link. Nobody needs to change any settings, you just click on that link. The session theme is called by the URL parameter <code>&theme=orangewhitepda</code>. The whole URL without the session theme could look like <code><nowiki>http://mymoodlesite.org/course/view.php?id=18</nowiki></code> and with the parameter for the PDA theme like <code><nowiki>"http://mymoodlesite.org/course/view.php?id=18&theme=orangewhitepda"</nowiki></code>.

In a standard Moodle installation, session themes are not active. To activate them the administrator must add the parameter <code>$CFG->allowthemechangeonurl = true;</code> to the Moodle ''config.php'' file in the Moodle base directory.

=== Page theme ===
A page theme is for special page-only themes set by code.

== Theme hierarchy ==
Here is the usual order that themes are considered by the Moodle interface.

{| style="border:1px dashed #ddd"
|- style="vertical-align:top;text-align:left"
!Theme type
! style="background:#eee"|Overwrites
!Display
! style="background:#eee"|Setting type
|- style="vertical-align:top"
|Site
|style="background:#eee"| -
|all pages*
|style="background:#eee"|saved in theme profile
|- style="vertical-align:top"
|User
|style="background:#eee"|Site theme
|all pages*
|style="background:#eee"|saved in user profile
|- style="vertical-align:top"
|Course
|style="background:#eee"|Site, user and session themes
|one course
|style="background:#eee"|saved in course profile
|- style="vertical-align:top"
|Session
|style="background:#eee"|Site and user themes
|all pages*
|style="background:#eee"|temporary until logout
|}
(* except courses with the course theme set)

=== Change default hierarchy===
The priority of themes can be set via the /moodle/config.php file. The order defines which theme wins when there are several set at different levels. You can set a variable called $CFG->themeorder (see config-dist.php for more details). By default it is set to:

<code><nowiki>$CFG->themeorder = array('page', 'course', 'category', 'session', 'user', 'site');</nowiki></code>

==Particular theme settings==

Logo, tagline, link colour, column width, custom CSS and other settings for a particular theme may be set by an administrator in ''Settings > Site administration > Appearance > Themes > Theme name''.

==See also==

*[http://www.youtube.com/watch?v=mCVsJ3Wsoj8 Video demonstrating how to set a category theme in Moodle 1.9]

[[es:Configuración de temas]]
[[fr:Configuration des thèmes]]
[[ja:テーマ設定]]
[[de:Design-Einstellungen]]

Theme settings

2012-04-26T05:13:29Z

Deraadt: Adding information about theme URLs

{{Themes}}
== Theme settings ==
An administrator can change theme settings in ''Settings > Site administration > Appearance > Themes > Theme settings''.

[[File:Themesettings.png]]

===Theme list===
This lists the themes available for course and user themes. Leave this blank to allow any valid theme to be used. If you want to shorten the theme menu, you may specify a comma-separated list of names, though don't use spaces (e.g. standard,orangewhite).

You can preview the available themes in ''Settings > Site Administration > Appearance > Themes > Themes selector.''

===Theme designer mode===
Turn this on if you are designing and testing themes as it will stop the themes being cached and enable you to see theme changes quickly. (You can also do this with the Clear theme cache button on the theme selector page.)

===Allow user themes===
If the option ''allowuserthemes'' is enabled, each user may select their preferred theme on the edit profile page. All Moodle pages will be displayed in the user's theme, apart from courses where a course theme has been set.

===Allow course themes===
If you enable this, then teachers will be able to set their own course themes. Course themes override all other theme choices (site, user, or session themes).

*If the option ''allowcoursethemes'' is enabled, each editing teacher may select their course theme via the Force theme option on the [[course/edit|Course settings]] page. The course will always be displayed in the theme specified in the course setting, with user and the site themes being overwritten.

===Allow category themes===
When enabled, themes can be set at the category level. This will affect all child categories and courses unless they have specifically set their own theme. WARNING: Enabling category themes may affect performance.

===Allow theme changes in the URL===
*If this is checked then the theme may be changed by adding the <code>?theme={theme_name}</code> (or as <code>&theme=theme_name</code> if there are other URL parameters) to the URL in the browser. Theme names should be in lower case with spaces replaced by underscores, for example the theme "Formal white" should be entered as <code>?theme=formal_white</code>

===Allow users to hide blocks===
Allows users to display and hide blocks

===Allow blocks to use the docks===
*If the theme allows it, then checking this will allow the user to move blocks to the side dock.

===Custom menu items===
The custommenuitems setting allows you to create a drop down menu that can be displayed by themes that support it. Currently all themes that are provided with Moodle 2.0 support this custom menu.

You are able to create the custom menu by entering custom menu items one per line into the setting. Each item is preceded by a number of hyphens (-), the number of hyphens determines the depth of the item. So items that are '''NOT''' preceded by a hyphen appear on the top level of the menu (always visible), items with a single hyphen appear on a drop down menu below the previous top level item, and items with two hyphens appear on a drop down menu below the previous first level item and so on.

The content of each item is constructed of up to three bits, each separated by a '''|''' (Shift + \) character. The bits are '''label''' | '''url''' | '''tooltip'''.
; label : This is the text that will be shown within the menu item. You must specify a label for every item on the menu.
; url : This is the URL that the user will be taken to it they click the menu item. This is optional, if not provided then the item will not link anywhere.
; tooltip : If you provide a URL you can also choose to provide a tooltip for the link that is created with the URL. This is optional and if not set the label is used as the tooltip for the menu item.

The following is an example of how you would create a custom menu:

<pre>
Moodle community|http://moodle.org
-Moodle free support|http://moodle.org/support
-Moodle development|http://moodle.org/development
--Moodle Tracker|http://tracker.moodle.org
--Moodle Docs|https://docs.moodle.org
-Moodle News|http://moodle.org/news
Moodle company
-Moodle commercial hosting|http://moodle.com/hosting
-Moodle commercial support|http://moodle.com/support
</pre>

Note: The custom menu does not escape characters within the label, if you want to use a special HTML character such as an ampersand you must escape it yourself within the label. e.g. use & instead of &.

For more information on this setting please see the ''Using Moodle'' forum discussion [http://moodle.org/mod/forum/discuss.php?d=149803 Moodle 2.0: Custom menu in core]

==== Multilanguage support ====

You can add a language code (or a comma separated list of codes) as the 4th item of the line. The line will be then printed if and only if the user has currently selected the listed language. For example:

<pre><nowiki>
English only|http://moodle.com|English only item|en
German only|http://moodle.de|Deutsch|de,de_du,de_kids
</nowiki></pre>

===Enable device detection===
Will detect mobile and tablets that identify themselves via the web browser at the time of login to Moodle. These work with the theme selector. When the theme selector has identified a default, mobile and tablet themes, this feature will use that theme.

===Device detection regular expressions===
This will allow you to customize the theme selector options. For example, you can add a custom theme for IE6 and another for Windows CE by entering the identifying expressions the browser sends and the "Return value" you want to display as the theme selectors "Device type".

==Special themes==

=== Session themes ===
Moodle offers an additional way to set a theme - the '''session theme'''. This is set with the URL and lasts until you log out. When you next login, the site/course/user themes are active again. This option is great for theme testing and works perfectly when you want to enable different themes for different situations.

For example you can offer a special link for PDA users and integrate the session theme ''orangewhitepda'' in that link. Nobody needs to change any settings, you just click on that link. The session theme is called by the URL parameter <code>&theme=orangewhitepda</code>. The whole URL without the session theme could look like <code><nowiki>http://mymoodlesite.org/course/view.php?id=18</nowiki></code> and with the parameter for the PDA theme like <code><nowiki>"http://mymoodlesite.org/course/view.php?id=18&theme=orangewhitepda"</nowiki></code>.

In a standard Moodle installation, session themes are not active. To activate them the administrator must add the parameter <code>$CFG->allowthemechangeonurl = true;</code> to the Moodle ''config.php'' file in the Moodle base directory.

=== Page theme ===
A page theme is for special page-only themes set by code.

== Theme hierarchy ==
Here is the usual order that themes are considered by the Moodle interface.

{| style="border:1px dashed #ddd"
|- style="vertical-align:top;text-align:left"
!Theme type
! style="background:#eee"|Overwrites
!Display
! style="background:#eee"|Setting type
|- style="vertical-align:top"
|Site
|style="background:#eee"| -
|all pages*
|style="background:#eee"|saved in theme profile
|- style="vertical-align:top"
|User
|style="background:#eee"|Site theme
|all pages*
|style="background:#eee"|saved in user profile
|- style="vertical-align:top"
|Course
|style="background:#eee"|Site, user and session themes
|one course
|style="background:#eee"|saved in course profile
|- style="vertical-align:top"
|Session
|style="background:#eee"|Site and user themes
|all pages*
|style="background:#eee"|temporary until logout
|}
(* except courses with the course theme set)

=== Change default hierarchy===
The priority of themes can be set via the /moodle/config.php file. The order defines which theme wins when there are several set at different levels. You can set a variable called $CFG->themeorder (see config-dist.php for more details). By default it is set to:

<code><nowiki>$CFG->themeorder = array('page', 'course', 'category', 'session', 'user', 'site');</nowiki></code>

==Particular theme settings==

Logo, tagline, link colour, column width, custom CSS and other settings for a particular theme may be set by an administrator in ''Settings > Site administration > Appearance > Themes > Theme name''.

==See also==

*[http://www.youtube.com/watch?v=mCVsJ3Wsoj8 Video demonstrating how to set a category theme in Moodle 1.9]

[[es:Configuración de temas]]
[[fr:Configuration des thèmes]]
[[ja:テーマ設定]]
[[de:Design-Einstellungen]]

Capabilities/repository/webdav:view

2012-01-10T01:57:21Z

Deraadt: Adding repository capability default information

* This allows a user to access the [[WebDAV repository]].
* This capability is set to allowed (CAP_ALLOW) by default for course creators, teachers, editing teachers and managers, but not to guests or students.

Capabilities/repository/local:view

2012-01-10T01:55:44Z

Deraadt: Adding repository capability default information

* This allows a user to access the [[Server files repository]].
* This capability is set to allowed (CAP_ALLOW) by default for course creators, teachers, editing teachers and managers, but not to guests or students.

Capabilities/repository/filesystem:view

2012-01-10T01:54:36Z

Deraadt: Adding repository capability default information

* This allows a user to access the [[File system repository]].
* This capability is set to allowed (CAP_ALLOW) by default for course creators, teachers, editing teachers and managers, but not to guests or students.

Capabilities/repository/coursefiles:view

2012-01-10T01:46:06Z

Deraadt: Adding repository capability default information

* This allows a user to access the [[Legacy course files]] area.
* This capability is available in Moodle 2.0 onwards and replaces the capability moodle/course:managefiles.
* This capability is set to allowed (CAP_ALLOW) by default for course creators, teachers, editing teachers and managers, but not to guests or students.

[[Category:Capabilities|Repository]]
[[Category:Repositories]]

WebDAV repository

2012-01-10T01:45:15Z

Deraadt: Adding repository capability default information

{{Repositories}}
Web-based Distributed Authoring and Versioning (WebDAV) is a set of methods based on the Hypertext Transfer Protocol (HTTP) that facilitates collaboration between users in editing and managing documents and files stored on World Wide Web servers.

A WebDAV repository can be enabled by a site administrator in ''Settings > Site administration > Plugins > Repositories > Manage repositories''.

==WebDAV configuration==

After enabling the WebDAV repository, a repository instance can be created in ''Settings > Site administration > Plugins > Repositories > WebDAV repository''.

[[Image:Webdav config.png]]

===Options===
WebDAV type: Choose from HTTP or HTTPS connection

WebDAV server: The server name

WebDAV path: The path to webdav directory

Authentication: We currently only support HTTP Basic Authentication

WebDAV server port: The webdav server port

WebDAV server user: HTTP Basic authentication username

WebDAV server password: HTTP Basic authentication password

For example, if you are going to added an webdav server at http://webdavserver.tld/path/to/dir, you should use following options:
WebDAV type: HTTP
WebDAV Server: webdavserver.tld

== Configuring WebDAV on Microsoft Windows Server 2003 R2 (Service Pack 2), IIS V6.0 ==

=== Configure Windows Server 2003 ===

First we need to install WebDAV on the server. ''Note:'' when you promote a basic Windows Server 2003 installation to an application server, it installs various IIS 6 components but WebDAV isn’t one of them.

==== Install and Enable WebDAV on the Server ====

To install WebDAV on the IIS 6 machine, use Add or Remove Programs in Control Panel and run the Windows Components Wizard. You can find WebDAV under '''Application Server -> Internet Information Services -> World Wide Web Service -> WebDAV Publishing'''.

Once WebDAV is installed it needs to be enabled. Check the WebDAV option under the Web Service Extensions node in IIS Manager.

=== Configure IIS ===

Configuring a new virtual directory in IIS is a two-step process:

#Create a new virtual directory using the Virtual Directory wizard
#Configure the access permissions on the new virtual directory

==== Create New Virtual Directory ====
#Open IIS and right-click on your Moodle website. Select '''New -> Virtual Directory'''... from the pop-up menu.<br />[[Image:New_virtual_directory.png|200 px|Menu option required for creating new virtual directory]]
#Select '''New -> Virtual directory...''' from the pop-up menu. The '''Create New Virtual Directory Wizard''' is displayed.<br />[[Image:Wizard_intro.png|200 px|IIS Virtual Directory Creation Wizard]]
#Call the new virtual directory '''Moodledata'''.<br />[[Image:Name_directory.png|200 px|alt text]]
#Specify the path to the Moodledata directory.<br />[[Image:Choose_path.png|200 px|Choosing path to folder on server]]
#Ensure the new virtual directory has '''Read''', '''Write''' and '''Browse''' permissions.<br />[[Image:Directory_permissions.png|200 px|Specifying directory permissions]]
#Press the Finish button to create the new virtual directory.

==== Configuring Virtual Directory Properties ====

#Right-click on the new virtual directory and select Properties from the pop-up menu.<br />[[Image:Check_properties.png|200 px|Checking new virtual directory properties]]
#Ensure that '''Read''', '''Write''', '''Directory browsing''', and '''Log visits''' are checked. Ensure '''Index this resource''' is unchecked.<br />[[Image:Properties_view.png|200 px|Virtual directory properties correctly configured]]
#Click on the '''Directory Security''' tab and press the '''Authentication and access control''' Edit... button<br />[[Image:Authentication_tab.png|200 px|Directory Security authentication and access control]]
#Authenticated access configuration will depend on your needs. Basic access will require you to uncheck '''Enable anonymous access''' and check '''Basic authentication (password is sent in clear text)'''. You may get a warning about security:<br />[[Image:Authentication_warn.png|200 px|Directory security warning]]
#Your new virtual directory is ready for testing.<br />[[Image:Final_view.png|200 px|New virtual directory ready for use]]

=== Testing WebDAV on Windows XP ===

WebDAV needs to be enabled on any client machines that will be used to create and manage content for Moodle. Windows XP has a built-in WebDAV client service that needs to be enabled:

#Open the '''Services''' console under '''Administrative Tools''' and find the '''WebClient''' service.
#Double-click on this service to open its '''Properties''' sheet.
#Change the '''Startup Type''' to ''Automatic'', then click the Start button to start the service.

''Note:'' Internet Explorer 8.0 no longer supports web folders. See [http://blogs.msdn.com/b/askie/archive/2009/03/20/open-as-web-folder-not-in-the-internet-explorer-8-file-open-dialog.aspx this blog post from David Conner] for details. Instead, you will need to map a network drive (instructions on mapping a network drive are also given in David's blog post).

WebDAV path: /path/to/dir/

==Repository permissions==

This repository is accessible by default to administrators, course creators, teachers, editing teachers and managers, but not to guests or students. This [[Capabilities/repository/webdav:view|capability]] can be changed to control access to users with specific roles.

==See also==

* MDL-22663

[[Category:Site administration]]
[[de:WebDAV Repository]]

Server files repository

2012-01-10T01:43:17Z

Deraadt: Adding repository capability default information

{{Repositories}}The server repository allows users with the correct permissions to see files on the server. This might mean only files and folders in the context of the current course, or access to a file system that will allow them to use other courses files.

To access any repository, click on it.

[[File:File_Picker_blank_course.png|thumb|300px|center|A new course, with arrow point to Server files repository]]

Below is an example of drilling down. The breadcrumb path has built in links to the level it represents. In the example below, click on "English" and you will see folders representing all the courses in the English category at demo.moodle.org .
[[Image:File_Picker_demo_moodle_legacy_files.png|center|Server files after drilling down in demo.moodle.org]]

==Repository permissions==

This repository is accessible by default to administrators, course creators, teachers, editing teachers and managers, but not to guests or students. This [[Capabilities/repository/local:view|capability]] can be changed to control access to users with specific roles.

File system repository

2012-01-10T01:41:49Z

Deraadt: Adding repository capability default information

{{Repositories}}
The file system repository allows users within Moodle to access files which have been uploaded via FTP into designated folders on the server. A file system repository may be available site wide for everyone; within an individual course or for an individual user.(However - see this [http://tracker.moodle.org/browse/MDL-28656 tracker entry] regarding course and individual repositories)

This must be done by a systems admin who has write permissions to the server directories.

=== Creating folders for your file system repositories===
*Find the moodledata folder on the server
*Inside it, create a folder called "repository"
*Inside that folder, create as many folders as you need, named appropriately.
[[File:Moodledatarepo2.png]]
*FTP into the appropriate folder the files you want. (The folders can hold all types of files)

=== Enabling the File System repository plugin===

*Go to ''Settings > Site administration > Plugins > Repositories > Manage Repositories'';
*Select from the drop down next to File sytem "Enabled and visible"
[[File:Filesystemrepo.png]]

===Setting up a site-wide file system repository===
*Once the repository is enabled as above, click on the "Settings" link to the right.
*Scroll down to Repositories instances of the site
*Click Create a repository instance
[[File:Sitefilesystemrepo.png]]
*Give it a name and (if there are several folders on the server) choose from the dropdown the one you want. Click save
[[File:Namedfilesystem.png]]
*It will now be available in the file picker in all courses.
''NOTE: Just repeat the process to get more than one site wide file system repository''

===Setting up a repository inside a course===
''NOTE: A regular user needs to have been given permission to do this by admin (MORE DETAILS SOON)''
*Go to the desired course and click on “repositories” in the administration block
*Scroll down and click "Create File System instance"
[[File:Courseinstance.png]]
*Follow the same process as [[#Setting_up_a_site-wide_file_system_repository|here]]

===Setting up an individual file system repository instance===
''NOTE: A regular user needs to have been given permission to do this by admin (MORE DETAILS SOON)
''
*In the navigation block, click on “my profile”
*Click on “repositories”
*Scroll down and click “create File System instance”
*Follow the same process as [[#Setting_up_a_site-wide_file_system_repository|here]]
*This will create a personal file system repository connecting just you to a folder on the server.
[[File:Privaterepo2.png]]

===Using it===
If you try to add a file in Moodle, then the File Picker should show you your new file system repository, and you should be able to browse it and select files to use.

Note that file types are respected (based on file extensions), so if you are adding an image in the editor, then you won't see Office docs (for example) appear in the File Picker.

[[File:Filesystemeg.png]]

==Repository permissions==

This repository is accessible by default to administrators, course creators, teachers, editing teachers and managers, but not to guests or students. This [[Capabilities/repository/filesystem:view|capability]] can be changed to control access to users with specific roles.

==See also==
*[[File_system_repository_FAQ|File system repository FAQ]]
* Overview of [[Repositories|Repositories]]
* [http://www.somerandomthoughts.com/blog/2010/06/15/ftp-files-into-moodle-2-0-with-the-repository-api/ FTP files into Moodle 2.0 with the repository API article from somerandomthoughts.com] including screencast

[[Category:Site administration]]
[[de:Dateisystem-Repository]]

Legacy course files

2012-01-10T01:38:49Z

Deraadt: Adding repository capability default information

{{Repositories}}
<p class="note">Note: This page only applies to sites which have been upgraded from Moodle 1.9.</p>
In Moodle 2.0 onwards, files are stored in separate areas, rather than together in the course files area. See [[Course files]] for a detailed explanation. When a site is upgraded from 1.9, the course files area is renamed 'Legacy course files'. By default, this area is not available in new courses.

''It is recommended that teachers make use of the new [[Repositories|repositories]] in Moodle 2.0 for storing course files, rather than saving them in the legacy course files area''.

==Enabling legacy course files areas==

To enable a legacy course files area in a new course

# Enable the legacy course files repository plugin in ''Settings > Site administration > Plugins > Repositories > [[Manage repositories]]''.
# Check the legacyfilesinnewcourses box in the Manage repositories common settings then click the 'Save changes' button.
# Set 'Legacy course files' to Yes in the course settings.

A legacy course files link will then appear in the ''Settings > Course administration'' area.

==Repository permissions==

This repository is accessible by default to administrators, course creators, teachers, editing teachers and managers, but not to guests or students. This [[Capabilities/repository/coursefiles:view|capability]] can be changed to control access to users with specific roles.

[[ja: レガシーコースファイル]]

Managing repositories

2012-01-10T01:36:51Z

Deraadt: Adding repository capability default information

{{Repositories}}
==Enabling repositories==

Repositories can be enabled by an administrator in ''Settings > Site administration > Plugins > Repositories > Manage repositories''.

A repository plugin may be set to

* Enabled and visible - appears in the file picker
* Enabled and hidden
* Disabled - default setting

The order in which repositories are shown in the file picker may be set using the up and down arrows.

==Vocabulary==
'''Repository plugin''': it is also called a repository type. It can be named Box.net, Flickr, Mahara, Youtube... Adding a plugin allow users to create instances of this plugin. Only instances are displayed into the file picker. Type only exist in order to let a Moodle administrator to deactivate/delete all instances of a type in one click.

'''Repository instance''': An instance is displayed into the file picker and it is the access point to an external repository. An instance can have specific settings (for example be linked to a personal account).

*First case: when you add the plugin, an instance is automatically created and can not be edited. The Moodle administrator cannot change the instance name. The instance name displayed into the file picker will be exactly the same as the plugin name. For example Youtube, Box.net...
*Second case: the plugin allow the Moodle administrator to add multiple instances. An instance has a name for example Flickr Public access to Martin account, Martin's Mahara... <br/>For this second case it is important to identify two different kind of instances:
#Common instances: The instances set by Moodle administrator in these same administration pages will be available into any file picker.
#Private instance: A teacher can set some instances available only for a course, and an user can set some instances only available for himself. In order to set instances for a course the teacher will go to the course page, and in order to set instances for a personal use, a user will go on his profile page. An administrator cannot add/edit private instances from the administration pages.

==Common repository settings==

Common repository settings can be set by an administrator in ''Settings > Site administration > Plugins > Repositories > Common Repository settings'':

===Cache Expire===

You can specify how long in seconds file listings are cached locally when browsing external repositories.

===Allow external links===

With some repositories such as Flickr, users can have the choice whether to copy the media into Moodle (the preferred solution) or to make a link to it instead.

===Legacy course files in new courses===

This repository is not normally available in new courses as it is designed for upgraded 1.9 courses. However, if it is checked here then it will appear when new courses are created - but certain backup and restore features won't work with it. See [[Legacy course files]] for more details.

==Repositories and capabilities==

Each repository plugin has a [[Roles and permissions|capability]] to control user access. This can be controlled for users of differing [[Roles and permissions|roles]]. Most, repositories distributed with Moodle are accessible to all roles, except the following repositories, which by default are accessible to administrators, course creators, teachers, editing teachers and managers, but not to guests or students.

* [[Capabilities/repository/coursefiles:view|Legacy course files]]
* [[Capabilities/repository/filesystem:view|File system]]
* [[Capabilities/repository/local:view|Server files]]
* [[Capabilities/repository/webdav:view|WebDAV repository]]

Database presets

2011-11-04T09:02:45Z

Deraadt: Adding to a top level category

{{Database}}
{{Update}}
To avoid the necessity of always having to create a new database from scratch, the database activity module has a presets feature. An image gallery preset is currently included in the database module to help get you started. You can create your own presets as well and share them with others.

==Importing a preset==

[[Image:Database preset.png|thumb|Database presets page]]
To use a preset:

# On the database page, click the Presets tab.
# The usual way to import a preset is clicking the "Choose file" button and browsing to the ZIP file containing the preset (eg. "preset.zip") stored on the server. If there does not yet exist a preset ZIP file on the server, upload it from your local machine. Choose the desired preset file by clicking on its action "Choose". Finally, press the "Import" button.
# Alternatively, you can choose a previously loaded preset.
# After the import, you can start to add or import entries. All the hard work of setting up the fields and templates has been done for you. If you desire, you can still customize the fields and templates.

You will see a "Overwrite current settings" checkbox after the "Import" button has been pressed. If checked, the database activity overwrites some of its current general settings by those stored in the preset:
* the "Introduction" HTML text
* "Required entries"
* "Entries required before viewing"
* "Maximum entries"
* "Comments"
* "Require approval?"
* rssarticles

==Exporting a preset==

If you wish to share your database presets with others, you have two options:

#Export as a ZIP file, which can then be imported to another course or Moodle site.
#Save as a preset, which publishes the database for other teachers on your site to use. It will then appear in the preset list. (You can delete it from the list at any time.)

Note: Only the fields and templates of the database are copied when exporting or saving it as a preset, not the entries.

==See also==
* [http://moodle.org/mod/data/view.php?id=7303 Database for Databases]
Using Moodle forum discussions:
*[http://moodle.org/mod/forum/discuss.php?d=84050 Can't get columns to line up in list view] including moodle.org presets for download
*[http://moodle.org/mod/forum/discuss.php?d=87005 New preset, please review, and make suggestions!] including FAQ preset for download
*[http://moodle.org/mod/forum/discuss.php?d=87560 Issue 53: Encyclopedia database preset] including encyclopedia-style preset for download
*[http://moodle.org/mod/forum/discuss.php?d=88727 Issue 51 - Design a Database Preset for Document Sharing] including preset for download
*[http://moodle.org/mod/forum/discuss.php?d=94854#p457252 Looking for some stellar examples of Moodle courses] including book reviews preset for download
*[http://moodle.org/mod/forum/discuss.php?d=89117#p511029 Restricting access to database content by user?] with research diary preset for download

[[de:Vorlagensätze]]
[[fr:Préréglages]]
[[ja:プリセット]]

[[Category:Plugins]]

MediaWiki:Copyrightwarning

2011-09-29T07:18:48Z

Deraadt:

Please note that all contributions to Moodle Docs are considered to be released under the [[:dev:License|GNU General Public License]]. If you don't want your writing to be edited and redistributed at will, then don't submit it here.<br />
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
<strong>DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION!</strong>

Wiki development

2011-09-21T08:12:53Z

Deraadt:

Development FAQ

2011-09-21T06:47:50Z

Deraadt: Shifted to dev docs

Testing credits

2011-09-15T08:42:03Z

Deraadt: Shifted to dev docs

Quality assurance

2011-09-15T08:41:53Z

Deraadt: Shifted to dev docs

GSOC/2011

2011-09-15T03:24:54Z

Deraadt: Shifted to dev docs

GSOC expectations

2011-09-15T02:17:47Z

Deraadt: Shifted to dev docs

GSOC Useful Links

2011-09-15T02:16:22Z

Deraadt: Replaced content with "{{Moved_to_dev_docs}}"

GSOC

2011-09-15T02:01:28Z

Deraadt: Shifted to dev docs

Applying to work with Moodle for GSOC

2011-09-14T08:49:26Z

Deraadt: Shifted to dev docs

Question tests

2011-09-14T08:44:39Z

Deraadt: Shifted to dev docs

Portfolio tests

2011-09-14T08:37:00Z

Deraadt: Shifted to dev docs

Messaging tests

2011-09-14T08:34:48Z

Deraadt: Shifted to dev docs

Course administration tests

2011-09-14T08:27:54Z

Deraadt: Shifted to dev docs

Community hub tests

2011-09-14T08:24:32Z

Deraadt: Shifted to dev docs

Activity module tests

2011-09-14T08:23:14Z

Deraadt: Shifted to dev docs

GSOC/2011

2011-09-02T08:24:18Z

Deraadt: /* Moodle flavours */

[[Image:gsoc2011 logo.png|right]]This evolving page provides an overview of the Google Summer of Code 2011 projects for Moodle.

==Improving SCORM reporting==

:'''Student''': [http://moodle.org/user/view.php?id=1310725&course=5 Ankit Kumar Agarwal]
:'''Mentor''': [http://moodle.org/user/view.php?id=21591&course=5 Dan Marsden]
:'''Specification''': [[Development:SCORM reporting improvements]]

See also:
* MDL-27256
* Developer blog [http://ankitkumaragarwal.com/ Ankit Kumar Agarwal]

==Moodle flavours==

:'''Student''': [http://moodle.org/user/view.php?id=122326&course=5 David Monllaó]
:'''Mentor''': [http://moodle.org/user/view.php?id=381842&course=5 Michael de Raadt]
:'''Specification''': [[Development:Moodle flavours]]
:'''Download''': [http://moodle.org/mod/data/view.php?d=13&rid=5036 Flavours on M&P]

See also:
* Developer blog [http://moodle.org/blog/index.php?userid=122326 David's moodle.org blog]
* Mentor blog [http://salvetore.wordpress.com/2011/09/02/moodle-has-flavours/ Michael's entry about Flavours]

==SCORM Test Harness==

:'''Student''': [http://moodle.org/user/view.php?id=1277285&course=5 Mayank Gupta]
:'''Mentor''': [http://moodle.org/user/view.php?id=21591&course=5 Dan Marsden]
:'''Specification''': [[Development:SCORM Test Harness]]

See also:
* MDL-26912
* Developer blog [http://mayankgupta.beakkon.com/ # Mayank Gupta]

[[Category:GSOC]]

QA testing

2011-07-28T02:51:53Z

Deraadt: Shifted to dev docs

Obsolete:How Moodle outputs HTML

2011-07-27T08:48:09Z

Deraadt: Shifted to dev docs

#REDIRECT [[:dev:How Moodle outputs HTML]]

Creating a custom theme

2011-07-05T08:10:24Z

Deraadt: Shifted to dev docs

Template:Themes

2011-07-05T08:09:44Z

Deraadt: Dividing theme info between user and dev docs

<div class="sideblock right" style="width: 16em;">
<div class="header">[[Themes]]</div>
<div class="content">
* [[Theme settings]]
* [[Standard themes]]
* [[:dev:Themes_2.0|Creating a custom theme]]
* [[:dev:Theme_development|Theme development]]

{{Customising appearance}}
</div>
</div>

<includeonly>[[Category:Themes]]</includeonly>
<noinclude>This template will categorize articles that include it into [[:Category:Themes]].</noinclude>

Themes

2011-07-05T07:59:06Z

Deraadt:

{{Themes}}

A Moodle theme is a pre-designed user "view" (interface) that can be changed by the site administrator, teacher, or student. While robust, it does not affect how Moodle functions, just how it looks. Moodle comes with a standard set of themes and there is a [http://moodle.org/mod/data/view.php?id=6552 large free library] available to download.

==Moodle themes==

Themes may be [[Theme settings|selected]] at site level, course level and/or user level as long as the Moodle site has been configured to allow changes at these levels.

== Installing a theme ==

To install a theme:
# Unzip the .zip file to an empty local directory.
# Upload folder to your web server to the /moodle/theme/[Theme Name]. (Replace [Theme Name] with the name of the theme you have downloaded.) Ensure the new theme folder and its contents are readable by the webserver. Change Read and Write permissions (CHMOD) for the files and folder to 755 - Owner read/write/execute, Group read/execute, Everyone read/execute. Incorrect permissions may prevent display of the newly installed theme.
# Choose your new theme from within Moodle via ''Administration > Appearance > Themes > Theme selector'' (version 1.7+) or ''Administration > Configuration > Themes'' (older versions).

See [[Installing a new theme]] for more information.

==Themes in standard install==

Themes included in Moodle 1.9 are [[Chameleon theme|chameleon]], cornflower, [[Custom corners theme|custom corners]], formal white, metal, oceanblue, orangewhite, orangewhitepda, standard (default), standardblue, standardgreen, standardlogo, standardred, standardwhite, wood. See [[Standard themes]] for screen shots of each.

==See also==

* [http://www.youtube.com/watch?v=pPUB_ReBPeg Installing 3rd Party Modules and Themes in Moodle video]
* [[Themes FAQ]]
* [[:dev:Theme_development|Theme development]]

[[es:Temas]]
[[eu:Itxurak]]
[[de:Designs]]
[[fr:Thèmes]]
[[ja:テーマ]]
[[pt:Temas]]

Release Notes

2011-07-01T05:52:23Z

Deraadt: Redirected page to dev:Latest release notes

#REDIRECT [[:dev:Latest release notes]]

Web Services API

2011-06-23T02:22:08Z

Deraadt: Shifted to dev docs

CSS FAQ

2011-06-23T02:05:10Z

Deraadt: Replaced content with "{{Moved_to_dev_docs}}"

Theme scrapbook

2011-06-23T01:40:45Z

Deraadt: Replaced content with "{{Moved_to_dev_docs}}"

Alternate icon set

2011-06-23T01:37:11Z

Deraadt: Replaced content with "{{Moved_to_dev_docs}}"

Theme directory

2011-06-23T01:33:30Z

Deraadt: Fixing links to dev pages

{{Themes}}
In the standard Moodle distribution, all themes are placed in the theme/ directory.

From version 1.7, moodle will support changing the location which themes are stored in and used with the theme selector.

More information about the content of a typical theme directory/folder can be found in [[:dev:Theme_basics#What_is_inside_a_theme_folder.3F|Theme basics]]

== Change themes default directory for site ==
{{Moodle 1.7}}
Starting from Moodle 1.7, the storage location of themes may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.

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

== Theme directory for Developers ==

Developers should follow the [[:dev:Theme directory guide|Theme directory guide]]

== See Also ==

*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=20152 Feature request: Themes path in a VAR]
*Moodle Tracker [http://tracker.moodle.org/browse/MDL-6784 MDL-6784]

[[Category:Administrator]]
[[Category:Themes]]

[[fr:Dossier de thèmes]]
[[ja:テーマディレクトリ]]
[[de:Design-Verzeichnis]]

Theme directory

2011-06-23T01:33:05Z

Deraadt: Fixing links to dev pages

{{Themes}}
In the standard Moodle distribution, all themes are placed in the theme/ directory.

From version 1.7, moodle will support changing the location which themes are stored in and used with the theme selector.

More information about the content of a typical theme directory/folder can be found in [[:dev:Theme_basics#What_is_inside_a_theme_folder.3F|Theme basics]]

== Change themes default directory for site ==
{{Moodle 1.7}}
Starting from Moodle 1.7, the storage location of themes may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.

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

== Theme directory for Developers ==

Developers should follow the [[:dev:Theme directory guide]]

== See Also ==

*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=20152 Feature request: Themes path in a VAR]
*Moodle Tracker [http://tracker.moodle.org/browse/MDL-6784 MDL-6784]

[[Category:Administrator]]
[[Category:Themes]]

[[fr:Dossier de thèmes]]
[[ja:テーマディレクトリ]]
[[de:Design-Verzeichnis]]

Theme directory

2011-06-23T01:32:12Z

Deraadt:

{{Themes}}
In the standard Moodle distribution, all themes are placed in the theme/ directory.

From version 1.7, moodle will support changing the location which themes are stored in and used with the theme selector.

More information about the content of a typical theme directory/folder can be found in [[:dev:Theme_basics#What_is_inside_a_theme_folder.3F|Theme basics]]

== Change themes default directory for site ==
{{Moodle 1.7}}
Starting from Moodle 1.7, the storage location of themes may be altered, using the variables ''$CFG->themewww'' and ''$CFG->themedir''. Themes from placed in the directory specified by these variables will then be available for selection using the theme selector.

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

== Theme directory for Developers ==

Developers should follow the [[Theme directory guide]]

== See Also ==

*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=20152 Feature request: Themes path in a VAR]
*Moodle Tracker [http://tracker.moodle.org/browse/MDL-6784 MDL-6784]

[[Category:Administrator]]
[[Category:Themes]]

[[fr:Dossier de thèmes]]
[[ja:テーマディレクトリ]]
[[de:Design-Verzeichnis]]

Theme config file

2011-06-23T01:29:13Z

Deraadt: Replaced content with "{{Moved_to_dev_docs}}"

Theme reference

2011-06-23T01:24:18Z

Deraadt: Replaced content with "{{Moved_to_dev_docs}}"