Исходный текст | Переводы |
---|---|
This text is displayed at the picture upload form in addition to the default guidelines. It's useful for helping or instructing your users. | Бу матн стандарт хабарларга қўшимча қилиб юклаш шаклида кўринади. Фойдаланувчилар ёрдами ёки йўл-йўриқлар учун фойдаланиш мумкин. |
The user module allows users to register, login, and log out. Users benefit from being able to sign on because it associates content they create with their account and allows various permissions to be set for their roles. The user module supports user roles which can setup fine grained permissions allowing each role to do only what the administrator wants them to. Each user is assigned to one or more roles. By default there are two roles <em>anonymous</em> - a user who has not logged in, and <em>authenticated</em> a user who has signed up and who has been authorized. | |
Users can use their own name or handle and can fine tune some personal configuration settings through their individual my account page. Registered users need to authenticate by supplying either a local username and password, or a remote username and password such as DelphiForums ID, or one from a Drupal powered website. A visitor accessing your website is assigned an unique ID, the so-called session ID, which is stored in a cookie. For security's sake, the cookie does not contain personal information but acts as a key to retrieve the information stored on your server. | |
For more information please read the configuration and customization handbook <a href="@user">User page</a>. | |
Drupal allows users to register, login, log out, maintain user profiles, etc. Users of the site may not use their own names to post content until they have signed up for a user account. | Drupal фойдаланувчиларга руйхатга ёзилишга, сайтга киришга, чиқишга, фойдаланувчиларнинг профилларини созлашга ва ҳ. имконият беради. Фойдаланувчилар сайтда материалларини жойлаштираётганда қайд ёзувини олмагунларигача ўз исмларидан фойдаланишлари мумкин эмас. |
This web page allows the administrators to register new users by hand. Note that you cannot have a user where either the e-mail address or the username match another user in the system. | |
Set up username and e-mail address access rules for new <em>and</em> existing accounts (currently logged in accounts will not be logged out). If a username or e-mail address for an account matches any deny rule, but not an allow rule, then the account will not be allowed to be created or to log in. A host rule is effective for every page view, not just registrations. | На этой странице вы можете установить правила для логина и почты новых и существующих аккаунтов. Если логин или почта совпадут с запрещающим правилом, то такой аккаунт нельзя будет зарегистрировать или войти в него, если он уже зарегистрирован. Правила касающиеся хостов действуют при просмотре страниц (но не при регистрации). |
Permissions let you control what users can do on your site. Each user role (defined on the <a href="@role">user roles page</a>) has its own set of permissions. For example, you could give users classified as "Administrators" permission to "administer nodes" but deny this power to ordinary, "authenticated" users. You can use permissions to reveal new features to privileged users (those with subscriptions, for example). Permissions also allow trusted users to share the administrative burden of running a busy site. | Ҳуқуқлар сайтингиздаги фойдаланувчиларнинг харакатларини назорат қилишга имконият беради. Ҳар бир фойдаланувчилик (<a href="@role">фойдаланувчилик роллари саҳифасида</a> белгиланган) роли ҳуқуқларнинг ўз тўпламига эга. Масалан, “Администраторлар” сифатида белгиланган фойдаланувчиларга “администратор материаллари” дан фойдалана олиш ҳуқуқини беришингиз мумкин, лекин оддий “руйхатга олинган” фойдаланувчиларга бу имкониятни тақиқлашингиз мумкин. Сиз ҳуқуқлардан имтиёзли фойдаланувчиларга янги имкониятларни (масалан, обуна бўлиш) тақдим этганда фойдаланишинигиз мумкин. Ҳуқуқлар фаол ишлайдиган сайтдаги административ ишнинг бир қисмини ишончли фойдаланувчиларга юклашга ҳам имконият беради. |
<p>Roles allow you to fine tune the security and administration of Drupal. A role defines a group of users that have certain privileges as defined in <a href="@permissions">user permissions</a>. Examples of roles include: anonymous user, authenticated user, moderator, administrator and so on. In this area you will define the <em>role names</em> of the various roles. To delete a role choose "edit".</p><p>By default, Drupal comes with two user roles:</p> ![]() <ul> ![]() <li>Anonymous user: this role is used for users that don't have a user account or that are not authenticated.</li> ![]() <li>Authenticated user: this role is automatically granted to all logged in users.</li> ![]() </ul> | <p>Роллар Drupal нинг ҳавфсизлигини ва маъмурий ишларни созлашга имконият беради. Ролларни, <a href="%permissions">правами доступа</a> билан белгиланадиган айрим имтиёзларга эга бўлган фойдаланувчилар гуруҳи томонидан белгилайди. Роллар мисоли: аноним фойдаланувчи, рўйхатга олингин фойдаланувчи, модератор, администратор ва ҳ. Ушбу саҳифада <em>ролларнинг номини</em> беришингиз мумкин. Ролни учириш учун "ўзгартириш"ни танланг.</p><p>Сукут бўйича Drupal икки ролни ўз ичига олади:</p>
![]() <ul> ![]() <li>Аноним фойдаланувчи (anonymous user): бу роль тизимда рўйхатига олинмаган ёки ичига кирмаган фойдаланувчилар учун фойдаланилади.</li> ![]() <li>Рўйхатга олинган фойдаланувчи (authenticated user): бу роль сайтга ўз номи ва пароли билан кирган барча фойдаланувчилар учун автоматик ҳолда юклатилади.</li> ![]() </ul> |
Enter a simple pattern ("*" may be used as a wildcard match) to search for a username. For example, one may search for "br" and Drupal might return "brian", "brad", and "brenda". |