# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2013, Various
# This file is distributed under the same license as the Elgg package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Elgg master\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-07-09 15:46+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../admin/backup-restore.rst:2
msgid "Backup and Restore"
msgstr ""

#: ../../admin/backup-restore.rst:6
#: ../../admin/composer.rst:9
#: ../../admin/cron.rst:6
#: ../../admin/duplicate-installation.rst:6
#: ../../admin/getting-help.rst:10
#: ../../admin/performance.rst:8
#: ../../admin/plugins.rst:8
#: ../../admin/security.rst:8
#: ../../admin/upgrading.rst:11
#: ../../admin/uservalidation.rst:8
msgid "Contents"
msgstr ""

#: ../../admin/backup-restore.rst:9
#: ../../admin/duplicate-installation.rst:9
msgid "Introduction"
msgstr ""

#: ../../admin/backup-restore.rst:12
msgid "Why"
msgstr ""

#: ../../admin/backup-restore.rst:14
msgid "Shared hosting providers typically don't provide an automated way to backup your Elgg installation. This article will address a method of accomplishing this task."
msgstr ""

#: ../../admin/backup-restore.rst:16
msgid "In IT there are often many ways to accomplish the same thing. Keep that in mind. This article will explain one method to backup and restore your Elgg installation on a shared hosting provider that uses the CPanel application. However, the ideas presented here can be tailored to other applications as well. The following are typical situations that might require a procedure such as this:"
msgstr ""

#: ../../admin/backup-restore.rst:18
msgid "Disaster Recovery"
msgstr ""

#: ../../admin/backup-restore.rst:19
msgid "Moving your Elgg site to a new host"
msgstr ""

#: ../../admin/backup-restore.rst:20
msgid "Duplicating an installation"
msgstr ""

#: ../../admin/backup-restore.rst:23
msgid "What"
msgstr ""

#: ../../admin/backup-restore.rst:25
msgid "Topics covered:"
msgstr ""

#: ../../admin/backup-restore.rst:27
msgid "Full backups of the Elgg directories and MySQL databases are performed daily (automated)"
msgstr ""

#: ../../admin/backup-restore.rst:28
msgid "The backups are sent to an off-site location via FTP (automated)"
msgstr ""

#: ../../admin/backup-restore.rst:29
msgid "The local backups are deleted after successful transfer to the off-site location (automatic)"
msgstr ""

#: ../../admin/backup-restore.rst:30
msgid "Five days of backups will be maintained (automated)"
msgstr ""

#: ../../admin/backup-restore.rst:31
msgid "Restoration of data to the new host (manual)"
msgstr ""

#: ../../admin/backup-restore.rst:33
msgid "This process was composed with assistance from previous articles in the Elgg documentation wiki."
msgstr ""

#: ../../admin/backup-restore.rst:36
msgid "Assumptions"
msgstr ""

#: ../../admin/backup-restore.rst:38
msgid "The following assumptions have been made:"
msgstr ""

#: ../../admin/backup-restore.rst:40
msgid "The Elgg program directory is ``/home/userx/public_html``"
msgstr ""

#: ../../admin/backup-restore.rst:41
msgid "The Elgg data directory is ``/home/userx/elggdata``"
msgstr ""

#: ../../admin/backup-restore.rst:42
msgid "You've created a local directory for your backups at ``/home/userx/sitebackups``"
msgstr ""

#: ../../admin/backup-restore.rst:43
msgid "You have an off-site FTP server to send the backup files to"
msgstr ""

#: ../../admin/backup-restore.rst:44
msgid "The directory that you will be saving the off-site backups to is ``/home/usery/sitebackups/``"
msgstr ""

#: ../../admin/backup-restore.rst:45
msgid "You will be restoring the site to a second shared hosting provider in the ``/home/usery/public_html`` directory"
msgstr ""

#: ../../admin/backup-restore.rst:49
msgid "Be sure to replace ``userx``, ``usery``, ``http://mynewdomain.com`` and all passwords with values that reflect your actual installation!"
msgstr ""

#: ../../admin/backup-restore.rst:52
msgid "Creating a usable backup - automatically"
msgstr ""

#: ../../admin/backup-restore.rst:55
msgid "Customize the backup script"
msgstr ""

#: ../../admin/backup-restore.rst:57
msgid "The script that you will use can be found :doc:`here <backup/ftp-backup-script>` ."
msgstr ""

#: ../../admin/backup-restore.rst:59
msgid "Just copy the script to a text file and name the file with a .pl extension. You can use any text editor to update the file."
msgstr ""

#: ../../admin/backup-restore.rst:61
msgid "Change the following to reflect your directory structure:"
msgstr ""

#: ../../admin/backup-restore.rst:71
msgid "Change the following to reflect your database parameters:"
msgstr ""

#: ../../admin/backup-restore.rst:82
msgid "Change the following to reflect your off-site FTP server parameters:"
msgstr ""

#: ../../admin/backup-restore.rst:92
msgid "Save the file with the ``.pl`` extension (for the purposes of this article we will name the file: ``elgg-ftp-backup-script.pl``) and upload it to the following directory ``/home/userx/sitebackups``"
msgstr ""

#: ../../admin/backup-restore.rst:94
msgid "Be aware that you can turn off FTP and flip a bit in the script so that it does not delete the local backup file in the event that you don't want to use off-site storage for your backups."
msgstr ""

#: ../../admin/backup-restore.rst:97
msgid "Configure the backup Cron job"
msgstr ""

#: ../../admin/backup-restore.rst:99
msgid "Login to your CPanel application and click on the \"Cron Jobs\" link. In the Common Settings dropdown choose \"Once a day\" and type the following in the command field ``/usr/bin/perl /home/userx/sitebackups/elgg-ftp-backup-script.pl``"
msgstr ""

#: ../../admin/backup-restore.rst:101
msgid "Click on the \"Add New Cron Job\" button. Daily full backups are now scheduled and will be transferred off-site."
msgstr ""

#: ../../admin/backup-restore.rst:104
msgid "Configure the cleanup Cron job"
msgstr ""

#: ../../admin/backup-restore.rst:106
msgid "If you are sending your backups, via FTP, to another shared hosting provider that uses the CPanel application or you've turned off FTP altogether you can configure your data retention as follows."
msgstr ""

#: ../../admin/backup-restore.rst:108
msgid "Login to your CPanel application for your FTP site, or locally if you're not using FTP, and click on the \"Cron Jobs\" link. In the Common Settings dropdown choose \"Once a day\" and type the following in the command field ``find /home/usery/sitebackups/full_* -mtime +4 -exec rm {} \\;``"
msgstr ""

#: ../../admin/backup-restore.rst:110
msgid "The ``-mtime X`` parameter will set the number of days to retain backups. All files older than ``x`` number of days will be deleted. Click on the \"Add New Cron Job\" button. You have now configured your backup retention time."
msgstr ""

#: ../../admin/backup-restore.rst:113
msgid "Restoring from backup"
msgstr ""

#: ../../admin/backup-restore.rst:116
msgid "Prepare your backup files"
msgstr ""

#: ../../admin/backup-restore.rst:118
msgid "The assumption is that you're restoring your site to another shared hosting provider with CPanel."
msgstr ""

#: ../../admin/backup-restore.rst:120
msgid "When the script backed the files up the original directory structure was maintained in the zip file. We need to do a little cleanup. Perform the following:"
msgstr ""

#: ../../admin/backup-restore.rst:122
msgid "Download the backup file that you wish to restore from"
msgstr ""

#: ../../admin/backup-restore.rst:123
msgid "Extract the contents of the backup file"
msgstr ""

#: ../../admin/backup-restore.rst:127
msgid "Drill down and you will find your site backup and SQL backup. Extract both of these. You will then have:"
msgstr ""

#: ../../admin/backup-restore.rst:125
msgid "a MySQL dump file with a ``.sql`` extension"
msgstr ""

#: ../../admin/backup-restore.rst:127
msgid "another directory structure with the contents of:"
msgstr ""

#: ../../admin/backup-restore.rst:127
msgid "``/home/userx/public_html``"
msgstr ""

#: ../../admin/backup-restore.rst:128
msgid "``/home/userx/elggdata``"
msgstr ""

#: ../../admin/backup-restore.rst:129
msgid "Repackage the contents of the ``/home/userx/public_html`` directory as a zip file so that the files are in the root of the zip file"
msgstr ""

#: ../../admin/backup-restore.rst:130
msgid "The reason for doing this is simple. It's much more efficient to upload one zip file than it is to ftp the contents of the ``/home/userx/public_html`` directory to your new host."
msgstr ""

#: ../../admin/backup-restore.rst:131
msgid "Repackage the contents of the /home/userx/elggdata directory as a zip file so that the files are in the root of the zip file"
msgstr ""

#: ../../admin/backup-restore.rst:133
msgid "You should now have the following files:"
msgstr ""

#: ../../admin/backup-restore.rst:135
msgid "the ``.sql`` file"
msgstr ""

#: ../../admin/backup-restore.rst:136
msgid "the zip file with the contents of ``/home/userx/public_html`` in the root"
msgstr ""

#: ../../admin/backup-restore.rst:137
msgid "the zip file with the contents of ``/home/userx/elggdata`` in the root"
msgstr ""

#: ../../admin/backup-restore.rst:140
msgid "Restore the files"
msgstr ""

#: ../../admin/backup-restore.rst:142
msgid "This is written with the assumption that you're restoring to a different host but maintaining the original directory structure. Perform the following:"
msgstr ""

#: ../../admin/backup-restore.rst:144
msgid "Login to the CPanel application on the host that you wish to restore the site to and open the File Manager."
msgstr ""

#: ../../admin/backup-restore.rst:148
msgid "Navigate to ``/home/usery/public_html``"
msgstr ""

#: ../../admin/backup-restore.rst:146
msgid "Upload the zip file that contains the ``/home/userx/public_html`` files"
msgstr ""

#: ../../admin/backup-restore.rst:147
#: ../../admin/backup-restore.rst:152
msgid "Extract the zip file"
msgstr ""

#: ../../admin/backup-restore.rst:148
msgid "You should now see all of the files in ``/home/usery/public_html``"
msgstr ""

#: ../../admin/backup-restore.rst:149
#: ../../admin/backup-restore.rst:154
msgid "Delete the zip file"
msgstr ""

#: ../../admin/backup-restore.rst:154
msgid "Navigate to ``/home/usery/elggdata``"
msgstr ""

#: ../../admin/backup-restore.rst:151
msgid "Upload the zip file that contains the ``/home/userx/elggdata`` files"
msgstr ""

#: ../../admin/backup-restore.rst:153
msgid "You should now see all of the files in /home/usery/elggdata"
msgstr ""

#: ../../admin/backup-restore.rst:156
msgid "Program and data file restoration is complete"
msgstr ""

#: ../../admin/backup-restore.rst:159
msgid "Restore the MySQL Database"
msgstr ""

#: ../../admin/backup-restore.rst:163
msgid "Again, the assumption here is that you're restoring your Elgg installation to a second shared hosting provider. Each shared hosting provider prepends the account holder's name to the databases associated with that account. For example, the username for our primary host is ``userx`` so the host will prepend ``userx_`` to give us a database name of ``userx_elgg``. When we restore to our second shared hosting provider we're doing so with a username of ``usery`` so our database name will be ``usery_elgg``. The hosting providers don't allow you to modify this behavior. So the process here isn't as simple as just restoring the database from backup to the usery account. However, having said that, it's not terribly difficult either."
msgstr ""

#: ../../admin/backup-restore.rst:166
msgid "Edit the MySQL backup"
msgstr ""

#: ../../admin/backup-restore.rst:168
msgid "Open the ``.sql`` file that you extracted from your backup in your favorite text editor. Comment out the following lines with a hash mark:"
msgstr ""

#: ../../admin/backup-restore.rst:175
msgid "Save the file."
msgstr ""

#: ../../admin/backup-restore.rst:178
msgid "Create the new database"
msgstr ""

#: ../../admin/backup-restore.rst:180
msgid "Perform the following:"
msgstr ""

#: ../../admin/backup-restore.rst:189
msgid "Login to the CPanel application on the new host and click on the \"MySQL Databases\" icon"
msgstr ""

#: ../../admin/backup-restore.rst:183
msgid "Fill in the database name and click the \"create\" button. For our example we are going to stick with ``elgg`` which will give us a database name of ``usery_elgg``"
msgstr ""

#: ../../admin/backup-restore.rst:185
msgid "You can associate an existing user with the new database, but to create a new user you will need to:"
msgstr ""

#: ../../admin/backup-restore.rst:185
msgid "Go to the \"Add New User\" section of the \"MySQL Databases\" page"
msgstr ""

#: ../../admin/backup-restore.rst:186
msgid "Enter the username and password. For our example we're going to keep it simple and use ``elgg`` once again. This will give us a username of ``usery_elgg``"
msgstr ""

#: ../../admin/backup-restore.rst:189
msgid "Associate the new user with the new database"
msgstr ""

#: ../../admin/backup-restore.rst:188
msgid "Go to the \"Add User To Database\" section of the \"MySQL Databases\" page. Add the ``usery_elgg`` user to the ``usery_elgg`` database"
msgstr ""

#: ../../admin/backup-restore.rst:189
msgid "Select \"All Privileges\" and click the \"Make Changes\" button"
msgstr ""

#: ../../admin/backup-restore.rst:192
msgid "Restore the production database"
msgstr ""

#: ../../admin/backup-restore.rst:194
msgid "Now it's time to restore the MySQL backup file by importing it into our new database named \"usery_elgg\"."
msgstr ""

#: ../../admin/backup-restore.rst:200
msgid "Login to the CPanel application on the new host and click on the \"phpMyAdmin icon"
msgstr ""

#: ../../admin/backup-restore.rst:197
msgid "Choose the ``usery_elgg`` database in the left hand column"
msgstr ""

#: ../../admin/backup-restore.rst:198
msgid "Click on the \"import\" tab at the top of the page"
msgstr ""

#: ../../admin/backup-restore.rst:199
msgid "Browse to the ``.sql`` backup on your local computer and select it"
msgstr ""

#: ../../admin/backup-restore.rst:200
msgid "Click the \"Go\" button on the bottom right side of the page"
msgstr ""

#: ../../admin/backup-restore.rst:202
msgid "You should now see a message stating that the operation was successful"
msgstr ""

#: ../../admin/backup-restore.rst:205
msgid "Bringing it all together"
msgstr ""

#: ../../admin/backup-restore.rst:207
msgid "The restored elgg installation knows **nothing** about the new database name, database username, directory structure, etc. That's what we're going to address here."
msgstr ""

#: ../../admin/backup-restore.rst:209
msgid "Edit ``/public_html/elgg-config/settings.php`` on the new hosting provider to reflect the database information for the database that you just created."
msgstr ""

#: ../../admin/backup-restore.rst:231
msgid "Upload the ``settings.php`` file back to the new host - overwriting the existing file."
msgstr ""

#: ../../admin/backup-restore.rst:233
msgid "Open the phpMyAdmin tool on the new host from the CPanel. Select the ``usery_elgg`` database on the left and click the SQL tab on the top of the page. Run the following SQL queries against the ``usery_elgg`` database:"
msgstr ""

#: ../../admin/backup-restore.rst:235
#: ../../admin/duplicate-installation.rst:175
msgid "Change the installation path"
msgstr ""

#: ../../admin/backup-restore.rst:241
#: ../../admin/duplicate-installation.rst:182
msgid "Change the data directory"
msgstr ""

#: ../../admin/backup-restore.rst:247
msgid "Change the filestore data directory"
msgstr ""

#: ../../admin/backup-restore.rst:254
msgid "Finalizing the new installation"
msgstr ""

#: ../../admin/backup-restore.rst:256
msgid "Run the upgrade script by visiting the following URL: ``http://mynewdomain.com/upgrade.php`` . Do this step twice - back to back."
msgstr ""

#: ../../admin/backup-restore.rst:258
msgid "Update your DNS records so that your host name resolves to the new host's IP address if this is a permanent move."
msgstr ""

#: ../../admin/backup-restore.rst:261
msgid "Congratulations!"
msgstr ""

#: ../../admin/backup-restore.rst:263
msgid "If you followed the steps outlined here you should now have a fully functional copy of your primary Elgg installation."
msgstr ""

#: ../../admin/backup-restore.rst:266
#: ../../admin/duplicate-installation.rst:231
msgid "Related"
msgstr ""

#: ../../admin/backup/ftp-backup-script.rst:2
msgid "FTP backup script"
msgstr ""

#: ../../admin/backup/ftp-backup-script.rst:4
msgid "Here is an automated script for backing up an Elgg installation."
msgstr ""

#: ../../admin/composer.rst:2
msgid "Composer installation"
msgstr ""

#: ../../admin/composer.rst:4
msgid "The easiest way to keep your Elgg site up-to-date is by using `Composer`_. Composer will take care of installing all the required dependencies of all plugins and Elgg, while also keeping those depencies up-to-date without having conflicts."
msgstr ""

#: ../../admin/composer.rst:12
msgid "Install Composer"
msgstr ""

#: ../../admin/composer.rst:14
msgid "https://getcomposer.org/download/"
msgstr ""

#: ../../admin/composer.rst:17
msgid "Install Elgg as a Composer Project"
msgstr ""

#: ../../admin/composer.rst:26
msgid "This will create a composer.json file based of the `Elgg starter project`_ which has the basics of installing Elgg."
msgstr ""

#: ../../admin/composer.rst:29
msgid "Open your browser"
msgstr ""

#: ../../admin/composer.rst:31
msgid "Go to your browser and install Elgg via the installation interface"
msgstr ""

#: ../../admin/composer.rst:34
msgid "Setup version controls"
msgstr ""

#: ../../admin/composer.rst:36
msgid "This step is optional but highly recommended. It'll allow you to easily manage the installation of the same plugin versions between environments (development/testing/production)."
msgstr ""

#: ../../admin/composer.rst:50
msgid "Install plugins"
msgstr ""

#: ../../admin/composer.rst:52
msgid "Install plugins as Composer depencies. This assumes that a plugin has been registered on `Packagist`_"
msgstr ""

#: ../../admin/composer.rst:61
msgid "Commit"
msgstr ""

#: ../../admin/composer.rst:63
msgid "Make sure ``composer.lock`` is not ignored in ``.gitignore``"
msgstr ""

#: ../../admin/composer.rst:72
msgid "Deploy to production"
msgstr ""

#: ../../admin/composer.rst:75
msgid "Initial Deploy"
msgstr ""

#: ../../admin/composer.rst:89
msgid "Subsequent Deploys"
msgstr ""

#: ../../admin/cron.rst:2
msgid "Cron"
msgstr ""

#: ../../admin/cron.rst:9
msgid "What does it do?"
msgstr ""

#: ../../admin/cron.rst:11
msgid "`Cron`_ is a program available on Unix-based operating systems that enables users to run commands and scripts at set intervals or at specific times."
msgstr ""

#: ../../admin/cron.rst:14
msgid "Elgg's cron handler allows administrators and plugin developers to setup jobs that need to be executed at set intervals."
msgstr ""

#: ../../admin/cron.rst:17
msgid "Most common examples of cron jobs in Elgg include:"
msgstr ""

#: ../../admin/cron.rst:19
msgid "sending out queued notifications"
msgstr ""

#: ../../admin/cron.rst:20
msgid "rotating the system log in the database"
msgstr ""

#: ../../admin/cron.rst:21
msgid "collecting garbage in the database (compacting the database by removing entries that are no longer required)"
msgstr ""

#: ../../admin/cron.rst:23
msgid "Plugins can add jobs by registering a plugin hook handler for one of the following cron intervals:"
msgstr ""

#: ../../admin/cron.rst:25
msgid "``minute`` - Run every minute"
msgstr ""

#: ../../admin/cron.rst:26
msgid "``fiveminute`` - Run every 5 minutes"
msgstr ""

#: ../../admin/cron.rst:27
msgid "``fifteenmin`` - Run every 15 minutes"
msgstr ""

#: ../../admin/cron.rst:28
msgid "``halfhour`` - Run every 30 minutes"
msgstr ""

#: ../../admin/cron.rst:29
msgid "``hourly`` - Run every hour"
msgstr ""

#: ../../admin/cron.rst:30
msgid "``daily`` - Run every day"
msgstr ""

#: ../../admin/cron.rst:31
msgid "``weekly`` - Run every week"
msgstr ""

#: ../../admin/cron.rst:32
msgid "``monthly`` - Run every month"
msgstr ""

#: ../../admin/cron.rst:33
msgid "``yearly`` - Run every year"
msgstr ""

#: ../../admin/cron.rst:50
msgid "How does it work?"
msgstr ""

#: ../../admin/cron.rst:52
msgid "``crontab`` must be setup in such a way as to activate Elgg cron handler every minute, or at a specific interval. Once cron tab activates the cron job, Elgg executes all hook handlers attached to that interval."
msgstr ""

#: ../../admin/cron.rst:55
msgid "If you have SSH access to your Linux servers, type ``crontab -e`` and add your crontab configuration."
msgstr ""

#: ../../admin/cron.rst:61
msgid "The above command will run every minute and activate all due cron jobs."
msgstr ""

#: ../../admin/cron.rst:63
msgid "Optionally you can activate handlers for a specific interval:"
msgstr ""

#: ../../admin/cron.rst:70
msgid "More information about cron can be found at:"
msgstr ""

#: ../../admin/duplicate-installation.rst:2
msgid "Duplicate Installation"
msgstr ""

#: ../../admin/duplicate-installation.rst:12
msgid "Why Duplicate an Elgg Installation?"
msgstr ""

#: ../../admin/duplicate-installation.rst:14
msgid "There are many reasons you may want to duplicate an Elgg installation: moving the site to another server, creating a test or development server, and creating functional backups are the most common. To create a successful duplicate of an Elgg site, 3 things need to be copied:"
msgstr ""

#: ../../admin/duplicate-installation.rst:17
msgid "Database"
msgstr ""

#: ../../admin/duplicate-installation.rst:18
msgid "Data from the data directory"
msgstr ""

#: ../../admin/duplicate-installation.rst:19
msgid "Code"
msgstr ""

#: ../../admin/duplicate-installation.rst:21
msgid "Also at least 5 pieces of information must be changed from the copied installation:"
msgstr ""

#: ../../admin/duplicate-installation.rst:23
msgid "``elgg-config/settings.php`` file which could also be in the pre 2.0 location ``engine/settings.php``"
msgstr ""

#: ../../admin/duplicate-installation.rst:24
msgid "``.htaccess`` file (Apache) or Nginx configuration depending on server used"
msgstr ""

#: ../../admin/duplicate-installation.rst:25
msgid "database entry for your site entity"
msgstr ""

#: ../../admin/duplicate-installation.rst:26
msgid "database entry for the installation path"
msgstr ""

#: ../../admin/duplicate-installation.rst:27
msgid "database entry for the data path"
msgstr ""

#: ../../admin/duplicate-installation.rst:30
msgid "What Is Not Covered in This Tutorial"
msgstr ""

#: ../../admin/duplicate-installation.rst:32
msgid "This tutorial expects a basic knowledge of Apache, MySQL, and Linux commands. As such, a few things will not be covered in this tutorial. These include:"
msgstr ""

#: ../../admin/duplicate-installation.rst:35
msgid "How to backup and restore MySQL databases"
msgstr ""

#: ../../admin/duplicate-installation.rst:36
msgid "How to configure Apache to work with Elgg"
msgstr ""

#: ../../admin/duplicate-installation.rst:37
msgid "How to transfer files to and from your production server"
msgstr ""

#: ../../admin/duplicate-installation.rst:40
msgid "Before You Start"
msgstr ""

#: ../../admin/duplicate-installation.rst:42
msgid "Before you start, make sure the Elgg installation you want to duplicate is fully functional. You will also need the following items:"
msgstr ""

#: ../../admin/duplicate-installation.rst:44
msgid "A backup of the live Elgg database"
msgstr ""

#: ../../admin/duplicate-installation.rst:45
msgid "A place to copy the live database"
msgstr ""

#: ../../admin/duplicate-installation.rst:47
msgid "A server suitable for installing duplicate Elgg site"
msgstr ""

#: ../../admin/duplicate-installation.rst:47
msgid "(This can be the same server as your production Elgg installation.)"
msgstr ""

#: ../../admin/duplicate-installation.rst:49
msgid "Backups of the database can be obtained various ways, including phpMyAdmin, the MySQL official GUI, and the command line. Talk to your host for information on how to backup and restore databases or use Google to find information on this."
msgstr ""

#: ../../admin/duplicate-installation.rst:52
msgid "During this tutorial, we will make these assumptions about the production Elgg site:"
msgstr ""

#: ../../admin/duplicate-installation.rst:54
msgid "The URL is ``http://www.myelgg.org/``"
msgstr ""

#: ../../admin/duplicate-installation.rst:55
msgid "The installation path is ``/var/www/elgg/``"
msgstr ""

#: ../../admin/duplicate-installation.rst:56
msgid "The data directory is ``/var/data/elgg/``"
msgstr ""

#: ../../admin/duplicate-installation.rst:57
#: ../../admin/duplicate-installation.rst:68
msgid "The database host is ``localhost``"
msgstr ""

#: ../../admin/duplicate-installation.rst:58
msgid "The database name is ``production_elgg``"
msgstr ""

#: ../../admin/duplicate-installation.rst:59
#: ../../admin/duplicate-installation.rst:70
msgid "The database user is ``db_user``"
msgstr ""

#: ../../admin/duplicate-installation.rst:60
#: ../../admin/duplicate-installation.rst:71
msgid "The database password is ``db_password``"
msgstr ""

#: ../../admin/duplicate-installation.rst:61
#: ../../admin/duplicate-installation.rst:72
msgid "The database prefix is ``elgg``"
msgstr ""

#: ../../admin/duplicate-installation.rst:63
msgid "At the end of the tutorial, our test Elgg installation details will be:"
msgstr ""

#: ../../admin/duplicate-installation.rst:65
msgid "The URL is ``http://test.myelgg.org/``"
msgstr ""

#: ../../admin/duplicate-installation.rst:66
msgid "The installation path is ``/var/www/elgg_test/``"
msgstr ""

#: ../../admin/duplicate-installation.rst:67
msgid "The data directory is ``/var/data/elgg_test/``"
msgstr ""

#: ../../admin/duplicate-installation.rst:69
msgid "The database name is ``test_elgg``"
msgstr ""

#: ../../admin/duplicate-installation.rst:75
msgid "Copy Elgg Code to the Test Server"
msgstr ""

#: ../../admin/duplicate-installation.rst:77
msgid "The very first step is to duplicate the production Elgg code. In our example, this is as simple as copying ``/var/www/elgg/`` to ``/var/www/elgg_test/``."
msgstr ""

#: ../../admin/duplicate-installation.rst:85
msgid "Copy Data to the Test Server"
msgstr ""

#: ../../admin/duplicate-installation.rst:87
msgid "In this example, this is as simple as copying ``/var/data/elgg/`` to ``/var/data/elgg_test/``."
msgstr ""

#: ../../admin/duplicate-installation.rst:93
msgid "If you don't have shell access to your server and have to ftp the data, you may need to change ownership and permissions on the files."
msgstr ""

#: ../../admin/duplicate-installation.rst:97
msgid "You also need to delete cache directories from your disk. These correspond to ``cacheroot`` and ``assetroot`` directories in your config."
msgstr ""

#: ../../admin/duplicate-installation.rst:100
msgid "Edit settings.php"
msgstr ""

#: ../../admin/duplicate-installation.rst:102
msgid "The ``elgg-config/settings.php`` file contains the database configuration details. These need to be adjusted for your new test Elgg installation. In our example, we'll look in ``/var/www/elgg_test/elgg-config/settings.php`` and find the lines that look like this:"
msgstr ""

#: ../../admin/duplicate-installation.rst:127
msgid "We need to change these lines to match our new installation:"
msgstr ""

#: ../../admin/duplicate-installation.rst:155
msgid "Notice the ``$CONFIG->dbname`` has changed to reflect our new database."
msgstr ""

#: ../../admin/duplicate-installation.rst:158
msgid "Copy Elgg Database"
msgstr ""

#: ../../admin/duplicate-installation.rst:160
msgid "Now the database must be copied from ``elgg_production`` to ``elgg_test``. See your favorite MySQL manager's documentation for how to make a duplicate database. You will generally export the current database tables to a file, create the new database, and then import the tables that you previously exported."
msgstr ""

#: ../../admin/duplicate-installation.rst:164
msgid "You have two options on updating the values in the database. You could change the values in the export file or you could import the file and change the values with database queries. One advantage of modifying the dump file is that you can also change links that people have created to content within your site. For example, if people have bookmarked pages using the bookmark plugin, the bookmarks will point to the old site unless your update their URLs."
msgstr ""

#: ../../admin/duplicate-installation.rst:170
msgid "Database Entries"
msgstr ""

#: ../../admin/duplicate-installation.rst:172
msgid "We must now change 4 entries in the database. This is easily accomplished with 4 simple SQL commands:"
msgstr ""

#: ../../admin/duplicate-installation.rst:189
msgid "Check .htaccess"
msgstr ""

#: ../../admin/duplicate-installation.rst:191
msgid "If you have made changes to .htaccess that modify any paths, make sure you update them in the test installation."
msgstr ""

#: ../../admin/duplicate-installation.rst:194
msgid "Update Webserver Config"
msgstr ""

#: ../../admin/duplicate-installation.rst:196
msgid "For this example, you must edit the Apache config to enable a subdomain with a document root of ``/var/www/elgg_test/``. If you plan to install into a subdirectory of your document root, this step is unnecessary."
msgstr ""

#: ../../admin/duplicate-installation.rst:199
msgid "If you're using Nginx, you need to update server config to match new paths based on ``install/config/nginx.dist``."
msgstr ""

#: ../../admin/duplicate-installation.rst:202
msgid "Run upgrade.php"
msgstr ""

#: ../../admin/duplicate-installation.rst:204
msgid "To regenerate cached data, make sure to run ``http://test.myelgg.org/upgrade.php``"
msgstr ""

#: ../../admin/duplicate-installation.rst:207
msgid "Tips"
msgstr ""

#: ../../admin/duplicate-installation.rst:209
msgid "It is a good idea to keep a test server around to experiment with installing new mods and doing development work. If you automate restorations to the ``elgg_test`` database, changing the ``$CONFIG`` values and adding the follow lines to the end of the ``elgg_test/elgg-config/settings.php`` file will allow seamless re-writing of the MySQL database entries."
msgstr ""

#: ../../admin/duplicate-installation.rst:235
msgid ":doc:`backup-restore`"
msgstr ""

#: ../../admin/getting-help.rst:2
msgid "Getting Help"
msgstr ""

#: ../../admin/getting-help.rst:4
msgid "Having a problem with Elgg? The best way to get help is to ask at the `Community Site`_. This site is community supported by a large group of volunteers. Here are a few tips to help you get the help you need."
msgstr ""

#: ../../admin/getting-help.rst:13
msgid "Getting help"
msgstr ""

#: ../../admin/getting-help.rst:16
msgid "Don't be a `Help Vampire`_"
msgstr ""

#: ../../admin/getting-help.rst:18
msgid "We were all newbies at one time, but we can all learn. Not showing that you are making attempts to learn on your own or do your own research is off putting for those helping. Also, very generic questions like \"How do I build a forum?\" are almost impossible to answer."
msgstr ""

#: ../../admin/getting-help.rst:23
msgid "Search first"
msgstr ""

#: ../../admin/getting-help.rst:25
msgid "Be sure to search the documentation (this site), the `Community Site`_, and Google before asking a question. New users to Elgg frequently have the same questions, so please search. People are less inclined to reply to a post that has been answered many other times or that can be answered easily by Googling."
msgstr ""

#: ../../admin/getting-help.rst:28
msgid "Ask once"
msgstr ""

#: ../../admin/getting-help.rst:30
msgid "Posting the same questions in multiple places makes it hard to answer you. Ask your question in one place only. Duplicate questions may be moderated."
msgstr ""

#: ../../admin/getting-help.rst:33
msgid "Include Elgg Version"
msgstr ""

#: ../../admin/getting-help.rst:35
msgid "Different versions of Elgg have different features (and different bugs). Including the version of Elgg that you are using will help those helping you."
msgstr ""

#: ../../admin/getting-help.rst:38
msgid "Have a reasonable profile"
msgstr ""

#: ../../admin/getting-help.rst:40
msgid "Profiles that look like spam or have silly names will often be ignored. Joviality is fine, but people are more likely to help Michael than 1337elggHax0r."
msgstr ""

#: ../../admin/getting-help.rst:43
msgid "Post in the appropriate forum"
msgstr ""

#: ../../admin/getting-help.rst:45
msgid "Check to make sure you're posting in the right forum. If you have a question about creating a plugin, don't post to the Elgg Feedback forum. If you need help installing Elgg, post to Technical Support instead of the Theming group."
msgstr ""

#: ../../admin/getting-help.rst:48
msgid "Use a descriptive topic title"
msgstr ""

#: ../../admin/getting-help.rst:50
msgid "Good topic titles concisely describe your problem or question. Bad topic titles are vague, contain all capital letters, and excessive punctuation."
msgstr ""

#: ../../admin/getting-help.rst:52
msgid "Good title: \"White screen after upgrading to 1.7.4.\""
msgstr ""

#: ../../admin/getting-help.rst:54
msgid "Bad title: \"URGENT!!!!! site broke ;-( losing money help!!!!!!!!!!!\""
msgstr ""

#: ../../admin/getting-help.rst:57
msgid "Be detailed"
msgstr ""

#: ../../admin/getting-help.rst:59
msgid "Include as many details about your problem as possible. If you have a live site, include a link. Be forthcoming if community members might ask for more information. We can't help you if you won't give any details!"
msgstr ""

#: ../../admin/getting-help.rst:62
msgid "Keep it public"
msgstr ""

#: ../../admin/getting-help.rst:64
msgid "This is a public forum for the good of the Elgg project. Keep posts public. There's no reason for anyone to ask you to send a private message or email. Likewise, there's no reason to ask anyone to send a private email to you. Post in the public."
msgstr ""

#: ../../admin/getting-help.rst:67
msgid "Guidelines"
msgstr ""

#: ../../admin/getting-help.rst:69
msgid "In addition to the `site-wide Terms and Policies`_, following these guidelines keeps our community site useful and safe for everyone."
msgstr ""

#: ../../admin/getting-help.rst:74
msgid "Content"
msgstr ""

#: ../../admin/getting-help.rst:76
msgid "All content must be safe for work: PG in the US and UK. If your Elgg site has adult content and you have been asked to post a link, please mark it NSFW (Not Safe For Work) so people know."
msgstr ""

#: ../../admin/getting-help.rst:78
msgid "Excessive swearing in any language will not be tolerated."
msgstr ""

#: ../../admin/getting-help.rst:81
msgid "Mood"
msgstr ""

#: ../../admin/getting-help.rst:83
msgid "Working with technical problems can be frustrating. Please keep the community site free of frustration. If you're feeling anxious, take a step away and do something else. Threatening or attacking community members, core developers, or plugin developers will not help solve your problem and will likely get you banned."
msgstr ""

#: ../../admin/getting-help.rst:86
msgid "Advertising"
msgstr ""

#: ../../admin/getting-help.rst:88
msgid "Advertising is not allowed. Posts with any sort of advertising will be moderated."
msgstr ""

#: ../../admin/getting-help.rst:91
msgid "Asking for money / Offering to pay"
msgstr ""

#: ../../admin/getting-help.rst:93
msgid "Don't ask for money on the community site. Likewise, don't offer to pay for answers. If you are looking for custom development, post to the Professional Services group. Posts asking for money or recommending a commercial plugin may be moderated."
msgstr ""

#: ../../admin/getting-help.rst:96
msgid "Links"
msgstr ""

#: ../../admin/getting-help.rst:98
msgid "If you're having a problem with a live site, please provide a link to it."
msgstr ""

#: ../../admin/getting-help.rst:100
msgid "That said, the community site is not a back linking service or SEO tool. Excessive linking will be moderated and your account may be banned."
msgstr ""

#: ../../admin/getting-help.rst:103
msgid "Signatures"
msgstr ""

#: ../../admin/getting-help.rst:105
msgid "There's a reason Elgg doesn't have an option for signatures: they cause clutter and distract from the conversation. Users are discouraged from using signatures on the community site, and signatures with links or advertising will be removed."
msgstr ""

#: ../../admin/getting-help.rst:108
msgid "Bumping, +1, me too"
msgstr ""

#: ../../admin/getting-help.rst:110
msgid "Don't do it. If your question hasn't been answered, see the top of this document for tips. These types of post add nothing to the conversation and may be moderated."
msgstr ""

#: ../../admin/getting-help.rst:113
msgid "Posting Code"
msgstr ""

#: ../../admin/getting-help.rst:115
msgid "Long bits of code are confusing to read through in a forums context. Please use http://elgg.pastebin.com to post long bits of code and provide the Paste Bin link instead of directly posting the code."
msgstr ""

#: ../../admin/getting-help.rst:118
msgid "Good Ideas"
msgstr ""

#: ../../admin/getting-help.rst:120
msgid "Not policies, but good ideas."
msgstr ""

#: ../../admin/getting-help.rst:123
msgid "Say thanks"
msgstr ""

#: ../../admin/getting-help.rst:125
msgid "Did someone help you? Be sure to thank them! The community site is run by volunteers. No one has to help you with your problem. Be sure to show your appreciation!"
msgstr ""

#: ../../admin/getting-help.rst:128
msgid "Give back"
msgstr ""

#: ../../admin/getting-help.rst:130
msgid "Have a tip for Elgg? See someone with a similar problem you had? You've been there and can help them out, so give them a hand!"
msgstr ""

#: ../../admin/getting_started.rst:2
msgid "Getting Started"
msgstr ""

#: ../../admin/getting_started.rst:4
msgid "You have installed Elgg and worked through any potential initial issues. What now? Here are some suggestions on how to to familiarize yourself with Elgg."
msgstr ""

#: ../../admin/getting_started.rst:8
msgid "Focus first on core functionality"
msgstr ""

#: ../../admin/getting_started.rst:10
msgid "When you're new to Elgg, it's best to explore the stock features in core and its bundled plugins before installing any third party plugins. It's tempting install every interesting plugin from the community site, but exploring the core features builds a familiarity with Elgg's expected behavior, and prevents introducing any confusing bugs from third party plugin into your new Elgg network."
msgstr ""

#: ../../admin/getting_started.rst:12
msgid "Elgg installs with a basic set of social network plugins activated: blogs, social bookmarking, files, groups, likes, message boards, wiki-like pages, user profiles, and microblogging. To change the plugins that are activated, log in as an admin user, then use the topbar to browse to Administration, then to Plugins on the right sidebar."
msgstr ""

#: ../../admin/getting_started.rst:14
msgid "The user you create during installation is an admin user."
msgstr ""

#: ../../admin/getting_started.rst:17
msgid "Create test users"
msgstr ""

#: ../../admin/getting_started.rst:18
msgid "Users can be created two ways in stock Elgg:"
msgstr ""

#: ../../admin/getting_started.rst:20
msgid "Complete the signup process using a different email address and username. (Logout first or use a different browser!)"
msgstr ""

#: ../../admin/getting_started.rst:21
msgid "Add a user through the Admin section by browsing to Administration -> Users -> Add New User."
msgstr ""

#: ../../admin/getting_started.rst:23
msgid "Users that self-register must validate their account through email before they can log in. Users that an admin creates are already validated."
msgstr ""

#: ../../admin/getting_started.rst:26
msgid "Explore user functionality"
msgstr ""

#: ../../admin/getting_started.rst:27
msgid "Use your test users to create blogs, add widgets to your profile or dashboard, post to the Wire (microblogging), and create pages (wiki-like page creation). Investigate the Settings on the topbar. This is where a user sets notification settings and configures tools (which will be blank because none of the default plugins add controls here)."
msgstr ""

#: ../../admin/getting_started.rst:30
msgid "Explore admin functionality"
msgstr ""

#: ../../admin/getting_started.rst:31
msgid "All of the admin controls are found by clicking Administration in the topbar. The has a dashboard with a widget that explains the various sections. Change options in the Configure menu to change how Elgg looks and acts."
msgstr ""

#: ../../admin/getting_started.rst:34
msgid "Extending Elgg"
msgstr ""

#: ../../admin/getting_started.rst:35
msgid "After exploring what Elgg can do out of the box, install some themes and plugins. You can find many plugins and themes at the community site that have been developed by third parties. These plugins do everything from changing language strings, to adding chat, to completely redesigning Elgg's interface. Because these plugins are not official, be certain to check the comments to make sure you only install well-written plugins by high quality developers."
msgstr ""

#: ../../admin/index.rst:2
msgid "Administrator Guides"
msgstr ""

#: ../../admin/index.rst:4
msgid "Best practices for effectively managing an Elgg-based site."
msgstr ""

#: ../../admin/performance.rst:2
msgid "Performance"
msgstr ""

#: ../../admin/performance.rst:4
msgid "Make your site run as smoothly and responsively as possible."
msgstr ""

#: ../../admin/performance.rst:11
msgid "Can Elgg scale to X million users?"
msgstr ""

#: ../../admin/performance.rst:13
msgid "People often ask whether Elgg can scale to large installations."
msgstr ""

#: ../../admin/performance.rst:15
msgid "First, we might stop and ask, \"where are you planning to get all those users?\" Seriously, though, this is a really interesting problem. Making Elgg scale is, if anything, an issue of technical engineering. It's interesting but more or less a solved problem. Computer science doesn't work differently for Elgg than for Google, for example. Getting millions of users? That's like the Holy Grail of the entire tech industry."
msgstr ""

#: ../../admin/performance.rst:22
msgid "Second, as with most things in life, the answer is \"it depends\":"
msgstr ""

#: ../../admin/performance.rst:24
msgid "How active are your users?"
msgstr ""

#: ../../admin/performance.rst:25
msgid "What hardware is Elgg running on?"
msgstr ""

#: ../../admin/performance.rst:26
msgid "Are your plugins behaving well?"
msgstr ""

#: ../../admin/performance.rst:28
msgid "`Improving the efficiency of the Elgg engine`__ is an ongoing project, although there are limits to the amount that any script can do."
msgstr ""

#: ../../admin/performance.rst:33
msgid "If you are serious about scalability you will probably want to look at a number of things yourself."
msgstr ""

#: ../../admin/performance.rst:36
msgid "Measure first"
msgstr ""

#: ../../admin/performance.rst:38
msgid "There is no point in throwing resources at a problem if you don't know:"
msgstr ""

#: ../../admin/performance.rst:40
msgid "what the problem is"
msgstr ""

#: ../../admin/performance.rst:41
msgid "what resources the problem needs"
msgstr ""

#: ../../admin/performance.rst:42
msgid "where those resources are needed"
msgstr ""

#: ../../admin/performance.rst:44
msgid "Invest in some kind of profiling to tell you where your bottleneck is, especially if you're considering throwing significant money at a problem."
msgstr ""

#: ../../admin/performance.rst:48
msgid "Tune MySQL"
msgstr ""

#: ../../admin/performance.rst:50
msgid "Elgg makes extensive use of the back end database, making many trips on each pageload. This is perfectly normal and a well configured database server will be able to cope with thousands of requests per second."
msgstr ""

#: ../../admin/performance.rst:53
msgid "Here are some configuration tips that might help:"
msgstr ""

#: ../../admin/performance.rst:55
msgid "Make sure that MySQL is configured to use an appropriate my.cnf for the size of your website."
msgstr ""

#: ../../admin/performance.rst:56
msgid "Increase the amount of memory available to PHP and MySQL (you will have to increase the amount of memory available to the php process in any case)"
msgstr ""

#: ../../admin/performance.rst:60
msgid "Enable caching"
msgstr ""

#: ../../admin/performance.rst:62
msgid "Generally, if a program is slow, that is because it is repeatedly performing an expensive computation or operation. Caching allows the system to avoid doing that work over and over again by using memory to store the results so that you can skip all the work on subsequent requests. Below we discuss several generally-available caching solutions relevant to Elgg."
msgstr ""

#: ../../admin/performance.rst:69
msgid "Simplecache"
msgstr ""

#: ../../admin/performance.rst:71
msgid "By default, views are cached in the Elgg data directory for a given period of time. This removes the need for a view to be regenerated on every page load."
msgstr ""

#: ../../admin/performance.rst:74
msgid "This can be disabled by setting ``$CONFIG->simplecache_enabled = false;`` For best performance, make sure this value is set to ``true``."
msgstr ""

#: ../../admin/performance.rst:77
msgid "This does lead to artifacts during development if you are editing themes in your plugin as the cached version will be used in preference to the one provided by your plugin."
msgstr ""

#: ../../admin/performance.rst:80
msgid "The simple cache can be disabled via the administration menu. It is recommended that you do this on your development platform if you are writing Elgg plugins."
msgstr ""

#: ../../admin/performance.rst:83
msgid "This cache is automatically flushed when a plugin is enabled, disabled or reordered, or when upgrade.php is executed."
msgstr ""

#: ../../admin/performance.rst:86
msgid "For best performance, you can also create a symlink from ``/cache/`` in your www root dir to the ``assetroot`` directory specified in your config (by default it's located under ``/path/to/dataroot/caches/views_simplecache/``:"
msgstr ""

#: ../../admin/performance.rst:95
msgid "If your webserver supports following symlinks, this will serve files straight off disk without booting up PHP each time."
msgstr ""

#: ../../admin/performance.rst:98
msgid "For security reasons, some webservers (e.g. Apache in version 2.4) might follow the symlinks by default only if the owner of the symlink source and target match. If the cache symlink fails to work on your server, you can change the owner of the cache symlink itself (and not the ``/views_simplecache/`` directory) with"
msgstr ""

#: ../../admin/performance.rst:108
msgid "In this example it's assumed that the ``/views_simplecache/`` directory in the data directory is owned by the wwwrun account that belongs to the www group. If this is not the case on your server, you have to modify the chown command accordingly."
msgstr ""

#: ../../admin/performance.rst:113
msgid "System cache"
msgstr ""

#: ../../admin/performance.rst:115
msgid "The location of views are cached so that they do not have to be discovered (profiling indicated that page load took a non-linear amount of time the more plugins were enabled due to view discovery). Elgg also caches information like the language mapping and class map."
msgstr ""

#: ../../admin/performance.rst:120
msgid "This can be disabled by setting ``$CONFIG->system_cache_enabled = false;`` For best performance, make sure this value is set to ``true``."
msgstr ""

#: ../../admin/performance.rst:123
msgid "This is currently stored in files in your dataroot (although later versions of Elgg may use memcache). As with the simple cache it is flushed when a plugin is enabled, disabled or reordered, or when upgrade.php is executed."
msgstr ""

#: ../../admin/performance.rst:128
msgid "The system cache can be disabled via the administration menu, and it is recommended that you do this on your development platform if you are writing Elgg plugins."
msgstr ""

#: ../../admin/performance.rst:133
msgid "Boot cache"
msgstr ""

#: ../../admin/performance.rst:135
msgid "Elgg has the ability to cache numerous resources created and fetched during the boot process. To configure how long this cache is valid you must set a TTL in your ``settings.php`` file: ``$CONFIG->boot_cache_ttl = 3600;``"
msgstr ""

#: ../../admin/performance.rst:139
msgid "Look at the `Stash <http://www.stashphp.com/index.html>`_ documentation for more info about the TTL."
msgstr ""

#: ../../admin/performance.rst:143
msgid "Database query cache"
msgstr ""

#: ../../admin/performance.rst:145
msgid "For the lifetime of a given page's execution, a cache of all ``SELECT`` queries is kept. This means that for a given page load a given select query will only ever go out to the database once, even if it is executed multiple times. Any write to the database will flush this cache. This cache will be automatically cleared at the end of a page load."
msgstr ""

#: ../../admin/performance.rst:150
msgid "You may experience memory problems if you use the Elgg framework as a library in a PHP CLI script. This can be disabled by setting ``$CONFIG->db_disable_query_cache = true;``"
msgstr ""

#: ../../admin/performance.rst:155
msgid "Etags and Expires headers"
msgstr ""

#: ../../admin/performance.rst:157
msgid "These technologies tell your users' browsers to cache static assets (CSS, JS, images) locally. Having these enabled greatly reduces server load and improves user-perceived performance."
msgstr ""

#: ../../admin/performance.rst:160
msgid "Use the `Firefox yslow plugin`__ or Chrome DevTools Audits to confirm which technologies are currently running on your site."
msgstr ""

#: ../../admin/performance.rst:166
msgid "If the static assets aren't being cached:"
msgstr ""

#: ../../admin/performance.rst:164
msgid "Verify that you have these extensions installed and enabled on your host"
msgstr ""

#: ../../admin/performance.rst:165
msgid "Update your .htaccess file, if you are upgrading from a previous version of Elgg"
msgstr ""

#: ../../admin/performance.rst:166
msgid "Enable Simplecache_, which turns select views into browser-cacheable assets"
msgstr ""

#: ../../admin/performance.rst:171
msgid "Memcached"
msgstr ""

#: ../../admin/performance.rst:173
msgid "Libmemcached was created by Brian Aker and was designed from day one to give the best performance available to users of Memcached."
msgstr ""

#: ../../admin/performance.rst:177
msgid "http://libmemcached.org/About.html and https://secure.php.net/manual/en/book.memcached.php"
msgstr ""

#: ../../admin/performance.rst:179
msgid "Installation requirements:"
msgstr ""

#: ../../admin/performance.rst:181
msgid "php-memcached"
msgstr ""

#: ../../admin/performance.rst:182
msgid "libmemcached"
msgstr ""

#: ../../admin/performance.rst:183
msgid "memcached"
msgstr ""

#: ../../admin/performance.rst:185
msgid "Configuration:"
msgstr ""

#: ../../admin/performance.rst:187
msgid "Uncomment and populate the following sections in ``settings.php``"
msgstr ""

#: ../../admin/performance.rst:198
msgid "Optionaly if you run multiple Elgg installations but use ony one Memcache server, you may want to add a namespace prefix. In order to do this, uncomment the following line"
msgstr ""

#: ../../admin/performance.rst:206
msgid "Squid"
msgstr ""

#: ../../admin/performance.rst:208
msgid "We have had good results by using `Squid`_ to cache images for us."
msgstr ""

#: ../../admin/performance.rst:214
msgid "Bytecode caching"
msgstr ""

#: ../../admin/performance.rst:216
msgid "There are numerous PHP code caches available on the market. These speed up your site by caching the compiled byte code from your script meaning that your server doesn't have to compile the PHP code each time it is executed."
msgstr ""

#: ../../admin/performance.rst:222
msgid "Direct file serving"
msgstr ""

#: ../../admin/performance.rst:224
msgid "If your server can be configured to support the X-Sendfile or X-Accel headers, you can configure it to be used in ``settings.php``. This allows your web server to directly stream files to the client instead of using PHP's ``readfile()``."
msgstr ""

#: ../../admin/performance.rst:229
msgid "Composer Autoloader Optimization"
msgstr ""

#: ../../admin/performance.rst:231
msgid "The Composer autoloader is responsible for loading classes provided by dependencies of Elgg. The way the autoloader works is it searches for a classname in the installed dependencies. While this is mostly a fast process it can be optimized."
msgstr ""

#: ../../admin/performance.rst:234
msgid "You can optimize the autoloader 2 different ways. The first is in the commandline, the other is in the ``composer.json`` of your project."
msgstr ""

#: ../../admin/performance.rst:236
msgid "If you want to optimize the autoloader using the commandline use the ``-o`` flag. The disadvantage is you have to add the ``-o`` flag every time you run Composer."
msgstr ""

#: ../../admin/performance.rst:247
msgid "The second option is to add the optimization to your ``composer.json`` file, that way you never forget it."
msgstr ""

#: ../../admin/performance.rst:260
msgid "Check out the `Autoloader Optimization`__ page for more information about how to optimize the Composer autoloader."
msgstr ""

#: ../../admin/performance.rst:266
msgid "As of Elgg 3.0 all the `downloads`__ of Elgg from the website have the optimized autoloader."
msgstr ""

#: ../../admin/performance.rst:271
msgid "Hosting"
msgstr ""

#: ../../admin/performance.rst:273
msgid "Don't expect to run a site catering for millions of users on a cheap shared host. You will need to have your own host hardware and access over the configuration, as well as lots of bandwidth and memory available."
msgstr ""

#: ../../admin/performance.rst:278
msgid "Memory, CPU and bandwidth"
msgstr ""

#: ../../admin/performance.rst:280
msgid "Due to the nature of caching, all caching solutions will require memory. It is a fairly cheap return to throw memory and CPU at the problem."
msgstr ""

#: ../../admin/performance.rst:283
msgid "On advanced hardware it is likely that bandwidth is going to be your bottleneck before the server itself. Ensure that your host can support the load you are suggesting."
msgstr ""

#: ../../admin/performance.rst:287
msgid "Configuration"
msgstr ""

#: ../../admin/performance.rst:289
msgid "Lastly, take a look at your configuration as there are a few gotchas that can catch people."
msgstr ""

#: ../../admin/performance.rst:291
msgid "For example, out of the box, Apache can handle quite a high load. However, most distros of Linux come with mysql configured for small sites. This can result in Apache processes getting stalled waiting to talk to one very overloaded MySQL process."
msgstr ""

#: ../../admin/performance.rst:296
msgid "Check for poorly-behaved plugins"
msgstr ""

#: ../../admin/performance.rst:298
msgid "Plugins can be programmed in a very naive way and this can cause your whole site to feel slow."
msgstr ""

#: ../../admin/performance.rst:300
msgid "Try disabling some plugins to see if that noticeably improves performance. Once you've found a likely offender, go to the original plugin author and report your findings."
msgstr ""

#: ../../admin/performance.rst:304
msgid "Use client-rendered HTML"
msgstr ""

#: ../../admin/performance.rst:306
msgid "We've found that at a certain point, much of the time spent on the server is simply building the HTML of the page with Elgg's views system."
msgstr ""

#: ../../admin/performance.rst:309
msgid "It's very difficult to cache the output of templates since they can generally take arbitrary inputs. Instead of trying to cache the HTML output of certain pages or views, the suggestion is to switch to an HTML-based templating system so that the user's browser can cache the templates themselves. Then have the user's computer do the work of generating the output by applying JSON data to those templates."
msgstr ""

#: ../../admin/performance.rst:314
msgid "This can be very effective, but has the downside of being significant extra development cost. The Elgg team is looking to integrate this strategy into Elgg directly, since it is so effective especially on pages with repeated or hidden content."
msgstr ""

#: ../../admin/plugins.rst:2
msgid "Plugins"
msgstr ""

#: ../../admin/plugins.rst:4
msgid "Plugins can modify the behavior of and add new features to Elgg."
msgstr ""

#: ../../admin/plugins.rst:11
msgid "Where to get plugins"
msgstr ""

#: ../../admin/plugins.rst:13
msgid "Plugins can be obtained from:"
msgstr ""

#: ../../admin/plugins.rst:15
msgid "`The Elgg Community`_"
msgstr ""

#: ../../admin/plugins.rst:16
msgid "`Github`_"
msgstr ""

#: ../../admin/plugins.rst:17
msgid "Third-party sites (typically for a price)"
msgstr ""

#: ../../admin/plugins.rst:19
msgid "If no existing plugins meet your needs, you can `hire a developer`_ or :doc:`create your own </guides/index>`."
msgstr ""

#: ../../admin/plugins.rst:26
msgid "The Elgg Community"
msgstr ""

#: ../../admin/plugins.rst:29
msgid "Finding Plugins"
msgstr ""

#: ../../admin/plugins.rst:32
msgid "Sort based on most popular"
msgstr ""

#: ../../admin/plugins.rst:34
msgid "On the community plugin page, you can sort by date uploaded (Filter: Newest) or number of downloads (Filter: Most downloads). Sorting by the number of downloads is a good idea if you are new to Elgg and want to see which plugins are frequently used by other administrators. These will often (but not always) be higher quality plugins that provide significant capabilities."
msgstr ""

#: ../../admin/plugins.rst:37
msgid "Use the plugin tag search"
msgstr ""

#: ../../admin/plugins.rst:39
msgid "Next to the filtering control on the plugin page is a search box. It enables you to search by tags. Plugins authors choose the tags."
msgstr ""

#: ../../admin/plugins.rst:42
msgid "Look for particular plugin authors"
msgstr ""

#: ../../admin/plugins.rst:44
msgid "The quality of plugins varies substantially. If you find a plugin that works well on your site, you can check what else that plugin author has developed by clicking on their name when viewing a plugin."
msgstr ""

#: ../../admin/plugins.rst:47
msgid "Evaluating Plugins"
msgstr ""

#: ../../admin/plugins.rst:50
msgid "Look at the comments and ratings"
msgstr ""

#: ../../admin/plugins.rst:52
msgid "Before downloading and using a plugin, it is always a good idea to read through the comments that others have left. If you see people complaining that the plugin does not work or makes their site unstable, you probably want to stay away from that plugin. The caveat to that is that sometimes users ignore installation instructions or incorrectly install a plugin and then leave negative feedback. Further, some plugin authors have chosen to not allow comments."
msgstr ""

#: ../../admin/plugins.rst:55
msgid "Install on a test site"
msgstr ""

#: ../../admin/plugins.rst:57
msgid "If you are trying out a plugin for the first time, it is a bad idea to install it on your production site. You should maintain a separate test site for evaluating plugins. It is a good idea to slowly roll out new plugins to your production site even after they pass your evaluation on your test site. This enables you to isolate problems introduced by a new plugin."
msgstr ""

#: ../../admin/plugins.rst:60
msgid "Types of plugins"
msgstr ""

#: ../../admin/plugins.rst:63
msgid "Themes"
msgstr ""

#: ../../admin/plugins.rst:65
msgid "Themes are plugins that modify the look-and-feel of your site. They generally include stylesheets, client-side scripts and views that alter the default presentation and behavior of Elgg."
msgstr ""

#: ../../admin/plugins.rst:70
msgid "Language Packs"
msgstr ""

#: ../../admin/plugins.rst:72
msgid "Language packs are plugins that provide support for other languages."
msgstr ""

#: ../../admin/plugins.rst:74
msgid "Language packs can extend and include translations for language strings found in the core, core plugins and/or third-party plugins."
msgstr ""

#: ../../admin/plugins.rst:77
msgid "Some of the language packs are already included in the core, and can be found in ``languages`` directory in Elgg's root directory. Individual plugins tend to include their translations under the ``languages`` directory within the plugin's root."
msgstr ""

#: ../../admin/plugins.rst:82
msgid "This structure makes it easy to create new language packs that supercede existing language strings or add support for new languages."
msgstr ""

#: ../../admin/plugins.rst:86
msgid "Installation"
msgstr ""

#: ../../admin/plugins.rst:88
msgid "All plugins reside in the ``mod`` directory of your Elgg installation."
msgstr ""

#: ../../admin/plugins.rst:93
msgid "To install a new plugin:"
msgstr ""

#: ../../admin/plugins.rst:91
msgid "extract (unzip) contents of the plugin distribution package"
msgstr ""

#: ../../admin/plugins.rst:92
msgid "copy/FTP the extracted folder into the ``mod`` directory of your Elgg installation"
msgstr ""

#: ../../admin/plugins.rst:93
msgid "activate the plugin from your admin panel"
msgstr ""

#: ../../admin/plugins.rst:99
msgid "To activate a plugin:"
msgstr ""

#: ../../admin/plugins.rst:96
msgid "Log in to your Elgg site with your administrator account"
msgstr ""

#: ../../admin/plugins.rst:97
msgid "Go to Administration -> Configure -> Plugins"
msgstr ""

#: ../../admin/plugins.rst:98
msgid "Find your plugin in the list of installed plugins and click on the 'enable' button."
msgstr ""

#: ../../admin/plugins.rst:104
msgid "Plugin order"
msgstr ""

#: ../../admin/plugins.rst:106
msgid "Plugins are loaded according to the order they are listed on the Plugins page. The initial ordering after an install is more or less random. As more plugins are added by an administrator, they are placed at the bottom of the list."
msgstr ""

#: ../../admin/plugins.rst:108
msgid "Some general rules for ordering plugins:"
msgstr ""

#: ../../admin/plugins.rst:110
msgid "A theme plugin should be last or at least near the bottom"
msgstr ""

#: ../../admin/plugins.rst:111
msgid "A plugin that modifies the behavior of another plugin should be lower in the plugin list"
msgstr ""

#: ../../admin/security.rst:2
msgid "Security"
msgstr ""

#: ../../admin/security.rst:4
msgid "As of Elgg 3.0 several hardening settings have been added to Elgg. You can enable/disable these settings as you like."
msgstr ""

#: ../../admin/security.rst:11
msgid "Upgrade protection"
msgstr ""

#: ../../admin/security.rst:13
msgid "The URL of http://your-elgg-site.com/upgrade.php can be protected by a unique token. This will prevent random users from being able to run this file. The token is not needed for logged in site administrators."
msgstr ""

#: ../../admin/security.rst:17
msgid "Cron protection"
msgstr ""

#: ../../admin/security.rst:19
msgid "The URLs of the :doc:`cron </admin/cron>` can be protected by a unique token. This will prevent random users from being able to run the cron. The token is not needed when running the cron from the commandline of the server."
msgstr ""

#: ../../admin/security.rst:23
msgid "Disable password autocomplete"
msgstr ""

#: ../../admin/security.rst:25
msgid "Data entered in these fields will be cached by the browser. An attacker who can access the victim's browser could steal this information. This is especially important if the application is commonly used in shared computers such as cyber cafes or airport terminals. If you disable this, password management tools can no longer autofill these fields. The support for the autocomplete attribute can be browser specific."
msgstr ""

#: ../../admin/security.rst:30
msgid "Email address change requires password"
msgstr ""

#: ../../admin/security.rst:32
msgid "When a user wishes to change their email address associated with their account, they need to also supply their current password."
msgstr ""

#: ../../admin/security.rst:35
msgid "Email address change requires confirmation"
msgstr ""

#: ../../admin/security.rst:37
msgid "When a user wishes to change their email address associated with their account, they need to confirm the new email address. This is done by sending an email to the new address with a validation link. After clicking this link the new email address will be used."
msgstr ""

#: ../../admin/security.rst:41
msgid "Session bound icons"
msgstr ""

#: ../../admin/security.rst:43
msgid "Entity icons can be session bound by default. This means the URLs generated also contain information about the current session. Having icons session bound makes icon urls not shareable between sessions. The side effect is that caching of these urls will only help the active session."
msgstr ""

#: ../../admin/security.rst:47
msgid "Notification to site administrators"
msgstr ""

#: ../../admin/security.rst:49
msgid "When a new site administrator is added or when a site administrator is removed all the site administrators get a notification about this action."
msgstr ""

#: ../../admin/security.rst:52
msgid "Notifications to user"
msgstr ""

#: ../../admin/security.rst:55
msgid "Site administrator"
msgstr ""

#: ../../admin/security.rst:57
msgid "When the site administrator role is added to or removed from the account, send a notification to the user whos account this is affecting."
msgstr ""

#: ../../admin/security.rst:60
msgid "(Un)ban"
msgstr ""

#: ../../admin/security.rst:62
msgid "When the account of a user gets banned or unbanned, let the affected user know about this action."
msgstr ""

#: ../../admin/security.rst:65
msgid "Minimal username length"
msgstr ""

#: ../../admin/security.rst:67
msgid "You can configure the minimal length the username should have upon registration of a user."
msgstr ""

#: ../../admin/security.rst:70
msgid "Minimal password requirements"
msgstr ""

#: ../../admin/security.rst:72
msgid "You can configure several requirements for new passwords of the users"
msgstr ""

#: ../../admin/security.rst:74
msgid "**length**: the password should be at least x characters long"
msgstr ""

#: ../../admin/security.rst:75
msgid "**lower case**: minimal number of lower case (a-z) characters in the password"
msgstr ""

#: ../../admin/security.rst:76
msgid "**upper case**: minimal number of upper case (A-Z) characters in the password"
msgstr ""

#: ../../admin/security.rst:77
msgid "**numbers**: minimal number of numbers (0-9) characters in the password"
msgstr ""

#: ../../admin/security.rst:78
msgid "**specials**: minimal number of special (like !@#$%^&*(), etc.) characters in the password"
msgstr ""

#: ../../admin/security.rst:81
msgid ".htaccess file access hardening"
msgstr ""

#: ../../admin/security.rst:83
msgid "In the .htaccess file a set of file access hardening rules have been added to prevent direct access to files in certain folders. Enabling these rules `shouldn't` cause any issues when all the plugins you use follow the Elgg coding guidelines."
msgstr ""

#: ../../admin/security.rst:86
msgid "Examples of the rules are:"
msgstr ""

#: ../../admin/security.rst:88
msgid "the ``vendor`` folder. This folder only contains helper libraries that Elgg uses and there is no need for direct access to this folder. All required dependecies are loaded from within Elgg"
msgstr ""

#: ../../admin/security.rst:89
msgid "the ``languages`` folder. This folder contains the main Elgg language files. These files are loaded from within Elgg"
msgstr ""

#: ../../admin/spam.rst:2
msgid "Spam"
msgstr ""

#: ../../admin/spam.rst:4
msgid "Keep spam under control."
msgstr ""

#: ../../admin/spam.rst:6
msgid "Spam is a very common problem that admins need to deal with and which we aim to improve in core, but there are some actions site admins can take to mitigate the problem."
msgstr ""

#: ../../admin/spam.rst:10
msgid "Install an anti-spam plugin"
msgstr ""

#: ../../admin/spam.rst:11
msgid "There are several available on the community"
msgstr ""

#: ../../admin/spam.rst:13
msgid "http://community.elgg.org/plugins/search?f[c][]=spam&sb=Search"
msgstr ""

#: ../../admin/spam.rst:16
msgid "Change the registration url"
msgstr ""

#: ../../admin/spam.rst:17
msgid "Some have said they have good success changing the registration URL, since the spammers are naive bots and can no longer find where to create the fake accounts."
msgstr ""

#: ../../admin/spam.rst:22
msgid "Disable open registration"
msgstr ""

#: ../../admin/spam.rst:23
msgid "If the flow of registrations is low enough, you can vet all users that come in to keep the quality of interaction high."
msgstr ""

#: ../../admin/spam.rst:27
msgid "Contribute to anti-spam measures in core"
msgstr ""

#: ../../admin/spam.rst:29
msgid "https://github.com/Elgg/Elgg/issues?labels=spam&state=open"
msgstr ""

#: ../../admin/upgrading.rst:2
msgid "Upgrading Elgg"
msgstr ""

#: ../../admin/upgrading.rst:4
msgid "This document will guide you through steps necessary to upgrade your Elgg installation to the latest version."
msgstr ""

#: ../../admin/upgrading.rst:6
msgid "If you've written custom plugins, you should also read the developer guides for :doc:`information on upgrading plugin code </appendix/upgrade-notes>` for the latest version of Elgg."
msgstr ""

#: ../../admin/upgrading.rst:14
msgid "Advice"
msgstr ""

#: ../../admin/upgrading.rst:16
msgid "**Back up your database, data directory and code**"
msgstr ""

#: ../../admin/upgrading.rst:17
msgid "Mind any version-specific comments below"
msgstr ""

#: ../../admin/upgrading.rst:18
msgid "Version below 2.0 are advised to only upgrade **one minor version at a time**"
msgstr ""

#: ../../admin/upgrading.rst:19
msgid "You can upgrade from any minor version to any higher minor version in the same major (2.0 -> 2.1 or 2.0 -> 2.3)"
msgstr ""

#: ../../admin/upgrading.rst:20
msgid "You can only upgrade the latest minor version in the previous major version to any minor version in the next version (2.3 -> 3.0 or 2.3 -> 3.2, but not 2.2 -> 3.x)."
msgstr ""

#: ../../admin/upgrading.rst:21
msgid "From Elgg 2.3.* you can upgrade to any future version of Elgg without having to go through each minor version (e.g. you can upgrade directly from 2.3.8 to 3.2.5, without having to upgrade to 3.0 and 3.1)"
msgstr ""

#: ../../admin/upgrading.rst:22
msgid "Try out the new version on a test site before doing an upgrade"
msgstr ""

#: ../../admin/upgrading.rst:23
msgid "Report any problems in plugins to the plugin authors"
msgstr ""

#: ../../admin/upgrading.rst:24
msgid "If you are a plugin author you can `report any backwards-compatibility issues to GitHub <issues_>`_"
msgstr ""

#: ../../admin/upgrading.rst:29
msgid "From 2.3 to 3.0"
msgstr ""

#: ../../admin/upgrading.rst:32
msgid "1. Update ``composer.json``"
msgstr ""

#: ../../admin/upgrading.rst:34
msgid "If you have used Elgg's starter project to install Elgg 2.3, you may need to update your ``composer.json``:"
msgstr ""

#: ../../admin/upgrading.rst:36
msgid "change platform requirements to PHP >= 7.0"
msgstr ""

#: ../../admin/upgrading.rst:37
msgid "optionally, set autoloader optimization parameters"
msgstr ""

#: ../../admin/upgrading.rst:38
msgid "optionally, disable fxp-asset plugin in favor of asset-packagist"
msgstr ""

#: ../../admin/upgrading.rst:40
msgid "Your ``composer.json`` would look something like this (depending what changes you may have introduced yourself):"
msgstr ""

#: ../../admin/upgrading.rst:71
msgid "2. Update ``.htaccess``"
msgstr ""

#: ../../admin/upgrading.rst:73
msgid "Find the line:"
msgstr ""

#: ../../admin/upgrading.rst:79
msgid "And replace it with:"
msgstr ""

#: ../../admin/upgrading.rst:87
msgid "3a. Composer Upgrade (recommended)"
msgstr ""

#: ../../admin/upgrading.rst:89
msgid "If you had your Elgg 2.3 project installed using composer, you can follow this sequence:"
msgstr ""

#: ../../admin/upgrading.rst:91
#: ../../admin/upgrading.rst:116
msgid "**Back up your database, data directory, and code**"
msgstr ""

#: ../../admin/upgrading.rst:106
msgid "In some cases the command line upgrade will fail because some database schema changes need to be applied first. In that case you need to execute the :ref:`Phinx migrations <contribute/database#execute-migration>` manually"
msgstr ""

#: ../../admin/upgrading.rst:110
msgid "3b. Manual Upgrade (legacy approach)"
msgstr ""

#: ../../admin/upgrading.rst:112
msgid "Manual upgrades are a major undertaking for site admins. We discourage you from maintaining an Elgg installation using ZIP dist packages. Save yourself some time by learning how to use ``composer`` and version control systems, such as ``git``. This task will also be complicated if you have third-party plugins and/or have made any modifications to core files!"
msgstr ""

#: ../../admin/upgrading.rst:117
msgid "Log in as an admin to your site"
msgstr ""

#: ../../admin/upgrading.rst:118
msgid "Download the new version of Elgg from http://elgg.org"
msgstr ""

#: ../../admin/upgrading.rst:121
msgid "Update the files"
msgstr ""

#: ../../admin/upgrading.rst:120
msgid "If upgrading to a major version, you need to overwrite all core files and remove any files that were removed from Elgg core, as they may interfere with proper functioning of your site."
msgstr ""

#: ../../admin/upgrading.rst:122
msgid "If upgrading to a minor version or patching, you need to overwrite all core files."
msgstr ""

#: ../../admin/upgrading.rst:124
msgid "Merge any new changes to the rewrite rules"
msgstr ""

#: ../../admin/upgrading.rst:124
msgid "For Apache from ``install/config/htaccess.dist`` into ``.htaccess``"
msgstr ""

#: ../../admin/upgrading.rst:125
msgid "For Nginx from ``install/config/nginx.dist`` into your server configuration (usually inside ``/etc/nginx/sites-enabled``)"
msgstr ""

#: ../../admin/upgrading.rst:126
msgid "Visit http://your-elgg-site.com/upgrade.php"
msgstr ""

#: ../../admin/upgrading.rst:127
msgid "Execute asynchronous upgrades at http://your-elgg-site.com/admin/upgrades"
msgstr ""

#: ../../admin/upgrading.rst:131
msgid "Any modifications should have been written within plugins, so that they are not lost on overwriting. If this is not the case, take care to maintain your modifications."
msgstr ""

#: ../../admin/upgrading.rst:136
msgid "If you are unable to access ``upgrade.php`` script and receive an error, add ``$CONFIG->security_protect_upgrade = false;`` to your ``settings.php`` and remove it after you have completed all of the upgrade steps."
msgstr ""

#: ../../admin/upgrading.rst:141
msgid "If you encounter issues with plugins during the upgrade, add an empty file called ``disabled`` in your ``/mod/`` directory. This will disable the plugins, so that you can finish the core upgrade. You can then deal with issues on per-plugin basis."
msgstr ""

#: ../../admin/upgrading.rst:145
msgid "If you have installed Elgg using a dist package but would now like to switch to composer:"
msgstr ""

#: ../../admin/upgrading.rst:147
msgid "Upgrade your current installation using Manual Upgrade method"
msgstr ""

#: ../../admin/upgrading.rst:148
msgid "Move your codebase to a temporary location"
msgstr ""

#: ../../admin/upgrading.rst:149
msgid "Create a new composer project using Elgg's starter project following :doc:`installation instructions </intro/install>` in the root directory of your current installation"
msgstr ""

#: ../../admin/upgrading.rst:150
msgid "Copy third-party plugins from your old installation into ``/mod`` directory"
msgstr ""

#: ../../admin/upgrading.rst:151
msgid "Run Elgg's installer using your browser or ``elgg-cli`` tool"
msgstr ""

#: ../../admin/upgrading.rst:152
msgid "When you reach the database step, provide the same credentials you have used for manual installation, Elgg will understand that is's an existing installation and will not override any database values"
msgstr ""

#: ../../admin/upgrading.rst:153
msgid "Optionally commit your new project to version control"
msgstr ""

#: ../../admin/upgrading.rst:156
msgid "Applying a patch using Composer"
msgstr ""

#: ../../admin/upgrading.rst:158
msgid "The definition of a patch can be found in the :doc:`Release policy </appendix/releases>`."
msgstr ""

#: ../../admin/upgrading.rst:160
msgid "Your ``composer.json`` requirement for Elgg should be ``~3.y.0`` (where ``y`` is the minor version ``0``, ``1``, etc. you wish to have installed). This will make sure you can easily install patches without the risk of installing the next minor release."
msgstr ""

#: ../../admin/upgrading.rst:171
msgid "Just to be sure you can first verify what will be installed / upgraded by executing the folowing command"
msgstr ""

#: ../../admin/upgrading.rst:181
msgid "To upgrade Elgg simply execute"
msgstr ""

#: ../../admin/upgrading.rst:192
msgid "Earlier versions"
msgstr ""

#: ../../admin/upgrading.rst:194
msgid "Check Elgg documentation that corresponds to the Elgg version you want to upgrade to, by switching the documentation version in the lower left corner of :doc:`Upgrading docs <upgrading>`"
msgstr ""

#: ../../admin/uservalidation.rst:2
msgid "User validation"
msgstr ""

#: ../../admin/uservalidation.rst:4
msgid "Plugins can influence how users are validated before they can use the website."
msgstr ""

#: ../../admin/uservalidation.rst:11
msgid "Listing of unvalidated users"
msgstr ""

#: ../../admin/uservalidation.rst:13
msgid "In the Admin section of the website is a list of all unvalidated users. Some actions can be taken on the users, like delete them from the system or validate them."
msgstr ""

#: ../../admin/uservalidation.rst:16
msgid "Plugins have the option to add additional features to this list."
msgstr ""

#: ../../admin/uservalidation.rst:20
msgid "An example of this is the :doc:`/plugins/uservalidationbyemail` plugin which doesn't allow users onto the website until their e-mail address is validated."
msgstr ""

#: ../../admin/uservalidation.rst:24
msgid "Require admin validation"
msgstr ""

#: ../../admin/uservalidation.rst:26
msgid "In the Site settings under the Users section there is a setting which can be enabled to require admin validation of a new user account before the user can use their account. After registration the user gets notified that their account is awaiting validation by an administrator."
msgstr ""

#: ../../admin/uservalidation.rst:29
msgid "Site administrators can receive an e-mail notification that there are users awaiting validation."
msgstr ""

#: ../../admin/uservalidation.rst:31
msgid "After validation the user is notified that they can use their account."
msgstr ""

