https://docs.moodle.org/36/en/api.php?action=feedcontributions&user=Rwijaya&feedformat=atomMoodleDocs - User contributions [en]2024-03-28T08:52:55ZUser contributionsMediaWiki 1.39.6https://docs.moodle.org/36/en/index.php?title=Multimedia_plugins_filter&diff=79289Multimedia plugins filter2010-12-16T03:10:47Z<p>Rwijaya: /* Supported media formats */</p>
<hr />
<div>Location: Multimedia Plugins settings link in ''Site administration > Modules > Filters > Manage filters''<br />
<br />
<br />
The Multimedia plugins filter finds URLs that point to multimedia resources in text and replaces them with an appropriate multimedia player.<br />
<br />
<br />
== Supported media formats ==<br />
* .mp3 - MPEG Audio Stream, Layer III<br />
* .swf - Macromedia Flash Format File (Adobe, Inc.)<br />
* .mov - QuickTime Video Clip (Apple Computer, Inc.)<br />
* .wmv - Windows Media File (Microsoft)<br />
* .mpg - MPEG Animation<br />
* .avi - Audio Video Interleave File<br />
* .flv - Flash Video File (Macromedia, Inc.)<br />
* .ram - RealMedia Metafile (RealNetworks, Inc.)<br />
* .rpm - RealMedia Player Plug-in (RealNetworks)<br />
* .rm - RealMedia Streaming Media (Real Networks, Inc.)<br />
* .mp4 (in Moodle 1.9.6 onwards)<br />
* .m4v (in Moodle 1.9.6 onwards)<br />
* .ogg (in Moodle 2.0 onwards)<br />
* .ogv (in Moodle 2.0 onwards)<br />
<br />
In Moodle 1.9.6 onwards, a YouTube link filter (disabled by default) is also available.<br />
<br />
== Usage ==<br />
<br />
Insert the URL of the multimedia resource into your text (which can be the URL of a file in the course files area). When displayed a suitable player will be provided. Moodle detects the media type using the filename extension, so you should ensure that the file contents match the extension correctly.<br />
<br />
For some file types, like Flash, you can size the plugin using an extended syntax:<br />
<br />
<a href="somepath.swf?d=640x480">My link name</a><br />
<br />
where the first number is the width in pixels, and the second is the height.<br />
<br />
== Required Software ==<br />
<br />
Although Moodle prepares the media files to be played in the browser, the actual playback is handled by various types of browser plug-in software, primarily Adobe Flash, Quicktime, Windows Media Player and Real Player. If users do not have these installed they may be prompted to go and install them by their browser. These pieces of software are generally free, easily installed and widely used so this will only be an issue for small numbers of users.<br />
<br />
== Settings page ==<br />
The settings page is in the administration block. Prior to version 1.7, this can be reached from ''Configuration > Filters > MultiMedia Plugins''. In 1.7 it can be found via ''Administration > Modules > Filters > MultiMedia Plugins''. In 1.8 it can be found via:<br />
''Notifications > Modules > Filters > MultiMedia Plugins > Settings''.<br />
<br />
There is an individual setting to turn on or off each supported media type. Note that by default all but the Flash (.swf) filter are enabled. As Flash files present a theoretical security risk, it is strongly recommended not to allow users to add flash content.<br />
<br />
== YouTube Link Filter ==<br />
<br />
The youtube filter uses a custom delimiting tag inserted anywhere within the text of a resource to embed and display an embedded youtube player<br />
without having to paste the embed code into the HTML of the page. It is also designed to ignore youtube links placed in standard <a href> tags.<br />
<br />
* Enable the filter from the administration menu in Moodle: Modules -> Filters -> Manage filters.<br />
* To embed the youtube video, enclose the video URL in [youtube] tags. Note that there is no closing tab ([/youtube]) - simply us e the regular tag again.<br />
* Videos that cannot be embedded will display with an error message and a standard html link to the video on youtube.<br />
* Youtube links placed inside of <a href> tags are designed to display normally as HTML.<br />
* The filter does its best to strip out additional php GET parameters. Example: anything after the video ID root in the URL, starting with the first '&': http://www.youtube.com/watch?v=ahuduPpZJQA(-->)&feature=featured)<br />
* Multiple links can be placed within a page.<br />
<br />
Examples:<br />
* RIGHT:<br />
**This is some text of a page.[youtube]http://www.youtube.com/watch?v=zs2XiyLYJOo[youtube] This is some more text in a page.<br />
** This is some text that has a non-embedable video. [youtube]http://www.youtube.com/watch?v=ahuduPpZJQA&feature=featured[youtube]<br />
** This is some text of a page.<a href='http://www.youtube.com/watch?v=zs2XiyLYJOo'>This video will show up as a standard html link.</a> This is some more text in a page.<br />
<br />
* WRONG:<br />
** This is some text of a page.[youtube]http://www.youtube.com/watch?v=zs2XiyLYJOo[/youtube] This is some more text in a page.<br />
** This is some text of a page. http://www.youtube.com/watch?v=zs2XiyLYJOo This is some more text in a page.<br />
<br />
* Advanced Quirk:<br />
** A youtube url that is place in a resource that is the only text on the page will display, but will not if any other text or HTML on the page exists.<br />
<br />
<br />
<br />
== See also ==<br />
<br />
* [[Filters]]<br />
* [[MP3 player]]<br />
* [[Audio in Moodle]]<br />
* [[Speech tools]]<br />
<br />
Using Moodle forum discussions:<br />
* [http://moodle.org/mod/forum/discuss.php?d=37119 Multimedia plugin vs object embed]<br />
* [http://moodle.org/mod/forum/discuss.php?d=29588 Size of embedded Flash]<br />
* [http://moodle.org/mod/forum/discuss.php?d=89416&parent=394828 Linking to FLV video files]<br />
* [http://moodle.org/mod/forum<br />
<br />
<br />
/discuss.php?d=90781 video streaming]<br />
* [http://moodle.org/mod/forum/discuss.php?d=95174 Media filter does not work for rm files]<br />
* [http://moodle.org/mod/forum/discuss.php?d=98698 swf filter security]<br />
* [http://moodle.org/mod/forum/discuss.php?d=125619 How to upload a screen capture video to the Moodle?]<br />
* [http://moodle.org/mod/forum/discuss.php?d=143478 Best video format]<br />
<br />
[[Category:Filter]]<br />
<br />
[[pl:Pluginy_Multimedia]]<br />
[[ja:マルチメディアプラグイン]]<br />
[[de:Multimedia Plugins]]<br />
[[fr:Extensions multimédia]]<br />
[[es:Multimedia plugins (filtro)|Multimedia plugins]]</div>Rwijayahttps://docs.moodle.org/36/en/index.php?title=Authentication_FAQ&diff=77472Authentication FAQ2010-11-05T07:31:54Z<p>Rwijaya: </p>
<hr />
<div>==What is an authentication plugin?==<br />
<br />
An authentication plugin is a method of handling user authentication i.e. enabling certain people to login to your Moodle site.<br />
<br />
==How do I enable the "Create new account" button on the login page?==<br />
<br />
To display the "Is this your first time here?" instructions and the "Create new account" button:<br />
<br />
# Make sure that the [[Email-based self-registration|email-based self-registration plugin]] (or any other plugin that can support self-registration, such as LDAP) is enabled in ''Administration > Users > Authentication > [[Manage authentication]]''.<br />
# Select the self-registration plugin in the common module settings.<br />
<br />
Warning: Enabling self registration results in the possibility of spammers creating accounts in order to use forum posts, blog entries etc. for spam. See [[Reducing spam in Moodle]] for ways of minimizing the risk.<br />
<br />
==How can I change the "Is this your first time here?" instructions?==<br />
#Access ''Site administration block> Users > Authentication > [[Manage authentication]]''.<br />
#Write the instructions in the ''auth_instructions'' text field.<br />
#Click the "Save changes" button at the bottom of the page.<br />
<br />
If your site caters to more than one language you can edit the language via ''Site administration > [[Language editing]]. Choose the languages (one at a time) and click "edit words or phrases". Choose "file to edit" : moodle.php<br />
Go to the string called "loginsteps" and put in the instruction text you want (for that language). Then repeat for the other languages you want offered.<br />
<br />
==How do I set up LDAP authentication?==<br />
<br />
See [[LDAP authentication]] for full instructions.<br />
<br />
==How is the "No login" authentication plugin used?==<br />
<br />
The [[No login]] authentication plugin can be used to suspend particular user accounts. To do so:<br />
<br />
# Access the user's profile page.<br />
# Click the edit profile tab.<br />
# Select "No login" as the authentication method. (If the setting isn't shown, click the "Show advanced" button to reveal it.)<br />
# Click the "Update profile" button at the bottom of the page.<br />
<br />
==Since upgrading, users are reporting that they can no longer login. What should be done?==<br />
<br />
If users are unable to login following an upgrade to 1.8 or 1.9, then most likely their account authentication method, such as [[Email-based self-registration]], requires enabling in ''Administration > Users > Authentication''.<br />
<br />
Note: The [[No authentication|No authentication (none)]] type should not be enabled on any production server. You can use phpmyadmin to convert all existing accounts created with 'none' to 'manual' or an admin can change the authentication type in [[Edit profile]].<br />
<br />
==What is the difference between enabling the email-based self-registration auth plugin and selecting it as the self registration method?==<br />
<br />
The [[Email-based self-registration| email-based self-registration authentication plugin]] must be enabled to allow users who previously self-registered to login.<br />
<br />
Selecting email-based self-registration as the self registration method allows potential users to self register.<br />
<br />
Warning: Enabling self registration results in the possibility of spammers creating accounts in order to use forum posts, blog entries etc. for spam. This risk can be minimized by limiting self registration to particular email domains with the allowed email domains setting in ''Administration > Users > Authentication > [[Authentication|Manage authentication]]'' (or in ''Administration > Server > [[Email settings|Email]]'' prior to Moodle 1.9). Alternatively, self registration may be enabled for a short period of time to allow users to create accounts, and then later disabled.<br />
<br />
==How can I create an authentication plugin?==<br />
<br />
See [[Development:Authentication plugins]].<br />
<br />
==How can students without email addresses have Moodle accounts?==<br />
<br />
See [[No Email]].<br />
<br />
==Where are users' details stored?==<br />
<br />
Users' details can be stored in local Moodle database or externally. <br />
<br />
If Users' details are stored in local Moodle database, it indicates as internal authentication. Storing users' details externally would be indicate as external authentication.<br />
<br />
See [[Manage authentication]] for more information.<br />
<br />
<br />
==See also==<br />
<br />
* Using Moodle [http://moodle.org/mod/forum/view.php?id=42 User authentication forum]<br />
<br />
[[Category:Authentication]]<br />
[[Category:FAQ]]<br />
<br />
[[de:Authentifizierung FAQ]]</div>Rwijayahttps://docs.moodle.org/36/en/index.php?title=Authentication&diff=77471Authentication2010-11-05T06:37:52Z<p>Rwijaya: /* External authentication */</p>
<hr />
<div>Location: ''Administration > Plugins > Authentication > Manage authentication'' in 2.0 onwards or ''Administration > Users > Authentication > Manage authentication'' in 1.9<br />
<br />
Authentication is the process which allows a user to login to a Moodle site. [[Site policies]] determines if users must login before reaching the [[Front Page]].<br />
<br />
<br />
==Setting the authentication method==<br />
[[Image:authentication plugins.png|thumb|Choosing an authentication plugin in Moodle 1.8 (only shows top of Authentication page)]]<br />
To set the authentication method:<br />
<br />
#Access ''Administration > Plugins > Authentication > Manage authentication'' in 2.0 onwards or ''Administration > Users > Authentication > Manage authentication'' in 1.9.<br />
#On the Manage authentication page, click on the closed eye icon to enable your chosen [[Authentication|authentication plugin(s)]]. In Moodle 1.8 onwards, you can choose to use more than one authentication plugin (see Multi-authentication below). Use the up/down arrow icons to arrange the plugins in order, with the plugin handling the most logins at the top of the page.<br />
#If you have chosen [[Email-based self-registration]] and wish potential users to be able to create their own accounts, select "Email-based self-registration" from the self registration drop-down menu in the common settings section. Potential users will then be presented with a "Create new account" button on the login page.<br />
#If you have courses with guest access, set the Guest login button to show.<br />
#Click the "Save changes" button.<br />
#Click on Settings opposite the authentication plugin(s) you have chosen.<br />
#Configure the required settings and click the "Save changes" button.<br />
<br />
==Authentication methods==<br />
<br />
Authentication methods (also known as authentication plugins) include:<br />
<br />
*[[Manual accounts]] - accounts created manually by an administrator<br />
*[[No login]] - suspend particular user account<br />
*[[Email-based self-registration]] - for enabling users to create their own accounts<br />
*[[CAS server (SSO)]] - account details are located on an external CAS server<br />
*[[External database authentication|External database]] - account details are located on an external database<br />
*[[FirstClass authentication|FirstClass server]] - account details are located on an external FirstClass server<br />
*[[IMAP authentication|IMAP server]] - account details are located on an external IMAP server<br />
*[[LDAP authentication|LDAP server]] - account details are located on an external LDAP server<br />
*[[MNet|Moodle Network authentication]] - how different Moodle sites can connect and authenticate users<br />
*[[NNTP authentication|NNTP server]] - account details are located on an external NNTP server<br />
*[[No authentication]] - for testing purposes only<br />
*[[PAM (Pluggable Authentication Modules)]] - account details come from the operating system Moodle is running on, via PAM (can only be used Linux/Unix).<br />
*[[POP3 server]] - account details are located on an external POP3 server<br />
*[[RADIUS authentication|RADIUS server]] - account details are located on an external RADIUS server<br />
*[[Shibboleth]] - account details are located on an external Shibboleth server<br />
*[[NTLM authentication|NTLM/Integrated Authentication]] (contributed plugin prior to Moodle 1.9; is part of the LDAP authentication plugin from 1.9 onwards).<br />
<br />
==Authentication types==<br />
<br />
===Internal authentication===<br />
This type of authentication is used when Moodle stores users' passwords and other details in local Moodle database. Authentication plugins such as manual and email are indicate as internal authentication<br />
<br />
===External authentication===<br />
Other authentication plugins (such as: LDAP or POP3) are indicate as external authentication. With this type of authentication, user's details are not required to be stored in local Moodle database and user's password field will be labeld as 'not cached'.<br />
<br />
==Multi-authentication==<br />
From Moodle 1.8 onwards, multi-authentication is supported. Each authentication plugin may be used to find a username/password match. Once found, a user is logged in and alternative plugins are not used. Therefore the plugin which handles the most logins should be moved to the top of the page in order that less load is put on authentication servers.<br />
<br />
==Common settings==<br />
<br />
===Self registration===<br />
<br />
If you wish users to be able to create their own user accounts, i.e. self-register, then select Email-based self-registration (or any other enabled plugin that can support self registration, like LDAP) from the drop-down menu. This will result in a "Is this your first time here?" instructions and a "Create new account" button being displayed on the login page.<br />
<br />
Warning: Enabling self registration results in the possibility of spammers creating accounts in order to use forum posts, blog entries etc. for spam. This risk can be minimized by limiting self registration to particular email domains with the allowed email domains setting (see below). Alternatively, self registration may be enabled for a short period of time to allow users to create accounts, and then later disabled.<br />
<br />
Note: The [[Email-based self-registration]] authentication plugin must be enabled to allow users who previously self-registered to login with that plugin. Selecting Email-based self-registration as the self registration method allows potential users to self register.<br />
<br />
===Guest login button===<br />
<br />
You can hide or show the guest login button on the login page. Hiding the guest login button disables [[Guest role|guest access]] to the Moodle site, however logged-in users can still enter any courses which allow guest access without being required to enrol.<br />
<br />
===Alternate login URL===<br />
<br />
This should be used with care, since a mistake in the URL or on the actual login page can lock you out of your site. If you do mess it up, you can remove the entry from your database (table mdl_config) using, e.g., phpmyadmin for mysql.<br />
<br />
===Forgotten password URL===<br />
<br />
{{Moodle 1.9}}In Moodle 1.9 onwards, if your lost password handling is performed entirely outside of Moodle (for example, only by a help desk), you can set the url of that service here. Anybody pressing a "lost password" link in Moodle will be redirected to this URL. Note that this will disable '''all''' of Moodle's lost password recovery options regardless of authentication method(s) in use.<br />
<br />
===Allowed and denied email domains===<br />
<br />
Authentication may be restricted to particular email domains when using [[Email-based self-registration]] so that, for example, only students with a university email can login.<br />
<br />
(Note: Prior to Moodle 1.9, the allowed and denied email domains settings can be found in ''Administration > Server > [[Email settings|Email]]''.) ('It should be:- Administration > User > Manage Authentication')<br />
<br />
===Restrict domains when changing email===<br />
<br />
In Moodle 1.9.3 onwards, you can choose to enforce email domains only when users create an account using [[Email-based self-registration]] i.e. after creating an account, users may change their email to a different domain.<br />
<br />
===ReCAPTCHA===<br />
<br />
[[Image:New account form with captcha element.png|thumb|New account form with CAPTCHA element]]<br />
A CAPTCHA is a program that can tell whether its user is a human or a computer. CAPTCHAs are used by many websites to prevent abuse from bots, or automated programs usually written to generate spam. No computer program can read distorted text as well as humans can, so bots cannot navigate sites protected by CAPTCHAs.<br />
<br />
From Moodle 1.9.1 onwards, spam protection may be added to the [[Email-based self-registration]] new account form with a CAPTCHA element - a challenge-response test used to determine whether the user is human.<br />
<br />
ReCAPTCHA keys can be obtained from http://www.google.com/recaptcha by [https://www.google.com/accounts signing up for an account] (free) then entering a domain. The public and private keys provided can then be copied and pasted into the ''recaptchapublickey'' and ''recaptchaprivatekey'' fields in the manage authentication common settings, and the changes saved.<br />
<br />
In addition to setting reCAPTCHA keys, email-based self-registration should be set as the self registration authentication plugin in the manage authentication common settings and the reCAPTCHA element should be enabled in the [[Email-based self-registration]] settings.<br />
<br />
==Profile fields data mapping and locking==<br />
Most (but not all) authentication plugins that use an external source for the user account details allow us to retrieve some user profile details (like first name, last name, email, etc.). By using the Data Mapping section on those authentication plugins configuration page we can configure what, when and how to manage all those user profile details.<br />
<br />
[[Image:Authent-data-map-fname.jpg|Data Mapping Options]]<br />
<br />
These fields are optional. You can choose to pre-fill some Moodle user fields with information from the external authentication source (if you are using one), from the fields that you specify here. If you leave these fields blank, then nothing will be transferred from the external authentication source and Moodle defaults will be used instead. In either case, the user will be able to edit all of these fields after they log in.<br />
<br />
In addition to specifying how to fill this fields, we can set how to update them (in both directions, to Moodle or from Moodle), and whether we want to lock them (so the user cannot modify their value) or not:<br />
<br />
*'''Update local''': When the user field will be updated from the external authentication source:<br />
** '''On creation''': when the user account is created during the first login<br />
** '''On every login''': every time the user logs in (or there is a user synchronization, for those authentication plugins that support it). Fields set to update locally should be locked.<br />
*'''Update external''': When the external authentication source will be updated from the user field:<br />
** '''Never''': never update the external authentication source from Moodle.<br />
** '''On update''': the external authentication source will be updated when the user profile is updated. Fields should be unlocked to allow edits. <br />
*'''Lock value''': To prevent users from altering some fields (e.g. students changing profile information to inappropriate or misleading information), the site administrator can lock profile fields. It's usually a good idea to lock profile fields if you are maintaining this data in the external authentication system.<br />
** '''Unlocked''': The field is unlocked and can be edited by the user at any time.<br />
** '''Unlocked if empty''': The field is unlocked if it is empty, but once the user fills in some information, it becomes locked and cannot be edited any more.<br />
** '''Locked''': The field is locked and cannot be edited by the user.<br />
<br />
If you are using a mixture of authentication types (such as IMAP and manual), then the fields you map and lock in the authentication options are specific to that particular authentication plugin. Each authentication plugin has its own set of mapped and locked fields.<br />
<br />
Remember to test the field locking by logging in with the proper type of account! If you test with a manual account but have set the field locking to apply to IMAP accounts, you will not be able to tell if it worked!<br />
<br />
==See also==<br />
<br />
*[[Authentication FAQ]]<br />
*Multi authentication in [[Upgrading to Moodle 1.8]]<br />
*Using Moodle [http://moodle.org/mod/forum/view.php?id=42 User authentication forum]<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=95559 Do users need e-mail addresses?] forum discussion<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97938 Admin approving self registrations?] forum discussion<br />
<br />
[[Category:Authentication]]<br />
<br />
[[eu:Erabiltzaileen_autentifikazioa]]<br />
[[fr:Authentification]]<br />
[[de:Authentifizierung]]<br />
[[ja:認証]]</div>Rwijayahttps://docs.moodle.org/36/en/index.php?title=Authentication&diff=77470Authentication2010-11-05T06:34:58Z<p>Rwijaya: </p>
<hr />
<div>Location: ''Administration > Plugins > Authentication > Manage authentication'' in 2.0 onwards or ''Administration > Users > Authentication > Manage authentication'' in 1.9<br />
<br />
Authentication is the process which allows a user to login to a Moodle site. [[Site policies]] determines if users must login before reaching the [[Front Page]].<br />
<br />
<br />
==Setting the authentication method==<br />
[[Image:authentication plugins.png|thumb|Choosing an authentication plugin in Moodle 1.8 (only shows top of Authentication page)]]<br />
To set the authentication method:<br />
<br />
#Access ''Administration > Plugins > Authentication > Manage authentication'' in 2.0 onwards or ''Administration > Users > Authentication > Manage authentication'' in 1.9.<br />
#On the Manage authentication page, click on the closed eye icon to enable your chosen [[Authentication|authentication plugin(s)]]. In Moodle 1.8 onwards, you can choose to use more than one authentication plugin (see Multi-authentication below). Use the up/down arrow icons to arrange the plugins in order, with the plugin handling the most logins at the top of the page.<br />
#If you have chosen [[Email-based self-registration]] and wish potential users to be able to create their own accounts, select "Email-based self-registration" from the self registration drop-down menu in the common settings section. Potential users will then be presented with a "Create new account" button on the login page.<br />
#If you have courses with guest access, set the Guest login button to show.<br />
#Click the "Save changes" button.<br />
#Click on Settings opposite the authentication plugin(s) you have chosen.<br />
#Configure the required settings and click the "Save changes" button.<br />
<br />
==Authentication methods==<br />
<br />
Authentication methods (also known as authentication plugins) include:<br />
<br />
*[[Manual accounts]] - accounts created manually by an administrator<br />
*[[No login]] - suspend particular user account<br />
*[[Email-based self-registration]] - for enabling users to create their own accounts<br />
*[[CAS server (SSO)]] - account details are located on an external CAS server<br />
*[[External database authentication|External database]] - account details are located on an external database<br />
*[[FirstClass authentication|FirstClass server]] - account details are located on an external FirstClass server<br />
*[[IMAP authentication|IMAP server]] - account details are located on an external IMAP server<br />
*[[LDAP authentication|LDAP server]] - account details are located on an external LDAP server<br />
*[[MNet|Moodle Network authentication]] - how different Moodle sites can connect and authenticate users<br />
*[[NNTP authentication|NNTP server]] - account details are located on an external NNTP server<br />
*[[No authentication]] - for testing purposes only<br />
*[[PAM (Pluggable Authentication Modules)]] - account details come from the operating system Moodle is running on, via PAM (can only be used Linux/Unix).<br />
*[[POP3 server]] - account details are located on an external POP3 server<br />
*[[RADIUS authentication|RADIUS server]] - account details are located on an external RADIUS server<br />
*[[Shibboleth]] - account details are located on an external Shibboleth server<br />
*[[NTLM authentication|NTLM/Integrated Authentication]] (contributed plugin prior to Moodle 1.9; is part of the LDAP authentication plugin from 1.9 onwards).<br />
<br />
==Authentication types==<br />
<br />
===Internal authentication===<br />
This type of authentication is used when Moodle stores users' passwords and other details in local Moodle database. Authentication plugins such as manual and email are indicate as internal authentication<br />
<br />
===External authentication===<br />
Other authentication plugins(such as: LDAP or POP3) are indicate as external authentication. With this type of authentication, user's details are not required to be stored in local Moodle database and user's password field will be labeld as 'not cached'.<br />
<br />
==Multi-authentication==<br />
From Moodle 1.8 onwards, multi-authentication is supported. Each authentication plugin may be used to find a username/password match. Once found, a user is logged in and alternative plugins are not used. Therefore the plugin which handles the most logins should be moved to the top of the page in order that less load is put on authentication servers.<br />
<br />
==Common settings==<br />
<br />
===Self registration===<br />
<br />
If you wish users to be able to create their own user accounts, i.e. self-register, then select Email-based self-registration (or any other enabled plugin that can support self registration, like LDAP) from the drop-down menu. This will result in a "Is this your first time here?" instructions and a "Create new account" button being displayed on the login page.<br />
<br />
Warning: Enabling self registration results in the possibility of spammers creating accounts in order to use forum posts, blog entries etc. for spam. This risk can be minimized by limiting self registration to particular email domains with the allowed email domains setting (see below). Alternatively, self registration may be enabled for a short period of time to allow users to create accounts, and then later disabled.<br />
<br />
Note: The [[Email-based self-registration]] authentication plugin must be enabled to allow users who previously self-registered to login with that plugin. Selecting Email-based self-registration as the self registration method allows potential users to self register.<br />
<br />
===Guest login button===<br />
<br />
You can hide or show the guest login button on the login page. Hiding the guest login button disables [[Guest role|guest access]] to the Moodle site, however logged-in users can still enter any courses which allow guest access without being required to enrol.<br />
<br />
===Alternate login URL===<br />
<br />
This should be used with care, since a mistake in the URL or on the actual login page can lock you out of your site. If you do mess it up, you can remove the entry from your database (table mdl_config) using, e.g., phpmyadmin for mysql.<br />
<br />
===Forgotten password URL===<br />
<br />
{{Moodle 1.9}}In Moodle 1.9 onwards, if your lost password handling is performed entirely outside of Moodle (for example, only by a help desk), you can set the url of that service here. Anybody pressing a "lost password" link in Moodle will be redirected to this URL. Note that this will disable '''all''' of Moodle's lost password recovery options regardless of authentication method(s) in use.<br />
<br />
===Allowed and denied email domains===<br />
<br />
Authentication may be restricted to particular email domains when using [[Email-based self-registration]] so that, for example, only students with a university email can login.<br />
<br />
(Note: Prior to Moodle 1.9, the allowed and denied email domains settings can be found in ''Administration > Server > [[Email settings|Email]]''.) ('It should be:- Administration > User > Manage Authentication')<br />
<br />
===Restrict domains when changing email===<br />
<br />
In Moodle 1.9.3 onwards, you can choose to enforce email domains only when users create an account using [[Email-based self-registration]] i.e. after creating an account, users may change their email to a different domain.<br />
<br />
===ReCAPTCHA===<br />
<br />
[[Image:New account form with captcha element.png|thumb|New account form with CAPTCHA element]]<br />
A CAPTCHA is a program that can tell whether its user is a human or a computer. CAPTCHAs are used by many websites to prevent abuse from bots, or automated programs usually written to generate spam. No computer program can read distorted text as well as humans can, so bots cannot navigate sites protected by CAPTCHAs.<br />
<br />
From Moodle 1.9.1 onwards, spam protection may be added to the [[Email-based self-registration]] new account form with a CAPTCHA element - a challenge-response test used to determine whether the user is human.<br />
<br />
ReCAPTCHA keys can be obtained from http://www.google.com/recaptcha by [https://www.google.com/accounts signing up for an account] (free) then entering a domain. The public and private keys provided can then be copied and pasted into the ''recaptchapublickey'' and ''recaptchaprivatekey'' fields in the manage authentication common settings, and the changes saved.<br />
<br />
In addition to setting reCAPTCHA keys, email-based self-registration should be set as the self registration authentication plugin in the manage authentication common settings and the reCAPTCHA element should be enabled in the [[Email-based self-registration]] settings.<br />
<br />
==Profile fields data mapping and locking==<br />
Most (but not all) authentication plugins that use an external source for the user account details allow us to retrieve some user profile details (like first name, last name, email, etc.). By using the Data Mapping section on those authentication plugins configuration page we can configure what, when and how to manage all those user profile details.<br />
<br />
[[Image:Authent-data-map-fname.jpg|Data Mapping Options]]<br />
<br />
These fields are optional. You can choose to pre-fill some Moodle user fields with information from the external authentication source (if you are using one), from the fields that you specify here. If you leave these fields blank, then nothing will be transferred from the external authentication source and Moodle defaults will be used instead. In either case, the user will be able to edit all of these fields after they log in.<br />
<br />
In addition to specifying how to fill this fields, we can set how to update them (in both directions, to Moodle or from Moodle), and whether we want to lock them (so the user cannot modify their value) or not:<br />
<br />
*'''Update local''': When the user field will be updated from the external authentication source:<br />
** '''On creation''': when the user account is created during the first login<br />
** '''On every login''': every time the user logs in (or there is a user synchronization, for those authentication plugins that support it). Fields set to update locally should be locked.<br />
*'''Update external''': When the external authentication source will be updated from the user field:<br />
** '''Never''': never update the external authentication source from Moodle.<br />
** '''On update''': the external authentication source will be updated when the user profile is updated. Fields should be unlocked to allow edits. <br />
*'''Lock value''': To prevent users from altering some fields (e.g. students changing profile information to inappropriate or misleading information), the site administrator can lock profile fields. It's usually a good idea to lock profile fields if you are maintaining this data in the external authentication system.<br />
** '''Unlocked''': The field is unlocked and can be edited by the user at any time.<br />
** '''Unlocked if empty''': The field is unlocked if it is empty, but once the user fills in some information, it becomes locked and cannot be edited any more.<br />
** '''Locked''': The field is locked and cannot be edited by the user.<br />
<br />
If you are using a mixture of authentication types (such as IMAP and manual), then the fields you map and lock in the authentication options are specific to that particular authentication plugin. Each authentication plugin has its own set of mapped and locked fields.<br />
<br />
Remember to test the field locking by logging in with the proper type of account! If you test with a manual account but have set the field locking to apply to IMAP accounts, you will not be able to tell if it worked!<br />
<br />
==See also==<br />
<br />
*[[Authentication FAQ]]<br />
*Multi authentication in [[Upgrading to Moodle 1.8]]<br />
*Using Moodle [http://moodle.org/mod/forum/view.php?id=42 User authentication forum]<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=95559 Do users need e-mail addresses?] forum discussion<br />
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=97938 Admin approving self registrations?] forum discussion<br />
<br />
[[Category:Authentication]]<br />
<br />
[[eu:Erabiltzaileen_autentifikazioa]]<br />
[[fr:Authentification]]<br />
[[de:Authentifizierung]]<br />
[[ja:認証]]</div>Rwijayahttps://docs.moodle.org/36/en/index.php?title=Site_policies&diff=67177Site policies2010-01-13T06:56:02Z<p>Rwijaya: /* Allow extended characters in usernames */</p>
<hr />
<div>Location: ''Administration > Security > Site policies''<br />
<br />
<br />
==Open to Google==<br />
<br />
Enabling this setting allows Google's search spiders guest access to your site. Any part of the site that allows guest access will then be searchable on Google. In addition, people coming in to your site via a Google search will automatically be logged in as a guest.<br />
<br />
==Maximum uploaded file size==<br />
<br />
Probably the most frequently asked question in the Moodle.org Using Moodle forums is "How do I increase the upload file size limit?"<br />
<br />
Upload file sizes are restricted in a number of ways - each one in this list restricts the following ones:<br />
<br />
1. The Apache server setting LimitRequestBody ... default in Apache 2.x or greater is set to 0 or an unlimited upload size<br />
<br />
2. The PHP site settings post_max_size and upload_max_filesize in php.ini : '''modify php.ini in web server directories''' ( apache2.x.x/bin/php.ini ) not in php directories :<br />
<br />
post_max_size = 128M; to increase limit to 128 Megabytes;<br />
upload_max_filesize = 128M; to increase limit to 128 Megabytes;<br />
max_execution_time = 600 ; Maximum execution time of each script, in seconds;<br />
<br />
3. The Moodle site-wide maximum uploaded file size setting: ''Administration > Security > Site policies > Maximum uploaded file size [128M]''.<br />
<br />
4. The Moodle course maximum uploaded file size setting in the course settings: ''Administration > Courses > Add/Edit courses > select Course category & edit each course > Maximum upload size [128M]''.<br />
<br />
5. Certain course activity module settings (for example, Assignment)<br />
<br />
===See Also===<br />
*[[File_upload_size | File Upload Size]]<br />
<br />
==Enable messaging system==<br />
<br />
Click the checkbox to enable site-wide [[Messaging]].<br />
<br />
:''Note'': If you enable the messaging system, all users will be able to send and receive messages at any time. Teachers can't choose whether or not messaging is allowed between students in their particular course.<br />
<br />
==Force users to login==<br />
<br />
If you turn this setting on all users must login before they even see the front page of the site.<br />
<br />
==Force users to login for profiles==<br />
<br />
Leave this set to Yes to keep anonymous visitors away from user profiles. (See the Using Moodle forum discussion [http://moodle.org/mod/forum/discuss.php?d=89061 3rd party spam exploit possible? Help please!].)<br />
<br />
==Enable trusted content==<br />
<br />
Please refer to [[Development:Trusttext cleaning bypass]] for further information.<br />
<br />
==Maximum time to edit posts==<br />
<br />
This sets the editing time for forum postings. The editing time is the amount of time users have to change forum postings before they are mailed to subscribers.<br />
<br />
Please refer to the forum discussions [http://moodle.org/mod/forum/discuss.php?d=28679 Editing a forum post after the 30 minutes deadline] and [http://moodle.org/mod/forum/discuss.php?d=5367 The philosophy underlying "no editing after 30 minutes"]<br />
<br />
==Allow extended characters in usernames==<br />
<br />
The default here, unchecked = unenabled, can only contain alphabetical letters in lowercase, numbers, hypen '-', underscore '_', period '.', or at sign '@'. If you enable this, it will be possible to have any characters for the username.<br />
<br />
==Site policy URL==<br />
<br />
If you have a site policy that all users must see and agree to before using this site, then specify the URL to it here, otherwise leave this field blank. The URL can point to anywhere, for example a file in the site files.<br />
<br />
:''Tips'' <br />
:*It is recommended that the site policy is on the same domain as Moodle to avoid the problem of Internet Explorer users seeing a blank screen when the site policy is on a different domain.<br />
:*If the front page of your site is [[Site_policies#Force_users_to_login|open to guests]] (i.e. not forcing everyone to log in before viewing the front page) then you can upload it to your site files area.<br />
:*If you do force everyone to log in then you will need to upload it via FTP to another location; i.e. the root of your web server.<br />
<br />
==Blog visibility==<br />
<br />
To enable [[Blogs]], select the level to which user blogs can be viewed.<br />
<br />
By default, all site users can see all blogs. Blog visibility may be restricted so that users can only see blogs for people whom they share a course with or whom they share a group with.<br />
<br />
:''Note'': This setting is for specifying the maximum context of the VIEWER not the poster. To limit blogging to specific users only, a [[Blogger role]] should be created and users assigned to it in the system context.<br />
<br />
==Enable tags functionality==<br />
<br />
{{Moodle 1.9}}In Moodle 1.9 onwards, users may [[Tags|tag]] themselves and create interest pages around those tags.<br />
<br />
==Keep tag name casing==<br />
<br />
If checked, then tags like the following will be displayed: SOCCER, gUiTaR, MacDonalds, music<br />
<br />
If unchecked, then all tags will be displayed as follows: Soccer, Guitar, Macdonalds, Music<br />
<br />
:''Tips'':<br />
:* For English, off is useful.<br />
:* For Japanese, no changes are made either way.<br />
:* For languages where this kind of capitalization changes the meaning, it is best to keep this option on.<br />
<br />
==Profiles for enrolled users only==<br />
<br />
In Moodle 1.7.7, 1.8.8 and in 1.9.4 onwards, to prevent misuse by spammers, profile descriptions of users who are not yet enrolled in any course are hidden. New users must enrol in at least one course before they can add a profile description.<br />
<br />
==Password policy==<br />
<br />
{{Moodle 1.9}}In Moodle 1.9 onwards, a [[Password policy|password policy]] may be set up, ensuring users choose passwords of a certain length etc. The password policy is enabled by default in Moodle 1.9.7 (upgrades and new installs) onwards.<br />
<br />
==Disable user profile images==<br />
<br />
In Moodle 1.9 onwards, the ability for users to change their profile images may be disabled by checking the ''disableuserimages'' box.<br />
<br />
==Email change confirmation==<br />
<br />
{{Moodle 1.8}}In Moodle 1.8.6 and in 1.9.2 onwards, a confirmation step is required for users to change their email address unless the ''emailchangeconfirmation'' box is unchecked.<br />
<br />
==Enable notes==<br />
<br />
{{Moodle 1.9}}In Moodle 1.9.4 onwards, [[Notes]] may be disabled.<br />
<br />
== See also ==<br />
<br />
*[[Administration FAQ]]<br />
<br />
[[Category:Administrator]]<br />
[[Category:Security]]<br />
<br />
[[eu:Gunearen_politikak]]<br />
[[fr:Règles site]]<br />
[[hu:Portál alapelvei]]<br />
[[ja:サイトポリシー]]<br />
[[de:Website-Rechte]]</div>Rwijayahttps://docs.moodle.org/36/en/index.php?title=Edit_profile&diff=67176Edit profile2010-01-13T06:54:37Z<p>Rwijaya: /* User name */</p>
<hr />
<div>{{Course admin}}<br />
[[Student]]s are usually asked to edit their profile in [[Moodle]]. It is also possible for the [[Administrator|site administrator]] to edit users' profiles. These instructions reflect the 1.9 format of the user's page for the site administrator. A student has a shorter list.<br />
<br />
==Table of Contents==<br />
__TOC__<br />
<br />
==Standard settings==<br />
===General===<br />
====User name====<br />
This may be changed. Can only only contain alphabetical letters in lowercase, numbers, hypen '-', underscore '_', period '.', or at sign '@'.<br />
<br />
====New Password====<br />
Has an unmask setting to reveal the actual password. Password is validated to ensure that password complexity requirements as enforced. See [[Site_policies#Password_policy|Password policy]] for more information.<br />
<br />
====Force password change====<br />
An initial password can be set by the administrator or bulk uploading, but this will force the user to create a new password.<br />
<br />
====First name, surname====<br />
The first two fields are quite self-explanatory. The first and last names should be those that the student is to be known by in the course. They will identify the student everywhere in the course.<br />
<br />
====Email address====<br />
The email address should be the address at which the student receives acknowledgements and messages from the system, and is also the address that is displayed to the instructor and other users of the Moodle site, assuming that they have set the "Email display" option to allow other participants in the course to see their address, so it should be a mail address that they check regularly. Other email display options are to hide your mail address from all users (it will still be visible to admins and instructors), or to make it available to everyone who visits the course, not just those that are enrolled.<br />
<br />
====Email display====<br />
This controls the visibility of the address to others, allowing you to show or hide your email in the class. There are three options: you can set it so that all users (including guests) could see your email, or so that only other enrollees in the course can see the email address, or so that no one could see your email address at all. <br />
<br />
====Email activated====<br />
One can either enable or disable emails being sent to the email address in their profile. Note that if this is disabled, the user will not receive any mail whatsoever from the site.<br />
<br />
====City/town; country====<br />
These fields are used to further identify you by geographical location.<br />
<br />
====Timezone====<br />
This field is used to convert time-related messages on the system (such as assignment deadlines) from the default Moodle timezone to the correct time in whichever zone you have selected. <br />
<br />
====Preferred language ====<br />
A Moodle site might have multiple languages installed from language packs. This sets the user's prefered language using a drop down menu.<br />
<br />
====Preferred theme====<br />
If site configurations has [[Theme_settings|allowuserthemes]] enabled, then users will be allowed to set their own preferred theme. User themes override site themes but not if the course setting is [[Course_settings#Force_Theme|Force theme]].<br />
<br />
====Description====<br />
In this field you can enter some text about yourself, be it information about your studies, hobbies, qualifications or anything else that does not break the acceptable use policy of this site. This text will be visible to anyone that views your profile.<br />
<br />
===Picture of===<br />
The user's picture (also known as an Avatar) can be changed in this section. The default, Moodle picture is automatically used when a new user is created. Moodle creates two sizes of a user's picture. The two images files are called "f1" and 'f2". The site administrator can change the default images. Here is the standard default "f1" image.<br />
[[Image:F1 user default image.jpg|center]]<br />
====Current picture====<br />
This shows the picture associated with a profile. Sometimes the refresh button on your browser will update the current image view.<br />
<br />
:''TIP:'' The site administrator can view all uploaded user pictures via the URL <moodle url>/userpix/. For example <nowiki>http://demo.moodle.org/userpix/</nowiki>.<br />
:''TIP:'' Want the default picture to be blank? Replace the picture with a file that has 1 white pixel. <br />
:''TIP:'' The site administrator can change the default picture for the site by replacing the F1 and F2 images in the theme or pic folders.<br />
<br />
====Delete====<br />
Checking this box and using the update button will delete the current picture and restore the Moodle site default user picture.<br />
<br />
====New picture====<br />
This field has a Browse button to allow the user to find and then upload a new picture for the profile. Uploaded image types supported include gif, jpg, and png. The file upload size shown is determined by the maxbytes variable on the configuration page. User pictures are 100px by 100px for the larger view and 35px by 35px for the smaller view. Both of these small images are created by Moodle in the upload process, which also reduces the file size to around 4K. The pictures are stored in each Users sub-folder of the Moodle data folder as "f1" and "f2".<br />
<br />
:''TIP:'' The picture does not change? Or the picture will not change after repeated uploads of a new photo file? The most common solution is to refresh your browser cache. It is also possible the problem has to do with the server cache. Ask your site administrator or hosting service if there is a server cache setting that is causing this problem. Often removing an unnecessary cache will solve this.<br />
<br />
====Picture Description====<br />
This text appears when the mouse rolls over the picture as a description.<br />
<br />
===Interests===<br />
====List of interests====<br />
Use a comma between different interests. This allows you to connect with others who list similar interests.<br />
<br />
==Advanced==<br />
Clicking on the Show Advanced button will reveal additonal fields.<br />
===General===<br />
====Choose an authentication method====<br />
The administrator can select a particular [[Authentication]] method for the user. This is also the place to turn on the "[[No login]]" setting.<br />
<br />
====Email format====<br />
There are two "Pretty HTML format" (which means that the messages will be formatted with different fonts and colours to make them easier to read) and "Plain text format" (plain text with no fancy formatting or colours). <br />
<br />
====Email digest type====<br />
This setting determines how one receives any posts from forums to which one is subscribed. There are three possible choices:<br />
* No digest (one receives individual emails),<br />
* Complete (a single digest daily) or<br />
* Subjects (a single digest daily with only the post topics included).<br />
<br />
[[Image:Forum_subscription_options.gif|frame|right|users may choose how they receive email from forums]]<br />
<br><br />
<br />
====Forum auto-subscribe====<br />
This setting lets one decide if one wants email copies of posts that are added to forums. If you set this to subscribe, the system will automatically email one copies of new posts in forums that one posts in, unless they manually override it when posting. <br />
<br />
====Forum tracking====<br />
Enabling forum tracking means highlighting the posts you have not read yet, which should improve your forum navigation. <br />
<br />
====When editing text====<br />
This can usually be left on "Use HTML editor (some browsers only)". This allows for text formatting options, but requires newer browsers. If you find your browser is not letting you edit text, change this setting to "Use standard web forms". <br />
<br />
====AJAX and Javascript ====<br />
No: Use basic web features.<br />
Yes: e.g., if you want to be able to drag and drop.<br />
<br />
====Screen reader====<br />
<br />
===Options===<br />
The site administrator may have [[User profile fields|added more fields]] to the user profile. The following are standard with Moodle and are revealed by the "Show Advanced" button:<br />
<br />
*Web page<br />
*ICQ number<br />
*Skype ID<br />
*AIM ID<br />
*Yahoo ID<br />
*MSN ID<br />
*ID number<br />
*Institution<br />
*Department<br />
*Phone<br />
*Mobile Phone<br />
*Address<br />
<br />
==Older version notes==<br />
*In 1.6, on the home page in the administration block select '''users''', and then '''edit user accounts'''. Find the student and click on the edit link. This brings you to their profile page, which has tabs for Edit Profile, Forum Posts, Blogs, and activity reports. <br />
<br />
==See also==<br />
*[[Student tutorials#Your profile]]<br />
*The capabilities [[Capabilities/moodle/user:editprofile|moodle/user:editprofile]], [[Capabilities/moodle/user:editownprofile|moodle/user:editownprofile]] and [[Capabilities/moodle/user:update|moodle/user:update]]<br />
<br />
[[ca:Editar Perfil]]<br />
[[es:Editar Información personal]]<br />
[[fr:Modifier mon profil]]<br />
[[ja:プロフィールの編集]]<br />
[[de:Nutzerprofil bearbeiten]]</div>Rwijayahttps://docs.moodle.org/36/en/index.php?title=Upload_users&diff=67175Upload users2010-01-13T06:53:07Z<p>Rwijaya: /* Upload file format */</p>
<hr />
<div>{{Template:Update}}<br />
<br />
Location: ''Administration > Users > Accounts > Upload users''<br />
<br />
<br />
The upload users utility is a simple but powerful way to upload user information into Moodle. It is possible to either create authenticate users, or to create authenticate users and enrol them into a course at once.<br />
<br />
*Note: that recent versions of Moodle have tools to keep the site administrators' personal maintenance work down besides this particular form of manual authentication. For example, connecting to existing external databases or letting the [[Internal enrolment|users create their own accounts]]. See the [[Authentication]] section in the admin menus.<br />
<br />
The user data text file must follow a certain format, as described below.<br />
<br />
<br />
==Upload file format==<br />
<br />
Users may be imported, enrolled on courses and organised into groups via flat file.<br />
<br />
<br />
If you are sure you want to import multiple user accounts from a text file, then you need to format your text file as follows:<br />
<br />
* Each line of the file contains one record<br />
* Each record is a series of data separated by commas<br />
* The first record of the file is special, and contains a list of fieldnames. This defines the format of the rest of the file.<br />
<br />
:'''Required fieldnames''': these fields must be included in the first record, and defined for each user<br />
:<p><code>username, password, firstname, lastname, email</code></p><br />
:<p>Remember that validity checks for the username, password, and email fields will be performed.Usernames can only contain alphabetical letters in lowercase, numbers, hypen '-', underscore '_', period '.', or at sign '@'. Passwords should meet the requirements specified for the site's [[Site_policies#Password_policy|Password policy]]. Emails should be in the format of a valid email.</p> <br />
<br />
:'''Default fieldnames''': these are optional - if they are not included then the values are taken from the primary admin<br />
:<p><code>institution, department, city, country, lang, auth, timezone</code></p><br />
<br />
:'''Optional fieldnames''': all of these are completely optional. The course names are the "shortnames" of the courses - if present then the user will be enrolled as students in those courses. Group names must be associated to the corresponding courses, i.e. group1 to course1, etc.<br />
:<p><code>idnumber, icq, phone1, phone2, address, url, description, mailformat, maildisplay, htmleditor, autosubscribe, course1, course2, course3, course4, course5, group1, group2, group3, group4, group5, type1, type2, type3, type4, type5</code></p><br />
<br />
:'''User Profile Field''': all the user profile fields or custom profiles shall use the following convention (moodle 1.9): profile_field_<your_custom_field>.<br />
<br />
'''Roles amendments''': Note that since roles have been added in Moodle 1.7, there is a new (better) fieldname to use for enrolments and that is ''role''. You can use ''role'' field instead of the legacy ''type'' field to specify roles directly - use either role short name or id (numeric names of roles are not supported).<br />
<br />
* Commas within the data should be encoded as &#44 - the script will automatically decode these back to commas.<br />
* For Boolean fields, use 0 for false and 1 for true.<br />
* Types are used to tell Moodle whether the user is a student or a teacher if a corresponding course exists (e.g. type2 corresponds to course2). 1 = Student, 2 = Editing Teacher, and 3 = Non-editing Teacher. If type is left blank, or if no course is specified, the user is default to student.<br />
* Force password change: Set the password field for desired users to '''changeme'''.<br />
* Turn email off: The parameter '''emailstop''' must be set to 1 if the email address should not work. If you set it to 0 then the email address is switched on. If you want to have all the email addresses active then you do not need the additional parameter in your upload file.<br />
* For courses, use the short name for the course<br />
* Note: If a user is already registered in the Moodle user database, this script will return the userid number (database index) for that user, and will enrol the user as a student in any of the specified courses WITHOUT updating the other specified data.<br />
<br />
Here is an example of a valid import file:<br />
<br />
<code>username, password, firstname, lastname, email, lang, idnumber, maildisplay, course1, group1, type1<br /><br />
jonest, verysecret, Tom, Jones, jonest@someplace.edu, en, 3663737, 1, Junk102, Section 1, 1<br /><br />
reznort, somesecret, Trent, Reznor, reznort@someplace.edu, en_us, 6736733, 0, Junk102, Section 3, 3</code><br />
<br />
(Text copied from [http://moodle.org/help.php?file=uploadusers.html Upload users help file].)<br />
<br />
==Updating existing accounts==<br />
<br />
By default Moodle assumes that you will be creating new user accounts, and skips records where the username matches an existing account. However, if you set "Update existing accounts" to '''Yes''', the existing user account will be updated.<br />
<br />
When updating existing accounts you can change usernames as well. Set "Allow renames" to '''Yes''' and include in your file a field called <code>oldusername</code>.<br />
<br />
'''Warning''': any errors updating existing accounts can affect your users badly. Be careful when using the options to update.<br />
<br />
==Encoding==<br />
<br />
Prior to Moodle 1.6, the file must have the same encoding as your language pack. In Moodle 1.7 and 1.8 it is always UTF-8.<br />
<br />
{{Moodle 1.9}}In Moodle 1.9 onwards, the encoding may be selected from a large list, including ISO-8859-1.<br />
<br />
==Upload users preview==<br />
<br />
[[Image:Upload users preview.png|thumb|Upload users preview in Moodle 1.9]]<br />
<br />
==Hints==<br />
<br />
===Spreadsheet===<br />
<br />
If you use a spreadsheet program such as Excel to create your .csv file, check the resulting output in a text editor before you upload it. It is possible to get trailing commas on each line from an empty field if you have added and deleted columns of information prior to saving the final file. Also check the character encoding. A csv file is a simple text file (ASCII or Unicode) that can be used to upload user accounts.<br />
<br />
Excel translates passwords that begin with - (minus) or + (plus) as zero. Even when saving as .csv and saying "Yes" to "Keep this format, and leave out any incompatible features." Check for this before uploading, as a zero halts the upload process.<br />
<br />
If you use a formula in Excel to create fields (for example, the concatenate function to create a user name), then remember to copy the cells with the formula and use special paste with values checked to make them into an acceptable data for a csv file.<br />
<br />
===Country===<br />
The country should be written as a two letter code, in capitals. For example, use BE for Belgium or NL for the Netherlands. Using "be" or "nl" as a country code will result in a database error.<br />
:''Tip:'' If you are having trouble working out the two-letter code for a country, you can consult this Moodle source code file /moodle/lang/en_utf8/countries.php [http://cvs.moodle.org/moodle/lang/en_utf8/countries.php?view=markup&pathrev=MOODLE_19_STABLE or click here for a 1.9 STABLE list].<br />
<br />
== See also ==<br />
Moodle Docs:<br />
*[[Flat file]]<br />
<br />
Using Moodle forum discussions:<br />
*[http://moodle.org/mod/forum/discuss.php?d=36851 Can I auto enroll from Excel?]<br />
*[http://moodle.org/mod/forum/discuss.php?d=58215 Making Email Optional]<br />
*[http://moodle.org/mod/forum/discuss.php?d=97903 Uploading users to custom roles]<br />
<br />
[[Category:Authentication]]<br />
[[Category:Enrolment]]<br />
[[Category:Groups]]<br />
<br />
[[fr:Importer des utilisateurs]]<br />
[[ja:ユーザのアップロード]]<br />
[[zh:上传用户]]<br />
[[ru:Загрузка пользователей]]</div>Rwijayahttps://docs.moodle.org/36/en/index.php?title=Update_profile&diff=67174Update profile2010-01-13T06:48:24Z<p>Rwijaya: /* Adding a new user */</p>
<hr />
<div>Location: ''Administration > Users > Accounts > Add a new user'' or ''Browse list of users'', or by choosing the ''Edit profile'' tab from one's own profile.<br />
<br />
==Updating Your Profile ==<br />
{{Moodle 1.8}}<br />
The fields are divided into 3 sections - General, Picture & Optional which are all explained below. Note that some settings are 'advanced', so you may need to click the 'Show Advanced' button on the right to see all the settings. The advanced settings are indicated below.<br />
<br />
Remember to click 'Update profile' when you have finished.<br />
<br />
=== General ===<br />
<br />
The first section contains fields that must be completed:<br />
<br />
'''First name & Surname'''<br />
<br />
These are self-explanatory. These names will identify you everywhere in your Moodle courses.<br />
<br />
'''Email address'''<br />
<br />
The email address should be an address that you check regularly. It is used for acknowledgements and announcements from Moodle, including messages from Forums that you are subscribed to. It is also the address that is displayed to other users of Moodle, depending on your 'Email display' setting (below).<br />
<br />
'''Email display'''<br />
<br />
This controls the visibility of your email address to others. The three settings are self-explanatory but please note 'Hide my email address from everyone' only hides it from students. Teaching staff and other staff with editing access will always be able to see your email address.<br />
<br />
'''Email activated'''<br />
<br />
You can either enable or disable emails being sent to an address. Note that if this is disabled, you will not receive any email whatsoever from the site. This is not recommend, as you may miss important course-related messages.<br />
<br />
'''Email format (advanced)'''<br />
<br />
There are two formats: "Pretty HTML format" (messages will be formatted) and "Plain text format" (plain text with no formatting).<br />
<br />
'''Email digest type (advanced)'''<br />
<br />
This setting determines how you receive any posts from Forums to which you are subscribed, allowing you to receive messages individually or on a daily basis.<br />
<br />
'''Forum auto-subscribe (advanced)'''<br />
<br />
This setting lets you decide if you want email copies of posts that are added to forums. If you set this to subscribe, the system will automatically email you copies of new posts in forums that you post in, unless you manually override it when posting.<br />
<br />
'''Forum tracking (advanced)'''<br />
<br />
Enabling forum tracking means highlighting the posts you have not read yet, which should improve your forum navigation.<br />
<br />
'''When editing text (advanced)'''<br />
<br />
This can usually be left on "Use HTML editor (some browsers only)". This allows for text formatting options, but requires newer browsers. If you find your browser is not letting you edit text, change this setting to "Use standard web forms".<br />
<br />
'''AJAX and JavaScript (advanced)'''<br />
<br />
This determines whether the Moodle interface will use advanced navigation features such as drag-and-drop, that require AJAX and JavaScript to function. These features can cause problems on some browsers so you might prefer to turn them off.<br />
<br />
'''Screen Reader (advanced)'''<br />
<br />
If you use a screen reader, this setting should be set to 'Yes'. (A screen reader is a form of 'assistive technology' used by blind and partially-sighted users to interpret what is displayed on the screen).<br />
<br />
'''City/town & Country'''<br />
<br />
Add your location.<br />
<br />
'''Timezone'''<br />
<br />
This field is used to convert time-related messages on the system (such as assignment deadlines) from the local timezone (the time in London) to the correct time in whichever zone you have selected.<br />
<br />
'''Preferred language and theme (advanced)'''<br />
<br />
You can view Moodle in several different languages and colour themes, which you can select via these two options. Note: changing the preferred language only affects the Moodle interface, not the course content!<br />
<br />
'''Description'''<br />
<br />
In this field you can enter some text about yourself, be it information about your studies, hobbies, qualifications or anything else.<br />
<br />
=== Picture ===<br />
<br />
This section is optional and allows you to choose your own profile picture. Your current picture is shown, if you have already chosen one.<br />
<br />
'''New picture'''<br />
<br />
The Browse button allows you to choose a new picture for your profile. Your picture is uploaded when you choose the 'Update Profile' at the bottom of the page.<br />
<br />
Your picture will be resized by Moodle when you upload it - to 100 pixels by 100 pixels for the larger view (e.g. in your profile) and 35 pixels by 35 pixels for the smaller view (e.g. on the Forums). If the picture you upload is not square, Moodle will automatically crop the image to make it square.<br />
<br />
=== Optional ===<br />
<br />
There are several optional fields (all advanced) allowing you to add further details to your profile such as contact details and your website.<br />
<br />
===Custom Profile Categories===<br />
If any custom user profile categories and fields have been created on your Moodle site, they will be listed at the bottom of the [[User profile fields|Admin >Accounts>User profile fields]]<br />
<br />
==Adding a new user==<br />
<br />
The add a new user page allows you to manually create a new user account. If you create a test account, you can use a made-up email address.<br />
<br />
The required field must be entered before the user will be accepted by Moodle. The required fields in a standard Moodle install are: Username, New password, Surname, Email address, City/town, Select a country.<br />
<br />
Validity checks on the required field are performed. For example, usernames can only contain alphabetical letters in lowercase, numbers, hypen '-', underscore '_', period '.', or at sign '@'. So username of joe_smith, joe.smith and joesmith123@myisp.com are permissible; however, username for JohnSmith is not permissible. The email address should be in the format of a valid email (for example, joe.smith@myisp.com). If password complexity requirements are enabled by the site administrator, the new password field is also checked to ensure it complies with those requirements. See [[admin/setting/sitepolicies#Password_policy|Password policy]] for more information.<br />
<br />
Other fields that are part of a user's profile can also be filled out when the user is created. Some of the profile fields can be revealed by pressing the "Show Advanced" button.<br />
<br />
The new user information is saved by pressing the "Update user" button near the bottom of the form.<br />
<br />
Note: You can always create new accounts manually, regardless of which [[Authentication|authentication method]] you are using.<br />
<br />
==Updating a user profile==<br />
<br />
Users with the capability [[Capabilities/moodle/user:update|moodle/user:update]] are able to update another user's profile i.e. in addition to being able to edit the profile, all settings (username, password, authentication method, force new password etc.) may be changed.<br />
<br />
==Account disabling==<br />
<br />
An account may be disabled by setting the authentication method to "[[No login]]". The account email may not be used to create another account.<br />
<br />
[[Category:Administrator]]<br />
<br />
[[fr:Modifier le profil]]<br />
[[de:Nutzerprofil aktualisieren]]</div>Rwijaya