how to do some personalisation ?

Next topic

Author	Message
orlando gall	Thursday 13 January 2005 12:53:13 am I want to tell ezPublish a specific content to be displayed to a specific user only or a specific group of users. how to setup this kind of personalisation rules ? anyone has an idea ?
Eivind Marienborg	Thursday 13 January 2005 3:14:55 am {let user=fetch( 'user', 'current_user' ) approved=false()} {section loop=$user.groups} {switch match=$:item} {case match=OBJECT_ID_OF_USER_GROUP} {set approved=true()} {/case} {/switch} {/section} {/let} {section show=$approved} {* THINGS TO SHOW MEMBERS OF GROUP *} {/section} This works at my site, I think-
orlando gall	Thursday 13 January 2005 7:33:43 am okay, thx i'm not sure to understand exactly (because not yet fluant with the templating language) but i think this is not exactly what i meant. I want to define in the back end, that a specific content will be only available to a specific user or user groupe. I want to do this not once but many times, so i would need to do it using the administration consile, and not via coding. A solution would be to define an attribute in the class defining my content. This attribute would define the ID of the user allowed to view the content ... anyone did this this ?

Author

Message

Thursday 13 January 2005 12:53:13 am

I want to tell ezPublish a specific content to be displayed to a specific user only or a specific group of users.
how to setup this kind of personalisation rules ?

anyone has an idea ?

Eivind Marienborg

Thursday 13 January 2005 3:14:55 am

{let    user=fetch( 'user', 'current_user' )
        approved=false()}

{section loop=$user.groups}

{switch match=$:item}

{case match=OBJECT_ID_OF_USER_GROUP}
        {set approved=true()}
{/case}

{/switch}
{/section}

{/let}

{section show=$approved}
{* THINGS TO SHOW MEMBERS OF GROUP *}
{/section}

This works at my site, I think-

orlando gall

Thursday 13 January 2005 7:33:43 am

okay, thx i'm not sure to understand exactly (because not yet fluant with the templating language) but i think this is not exactly what i meant.

I want to define in the back end, that a specific content will be only available to a specific user or user groupe.
I want to do this not once but many times, so i would need to do it using the administration consile, and not via coding.

A solution would be to define an attribute in the class defining my content. This attribute would define the ID of the user allowed to view the content ...

anyone did this this ?

eZ debug

Timing:	Jan 31 2025 01:18:31
Script start
Timing:	Jan 31 2025 01:18:31
Module start 'layout'
Timing:	Jan 31 2025 01:18:31
Module start 'content'
Timing:	Jan 31 2025 01:18:31
Module end 'content'
Timing:	Jan 31 2025 01:18:31
Script end

Main resources:

Total runtime	0.0282 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0055	588.1250	151.2109
Module start 'layout'	0.0055	0.0035	739.3359	220.6875
Module start 'content'	0.0090	0.0172	960.0234	997.8984
Module end 'content'	0.0262	0.0020	1,957.9219	29.9922
Script end	0.0281		1,987.9141

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	10.4633	14	0.0002
Check MTime	0.0013	4.6904	14	0.0001
Mysql Total
Database connection	0.0010	3.4835	1	0.0010
Mysqli_queries	0.0025	8.7651	3	0.0008
Looping result	0.0000	0.0389	1	0.0000
Template Total	0.0013	4.4	1	0.0013
Template load	0.0010	3.3947	1	0.0010
Template processing	0.0003	1.0216	1	0.0003
Override
Cache load	0.0006	2.1464	1	0.0006
General
dbfile	0.0028	9.8468	8	0.0003
String conversion	0.0000	0.0203	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