How setting up an administrative view for publishers?

Previous topic

General

Next topic

Author	Message
Paolo Tramontani	Wednesday 10 September 2003 1:32:53 am I'm setting up a site with news section and articles. I'm using admin access to design the site, create metadata, manage users and so on. When the site will ready some employees will publish news and articles (content in general). They will need a thiny interface with only the functions they need (insert news, or articles in particular sections). Does Ezpublish provide something to accomplish this or is it necessary to create a new site dedicated with templates, calling modules for content management and so on? Thanks Paolo
Paul Borgermans	Thursday 11 September 2003 2:07:04 pm No you can use some admin functionality in your regular site. The trick is to assign the rights/roles to your editors and create a few forms depending on the fact if the current user can create certain objects. Look in the admin interface templates how it is done (where you have the drop down of create .... ) It's easy. -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Bjørn Kaarstein	Friday 12 September 2003 1:51:51 am I have copied the admin interface, named it editor, and stripped it down to a minium within the admin-templates. I've given it it's own siteaccess. I then run it from http://editor.domain.no where the editors can log in to edit their content. My full admin runs from http://admin.domain.no and is only for me. The site runs from http://www.domain.no. It's so nice to have control of your own server with full freedom to create subdomains :) This works fine on the smaller sites I've created, and minimizes the potential threat of none-technical editors messing up the content. Regards Bjørn

Author

Message

Paolo Tramontani

Wednesday 10 September 2003 1:32:53 am

I'm setting up a site with news section and articles.

I'm using admin access to design the site, create metadata, manage users and so on.

When the site will ready some employees will publish news and articles (content in general). They will need a thiny interface with only the functions they need (insert news, or articles in particular sections).
Does Ezpublish provide something to accomplish this or is it necessary to create a new site dedicated with templates, calling modules for content management and so on?

Thanks
Paolo

Paul Borgermans

Thursday 11 September 2003 2:07:04 pm

No you can use some admin functionality in your regular site. The trick is to assign the rights/roles to your editors and create a few forms depending on the fact if the current user can create certain objects. Look in the admin interface templates how it is done (where you have the drop down of create .... ) It's easy.

-paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Bjørn Kaarstein

Friday 12 September 2003 1:51:51 am

I have copied the admin interface, named it editor, and stripped it down to a minium within the admin-templates. I've given it it's own siteaccess.

I then run it from http://editor.domain.no where the editors can log in to edit their content. My full admin runs from http://admin.domain.no and is only for me. The site runs from http://www.domain.no. It's so nice to have control of your own server with full freedom to create subdomains :)

This works fine on the smaller sites I've created, and minimizes the potential threat of none-technical editors messing up the content.

Regards Bjørn

eZ debug

Timing:	Jan 18 2025 19:14:42
Script start
Timing:	Jan 18 2025 19:14:42
Module start 'layout'
Timing:	Jan 18 2025 19:14:42
Module start 'content'
Timing:	Jan 18 2025 19:14:43
Module end 'content'
Timing:	Jan 18 2025 19:14:43
Script end

Main resources:

Total runtime	1.3018 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0068	588.0391	152.6406
Module start 'layout'	0.0068	0.0038	740.6797	39.4922
Module start 'content'	0.0107	1.2900	780.1719	567.8359
Module end 'content'	1.3006	0.0012	1,348.0078	12.1250
Script end	1.3018		1,360.1328

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0037	0.2837	16	0.0002
Check MTime	0.0016	0.1202	16	0.0001
Mysql Total
Database connection	0.0009	0.0711	1	0.0009
Mysqli_queries	1.2507	96.0757	59	0.0212
Looping result	0.0005	0.0381	57	0.0000
Template Total	1.2648	97.2	2	0.6324
Template load	0.0020	0.1574	2	0.0010
Template processing	1.2628	97.0002	2	0.6314
Template load and register function	0.0001	0.0090	1	0.0001
states
state_id_array	0.0010	0.0787	1	0.0010
state_identifier_array	0.0018	0.1355	2	0.0009
Override
Cache load	0.0017	0.1341	18	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0376	3	0.0002
Fetch class attribute name	0.0011	0.0813	4	0.0003
XML
Image XML parsing	0.0008	0.0637	3	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0005	4	0.0000
General
dbfile	0.0009	0.0655	17	0.0001
String conversion	0.0000	0.0010	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
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 13 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs