How to start (filtering)?

Next topic

Author	Message
Vicente Olivan	Monday 21 July 2008 2:53:28 am At the news folder I created a form to filter the news by: - day - month - year - group (attribute class options list [selection]) - type (attribute class options list [selection]) - area (other folder) <form> <fieldset> <legend>by Date</legend> <label for="Day" class="hide">Dia</label> <select title="{'Day'\|i18n( 'design/.../node/view/full' )\|wash()}"> <option value="">Any</option> ... </select> <label for="Month" class="hide">Mes</label> <select title="{'Month'\|i18n( 'design/.../node/view/full' )\|wash()}"> <option value="">Any</option> ... </select> <label for="Year" class="hide">Año</label> <select title="{'Year'\|i18n( 'design/.../node/view/full' )\|wash()}"> <option value="">Any</option> ... </select> </fieldset> <fieldset> <legend>by Group</legend> <select title="{'by Group'\|i18n( 'design/.../node/view/full' )\|wash()}"> <option value="">Any</option> ... </select> </fieldset> <fieldset> <legend>by Type</legend> <select title="{'by Type'\|i18n( 'design/.../node/view/full' )\|wash()}"> <option value="">Any</option> ... </select> </fieldset> <fieldset> <legend>by Area</legend> {def $areas=fetch( 'content', 'list', hash( 'parent_node_id', 176 ) )} <select title="{'by Area'\|i18n( 'design/.../node/view/full' )\|wash()}"> <option value="">Any</option> {foreach $areas as $area} <option value="{$area.name}">{$area.name}</option> {/foreach} </select> </fieldset> <input id="boboton" name="boton" type="submit" value="Show" title="{'Show'\|i18n( 'design/.../node/view/full' )\|wash()}"> </form> My questions are: - What is the action/metod to use? - How to fetch date? 1, 2, 3, 4... January, February, March... 2000, 2001, 2002... - How to fetch options selection attribute? - Is the right way to do this? - Another way? - Do I think correctly? Thanks in advance.
André R.	Monday 21 July 2008 5:43:54 am One important part is to use the view cache system, so in some way you need to pass these filters as user parameters aka "mysite/myfolder/newsfolder/(filter1)/filtervalue/(filter2)/filtervalue". - What is the action/metod to use? two methods to transform the post into user parameters: 1. javascript 2. (havn't tested this but seems possible) use the DestinationURL action in content/action should work with something like this(notice the name): <fieldset> <legend>by Date</legend> <label for="my_filter_form_day" class="hide">Dia</label> <select name="(day)" id="my_filter_form_day" title="{'Day'\|i18n( 'design/.../node/view/full' )\|wash()}"> <option value="">Any</option> ... </select> - How to fetch options selection attribute? {def $option_array = $node.data_map.<selection_attribute>.content} {foreach $node.data_map.<selection_attribute>.class_content.options as $option} {if $option_array\|contains( $option.identifier )}{$option.name\|wash(xhtml)}{/if} {/foreach} eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom

Author

Message

Monday 21 July 2008 2:53:28 am

At the news folder I created a form to filter the news by:
- day
- month
- year
- group (attribute class options list [selection])
- type (attribute class options list [selection])
- area (other folder)

<form>

<fieldset>
	<legend>by Date</legend>
	<label for="Day" class="hide">Dia</label>
        <select title="{'Day'|i18n( 'design/.../node/view/full' )|wash()}">
                <option value="">Any</option>
                ...
       </select>
	<label for="Month" class="hide">Mes</label>
        <select title="{'Month'|i18n( 'design/.../node/view/full' )|wash()}">
                <option value="">Any</option>
                ...
       </select>
	<label for="Year" class="hide">Año</label>
        <select title="{'Year'|i18n( 'design/.../node/view/full' )|wash()}">
                <option value="">Any</option>
                ...
       </select>
</fieldset>

<fieldset>
	<legend>by Group</legend>
        <select title="{'by Group'|i18n( 'design/.../node/view/full' )|wash()}">
		<option value="">Any</option>
                ...
       </select>
</fieldset>

<fieldset>
	<legend>by Type</legend>
        <select title="{'by Type'|i18n( 'design/.../node/view/full' )|wash()}">
		<option value="">Any</option>
                ...
       </select>
</fieldset>

<fieldset>
	<legend>by Area</legend>
{def $areas=fetch( 'content', 'list', hash( 'parent_node_id', 176 ) )} 
        <select title="{'by Area'|i18n( 'design/.../node/view/full' )|wash()}">
            <option value="">Any</option>
            {foreach $areas as $area}             
                <option value="{$area.name}">{$area.name}</option>
            {/foreach}
       </select>
</fieldset>

<input id="boboton" name="boton" type="submit" value="Show" title="{'Show'|i18n( 'design/.../node/view/full' )|wash()}"> 
</form>

My questions are:
- What is the action/metod to use?
- How to fetch date? 1, 2, 3, 4... January, February, March... 2000, 2001, 2002...
- How to fetch options selection attribute?
- Is the right way to do this?
- Another way?
- Do I think correctly?
Thanks in advance.

André R.

Monday 21 July 2008 5:43:54 am

One important part is to use the view cache system, so in some way you need to pass these filters as user parameters aka "mysite/myfolder/newsfolder/(filter1)/filtervalue/(filter2)/filtervalue".

- What is the action/metod to use?

two methods to transform the post into user parameters:
1. javascript
2. (havn't tested this but seems possible) use the DestinationURL action in content/action
should work with something like this(notice the name):

<fieldset>
        <legend>by Date</legend>
        <label for="my_filter_form_day" class="hide">Dia</label>
       <select name="(day)" id="my_filter_form_day" title="{'Day'|i18n( 'design/.../node/view/full' )|wash()}">
               <option value="">Any</option>
               ...
      </select>

- How to fetch options selection attribute?

{def $option_array    = $node.data_map.<selection_attribute>.content}
{foreach $node.data_map.<selection_attribute>.class_content.options as $option}
    {if $option_array|contains( $option.identifier )}{$option.name|wash(xhtml)}{/if}
{/foreach}

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

eZ debug

Timing:	Jan 18 2025 16:18:46
Script start
Timing:	Jan 18 2025 16:18:46
Module start 'layout'
Timing:	Jan 18 2025 16:18:46
Module start 'content'
Timing:	Jan 18 2025 16:18:47
Module end 'content'
Timing:	Jan 18 2025 16:18:47
Script end

Main resources:

Total runtime	0.8621 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0066	587.9063	152.6250
Module start 'layout'	0.0066	0.0038	740.5313	39.4297
Module start 'content'	0.0104	0.8504	779.9609	550.7656
Module end 'content'	0.8608	0.0013	1,330.7266	12.4922
Script end	0.8621		1,343.2188

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0039	0.4474	16	0.0002
Check MTime	0.0013	0.1509	16	0.0001
Mysql Total
Database connection	0.0010	0.1203	1	0.0010
Mysqli_queries	0.8147	94.4961	54	0.0151
Looping result	0.0005	0.0563	52	0.0000
Template Total	0.8286	96.1	2	0.4143
Template load	0.0027	0.3094	2	0.0013
Template processing	0.8260	95.8025	2	0.4130
Template load and register function	0.0001	0.0089	1	0.0001
states
state_id_array	0.0017	0.2023	1	0.0017
state_identifier_array	0.0014	0.1648	2	0.0007
Override
Cache load	0.0024	0.2758	32	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0004	0.0455	2	0.0002
Fetch class attribute name	0.0009	0.1059	4	0.0002
XML
Image XML parsing	0.0008	0.0973	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0006	4	0.0000
General
dbfile	0.0008	0.0895	23	0.0000
String conversion	0.0000	0.0011	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/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 17 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs