Fetch on single keyword and random objects

Next topic

Author	Message
Tore Skobba	Tuesday 11 January 2005 2:07:26 pm Hi I am making an personnal website at http://www.skobba.com (non dynamic). I there have several images in various folders, each image have several customized keywords. I would like to list up the releated images for each keyword (instead of ALL releated images to the image). Exampe: Keyword: house, three, boat Boat img 1 img 2 Three img9 etc.. Currently I only manage to get an list of ALL the reletaed images, but I want them grouped on each keyword.. Is this possible? And secondly.. Does the fetch function have an random function, I remember reading about it but I am totally unable to find it. Cheers Tore
Gabriel Ambuehl	Wednesday 12 January 2005 12:02:18 am Two ways: either use content,search instead of content,fetch or use object relations to assemble the keywords (this can potentially lead to a lot of objects you link to, though), the second way is what I did on a page to easily have topic maps. Visit http://triligon.org
Tore Skobba	Wednesday 12 January 2005 12:05:17 pm Are you sure this would work for my solution, basically I need this kind of algorithm. {section loop=$node.keywords} Keyword{$item.name} {section loop=fetch(all images having keyword $item.name} {display iamge} {section} {/section}

Author

Message

Tuesday 11 January 2005 2:07:26 pm

I am making an personnal website at http://www.skobba.com (non dynamic). I there have several images in various folders, each image have several customized keywords. I would like to list up the releated images for each keyword (instead of ALL releated images to the image). Exampe:

Keyword: house, three, boat

Boat
img 1
img 2
Three
img9
etc.. Currently I only manage to get an list of ALL the reletaed images, but I want them grouped on each keyword.. Is this possible?

And secondly.. Does the fetch function have an random function, I remember reading about it but I am totally unable to find it.

Cheers
Tore

Gabriel Ambuehl

Wednesday 12 January 2005 12:02:18 am

Two ways: either use content,search instead of content,fetch or use object relations to assemble the keywords (this can potentially lead to a lot of objects you link to, though), the second way is what I did on a page to easily have topic maps.

Visit http://triligon.org

Tore Skobba

Wednesday 12 January 2005 12:05:17 pm

Are you sure this would work for my solution, basically I need this kind of algorithm.

{section loop=$node.keywords}
   Keyword{$item.name}
   {section loop=fetch(all images having keyword $item.name}
      {display iamge}
   {section}
{/section}

eZ debug

Timing:	Jan 19 2025 11:48:18
Script start
Timing:	Jan 19 2025 11:48:18
Module start 'layout'
Timing:	Jan 19 2025 11:48:18
Module start 'content'
Timing:	Jan 19 2025 11:48:18
Module end 'content'
Timing:	Jan 19 2025 11:48:18
Script end

Main resources:

Total runtime	0.0189 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.0080	590.4063	152.6406
Module start 'layout'	0.0080	0.0040	743.0469	39.4766
Module start 'content'	0.0120	0.0047	782.5234	89.3828
Module end 'content'	0.0167	0.0022	871.9063	30.3047
Script end	0.0189		902.2109

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	16.2738	14	0.0002
Check MTime	0.0015	7.9712	14	0.0001
Mysql Total
Database connection	0.0015	7.8565	1	0.0015
Mysqli_queries	0.0044	23.1333	3	0.0015
Looping result	0.0000	0.0958	1	0.0000
Template Total	0.0017	8.9	1	0.0017
Template load	0.0009	4.9271	1	0.0009
Template processing	0.0007	3.9389	1	0.0007
Override
Cache load	0.0007	3.6793	1	0.0007
General
dbfile	0.0002	1.2857	8	0.0000
String conversion	0.0001	0.3643	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