New Tab at Administration Interface

Author Message

Michael Scofield

Tuesday 10 June 2008 3:15:01 am

Hello,

I'm trying to create a new Tab at the administration interface to make an interface to manage some additional tables I have in the database.

I changed the menu.ini.append.php and now I have a tab showing at the back end.

But I don't know how to proceed from this step.

Do I have to create a module?

The screens I need are from basic management. For each table I want to have a link to manage the table. When I click this link, it's supposed to show me buttons to Insert a new registry, Search for inserted registries, delete and edit.

Do I need a module for that?

Thank you
Michael Scofield

Piotrek Karaƛ

Tuesday 10 June 2008 9:43:20 am

If you managed to create a tab, you're almost there. But of course module view will be necessary for the tab to be able to point to. So yes, you need a module and view(s). You would probably at least need views like browse and edit. Deletion and adding_blank can usually be combined within browse view, but that's up to your preferences.

If you plan more than one view, you may want to create a left-side menu for that tab. This is defined in the module.php, the definition file for your module, with the following line for each view array:

'default_navigation_part' => 'somecustomnavigationpart',

and has corresponding templates in /design/admin/templates/parts/*

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

anry gon

Tuesday 17 June 2008 1:49:31 am

try add
extension/ext_name/design/standart/templates/ext_name/parts/menu.tpl
and

$Result ['left_menu'] =  'design:ext_name/parts/menu.tpl' ;

in your view file
It's works in my case.

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 19 2025 07:16:52
Script start
Timing: Jan 19 2025 07:16:52
Module start 'layout'
Timing: Jan 19 2025 07:16:52
Module start 'content'
Timing: Jan 19 2025 07:16:52
Module end 'content'
Timing: Jan 19 2025 07:16:52
Script end

Main resources:

Total runtime0.0135 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0055 589.1797152.6250
Module start 'layout' 0.00550.0026 741.804739.4453
Module start 'content' 0.00810.0037 781.250089.4609
Module end 'content' 0.01180.0016 870.710934.3047
Script end 0.0135  905.0156 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002216.1141140.0002
Check MTime0.00117.8819140.0001
Mysql Total
Database connection0.00129.171610.0012
Mysqli_queries0.002720.222230.0009
Looping result0.00000.244210.0000
Template Total0.001410.110.0014
Template load0.00075.217410.0007
Template processing0.00074.890110.0007
Override
Cache load0.00053.614510.0005
General
dbfile0.00021.769280.0000
String conversion0.00000.053140.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs