Translations by Mitsuhiro Yoshida

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Sync groups automatically via cron job</h3> <p>Enable this setting to activate a task in the cron which will automatically create and/or update groups and their membership based on records in the LDAP server. By default, this cron task will execute once daily at midnight (server time). Edit the record in the "auth_cron" table or use the optional command-line scripts supplied in htdocs/auth/ldap/cli/ if you wish to schedule it to run at other times or with other settings.</p> <p><b>Note:</b> You'll also need to activate the "Sync groups stored as LDAP objects" and/or "Sync groups stored as user attributes" settings in order for groups to be synced.</p> <p>Group members can be removed as well as added by this setting. If a group is no longer found in the LDAP records, all of its members will be removed from the group.</p> <p>This setting will have no effect if the cron is not running. See the <a href="http://wiki.mahara.org/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for instructions on how to set it up.</p>

This gives you an export in the <a href="http://wiki.leapspecs.org/2A/specification">Leap2A standard format</a>. You can later use this to import your data into <a href="https://wiki.mahara.org/index.php/Developer_Area/Import//Export/Interoperability">other Leap2A-compliant systems</a>, although the export is hard for humans to read.

Please consider creating a backup of this page by <a href="%sexport/" target="_blank">exporting</a> it.

<p>You can choose to register your Mahara site with <a href="http://mahara.org/">mahara.org</a> and help us to build up a picture of the Mahara installations around the world. Registering will remove this notice.</p> <p>You can register your site and preview the information that will be sent on the <strong><a href="%sadmin/registersite.php">site registration page.</a></strong></p>

This gives you an export in the <a href="http://wiki.leapspecs.org/2A/specification">Leap2A standard format</a>. You can later use this to import your data into <a href="https://wiki.mahara.org/index.php/Developer_Area/Import//Export/Interoperability">other Leap2A-compliant systems</a>, although the export is hard for humans to read.

<h1>About</h1> <p><i>Add text about your organisation or the installation here</i></p> <p><strong>[<i>Name of your installation here</i>]</strong> is powered by <a href="http://mahara.org">Mahara</a>. Mahara is provided freely as open source software (under the GNU General Public License). In brief, this means that you are allowed to copy, use and modify Mahara provided you agree to:</p> <ul> <li>provide the source code to others, </li> <li>not modify or remove the original license and copyrights and</li> <li>apply this same license to any derivative work.</li> </ul>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Sync groups automatically via cron job</h3> <p>Enable this setting to activate a task in the cron which will automatically create and/or update groups and their membership based on records in the LDAP server. By default, this cron task will execute once daily at midnight (server time). Edit the record in the "auth_cron" table or use the optional command-line scripts supplied in htdocs/auth/ldap/cli/ if you wish to schedule it to run at other times or with other settings.</p> <p><b>Note:</b> You'll also need to activate the "Sync groups stored as LDAP objects" and/or "Sync groups stored as user attributes" settings in order for groups to be synced.</p> <p>Group members can be removed as well as added by this setting. If a group is no longer found in the LDAP records, all of its members will be removed from the group.</p> <p>This setting will have no effect if the cron is not running. See the <a href="http://wiki.mahara.org/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for instructions on how to set it up.</p>

<p>You can choose to register your Mahara site with <a href="http://mahara.org/">mahara.org</a>. Registration is free and helps us build up a picture of the Mahara installations around the world.</p> <p>You can see the information that will be sent to mahara.org - nothing that can personally identify any of your users will be sent.</p> <p>If you tick &quot;send weekly updates&quot;, Mahara will automatically send an update to mahara.org once a week with your updated information.</p> <p>Registering will remove this notice. You will be able to change whether you send weekly updates on the <a href="%sadmin/site/options.php">site options</a> page.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Authentication plugin</h3> <p>Here you can choose how users in this institution will authenticate to the site. Institutions should have at least one method of authentication tied to them.</p> <p>The <strong>internal</strong> authentication plugin checks the site database for usernames and passwords. Users have to have an account for this to work, which can be done by allowing registration via the registration form, or using the <a href="add.php" target="_blank">Add user</a> or <a href="uploadcsv.php" target="_blank">Add users by CSV</a> pages.</p> <p>The <strong>none</strong> authentication method allows anyone in. Users can pick any username and password. This should only be used for testing!</p> <p>The other authentication methods generally authenticate against an external source, such as an LDAP server or remote application. They have their own settings, which you can configure in a pop-up window when you add them. Some methods are disabled because their required PHP extensions are missing or the outgoing connection to the external sources cannot be established. For example, the Persona authentication plugin needs the cURL PHP extension and the HTTPS connection to <em>verifier.login.persona.org</em>.</p> <p>One setting they normally share is whether accounts can be automatically created on the site when a user signs in for the first time (as opposed to accounts being created previously by the administrator, which users can then log in to).</p>

<p>You can choose to register your Mahara site with <a href="http://mahara.org/">mahara.org</a> and help us to build up a picture of the Mahara installations around the world. Registering will remove this notice.</p> <p>You can register your site and preview the information that will be sent on the <strong><a href="%sadmin/registersite.php">site registration page.</a></strong></p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Sync groups automatically via cron job</h3> <p>Enable this setting to activate a task in the cron which will automatically create and/or update groups and their membership based on records in the LDAP server. By default, this cron task will execute once daily at midnight (server time). Edit the record in the "auth_cron" table or use the optional command-line scripts supplied in htdocs/auth/ldap/cli/ if you wish to schedule it to run at other times or with other settings.</p> <p><b>Note:</b> You'll also need to activate the "Sync groups stored as LDAP objects" and/or "Sync groups stored as user attributes" settings in order for groups to be synced.</p> <p>Group members can be removed as well as added by this setting. If a group is no longer found in the LDAP records, all of its members will be removed from the group.</p> <p>This setting will have no effect if the cron is not running. See the <a href="http://wiki.mahara.org/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for instructions on how to set it up.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>BBCode</h3> <p>BBCode gives you a way to include formatting like <strong>bold</strong> or <em>italics</em> in your messages.</p> <p>For example, to make a word bold, you would write it like this: [b]hello[/b]. In your message, the word will show up as <strong>hello</strong>. The BBCode markers - the [b] and [/b] - disappear.</p> <p>The following BBCodes are available:</p> <ul> <li><strong>[b]</strong> and <strong>[/b]</strong> to make words <strong>bold</strong> - e.g. [b]ponies[/b].</li> <li><strong>[i]</strong> and <strong>[/i]</strong> to make words <em>italic</em> - e.g. [i]amazing![/i].</li> <li><strong>[img]</strong> and <strong>[/img]</strong> to insert an image - e.g. [img]http://mahara.org/favicon.ico[/img]</li> <li><strong>[url]</strong> and <strong>[/url]</strong> to insert a link - e.g. [url]http://google.co.nz[/url] or [url=http://google.co.nz/]Google[/url]</li> </ul> <p>Note that links in your message will automatically be made clickable.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Leap2A files</h3> <p>This option gives you the ability to import a <a href="http://wiki.cetis.ac.uk/2009-03/Leap2A_specification#About_this_specification" target="_blank">Leap2A export file</a>, which contains data about a person's portfolio.</p> <p>You can read more on the Mahara wiki about <a href="http://wiki.mahara.org/Developer_Area/Import//Export" target="_blank">Mahara's support for Leap2A</a>.</p>

<p> Add fonts, which allow font embedding into web pages, via the CSS @font-face rule. Remember that not all authors / foundries allow this. </p> <p> When you find an appropriate free font that you are allowed to embed into a web page, you must convert it into the following formats: <br />TrueType Font, Embedded OpenType Font, Web Open Font Format Font and Scalable Vector Graphic Font. </p> <p> You can use <a href="http://www.fontsquirrel.com/fontface/generator/" target="_blank">FontSquirrel Online Generator</a> for the conversion. </p>

This gives you an export in the <a href="http://wiki.leapspecs.org/2A/specification">Leap2A standard format</a>. You can later use this to import your data into <a href="https://wiki.mahara.org/index.php/Developer_Area/Import//Export/Interoperability">other Leap2A-compliant systems</a>, although the export is hard for humans to read.

<p>You can configure your site to use human-readable URLs for user profiles, group homepages and portfolio pages. For example, <ul><li>http://mahara.example.com/user/bob</li> <li>http://mahara.example.com/group/bobs-group</li> <li>http://mahara.example.com/user/bob/bobs-portfolio-page</li> </ul> Before enabling this option, your server administrator must configure your web server so that incoming requests have their URLs rewritten.</p> <p>See <a href="https://wiki.mahara.org/index.php/System_Administrator's_Guide/Clean_URL_Configuration">Clean URL Configuration</a> on the Mahara wiki for instructions on how to do this.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Registration allowed?</h3> <p>If this setting is enabled, users will be able to register for the site using the registration form. If it is disabled, the registration form will not be available, but users may be able to create an account through an authentication plugin which has auto-creation of accounts enabled. Make sure you remove such authentication plugins from your institution if you want to fully disable auto-creation for all new accounts.</p> <p>If more than one institution has this setting enabled, the user will be able to choose which institution they wish to register for using a drop-down menu.</p> <p>If no institutions have this setting enabled, then users will not be able to register using the registration form.</p> <p>In general, if you have users set up to join this institution through a mechanism such as LDAP login or SSO from an external application, you should turn this setting off. You should also turn it off if you wish to control the creation of accounts using the <a href="add.php" target="_blank">Add user</a> or <a href="uploadcsv.php" target="_blank">Add users by CSV</a> pages.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Authentication plugin</h3> <p>Here you can choose how users in this institution will authenticate to the site. Institutions should have at least one method of authentication tied to them.</p> <p>The <strong>internal</strong> authentication plugin checks the site database for usernames and passwords. Users have to have an account for this to work, which can be done by allowing registration via the registration form, or using the <a href="add.php" target="_blank">Add user</a> or <a href="uploadcsv.php" target="_blank">Add users by CSV</a> pages.</p> <p>The <strong>none</strong> authentication method allows anyone in. Users can pick any username and password. This should only be used for testing!</p> <p>The other authentication methods generally authenticate against an external source, such as an LDAP server or remote application. They have their own settings, which you can configure in a pop-up window when you add them. Some methods are disabled because their required PHP extensions are missing or the outgoing connection to the external sources cannot be established. For example, the Persona authentication plugin needs the cURL PHP extension and the HTTPS connection to <em>verifier.login.persona.org</em>.</p> <p>One setting they normally share is whether accounts can be automatically created on the site when a user signs in for the first time (as opposed to accounts being created previously by the administrator, which users can then log in to).</p>

<p><strong>Sorry - the import of your Leap2A file failed.</strong></p><p>This could be because you did not select a valid Leap2A file to upload or because the version of your Leap2A file is not supported by this Mahara version. Alternatively, there may be a bug in Mahara causing the import to fail, even though the Leap2A file is valid.</p><p>Please go back and try again, and if the problem persists, you may want to post to the <a href="http://mahara.org/forums/">Mahara Forums</a> to ask for help. Be prepared to be asked for a copy of your file.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Registration allowed?</h3> <p>If this setting is enabled, users will be able to register for the site using the registration form. If it is disabled, the registration form will not be available, but users may be able to create an account through an authentication plugin which has auto-creation of accounts enabled. Make sure you remove such authentication plugins from your institution if you want to fully disable auto-creation for all new accounts.</p> <p>If more than one institution has this setting enabled, the user will be able to choose which institution they wish to register for using a drop-down menu.</p> <p>If no institutions have this setting enabled, then users will not be able to register using the registration form.</p> <p>In general, if you have users set up to join this institution through a mechanism such as LDAP login or SSO from an external application, you should turn this setting off. You should also turn it off if you wish to control the creation of accounts using the <a href="add.php" target="_blank">Add user</a> or <a href="uploadcsv.php" target="_blank">Add users by CSV</a> pages.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>BBCode</h3> <p>BBCode gives you a way to include formatting like <strong>bold</strong> or <em>italics</em> in your messages.</p> <p>For example, to make a word bold, you would write it like this: [b]hello[/b]. In your message, the word will show up as <strong>hello</strong>. The BBCode markers - the [b] and [/b] - disappear.</p> <p>The following BBCodes are available:</p> <ul> <li><strong>[b]</strong> and <strong>[/b]</strong> to make words <strong>bold</strong> - e.g. [b]ponies[/b].</li> <li><strong>[i]</strong> and <strong>[/i]</strong> to make words <em>italic</em> - e.g. [i]amazing![/i].</li> <li><strong>[img]</strong> and <strong>[/img]</strong> to insert an image - e.g. [img]http://mahara.org/favicon.ico[/img]</li> <li><strong>[url]</strong> and <strong>[/url]</strong> to insert a link - e.g. [url]http://google.co.nz[/url] or [url=http://google.co.nz/]Google[/url]</li> </ul> <p>Note that links in your message will automatically be made clickable.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Registration allowed?</h3> <p>If this setting is enabled, users will be able to register for the site using the registration form. If it is disabled, the registration form will not be available, but users may be able to create an account through an authentication plugin which has auto-creation of accounts enabled. Make sure you remove such authentication plugins from your institution if you want to fully disable auto-creation for all new accounts.</p> <p>If more than one institution has this setting enabled, the user will be able to choose which institution they wish to register for using a drop-down menu.</p> <p>If no institutions have this setting enabled, then users will not be able to register using the registration form.</p> <p>In general, if you have users set up to join this institution through a mechanism such as LDAP login or SSO from an external application, you should turn this setting off. You should also turn it off if you wish to control the creation of accounts using the <a href="add.php" target="_blank">Add user</a> or <a href="uploadcsv.php" target="_blank">Add users by CSV</a> pages.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Sync groups automatically via cron job</h3> <p>Enable this setting to activate a task in the cron which will automatically create and/or update groups and their membership based on records in the LDAP server. By default, this cron task will execute once daily at midnight (server time). Edit the record in the "auth_cron" table or use the optional command-line scripts supplied in htdocs/auth/ldap/cli/ if you wish to schedule it to run at other times or with other settings.</p> <p><b>Note:</b> You'll also need to activate the "Sync groups stored as LDAP objects" and/or "Sync groups stored as user attributes" settings in order for groups to be synced.</p> <p>Group members can be removed as well as added by this setting. If a group is no longer found in the LDAP records, all of its members will be removed from the group.</p> <p>This setting will have no effect if the cron is not running. See the <a href="http://wiki.mahara.org/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for instructions on how to set it up.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Sync users automatically via cron job</h3> <p>Enable this setting to activate a task in the cron which will automatically create and/or update user accounts based on records in the LDAP server. By default, this cron task will execute once daily at midnight (server time). Edit the record in the "auth_cron" table or use the optional command-line script supplied at htdocs/auth/ldap/cli/sync_users.php if you wish to schedule it to run at other times or with other settings.</p> <p>This setting will have no effect if the cron is not running. See the <a href="http://wiki.mahara.org/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for instructions on how to set it up.</p>

<p><strong>Sorry - the import of your Leap2A file failed.</strong></p><p>This could be because you did not select a valid Leap2A file to upload or because the version of your Leap2A file is not supported by this Mahara version. Alternatively, there may be a bug in Mahara causing the import to fail, even though the Leap2A file is valid.</p><p>Please go back and try again, and if the problem persists, you may want to post to the <a href="http://mahara.org/forums/">Mahara Forums</a> to ask for help. Be prepared to be asked for a copy of your file.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Leap2A files</h3> <p>This option gives you the ability to import a <a href="http://wiki.cetis.ac.uk/2009-03/Leap2A_specification#About_this_specification" target="_blank">Leap2A export file</a>, which contains data about a person's portfolio.</p> <p>You can read more on the Mahara wiki about <a href="http://wiki.mahara.org/Developer_Area/Import//Export" target="_blank">Mahara's support for Leap2A</a>.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Authentication plugin</h3> <p>Here you can choose how users in this institution will authenticate to the site. Institutions should have at least one method of authentication tied to them.</p> <p>The <strong>internal</strong> authentication plugin checks the site database for usernames and passwords. Users have to have an account for this to work, which can be done by allowing registration via the registration form, or using the <a href="add.php" target="_blank">Add user</a> or <a href="uploadcsv.php" target="_blank">Add users by CSV</a> pages.</p> <p>The <strong>none</strong> authentication method allows anyone in. Users can pick any username and password. This should only be used for testing!</p> <p>The other authentication methods generally authenticate against an external source, such as an LDAP server or remote application. They have their own settings, which you can configure in a pop-up window when you add them. Some methods are disabled because their required PHP extensions are missing or the outgoing connection to the external sources cannot be established. For example, the Persona authentication plugin needs the cURL PHP extension and the HTTPS connection to <em>verifier.login.persona.org</em>.</p> <p>One setting they normally share is whether accounts can be automatically created on the site when a user signs in for the first time (as opposed to accounts being created previously by the administrator, which users can then log in to).</p>

Mahara requires permission to create database triggers, but is unable to do so. Please ensure that the trigger privilege has been granted to the appropriate user in your MySQL installation. For instructions on how to do this, see https://wiki.mahara.org/index.php/System_Administrator's_Guide/Granting_Trigger_Privilege

The PL/pgSQL language is not enabled in your Postgres installation, and Mahara cannot enable it. Please install PL/pgSQL in your database manually. For instructions on how to do this, see https://wiki.mahara.org/index.php/System_Administrator's_Guide/Enabling_Plpgsql

<p>You can configure your site to use human-readable URLs for user profiles, group homepages and portfolio pages. For example, <ul><li>http://mahara.example.com/user/bob</li> <li>http://mahara.example.com/group/bobs-group</li> <li>http://mahara.example.com/user/bob/bobs-portfolio-page</li> </ul> Before enabling this option, your server administrator must configure your web server so that incoming requests have their URLs rewritten.</p> <p>See <a href="https://wiki.mahara.org/index.php/System_Administrator's_Guide/Clean_URL_Configuration">Clean URL Configuration</a> on the Mahara wiki for instructions on how to do this.</p>

A user account with an email address of '%s' was not found in any of the institutions where Persona is enabled.

The Persona authentication plugin is not enabled in any active institution.

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>We auto-create users</h3> <p>Users that successfully authenticate but are not users of this system yet will have an account created automatically.</p> <p>Their username will be their email address.</p>

To show photo albums from Photobucket, you'll need a valid API key and API private key.<br>Go to the <a href="http://developer.photobucket.com/" target="_blank">Photobucket developer website</a>, agree to the terms of service, sign up, and get the API keys.

To show photo sets from Flickr, you'll need a valid Flickr API key. <a href="https://www.flickr.com/services/api/keys/apply/" target="_blank">Apply for your key online</a>.

Please consider creating a backup of this page by <a href="%sexport/" target="_blank">exporting</a> it.

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Authentication plugin</h3> <p>Here you can choose how users in this institution will authenticate to the site. Institutions should have at least one method of authentication tied to them.</p> <p>The <strong>internal</strong> authentication plugin checks the site database for usernames and passwords. Users have to have an account for this to work, which can be done by allowing registration via the registration form, or using the <a href="add.php" target="_blank">Add user</a> or <a href="uploadcsv.php" target="_blank">Add users by CSV</a> pages.</p> <p>The <strong>none</strong> authentication method allows anyone in. Users can pick any username and password. This should only be used for testing!</p> <p>The other authentication methods generally authenticate against an external source, such as an LDAP server or remote application. They have their own settings, which you can configure in a pop-up window when you add them. Some methods are disabled because their required PHP extensions are missing or the outgoing connection to the external sources cannot be established. For example, the Persona authentication plugin needs the cURL PHP extension and the HTTPS connection to <em>verifier.login.persona.org</em>.</p> <p>One setting they normally share is whether accounts can be automatically created on the site when a user signs in for the first time (as opposed to accounts being created previously by the administrator, which users can then log in to).</p>

This gives you an export in the <a href="http://wiki.leapspecs.org/2A/specification">Leap2A standard format</a>. You can later use this to import your data into <a href="https://wiki.mahara.org/index.php/Developer_Area/Import//Export/Interoperability">other Leap2A-compliant systems</a>, although the export is hard for humans to read.

Copyright &copy; 2006 onwards, <a href="http://wiki.mahara.org/Contributors">Catalyst IT and others</a>

This gives you an export in the <a href="http://wiki.leapspecs.org/2A/specification">Leap2A standard format</a>. You can later use this to import your data into <a href="https://wiki.mahara.org/index.php/Developer_Area/Import//Export/Interoperability">other Leap2A-compliant systems</a>, although the export is hard for humans to read.

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Leap2A files</h3> <p>This option gives you the ability to import a <a href="http://wiki.cetis.ac.uk/2009-03/Leap2A_specification#About_this_specification" target="_blank">Leap2A export file</a>, which contains data about a person's portfolio.</p> <p>You can read more on the Mahara wiki about <a href="http://wiki.mahara.org/Developer_Area/Import//Export" target="_blank">Mahara's support for Leap2A</a>.</p>

<p>You can configure your site to use human-readable URLs for user profiles, group homepages and portfolio pages. For example, <ul><li>http://mahara.example.com/user/bob</li> <li>http://mahara.example.com/group/bobs-group</li> <li>http://mahara.example.com/user/bob/bobs-portfolio-page</li> </ul> Before enabling this option, your server administrator must configure your web server so that incoming requests have their URLs rewritten.</p> <p>See <a href="https://wiki.mahara.org/index.php/System_Administrator's_Guide/Clean_URL_Configuration">Clean URL Configuration</a> on the Mahara wiki for instructions on how to do this.</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>Authentication plugin</h3> <p>Here you can choose how users in this institution will authenticate to the site. Institutions should have at least one method of authentication tied to them.</p> <p>The <strong>internal</strong> authentication plugin checks the site database for usernames and passwords. Users have to have an account for this to work, which can be done by allowing registration via the registration form, or using the <a href="add.php" target="_blank">Add user</a> or <a href="uploadcsv.php" target="_blank">Add users by CSV</a> pages.</p> <p>The <strong>none</strong> authentication method allows anyone in. Users can pick any username and password. This should only be used for testing!</p> <p>The other authentication methods generally authenticate against an external source, such as an LDAP server or remote application. They have their own settings, which you can configure in a pop-up window when you add them. Some methods are disabled because their required PHP extensions are missing or the outgoing connection to the external sources cannot be established. For example, the Persona authentication plugin needs the cURL PHP extension and the HTTPS connection to <em>verifier.login.persona.org</em>.</p> <p>One setting they normally share is whether accounts can be automatically created on the site when a user signs in for the first time (as opposed to accounts being created previously by the administrator, which users can then log in to).</p>

<!-- @license http://www.gnu.org/copyleft/gpl.html GNU GPL version 3 or later --> <!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. --> <h3>We auto-create users</h3> <p>Users that successfully authenticate but are not users of this system yet will have an account created automatically.</p> <p>Their username will be their email address.</p>

To show photo albums from Photobucket, you'll need a valid API key and API private key.<br>Go to the <a href="http://developer.photobucket.com/" target="_blank">Photobucket developer website</a>, agree to the terms of service, sign up, and get the API keys.

To show photo sets from Flickr, you'll need a valid Flickr API key. <a href="https://www.flickr.com/services/api/keys/apply/" target="_blank">Apply for your key online</a>.