Elgg-Lorea-Hydra/docs/locale/pot/appendix.pot

# 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 1.12\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-03-06 18:02+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"

#: ../../appendix/faqs.rst:2
msgid "FAQs and Other Troubleshooting"
msgstr ""

#: ../../appendix/faqs.rst:4
msgid "Below are some commonly asked questions about Elgg."
msgstr ""

#: ../../appendix/faqs.rst:0
msgid "Contents"
msgstr ""

#: ../../appendix/faqs/general.rst:2
#: ../../appendix/faqs/general.rst:2
msgid "General"
msgstr ""

#: ../../appendix/faqs/general.rst:6
#: ../../appendix/faqs/general.rst:6
msgid ":doc:`/admin/getting-help`"
msgstr ""

#: ../../appendix/faqs/general.rst:9
#: ../../appendix/faqs/general.rst:9
msgid "\"Plugin cannot start and has been deactivated\" or \"This plugin is invalid\""
msgstr ""

#: ../../appendix/faqs/general.rst:10
#: ../../appendix/faqs/general.rst:10
msgid "This error is usually accompanied by more details explaining why the plugin is invalid. This is usually caused by an incorrectly installed plugin."
msgstr ""

#: ../../appendix/faqs/general.rst:13
#: ../../appendix/faqs/general.rst:13
msgid "If you are installing a plugin called \"test\", there will be a test directory under mod. In that test directory there needs to be a start.php file: ``/mod/test/start.php`` and a manifest.xml file ``/mod/test/manifest.xml``."
msgstr ""

#: ../../appendix/faqs/general.rst:19
#: ../../appendix/faqs/general.rst:19
msgid "If these files do not exist, it could be caused by:"
msgstr ""

#: ../../appendix/faqs/general.rst:16
#: ../../appendix/faqs/general.rst:16
msgid "installing a plugin to the wrong directory"
msgstr ""

#: ../../appendix/faqs/general.rst:17
#: ../../appendix/faqs/general.rst:17
msgid "creating a directory under /mod that does not contain a plugin"
msgstr ""

#: ../../appendix/faqs/general.rst:18
#: ../../appendix/faqs/general.rst:18
msgid "a bad ftp transfer"
msgstr ""

#: ../../appendix/faqs/general.rst:19
#: ../../appendix/faqs/general.rst:19
msgid "unzipping a plugin into an extra directory (myplugin.zip unzips to ``myplugin/myplugin``)"
msgstr ""

#: ../../appendix/faqs/general.rst:21
#: ../../appendix/faqs/general.rst:21
msgid "If you are on a Unix-based host and the files exist in the correct directory, check the permissions. Elgg must have read access to the files and read + execute access on the directories."
msgstr ""

#: ../../appendix/faqs/general.rst:24
#: ../../appendix/faqs/general.rst:24
msgid "White Page (WSOD)"
msgstr ""

#: ../../appendix/faqs/general.rst:29
#: ../../appendix/faqs/general.rst:29
msgid "A blank, white page (often called a \"white screen of death\") means there is a PHP syntax error. There are a few possible causes of this:"
msgstr ""

#: ../../appendix/faqs/general.rst:27
#: ../../appendix/faqs/general.rst:27
msgid "corrupted file - try transfering the code again to your server"
msgstr ""

#: ../../appendix/faqs/general.rst:28
#: ../../appendix/faqs/general.rst:28
msgid "a call to a php module that was not loaded - this can happen after you install a plugin that requires a specific module."
msgstr ""

#: ../../appendix/faqs/general.rst:29
#: ../../appendix/faqs/general.rst:29
msgid "bad plugin - not all plugins have been written to the same quality so you should be careful which ones you install."
msgstr ""

#: ../../appendix/faqs/general.rst:31
#: ../../appendix/faqs/general.rst:31
msgid "To find where the error is occurring, change the .htaccess file to display errors to the browser. Set display_errors to 1 and load the same page again. You should see a PHP error in your browser. Change the setting back once you've resolved the problem."
msgstr ""

#: ../../appendix/faqs/general.rst:35
#: ../../appendix/faqs/general.rst:35
msgid "If you are using the Developer's Tools plugin, go to its settings page and make sure you have \"Display fatal PHP errors\" enabled."
msgstr ""

#: ../../appendix/faqs/general.rst:37
#: ../../appendix/faqs/general.rst:37
msgid "If the white screen is due to a bad plugin, remove the latest plugins that you have installed by deleting their directories and then reload the page."
msgstr ""

#: ../../appendix/faqs/general.rst:41
#: ../../appendix/faqs/general.rst:41
msgid "You can temporarily disable all plugins by creating an empty file at ``mod/disabled``. You can then disable the offending module via the administrator tools panel."
msgstr ""

#: ../../appendix/faqs/general.rst:43
#: ../../appendix/faqs/general.rst:43
msgid "If you are getting a WSOD when performing an action, like logging in or posting a blog, but there are no error messages, it's most likely caused by non-printable characters in plugin code. Check the plugin for white spaces/new lines characters after finishing php tag (``?>``) and remove them."
msgstr ""

#: ../../appendix/faqs/general.rst:46
#: ../../appendix/faqs/general.rst:46
msgid "Page not found"
msgstr ""

#: ../../appendix/faqs/general.rst:48
#: ../../appendix/faqs/general.rst:48
msgid "If you have recently installed your Elgg site, the most likely cause for a page not found error is that ``mod_rewrite`` is not setup correctly on your server. There is information in the :doc:`Install Troubleshooting </intro/install>` page on fixing this. The second most likely cause is that your site url in your database is incorrect."
msgstr ""

#: ../../appendix/faqs/general.rst:50
#: ../../appendix/faqs/general.rst:50
msgid "If you've been running your site for a while and suddenly start getting page not found errors, you need to ask yourself what has changed. Have you added any plugins? Did you change your server configuration?"
msgstr ""

#: ../../appendix/faqs/general.rst:52
#: ../../appendix/faqs/general.rst:52
msgid "To debug a page not found error:"
msgstr ""

#: ../../appendix/faqs/general.rst:54
#: ../../appendix/faqs/general.rst:54
msgid "Confirm that the link leading to the missing page is correct. If not, how is that link being generated?"
msgstr ""

#: ../../appendix/faqs/general.rst:55
#: ../../appendix/faqs/general.rst:55
msgid "Confirm that the ``.htaccess`` rewrite rules are being picked up."
msgstr ""

#: ../../appendix/faqs/general.rst:58
#: ../../appendix/faqs/general.rst:58
msgid "Login token mismatch"
msgstr ""

#: ../../appendix/faqs/general.rst:60
#: ../../appendix/faqs/general.rst:60
msgid "If you have to log in twice to your site and the error message after the first attempt says there was a token mismatch error, the URL in Elgg's settings does not match the URL used to access it. The most common cause for this is adding or removing the \"www\" when accessing the site. For example, www.elgg.org vs elgg.org. This causes a problem with session handling because of the way that web browsers save cookies."
msgstr ""

#: ../../appendix/faqs/general.rst:62
#: ../../appendix/faqs/general.rst:62
msgid "To fix this, you can add rewrite rules. To redirect from www.elgg.org to elgg.org in Apache, the rules might look like::"
msgstr ""

#: ../../appendix/faqs/general.rst:68
#: ../../appendix/faqs/general.rst:68
msgid "Redirecting from non-www to www could look like this::"
msgstr ""

#: ../../appendix/faqs/general.rst:73
#: ../../appendix/faqs/general.rst:73
msgid "If you don't know how to configure rewrite rules, ask your host for more information."
msgstr ""

#: ../../appendix/faqs/general.rst:76
#: ../../appendix/faqs/general.rst:76
msgid "Form is missing __token or __ts fields"
msgstr ""

#: ../../appendix/faqs/general.rst:78
#: ../../appendix/faqs/general.rst:78
msgid "All Elgg actions require a security token, and this error occurs when that token is missing. This is either a problem with your server configuration or with a 3rd party plugin."
msgstr ""

#: ../../appendix/faqs/general.rst:80
#: ../../appendix/faqs/general.rst:80
msgid "If you experience this on a new installation, make sure that your server is properly configured and your rewrite rules are correct. If you experience this on an upgrade, make sure you have updated your rewrite rules either in .htaccess (Apache) or in the server configuration."
msgstr ""

#: ../../appendix/faqs/general.rst:82
#: ../../appendix/faqs/general.rst:82
msgid "If you are experiencing this, disable all 3rd party plugins and try again. Very old plugins for Elgg don't use security tokens. If the problem goes away when plugins are disabled, it's due to a plugin that should be updated by its author."
msgstr ""

#: ../../appendix/faqs/general.rst:85
#: ../../appendix/faqs/general.rst:85
msgid "Maintenance mode"
msgstr ""

#: ../../appendix/faqs/general.rst:87
#: ../../appendix/faqs/general.rst:87
msgid "To take your site temporarily offline, go to Administration -> Utilities -> Maintenance Mode. Complete the form and hit save to disable your site for everyone except admin users."
msgstr ""

#: ../../appendix/faqs/general.rst:90
#: ../../appendix/faqs/general.rst:90
msgid "Missing email"
msgstr ""

#: ../../appendix/faqs/general.rst:92
#: ../../appendix/faqs/general.rst:92
msgid "If your users are reporting that validation emails are not showing up, have them check their spam folder. It is possible that the emails coming from your server are being marked as spam. This depends on many factors such as whether your hosting provider has a problem with spammers, how your PHP mail configuration is set up, what mail transport agent your server is using, or your host limiting the number of email that you can send in an hour."
msgstr ""

#: ../../appendix/faqs/general.rst:94
#: ../../appendix/faqs/general.rst:94
msgid "If no one gets email at all, it is quite likely your server is not configured properly for email. Your server needs a program to send email (called a Mail Transfer Agent - MTA) and PHP must be configured to use the MTA."
msgstr ""

#: ../../appendix/faqs/general.rst:96
#: ../../appendix/faqs/general.rst:96
msgid "To quickly check if PHP and an MTA are correctly configured, create a file on your server with the following content:"
msgstr ""

#: ../../appendix/faqs/general.rst:115
#: ../../appendix/faqs/general.rst:115
msgid "Be sure to replace \"your_email@your_host.com\" with your actual email address.  Take care to keep quotes around it!  When you access this page through your web browser, it will attempt to send a test email.  This test will let you know that PHP and your MTA are correctly configured.  If it fails--either you get an error or you never receive the email--you will need to do more investigating and possibly contact your service provider."
msgstr ""

#: ../../appendix/faqs/general.rst:117
#: ../../appendix/faqs/general.rst:117
msgid "Fully configuring an MTA and PHP's email functionality is beyond the scope of this FAQ and you should search the Internet for more resources on this. Some basic information on php parameters can be found on `PHP's site`__"
msgstr ""

#: ../../appendix/faqs/general.rst:123
#: ../../appendix/faqs/general.rst:123
msgid "Server logs"
msgstr ""

#: ../../appendix/faqs/general.rst:125
#: ../../appendix/faqs/general.rst:125
msgid "Most likely you are using Apache as your web server. Warnings and errors are written to a log by the web server and can be useful for debugging problems. You will commonly see two types of log files: access logs and error logs. Information from PHP and Elgg is written to the server error log."
msgstr ""

#: ../../appendix/faqs/general.rst:127
#: ../../appendix/faqs/general.rst:127
msgid "Linux -- The error log is probably in /var/log/httpd or /var/log/apache2."
msgstr ""

#: ../../appendix/faqs/general.rst:128
#: ../../appendix/faqs/general.rst:128
msgid "Windows - It is probably inside your Apache directory."
msgstr ""

#: ../../appendix/faqs/general.rst:129
#: ../../appendix/faqs/general.rst:129
msgid "Mac OS - The error log is probably in /var/log/apache2/error_log"
msgstr ""

#: ../../appendix/faqs/general.rst:131
#: ../../appendix/faqs/general.rst:131
msgid "If you are using shared hosting without ssh access, your hosting provider may provide a mechanism for obtaining access to your server logs. You will need to ask them about this."
msgstr ""

#: ../../appendix/faqs/general.rst:134
#: ../../appendix/faqs/general.rst:134
msgid "How does registration work?"
msgstr ""

#: ../../appendix/faqs/general.rst:136
#: ../../appendix/faqs/general.rst:136
msgid "With a default setup, this is how registration works:"
msgstr ""

#: ../../appendix/faqs/general.rst:138
#: ../../appendix/faqs/general.rst:138
msgid "User fills out registration form and submits it"
msgstr ""

#: ../../appendix/faqs/general.rst:139
#: ../../appendix/faqs/general.rst:139
msgid "User account is created and disabled until validated"
msgstr ""

#: ../../appendix/faqs/general.rst:140
#: ../../appendix/faqs/general.rst:140
msgid "Email is sent to user with a link to validate the account"
msgstr ""

#: ../../appendix/faqs/general.rst:141
#: ../../appendix/faqs/general.rst:141
msgid "When a user clicks on the link, the account is validated"
msgstr ""

#: ../../appendix/faqs/general.rst:142
#: ../../appendix/faqs/general.rst:142
msgid "The user can now log in"
msgstr ""

#: ../../appendix/faqs/general.rst:144
#: ../../appendix/faqs/general.rst:144
msgid "Failures during this process include the user entering an incorrect email address, the validation email being marked as spam, or a user never bothering to validate the account."
msgstr ""

#: ../../appendix/faqs/general.rst:147
#: ../../appendix/faqs/general.rst:147
msgid "User validation"
msgstr ""

#: ../../appendix/faqs/general.rst:149
#: ../../appendix/faqs/general.rst:149
msgid "By default, all users who self-register must validate their accounts through email. If a user has problems validating an account, you can validate users manually by going to Administration -> Users -> Unvalidated."
msgstr ""

#: ../../appendix/faqs/general.rst:152
#: ../../appendix/faqs/general.rst:152
msgid "You can remove this requirement by deactivating the User Validation by Email plugin."
msgstr ""

#: ../../appendix/faqs/general.rst:156
#: ../../appendix/faqs/general.rst:156
msgid "Removing validation has some consequences: There is no way to know that a user registered with a working email address, and it may leave you system open to spammers."
msgstr ""

#: ../../appendix/faqs/general.rst:159
#: ../../appendix/faqs/general.rst:159
msgid "Manually add user"
msgstr ""

#: ../../appendix/faqs/general.rst:161
#: ../../appendix/faqs/general.rst:161
msgid "To manually add a user, under the Administer controls go to Users. There you will see a link title \"Add new User\". After you fill out the information and submit the form, the new user will receive an email with username and password and a reminder to change the password."
msgstr ""

#: ../../appendix/faqs/general.rst:165
#: ../../appendix/faqs/general.rst:165
msgid "Elgg does not force the user to change the password."
msgstr ""

#: ../../appendix/faqs/general.rst:168
#: ../../appendix/faqs/general.rst:168
msgid "I'm making or just installed a new theme, but graphics or other elements aren't working"
msgstr ""

#: ../../appendix/faqs/general.rst:170
#: ../../appendix/faqs/general.rst:170
msgid "Make sure the theme is at the bottom of the plugin list."
msgstr ""

#: ../../appendix/faqs/general.rst:172
#: ../../appendix/faqs/general.rst:172
msgid "Clear your browser cache and reload the page. To lighten the load on the server, Elgg instructs the browser to rarely load the CSS file. A new theme will completely change the CSS file and a refresh should cause the browser to request the CSS file again."
msgstr ""

#: ../../appendix/faqs/general.rst:174
#: ../../appendix/faqs/general.rst:174
msgid "If you're building or modifying a theme, make sure you have disabled the simple and system caches. This can be done by enabling the Developer Tools plugin, then browsing to Administration -> Develop -> Settings. Once you're satisfied with the changes, enable the caches or performance will suffer."
msgstr ""

#: ../../appendix/faqs/general.rst:178
#: ../../appendix/faqs/general.rst:178
msgid "Changing profile fields"
msgstr ""

#: ../../appendix/faqs/general.rst:180
#: ../../appendix/faqs/general.rst:180
msgid "Within the Administration settings of Elgg is a page for replacing the default profile fields. Elgg by default gives the administrator two choices:"
msgstr ""

#: ../../appendix/faqs/general.rst:182
#: ../../appendix/faqs/general.rst:182
msgid "Use the default profile fields"
msgstr ""

#: ../../appendix/faqs/general.rst:183
#: ../../appendix/faqs/general.rst:183
msgid "Replace the default with a set of custom profile fields"
msgstr ""

#: ../../appendix/faqs/general.rst:185
#: ../../appendix/faqs/general.rst:185
msgid "You cannot add new profile fields to the default ones. Adding a new profile field through the replace profile fields option clears the default ones. Before letting in users, it is best to determine what profile fields you want, what field types they should be, and the order they should appear. You cannot change the field type or order or delete fields after they have been created without wiping the entire profile blank."
msgstr ""

#: ../../appendix/faqs/general.rst:187
#: ../../appendix/faqs/general.rst:187
msgid "More flexibility can be gained through plugins. There is at least two plugins on the community site that enable you to have more control over profile fields. The `Profile Manager`_ plugin has become quite popular in the Elgg community. It lets you add new profile fields whenever you want, change the order, group profile fields, and add them to registration."
msgstr ""

#: ../../appendix/faqs/general.rst:192
#: ../../appendix/faqs/general.rst:192
msgid "Changing registration"
msgstr ""

#: ../../appendix/faqs/general.rst:194
#: ../../appendix/faqs/general.rst:194
msgid "The registration process can be changed through a plugin. Everything about registration can be changed: the look and feel, different registration fields, additional validation of the fields, additional steps and so on. These types of changes require some basic knowledge of HTML, CSS, PHP."
msgstr ""

#: ../../appendix/faqs/general.rst:196
#: ../../appendix/faqs/general.rst:196
msgid "Another option is to use the `Profile Manager`_ plugin that lets you add fields to both user profiles and the registration form."
msgstr ""

#: ../../appendix/faqs/general.rst:199
#: ../../appendix/faqs/development.rst:36
#: ../../appendix/faqs/development.rst:36
#: ../../appendix/faqs/general.rst:199
msgid "Create the plugin skeleton"
msgstr ""

#: ../../appendix/faqs/general.rst:199
#: ../../appendix/faqs/development.rst:38
#: ../../appendix/faqs/development.rst:38
#: ../../appendix/faqs/general.rst:199
msgid ":doc:`/guides/plugins/plugin-skeleton`"
msgstr ""

#: ../../appendix/faqs/general.rst:202
#: ../../appendix/faqs/general.rst:202
msgid "Changing registration display"
msgstr ""

#: ../../appendix/faqs/general.rst:202
#: ../../appendix/faqs/general.rst:202
msgid "Override the ``account/forms/register`` view"
msgstr ""

#: ../../appendix/faqs/general.rst:205
#: ../../appendix/faqs/general.rst:205
msgid "Changing the registration action handler"
msgstr ""

#: ../../appendix/faqs/general.rst:205
#: ../../appendix/faqs/general.rst:205
msgid "You can write your own action to create the user's account"
msgstr ""

#: ../../appendix/faqs/general.rst:208
#: ../../appendix/faqs/general.rst:208
msgid "How do I change PHP settings using .htaccess?"
msgstr ""

#: ../../appendix/faqs/general.rst:210
#: ../../appendix/faqs/general.rst:210
msgid "You may want to change php settings in your ``.htaccess`` file. This is especially true if your hosting provider does not give you access to the server's ``php.ini`` file. The variables could be related to file upload size limits, security, session length, or any number of other php attributes. For examples of how to do this, see the `PHP documentation`_ on this."
msgstr ""

#: ../../appendix/faqs/general.rst:215
#: ../../appendix/faqs/general.rst:215
msgid "HTTPS login turned on accidently"
msgstr ""

#: ../../appendix/faqs/general.rst:217
#: ../../appendix/faqs/general.rst:217
msgid "If you have turned on HTTPS login but do not have SSL configured, you are now locked out of your Elgg install. To turn off this configuration parameter, you will need to edit your database. Use a tool like phpMyAdmin to view your database. Select the ``config`` table and delete the row that has the name ``https_login``."
msgstr ""

#: ../../appendix/faqs/general.rst:220
#: ../../appendix/faqs/general.rst:220
msgid "Using a test site"
msgstr ""

#: ../../appendix/faqs/general.rst:222
#: ../../appendix/faqs/general.rst:222
msgid "It is recommended to always try out new releases or new plugins on a test site before running them on a production site (a site with actual users). The easiest way to do this is to maintain a separate install of Elgg with dummy accounts. When testing changes it is important to use dummy accounts that are not admins to test what your users will see."
msgstr ""

#: ../../appendix/faqs/general.rst:224
#: ../../appendix/faqs/general.rst:224
msgid "A more realistic test is to mirror the content from your production site to your test site. Following the instructions for :doc:`duplicating a site </admin/duplicate-installation>`. Then make sure you prevent emails from being sent to your users. You could write a small plugin that redirects all email to your own account (be aware of plugins that include their own custom email sending code so you'll have to modify those plugins). After this is done you can view all of the content to make sure the upgrade or new plugin is functioning as desired and is not breaking anything. If this process sounds overwhelming, please stick with running a simple test site."
msgstr ""

#: ../../appendix/faqs/general.rst:227
#: ../../appendix/faqs/general.rst:227
msgid "500 - Internal Server Error"
msgstr ""

#: ../../appendix/faqs/general.rst:230
#: ../../appendix/faqs/general.rst:230
msgid "What is it?"
msgstr ""

#: ../../appendix/faqs/general.rst:232
#: ../../appendix/faqs/general.rst:232
msgid "A **500 - Internal Server Error** means the web server experienced a problem serving a request."
msgstr ""

#: ../../appendix/faqs/general.rst:236
#: ../../appendix/faqs/general.rst:236
msgid "`The Wikipedia page on HTTP status codes <https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#5xx_Server_Error>`_"
msgstr ""

#: ../../appendix/faqs/general.rst:239
#: ../../appendix/faqs/general.rst:239
msgid "Possible causes"
msgstr ""

#: ../../appendix/faqs/general.rst:242
#: ../../appendix/faqs/general.rst:242
msgid "Web server configuration"
msgstr ""

#: ../../appendix/faqs/general.rst:242
#: ../../appendix/faqs/general.rst:242
msgid "The most common cause for this is an incorrectly configured server. If you edited the ``.htaccess`` file and added something incorrect, Apache will send a 500 error."
msgstr ""

#: ../../appendix/faqs/general.rst:245
#: ../../appendix/faqs/general.rst:245
msgid "Permissions on files"
msgstr ""

#: ../../appendix/faqs/general.rst:245
#: ../../appendix/faqs/general.rst:245
msgid "It could also be a permissions problem on a file. Apache needs to be able to read Elgg's files. Using permissions 755 on directories and 644 on files will allow Apache to read the files."
msgstr ""

#: ../../appendix/faqs/general.rst:248
#: ../../appendix/faqs/general.rst:248
msgid "When I upload a photo or change my profile picture I get a white screen"
msgstr ""

#: ../../appendix/faqs/general.rst:250
#: ../../appendix/faqs/general.rst:250
msgid "Most likely you don't have the PHP GD library installed or configured properly. You may need assistance from the administrator of your server."
msgstr ""

#: ../../appendix/faqs/general.rst:253
#: ../../appendix/faqs/general.rst:253
msgid "CSS is missing"
msgstr ""

#: ../../appendix/faqs/general.rst:256
#: ../../appendix/faqs/general.rst:256
msgid "Wrong URL"
msgstr ""

#: ../../appendix/faqs/general.rst:258
#: ../../appendix/faqs/general.rst:258
msgid "Sometimes people install Elgg so that the base URL is ``localhost`` and then try to view the site using a hostname. In this case, the browser won't be able to load the CSS file. Try viewing the source of the web page and copying the link for the CSS file. Paste that into your browser. If you get a 404 error, it is likely this is your problem. You will need to change the base URL of your site."
msgstr ""

#: ../../appendix/faqs/general.rst:261
#: ../../appendix/faqs/general.rst:261
msgid "Syntax error"
msgstr ""

#: ../../appendix/faqs/general.rst:263
#: ../../appendix/faqs/general.rst:263
msgid "Elgg stores its CSS as PHP code to provide flexibility and power. If there is a syntax error, the CSS file served to the browser may be blank. Disabling non-bundled plugins is the recommended first step."
msgstr ""

#: ../../appendix/faqs/general.rst:266
#: ../../appendix/faqs/general.rst:266
msgid "Rewrite rules errors"
msgstr ""

#: ../../appendix/faqs/general.rst:268
#: ../../appendix/faqs/general.rst:268
msgid "A bad ``.htaccess`` file could also result in a 404 error when requesting the CSS file. This could happen when doing an upgrade and forgetting to also upgrade ``.htaccess``."
msgstr ""

#: ../../appendix/faqs/general.rst:271
#: ../../appendix/faqs/general.rst:271
msgid "Should I edit the database manually?"
msgstr ""

#: ../../appendix/faqs/general.rst:275
#: ../../appendix/faqs/general.rst:275
msgid "No, you should never manually edit the database!"
msgstr ""

#: ../../appendix/faqs/general.rst:278
#: ../../appendix/faqs/general.rst:278
msgid "Will editing the database manually break my site?"
msgstr ""

#: ../../appendix/faqs/general.rst:280
#: ../../appendix/faqs/general.rst:280
msgid "Yes."
msgstr ""

#: ../../appendix/faqs/general.rst:283
#: ../../appendix/faqs/general.rst:283
msgid "Can I add extra fields to tables in the database?"
msgstr ""

#: ../../appendix/faqs/general.rst:285
#: ../../appendix/faqs/general.rst:285
msgid "(AKA: I don't understand the Elgg :doc:`data model </design/database>` so I'm going to add columns. Will you help?)"
msgstr ""

#: ../../appendix/faqs/general.rst:287
#: ../../appendix/faqs/general.rst:287
msgid "No, this is a bad idea. Learn the :doc:`data model </design/database>` and you will see that unless it's a very specific and highly customized installation, you can do everything you need within Elgg's current data model."
msgstr ""

#: ../../appendix/faqs/general.rst:290
#: ../../appendix/faqs/general.rst:290
msgid "I want to remove users. Can't I just delete them from the elgg_users_entity table?"
msgstr ""

#: ../../appendix/faqs/general.rst:292
#: ../../appendix/faqs/general.rst:292
msgid "No, it will corrupt your database. Delete them through the site."
msgstr ""

#: ../../appendix/faqs/general.rst:295
#: ../../appendix/faqs/general.rst:295
msgid "I want to remove spam. Can't I just search and delete it from the elgg_objects_entity table?"
msgstr ""

#: ../../appendix/faqs/general.rst:297
#: ../../appendix/faqs/general.rst:297
msgid "No, it will corrupt your database. Delete it through the site."
msgstr ""

#: ../../appendix/faqs/general.rst:300
#: ../../appendix/faqs/general.rst:300
msgid "Someone on the community site told me to edit the database manually. Should I?"
msgstr ""

#: ../../appendix/faqs/general.rst:302
#: ../../appendix/faqs/general.rst:302
msgid "Who was it? Is it someone experienced with Elgg, like one of the core developers or a well-known plugin author? Did he or she give you clear and specific instructions on what to edit? If you don't know who it is, or if you can't understand or aren't comfortable following the instructions, do not edit the database manually."
msgstr ""

#: ../../appendix/faqs/general.rst:305
#: ../../appendix/faqs/general.rst:305
msgid "I know PHP and MySQL and have a legitimate reason to edit the database. Is it okay to manually edit the database?"
msgstr ""

#: ../../appendix/faqs/general.rst:307
#: ../../appendix/faqs/general.rst:307
msgid "Make sure you understand Elgg's :doc:`data model </design/database>` and schema first. Make a backup, edit carefully, then test copiously."
msgstr ""

#: ../../appendix/faqs/general.rst:310
#: ../../appendix/faqs/general.rst:310
msgid "Internet Explorer (IE) login problem"
msgstr ""

#: ../../appendix/faqs/general.rst:313
#: ../../appendix/faqs/general.rst:313
msgid "Canonical URL"
msgstr ""

#: ../../appendix/faqs/general.rst:315
#: ../../appendix/faqs/general.rst:315
msgid "IE does not like working with sites that use both http://example.org and http://www.example.org. It stores multiple cookies and this causes problems. Best to only use one base URL. For details on how to do this see Login token mismatch error."
msgstr ""

#: ../../appendix/faqs/general.rst:318
#: ../../appendix/faqs/general.rst:318
msgid "Chrome Frame"
msgstr ""

#: ../../appendix/faqs/general.rst:320
#: ../../appendix/faqs/general.rst:320
msgid "Using the chrome frame within IE can break the login process."
msgstr ""

#: ../../appendix/faqs/general.rst:323
#: ../../appendix/faqs/general.rst:323
msgid "Emails don't support non-Latin characters"
msgstr ""

#: ../../appendix/faqs/general.rst:325
#: ../../appendix/faqs/general.rst:325
msgid "In order to support non-Latin characters, (such as Cyrillic or Chinese) Elgg requires `multibyte string support`_ to be compiled into PHP."
msgstr ""

#: ../../appendix/faqs/general.rst:327
#: ../../appendix/faqs/general.rst:327
msgid "On many installs (e.g. Debian & Ubuntu) this is turned on by default. If it is not, you need to turn it on (or recompile PHP to include it). To check whether your server supports multibyte strings, check `phpinfo`_."
msgstr ""

#: ../../appendix/faqs/general.rst:333
#: ../../appendix/faqs/general.rst:333
msgid "Session length"
msgstr ""

#: ../../appendix/faqs/general.rst:335
#: ../../appendix/faqs/general.rst:335
msgid "Session length is controlled by your php configuration. You will first need to locate your ``php.ini`` file. In that file will be several session variables. A complete list and what they do can be found in the `php manual`_."
msgstr ""

#: ../../appendix/faqs/general.rst:340
#: ../../appendix/faqs/general.rst:340
msgid "File is missing an owner"
msgstr ""

#: ../../appendix/faqs/general.rst:342
#: ../../appendix/faqs/general.rst:342
msgid "There are three causes for this error. You could have an entity in your database that has an ``owner_guid`` of ``0``. This should be extremely rare and may only occur if your database/server crashes during a write operation."
msgstr ""

#: ../../appendix/faqs/general.rst:344
#: ../../appendix/faqs/general.rst:344
msgid "The second cause would be an entity where the owner no longer exists. This could occur if a plugin is turned off that was involved in the creation of the entity and then the owner is deleted but the delete operation failed (because the plugin is turned off). If you can figure out entity is causing this, look in your ``entities`` table and change the ``owner_guid`` to your own and then you can delete the entity through Elgg."
msgstr ""

#: ../../appendix/faqs/general.rst:348
#: ../../appendix/faqs/general.rst:348
msgid "Reed the section \"Should I edit the database manually?\". Be very carefull when editing the database directly. It can break your site. **Always** make a backup before doing this."
msgstr ""

#: ../../appendix/faqs/general.rst:350
#: ../../appendix/faqs/general.rst:350
msgid "The third cause is a user not having a username. This also indicates a database problem as this should not be possible. If it does occur, you could see this error when viewing a list of users (such as with the Members plugin). To fix, check your ``users_entity`` table for users without a username and if so, create a fake a username for that person. You should probably then delete the user through Elgg."
msgstr ""

#: ../../appendix/faqs/general.rst:353
#: ../../appendix/faqs/general.rst:353
msgid "Fixes"
msgstr ""

#: ../../appendix/faqs/general.rst:355
#: ../../appendix/faqs/general.rst:355
msgid "`Database Validator`_ plugin will check your database for these causes and provide an option to fix them. Be sure to backup the database before you try the fix option."
msgstr ""

#: ../../appendix/faqs/general.rst:360
#: ../../appendix/faqs/general.rst:360
msgid "No images"
msgstr ""

#: ../../appendix/faqs/general.rst:362
#: ../../appendix/faqs/general.rst:362
msgid "If profile images, group images, or other files have stopped working on your site it is likely due to a misconfiguration, especially if you have migrated to a new server."
msgstr ""

#: ../../appendix/faqs/general.rst:364
#: ../../appendix/faqs/general.rst:364
msgid "These are the most common misconfigurations that cause images and other files to stop working."
msgstr ""

#: ../../appendix/faqs/general.rst:367
#: ../../appendix/faqs/general.rst:367
msgid "Wrong path for data directory"
msgstr ""

#: ../../appendix/faqs/general.rst:369
#: ../../appendix/faqs/general.rst:369
msgid "Make sure the data directory's path is correct in the Site Administration admin area. It should have a trailing slash."
msgstr ""

#: ../../appendix/faqs/general.rst:372
#: ../../appendix/faqs/general.rst:372
msgid "Wrong permissions on the data directory"
msgstr ""

#: ../../appendix/faqs/general.rst:374
#: ../../appendix/faqs/general.rst:374
msgid "Check the permissions for the data directory. The data directory should be readable and writeable by the web server user."
msgstr ""

#: ../../appendix/faqs/general.rst:377
#: ../../appendix/faqs/general.rst:377
msgid "Different timezone"
msgstr ""

#: ../../appendix/faqs/general.rst:381
#: ../../appendix/faqs/general.rst:381
msgid "This only applies to Elgg versions before 1.9"
msgstr ""

#: ../../appendix/faqs/general.rst:383
#: ../../appendix/faqs/general.rst:383
msgid "If you migrated servers or upgraded PHP, check that PHP's timezone settings are the same between the old and the new. If you cannot or don't want to change the system-wide ``php.ini`` file, you can put the following at the top of ``engine/settings.php``:"
msgstr ""

#: ../../appendix/faqs/general.rst:389
#: ../../appendix/faqs/general.rst:389
msgid "Where ``MY_TIME_ZONE`` is a valid `PHP timezone`_."
msgstr ""

#: ../../appendix/faqs/general.rst:394
#: ../../appendix/faqs/general.rst:394
msgid "Migrated installation with new data directory location"
msgstr ""

#: ../../appendix/faqs/general.rst:396
#: ../../appendix/faqs/general.rst:396
msgid "If you migrated an installation and need to change your data directory path, be sure to update the SQL for the filestore location as documented in the :doc:`/admin/duplicate-installation` instructions."
msgstr ""

#: ../../appendix/faqs/general.rst:399
#: ../../appendix/faqs/general.rst:399
msgid "Deprecation warnings"
msgstr ""

#: ../../appendix/faqs/general.rst:401
#: ../../appendix/faqs/general.rst:401
msgid "If you are seeing many deprecation warnings that say things like"
msgstr ""

#: ../../appendix/faqs/general.rst:407
#: ../../appendix/faqs/general.rst:407
msgid "then you are using a plugin that was written for an older version of Elgg. This means the plugin is using functions that are scheduled to be removed in a future version of Elgg. You can ask the plugin developer if the plugin will be updated or you can update the plugin yourself. If neither of those are likely to happen, you should not use that plugin."
msgstr ""

#: ../../appendix/faqs/general.rst:410
#: ../../appendix/faqs/general.rst:410
msgid "Javascript not working"
msgstr ""

#: ../../appendix/faqs/general.rst:412
#: ../../appendix/faqs/general.rst:412
msgid "If the user hover menu stops working or you cannot dismiss system messages, that means JavaScript is broken on your site. This usually due to a plugin having bad JavaScript code. You should find the plugin causing the problem and disable it. You can do this be disabling non-bundled plugins one at a time until the problem goes away. Another approach is disabling all non-bundled plugins and then enabling them one by one until the problem occurs again."
msgstr ""

#: ../../appendix/faqs/general.rst:414
#: ../../appendix/faqs/general.rst:414
msgid "Most web browsers will give you a hint as to what is breaking the JavaScript code. They often have a console for JavaScript errors or an advanced mode for displaying errors. Once you see the error message, you may have an easier time locating the problem."
msgstr ""

#: ../../appendix/faqs/security.rst:2
#: ../../appendix/faqs/security.rst:2
msgid "Security"
msgstr ""

#: ../../appendix/faqs/security.rst:5
#: ../../appendix/faqs/security.rst:5
msgid "Is upgrade.php a security concern?"
msgstr ""

#: ../../appendix/faqs/security.rst:7
#: ../../appendix/faqs/security.rst:7
msgid "Upgrade.php is a file used to run code and database upgrades. It is in the root of the directory and doesn't require a logged in account to access. On a fully upgraded site, running the file will only reset the caches and exit, so this is not a security concern."
msgstr ""

#: ../../appendix/faqs/security.rst:9
#: ../../appendix/faqs/security.rst:9
msgid "If you are still concerned, you can either delete, move, or change permissions on the file until you need to upgrade."
msgstr ""

#: ../../appendix/faqs/security.rst:12
#: ../../appendix/faqs/security.rst:12
msgid "Should I delete install.php?"
msgstr ""

#: ../../appendix/faqs/security.rst:14
#: ../../appendix/faqs/security.rst:14
msgid "This file is used to install Elgg and doesn't need to be deleted. The file checks if Elgg is already installed and forwards the user to the front page if it is."
msgstr ""

#: ../../appendix/faqs/security.rst:17
#: ../../appendix/faqs/security.rst:17
msgid "Filtering"
msgstr ""

#: ../../appendix/faqs/security.rst:19
#: ../../appendix/faqs/security.rst:19
msgid "Filtering is used in Elgg to make `XSS`_ attacks more difficult. The purpose of the filtering is to remove Javascript and other dangerous input from users."
msgstr ""

#: ../../appendix/faqs/security.rst:21
#: ../../appendix/faqs/security.rst:21
msgid "Filtering is performed through the function ``filter_tags()``. This function takes in a string and returns a filtered string. It triggers a *validate*, *input* :ref:`plugin hook <design/events#plugin-hooks>`. By default Elgg comes with the htmLawed filtering code as a plugin. Developers can drop in any additional or replacement filtering code as a plugin."
msgstr ""

#: ../../appendix/faqs/security.rst:23
#: ../../appendix/faqs/security.rst:23
msgid "The ``filter_tags()`` function is called on any user input as long as the input is obtained through a call to ``get_input()``. If for some reason a developer did not want to perform the default filtering on some user input, the ``get_input()`` function has a parameter for turning off filtering."
msgstr ""

#: ../../appendix/faqs/development.rst:2
#: ../../appendix/faqs/development.rst:2
msgid "Development"
msgstr ""

#: ../../appendix/faqs/development.rst:5
#: ../../appendix/faqs/development.rst:5
msgid "What should I use to edit php code"
msgstr ""

#: ../../appendix/faqs/development.rst:7
#: ../../appendix/faqs/development.rst:7
msgid "There are two main options: text editor or `integrated development environment`_ (IDE)."
msgstr ""

#: ../../appendix/faqs/development.rst:10
#: ../../appendix/faqs/development.rst:10
msgid "Text Editor"
msgstr ""

#: ../../appendix/faqs/development.rst:12
#: ../../appendix/faqs/development.rst:12
msgid "If you are new to software development or do not have much experience with IDEs, using a text editor will get you up and running the quickest. At a minimum, you will want one that does syntax highlighting to make the code easier to read. If you think you might submit patches to the bug tracker, you will want to make sure that your text editor does not change line endings. If you are using Windows, `Notepad++`_ is a good choice. If you are on a Mac, TextWrangler_ is a popular choice. You could also give TextMate_ a try."
msgstr ""

#: ../../appendix/faqs/development.rst:15
#: ../../appendix/faqs/development.rst:15
msgid "Integrated Development Environment"
msgstr ""

#: ../../appendix/faqs/development.rst:17
#: ../../appendix/faqs/development.rst:17
msgid "An IDE does just what it's name implies: it includes a set of tools that you would normally use separately. Most IDEs will include source code control which will allow you to directly commit and update your code from your cvs repository. It may have an FTP client built into it to make the transfer of files to a remote server easier. It will have syntax checking to catch errors before you try to execute the code on a server."
msgstr ""

#: ../../appendix/faqs/development.rst:19
#: ../../appendix/faqs/development.rst:19
msgid "The two most popular free IDEs for PHP developers are Eclipse_ and NetBeans_. Eclipse has two different plugins for working with PHP code: PDT_ and PHPEclipse_."
msgstr ""

#: ../../appendix/faqs/development.rst:31
#: ../../appendix/faqs/development.rst:31
msgid "I don't like the wording of something in Elgg. How do I change it?"
msgstr ""

#: ../../appendix/faqs/development.rst:33
#: ../../appendix/faqs/development.rst:33
msgid "The best way to do this is with a plugin."
msgstr ""

#: ../../appendix/faqs/development.rst:41
#: ../../appendix/faqs/development.rst:41
msgid "Locate the string that you want to change"
msgstr ""

#: ../../appendix/faqs/development.rst:43
#: ../../appendix/faqs/development.rst:43
msgid "All the strings that a user sees should be in the ``/languages`` directory or in a plugin's languages directory (``/mod/<plugin name>/languages``). This is done so that it is easy to change what language Elgg uses. For more information on this see the developer documentation on :doc:`/guides/i18n` ."
msgstr ""

#: ../../appendix/faqs/development.rst:45
#: ../../appendix/faqs/development.rst:45
msgid "To find the string use ``grep`` or a text editor that provides searching through files to locate the string. (A good text editor for Windows is `Notepad++`_ ) Let's say we want to change the string \"Add friend\" to \"Make a new friend\". The ``grep`` command to find this string would be ``grep -r \"Add friend\" *``. Using `Notepad++`_ , you would use the \"Find in files\" command. You would search for the string, set the filter to ``*.php``, set the directory to the base directory of Elgg, and make sure it searches all subdirectories. You might want to set it to be case sensitive also."
msgstr ""

#: ../../appendix/faqs/development.rst:47
#: ../../appendix/faqs/development.rst:47
msgid "You should locate the string \"Add friend\" in ``/languages/en.php``. You should see something like this in the file:"
msgstr ""

#: ../../appendix/faqs/development.rst:53
#: ../../appendix/faqs/development.rst:53
msgid "This means every time Elgg sees ``friend:add`` it replaces it with \"Add friend\". We want to change the definition of ``friend:add``."
msgstr ""

#: ../../appendix/faqs/development.rst:56
#: ../../appendix/faqs/development.rst:56
msgid "Override the string"
msgstr ""

#: ../../appendix/faqs/development.rst:58
#: ../../appendix/faqs/development.rst:58
msgid "To override this definition, we will add a languages file to the plugin that we built in the first step."
msgstr ""

#: ../../appendix/faqs/development.rst:60
#: ../../appendix/faqs/development.rst:60
msgid "Create a new directory: ``/mod/<your plugin name>/languages``"
msgstr ""

#: ../../appendix/faqs/development.rst:61
#: ../../appendix/faqs/development.rst:61
msgid "Create a file in that directory called ``en.php``"
msgstr ""

#: ../../appendix/faqs/development.rst:62
#: ../../appendix/faqs/development.rst:62
msgid "Add these lines to that file"
msgstr ""

#: ../../appendix/faqs/development.rst:72
#: ../../appendix/faqs/development.rst:72
msgid "Make sure that you do not have any spaces or newlines before the ``<?php``."
msgstr ""

#: ../../appendix/faqs/development.rst:74
#: ../../appendix/faqs/development.rst:74
msgid "You're done now and should be able to enable the plugin and see the change. If you are override the language of a plugin, make sure your plugin is loaded after the one you are trying to modify. The loading order is determined in the Tools Administration page of the admin section. As you find more things that you'd like to change, you can keep adding them to this plugin."
msgstr ""

#: ../../appendix/faqs/development.rst:77
#: ../../appendix/faqs/development.rst:77
msgid "How do I find the code that does x?"
msgstr ""

#: ../../appendix/faqs/development.rst:79
#: ../../appendix/faqs/development.rst:79
msgid "The best way to find the code that does something that you would like to change is to use ``grep`` or a similar search tool. If you do not have ``grep`` as a part of your operating system, you will want to install a grep tool or use a text-editor/IDE that has good searching in files. `Notepad++`_ is a good choice for Windows users. `Eclipse`_ with PHP and `NetBeans`_ are good choices for any platform."
msgstr ""

#: ../../appendix/faqs/development.rst:82
#: ../../appendix/faqs/development.rst:82
msgid "String Example"
msgstr ""

#: ../../appendix/faqs/development.rst:84
#: ../../appendix/faqs/development.rst:84
msgid "Let's say that you want to find where the *Log In* box code is located. A string from the *Log In* box that should be fairly unique is ``Remember me``. ``Grep`` for that string. You will find that it is only used in the ``en.php`` file in the ``/languages`` directory. There it is used to define the :doc:`/guides/i18n` string ``user:persistent``. ``Grep`` for that string now. You will find it in two places: the same ``en.php`` language file and in ``/views/default/forms/login.php``. The latter defines the html code that makes up the *Log In* box."
msgstr ""

#: ../../appendix/faqs/development.rst:87
#: ../../appendix/faqs/development.rst:87
msgid "Action Example"
msgstr ""

#: ../../appendix/faqs/development.rst:89
#: ../../appendix/faqs/development.rst:89
msgid "Let's say that you want to find the code that is run when a user clicks on the *Save* button when arranging widgets on a profile page. View the Profile page for a test user. Use Firebug to drill down through the html of the page until you come to the action of the edit widgets form. You'll see the url from the base is ``action/widgets/move``."
msgstr ""

#: ../../appendix/faqs/development.rst:91
#: ../../appendix/faqs/development.rst:91
msgid "``Grep`` on ``widgets/move`` and two files are returned. One is the JavaScript code for the widgets : ``/js/lib/ui.widgets.js``. The other one, ``/engine/lib/widgets.php``, is where the action is registered using ``elgg_register_action('widgets/reorder')``. You may not be familiar with that function in which case, you should look it up at the API reference. Do a search on the function and it returns the documentation on the function. This tells you that the action is in the default location since a file location was not specified. The default location for actions is ``/actions`` so you will find the file at ``/actions/widgets/move.php``."
msgstr ""

#: ../../appendix/faqs/development.rst:94
#: ../../appendix/faqs/development.rst:94
msgid "Debug mode"
msgstr ""

#: ../../appendix/faqs/development.rst:96
#: ../../appendix/faqs/development.rst:96
msgid "During the installation process you might have noticed a checkbox that controlled whether debug mode was turned on or off. This setting can also be changed on the Site Administration page. Debug mode writes a lot of extra data to your php log. For example, when running in this mode every query to the database is written to your logs. It may be useful for debugging a problem though it can produce an overwhelming amount of data that may not be related to the problem at all. You may want to experiment with this mode to understand what it does, but make sure you run Elgg in normal mode on a production server."
msgstr ""

#: ../../appendix/faqs/development.rst:100
#: ../../appendix/faqs/development.rst:100
msgid "Because of the amount of data being logged, don't enable this on a production server as it can fill up the log files really quick."
msgstr ""

#: ../../appendix/faqs/development.rst:103
#: ../../appendix/faqs/development.rst:103
msgid "What goes into the log in debug mode?"
msgstr ""

#: ../../appendix/faqs/development.rst:105
#: ../../appendix/faqs/development.rst:105
msgid "All database queries"
msgstr ""

#: ../../appendix/faqs/development.rst:106
#: ../../appendix/faqs/development.rst:106
msgid "Database query profiling"
msgstr ""

#: ../../appendix/faqs/development.rst:107
#: ../../appendix/faqs/development.rst:107
msgid "Page generation time"
msgstr ""

#: ../../appendix/faqs/development.rst:108
#: ../../appendix/faqs/development.rst:108
msgid "Number of queries per page"
msgstr ""

#: ../../appendix/faqs/development.rst:109
#: ../../appendix/faqs/development.rst:109
msgid "List of plugin language files"
msgstr ""

#: ../../appendix/faqs/development.rst:110
#: ../../appendix/faqs/development.rst:110
msgid "Additional errors/warnings compared to normal mode (it's very rare for these types of errors to be related to any problem that you might be having)"
msgstr ""

#: ../../appendix/faqs/development.rst:113
#: ../../appendix/faqs/development.rst:113
msgid "What does the data look like?"
msgstr ""

#: ../../appendix/faqs/development.rst:145
#: ../../appendix/faqs/development.rst:145
msgid "What events are triggered on every page load?"
msgstr ""

#: ../../appendix/faqs/development.rst:147
#: ../../appendix/faqs/development.rst:147
msgid "There are 5 :doc:`Elgg events </design/events>` that are triggered on every page load:"
msgstr ""

#: ../../appendix/faqs/development.rst:149
#: ../../appendix/faqs/development.rst:149
msgid "boot, system"
msgstr ""

#: ../../appendix/faqs/development.rst:150
#: ../../appendix/faqs/development.rst:150
msgid "plugins_boot, system"
msgstr ""

#: ../../appendix/faqs/development.rst:151
#: ../../appendix/faqs/development.rst:151
msgid "init, system"
msgstr ""

#: ../../appendix/faqs/development.rst:152
#: ../../appendix/faqs/development.rst:152
msgid "pagesetup, system"
msgstr ""

#: ../../appendix/faqs/development.rst:153
#: ../../appendix/faqs/development.rst:153
msgid "shutdown, system"
msgstr ""

#: ../../appendix/faqs/development.rst:155
#: ../../appendix/faqs/development.rst:155
msgid "The *boot*, *system* event is triggered before the plugins get loaded. There does not appear to be any difference between the timing of the next two events: *plugins_boot*, *system* and *init*, *system* so plugins tend to use *init*, *system*. This event is triggered just after the plugins are loaded near the end of the boot script (``/engine/start.php``). The *pagesetup*, *system* event is thrown the first time ``elgg_view()`` is called. Some pages like the default ``index.php`` do not call ``elgg_view()`` so it is not triggered for them. The *shutdown*, *system* event is triggered after the page has been sent to the requester and is handled through the PHP function ``register_shutdown_function()``."
msgstr ""

#: ../../appendix/faqs/development.rst:157
#: ../../appendix/faqs/development.rst:157
msgid "There are :doc:`other events </guides/events-list>` that are triggered by the Elgg core but they happen occasionally (such as when a user logs in)."
msgstr ""

#: ../../appendix/faqs/development.rst:160
#: ../../appendix/faqs/development.rst:160
msgid "What variables are reserved by Elgg?"
msgstr ""

#: ../../appendix/faqs/development.rst:162
#: ../../appendix/faqs/development.rst:162
msgid "``$CONFIG``"
msgstr ""

#: ../../appendix/faqs/development.rst:163
#: ../../appendix/faqs/development.rst:163
msgid "``$vars``"
msgstr ""

#: ../../appendix/faqs/development.rst:164
#: ../../appendix/faqs/development.rst:164
msgid "``$autofeed``"
msgstr ""

#: ../../appendix/faqs/development.rst:165
#: ../../appendix/faqs/development.rst:165
msgid "``$_GET['action']`` / ``$_POST['action']``"
msgstr ""

#: ../../appendix/faqs/development.rst:166
#: ../../appendix/faqs/development.rst:166
msgid "``$viewtype``"
msgstr ""

#: ../../appendix/faqs/development.rst:169
#: ../../appendix/faqs/development.rst:169
msgid "Copy a plugin"
msgstr ""

#: ../../appendix/faqs/development.rst:171
#: ../../appendix/faqs/development.rst:171
msgid "There are many questions asked about how to copy a plugin. Let's say you want to copy the ``blog`` plugin in order to run one plugin called ``blog`` and another called ``poetry``. This is not difficult but it does require a lot of work. You would need to"
msgstr ""

#: ../../appendix/faqs/development.rst:173
#: ../../appendix/faqs/development.rst:173
msgid "change the directory name"
msgstr ""

#: ../../appendix/faqs/development.rst:174
#: ../../appendix/faqs/development.rst:174
msgid "change the names of every function (having two functions causes PHP to crash)"
msgstr ""

#: ../../appendix/faqs/development.rst:175
#: ../../appendix/faqs/development.rst:175
msgid "change the name of every view (so as not to override the views on the original plugin)"
msgstr ""

#: ../../appendix/faqs/development.rst:176
#: ../../appendix/faqs/development.rst:176
msgid "change any data model subtypes"
msgstr ""

#: ../../appendix/faqs/development.rst:177
#: ../../appendix/faqs/development.rst:177
msgid "change the language file"
msgstr ""

#: ../../appendix/faqs/development.rst:178
#: ../../appendix/faqs/development.rst:178
msgid "change anything else that was specific to the original plugin"
msgstr ""

#: ../../appendix/faqs/development.rst:182
#: ../../appendix/faqs/development.rst:182
msgid "If you are trying to clone the ``groups`` plugin, you will have the additional difficulty that the group plugin does not set a subtype."
msgstr ""

#: ../../appendix/history.rst:2
msgid "History"
msgstr ""

#: ../../appendix/history.rst:4
msgid "The name comes from `a town in Switzerland`__. It also means \"elk\" or \"moose\" in Danish."
msgstr ""

#: ../../appendix/history.rst:8
msgid "Elgg's initial funding was by a company called Curverider Ltd, which was started by David Tosh and Ben Werdmuller. In 2010, Curverider was acquired by Thematic Networks and control of the open-source project was turned over to `The Elgg Foundation`_. Today, Elgg is a community-driven open source project and has a variety of contributors and supporters."
msgstr ""

#: ../../appendix/index.rst:2
msgid "Appendix"
msgstr ""

#: ../../appendix/index.rst:4
msgid "Miscellaneous information about the project."
msgstr ""

#: ../../appendix/releases.rst:2
msgid "Release Policy"
msgstr ""

#: ../../appendix/releases.rst:4
msgid "What to expect when upgrading Elgg."
msgstr ""

#: ../../appendix/releases.rst:6
msgid "In general, we adhere to `semantic versioning`_."
msgstr ""

#: ../../appendix/releases.rst:10
msgid "Follow the blog to `stay up to date on the latest releases`__."
msgstr ""

#: ../../appendix/releases.rst:15
msgid "Bugfix Releases (1.9.x)"
msgstr ""

#: ../../appendix/releases.rst:16
msgid "Every few weeks."
msgstr ""

#: ../../appendix/releases.rst:18
msgid "Bugfix releases are made regularly to make sure Elgg stays stable, secure, and bug-free. The higher the third digit, the more tested and stable the release is. Since bugfix release focus on fixing bugs and not making major changes, themes and plugins should work from bugfix release to bugfix release."
msgstr ""

#: ../../appendix/releases.rst:25
msgid "Feature Releases (1.x.0)"
msgstr ""

#: ../../appendix/releases.rst:26
msgid "Every few months."
msgstr ""

#: ../../appendix/releases.rst:28
msgid "New features are introduced in Elgg every few months in minor new feature releases. These versions are identified by the second digit (1.**8**.0). These releases aren't as mature as bugfix release, but are considered stable and useable. Though these releases try to be backward compatible, features are added, unused code removed, and overall improvements are made, so plugins and themes might need to be updated to make use of the new and improved features."
msgstr ""

#: ../../appendix/releases.rst:37
msgid "Major Releases (x.0.0)"
msgstr ""

#: ../../appendix/releases.rst:38
msgid "Every few years."
msgstr ""

#: ../../appendix/releases.rst:40
msgid "Elgg, as all software, inevitably undergoes serious changes and a major new feature release is made. These releases are opportunities for the core team to make dramatic improvements to the underlying platform. Themes and plugins from older versions are not expected to work without modification on different major releases."
msgstr ""

#: ../../appendix/releases.rst:46
msgid "Release Candidates/Betas"
msgstr ""

#: ../../appendix/releases.rst:47
msgid "Before feature releases and major releases, the core team will typically offer a release candidate or beta. These are meant for testing only and should not be considered production quality. The core team makes these releases available to get some real-world testing and feedback on the release. That said, the API in release candidates is considered stable, so once a release candidate is made available, you should feel comfortable writing plugins against any new APIs."
msgstr ""

#: ../../appendix/roadmap.rst:2
msgid "Roadmap"
msgstr ""

#: ../../appendix/roadmap.rst:4
msgid "What direction is the project going? What exciting new features are coming soon?"
msgstr ""

#: ../../appendix/roadmap.rst:6
msgid "We do not publish detailed roadmaps, but it’s possible to get a sense for our general direction by utilizing the following resources:"
msgstr ""

#: ../../appendix/roadmap.rst:9
msgid "Our `feedback and planning group`_ is used to host early discussion about what will be worked on next."
msgstr ""

#: ../../appendix/roadmap.rst:10
msgid "Our `Github milestones`_ represent a general direction for the future releases of Elgg. This is the closest thing to a traditional roadmap that we have."
msgstr ""

#: ../../appendix/roadmap.rst:12
msgid "`Github pull requests`_ will give you a good idea of what’s currently being developed, but nothing is sure until the PR is actually checked in."
msgstr ""

#: ../../appendix/roadmap.rst:14
msgid "We use the `developer blog`_ to post announcements of features that have recently been checked in to our development branch, which gives the surest indication of what features will be available in the next release."
msgstr ""

#: ../../appendix/roadmap.rst:24
msgid "Values"
msgstr ""

#: ../../appendix/roadmap.rst:26
msgid "We have several overarching goals/values that affect the direction of Elgg. Enhancements generally must promote these values in order to be accepted."
msgstr ""

#: ../../appendix/roadmap.rst:30
msgid "Accessibility"
msgstr ""

#: ../../appendix/roadmap.rst:32
msgid "Elgg-based sites should be usable by anyone anywhere. That means we'll always strive to make Elgg:"
msgstr ""

#: ../../appendix/roadmap.rst:34
msgid "Device-agnostic -- mobile, tablet, desktop, etc. friendly"
msgstr ""

#: ../../appendix/roadmap.rst:35
msgid "Language-agnostic -- i18n, RTL, etc."
msgstr ""

#: ../../appendix/roadmap.rst:36
msgid "Capability-agnostic -- touch, keyboard, screen-reader friendly"
msgstr ""

#: ../../appendix/roadmap.rst:39
msgid "Testability"
msgstr ""

#: ../../appendix/roadmap.rst:41
msgid "We want to **make manual testing unnecessary** for core developers, plugin authors, and site administrators by promoting and enabling fast, automated testing at every level of the Elgg stack."
msgstr ""

#: ../../appendix/roadmap.rst:44
msgid "We think APIs are broken if they require plugin authors to write untestable code. We know there are a lot of violations of this principle in core currently and are working to fix it."
msgstr ""

#: ../../appendix/roadmap.rst:47
msgid "We look forward to a world where the core developers do not need to do any manual testing to verify the correctness of code contributed to Elgg. Similarly, we envision a world where site administrators can upgrade and install new plugins with confidence that everything works well together."
msgstr ""

#: ../../appendix/roadmap.rst:51
msgid "TODO: other goals/values?"
msgstr ""

#: ../../appendix/roadmap.rst:54
msgid "FAQ"
msgstr ""

#: ../../appendix/roadmap.rst:57
msgid "When will feature X be implemented?"
msgstr ""

#: ../../appendix/roadmap.rst:58
msgid "We cannot promise when features will get implemented because new features are checked into Elgg only when someone is motivated enough to implement the feature and submit a pull request. The best we can do is tell you to look out for what features existing developers have expressed interest in working on."
msgstr ""

#: ../../appendix/roadmap.rst:64
msgid "The best way to ensure a feature gets implemented is to discuss it with the core team and implement it yourself. See our :doc:`/contribute/index` guide if you're interested. We love new contributors!"
msgstr ""

#: ../../appendix/roadmap.rst:67
msgid "Do not rely on future enhancements if you're on the fence as to whether to use Elgg. Evaluate it given the current feature set. Upcoming features will almost certainly not materialize within your timeline."
msgstr ""

#: ../../appendix/roadmap.rst:72
msgid "When is version X.Y.Z going to be released?"
msgstr ""

#: ../../appendix/roadmap.rst:73
msgid "The next version will be released when the core team feels it's ready and has time to cut the release. http://github.com/Elgg/Elgg/issues/milestones will give you some rough ideas of timeline."
msgstr ""

#: ../../appendix/support.rst:2
msgid "Support policy"
msgstr ""

#: ../../appendix/support.rst:6
msgid "As of Elgg 1.9, each minor release gets:"
msgstr ""

#: ../../appendix/support.rst:5
msgid "Normal bugfixes every 2 weeks for 3 months, at which point the next minor release candidate is made available."
msgstr ""

#: ../../appendix/support.rst:6
msgid "Security and critical (i.e. regression) bug fixes for 1 year from the date of the next stable minor release. These will be released on an as-needed basis."
msgstr ""

#: ../../appendix/support.rst:10
msgid ":doc:`releases`"
msgstr ""

#: ../../appendix/support.rst:12
msgid "Below is a table outlining the specifics for each release:"
msgstr ""

#: ../../appendix/support.rst:15
msgid "Version"
msgstr ""

#: ../../appendix/support.rst:15
msgid "First stable release"
msgstr ""

#: ../../appendix/support.rst:15
msgid "Bug fixes through"
msgstr ""

#: ../../appendix/support.rst:15
msgid "Security fixes through"
msgstr ""

#: ../../appendix/support.rst:17
msgid "1.8"
msgstr ""

#: ../../appendix/support.rst:17
msgid "September 2011"
msgstr ""

#: ../../appendix/support.rst:17
msgid "August 2014"
msgstr ""

#: ../../appendix/support.rst:17
msgid "September 2015"
msgstr ""

#: ../../appendix/support.rst:19
msgid "1.9"
msgstr ""

#: ../../appendix/support.rst:19
msgid "September 2014"
msgstr ""

#: ../../appendix/support.rst:19
#: ../../appendix/support.rst:21
msgid "January 2015"
msgstr ""

#: ../../appendix/support.rst:19
msgid "January 2016"
msgstr ""

#: ../../appendix/support.rst:21
msgid "1.10"
msgstr ""

#: ../../appendix/support.rst:21
#: ../../appendix/support.rst:23
msgid "April 2015"
msgstr ""

#: ../../appendix/support.rst:21
msgid "April 2016"
msgstr ""

#: ../../appendix/support.rst:23
msgid "1.11"
msgstr ""

#: ../../appendix/support.rst:23
msgid "July 2015"
msgstr ""

#: ../../appendix/support.rst:23
msgid "July 2016"
msgstr ""

#: ../../appendix/support.rst:26
msgid "We don't have a support policy for major releases (x.0.0) yet because we've never done one."
msgstr ""