summaryrefslogtreecommitdiff
path: root/modules/user.module
diff options
context:
space:
mode:
authorDries Buytaert <dries@buytaert.net>2005-07-19 17:57:55 +0000
committerDries Buytaert <dries@buytaert.net>2005-07-19 17:57:55 +0000
commit7ee24ccfe4b3c59fadfa9a4920bf374f40ed525f (patch)
tree340b965144e036aeac99daff0d34aa844140775c /modules/user.module
parent13954f90dde57a05aa54e0b269f7399f6d767c6e (diff)
downloadbrdo-7ee24ccfe4b3c59fadfa9a4920bf374f40ed525f.tar.gz
brdo-7ee24ccfe4b3c59fadfa9a4920bf374f40ed525f.tar.bz2
- Patch #27062 by nysus: improved the help text of the 'access control' page.
Generally improves readability; gets rid of technical jargon; provides concrete example; provides suggestions for how permissions can be used.
Diffstat (limited to 'modules/user.module')
-rw-r--r--modules/user.module2
1 files changed, 1 insertions, 1 deletions
diff --git a/modules/user.module b/modules/user.module
index 8ad3b82d8..b0af8050a 100644
--- a/modules/user.module
+++ b/modules/user.module
@@ -1779,7 +1779,7 @@ function user_help($section) {
case strstr($section, 'admin/access/rules'):
return t('<p>Set up username and e-mail address access rules for new accounts. If a username or email address for a new account matches any deny rule, but not an allow rule, then the new account will not be allowed to be created. A host rule is effective for every page view, not just registrations.</p>');
case 'admin/access':
- return t('<p>In this area you will define the permissions for each user role (role names are defined on the <a href="%role">user roles page</a>). Each permission describes a fine-grained logical operation, such as being able to access the administration pages, or adding/modifying a user account. You could say a permission represents access granted to a user to perform a set of operations.</p>', array('%role' => url('admin/access/roles')));
+ return t('<p>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.</p>', array('%role' => url('admin/access/roles')));
case 'admin/access/roles':
return t('<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>