Specific pagelayout for connected user

Previous topic

Setup & design

Next topic

Author	Message
Pascal France	Thursday 23 February 2006 11:56:18 am Hi, I would like to set up specific designs for specific user groups I tried to create an override like that: 598 [pagelayout_connecte] 599 Source=pagelayout.tpl 600 MatchFile=pagelayout_connecte.tpl 601 Subdir=templates 602 Match[node]=xxx where xxx is the number ID of a user group or a user. I tried Match[parent_node]=xxx without success too. It seems it's not the good way to do what I want. Thanks for your help Pascal Ce qui embellit le désert c'est qu'il cache un puits... quelque part... (A. de Saint-Exupéry) - http://luxpopuli.fr/eZ-Publish
Roy Bøhmer	Friday 24 February 2006 3:09:36 am Hi Pascal! As far as I know you can't override based on logged in users. My suggestion would be to edit pagelayout.tpl and include appropriate css-files and other includes based on the users usergroup. I haven't done it my self, but that information about current user should be pretty stright forward to access in the templates using $current_user in pagelayout. See http://ez.no/doc/ez_publish/technical_manual/3_6/templates/the_pagelayout/variables_in_pagelayout I hope someone else has a better solution, because this is defenitly not a nice way to do it if your designs are very different. Roy

Author

Message

Pascal France

Thursday 23 February 2006 11:56:18 am

Hi,

I would like to set up specific designs for specific user groups
I tried to create an override like that:

    598 [pagelayout_connecte]
    599 Source=pagelayout.tpl
    600 MatchFile=pagelayout_connecte.tpl
    601 Subdir=templates
    602 Match[node]=xxx

where xxx is the number ID of a user group or a user.
I tried Match[parent_node]=xxx without success too.

It seems it's not the good way to do what I want.

Thanks for your help

Pascal

Ce qui embellit le désert c'est qu'il cache un puits... quelque part... (A. de Saint-Exupéry) - http://luxpopuli.fr/eZ-Publish

Roy Bøhmer

Friday 24 February 2006 3:09:36 am

Hi Pascal!

As far as I know you can't override based on logged in users.

My suggestion would be to edit pagelayout.tpl and include appropriate css-files and other includes based on the users usergroup. I haven't done it my self, but that information about current user should be pretty stright forward to access in the templates using $current_user in pagelayout.
See http://ez.no/doc/ez_publish/technical_manual/3_6/templates/the_pagelayout/variables_in_pagelayout

I hope someone else has a better solution, because this is defenitly not a nice way to do it if your designs are very different.

Roy

eZ debug

Timing:	Jan 18 2025 11:46:12
Script start
Timing:	Jan 18 2025 11:46:12
Module start 'layout'
Timing:	Jan 18 2025 11:46:12
Module start 'content'
Timing:	Jan 18 2025 11:46:12
Module end 'content'
Timing:	Jan 18 2025 11:46:12
Script end

Main resources:

Total runtime	0.0164 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.0057	589.1484	152.6406
Module start 'layout'	0.0057	0.0028	741.7891	39.4766
Module start 'content'	0.0085	0.0054	781.2656	89.3516
Module end 'content'	0.0139	0.0024	870.6172	30.3047
Script end	0.0163		900.9219

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	15.4851	14	0.0002
Check MTime	0.0011	6.6827	14	0.0001
Mysql Total
Database connection	0.0007	4.5775	1	0.0007
Mysqli_queries	0.0028	17.3776	3	0.0009
Looping result	0.0000	0.0860	1	0.0000
Template Total	0.0015	9.4	1	0.0015
Template load	0.0008	5.1020	1	0.0008
Template processing	0.0007	4.2584	1	0.0007
Override
Cache load	0.0006	3.3785	1	0.0006
General
dbfile	0.0003	1.8065	8	0.0000
String conversion	0.0000	0.0612	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