Browsing Slovenian translation

55.

Give 1 feedback on an annotation

764.

Hello %s,

You have added the email addresses to your user account in %s:

%s

If you have not requested this change in your %s account, please contact the site administrator

%scontact.php

765.

<p>Hello %s,</p>

<p>You have added the email addresses to your user account in %s:</p>

<p>%s</p>

<p>If you have not requested this change in your %s account, please <a href="%scontact.php">contact the site administrator</a></p>

1086.

As of 30 November 2016, <a href="https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers">Mozilla is discontinuing the Persona
authentication service</a>. This plugin is a placeholder to aid in migrating existing Persona accounts from Persona to internal authentication.

1087.

This site has no Persona auth instances, so no action needs to be taken.

1091.

Automatically move all Persona users to internal auth, and delete all Persona auth instances.

1092.

<!-- @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>Auto-migrate Persona users</h3>
<p>Mozilla is <a href="https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers">discontinuing the Persona authentication service</a> as of 30 November, 2016.
If your site is using Persona, you will need to migrate those users to a different authentication method. This plugin provides a basic option to change all Persona-based user
accounts on your site, to the Mahara "internal" authentication method.</p>
<p>Selecting "Yes" and saving this form, will activate the migration script, and do the following:</p>
<ol>
<li>All Persona auth instances on the site will be deleted.</li>
<li>All users who are on Persona authentication, will be switched to the Internal auth instance for their institution.</li>
<li>If their institution has no Internal auth instance, one will be created.</li>
<li>These users will <b>not</b> have a password set. They will need to use the "Forgot password" link (and their Persona email address) to set an initial Mahara password.</li>
<li>The users' usernames will be unchanged.</li>
</ol>
<p><b>Note:</b> Users will not receive any notification that their authentication method has changed. You may wish to put a message on your site's logged-out homepage to explain
to former Persona users that they should use the "Forgot password" link, and their Persona email address, to set a new password and access their Mahara account.</p>

1223.

<!-- @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="https://wiki.mahara.org/wiki/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for
instructions on how to set it up.</p>

2291.

<span class="error">Cron is not running.</span><br>See the <a href="https://wiki.mahara.org/wiki/System_Administrator's_Guide/Installing_Mahara">installation guide</a> for instructions on how to set it up. If you have already set up cron, one or more of its activities have failed to run recently.