fetch - sort by date created

«

Previous topic

|

|

Next topic

»

Author	Message
Marko Žmak	Friday 21 July 2006 11:47:20 am I know it is possible to sort nodes in a fetch operator function but is it possible to sort them by the date they were initially created? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Matthew Carroll	Friday 21 July 2006 11:54:22 am Is 'sort_by', 'published' not what you want? http://ez.no/doc/ez_publish/technical_manual/3_8/reference/modules/content/fetch_functions/list Matthew http://carroll.org.uk
Marko Žmak	Saturday 22 July 2006 10:12:42 am No, I don't want to sort them by "published date" but by "creation date". Sorting by "published" sorts nodes based on creation date of the last published version. But I wan't to sort them by the creation date of the object, that is the creation date of the first version that was created. Is this possible somehow? -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth
Kristof Coomans	Tuesday 25 July 2006 10:47:05 am I doubt the documentation is right about that. The published date only is initialized when the object gets published for the first time (it's still 0). The modified time is changed every time a new version is published. See kernel/content/ezcontentoperationcollection.php function setObjectStatusPublished, starting from line 184 on trunk rev. 16527 if ( $object->attribute( 'published' ) == 0 ) { $object->setAttribute( 'published', mktime() ); } $object->setAttribute( 'modified', mktime() ); independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Marko Žmak	Tuesday 25 July 2006 11:14:57 pm Yes Kristof, you're right I just verified it on my site. I think the documentation should be changed in order not to confuse people. -- Nothing is impossible. Not if you can imagine it! Hubert Farnsworth

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 21 2025 04:15:01
Script start
Timing:	Jan 21 2025 04:15:01
Module start 'layout'
Timing:	Jan 21 2025 04:15:01
Module start 'content'
Timing:	Jan 21 2025 04:15:01
Module end 'content'
Timing:	Jan 21 2025 04:15:01
Script end

Main resources:

Total runtime	0.0177 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.0067	587.9141	151.2109
Module start 'layout'	0.0067	0.0032	739.1250	36.6484
Module start 'content'	0.0099	0.0059	775.7734	94.1719
Module end 'content'	0.0159	0.0018	869.9453	37.9922
Script end	0.0177		907.9375

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	14.4256	14	0.0002
Check MTime	0.0012	6.7232	14	0.0001
Mysql Total
Database connection	0.0008	4.5188	1	0.0008
Mysqli_queries	0.0031	17.6401	3	0.0010
Looping result	0.0000	0.1464	1	0.0000
Template Total	0.0010	5.7	1	0.0010
Template load	0.0007	4.1803	1	0.0007
Template processing	0.0003	1.5152	1	0.0003
Override
Cache load	0.0005	2.6530	1	0.0005
General
dbfile	0.0015	8.2021	8	0.0002
String conversion	0.0000	0.0564	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