Creating a customed back office ?

Previous topic

Setup & design

Next topic

Author	Message
Nabil Alimi	Friday 03 June 2005 6:14:32 am Hi there, Is there a way to create a customed back-office ? I'll explain. The default back-end in EzPublish is a little bit to complicated for common users. I'd like ton create a custom one with only what contributors needs. In order to do so, i'd like to create a custom page that would be accessed by a different url. Example : a default EzPublish site has 2 different base urls : plain, plain_admin. I'd like to add plain_manage that will be my custom back office. Just the layout will be different. The contents accessed will be the same. Is this possible ? My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com eZ Publish Freelance developper. Feel free to contact me +33 674 367 057 nabil at assiki d0t fr
Mikhail Chekanov	Friday 03 June 2005 7:07:20 am Yes, of course you can create another siteaccess to manage your site. Also you can add this functionality directly to the frontend: just provide additional edit view templates and set appropriate permissions for this siteaccess. Or you can simplify admin interface, provided by eZ Publish and add it as additional siteaccess :) -- mike #6595551

Author

Message

Nabil Alimi

Friday 03 June 2005 6:14:32 am

Hi there,

Is there a way to create a customed back-office ?
I'll explain. The default back-end in EzPublish is a little bit to complicated for common users. I'd like ton create a custom one with only what contributors needs.
In order to do so, i'd like to create a custom page that would be accessed by a different url. Example : a default EzPublish site has 2 different base urls : plain, plain_admin. I'd like to add plain_manage that will be my custom back office.
Just the layout will be different. The contents accessed will be the same.
Is this possible ?

My blog : http://www.starnab.com/ezpublish / http://www.starnab.com/ / http://www.assiki-consulting.com
eZ Publish Freelance developper. Feel free to contact me +33 674 367 057
nabil at assiki d0t fr

Mikhail Chekanov

Friday 03 June 2005 7:07:20 am

Yes, of course you can create another siteaccess to manage your site. Also you can add this functionality directly to the frontend: just provide additional edit view templates and set appropriate permissions for this siteaccess.
Or you can simplify admin interface, provided by eZ Publish and add it as additional siteaccess :)

--
mike
#6595551

eZ debug

Timing:	Jan 18 2025 15:57:42
Script start
Timing:	Jan 18 2025 15:57:42
Module start 'layout'
Timing:	Jan 18 2025 15:57:42
Module start 'content'
Timing:	Jan 18 2025 15:57:42
Module end 'content'
Timing:	Jan 18 2025 15:57:42
Script end

Main resources:

Total runtime	0.0156 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.0053	589.0469	152.6250
Module start 'layout'	0.0053	0.0026	741.6719	39.4609
Module start 'content'	0.0080	0.0058	781.1328	89.3359
Module end 'content'	0.0137	0.0018	870.4688	30.3047
Script end	0.0155		900.7734

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	15.4010	14	0.0002
Check MTime	0.0011	6.9740	14	0.0001
Mysql Total
Database connection	0.0009	6.0753	1	0.0009
Mysqli_queries	0.0023	14.8942	3	0.0008
Looping result	0.0000	0.1164	1	0.0000
Template Total	0.0015	9.5	1	0.0015
Template load	0.0008	5.2653	1	0.0008
Template processing	0.0007	4.2012	1	0.0007
Override
Cache load	0.0006	3.6164	1	0.0006
General
dbfile	0.0017	11.0528	8	0.0002
String conversion	0.0000	0.0383	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