Shuffle works only with fetch blocks?

Next topic

Author	Message
Denitsa M.	Tuesday 09 August 2011 3:28:15 am Hello, I need a manual adding items block, in which to put N items, show X of them (X < N) with shuffling. I want to use the shuffle ability of ezflow, but it seems not to be working in manual block. So I assume shuffle is working only when block uses fetch from settings, is that correct, or there is any way to use the shuffle with manual blocks too and set the valid_nodes as a random array of X items out of N? Iguana IT - http://www.iguanait.com
Felix Laate	Tuesday 09 August 2011 4:41:59 am You could use a shuffle operator. Add e.g. the http://projects.ez.no/swark_for_ez_publish_4 extension, and then use the shuffle operator to randomize the order of the $valid_nodes array. Publlic Relations Manager Greater Stavanger www.greaterstavanger.com
Denitsa M.	Tuesday 09 August 2011 4:56:14 am Thank you for your reply, but my meaning is exactly not to use any operator in templates. It is pointless system to return all N items into the valid_nodes array, when it can return only X items; imagine if N is 100 and X is 3, then this is just a waste of resources. If it was up to an operator usage, you do not even need an extra extension to do this with template code. Iguana IT - http://www.iguanait.com

Author

Message

Tuesday 09 August 2011 3:28:15 am

Hello,

I need a manual adding items block, in which to put N items, show X of them (X < N) with shuffling. I want to use the shuffle ability of ezflow, but it seems not to be working in manual block. So I assume shuffle is working only when block uses fetch from settings, is that correct, or there is any way to use the shuffle with manual blocks too and set the valid_nodes as a random array of X items out of N?

Iguana IT - http://www.iguanait.com

Felix Laate

Tuesday 09 August 2011 4:41:59 am

You could use a shuffle operator. Add e.g. the http://projects.ez.no/swark_for_ez_publish_4 extension, and then use the shuffle operator to randomize the order of the $valid_nodes array.

Publlic Relations Manager
Greater Stavanger
www.greaterstavanger.com

Denitsa M.

Tuesday 09 August 2011 4:56:14 am

Thank you for your reply, but my meaning is exactly not to use any operator in templates. It is pointless system to return all N items into the valid_nodes array, when it can return only X items; imagine if N is 100 and X is 3, then this is just a waste of resources. If it was up to an operator usage, you do not even need an extra extension to do this with template code.

Iguana IT - http://www.iguanait.com

eZ debug

Timing:	Jan 29 2025 10:19:01
Script start
Timing:	Jan 29 2025 10:19:01
Module start 'layout'
Timing:	Jan 29 2025 10:19:01
Module start 'content'
Timing:	Jan 29 2025 10:19:01
Module end 'content'
Timing:	Jan 29 2025 10:19:01
Script end

Main resources:

Total runtime	0.0201 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.0065	589.4219	151.2266
Module start 'layout'	0.0065	0.0041	740.6484	36.6875
Module start 'content'	0.0106	0.0074	777.3359	91.2500
Module end 'content'	0.0180	0.0021	868.5859	33.9766
Script end	0.0201		902.5625

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	12.4540	14	0.0002
Check MTime	0.0011	5.3333	14	0.0001
Mysql Total
Database connection	0.0015	7.5802	1	0.0015
Mysqli_queries	0.0038	18.7810	3	0.0013
Looping result	0.0000	0.1137	1	0.0000
Template Total	0.0016	7.8	1	0.0016
Template load	0.0012	5.8521	1	0.0012
Template processing	0.0004	1.9081	1	0.0004
Override
Cache load	0.0007	3.7012	1	0.0007
General
dbfile	0.0017	8.3559	8	0.0002
String conversion	0.0000	0.0296	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