view modes for attribute_edit_gui and attribute_view_gui

«

Previous topic

|

|

Next topic

»

Author	Message
Claudia Kosny	Friday 29 September 2006 2:22:30 pm Hi there Is it possible to have different views for the attribute_edit_gui? Example: I have an ezselection attribute. There a several ways to edit such an attribute, one could use an selectbox, some radiobuttons or some checkboxes (if multiselect). I want to tell the attribute_edit_gui function what template to use. The same applies to the attribute_view_gui. At the moment I use a parameter for this but I would like this to work like the different view modes possible for the node_view_gui. Then I could have different templates for each required attribute view and not have all of them in one big switch. Claudia
Kristian Hole	Friday 29 September 2006 4:28:55 pm Hi Claudia, You can create different overrides for the edit templates. Look here: http://ez.no/doc/ez_publish/technical_manual/3_8/reference/template_override_conditions/content_datatype_edit_tpl Alternatively, you can also pass variables to the edit templates {attribute_edit_gui attribute=$basdf variable1="value1"} Kristian http://ez.no/ez_publish/documenta...tricks/show_which_templates_are_used http://ez.no/doc/ez_publish/techn...te_operators/miscellaneous/attribute
Claudia Kosny	Saturday 30 September 2006 2:24:24 am Hi Kristian Yes I know that I can create overrides. The problem is that these overrides would be valid for the entire siteaccess but I would like to be able to choose which view I want depending on the template the attribute_edit_gui function is used in. Currently I use your second idea by selecting which view to use basing on some variable I pass to the edit template. This works alright so it is truly not necessary to have the functionality I asked for. It just would be nice to have the same functionality for all xx_yy_gui functions and it is possible to choose different view modes for displaying nodes or objects after all. So this is really just a suggestion, definitely not something necessary. Greetings from Luxembourg Claudia
Damien Pobel	Saturday 30 September 2006 3:42:08 am Hi, I agree with Claudia, an override system also based on a view parameter (or something similar) on attribute_view_gui would be a really nice feature even if there are solutions without it. Damien Planet eZ Publish.fr : http://www.planet-ezpublish.fr Certification : http://auth.ez.no/certification/verify/372448 Publications about eZ Publish : http://pwet.fr/tags/keywords/weblog/ez_publish

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 30 2025 21:23:26
Script start
Timing:	Jan 30 2025 21:23:26
Module start 'layout'
Timing:	Jan 30 2025 21:23:26
Module start 'content'
Timing:	Jan 30 2025 21:23:26
Module end 'content'
Timing:	Jan 30 2025 21:23:26
Script end

Main resources:

Total runtime	0.0227 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	588.3906	151.2422
Module start 'layout'	0.0050	0.0034	739.6328	220.7500
Module start 'content'	0.0084	0.0126	960.3828	1,001.8672
Module end 'content'	0.0210	0.0016	1,962.2500	33.9922
Script end	0.0226		1,996.2422

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	11.2881	14	0.0002
Check MTime	0.0011	4.8818	14	0.0001
Mysql Total
Database connection	0.0006	2.5724	1	0.0006
Mysqli_queries	0.0027	11.7815	3	0.0009
Looping result	0.0000	0.0484	1	0.0000
Template Total	0.0013	5.5	1	0.0013
Template load	0.0010	4.2148	1	0.0010
Template processing	0.0003	1.2446	1	0.0003
Override
Cache load	0.0007	2.9869	1	0.0007
General
dbfile	0.0011	4.9102	8	0.0001
String conversion	0.0000	0.0263	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.0002 secs