A "members" section

Next topic

Author	Message
Steve P	Friday 01 April 2005 8:06:55 am Hello all. This seems to have come up before, though the replies are as clear as mud to me! Surely there's an easy way to create a section that only members can access after log-in? The admin interface roles section is really confusing... Thanks - have a good weekend. Steve
Frey Staso	Friday 01 April 2005 8:50:12 am An individual user belongs to a user group. Examples being administrator and annonymous. These user groups (or the users themselves) may be assigned "Roles" that determine what they can and cannot access/read/change etc. In order to have a members section, change the annonymous role so that it has a policy that says something like content/read/all, then assign it with limitation to all the sections you want regular people to be able to see (to the annonymous group) Make a "members" user group. Assign with limitation all the sections you wish your members to be able to see.

Author

Message

Friday 01 April 2005 8:06:55 am

Hello all. This seems to have come up before, though the replies are as clear as mud to me! Surely there's an easy way to create a section that only members can access after log-in? The admin interface roles section is really confusing...

Thanks - have a good weekend.

Steve

Frey Staso

Friday 01 April 2005 8:50:12 am

An individual user belongs to a user group. Examples being administrator and annonymous. These user groups (or the users themselves) may be assigned "Roles" that determine what they can and cannot access/read/change etc.

In order to have a members section, change the annonymous role so that it has a policy that says something like content/read/all, then assign it with limitation to all the sections you want regular people to be able to see (to the annonymous group)

Make a "members" user group. Assign with limitation all the sections you wish your members to be able to see.

eZ debug

Timing:	Jan 31 2025 06:00:32
Script start
Timing:	Jan 31 2025 06:00:32
Module start 'layout'
Timing:	Jan 31 2025 06:00:32
Module start 'content'
Timing:	Jan 31 2025 06:00:32
Module end 'content'
Timing:	Jan 31 2025 06:00:32
Script end

Main resources:

Total runtime	0.0115 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0046	588.0313	151.1953
Module start 'layout'	0.0046	0.0025	739.2266	36.6172
Module start 'content'	0.0071	0.0032	775.8438	90.0313
Module end 'content'	0.0103	0.0011	865.8750	29.9922
Script end	0.0114		895.8672

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0022	19.2763	14	0.0002
Check MTime	0.0011	9.1804	14	0.0001
Mysql Total
Database connection	0.0008	6.8083	1	0.0008
Mysqli_queries	0.0023	19.7653	3	0.0008
Looping result	0.0000	0.1498	1	0.0000
Template Total	0.0009	7.6	1	0.0009
Template load	0.0007	5.7762	1	0.0007
Template processing	0.0002	1.5876	1	0.0002
Override
Cache load	0.0005	4.1033	1	0.0005
General
dbfile	0.0002	1.8415	8	0.0000
String conversion	0.0000	0.0728	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs