Login
Username:

Password:

Remember me



Lost Password?

Register now!
Main Menu
Site Info
Webmasters
admin
admin

Who's Online
4 user(s) are online (2 user(s) are browsing XOOPS Docman)

Members: 0
Guests: 4

more...

2.8. Groups

2.8.1. Overview

XOOPS provides a core system of user access rights through the “Groups” settings. This allows the site administrator to control and filter access on at least 3 different user levels. All modules and their associated blocks must have their settings for visibility, rights and access correctly defined in order to achieve correct display and function on the website. Put simply, if you don’t grant these rights for a block to every available group, it won’t be visible on the page

The three default user access groups are as follows:

  • Anonymous users

  • Registered users

  • Webmasters (site administrators)

You can change the name of these default groups, but, you cannot delete them. Other user groups can also be set and defined as discussed later.

Let’s explain the meaning of each default groups. Someone who visits your site is an “Anonymous User”. If a visitor is registered AND logged in to your site, he will be recognized as a “Registered User”. The “Administrators” group automatically contains the primary user you created during the installation.

In a typical web setup we may set group permissions as follows:

  • Anonymous users:” Anonymous users may be allowed to view certain content as displayed by a particular module, or groups of modules. When anonymous users visit your site they will automatically see a default level of content for this group without any action on their part.

  • Registered users:” Registered users of the site can be granted rights to view and interact with other modules not available to the anonymous group. On initial site visit, assuming there is no auto-login function, they see the default content like any other visitor. However, when they login with their correct user details, the page will reload to include any links, menus and module content accessible to the registered group. The site administrator can design a site to display totally different module content, or simply additional module content to registered users.

  • Webmasters” As the creator of the XOOPS site the Webmaster or site administrator has complete and overall rights of access and administration. However, it is possible to promote any registered user to Webmaster status and share your privileges. It is safer to create a custom group and grant module and administration access for selected modules if you wish to allow others to administrate areas of the site.

2.8.2. The different sets of rights

Go to System admin->groups->Edit Groups page.

The “Edit groups” page begins with a section called “Edit Groups” (see Figure 2.7, “Edit Groups”). This allows you to select a specific group to work with and modify. Initially 3 default groups already exist, as described above.

Select a group from this list and click ‘modify’.

Edit Groups

Figure 2.7. Edit Groups

The modify group page is returned (see Figure 2.8, “Modify Groups”). You can now change the name of this group and give a meaningful description in the form boxes provided.

Looking further down the page you will see 4 sections, which represent the 4 sets of rights that can be defined in the permission system. In every section, ticking a checkbox will grant this group the rights as described. If the checkbox is unchecked, this group will not have access to the selected resource.

[Note]Note

Whenever you make changes to the settings on a page, you must click the “Update Group” button at the bottom before changes take place.

Let’s look at each set of rights individually.

  • System Admin Rights” - As their name says, System Admin Rights are rights that will control access to the System module. Each item in this sections represent an item found in the Administration Menu->System Admin->Preferences menu. In order to see the System Admin module in the Administration Menu->Control Panel Home page, at least one item has to be checked in this section!

  • Module Admin Rights” - As for the Module Admin Rights, the Module Access Rights section lists all the modules currently installed on your site. In order for a group to access a particular module, the corresponding item must be checked in the present section. In addition to not being able to access a module which item has not been checked, the members of the group will not even see that module through the Main Menu. For example: if, for the anonymous users group, the “News” module is checked, when they visit your site, the “News” module will be shown in the main menu and they can access the content (pages) of ‘News’. If the “Forums” module is unchecked it will not show up in the main menu, and they will not be able to access any content in the “Forums” module.

    However, using the search function, a member of this group will be able to perform a search in module for which his group does not have access. Of course, the member will only be able to see the title of the items returned by the search and will not be able to actually access the item.

  • Block Access Rights” If a module has specific blocks that are available as part of its functionality, they will appear in this section. Each block can be assigned a position on the page (this is detailed in the block section of this manual) If we have already assigned a page position to a block, it will be seen in that position in the “Block Access Rights” section.

    Each block displayed is given a system ID number. The name is also a hyperlink to a “block edit” page. For further information on the Block Edit page, please see Section 2.5.3, “Editing a block”.

Modify Groups

Figure 2.8. Modify Groups

2.8.3. Edit members of this group

The final section on each “Modify group” page displays a list box of “Non-members” and “Members”. This list is specific to each group you are viewing.

All registered members will be shown in one of these list boxes. You can remove and add members for any group by using this feature.

The XOOPS Core Development Team recommends that each user be part of only 1 group. Doing this, you’ll be assured that no conflicts occurred.

2.8.4. Creating a new group

The final option you have is to 'Create new group'.

Go to Administration Menu->System Admin->Groups->Edit Groups page.

The Create a New Group section displays a familiar table that you have already seen in the 3 default groups with all the modules and blocks installed in the system. Notice they are listed against empty check boxes, until you assign the settings for the new group.

Enter a name and description for the new group. Assign rights and access for each module and block displayed, by filling the check boxes in the same way as the 3 default groups previously.

At the bottom you will see a button for create new group, click this to create the new group you have defined in the page.

Your new group will now appear in the list of groups throughout the site administration pages. Note that the newly created group does not have any members yet. You’ll have to click Modify and add the users you want in the group, as seen on section Section 2.12.5, “Search Options”.

The comments are owned by the author. We aren't responsible for their content.

Author Thread
dalong
Published: 2006/11/16 8:00  Updated: 2006/11/16 8:00
Just popping in
Joined: 2006/11/16
From:
Comments: 2
 Re: xo-002 http://www.apachefriends.org/en/xampp.html
very good!
I like here!

Author Thread
dalong
Published: 2006/11/16 10:13  Updated: 2006/11/16 10:13
Just popping in
Joined: 2006/11/16
From:
Comments: 2
 Re: xo-002 http://www.apachefriends.org/en/xampp.html
thank for your work!

Author Thread
huqilong
Published: 2006/11/20 2:50  Updated: 2006/11/20 2:50
Just popping in
Joined: 2006/11/16
From:
Comments: 3
 Re: xo-002 http://www.apachefriends.org/en/xampp.html
I hava a question ,when I have installed phpeclipse,I can't user the button for the apache in the Eclipse IDE,how shoud I do?

Author Thread
huqilong
Published: 2006/11/20 3:10  Updated: 2006/11/20 3:10
Just popping in
Joined: 2006/11/16
From:
Comments: 3
 Re: xo-002 http://www.apachefriends.org/en/xampp.html
dddd

Author Thread
Mark_1900
Published: 2006/11/18 11:05  Updated: 2006/11/18 11:09
Just popping in
Joined: 2006/11/18
From:
Comments: 2
 Alias Permission Problems
For an Alias I also had to add a Directory tag to the httpd.conf, otherwise I had permission problems accessing the files... <br /> [code] Alias /wiki "C:/Documents and Settings/Me/wiki"<br /> <Directory "C:/Documents and Settings/Me/wiki"><br /> Options Indexes MultiViews<br /> AllowOverride None<br /> Order allow,deny<br /> Allow from all<br /> </Directory><br /> [/code]<br /> Oh and all these editing tags seem broken!!

Author Thread
Mark_1900
Published: 2006/11/18 11:21  Updated: 2006/11/18 11:32
Just popping in
Joined: 2006/11/18
From:
Comments: 2
 Getting the correct php_dbg.dll
I want a debugger. I downloaded the latest XAMPP 1.5.4a and noticed that it comes with PHP 5.1.6 & PHP 4.4.4, and neither are supported. The debugger module only supports a subset of these major versions from 5.1.0 to 5.1.2 and 4.4.0 to 4.4.2 (http://dd.cron.ru/dbg/downloads.php). I think right at the beginning you should specify which versions to download to get a debugger Version "XAMPP 1.5.2" would be fine.

Author Thread
huqilong
Published: 2006/11/30 6:28  Updated: 2006/11/30 6:28
Just popping in
Joined: 2006/11/16
From:
Comments: 3
 Re: xo-002 http://www.apachefriends.org/en/xampp-windows....
I want to know how to use phpeclipse with eclipse detailly!

Author Thread
thierrybo
Published: 2007/2/3 16:19  Updated: 2007/2/3 16:21
Just popping in
Joined: 2007/2/3
From:
Comments: 1
 Re: xo-002 ch02s03.html Workspace Method 2
I do not agree with the suggested method 2: Quote:
For example you have set up XAMPP and your “document root” path is the XAMPP default:
C:Program Filesapachefriendsxampphtdocs
Quote:
,then your appropriate workspace path should be one level less:
C:Program Filesapachefriendsxampp
If htdocs is your document root, then each folder inside IS a new project and you should set workspace directory as Document Root directory. With suggested method, all your web projects are managed with ONE big PHPeclipse project.

Author Thread
dafydd
Published: 2007/4/3 6:01  Updated: 2007/4/3 6:01
Just popping in
Joined: 2007/4/3
From:
Comments: 2
 Re: xo-002 ch01.html
Trying this out on a Mac. J2SE 1.5.0_07-164 installed. 1.5.0_06 is what's available on the download site. However, it would almost certainly be updated with Software Update.

Author Thread
dafydd
Published: 2007/4/6 1:00  Updated: 2007/4/6 1:00
Just popping in
Joined: 2007/4/3
From:
Comments: 2
 Re: xo-002 ch01s04.html
Second question: How do we point the XAMPP start/stop buttons in the Eclipse toobar to where we put XAMPP?

dafydd

Author Thread
dysmas
Published: 2007/8/4 14:18  Updated: 2007/8/4 14:18
Just popping in
Joined: 2007/8/4
From:
Comments: 1
 Debugging standalone PHP applications
Thanks hundred times for all the detailed explanations here !!

And especially for the note which explains why debugging a CLI application does not work in 1.1.8 version and only in 1.1.9. (wrong port, as I guessed, but I have been looking for this information for some hours before coming here). Unfortunately this 1.1.9 CVS version does not work in the last 3.2.0 Eclipse version I just got. Let us hope the stable version is going quickly.

Author Thread
Mercyful
Published: 2007/9/10 14:46  Updated: 2007/9/10 14:46
Just popping in
Joined: 2007/9/10
From:
Comments: 1
 Re: dbg is not working
I want using eclipse3.2 with php-plugin and for debugging i want using dbg.
I'm using xampp 1.6.3a with php 4.4.7. and php_dbg.dll-4.4.x
After step by step installation
http://docs.schuetzengau-freising.de/ ... =xo-002&file=ch01s05.html
the debugger dbg will not work.
When i called phpinfo() there is no section dbg shown.
Who have any ideas?
Thanks a lot!
Regards Mercyful

Author Thread
keryx
Published: 2007/9/26 22:59  Updated: 2007/9/26 22:59
Just popping in
Joined: 2007/9/26
From:
Comments: 1
 Re: xo-002 ch04.html
A section about verrors should be nice. I get the following:


<terminated, exit value: 0>PHP C:\Program\PHP\php.exe : <path>/<fil>.php

I've googled like crazy but to no avail. And yes - it does not stop at breakpoints and "variables" are empty. DBG is working:

if (function_exists ("DebugBreak")) {
DebugBreak ();
echo "debugging started!<br />\n";
}

Outputs "debugging started!" And DBG is reported on phpinfo().

Author Thread
koski
Published: 2007/10/19 3:55  Updated: 2007/10/19 3:55
Just popping in
Joined: 2007/10/19
From:
Comments: 1
 Re: xo-002 ch01s03.html
Hi,

Seems that the mentioned link for cvs:

http://phpeclipse.sourceforge.net/update/cvs

is out of date or wrong.

Author Thread
andybruk
Published: 2007/11/18 1:11  Updated: 2007/11/18 1:11
Just popping in
Joined: 2007/11/18
From:
Comments: 1
 Re: xo-002 index.html
I've been searching for a PHP debugger for ages. This is the only one I can find that works perfectly, thanks very much for providing this documentation.<br /><br />I doubt if I could ever get it to work on Windows, but it works so well with Ubuntu Linux and Eclipse 3.1.<br />
Powered by XOOPS 2.0 © 2001-2005 The XOOPS Project