Customisable admin interface

Next topic

Author	Message
Paul Forsyth	Friday 03 October 2003 2:14:00 am The admin interface could have a section from which admins specified what access lesser users (editors, anyone but admins) have to the admin interface. So, locations like 'shop', 'Extension setup', 'RAD', etc would not be shown. I understand 3.3 will allow the admin to be reskinned but it would be great if more was controllable by the admin... :) At the moment i have to change the templates by hand to reduce the functionality. paul
Paul Forsyth	Friday 03 October 2003 3:45:08 am Following on from this. With the ability to customise the admin interface for users it would be natural to have example profiles for different types of users. The control of what is displayed may be through the admin or an ini file. One problem here is the separation of the presentation from the role. If a link is given the role usually has to be updated to allow that link to work for the user. The role function could itself allow a user/group to be set up with specific roles in categories and the admin would then display these categories as menus with links. A simple extension could use the url translation mechanism to assign urls users would use to access the functions. On one hand i like that user access is explicit, no (* * *) for some. But on the other if the list is too complex there may be too many options and may hinder maintanence - can't see the wood for the trees syndrome. paul

Author

Message

Friday 03 October 2003 2:14:00 am

The admin interface could have a section from which admins specified what access lesser users (editors, anyone but admins) have to the admin interface.

So, locations like 'shop', 'Extension setup', 'RAD', etc would not be shown.

I understand 3.3 will allow the admin to be reskinned but it would be great if more was controllable by the admin... :)

At the moment i have to change the templates by hand to reduce the functionality.

paul

Paul Forsyth

Friday 03 October 2003 3:45:08 am

Following on from this.

With the ability to customise the admin interface for users it would be natural to have example profiles for different types of users. The control of what is displayed may be through the admin or an ini file.

One problem here is the separation of the presentation from the role. If a link is given the role usually has to be updated to allow that link to work for the user.

The role function could itself allow a user/group to be set up with specific roles in categories and the admin would then display these categories as menus with links. A simple extension could use the url translation mechanism to assign urls users would use to access the functions.

On one hand i like that user access is explicit, no (* * *) for some. But on the other if the list is too complex there may be too many options and may hinder maintanence - can't see the wood for the trees syndrome.

paul

eZ debug

Timing:	Jan 18 2025 11:22:55
Script start
Timing:	Jan 18 2025 11:22:55
Module start 'layout'
Timing:	Jan 18 2025 11:22:55
Module start 'content'
Timing:	Jan 18 2025 11:22:56
Module end 'content'
Timing:	Jan 18 2025 11:22:56
Script end

Main resources:

Total runtime	0.6302 sec
Peak memory usage	4,096.0000 KB
Database Queries	52

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0068	589.0469	152.6250
Module start 'layout'	0.0068	0.0033	741.6719	39.4453
Module start 'content'	0.0101	0.6186	781.1172	423.9141
Module end 'content'	0.6287	0.0014	1,205.0313	8.1641
Script end	0.6301		1,213.1953

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0042	0.6655	16	0.0003
Check MTime	0.0017	0.2737	16	0.0001
Mysql Total
Database connection	0.0006	0.1025	1	0.0006
Mysqli_queries	0.5728	90.8984	52	0.0110
Looping result	0.0006	0.0989	50	0.0000
Template Total	0.5822	92.4	2	0.2911
Template load	0.0023	0.3672	2	0.0012
Template processing	0.5799	92.0182	2	0.2899
Template load and register function	0.0002	0.0295	1	0.0002
states
state_id_array	0.0011	0.1749	1	0.0011
state_identifier_array	0.0016	0.2542	2	0.0008
Override
Cache load	0.0020	0.3103	15	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0010	0.1546	1	0.0010
Fetch class attribute name	0.0018	0.2841	2	0.0009
XML
Image XML parsing	0.0001	0.0197	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0009	2	0.0000
General
dbfile	0.0023	0.3651	10	0.0002
String conversion	0.0000	0.0014	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
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
2	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 6 Number of unique templates used: 4

Time used to render debug report: 0.0001 secs