Different starting points in admin interface?

Next topic

Author	Message
Nicklas Lundgren	Friday 27 May 2005 4:10:05 am Hi all, Does anyone know if it is possible to change the starting point of the admin-interface based on a user-role policy? We are planning to set up a site with a lot of different userrights. And we would like to make sure that a person with editing permissions to a certain area of the site gets to this area immediately when logging in to the admin interface. Best regards, /Nicklas Lundgren Nicklas Lundgren, Managing Director Novitell AB, Sweden
Lex 007	Friday 27 May 2005 7:36:09 am Hi I think you can do that with several site accesses, that each have a different root node (this parameter should be in the site.ini) Lex
Nicklas Lundgren	Sunday 29 May 2005 8:44:45 am Thanks Lex007, I have already tried that, and it does work to set different starting points with different siteaccesses. However, I would like to keep it down to one siteaccess but still have different starting points based on user-rights. But maybe its not possible? Nicklas Lundgren, Managing Director Novitell AB, Sweden
kracker (the)	Sunday 29 May 2005 11:48:59 am Snazzy Idea, I think your going to want to create a user class with a sort of attribute that contains the path to the default root / index variables (perhaps two attributes). The goal is to move the abstraction of these site.ini variables to a higher level of abstraction. I think is going to require some changes to a few key internal places inside eZ publish (kernel hacking / extension), specificaly the user kernel class / authentication functions which use these variables. IndexPage=/content/view/full/2/ DefaultPage=/content/view/full/2/ //kracker <i>korn : leave this place</i> Member since: 2001.07.13 \|\| http://ezpedia.se7enx.com/
kracker (the)	Sunday 29 May 2005 11:57:28 am Specifically, You will want to look (as I have for you) at this directory: <i>kernel/user/</i> And again at this file specifically: <i>kernel/user/login.php</i> At this specific chunk of code (<b>search</b> for it): $redirectionURI = $userRedirectURI; if ( $redirectionURI == '' ) $redirectionURI = $ini->variable( 'SiteSettings', 'DefaultPage' ); I have this idea that If you were to replace the ini variable reference with a call to your current user's class attribute by the same name you could achieve your short-term goal. This is kernel hacking of course so it is not the most long term efficient way of implementing this change long-term. Still it does give you a specific idea on what code you must <i>override</i> with your extension. //kracker <i>korn : here to stay (remix)</i> Member since: 2001.07.13 \|\| http://ezpedia.se7enx.com/
kracker (the)	Sunday 29 May 2005 12:12:41 pm If you are looking to do it right .. These are the nodes which you must assimilate first. With a little reading and practice with the hello world example you too can create an eZ publish extension. <i>http://www.ez.no/ez_publish/documentation/development/extensions http://www.ez.no/ez_publish/documentation/development/extensions/module/hello_world http://www.ez.no/ez_publish/documentation/development/extensions/module http://www.ez.no/ez_publish/documentation/development/extensions/module/module_tutorial_part_1 http://www.ez.no/ez_publish/documentation/development/extensions/building_an_ez_publish_module http://www.ez.no/ez_publish/documentation/installation/adding_extensions http://www.ez.no/ez_publish/documentation/development/kernel</i> The #1 reason to develop this functionality is without using an extension you loose your changes to the eZ publish kernel when you need to upgrade eZ publish. If you put this logic into an extension (which is relatively simple to do) you don't have to worry about upgrades at all, your protected !) Alternately, if you create an extension and eZ package of your user class you can <b>contribute</b> them back to the community for all of us to share this functionality and improve on it. //kracker <i>linkin park : nobody's listening</i> <i>sole : cheep entertainment</i> Member since: 2001.07.13 \|\| http://ezpedia.se7enx.com/

eZ debug

Timing:	Jan 19 2025 00:55:32
Script start
Timing:	Jan 19 2025 00:55:32
Module start 'layout'
Timing:	Jan 19 2025 00:55:32
Module start 'content'
Timing:	Jan 19 2025 00:55:33
Module end 'content'
Timing:	Jan 19 2025 00:55:33
Script end

Main resources:

Total runtime	1.1724 sec
Peak memory usage	4,096.0000 KB
Database Queries	68

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0056	589.2891	152.6406
Module start 'layout'	0.0056	0.0031	741.9297	39.4766
Module start 'content'	0.0087	1.1625	781.4063	634.3906
Module end 'content'	1.1711	0.0013	1,415.7969	16.1250
Script end	1.1724		1,431.9219

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.3062	16	0.0002
Check MTime	0.0013	0.1129	16	0.0001
Mysql Total
Database connection	0.0008	0.0685	1	0.0008
Mysqli_queries	1.0875	92.7533	68	0.0160
Looping result	0.0007	0.0563	66	0.0000
Template Total	1.1242	95.9	2	0.5621
Template load	0.0025	0.2150	2	0.0013
Template processing	1.1217	95.6726	2	0.5609
Template load and register function	0.0002	0.0186	1	0.0002
states
state_id_array	0.0045	0.3808	1	0.0045
state_identifier_array	0.0013	0.1092	2	0.0006
Override
Cache load	0.0021	0.1801	56	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0527	3	0.0002
Fetch class attribute name	0.0014	0.1158	9	0.0002
XML
Image XML parsing	0.0041	0.3539	3	0.0014
class_abstraction
Instantiating content class attribute	0.0000	0.0023	12	0.0000
General
dbfile	0.0053	0.4556	31	0.0002
String conversion	0.0000	0.0006	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
6	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
6	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
12	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 34 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs