ezdatetime as object name pattern

Next topic

Author	Message
Mads Ovesen	Monday 16 January 2006 2:18:40 pm Between ez v. 3.4.4 and 3.4.7 there has been a change in the way ezpublish interprets the ezdatetime datatype when used as an object name pattern. In v. 3.4.4 is it shown as a timestamp and in v. 3.4.7 it is shown in the datetime format. Right now I have updated a site from 3.4.4 to 3.4.7, so some objects of a class (those prior to the upgrade), which uses ezdatetime as object name pattern, show a timestamp while others (those after the upgrade) show it in datetimeformat. This is confusing, because I want to sort the objects by 'name', that is by the timestamp. The new objects, when sorted by name, is sorted like fx: friday_13_05_... monday_07_03_... saturday_05_09_... thursday_03_01_... i.e. not in any cronological order. How/Where can I change it back, so when the ezdatetime is used as a object name pattern, it uses the timestamp and not a datetime format of it?? - Thanks Mads /m
Mads Ovesen	Thursday 19 January 2006 11:57:25 pm Anyone?? Ez crew, why has this been changed?? /m
Łukasz Serwatka	Friday 20 January 2006 1:25:41 am Hi Mads, Take a look at eZDateTimeType::title() method in the kernel/classes/datatypes/ezdatetime/ezdatetimetype.php file. I can suppose that reason behind of this change was that timestamp is not human readable as object name. Object name like 'Saturday 14 January 2006 10:32:00 pm' says more about the date. However you can always do sorting on datetime attribute using sort_by or play with output format using datetime operator. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Tobias Adam	Thursday 01 June 2006 6:45:53 am Hi Mads, I had the same problem and tried format the resulting object's name when using a ezdatetime datatype as object name pattern. I wanted something like YYYY-MM-DD, so that I could use the standard "sort by name"-function in the admin view to sort the items chronologically in the backend. Because of Lukasz' tip I found out that eZ (I'm currently using version 3.6.1) uses the DateTimeFormat entry in the currently used locale ini-file (located in /share/locale) to create an object name based on an ezdatetime datatype. In my case, I edited the file ger-DE.ini in /share/locale, where I changed the value DateTimeFormat=%l, %d.%F %Y %H:%i:%s in the DateTime settings group to DateTimeFormat=%Y-%m-%d %H:%i, which leads to a result like YYYY-MM-DD HH:MM. [DateTime] TimeFormat=%H:%i:%s ShortTimeFormat=%H:%i DateFormat=%l, %d.%F %Y ShortDateFormat=%d.%m.%Y #DateTimeFormat=%l, %d.%F %Y %H:%i:%s DateTimeFormat=%Y-%m-%d %H:%i ShortDateTimeFormat=%d.%m.%Y %H:%i MondayFirst=yes

eZ debug

Timing:	Jan 19 2025 01:11:41
Script start
Timing:	Jan 19 2025 01:11:41
Module start 'layout'
Timing:	Jan 19 2025 01:11:41
Module start 'content'
Timing:	Jan 19 2025 01:11:42
Module end 'content'
Timing:	Jan 19 2025 01:11:42
Script end

Main resources:

Total runtime	0.8893 sec
Peak memory usage	4,096.0000 KB
Database Queries	62

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0066	589.1563	152.6250
Module start 'layout'	0.0066	0.0029	741.7813	39.4453
Module start 'content'	0.0096	0.8784	781.2266	584.0469
Module end 'content'	0.8879	0.0013	1,365.2734	12.1563
Script end	0.8893		1,377.4297

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0038	0.4325	16	0.0002
Check MTime	0.0019	0.2089	16	0.0001
Mysql Total
Database connection	0.0015	0.1652	1	0.0015
Mysqli_queries	0.8395	94.3990	62	0.0135
Looping result	0.0006	0.0707	60	0.0000
Template Total	0.8557	96.2	2	0.4278
Template load	0.0019	0.2102	2	0.0009
Template processing	0.8538	96.0084	2	0.4269
Template load and register function	0.0007	0.0761	1	0.0007
states
state_id_array	0.0009	0.1017	1	0.0009
state_identifier_array	0.0025	0.2816	2	0.0013
Override
Cache load	0.0015	0.1731	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.0854	3	0.0003
Fetch class attribute name	0.0018	0.1974	5	0.0004
XML
Image XML parsing	0.0009	0.1006	3	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0011	5	0.0000
General
dbfile	0.0008	0.0863	18	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
4	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
4	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	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: 13 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs